Subject: Re: [ecasound] reverse audio object added
From: Jeremy Hall (jhall_AT_uu.net)
Date: Tue Jan 29 2002 - 21:01:47 EET
for the db stuff, is this a latency hog or does it properly calculate the
capture offset? I am finding that if I use -z:nodb that my ecasounds are
killed by jack's subgraph manager. Something seems to have happened to
the I/O stuff recently causing a performance hit.
In the new year, Kai Vehmanen wrote:
> Inspired by Sooperlooper's reverse function, I decided to do some coding.
> The result is a new audio object type 'reverse'. I committed the first
> version to CVS. Quoting ecasound(1) man page:
> dit(Reverse - process audio data backwards)
> Object type 'reverse' can be used to reverse audio
> data coming from an audio object. As an example,
> "ecasound -i reverse,foo.wav -o /dev/dsp" will play 'foo.wav'
> backwards. Reversing output objects is not supported.
> Note! Trying to reverse audio object types with really
> slow seek operation (like mp3), works extremely badly.
> Try converting to an uncompressed format (wav or raw)
> first, and then do reversation.
> It's a bit inefficient, but thanks to the disk i/o subsystem, still quite
> usable. By increasing the doublebuffer size to 500000 samples
> (-z:db,500000), I managed to play a 10ch/32bit/44.1kHz test file backwards
> (total filesize 600MB), without xruns.
> Audio software for Linux!
> To unsubscribe send message 'unsubscribe' in the body of the
> message to <ecasound-list-request_AT_wakkanet.fi>.
-- To unsubscribe send message 'unsubscribe' in the body of the message to <ecasound-list-request_AT_wakkanet.fi>.
This archive was generated by hypermail 2b28 : Tue Jan 29 2002 - 20:52:04 EET