On Thu, January 17, 2013 3:47 pm, Federico Bruni wrote:
Ja, I noticed that too. I was looking for some info on netjack.
There are some interesting things with PA (Pulseaudio). If PA starts while
a device is busy with another application (like jackd) that device will
not be available to pulse even after Jackd is stopped and the device is
available. pulseaudio -k will make it rescan the devices... well actually
it kills PA and when PA restarts (normally runs respawn) it rescans.
It would seem you are using jackd and not jackdbus then?
module-jackdbus-detect would normally start module-jack-sink/source when
it detects jack is present and stop them when jackdbus stops. (I am not
suggesting you run that way unless you want to run dbus) qjackctl can be
set to run dbus or not, I would check to see if it is checked or not. For
how you have things set up it should not be checked.
If you do want to use module-jackdbus-detect... I would wait for wait for
the bug fix :) (though there is a work around)
Linux-audio-user mailing list