Re: [LAU] bristol and midi

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <bill@...>, linux-audio-user@lists.linuxaudio.org <linux-audio-user@...>, countfuzzball@gmail.com <countfuzzball@...>
Date: Sunday, October 14, 2012 - 7:36 am

--_da137918-ce4a-47eb-b421-afffaf015c80_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

> You wouldn't happen to know=2C Andrew=2C if these connections can be stor=
ed? It would be > easiest=2C if i'm ever in a live situation=2C to be able=
to call up the b3 without remapping all > the midi assignments. i'm alway=
s a little nervous asking these things=2C though. If the > only solution i=
s to write the code=2C i wouldn't know how to do it.
There is a MIDI mapping file for each emulator=2C the settings are global t=
o all of its memoriesand it is saved every time you save a memory. The sett=
ings are reloaded when the synthrestarts so if you set up the drawbar mappi=
ngs for your MIDI controller and save that memoryyou will have them active =
next time you start the organ.
If you have a complex set of options that you have to give on the commandli=
ne when you start bristol then you can put them in your ${HOME}/.bristol/br=
istolrc file. The README explains some of that but if you can't find the RE=
ADME file then post a reply here and I can give you some examples of the co=
ntents of this file too.

Regards=2C nick.
On October 11=2C 2012 at 10:35 AM Andrew C wrote=
:=20
=20
=20
=20

=20
=20
=20
=20
=20
=20
=20
=20
=20
=20
=20
=20
=20
=20
=20
=20
=20
=20
wbars=20
=20
.=20
=20
=20
=20
=20
=20
=20
=20
=20
=20
=20
=20
=20
=20
=20

_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user =

--_da137918-ce4a-47eb-b421-afffaf015c80_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

&gt=3B You wouldn't happen to know=2C Andrew=2C if these connecti=
ons can be stored?&nbsp=3B It would be&nbsp=3B&gt=3B easiest=2C if i'm =
ever in a live situation=2C to be able to call up the b3 without remapping =
all&nbsp=3B&gt=3B the midi assignments.&nbsp=3B i'm always a little ner=
vous asking these things=2C though.&nbsp=3B If the&nbsp=3B&gt=3B only s=
olution is to write the code=2C i wouldn't know how to do it.Th=
ere is a MIDI mapping file for each emulator=2C the settings are global to =
all of its memoriesand it is saved every time you save a memory. The se=
ttings are reloaded when the synthrestarts so if you set up the drawbar=
mappings for your MIDI controller and save that memoryyou will have th=
em active next time you start the organ.If you have a complex s=
et of options that you have to give on the commandline when you&nbsp=3B=
start bristol then you can put them in your ${HOME}/.bristol/bristolrc file=
. The README&nbsp=3Bexplains some of that but if you can't find the REA=
DME file then post a reply here and I&nbsp=3Bcan give you some examples=
of the contents of this file too.Regards=2C nick.<=
div id=3D"ecxmcePresetContent" style=3D"" class=3D"ecxmceHTML">On October 1=
1=2C 2012 at 10:35 AM Andrew C &lt=3Bcountfuzzball@gmail.comn&gt=3B wrote:=
=20
=20
&gt=3B Hello Bill=2C=20
&gt=3B=20
&gt=3B Bristol does support this (indeed=2C nearly anything that's =
on the GUI=20
&gt=3B is midi cc controllable=2C buttons=2C sliders=2C knobs etc).=
=20
&gt=3B To get it work=2C you just need to middle click on the drawb=
ar on the=20
&gt=3B GUI=2C then move the physical fader on your controller and t=
he=20
&gt=3B connection should be set.=20
&gt=3B=20
&gt=3B With my M-audio oxygen 61 at least=2C it works flawlessly.=20
&gt=3B=20
&gt=3B Andrew.=20
&gt=3B=20
&gt=3B On Thu=2C Oct 11=2C 2012 at 2:53 PM=2C bill@wolfcomposer.com=
=20
&gt=3B &lt=3Bbill@wolfcomposer.com&gt=3B wrote:=20
&gt=3B &gt=3B Hello=2C All--=20
&gt=3B &gt=3B=20
&gt=3B &gt=3B i'm curious.&nbsp=3B Can Bristol receive control-chan=
ge messages?&nbsp=3B i've a midi=20
&gt=3B &gt=3B controller with eight faders and would love for them =
to control the drawbars=20
&gt=3B &gt=3B on Bristol's b3 gui.&nbsp=3B Any reading material wou=
ld be greatly appreciated.=20
&gt=3B &gt=3B=20
&gt=3B &gt=3B Thank you=2C much=2C for your help.=20
&gt=3B &gt=3B bill=20
&gt=3B &gt=3B=20
&gt=3B &gt=3B=20
&gt=3B &gt=3B _______________________________________________=20
&gt=3B &gt=3B Linux-audio-user mailing list=20
&gt=3B &gt=3B Linux-audio-user@lists.linuxaudio.org=20
&gt=3B &gt=3B http://lists.linuxaudio.org/listinfo/linux-audio-user=
=20
&gt=3B &gt=3B
=20
&nbsp=3B=20

=20
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
=

--_da137918-ce4a-47eb-b421-afffaf015c80_--

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [LAU] bristol and midi, bill@wolfcomposer.com, (Sun Oct 14, 7:07 am)
Re: [LAU] bristol and midi, Renato, (Sun Oct 14, 7:42 am)
Re: [LAU] bristol and midi, Nick Copeland, (Sun Oct 14, 7:36 am)
Re: [LAU] bristol and midi, bill@wolfcomposer.com, (Mon Oct 15, 4:27 pm)