[pulseaudio-discuss] [Fwd: Re: [Jack-Devel] pa vs jack2]
ngoonee at gmail.com
Thu Oct 29 07:44:47 PDT 2009
Please find below some details from Jack2 dev nedko on the
dbus-specifics, with relation to a recent topic on starting
module-jack-sink/source on surrendering control of the sound card to
Patrick Shirkey <pshirkey at boosthardware.com> writes:
> I just spotted this on the pa list.
>> I'm sure the Jack folk know better than I on the D-Bus name,
>> jack_control status seems to work fine to tell me when Jack
is ready for
>> use, and it communicates via dbus as well...
> Last time I checked they had a name they were picking before
> actually spawning off the jack audio daemon. As long as things
> that way round this is not useful for PA's needs.
> Can anyone confirm or deny? Seems to be a bit of a blocker to
> dbus integration if PA cannot work with the existing jack2
> registering a name with dbus.
"jack_control status" does not check whether dbus name is owned.
checks whether JACK server is started. There are also a D-Bus
that are emited when JACK server starts/stops. D-Bus name is
when controller is activated and that has nothing to do with
JACK server is started. The controller object is the one who
server. It is a persistent endpoint to control and monitor JACK
So, if pulseaudio needs polling, it can use the
If it needs notification mechanism, it should subscribe for the
More information about the pulseaudio-discuss