<html><head><meta name="qrichtext" content="1" /></head><body style="font-size:8pt;font-family:Nimbus Sans L">
<p>On Tuesday 10 March 2009 09:06:16 Cassiel wrote:</p>
<p>> generic or custom (rt patched) kernel?</p>
<p></p>
<p>Generic, Debian stock.</p>
<p></p>
<p>I didn't have time yet to try out and patch and build a kernel myself. (It's been a while since I did that).</p>
<p></p>
<p>sincerely,</p>
<p>Marije</p>
<p></p>
<p>> r</p>
<p>></p>
<p>> 2009/3/10 nescivi <nescivi@gmail.com></p>
<p>></p>
<p>> > realtime priorities were handled through limits.conf, and I am running on</p>
<p>> > the</p>
<p>> > Debian kernel 2.6.26-1-amd64 on a Intel Core2 Duo, T7500 2.20 GHz. (It's</p>
<p>> > a Lenovo Thinkpad T61).</p>
<p>> ></p>
<p>> > The previous Debian kernel 2.6.24, did give me better results with JACK,</p>
<p>> > but</p>
<p>> > had problem with the serial chip driver (the FTDI), at certain baudrates.</p>
<p>> ></p>
<p>> > So yes, the few xruns were problematic, since my soundtrack was the only</p>
<p>> > sound</p>
<p>> > that was going on, and I would really like to know how I could make this</p>
<p>> > whole setup a bit more robust.</p>
<p>> ></p>
<p>> > The video capturing and the visualisation are certainly less time</p>
<p>> > critical, as</p>
<p>> > I am only deriving control data from it, and/or using it to monitor. It</p>
<p>> > is not projected out again.</p>
<p>> ></p>
<p>> > sincerely,</p>
<p>> > Marije</p>
<p></p>
<p></p>
<p></p>
</body></html>