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@xxxxxxxxx To: linux-audio-user@xxxxxxxxxxxxxxxxxxxx Subject: Re: 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@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/listinfo/linux-audio-user |
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/listinfo/linux-audio-user
