24 Oct
2007
24 Oct
'07
10:01 a.m.
Hallo.
I posted to the jackit-devel list too, so apologies if you're seeing this
again. No luck there...
jackd version 0.103.0 tmpdir /dev/shm protocol 16
2.6.22.1-rt9
Debian testing
I've just noticed that I am unable to set jackd priority on the command
line. I have a script set up to use "sudo chrt" to change it, but when I
comment out that line in the script, jackd runs at 0 with schedule "other".
My script:
sudo chrt -fp 82 `pidof "IRQ-16"`
jackd --realtime -P 70 -dalsa -P -p256 -n2 -r44100 &
sudo chrt -fp 70 `pidof "jackd"`
chrt -p `pidof "IRQ-16"`
chrt -p `pidof "jackd"`
exit
If I comment out the second sudo chrt line, the last line returns:
pid 5032's current scheduling policy: SCHED_OTHER
pid 5032's current scheduling priority: 0
otherwise it is SCHED_FF and 70.
My kernel has:
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT_DESKTOP is not set
CONFIG_PREEMPT_RT=y
CONFIG_PREEMPT=y
CONFIG_PREEMPT_SOFTIRQS=y
CONFIG_PREEMPT_HARDIRQS=y
CONFIG_PREEMPT_BKL=y
# CONFIG_CLASSIC_RCU is not set
CONFIG_PREEMPT_RCU=y
/etc/security/limits.conf has:
@audio - nice -10
@audio - rtprio 99
@audio - memlock 4000000 (someone on the jack list suggested
that my previous value "unlimited" was not recognized, so I stuck this in
but no change)
and user "chuckk" is in group "audio".
Lastly, the output from my script when the second sudo chrt line is
commented out:
------------------------------
pid 684's current scheduling policy: SCHED_FIFO
pid 684's current scheduling priority: 82
jackd 0.103.0
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
pid 5132's current scheduling policy: SCHED_OTHER
pid 5132's current scheduling priority: 0
loading driver ..
Enhanced3DNow! detected
SSE2 detected
apparent rate = 44100
creating alsa driver ... hw:0|-|256|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 256 frames, buffer = 2 periods
ALSA: final selected sample format for playback: 32bit little-endian
ALSA: use 2 periods for playback
--------------------------------------
Any ideas what I may have missed or misconfigured?
Thanks!
-Chuckk
--
http://www.badmuthahubbard.com
24 Oct
24 Oct
10:30 a.m.
Chuckk Hubbard wrote:
Hallo.
I posted to the jackit-devel list too, so apologies if you're seeing
this again. No luck there...
jackd version 0.103.0 tmpdir /dev/shm protocol 16
2.6.22.1-rt9
Debian testing
I've just noticed that I am unable to set jackd priority on the
command line. I have a script set up to use "sudo chrt" to change it,
but when I comment out that line in the script, jackd runs at 0 with
schedule "other".
My script:
sudo chrt -fp 82 `pidof "IRQ-16"`
jackd --realtime -P 70 -dalsa -P -p256 -n2 -r44100 &
sudo chrt -fp 70 `pidof "jackd"`
chrt -p `pidof "IRQ-16"`
chrt -p `pidof "jackd"`
exit
If I comment out the second sudo chrt line, the last line returns:
pid 5032's current scheduling policy: SCHED_OTHER
pid 5032's current scheduling priority: 0
otherwise it is SCHED_FF and 70.
chuckk, i can only try to guess.
perhaps sudo on your system is not allowed to do chrt?
on my system i have the file /etc/sudoers containing this two important
lines:
root ALL=(ALL) ALL
nowhiskey ALL=NOPASSWD: ALL
don't know if it could be the root of the problem, because if so, i
would expect something like 'operation not permitted' error, but who knows.
cheers,
doc
My kernel has:
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT_DESKTOP is not set
CONFIG_PREEMPT_RT=y
CONFIG_PREEMPT=y
CONFIG_PREEMPT_SOFTIRQS=y
CONFIG_PREEMPT_HARDIRQS=y
CONFIG_PREEMPT_BKL=y
# CONFIG_CLASSIC_RCU is not set
CONFIG_PREEMPT_RCU=y
/etc/security/limits.conf has:
@audio - nice -10
@audio - rtprio 99
@audio - memlock 4000000 (someone on the jack list
suggested that my previous value "unlimited" was not recognized, so I
stuck this in but no change)
and user "chuckk" is in group "audio".
Lastly, the output from my script when the second sudo chrt line is
commented out:
------------------------------
pid 684's current scheduling policy: SCHED_FIFO
pid 684's current scheduling priority: 82
jackd 0.103.0
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
pid 5132's current scheduling policy: SCHED_OTHER
pid 5132's current scheduling priority: 0
loading driver ..
Enhanced3DNow! detected
SSE2 detected
apparent rate = 44100
creating alsa driver ... hw:0|-|256|2|44100|0|0|nomon
|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 256 frames, buffer = 2 periods
ALSA: final selected sample format for playback: 32bit little-endian
ALSA: use 2 periods for playback
--------------------------------------
Any ideas what I may have missed or misconfigured?
Thanks!
-Chuckk
--
http://www.badmuthahubbard.com
------------------------------------------------------------------------
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
10:59 a.m.
Hi doc, thanks for the guess. sudo chrt does work, though. I'm supposed to
not need it with the rt-patched kernel, which allows non-root users to set
high priorities.
-Chuckk
On 10/24/07, Dragan Noveski <perodog(a)gmx.net> wrote:
chuckk, i can only try to guess.
perhaps sudo on your system is not allowed to do chrt?
on my system i have the file /etc/sudoers containing this two important
lines:
root ALL=(ALL) ALL
nowhiskey ALL=NOPASSWD: ALL
don't know if it could be the root of the problem, because if so, i
would expect something like 'operation not permitted' error, but who
knows.
cheers,
doc
--
http://www.badmuthahubbard.com
My kernel has:
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT_DESKTOP is not set
CONFIG_PREEMPT_RT=y
CONFIG_PREEMPT=y
CONFIG_PREEMPT_SOFTIRQS=y
CONFIG_PREEMPT_HARDIRQS=y
CONFIG_PREEMPT_BKL=y
# CONFIG_CLASSIC_RCU is not set
CONFIG_PREEMPT_RCU=y
/etc/security/limits.conf has:
@audio - nice -10
@audio - rtprio 99
@audio - memlock 4000000 (someone on the jack list
suggested that my previous value "unlimited" was not recognized, so I
stuck this in but no change)
and user "chuckk" is in group "audio".
Lastly, the output from my script when the second sudo chrt line is
commented out:
------------------------------
pid 684's current scheduling policy: SCHED_FIFO
pid 684's current scheduling priority: 82
jackd 0.103.0
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK compiled with System V SHM support.
pid 5132's current scheduling policy: SCHED_OTHER
pid 5132's current scheduling priority: 0
loading driver ..
Enhanced3DNow! detected
SSE2 detected
apparent rate = 44100
creating alsa driver ... hw:0|-|256|2|44100|0|0|nomon
|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 256 frames, buffer = 2 periods
ALSA: final selected sample format for playback: 32bit little-endian
ALSA: use 2 periods for playback
--------------------------------------
Any ideas what I may have missed or misconfigured?
Thanks!
-Chuckk
--
http://www.badmuthahubbard.com
------------------------------------------------------------------------
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
2:51 p.m.
On Wed, 2007-10-24 at 15:59 +0300, Chuckk Hubbard wrote:
Hi doc, thanks for the guess. sudo chrt does work,
though. I'm
supposed to not need it with the rt-patched kernel, which allows
non-root users to set high priorities.
Not exactly right. The rt-patched kernel (Ingo's patches) only optimizes
the max latency paths in the kernel. Other software is what allows
non-root users to use SCHED_FIFO scheduling. There are several options,
the current one is /etc/security/limits.conf through PAM, there are
others.
-- Fernando
On 10/24/07, Dragan Noveski <perodog(a)gmx.net>
wrote:
chuckk, i can only try to guess.
perhaps sudo on your system is not allowed to do chrt?
on my system i have the file /etc/sudoers containing this two
important
lines:
root ALL=(ALL) ALL
nowhiskey ALL=NOPASSWD: ALL
don't know if it could be the root of the problem, because if
so, i
would expect something like 'operation not permitted' error,
but who knows.
cheers,
doc
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
--
http://www.badmuthahubbard.com
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
My kernel has:
# CONFIG_PREEMPT_NONE is not set
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT_DESKTOP is not set
CONFIG_PREEMPT_RT=y
CONFIG_PREEMPT=y
CONFIG_PREEMPT_SOFTIRQS=y
CONFIG_PREEMPT_HARDIRQS=y
CONFIG_PREEMPT_BKL=y
# CONFIG_CLASSIC_RCU is not set
CONFIG_PREEMPT_RCU=y
/etc/security/limits.conf has:
@audio - nice -10
@audio - rtprio 99
@audio - memlock 4000000 (someone on the
jack list
suggested that my previous value
"unlimited" was not
recognized, so I
stuck this in but no change)
and user "chuckk" is in group "audio".
Lastly, the output from my script when the second sudo chrt
line is
commented out:
------------------------------
pid 684's current scheduling policy: SCHED_FIFO
pid 684's current scheduling priority: 82
jackd 0.103.0
Copyright 2001-2005 Paul Davis and others.
jackd comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute
it
under certain conditions; see the file COPYING
for details
JACK compiled with System V SHM support.
pid 5132's current scheduling policy: SCHED_OTHER
pid 5132's current scheduling priority: 0
loading driver ..
Enhanced3DNow! detected
SSE2 detected
apparent rate = 44100
creating alsa driver ... hw:0|-|256|2|44100|0|0|nomon
|swmeter|-|32bit
control device hw:0
configuring for 44100Hz, period = 256 frames, buffer = 2
periods
ALSA: final selected sample format for playback:
32bit
little-endian
ALSA: use 2 periods for playback
--------------------------------------
Any ideas what I may have missed or misconfigured?
Thanks!
-Chuckk
--
http://www.badmuthahubbard.com
------------------------------------------------------------------------
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
4:20 p.m.
On 10/24/07, Fernando Lopez-Lezcano <nando(a)ccrma.stanford.edu> wrote:
Still true.
-Chuckk
--
http://www.badmuthahubbard.com
On Wed, 2007-10-24 at 15:59 +0300, Chuckk Hubbard wrote:
I see; that makes more sense now.
Any idea why Linux wouldn't honor /etc/security/limits.conf?
Hi doc, thanks for the guess. sudo chrt does
work, though. I'm
supposed to not need it with the rt-patched kernel, which allows
non-root users to set high priorities.
Not exactly right. The rt-patched kernel (Ingo's patches) only optimizes
the max latency paths in the kernel. Other software is what allows
non-root users to use SCHED_FIFO scheduling. There are several options,
the current one is /etc/security/limits.conf through PAM, there are
others.
/etc/security/limits.conf has:
@audio - nice -10
@audio - rtprio 99
@audio - memlock 4000000 (someone on the
jack list
suggested that my previous value
"unlimited" was not
recognized, so I
> stuck this in but no change)
>
> and user "chuckk" is in group "audio". 
6:36 p.m.
On Wednesday 24 October 2007, Chuckk Hubbard wrote:
Hallo.
I posted to the jackit-devel list too, so apologies if you're seeing this
again. No luck there...
jackd version 0.103.0 tmpdir /dev/shm protocol 16
2.6.22.1-rt9
Debian testing
I've just noticed that I am unable to set jackd priority on the command
line. I have a script set up to use "sudo chrt" to change it, but when I
comment out that line in the script, jackd runs at 0 with schedule "other".
My script:
sudo chrt -fp 82 `pidof "IRQ-16"`
jackd --realtime -P 70 -dalsa -P -p256 -n2 -r44100 &
sudo chrt -fp 70 `pidof "jackd"`
chrt -p `pidof "IRQ-16"`
chrt -p `pidof "jackd"`
exit
if you run
sudo chrt -fp 70 `pidof "jackd"`
as non root without using sudo
chrt -fp 70 `pidof "jackd"`
do you get an error?
Flo
--
Palimm Palimm!
http://tapas.affenbande.org
7:51 p.m.
On 10/24/07, Florian Schmidt <mista.tapas(a)gmx.net> wrote:
On Wednesday 24 October 2007, Chuckk Hubbard wrote:
Why no I don't! And it changes priority. I swore it didn't work before
when I tried it. I've just now added "session required
/lib/security/pam_limits.so" to /etc/pam.d/common-session, as others
suggested, maybe that did something?
So does that mean the -P flag can never set priority 70? I got it from your
site!
Thanks.
-Chuckk
--
http://www.badmuthahubbard.com
sudo chrt -fp 82 `pidof "IRQ-16"`
jackd --realtime -P 70 -dalsa -P -p256 -n2 -r44100 &
sudo chrt -fp 70 `pidof "jackd"`
chrt -p `pidof "IRQ-16"`
chrt -p `pidof "jackd"`
exit
if you run
sudo chrt -fp 70 `pidof "jackd"`
as non root without using sudo
chrt -fp 70 `pidof "jackd"`
do you get an error?
25 Oct
25 Oct
5:35 a.m.
On Wednesday 24 October 2007, Chuckk Hubbard wrote:
On 10/24/07, Florian Schmidt
<mista.tapas(a)gmx.net> wrote:
Well, if chrt works now without sudo, try running
jackd -R -P 70 -d alsa ...
again. It should work now, too..
Flo
--
Palimm Palimm!
http://tapas.affenbande.org
On Wednesday 24 October 2007, Chuckk Hubbard
wrote:
Why no I don't! And it changes priority. I swore it didn't work before
when I tried it. I've just now added "session required
/lib/security/pam_limits.so" to /etc/pam.d/common-session, as others
suggested, maybe that did something?
So does that mean the -P flag can never set priority 70? I got it from
your site! sudo chrt -fp 82 `pidof "IRQ-16"`
jackd --realtime -P 70 -dalsa -P -p256 -n2 -r44100 &
sudo chrt -fp 70 `pidof "jackd"`
chrt -p `pidof "IRQ-16"`
chrt -p `pidof "jackd"`
exit
if you run
sudo chrt -fp 70 `pidof "jackd"`
as non root without using sudo
chrt -fp 70 `pidof "jackd"`
do you get an error?
6:06 a.m.
On 10/25/07, Florian Schmidt <mista.tapas(a)gmx.net> wrote:
On Wednesday 24 October 2007, Chuckk Hubbard wrote:
Believe it or not, I thought of that. It doesn't work. I also tried with
Csound, no luck. chrt -fp 70 `pidof "jackd"` works, jackd -R -P 70 -dalsa
etc doesn't (it starts jackd with all the appropriate options except
realtime). Is it possible for realtime not to be compiled into jackd? I
have 0.103.0 from Debian testing.
-Chuckk
--
http://www.badmuthahubbard.com
On 10/24/07, Florian Schmidt
<mista.tapas(a)gmx.net> wrote:
Well, if chrt works now without sudo, try running
jackd -R -P 70 -d alsa ...
again. It should work now, too.. On Wednesday 24 October 2007, Chuckk Hubbard
wrote:
Why no I don't! And it changes priority. I swore it didn't work before
when I tried it. I've just now added "session required
/lib/security/pam_limits.so" to /etc/pam.d/common-session, as others
suggested, maybe that did something?
So does that mean the -P flag can never set priority 70? I got it from
your site! sudo chrt -fp 82 `pidof "IRQ-16"`
jackd --realtime -P 70 -dalsa -P -p256 -n2 -r44100 &
sudo chrt -fp 70 `pidof "jackd"`
chrt -p `pidof "IRQ-16"`
chrt -p `pidof "jackd"`
exit
if you run
sudo chrt -fp 70 `pidof "jackd"`
as non root without using sudo
chrt -fp 70 `pidof "jackd"`
do you get an error?
27 Oct
27 Oct
1:50 p.m.
On 10/25/07, Chuckk Hubbard <badmuthahubbard(a)gmail.com> wrote:
Well, if chrt works now without sudo, try running
I'm still wrestling with this. I've been through a bunch of PAM setup
stuff, and it just won't work. jackd and Csound both refuse to run with rt
priority as assigned, and yet I am able to chrt as normal user. Perhaps
jackd running as realtime is dependent on ALSA setup?
Any help is appreciated.
-Chuckk
--
http://www.badmuthahubbard.com
jackd -R -P 70 -d alsa ...
again. It should work now, too..
Believe it or not, I thought of that. It doesn't work. I also tried with
Csound, no luck. chrt -fp 70 `pidof "jackd"` works, jackd -R -P 70 -dalsa
etc doesn't (it starts jackd with all the appropriate options except
realtime). Is it possible for realtime not to be compiled into jackd? I
have 0.103.0 from Debian testing.
29 Oct
29 Oct
12:24 p.m.
On 10/25/07, Florian Schmidt <mista.tapas(a)gmx.net> wrote:
On Wednesday 24 October 2007, Chuckk Hubbard wrote:
Update: I just discovered that running jackd -R -P 70 -dalsa -P -p256 -n2
-r44100 as ROOT doesn't even set priority 70. jackd then runs as a root
process with priority 20, according to both chrt and top.
Apparently my system is not able to run anything higher than 20 priority;
does this mean my kernel is misconfigured, or might it be something else?
-Chuckk
--
http://www.badmuthahubbard.com
On 10/24/07, Florian Schmidt
<mista.tapas(a)gmx.net> wrote:
Well, if chrt works now without sudo, try running
jackd -R -P 70 -d alsa ...
again. It should work now, too.. if you run
sudo chrt -fp 70 `pidof "jackd"`
as non root without using sudo
chrt -fp 70 `pidof "jackd"`
do you get an error?
Why no I don't! And it changes priority. I swore it didn't work before
when I tried it. I've just now added "session required
/lib/security/pam_limits.so" to /etc/pam.d/common-session, as others
suggested, maybe that did something?
So does that mean the -P flag can never set priority 70? I got it from
your site! 
12:26 p.m.
On 10/29/07, Chuckk Hubbard <badmuthahubbard(a)gmail.com> wrote:
Update: I just discovered that running jackd -R -P 70
-dalsa -P -p256 -n2
-r44100 as ROOT doesn't even set priority 70. jackd then runs as a root
process with priority 20, according to both chrt and top.
Apparently my system is not able to run anything higher than 20 priority;
does this mean my kernel is misconfigured, or might it be something else?
jackd is a multithreaded process, you can't just look at the priority
of the main thread, you have to check all of them. It should have
some SCHED_FIFO threads and some SCHED_NORMAL threads.
Lee
1:21 p.m.
On 10/29/07, Lee Revell <rlrevell(a)joe-job.com> wrote:
On 10/29/07, Chuckk Hubbard <badmuthahubbard(a)gmail.com> wrote:
Interesting, I'll have to keep reading until I find out how to do that.
But is it normal, then, that chrt -p 70 `pidof "jackd"` would set rtprio 70
but jackd -R -P 70 etc. wouldn't?
Which is to say, if chrt can set the main thread priority, why not the -P
flag?
-Chuckk
--
http://www.badmuthahubbard.com
Update: I just discovered that running jackd -R
-P 70 -dalsa -P -p256
-n2
-r44100 as ROOT doesn't even set priority 70.
jackd then runs as a root
process with priority 20, according to both chrt and top.
Apparently my system is not able to run anything higher than 20
priority;
does this mean my kernel is misconfigured, or
might it be something
else?
jackd is a multithreaded process, you can't just look at the priority
of the main thread, you have to check all of them. It should have
some SCHED_FIFO threads and some SCHED_NORMAL threads.
5:46 p.m.
On 10/29/07, Chuckk Hubbard <badmuthahubbard(a)gmail.com> wrote:
On 10/29/07, Lee Revell <rlrevell(a)joe-job.com>
wrote:
That's normal. The main thread is not supposed to be SCHED_FIFO.
Lee
On 10/29/07, Chuckk Hubbard
<badmuthahubbard(a)gmail.com> wrote:
> Update: I just discovered that running jackd -R -P 70 -dalsa -P -p256
-n2
> -r44100 as ROOT doesn't even set
priority 70. jackd then runs as a root
> process with priority 20, according to both chrt and top.
> Apparently my system is not able to run anything higher than 20
priority;
> does this mean my kernel is misconfigured,
or might it be something
else?
jackd is a multithreaded process, you can't just look at the priority
of the main thread, you have to check all of them. It should have
some SCHED_FIFO threads and some SCHED_NORMAL threads.
Interesting, I'll have to keep reading until I find out how to do that.
But is it normal, then, that chrt -p 70 `pidof "jackd"` would set rtprio 70
but jackd -R -P 70 etc. wouldn't?
Which is to say, if chrt can set the main thread priority, why not the -P
flag?
3:30 p.m.
On Monday 29 October 2007, Chuckk Hubbard wrote:
On 10/25/07, Florian Schmidt
<mista.tapas(a)gmx.net> wrote:
install htop
run it
press f2 [setup]
-> Display Options
-> uncheck "Hide userland threads"
-> uncheck "Hide kernel threads"
Do you see all 4 jack threads now?
--
Palimm Palimm!
http://tapas.affenbande.org
On Wednesday 24 October 2007, Chuckk Hubbard
wrote:
Update: I just discovered that running jackd -R -P 70 -dalsa -P -p256 -n2
-r44100 as ROOT doesn't even set priority 70. jackd then runs as a root
process with priority 20, according to both chrt and top.
Apparently my system is not able to run anything higher than 20 priority;
does this mean my kernel is misconfigured, or might it be something else?
-Chuckk On 10/24/07, Florian Schmidt
<mista.tapas(a)gmx.net> wrote:
Well, if chrt works now without sudo, try running
jackd -R -P 70 -d alsa ...
again. It should work now, too.. if you run
sudo chrt -fp 70 `pidof "jackd"`
as non root without using sudo
chrt -fp 70 `pidof "jackd"`
do you get an error?
Why no I don't! And it changes priority. I swore it didn't work
before when I tried it. I've just now added "session required
/lib/security/pam_limits.so" to /etc/pam.d/common-session, as others
suggested, maybe that did something?
So does that mean the -P flag can never set priority 70? I got it from
your site!
6:54 p.m.
On 10/29/07, Florian Schmidt <mista.tapas(a)gmx.net> wrote:
On Monday 29 October 2007, Chuckk Hubbard wrote:
Woop, there it is. Thanks. I see 5 actually, one -71, one -81 (watchdog?),
and the rest 20. Running Csound with its --sched=N flag, I also see two
csound processes, one of which is -70 and the other 20, no matter what value
I put... time to take that up with the Csound list I guess.
Thanks guys.
-Chuckk
--
http://www.badmuthahubbard.com
On 10/25/07, Florian Schmidt
<mista.tapas(a)gmx.net> wrote:
-n2
Well, if chrt works now without sudo, try
running
jackd -R -P 70 -d alsa ...
again. It should work now, too..
Update: I just discovered that running jackd -R -P 70 -dalsa -P -p256 -r44100 as ROOT doesn't even set priority 70.
jackd then runs as a root
process with priority 20, according to both chrt and top.
Apparently my system is not able to run anything higher than 20
priority;
does this mean my kernel is misconfigured, or
might it be something
else?
-Chuckk
install htop
run it
press f2 [setup]
-> Display Options
-> uncheck "Hide userland threads"
-> uncheck "Hide kernel threads"
Do you see all 4 jack threads now? 
7:15 p.m.
On Mon, 2007-10-29 at 23:54 +0200, Chuckk Hubbard wrote:
On 10/29/07, Florian Schmidt
<mista.tapas(a)gmx.net> wrote:
On Monday 29 October 2007, Chuckk Hubbard wrote:
With JACK output?
From the Csound manual:
"DO NOT use "--sched" if you are using JACK for audio output. JACK
controls scheduling for the audio applications connected to it, and also
tries to run at the highest possible priority. If the "--sched" flag is
used, Csound and JACK will be competing rather than cooperating,
resulting in extremely poor performance."
--ll
On 10/25/07, Florian Schmidt
<mista.tapas(a)gmx.net> wrote:
-P -p256 -n2
Well, if chrt works now without sudo, try running
jackd -R -P 70 -d alsa ...
again. It should work now, too..
Update: I just discovered that running jackd -R -P 70 -dalsa -r44100 as ROOT doesn't even set priority 70.
jackd then
runs as a root
process with priority 20, according to both chrt
and top.
Apparently my system is not able to run anything higher than
20 priority;
does this mean my kernel is misconfigured, or
might it be
something else?
-Chuckk
install htop
run it
press f2 [setup]
-> Display Options
-> uncheck "Hide userland threads"
-> uncheck "Hide kernel threads"
Do you see all 4 jack threads now?
Woop, there it is. Thanks. I see 5 actually, one -71, one -81
(watchdog?), and the rest 20. Running Csound with its --sched=N flag,
I also see two csound processes, one of which is -70 and the other 20,
no matter what value I put... time to take that up with the Csound
list I guess.
7:23 p.m.
On 10/30/07, Lars Luthman <lars.luthman(a)gmail.com> wrote:
On Mon, 2007-10-29 at 23:54 +0200, Chuckk Hubbard wrote:
I combed that section carefully, but I missed that part. I'll request that
someone put it in the description of either -+rtaudio=jack or --sched...
Thanks so much!
-Chuckk
--
http://www.badmuthahubbard.com
On 10/29/07, Florian Schmidt
<mista.tapas(a)gmx.net> wrote:
On Monday 29 October 2007, Chuckk Hubbard wrote:
With JACK output?
From the Csound manual:
"DO NOT use "--sched" if you are using JACK for audio output. JACK
controls scheduling for the audio applications connected to it, and also
tries to run at the highest possible priority. If the "--sched" flag is
used, Csound and JACK will be competing rather than cooperating,
resulting in extremely poor performance." On 10/25/07, Florian Schmidt
<mista.tapas(a)gmx.net> wrote:
-P -p256 -n2
Well, if chrt works now without sudo, try
running
jackd -R -P 70 -d alsa ...
again. It should work now, too..
Update: I just discovered that running jackd -R -P 70 -dalsa -r44100 as ROOT doesn't even set priority 70.
jackd then
runs as a root
process with priority 20, according to both chrt
and top.
Apparently my system is not able to run anything higher than
20 priority;
does this mean my kernel is misconfigured, or
might it be
something else?
-Chuckk
install htop
run it
press f2 [setup]
-> Display Options
-> uncheck "Hide userland threads"
-> uncheck "Hide kernel threads"
Do you see all 4 jack threads now?
Woop, there it is. Thanks. I see 5 actually, one -71, one -81
(watchdog?), and the rest 20. Running Csound with its --sched=N flag,
I also see two csound processes, one of which is -70 and the other 20,
no matter what value I put... time to take that up with the Csound
list I guess.
30 Oct
30 Oct
10:04 a.m.
On 10/30/07, Lars Luthman <lars.luthman(a)gmail.com> wrote:
With JACK output?
From the Csound manual:
"DO NOT use "--sched" if you are using JACK for audio output. JACK
controls scheduling for the audio applications connected to it, and also
tries to run at the highest possible priority. If the "--sched" flag is
used, Csound and JACK will be competing rather than cooperating,
resulting in extremely poor performance."
Hold up.
From the exact same page of the Csound manual:
"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 on the same page where it says DO NOT use --sched with jack, it says to
use --sched=N with jack.
If you look in the Csound manual under the commandline flags section, you
will see that --sched and --sched=N are NOT the same flag.
Thanks though for drawing my attention to it.
-Chuckk
--
http://www.badmuthahubbard.com
6075
days inactive
6081
days old
linux-audio-user@lists.linuxaudio.org
18 comments
6 participants
participants (6)
-
Chuckk Hubbard -
Dragan Noveski -
Fernando Lopez-Lezcano -
Florian Schmidt -
Lars Luthman -
Lee Revell