Re: [Jack-Devel] ladish + jack autoconnect

Accidently, only replied to Paul, oops. re-posting to list.

> the proposal has some merits i think. i don't think its very useful
> for most use cases, but in some reasonably likely ones, some of these
> options would be very useful to have. it would integrate quite well
> with JACK Session, and enables that and ladish to do what they want
> without having to modify clients, which is a good thing. but ... to be

+1

> actually useful, i suspect that this option needs to be controllable
> in a running server, not just at startup.

This would be awesome If i am understanding, what you are saying
correctly....If so, I already have a use-case for this;

When i load up my template-type keyboard/module session, ie: some
synths/linuxsamper(4 piano) + some plugins... On startup, Jack is set
to ignore all self-connect requests -> this is because some clients
will directly connect to the hardware outputs, while i need them to
only connect to other clients. (ie: let the session manager handle
connections, not the app/clients).

However, often i may be watching videos, while practicing and/or
taking an online music lesson, learning a song, playing along with
something on youtube, etc...(or even just watching a video like a t.v
show, while playing) In this situation, i want the video's sound to
self-connect, because the alternative is to manually connect them for
*every* video that i watch. :\

currently, i do connect the jack client (video/flash) manually ~ as it
beats having to connect *everything else* manually. But i will add
that 'it is a thorn in my side' and not ideal.. ;) I think it would be
great to be able to switch the self-connect behavior while everything
is running, rather than just on startup. it would make life easier...
This is a great idea :)

cheerz

1325371453.16105_0.ltw:2,a <CAOcfFMyoBx+7PJogteuux+x7Sp0Eu65DJd=QVPNQxF9hotb_DQ at mail dot gmail dot com>