Bristol .30.3 needs jackd .109

  • cinder
Posted: Thu, 01/08/2009 - 12:22
I just tried to compile the latest Bristol after reading the HOW-TO in the tutorial section. No luck. I posted at sourceforge and the author said my version of jackd may be incompatible (.103), and that he compiled against .109. I can't find .109 in the repositories here, and I remember a big long thread between Quentin and skullnotions trying to find the elusive 109. So, I downloaded the source from sourceforge (not even the jack web site it). Is it a bad idea to install this allien code as apposed to a binary .deb? 64studio timing is everything!

@stevea: Thanks for the

  • azzapkp
  • 02/12/09
  • Sun, 02/15/2009 - 20:53
@stevea: Thanks for the compile options tip! I've just compiled 30.4 and it seems to be running ok. I haven't tested anything in any detail yet but it starts which is more than Bristol did out of the box :P

Bristol

  • cinder
  • 10/20/08
  • Fri, 01/09/2009 - 09:53
Thanks stevea! I've got Bristol Compiled without jack MIDI. Looks like a lot of time and effort has gone into it. And look! ... a granular synth. That's how a lot of the Native Instruments work. Timing is Everything!

by the way...

  • stevea
  • 06/25/07
  • Thu, 01/08/2009 - 21:30
Once Bristol is up and running, one thing which isn't obvious is how to assign physical controllers on an external midi keyboard to the various controls in the GUI. Here is how to do it: 1. position the cursor over the control in the GUI 2. click the middle button (for synaptics touchpad this is done by tapping top right of the pad) 3. move the physical controller you wish to allocate to this control that's it ! - the control on your external midi keyboard will now control the GUI To save this config for next time, you need to select save in the GUI

compiler flag

  • stevea
  • 06/25/07
  • Thu, 01/08/2009 - 21:19
I've got latest Bristol working OK in 2.1 There is a compiler flag to switch-off Jack-midi inputs. --disable-jack-midi Note that this is jack-midi which is being disabled - it doesn't prevent Bristol from outputting via Jack, nor does it stop Bristol from taking Midi from alsa (which is the way most things work anyway). basically, jack midi is a new feature and isn't needed. compile flag info is here http://bristol.sourceforge.net/news.html