On Mon, 23 Mar 2009, Paul Davis wrote: > On Mon, Mar 23, 2009 at 2:50 PM, Kjetil S. Matheussen < > k.s.matheussen@xxxxxxxxxx> 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... > >> >> I think this would have pleased everyone. > > > my reading is somewhat opposite of this. > Well, I said this too: " In addition, a jackd command line option to turn autoconnect off is required for those who (for good reasons) don't want that behaviour, or those who want to autonnect to a different client than the client handling the physical in/outs. And there should also be an option which turns autoconnect off for specific ports (i.e. an extra argument for jack_create_port). " Without that, the other things I said would have been incredibly stupid. > 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? _______________________________________________ Linux-audio-user mailing list Linux-audio-user@xxxxxxxxxxxxxxxxxxxx http://lists.linuxaudio.org/mailman/listinfo/linux-audio-user
