[LAU] Re: problems with Bristol on x86_64 SOLVED

Nick Copeland nickycopeland at hotmail.com
Wed Apr 18 04:29:34 EDT 2007


Hi All,

>to hack a bit with the build process to put everything in the standard 
>bin,usr/lib, and home directories.

There is an enhancement request open to put the source code under the GNU 
tools including install option. Its not top of my list but it is there.

>Also, I haven't figured out how to assign MIDI controllers to the graphics 
>controls

The engine and GUI are separate elements. You need to aconnect the engine, 
bristol, to a keyboard to be able play it. You also need to connect the GUI, 
brighton, to a MIDI controller to be able to drive the GUI. This is also 
with aconnect and both bristol and brighton should be visible. Then, place 
the mouse over the GUI device you want to control and press the middle mouse 
button, then joggle the MIDI control you want to drive it from.

>Even MIDI volume wasn't working on me with the Hammond.

There are a few things here. MIDI volume is a GM2 controller however these 
go through the GUI, not through the engine, so it would still need to be 
connected up to the GUI for them to possibly work. If you are actually after 
a swell pedal I will check the code. The engine does have access to all the 
MIDI controllers but only responds, per default, to few of them (pitchbend, 
modwheel, and some pressure tracking). It would make sense for some of the 
synths to respond to typical input devices such as the pedal in the case of 
the b3.

Regards,

Nick.

_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar - get it now! 
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/




More information about the Linux-audio-user mailing list