19 Jul
2011
19 Jul
'11
9:56 p.m.
Hello, I'm using the bristol mini moog. I saved a patch I created in an
empty "program" space. However, I'd like to use this patch for a
particular project, and I'm concerned that one day, using the moog for
something else, I'll overwrite this patch and thus break this project.
Is there a way to save and then load from command line a whole bank,
i.e. all 999 programs? that way I'd save a different bank in each
project directory I used bristol in and wouldn't have to worry of
remembering all the program slots of all other projects
or maybe it's possible to save (and then load) the current program to a
file? that would actually be better
cheers
renato
21 Jul
21 Jul
11:37 a.m.
On Tue, 19 Jul 2011 21:55:50 +0200
Renato <rennabh(a)gmail.com> wrote:
Hello, I'm using the bristol mini moog. I saved a
patch I created in
an empty "program" space. However, I'd like to use this patch for a
particular project, and I'm concerned that one day, using the moog for
something else, I'll overwrite this patch and thus break this project.
Is there a way to save and then load from command line a whole bank,
i.e. all 999 programs? that way I'd save a different bank in each
project directory I used bristol in and wouldn't have to worry of
remembering all the program slots of all other projects
or maybe it's possible to save (and then load) the current program to
a file? that would actually be better
cheers
renato
no one? so all of you using bristol are just using the globally saved
programs?
cheers
renato
noon
Hi Renato,
Bristol is delivered with 'factory' sounds which by default are in
/usr/local/share/bristol/memory/mini (or whichever emulator you are
looking at). The program does not typically write to this location.
When you save a memory the GUI will look for a variable called
BRISTOL_CACHE, find a subdirectory called <emulator>, 'mini' in
your case, then save the memory there. The default location for the
cache is ~/.bristol/memory and if the subdirectory structure does not
exist then it is created (if it is possible: you need write permissions
in the parent directory, naturally).
When you load memories this location is first scanned for the memory
you want, if that fails it will look for it in the installation 'factory' sounds.
This gives you two choices:
1. configure a unique BRISTOL_CACHE for each project.
2. keep a backup manually with `cd; tar cfvpz bristolprojectX.tgz .bristol`
You may want to do both.....
Kind regards, nick
"we have to make sure the old choice [Windows] doesn't disappear”.
Jim Wong, president of IT products, Acer
Date: Thu, 21 Jul 2011 11:36:23 +0200
From: rennabh(a)gmail.com
To: linux-audio-user(a)lists.linuxaudio.org
Subject: Re: [LAU] bristol saving/loading banks
On Tue, 19 Jul 2011 21:55:50 +0200
Renato <rennabh(a)gmail.com> wrote:
Hello, I'm using the bristol mini moog. I
saved a patch I created in
an empty "program" space. However, I'd like to use this patch for a
particular project, and I'm concerned that one day, using the moog for
something else, I'll overwrite this patch and thus break this project.
Is there a way to save and then load from command line a whole bank,
i.e. all 999 programs? that way I'd save a different bank in each
project directory I used bristol in and wouldn't have to worry of
remembering all the program slots of all other projects
or maybe it's possible to save (and then load) the current program to
a file? that would actually be better
cheers
renato
no one? so all of you using bristol are just using the globally saved
programs?
cheers
renato
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user 
12:05 p.m.
On 07/21/2011 12:00 PM, Nick Copeland wrote:
Hi Renato,
Bristol is delivered with 'factory' sounds which by default are in
/usr/local/share/bristol/memory/mini (or whichever emulator you are
looking at). The program does not typically write to this location.
When you save a memory the GUI will look for a variable called
BRISTOL_CACHE, find a subdirectory called <emulator>, 'mini' in
your case, then save the memory there. The default location for the
cache is ~/.bristol/memory and if the subdirectory structure does not
exist then it is created (if it is possible: you need write permissions
in the parent directory, naturally).
When you load memories this location is first scanned for the memory
you want, if that fails it will look for it in the installation
'factory' sounds.
This gives you two choices:
1. configure a unique BRISTOL_CACHE for each project.
2. keep a backup manually with `cd; tar cfvpz bristolprojectX.tgz
.bristol`
You may want to do both.....
And what about using JackSession, or do I miss something?
\r
12:09 p.m.
3. use jack session management
"we have to make sure the old choice [Windows] doesn't disappear”.
Jim Wong, president of IT products, Acer
Date: Thu, 21 Jul 2011 12:05:26 +0200
From: rosea.grammostola(a)gmail.com
To: linux-audio-user(a)lists.linuxaudio.org
Subject: Re: [LAU] bristol saving/loading banks
On 07/21/2011 12:00 PM, Nick Copeland wrote:
Hi Renato,
Bristol is delivered with 'factory' sounds which by default are
in
/usr/local/share/bristol/memory/mini (or whichever emulator you
are
looking at). The program does not typically write to this
location.
When you save a memory the GUI will look for a variable called
BRISTOL_CACHE, find a subdirectory called <emulator>,
'mini' in
your case, then save the memory there. The default location for
the
cache is ~/.bristol/memory and if the subdirectory structure
does not
exist then it is created (if it is possible: you need write
permissions
in the parent directory, naturally).
When you load memories this location is first scanned for the
memory
you want, if that fails it will look for it in the installation
'factory' sounds.
This gives you two choices:
1. configure a unique BRISTOL_CACHE for each project.
2. keep a backup manually with `cd; tar cfvpz
bristolprojectX.tgz .bristol`
You may want to do both.....
And what about using JackSession, or do I miss something?
\r
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
12:28 p.m.
On Thu, 21 Jul 2011 12:00:27 +0200
Nick Copeland <nickycopeland(a)hotmail.com> wrote:
This gives you two choices:
1. configure a unique BRISTOL_CACHE for each project.
2. keep a backup manually with `cd; tar cfvpz
bristolprojectX.tgz .bristol`
You may want to do both.....
many thanks, that works great
cheers
renato
4811
days inactive
4813
days old
linux-audio-user@lists.linuxaudio.org
5 comments
3 participants
participants (3)
-
Nick Copeland -
Renato -
rosea grammostola