Re: Server control plug-ins proposal

Stéphane Letz <letz@...> writes:

Hi,

There are two problems that i see with this implementation.

When dbus session bus daemon autoactivates jack controller it gets
started but jackdbus log file does not contain the log messages from
jack server. It contains this instead:

Thu Jun  4 10:32:15 2009: ------------------
Thu Jun  4 10:32:15 2009: Controller activated. Version 1.9.3 (3557M)
Thu Jun  4 10:32:15 2009: dbus : thread started...
Thu Jun  4 10:32:37 2009: dbus : thread exit...
Thu Jun  4 10:32:37 2009: Controller deactivated.

This is major drawback. I don't know yet why it happens.

The second problem is that autoactivation does not work. What I did:

 * autoactivate (reactivate in laditools) jack controller dbus
   object. laditools display that server is stopped (this is what should
   happen).
 * start jack client app that tries to autoactivate.

What happens:

In log file:
Thu Jun  4 10:34:05 2009: ------------------
Thu Jun  4 10:34:05 2009: Controller activated. Version 1.9.3 (3557M)
Thu Jun  4 10:34:05 2009: ERROR: Requested D-Bus service name already exists

In process list:
nedko     5741  0.0  0.1  15072  2540 ?        Ssl  10:32   0:00 /usr/bin/jackd
nedko     5829  0.4  0.4  50224  9680 ?        Ssl  10:44   0:00 /usr/bin/jackd -T -ndefault -p 128 -R -P 60 -T -d alsa -n 3 -r 48000 -p 512 -d hw:0,0

LADI tools report that JACK server is stopped when it was
(auto)started. They use the first jackd. JACK controller dbus object is
singleton. Thus the dbus error in the log file.

These problems aside, I think this is a better approach than using two
IPC layers between laditools and jack server. I still think that it can
be even simpler if client control API is launching the server in IPC
specific way (what i suggested instead).

Given that you wont accept the better (IMHO) solution I think the above
problems can fixed:

 1. plugin needs to configure the log callback of the jack server.
 2. jackd should refuse to start when jackdbus controller is already
    running.
 3. when dbus is enabled at configure stage, the resulting libjack
    must first try to start jack server through dbus.

I just saw another bug. If jack is configured with dbus only. you get no
jack server at all because jackd is not installed and jackdbus is
removed.

--
Nedko Arnaudov <GnuPG KeyID: DE1716B0>


_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org