14 Oct
2012
14 Oct
'12
9:07 a.m.
Hello, Andrew--
Thank you for your help! Your solution worked perfectly, once i jumped a few
hurdles on my end. First, i had to figure out how to middle click. i've never
had a mouse with a middle click, so i've never had to solve the problem.
Fortunately, my touchpad has a way of doing it. Then, i made things more
complicated then necessary. i ran the b3 with the -gmc switch, being absolutely
sure that the gui itself should receive this message. i was wrong.
You wouldn't happen to know, Andrew, if these connections can be stored? It
would be easiest, if i'm ever in a live situation, to be able to call up the b3
without remapping all the midi assignments. i'm always a little nervous asking
these things, though. If the only solution is to write the code, i wouldn't
know how to do it.
Thanks, again, Andrew. Take care.
bill
On October 11, 2012 at 10:35 AM Andrew C <countfuzzball(a)gmail.comn> wrote:
Hello Bill,
Bristol does support this (indeed, nearly anything that's on the GUI
is midi cc controllable, buttons, sliders, knobs etc).
To get it work, you just need to middle click on the drawbar on the
GUI, then move the physical fader on your controller and the
connection should be set.
With my M-audio oxygen 61 at least, it works flawlessly.
Andrew.
On Thu, Oct 11, 2012 at 2:53 PM, bill(a)wolfcomposer.com
<bill(a)wolfcomposer.com> wrote:
> Hello, All--
>
> i'm curious. Can Bristol receive control-change messages? i've a midi
> controller with eight faders and would love for them to control the drawbars
> on Bristol's b3 gui. Any reading material would be greatly appreciated.
>
> Thank you, much, for your help.
> bill
>
>
> _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user(a)lists.linuxaudio.org
> http://lists.linuxaudio.org/listinfo/linux-audio-user
>
14 Oct
14 Oct
9:36 a.m.
New subject: bristol and midi
You wouldn't happen to know, Andrew, if these
connections can be stored? It would be > easiest, if i'm ever in a live situation,
to be able to call up the b3 without remapping all > the midi assignments. i'm
always a little nervous asking these things, though. If the > only solution is to
write the code, i wouldn't know how to do it.
There is a MIDI mapping file for
each emulator, the settings are global to all of its memoriesand it is saved every time
you save a memory. The settings are reloaded when the synthrestarts so if you set up the
drawbar mappings 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 commandline when you
start bristol then you can put them in your ${HOME}/.bristol/bristolrc file. The README
explains some of that but if you can't find the README file then post a reply here and
I can give you some examples of the contents of this file too.
Regards, nick.
On October 11, 2012 at 10:35 AM Andrew C <countfuzzball(a)gmail.comn> wrote:
Hello Bill,
Bristol does support this (indeed, nearly anything
that's on the GUI
is midi cc controllable, buttons, sliders, knobs etc).
To get it work, you just need to middle click on the
drawbar on the
GUI, then move the physical fader on your controller
and the
connection should be set.
With my M-audio oxygen 61 at least, it works
flawlessly.
Andrew.
On Thu, Oct 11, 2012 at 2:53 PM, bill(a)wolfcomposer.com
<bill(a)wolfcomposer.com> wrote:
> Hello, All--
> > i'm curious. Can Bristol receive
control-change messages? i've a midi
> controller with eight faders and would love for
them to control the drawbars
> on Bristol's b3 gui. Any reading material
would be greatly appreciated.
> > Thank you, much, for your help.
> bill
> > _______________________________________________
> Linux-audio-user mailing list
> Linux-audio-user(a)lists.linuxaudio.org
>
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
15 Oct
15 Oct
6:27 p.m.
New subject: bristol and midi
Hello, Gentleman--
There is a MIDI mapping file for each emulator, the
settings are global to all
of its memories
and it is saved every time you save a memory. The settings are reloaded when
the synth
restarts so if you set up the drawbar mappings for your MIDI controller and
save that memory
you will have them active next time you start the organ.
Thank you, Nick. i had tried this before writing, and it didn't work. i was
pressed for time, though, and my initial error could have been as simple as not
connecting Bristol to the MIDI controller after making the initial mapping to
the fader, closing Bristol, and then starting it, again. Everything worked,
this morning, and i've made an initial B3 setting in my controller.
If you have a complex set of options that you have to
give on the commandline
when you
start bristol then you can put them in your ${HOME}/.bristol/bristolrc file.
The README
explains some of that but if you can't find the README file then post a reply
here and I
can give you some examples of the contents of this file too.
i doubt i'll need this, but it's always good to be prepared. i've printed
the
README--from startBristol -readme, i presume. After having it bound, i'll give
it a more thorough reading. Up to this point, i've been using it as a reference
manual to learn more about each synth. i would enjoy looking at any examples
you send, Nick, but let me dig around for a few days and see what i can learn.
i'll let you know when i'm ready.
Thank you, again, everybody.
Best,
bill
14 Oct
14 Oct
9:42 a.m.
New subject: bristol and midi
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 12 Oct 2012 08:10:58 -0400 (EDT)
"bill(a)wolfcomposer.com" <bill(a)wolfcomposer.com> wrote:
You wouldn't happen to know, Andrew, if these
connections can be
stored?
Hi, can't verify this ATM, but don't they get stored along with the
rest of the preset in ~/.bristol/memory/synth/ when you save the preset
in the GUI?
cheers,
renato
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQEcBAEBAgAGBQJQemzQAAoJEBz6xFdttjrfEnkH+gLWZveq8MWlQ6PmcdvmmqNf
WyFInq3we9yah2t6/ajRhrBHqgBYEZ9vPTjtcSglQzmalDxVO57HfmN54hb7l0wb
HoEb5XpwKPVyATT2cS/Zer4xjxDx1zygP9xnkbi4gFUINHQteZGOPxqgr6fJPBVf
qTfhR3HF2kPoRDKc8rNFOAcs0LeK9suDibdyrKb66Y4OPp4A9fU0ps26oMOlqzFo
OYfgRH42hiiFiEmAS56y57YvJs600axj6OhCKesmJ8cpxpklCWH850KYEe5G7JYz
KkyrIbi1uO5hlZrxMgeVaHmBJ95WKHFh5rKnyJCfcnQnz2TYV9/swDLY9cdqz4Q=
=esum
-----END PGP SIGNATURE-----
4451
days inactive
4452
days old
linux-audio-user@lists.linuxaudio.org
3 comments
3 participants
participants (3)
-
bill＠wolfcomposer.com -
Nick Copeland -
Renato