On Wed, Dec 19, 2007 at 11:55:55AM +0200, Nedko Arnaudov wrote:
Fons Adriaensen <fons(a)kokkinizita.net> writes:
The useful feature is one you mentioned, to separate control
interface. It also adds the logfile thing. Also it adds settings
persistence on jack side, so you dont need to have cryptic ~/.jackdrc
file, edited either by hand or by control app that needs to know what
jackd options are (moving target, also depends on drivers used).
Well, I don't think there's anything cryptic about ~/.jackdrc ...
It's pretty straightforward after just a minute of consideration.
Also, a file with command line options in it is about the simplest
form of 'persistence' you can have - anything else has to be more
complicated, or maybe the laws of logic have changed.
Can you explain what you mean by solving things at
desktop level?
By 'desktop level' I mean that level of a system that tries to be
friendly to users who don't know what they are doing, by hiding
reality and by trying to guess what they want and getting it wrong
most of the time :-) The typical Windoze / KDE / Gnome thing.
If this exercise of making jackd use dbus goes in that direction,
I'll resist :-)
Ciao,
--
FA
Laboratorio di Acustica ed Elettroacustica
Parma, Italia
Lascia la spina, cogli la rosa.