On 13 May 2004, Jack O'Quin wrote: > My feeling is that we should leave this as an obscure feature for > expert users to experiment with at this point. Eventually, full > support will evolve, but that will take a while.
Agreed. Its a really cool and nice feature for the experienced user, it will only work reliably for beginners when jack starts realiably for everyone, which it doesn't yet. With a non working jack the automatic startup would only cause more confusion. Guenter > > > Of course there are ways that the Debian package could be patched > > to enable this, but acting differently than upstream is always a bad > > thing. > > I think that would really confuse a lot of people. > > > What is the design behind the .jackdrc format ? > > Or is it rather an ad-hoc solution ? > > Very ad-hoc. Just a command line. > > > I think beside being useful for automatic server startup, it would > > be nice to have jackdrc as a general configuration file, that also > > works for the jackd command-line directly. > > I argued for that when this feature was first introduced, but didn't > get much support at the time. I like the basic concept of starting > the sever when needed, but am not thrilled with this design. But, I > guess I can live with it. > > > It seems the settings are just stored as command line, which probably > > does not scale very well, and it is difficult to parse, adapt and extend. > > That's right. At least it's well-defined. ;-) > > > Seems that qjackctl uses a different format and file too, then later > > there will be LASH ... > > Right. Qjackctl will write it's command line in .jackdrc, unless you > tell it not to. Maybe the UI can be handled adequately at that level. > -- > joq >
