Subject: Re: [ecasound] -t: at 48000
From: Kai Vehmanen (k_AT_eca.cx)
Date: Thu May 22 2003 - 00:25:40 EEST
On Mon, 19 May 2003, Jeremy Hall wrote:
>> The samplerate shouldn't have any effect to how -t:x works, so either it's
>> a bug or ...
> well I've seen something like this in the past. How can we procede?
That's a good question. Without a way to reproduce the problem there's not
much to do. :(
> also the loop thingie seems a bit wierd too:
> ecasound -a:1 -f:f32_le,1,48000 -i Audio_3-1.wav -a:2 -f:f32_le,1,48000 -i
> Audio_4-1.wav -a:1,2 -f:f32_le,2,48000 -o loop,1 -a:3 -f:f32_le,2,48000 -i
> loop,1 -o jack_alsa,out -a:4 -f:f32_le,2,48000 -i loop,1 -f:s16_le,2,48000
> -o file.raw -a:2 -erc:1,2 -epp:100
> it says that 2 is an invalid chain.
You are attaching "loop,1" two times, which results in a setup with
multiple "loop,1" inputs instread of one connected to two chains. So
the fixed version would be:
-a:1 -f:f32_le,1,48000 -i foo.wav
-a:2 -f:f32_le,1,48000 -i foo2.wav
-a:1,2 -f:f32_le,2,48000 -o loop,1
-a:3,4 -f:f32_le,2,48000 -i loop,1
-a:3 -o jack_alsa,out
-a:4 -f:s16_le,2,48000 -o bar.wav
-a:2 -erc:1,2 -epp:100
... I guess I really should take another look at Janne's chainsetup
auto-repair patch. :)
-- http://www.eca.cx Audio software for Linux!
This archive was generated by hypermail 2b28 : Thu May 22 2003 - 00:26:58 EEST