Re: [LAU] disabling jack plugin autoconnect or autoconnect in itself

From: <fons@email-addr-hidden>
Date: Wed Aug 04 2010 - 00:17:18 EEST

On Tue, Aug 03, 2010 at 11:57:50PM +0300, Jari Suominen wrote:

> Well here is the asoundrc I'm using:
>
> pcm.!default {
> type plug
> slave.channels 5
> slave { pcm "jack" channels 5}
> }
>
> pcm.jack {
> type jack
> playback_ports {
> 0 system:playback_1
> 1 system:playback_2
> 2 system:playback_2
> 3 system:playback_2
> 4 system:playback_2
> }
> capture_ports {
> 0 alsa_pcm:capture_1
> 1 alsa_pcm:capture_2
> }
> }
>
> ctl.mixer0 {
> type hw
> card 0
> }

OK, now I see your problem - I missed the 'alsa' in your description
of an app connecting to Jack, and was assuming a Jack app making
unwanted connections.

AFAICS, the syntax of the ALSA jack plugin specifies the ports to
connect to, and not the app's own ports which remain unknown. In
that case I don't see any solution. It's just bad design in the
sense that it missed a chance to be more general and configurable.

> >You can always watch connections using the callbacks and undo them.
> >But in many cases you'd be too late. The real solution is to allow
> >apps to 'lock' their ports, but this was removed from Jack some time
> >ago.
>
> Is there any ready made app to do this?

Not that I know.

Ciao,

-- 
FA
There are three of them, and Alleline.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@email-addr-hidden
http://lists.linuxaudio.org/listinfo/linux-audio-user
Received on Wed Aug 4 04:15:01 2010

This archive was generated by hypermail 2.1.8 : Wed Aug 04 2010 - 04:15:01 EEST