Yet again, I discover something strange.
From html/UsingRealTime.html
"DO NOT
use "--sched" if you are using JACK for audio output."
and later on the same page:
"An example of buffer settings for low latency on a fast system:
jackd -d alsa -P -r 48000 -p 64 -n 4 -zt &
csound -+rtaudio=jack -b 64 -B 256 [...]
with real time scheduling (as root):
jackd -R -P 90 -d alsa -P -r 48000 -p 64 -n 2 -zt &
csound --sched=80,90,10 -d -+rtaudio=jack -b 64 -B 192 [...]"
So it says DO NOT use "--sched" with "-+rtaudio=jack", but has an example using "--sched=N,MAXCPU,TIME" with "-+rtaudio=jack".
I know this whole setup is not common knowledge, and even the documentation for the Linux and Jack ends of things is poor, but can anyone straighten this all out for me?
If I'm using Csound with Jack, can I use "--sched=N" or not?
And it was my understanding that Jack clients should have slightly LOWER priority than jackd; but in this example they are set the same. What gives?
-Chuckk
On 10/30/07,
Chuckk Hubbard <badmuthahubbard@gmail.com> wrote:
Hi.
Debian 64 testing, 2.6.22.1, rt patch, limits.conf edited for rtprio.
So I'm running a test .csd with these flags:
<CsOptions>
-d -+rtaudio=jack -o dac:alsa_pcm:playback_ --sched=99 -b256 -B512
</CsOptions>
and when I check the csound processes in htop I see one that runs PRI 20 and one -45. If I switch to --sched=67, I still see 20 and -45. If I run --sched=37, it's 20 and -45. If I run --sched with no value, it's 20 and -45.
Am I not checking the priority correctly, or am I not entering the flag correctly?
Thanky.
-Chuckk
--
http://www.badmuthahubbard.com
--
http://www.badmuthahubbard.com