Re: jack trouble

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Atte André Jensen wrote:

> Basically. This is all very good news, although I'm not quite there yet. 
> But I'm wondering what's difference between starting jackd from qjackctl 
> and doing `cat ~/.jackdrc`?

I looked at "man jackd" and saw -Z (no zombies). Adding this to my 
commandline like this:

/usr/bin/jackd -Z -R -P80 -m -dalsa -dhw:1 -r44100 -p512 -n3 -s -S &

makes things a little different. Now it seems that the

subgraph starting at ChucK timed out (subgraph_wait_fd=9, status = 0, 
state = Running, pollret = 0 revents = 0x0)

message *sometimes* doesn't kill chuck. However sometimes (most of the 
time) chuck still dies, but now with an extra line after the 
"subgraph..." one:

bad status (1) for client ChucK handling event (type = 5)

A working work-around seems to be to start/killall *qjackctl* and not 
*jackd* from my chuck-start-song-script. Only problem is that focus is 
then not at mu terminal window, but I guess some googleing will turn up 
some linux magic to fix this...

-- 
Atte

http://atte.dk    http://modlys.dk
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user


[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux