Subject: Re: [ecasound] SHUHZAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAM! I FOUND ME A BUG!
From: Kai Vehmanen (email@example.com)
Date: Mon Dec 18 2000 - 01:00:35 EET
On Tue, 12 Dec 2000, Jeremy Hall wrote:
> ecasoud -i /dev/dsp -o file.wav
> if file.wav is a raw file with .wav extention, or, if file.wav was created
> somehow with ecasound but headers not properly written, when you go to
> write over it, if you manage to get an error like this one, riff block not
> found, ecasound normally exits (if not in interactive mode) but if in
> interactive mode, hords of data gets spewed to the console on stdout as
> /dev/dsp spews on me. This is definitely NOT cool and made my computer
Huh, this one's strange, but I can confirm it's a bug alright. Enabling
the current chainsetup (all audio objects are opened) fails, but for some
reason engine still gets started. Now processing is started with objects
in completely invalid state, and ecasound ends up writing data to
non-existant file descriptors. Will be fixed asap.
-- . http://www.eca.cx ... [ audio software for linux ] /\ . . http://www.eca.cx/sculpscape [ my armchair-tunes mp3/ra/wav ]
-- To unsubscribe send message 'unsubscribe' in the body of the message to <firstname.lastname@example.org>.
This archive was generated by hypermail 2b28 : Mon Dec 18 2000 - 03:11:46 EET