12 Mar
2005
12 Mar
'05
6:23 a.m.
I take back what I said about compiling Bristol. I built the buildable bits
and moved the whole directory into /opt (or you could edit the startup script
and put it somewhere else). Then, following the instructions in the thread
mentioned below, I put "jacklaunch" before the 2 occurences of
"bristolengine" at the end of the startBristol script and I now have a
working Jackified Bristol. Well kind of. The audio engine and the jack
routing work, but the midi doesn't. Or at least it doesn't show up in the
patchbay in qjackctl.
Any ideas on how to get midi working with Bristol and libjackasyn? Is it a
question of doing something to Bristol or is it something to do with how I
configure alsa or my kernel?
Thanks
Robert
On March 11, 2005 10:31 pm, quoth Robert Persson:
I've had a little rummage and come up with this
thread:
http://music.columbia.edu/pipermail/linux-audio-dev/2003-June/004108.html
It seems like people were loading Bristol using libjackasyn, rather than
having a jackified bristol per se. One person claimed to have jackified
bristol privately, but didn't release it for copyright reasons.
And someone else mentioned how hard it is to compile bristol anyway,
patched or not. And that I know because I can't get the thing to compile
either.
Robert
--
Robert Persson
"No matter how much ye shake yer peg
The last wee drap rins doon yer leg."