[Bug 773343] ext/jack uses JackNoStartServer

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=773343

--- Comment #5 from Sodhi, Cedric <manday at openmail.cc> ---
I'm not sure dbus is an appropriate substitute for the jack client library
autostart mechanism here. dbus autostart services are "available on request"
because they *are* dbus mediated services and the starting can be performed
"transparently" to the requesting client. This is not the case for Jack, as far
as I can see.

As for the policy, if I understand correctly what you mean: I think it can be
expected that if the pipeline contains a Ysink (for audio or video alike), then
it will be correct to assume that the associated "backend" Y (if any)
necessarily has to run. Very much because the case where the sink is backed by
a daemon which can started or not is just a special case. If there is a sink
for Y in the pipeline (like alsa, jack or X video), then it is to be assumed
that Y is in a working state (i.e.: if there is a daemon, it is running). If,
for some reason or another, various sinks cannot coexist, it is the
responsiblity of the user not to create them in the first place.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.