Subject: Re: [ecasound] c-bypass, how to recover from this
From: Jeremy Hall (firstname.lastname@example.org )
Date: Mon Nov 22 1999 - 04:25:41 EET
well I started ecasound, applied a compresser to a chain, then had to
apply an amplifier for over 4000 percent, then bypassed it. no matter how
many times I c-bypass, it will not unbypass. if I add an effect, it will
of course work.
I also cannot name the chain, whatever it starts with is what I get, and
if I try to create a new chain, I get a seg fault. (I think I reported
that already, not sure)
I plan to attempt recording multiple chains at once to see if things are
better in 1.6 vs 1.5.
I have noticed a difference in the combination of:
This should result in very little leakage, which on 1.5 it results on a
small leakage. On 1.6, however, the leakage is much more pronounced.
not sure which effect is at fault.
Kai Vehmanen said:
> On Sun, 21 Nov 1999, Kai Vehmanen wrote:
> >> I thought so, but it won't unbypass, n o matter how many times you
> > flags are 'selected', 'bypassed' and 'muted'). If chain isn't
> > selected, c-bypass won't work. But I'll test this more later today
> Another thing: if there are no chain operators (=effects), chain is
> always bypassed.
> Kai Vehmanen <email@example.com> -------- CS, University of Turku, Finland
> . http://www.wakkanet.fi/ecasound/ - linux audio processing
> . http://www.wakkanet.fi/sculpscape/ - ambient-idm-rock-... mp3/ra/wav
This archive was generated by hypermail 2a24 : Mon Nov 22 1999 - 04:27:20 EET