Subject: [ecasound] ecawave bug?
From: Jan Stary (firstname.lastname@example.org)
Date: Tue Apr 25 2000 - 11:49:41 EEST
this is what happened to me using ecawave-0.2.0d2:
I recorded a 16,1,44100 wav, 110.25s long. I tried to
do the common editing then, using ecasound.
The window opened, read wav in, bottom line said
"....wav - visible [0.00s - 110.25s] - ..."
I wanted to erase the tail [103.00s -> ] (containing
only noise) so I marked from 103.19 to end.
The bottom line said " ... - marked [103.19s - 115.71s]"
(!) and during processing even "current 190.68s" (!!!).
It resulted in either no change or
randomly-looking-god-knows-how-cut sequence of the wav.
Erased /tmp/*.wav, run again, no good.
During processing, ecawave said
libecasound error while processing event: [AUDIOIO-WAVE]: "no riff fmt-block found"
libecasound error while setting event input: [AUDIOIO-WAVE]: "invalid RIFF-header"
libecasound error while processing event: [AUDIOIO-WAVE]: "invalid RIFF-header"
The windowshots are available at
-- To unsubscribe send message 'unsubscribe' in the body of the message to <email@example.com>.
This archive was generated by hypermail 2b28 : Tue Apr 25 2000 - 11:49:55 EEST