[LAU] why shouldn't clients autoconnect to jack
faber at faberman.de
Mon Mar 23 16:37:17 EDT 2009
On Mon, 2009-03-23 at 19:58 +0100, Kjetil S. Matheussen wrote:
> On Mon, 23 Mar 2009, Paul Davis wrote:
> > On Mon, Mar 23, 2009 at 2:50 PM, Kjetil S. Matheussen <
> > k.s.matheussen at notam02.no> wrote:
> >> This is a design fault in jack. Jack should
> >> by default always autoconnect new ports to physical in/outs
> >> when they are created. (first created port is connected
> >> to the first physical port, and so on)
> > why the first?
> What do you mean? Would you rather connect to the last physical
> port instead? I have 10 physical output ports in jack, but
> only 2 of them are connected to loudspeakers...
That might be valid for your setup and most others, but in general this
is not true.
> > i do agree that it would be good to define some "system aliases" so that it
> > was possible to reliably and controllably discover *which* physical ports to
> > connect to if autoconnect is going to be used.
> That sounds too complicated. Why not just add a command line option for
> jackd for selecting which client to autoconnect to?
Port aliasing could introduce semantic ports, a feature that's
Machines can do the work, so people have time to think.
public key 6C002249 x-hkp://wwwkeys.eu.pgp.net
More information about the Linux-audio-user