for--_65284e62-bd0d-4f4e-9b7f-c4ef07e76949_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printableHi Renato=2C
Bristol is delivered with 'factory' sounds which by default are in=20
/usr/local/share/bristol/memory/mini (or whichever emulator you are=20
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=2C find a subdirectory called =2C 'mini' in
your case=2C then save the memory there. The default location for the=20
cache is ~/.bristol/memory and if the subdirectory structure does not
exist then it is created (if it is possible: you need write permissions=20
in the parent directory=2C naturally).When you load memories this location is first scanned for the memory
you want=2C if that fails it will look for it in the installation 'factory'=
sounds.This gives you two choices:=20
1. configure a unique BRISTOL_CACHE for each project.
2. keep a backup manually with `cd=3B tar cfvpz bristolprojectX.tgz .bristo=
l`You may want to do both.....
Kind regards=2C nick
"we have to make sure the old choice [Windows] doesn't disappear=94.
Jim Wong=2C president of IT products=2C Acer> Date: Thu=2C 21 Jul 2011 11:36:23 +0200
--_65284e62-bd0d-4f4e-9b7f-c4ef07e76949_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
Hi Renato=2C
Bristol is delivered with 'factory' sounds which by default are in =
/usr/local/share/bristol/memory/mini (or whichever emulator you are loo=
king at). The program does not typically write to this location.Whe=
n you save a memory the GUI will look for a variable calledBRISTOL_CACH=
E=2C find a subdirectory called <=3Bemulator>=3B=2C 'mini' inyour c=
ase=2C then save the memory there. The default location for the cache i=
s ~/.bristol/memory and if the subdirectory structure does notexist the=
n it is created (if it is possible: you need write permissions in the p=
arent directory=2C naturally).When you load memories this location =
is first scanned for the memoryyou want=2C if that fails it will look f=
or 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=3B tar cfvpz bristolpr=
ojectX.tgz .bristol`You may want to do both.....
Kind regards=2C nick"we have to make sure the old choice [Windows] =
doesn't disappear=94.Jim Wong=2C president of IT products=2C Acer>=3B Date: Thu=2C 21 Jul 2011 11:36:23 +0200>=3B From: r=
ennabh@gmail.com>=3B To: linux-audio-user@lists.linuxaudio.org>=
=3B Subject: Re: [LAU] bristol saving/loading banks>=3B >=3B On=
Tue=2C 19 Jul 2011 21:55:50 +0200>=3B Renato <=3Brennabh@gmail.com=
>=3B wrote:>=3B >=3B >=3B Hello=2C I'm using the bristol mi=
ni moog. I saved a patch I created in>=3B >=3B an empty "program" s=
pace. However=2C I'd like to use this patch for a>=3B >=3B particul=
ar project=2C and I'm concerned that one day=2C using the moog for>=
=3B >=3B something else=2C I'll overwrite this patch and thus break this =
project.>=3B >=3B >=3B >=3B Is there a way to save and then=
load from command line a whole bank=2C>=3B >=3B i.e. all 999 progr=
ams? that way I'd save a different bank in each>=3B >=3B project di=
rectory I used bristol in and wouldn't have to worry of>=3B >=3B re=
membering all the program slots of all other projects>=3B >=3B =
>=3B >=3B or maybe it's possible to save (and then load) the current pr=
ogram to>=3B >=3B a file? that would actually be better>=3B &=
gt=3B >=3B >=3B cheers>=3B >=3B renato>=3B >=3B >=3B >=3B no one? so all of you using bristol are just using the g=
lobally saved>=3B programs?>=3B >=3B cheers>=3B ren=
ato>=3B _______________________________________________>=3B Lin=
ux-audio-user mailing list>=3B Linux-audio-user@lists.linuxaudio.org<=
br>>=3B http://lists.linuxaudio.org/listinfo/linux-audio-user =
=
--_65284e62-bd0d-4f4e-9b7f-c4ef07e76949_--
LINUX® is a registered trademark of Linus Torvalds in the USA and other countries.
Linuxaudio.org logo copyright Thorsten Wilms © 2006.
Hosting provided by the Virginia Tech Department of Music and DISIS.