Fons Adriaensen wrote: > On Sun, May 17, 2009 at 05:19:21PM +0100, Rui Nuno Capela wrote: > >> the original issue on debate, as brought by Fons, was due to a probable >> mishap caused by the new d-bus stuff in jack2 (aka jackdmp): apparently, >> jackdbus is auto-starting the jackd service without regard to what's in >> ~/.jackdrc. it doesn't matter whomever wrote that file in the first >> place, either ardour, qjackctl or even jackd itself. jackdbus is just >> making a fool out of it :) > > That would be a minor sin compared to what actually > happens. Even if the autostarted jack is terminated > as soon as the app that started it terminates, it > comes back as soon as qjackctl is started. It is > impossible then impossible to start the right jackd > from qjackctl. > can you explain a bit what is supposed to be "the right jackd"? afaict, qjackctl starts jackd with the exact argument parameters as given in its setup dialog, no more, no less, no guessing. you can check that on the messages window, the exact jackd command line that qjackctl invokes. if that happen not to be "the right jackd" then there's something going hideously wrong from inside jackd code path, as it probably is ignoring or overriding its own command line arguments. seeya -- rncbc aka Rui Nuno Capela rncbc@xxxxxxxxx _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
