Re: [Jack-Devel] ladish + jack autoconnect

jordan <[hidden]> writes:

> 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 :)

ladish restores connection to external clients. you have to connect them
only once, not on each restart. However if the client changes its jack
client name (for example by adding pid as suffix), ladish treats it as
different client and will not reconnect. There is alrady known
workaround for such apps that create [somewhat] random names. If you add
a shell as an app in ladish and you start apps from there, ladish will
know that this is the same client and will reconnect it, despite of the
real jack client name. As you probably already know, ladish uses app
name in this case.

-- 
Nedko Arnaudov <GnuPG KeyID: 5D1B58ED>

1325445553.23943_0.ltw:2,a <87d3b3cjuq.fsf at arnaudov dot name>