<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
In release 0.40 bristol would not configure Jack MIDI interface when you<br>used the -jack option. I had not tested this interface that much so when you<br>requested -jack then bristol would still default to ALSA MIDI. Along the way<br>as more testing was done I took the obvious choice to default audio and MIDI<br>to Jack when you give the -jack flag.<br><br>That means bristol will now appear in the Jack MIDI tab of qjackctl, not in the <br>ALSA tab. Here is how you work around that:<br>
<br>
startBristol -jack -midi alsa -mini<br>
<br>
That will give you Jack audio and ALSA MIDI connections. If you want this to<br>be the default behaviour then you can edit your bristolrc and put in one line:<br>
<br>
vi $HOME/.bristol/bristolrc<br>
<br>
-jack -midi alsa<br>
<br>In my opinion, if you are using bristol 0.60.7 with jack drivers you should <br>also use the following options:<br><br>-jackstats -count <period size> -rate <samplerate><br><br>What this means it that you tell bristol, a priori, what buffer sizes and sample<br>rates it should use to be consistent with Jack. If you leave out these options<br>then bristol will attempt to find the correct rates using a poll to the daemon.<br>It works 99.999% of the time, but when it doesn't then things get a bit ugly:<br><br>-jack -jackstats -count 256 -rate 48000 -jack -midi alsa<br><br>
This will add these options every time you start bristol. Somebody recently<br>commented that the bristol command line options are a real inspiration<br>killer. No shit! Either bury these options once in the bristolrc or try using <br>monoBristol to launch the app, it will hide a lot of this stuff.<br><br>Let me know how it goes with the sticky notes and clicks/pops. In 0.60 there<br>is one known case where they still happen: monophonics without note<br>precedence (-nnp) however you have to ask for that to be configured, it is <br>not a default. The next release is intended to have a fix for this last issue.<br><br>As I said before, I can't rule out you still having the issue, there may be <br>other cases I have not considered but either send reports on this list or <br>send me an email and I will look into them.<br><br>In one of your other email you asked about Jack Session Management:<br><br>> | Build with JACK Session support ................ : false<br>><br>> What does this mean? <br>
<br>Bristol has an interface to the Jack Session Manager (JSM) so that you can<br>save application states and recover them in their entirety. I only include <br>the drivers in bristol if I find the correct Jack header files. The Jack dev<br>team will have to comment on which version that would be however last<br>time I checked it was not yet in general release. I would say that the <br>header files are not in the jack version you have installed but it shouldn't<br>give you any problems (unless you were going to use JSM of course).<br><br>
Kind regards, nick.<br><br><br>"we have to make sure the old choice [Windows] doesn't disappear”.<br>Jim Wong, president of IT products, Acer<br><br><br><br><br><hr id="stopSpelling">Date: Sat, 11 Dec 2010 22:59:49 +0000<br>From: f.rech@yahoo.fr<br>Subject: RE: [LAU] bristol synths hang<br>To: rennabh@gmail.com; nickycopeland@hotmail.com<br>CC: linux-audio-user@lists.linuxaudio.org<br><br><table border="0" cellpadding="0" cellspacing="0"><tbody><tr><td style="font: inherit;" valign="top"><br><br>--- En date de : <b>Sam 11.12.10, Nick Copeland <i><nickycopeland@hotmail.com></i></b> a écrit :<br><blockquote style="margin-left: 5px; padding-left: 5px;"><br>De: Nick Copeland <nickycopeland@hotmail.com><br>Objet: RE: [LAU] bristol synths hang<br>À: f.rech@yahoo.fr, rennabh@gmail.com<br>Cc: linux-audio-user@lists.linuxaudio.org<br>Date: Samedi 11 décembre 2010, 21h43<br><br><div id="ecxyiv1998603079">
<style>
.ExternalClass #ecxyiv1998603079 .ecxyiv1998603079hmmessage P
{padding:0px;}
.ExternalClass #ecxyiv1998603079 .ecxyiv1998603079hmmessage
{font-size:10pt;font-family:Tahoma;}
</style>
> > particular note "hangs" on the synth, and sending note off events<br>> > doesn't stop it... I have to restart the program, which makes it<br>> > unusable since it happens quite often. Untill now this happenede with<br>> > b3, minimoog and dx7.<br><br>> I have the same problem here, playing with an usb keyboard.<br>> Sometimes you probably have "clicks" (digital saturation) too.<br><br>Bristol has had these issues although they were supposed to have been <br>iron out in the later releases. The cause of the clicks was largely due to<br>voice reassignment with mono synths fixed by implementing a different<br>note assignment method (note preference with droning) and the sticky<br>notes were due to scheduling issues between threads fixed with a jack<br>ringbuffer message passing method.<br><br>Now a lot of the distributions are still packaging bristol-0.40 which is <br>a couple of years out of date. If you have newer versions
then I can<br>work on some debuging with you, if you don't have 0.60 then it would<br>make sense to try that first.<br><br>I cannot rule out other issues but lets start with the versions you have<br>and take it from there.<br><br>Kind regards, nick.<br><br><br>Have compile 0.60 with no problem, and no clicks anymore :)<br>But now Bristol lives -alone- in Qjacks'MIDI tab, and the rest of MIDI stuff are in ALSA tab...<br>What did I missed ?<br>
</div></blockquote></td></tr></tbody></table><br> </body>
</html>