Subject: Re: [ecasound] what is wrong with this chain setup?
From: Kai Vehmanen (email@example.com)
Date: Sun Jan 30 2000 - 12:03:53 EET
On Sat, 29 Jan 2000, Jeremy Hall wrote:
> Running today's CVS build, this is the result. chain 1 gets all the
> traffic, chain 2 doesn't see any signal.
> [root@pongo praise]# cat cd016-003.fil
> -b:128 -sr:44100 -n:cd016-003 -m:simple
> -a:1,2 -f:s16_le,2,44100 -i cd016-003.mp3
-m:simple is the reason here. Simple-mixmode skips all mixing routines
and processes only the first chain. Hmm, I guess I could add
a safety check that warns about the above situation.
> -a:1 -f:s16_le,2,44100 -o /dev/dsp1
> -a:2 -f:s16_le,2,44100 -o /tmp/out.raw
> -a:1 -eca:0.07,0.01,0.25,1.00 -ev -ea:57900.00
> -a:2 -eca:0.07,0.01,0.25,1.00 -ev -ea:57900.00
> I really don't like having to double-specify all the options for separate
> chains like this. It seems to me this is extra work for ecasound to do
> the work twice. Is this the case?
Yes, it has to do more work. Internal chainloops migh help here.
-a:1 -eca:x,x,x,x -ea:xx -o cloop,1
-a:2 -i cloop,1 -o /dev/dsp
-a:3 -i cloop,1 -o out.wav
-- Kai Vehmanen <firstname.lastname@example.org> -------- CS, University of Turku, Finland . http://www.wakkanet.fi/ecasound/ - linux multitrack audio processing . http://www.wakkanet.fi/sculpscape/ - ambient-idm-rock-... mp3/ra/wav
This archive was generated by hypermail 2a24 : Sun Jan 30 2000 - 12:37:43 EET