Subject: Re: [ecasound] One chain, multiple "run" calls = bad output length
From: Kai Vehmanen (kai.vehmanen_AT_wakkanet.fi)
Date: Mon Aug 23 2004 - 22:03:21 EEST
On Sat, 21 Aug 2004, Paul Winkler wrote:
> Kai, now that you're back among the living on this list ;-)
Yep, still alive and kicking! :) Sorry for the from-slow-to-nonexistant
response rate recently. Although I'm still actively following the list and
using ecasound on daily basis, I'm mostly not anywhere near my development
machine, which makes writing meaningful replies to non-trivial
questions somewhat difficult. :(
> I'll repeat some observations of a few days ago. Any clues here?
[...]
> I'd like to know whether re-using one chain for multiple "run" calls,
> with different output files for each call, is supposed to work.
> AFAICT it does not.
Let's see...
> ai-add foo-in.wav
> ao-add bar-out.wav
> cs-set-length-samples 12345 # doesn't come out that way
> ai-select foo-in.wav
> ai-set-position-samples 6789
The problem is caused by wrong chainsetup-level position when
starting the second run. 'cs-set-length-samples 12345' tells ecasound
to run until chainsetup position (see cs-get-position) reaches 12345.
Now if you issue 'cs-get-position' before the second run, you'll note that
the position is already 12345, and thus the second run stops immediately
after 'run'.
Fortunately the fix is easy, just issue 'cs-set-position-samples 0' after
'ao-add bar-out.wav', and ta-daa, it works as it should. :)
-- http://www.eca.cx Audio software for Linux!
This archive was generated by hypermail 2b28 : Mon Aug 23 2004 - 22:03:23 EEST