[linux-audio-dev] JACK error 4294967295

[Florian Schmidt]

On Wed, 14 Sep 2005 07:55:16 -0600
Hans Fugal <hans at fugal.net> wrote:

> > there's no priority 0 for SCHED_FIFO threads AFAIK, thus, as jackd runs
> > at the prio specified via the comandline, the watchdog at prio +10 and
> > the clients at prio -1, you effectively get a prio of 0 for the clients
> > when starting jackd with -P 1. Which doesn't work. So, a checking
> > whether the argument to -P is >= 2 should be enough. Plus the
> > documentation might need some updating to document the behaviour. I'll
> > send in a patch for the Documentation in a little while.
> 
> Ok, I understand that. So I take it if you set qjackctl priority to 0,
> it will not specify it and therefore use the JACK default which is >=2?
> I tried setting -P to 2 in qjackctl, and it works fine.

I suppose jackd should exit with an error when the prio is undefined. What 

BTW: if you run a RP system you usually want the jack threads to be
higher prio than all irq handlers other than the soundcard.

--- jackd.1.in.orig	2005-09-14 15:52:00.000000000 +0200
+++ jackd.1.in	2005-09-14 16:00:58.000000000 +0200
@@ -74,7 +74,7 @@
 .TP
 \fB\-P, \-\-realtime\-priority \fIint\fR
 When running \fB\-\-realtime\fR, set the scheduler priority to
-\fIint\fR.
+\fIint\fR. The valid range of values for this switch is between 2 and 89 (This is due to the fact that jackd runs its main thread, the watchdog thread and the clients threads at different priorities). The default value is 10.
 .TP
 \fB\-\-silent\fR
 Silence any output during operation.


-- 
Palimm Palimm!
http://tapas.affenbande.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jackd.1.in.patch
Type: application/octet-stream
Size: 536 bytes
Desc: not available
URL: <http://lists.linuxaudio.org/pipermail/linux-audio-dev/attachments/20050914/d7a23b2a/attachment.obj>