Re: [ecasound] a lot of trouble these days

From: Kai Vehmanen <kvehmanen@email-addr-hidden>
Date: Mon Jun 30 2008 - 01:47:59 EEST


On Wed, 4 Jun 2008, Julien Claassen wrote:

> I'm sorry this is just a list of what I experienced with my last ecasound
> version (git from 20.05.2008).
> 1. Still jack_auto doesn't care about the client parameter handed. It just
> connects to the first two ports of my soundcard regardless.

yes, this indeed was a bug (introduced by yours truly in March this year,
so not in Thanks a lot Julien for finding this out!

> 2. Effect troubles. Consider the following commandlne:
> ecasound -c -a:1 -i t1.wav -ea:60 -a:2 -i 2.ewf -ea:70 -a:3 -i 3.ewf -ea:40
> -a:4 -i 4.ewf -ea:64 ... -a:8 -i 8.ewf -ea:57 -z:mixmocd,sum -a:all -o out.wav
> I can say for sure, that with more then six chains, it ignore the ea-option
> on one of them. with eight chains it ignore chain 7s ea with less some other

This one is still open -- seems very odd to me, but stranger things have
happened. ;)

> 3. Not sure if this is a problem: I handed ecasound a few 24bit wav-files,
> but the output was 16bit. I passed -f:24,2,48000 to all chains and still it
> wouldn't work. I deleted the ouput-file I was trying to create and used the
> same commandline and voila. Is this behaviour intended?

Yes, this is intended. Passing '-f' doesn't have any impact when reading,
and updating an existing, .wav file. Ecasound always uses the params in
the file header. If you really want to override the header info, you can
for instance interpret the file as raw PCM ("-f:24,2,48000 -i
typeselect,.raw,foo.wav"). For output files, you can also pass '-x' so
that ecasound will truncate (vs updating) the outputs.

Check out the new Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
Ecasound-list mailing list
Received on Mon Jun 30 04:15:04 2008

This archive was generated by hypermail 2.1.8 : Mon Jun 30 2008 - 04:15:04 EEST