[LAD] [Jackit-devel] [PATCH] jack dbus and logs improvement

Fons Adriaensen fons at kokkinizita.net
Tue Dec 18 21:06:31 UTC 2007

On Tue, Dec 18, 2007 at 06:24:54PM +0200, Nedko Arnaudov wrote:

> Some terms explained:
>  * jack server is the what is seen by jack clients (audio/midi, through
>    libjack).
>  * jack controller is a dbus object that can start jack server
>  * jackd is the name of the executable starting jack server and parsing
>    commandline arguments to configure both engine and driver
>  * jackdbus is the name of the executable providing jack controller dbus
>    object. it can start jack server, amoung other things it can do.

If this isn't confusing then what is ?

I've been reading this thread, including the posts following
this one that I'm replying to. And since one poster wanted to
know what other ppl are thinking, let me say this:


We have a nice app called jackd even if it doesn't really
deserve the final 'd'. It works quite well. Please keep it
that way. 

I'm all in favour of a control interface to jackd that is
separated from the audio client interface.

But so far I've failed to understand which useful features,
if any, this dbus stuff would add to jackd. If it's 'desktop'
related, please solve it at that level, but don't destroy a
well working application.


Laboratorio di Acustica ed Elettroacustica
Parma, Italia

Lascia la spina, cogli la rosa.

More information about the Linux-audio-dev mailing list