17 May
2009
17 May
'09
12:06 p.m.
On Sun, May 17, 2009 at 02:07:55PM +0100, Rui Nuno Capela wrote:
It shouldn't depend on jack being 1 or 2.
Ciao,
--
FA
Io lo dico sempre: l'Italia รจ troppo stretta e lunga.
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
running.
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 ;)