[LAD] [Jack-Devel] more jack/qjackctl madness

Fons Adriaensen fons at kokkinizita.net
Sun May 17 13:57:24 UTC 2009

On Sun, May 17, 2009 at 02:07:55PM +0100, Rui Nuno Capela wrote:

> unfortunately, Qt4's class which is being used for wrapping the jackd
> process (QProcess) does kill it on its destructor. afaict, this behavior
> wasn't present in Qt3 and that's why there's no option to keep jackd
> running upon quitting qjackctl anymore.

First, you don't need Qt classes to start a process,
so that's a bit weak. Second, I'd be surprise if
Qt would not allow you to keep a process it created

> > 2. Qjackctl-0.3.4 seems to have a bug handling the port
> > creation and destruction callbacks, it continues to show
> > ports that have been deleted and does not show some new
> > ones. This happens when the delete/create calls are close
> > together. Jack_evmon shows the right events in the right
> > order, so it must be qjackctl getting it wrong.
> i suppose i'll have to fix this soon. by properly handling port
> unregistration callbacks, which will be a novelty after 5+ years of
> doing just fine without on jack1 at least ;)

It shouldn't depend on jack being 1 or 2.



Io lo dico sempre: l'Italia è troppo stretta e lunga.

More information about the Linux-audio-dev mailing list