Forums
This may be a RTFM problem, but i can't seem to figured this out. Is there a way to prevent qjackctl from killing the jack process on 'quit'? I've setup a system such that jack is loaded at boot-time before any visual X11 stuff (audio server)... So having the jack thread stopped isn't desirable.
Re: qjackctl shutdown question...
if the jackd process is started by qjackctl then it dies with qjackctl.
byee
Re: qjackctl shutdown question...
Interestingly enough I am not starting jack with qjackctl. I'm loading it at boot time with 'jack_control start' It's almost the very last thing that happens during boot.. After that i'm loading 'pulseaudio --start' with some modules that hook into the jack server. The idea being, when you load the X11 environment, pulse and jack are ready to be manage by your awesome app (qjackctl)... But i can't for the life of me figure out why qjackctl thinks it's starting jack when i've triple checked that it is not or should not be loading jack. Not using 'qjackctl -s' nor did i check off start jack in the config panel.
thanks!
Re: qjackctl shutdown question...
hmm... there might be a couple of reasons then...
is this by any chance related to d-bus (ie. jackdbus) anyhow?
or, have you checked whether your pre/post-shutdown scripts aren't involved somehow?
seeya
Re: qjackctl shutdown question...
Hah, i forgot to mention I'm running jack2-dbus so yes, dbus related issues. And I don't have any pre/post scripts in qjackctl.
Re: qjackctl shutdown question...
so there you have it.
answer is no: qjackctl will tear down the jack service, but not jackdbus though, when you either press stop or you quit. that is also the case when jackdbus is not involved, iow, when classic jackd is in the picture.
so sorry, it all seems working as designed :)
cheers
Add new comment