i see..... well, then i guess i have to question my memlock or nice settings again, dont I? <br><br>I&#39;ve tried the standard settings, nice @ -19 and then up to 19, memlock at 100%, rt prio at 99.  Memlock to 50%, to 65%. I haven&#39;t screwed around with rtprio much, though...... <br>
<br>My question now, would be: what are these settings actually doing? memlock seems to speak for itself, how much available mem is set for audio purposes...right?<br><br> but I dont see the difference between rtprio and nice, I only know that they handle interrupt priority in an indirect way. perhaps i&#39;ve been setting them incorrectly; for nice and rtprio, the lowest number = highest priority?<br>
<br>Otherwise, I just don&#39;t see why each time i changed the settings, i would get no difference. It makes sense that my cpu would be constantly running at 60% if I were to set memlock to 50 or 60%, but the xrun count was always rediculous. and yes, tried restarts each time, for the jack server, and my computer itself. <br>
<br>Guess I&#39;m looking for some good guidelines to follow while tweaking this stuff, too. Like what settings might be good for an amd x2 using 2gb ram?<br><br>thanks for the help<br><br><div class="gmail_quote">On Mon, Nov 16, 2009 at 4:37 PM, Hartmut Noack <span dir="ltr">&lt;<a href="mailto:zettberlin@linuxuse.de">zettberlin@linuxuse.de</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
Gary Morgan schrieb:<br>
<div class="im"><br>
&gt;<br>
&gt; This is after tweaking memlocks, nice %s , buffers and so on.<br>
&gt;<br>
&gt; I know that chipset sound, is not a very efficient recording interface, but<br>
&gt; it seems there is more going on, besides that.<br>
&gt;<br>
&gt; I have two main questions here (they sum up to: how much of this is the<br>
&gt; chipset?)<br>
&gt; a. i had heard here and there in forums that the RT kernel in 9.04 and on<br>
&gt; was &#39;broken&#39;. is that true?<br>
<br>
</div>9.4 was broken 9.10 works very good for me...<br>
<div class="im"><br>
&gt; b. Is RT only worth using for higher end machines with more ram and separate<br>
&gt; sound cards?<br>
<br>
</div>no -  the opposite is true: with a proper rt-kernel you can run critical<br>
 stuff on lower machines also. It just grabs everything your box can do<br>
for audio...<br>
<br>
<div class="im"><br>
&gt; And one more: Would anyone recommend using a different audio OS for this<br>
&gt; situation, like 64 studio?<br>
<br>
</div>Not really, wait until it is stable I would suggest...<br>
If you want to try something debianish go for pure:dyne or AVLinux.<br>
<div class="im"><br>
&gt;(i might have mentioned jacklab, but it seems<br>
&gt; that project has been killed)<br>
<br>
</div>Not so much killed but died more or less without big shock and awe...<br>
Still OpenSuse is very good for audio with the rt-kernel from jengelh<br>
installed...<br>
<br>
best regs<br>
<br>
HZN<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.9 (GNU/Linux)<br>
Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org" target="_blank">http://enigmail.mozdev.org</a><br>
<br>
iEYEARECAAYFAksB1DMACgkQ1Aecwva1SWNvpgCeMtKpL1JZBCgtQxgdYSOoD2Nd<br>
PgcAoIezwBpz2kK4B5OXMP2cGOelPpmz<br>
=PJFS<br>
-----END PGP SIGNATURE-----<br>
</blockquote></div><br>