[LAD] New proposal for the jackd/jackdbus mess : adding "config" API
warjamy at yahoo.com
Wed May 20 12:45:59 UTC 2009
the existence of ~/.jackdrc is fine and using it in the future for legacy reasons is also a good thing. Its format, on the other hand, is questionable. I don't find it a good practice to call a server configuration file something that is more some sort of shell script, because the current ~/.jackdrc is nothing but a shell script. However, I am no jack dev, so you can dismiss my opinion if you like.
--- On Wed, 5/20/09, Stéphane Letz <letz at grame.fr> wrote:
> From: Stéphane Letz <letz at grame.fr>
> Subject: [LAD] New proposal for the jackd/jackdbus mess : adding "config" API
> To: "Jack devel" <jack-devel at lists.jackaudio.org>, "Linux Audio Developers" <linux-audio-dev at lists.linuxaudio.org>
> Date: Wednesday, May 20, 2009, 8:30 AM
> Hi all,
> Here is an updated version that add a new (to be defined)
> "config" API in libjack.so. The idea is to provide a way to
> *share* multiple server configurations in a unique place for
> all control application. The important point are:
> - we are not allowed to break legacy use of ~/.jackdrc
> - we absolutely want to maintain server auto-start from
> So the overall suggestion is to *maintain* this
> ~/.jackdrc with it's current format and to define a
> new config API that will probably use another file (or set
> of files...).
> - legacy control application (Qjackcl for instance) can
> still use their multiple server configurations, they will
> not see and use this new share and centralized state, but I
> don't think we can do better.
> - new control front-end (jackdbus, jackOSC) would have to
> use this new config API.
> -----Inline Attachment Follows-----
> Linux-audio-dev mailing list
> Linux-audio-dev at lists.linuxaudio.org
More information about the Linux-audio-dev