Hi devs,
I've started to write a gui to starts/stops jack and deals with its
configuration but I stopped when the first discussion about
dbus started.
I'd like to add my (2 cents ?) "jack external client developer"
comments/opipion(/ideas ?):
- If jackd loads *every* installed plugins on startup, dbus plugin would
be available even if jackd is started by Ardour/QJackCtl... And if you
don't want it you don't install it and thats all. Using a Linux
distribution, jack_control would depend of a jack-plugin-dbus package
and it would be invisible for users.
Such a system solves Nedko Arnaudov points 2. and 3. no ?
*But* starting jackd through DBus isn't possible anymore...
- Stéphane Letz proposed, but it had not been discuss so much, a libjack
build-in multi-configs manager, to share configuration with every
control apps. I think it can solve few issues.
Imagine we've got two files : one containing the current/default
config like the normal ~/jackdrc and an other one with is a databases of
user configurations (xml ?).
A control app will just take one config from the database and write
it to ~/jackdrc and then ask jackd to start on a
common/shared-by-every-client way witch use ~/jackdrc. It could be a
fork+exec(jackd auto) for example. No need to use DBus (or whatever) for
starting up jackd.
That's just my vision of the problem...
Martin Blanchard
_______________________________________________
Jack-Devel mailing list
Jack-Devel@...
http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
