On Wed, 2007-12-19 at 23:55 +0100, Fons Adriaensen wrote:
> On Wed, Dec 19, 2007 at 11:55:55AM +0200, Nedko Arnaudov wrote:
>
> > Fons Adriaensen <fons@email-addr-hidden> 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.
Straightforward via being a toy. You can't express anything that isn't
a command line option in it, and you can only set up a single jack
configuration. A single line with a command in it isn't a configuration
file, it's a shell script with the hashbang missing ;)
Jack needs a /real/ configuration file. One good example of something
to go there is port aliases, and setting (or un-setting) the default
auto-connect ports (voila, the old auto connect problem solved).
-DR-
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Received on Fri Dec 21 20:15:10 2007
This archive was generated by hypermail 2.1.8 : Fri Dec 21 2007 - 20:15:10 EET