23 Mar
2009
23 Mar
'09
3:50 p.m.
Atte Andr? Jensen:
Hi
I often heard that it's considered bad when clients automatically auto
connect it's outputs to jack. I agree, mostly since:
1) This makes routing through other software before output difficult
2) The patchbay in qjackctl makes it easy to make auto connects anyways
But could anyone point me to some explanation from the devs (Paul Davis
for instance) of why this is considered bad?
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)
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).
I think this would have pleased everyone.
23 Mar
23 Mar
3:52 p.m.
New subject: why shouldn't clients autoconnect to jack
On Mon, Mar 23, 2009 at 2:50 PM, Kjetil S. Matheussen <
k.s.matheussen(a)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?
I think this would have pleased everyone.
my reading is somewhat opposite of this.
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.
3:58 p.m.
New subject: why shouldn't clients autoconnect to jack
On Mon, 23 Mar 2009, Paul Davis wrote:
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.
On Mon, Mar 23, 2009 at 2:50 PM, Kjetil S. Matheussen
<
k.s.matheussen(a)notam02.no> wrote:
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...
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?
I think this would have pleased everyone.
my reading is somewhat opposite of this.
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?
5:46 p.m.
New subject: why shouldn't clients autoconnect to jack
On Mon, 2009-03-23 at 19:58 +0100, Kjetil S. Matheussen wrote:
Port aliasing could introduce semantic ports, a feature that's
definitely missing.
Flo
--
Machines can do the work, so people have time to think.
public key 6C002249 x-hkp://wwwkeys.eu.pgp.net
On Mon, 23 Mar 2009, Paul Davis wrote:
That might be valid for your setup and most others, but in general this
is not true.
On Mon, Mar 23, 2009 at 2:50 PM, Kjetil S.
Matheussen <
k.s.matheussen(a)notam02.no> wrote:
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... 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? 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? 
6:33 p.m.
New subject: why shouldn't clients autoconnect to jack
On Monday 23 March 2009 14:58:38 Kjetil S. Matheussen wrote:
Without that, the other things I said would have been
incredibly stupid.
I don't think JACK should be complicated by defining autoconnect mechanisms in
there.
Applications should provide the option and configuration for it.
I think the proposals given for the app to ask upon first startup (either via
a GUI if the app has a graphical interface, or through command line interface
if not) to the user how you want to configure the behaviour is the clearest
way.
The configuration dialog can suggest the first hardware ports by default, if
that is the expected most common user case.
That way the user is aware that he can configure it, and can adapt the program
to her needs.
sincerely,
Marije
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?
5726
days inactive
5726
days old
linux-audio-user@lists.linuxaudio.org
4 comments
4 participants
participants (4)
-
Florian Faber -
Kjetil S. Matheussen -
nescivi -
Paul Davis