[LAD] [Jack-Devel] more jack/qjackctl madness : some comments

Fons Adriaensen fons at kokkinizita.net
Tue May 19 07:28:17 UTC 2009

On Tue, May 19, 2009 at 10:03:28AM +0300, Nedko Arnaudov wrote:

> Fons Adriaensen <fons at kokkinizita.net> writes:
> > Well, the current implementation *does* intercept C API
> > calls in order to divert them to dbus, it's not just an
> > addition to the standard jackd. I never mentioned babies
> > being eaten.
> As long as interface is same at C API level everything is fine. dbus
> cant and does not intercept any C API calls. The implementation of the
> jack_client_open(), only when compiled in dbus model, only when wants to
> start jack server, starts the jack server by *CALLING* libdbus
> function. That C level libdbus API call is then implemented by using the
> dbus IPC mechanism (sockets) and then gets into jackdbus process that
> executes the call. Nobody is intercepting jack.h API C level calls.

Nedko, you continue to contradict yourself.

What you write above confirms that the jack_client_open()
call is intercepted and its action modified. 



Io lo dico sempre: l'Italia è troppo stretta e lunga.

More information about the Linux-audio-dev mailing list