[LAD] [Jackit-devel] [PATCH] jack dbus and logs improvement
nedko at arnaudov.name
Tue Dec 18 15:52:34 UTC 2007
Lars Luthman <lars.luthman at gmail.com> writes:
> On Tue, 2007-12-18 at 16:56 +0200, Nedko Arnaudov wrote:
>> Krzysztof Foltman <wdev at foltman.com> writes:
>> > Nedko Arnaudov wrote:
>> >> I'd like to hear what other ppl think about this. It works for me both
>> >> ways. If most ppl like to have two modes merged in one executable just
>> >> to see jackd is running not jackdbus, so be it, I'll merge those changes
>> >> into dbus patch.
>> > I'm definitely in favour of the merge. The previous solution (old jackd,
>> > new jackdbus) was definitely confusing to me. While I understand the
>> > distinction now, it wasn't obvious at first.
>> So having jackd behave in orthagonal way is not confusing? Like, jackd
>> process is running, why my apps cannot connect?!?!?
> libjack needs to start the server automatically just like it does now.
> How does that work with the D-Bus control thing?
If libjack is compiled with dbus support it will first try to start jack
server through dbus. if it fails, it will fall back to the old
behaviour (reading ~/.jackdrc) and try to start jackd through it.
Starting it through dbus means activating the dbus object if not already
activated and strting the server. Calling any method of the dbus object,
"server start" in this case, autoactivates the object.
Nedko Arnaudov <GnuPG KeyID: DE1716B0>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 188 bytes
Desc: not available
More information about the Linux-audio-dev