Re: [ecasound] Propagation of signal width with jack inputs

From: Joel Roth <joelz@email-addr-hidden>
Date: Tue Dec 14 2010 - 06:51:16 EET

On Mon, Dec 13, 2010 at 11:04:57PM +0200, Kai Vehmanen wrote:
> Hi,
> On Mon, 13 Dec 2010, Kai Vehmanen wrote:
> >> Also Input (2) shows a stereo signal, despite the chain
> >> setup input line specifying mono. Is that due to the -chcopy
> >> operator?
> >
> > I think that's related to something fishy between requesting a certain
> > channel count for 'jack_multi' objects, and how many destinations you pass
> > to 'jack_multi'. Basicly ecasound could count the parameters from
> > 'jack_multi,a,b,c' params and lock the channel count of the object based
> > on that (i.e. 'a,b,c' -> fixed to 3 channels).
> ok, this is now fixed in git master as well. So if you do:
> ecasound -i null -f:32,1,48000 -o jack_multi,foo:in_1,foo:in_2
> If with 2.7.2, jack_multi would end up mono (as requested by the user),
> and foo:in_2 connection would not be made.
> With current git, jack_multi object will be listed as stereo (so the
> parameter list passed to jack_multi overrides the channel counter
> request), and connection to 'foo:in_2' is made.
> I think this is the right thing to do.
> Thanks for the bug report!


Part of my problem has come from misunderstanding the -f
operator. Even tho the docs say it affects *all* subsequent
audio objects, from viewing the examples, I have tended to
mistakenly assume some sort of scoping.

Good to finally get this straight. :-)


Joel Roth
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
Ecasound-list mailing list
Received on Tue Dec 14 08:15:03 2010

This archive was generated by hypermail 2.1.8 : Tue Dec 14 2010 - 08:15:03 EET