[PlanetCCRMA] qjackctl/jackd acting differently?
bernie arai
bernie at vcn.bc.ca
Mon Sep 19 16:18:02 PDT 2005
On Sun, 2005-09-18 at 17:30, Fernando Lopez-Lezcano wrote:
> On Fri, 2005-09-16 at 10:45 -0700, bernie at vcn.bc.ca wrote:
[snip]
> > when starting jack from qjackctl, i get:
> >
> > 10:28:46.977 /usr/bin/jackd -R -dalsa -dhw:0 -r48000 -p256 -n3 -S
> > 10:28:46.985 JACK was started with PID=5827 (0x16c3).
> > cannot write to jackstart sync pipe 4 (Bad file descriptor)
> > jackd: wait for startup process exit failed
> > jackd 0.99.36
> > Copyright 2001-2003 Paul Davis and others.
> >
> > (etc. etc.)
> >
> > it starts after that but no "RT" light in the qjackctl window.
>
> Hmmm, with the newer kernels you no longer need to use "jackstart" to
> start jack. Try replacing the command in qjackctl with just "jackd"
> instead.
>
> -- Fernando
>
thanks for answering. funny, i did use the "jackd" option in qjackctl,
and in the command-line call, (/usr/bin/jackd -R -dalsa -dhw:0 -r48000
-p1024 -S) but that "cannot write to jackstart" still only shows up when
using qjackctl (not CLI). i realize now too that in the "status" window
of qjackctl, it does say realtime mode: yes, but the "RT" light in the
main window is dark. i still get thousands of xruns trying to do
anything.
bernie
More information about the PlanetCCRMA
mailing list