Subject: Re: [ecasound] pyeca questions
From: Paul Winkler (pw_lists_AT_slinkp.com)
Date: Wed Jun 30 2004 - 01:57:24 EEST
I've found that my pyeca script is hanging,
and I can provoke an error by feeding the same commands
to ecasound -c.
the input wav files are 16-bit stereo 44.1k.
the first output file comes out fine, the second
is only 44 bytes when the error occurs.
I get no errors before the last command.
anybody know why this sequence barfs?
cs-add splitter_chainsetup
c-add main_chain
ai-add jeff_paul_2_26_2004.wav
ao-add splitted/jeff_paul_2_26_2004__01.wav
cs-set-length-samples 16699200
cs-connect
cs-set-position-samples 0
run
cs-disconnect
ai-select jeff_paul_2_26_2004.wav
ai-remove
ao-select splitted/jeff_paul_2_26_2004__01.wav
ao-remove
ai-add jeff_paul_2_26_2004.wav
ao-add splitted/jeff_paul_2_26_2004__02.wav
cs-set-length-samples 2814168
cs-connect
cs-set-position-samples 16699200
run
A few seconds after the last "run" command, I get this:
ecasound ('h' for help)> run
- [ Controller/Starting batch processing ] ---------------------------------
- [ Engine init - Driver start ] -------------------------------------------
Warning: DBC_CHECK failed - "impl_repp->rt_lock_rep != true", samplebuffer.cpp, 850.
Aborted
One mroe thing - after the last call to cs-set-position-samples I checked
memory usage with top and ecasound was using 55 MB. Is that normal?
--Paul Winkler http://www.slinkp.com
This archive was generated by hypermail 2b28 : Wed Jun 30 2004 - 01:47:39 EEST