Re: [Jack-Devel] ladish + jack autoconnect -- was Re: alsa_in problems

On Sat, Dec 24, 2011 at 11:55:29PM +0100, Robin Gareus wrote:
 
> I'm still curious where this (ladish?) auto-connect comes from.
> https://aur.archlinux.org/packages.php?ID=51977
> mentions:
>   http://www.grame.fr/~letz/jack-1.9.7.tar.bz2
>   no-selfconnect.patch
>   use_jackdbus_settings.patch
> 
> but the patches are not linked. I use jack-1.9.7.tar.bz2 with DBus and
> there is no auto-connect/self-connect what[so]ever.
> 
> I assume it's actually
> http://repo.or.cz/w/jack2.git/shortlog/refs/heads/ladi
> that was causing the trouble and it has meanwhile been fixed.

Could be. But there is nothing in the original post that 
suggests that the poster is using ladish or anything similar.

The reason he gets this feedback is that his DAW automatically
enables input monitoring on a new track. 

Even if there were no autoconnect, he would sooner or later
connect his mic manually to the new track, and still have
the same unwanted feedback.

So the real cause of his problem is not the autoconnect. 
It is the simple fact that his DAW is configured for  a
separated studio and control room situation - in that 
case you _want_ input monitoring.

Ciao,   

-- 
FA

Vor uns liegt ein weites Tal, die Sonne scheint - ein Glitzerstrahl.

1324768391.12859_0.ltw:2,a <20111224231305.GD736 at linuxaudio dot org>