Re: [ecasound] Question: is it a bug, a feature or necessary evil ?

From: Kai Vehmanen <kvehmanen@email-addr-hidden>
Date: Tue Apr 13 2010 - 20:41:10 EEST


On Sun, 11 Apr 2010, Artur wrote:

> Ecasound adds extra 1024 samples at the beginnig of output stream. For
> example, when I do something like:
> ecasound -t:0 -i:null -f:u8,1,48000 -o:output.wav

the '-t' option does not provide single sample granularity. Instead, the
granularity is determined by engine buffer size (-b:xxx), e.g. the length
of one engine iteration.

The default is '-b:1024' which explains the behaviour you are seeing. The
engine stops after the first iteration.

If you need sample granularity, you should use "select" input object.

ecasound -i:select,0,0,foo.wav -o bar.wav

.. creates a 44byte bar.wav (only the RIFF header). Unfortunately "select"
and other sequencing objects do not work with infinite length child
objects (like "null"). This is a limitation of the current

Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
Ecasound-list mailing list
Received on Wed Apr 14 00:15:01 2010

This archive was generated by hypermail 2.1.8 : Wed Apr 14 2010 - 00:15:01 EEST