Subject: [ecasound] xrun handling (was: Re: problems with -kl)
From: Kai Vehmanen (k@eca.cx)
Date: Wed Feb 07 2001 - 00:15:29 EET
On Thu, 1 Feb 2001, Jeremy Hall wrote:
> Ecasound needs a setting to decide what to do with a XRUN. If a XRUN is
> detected when you're multitrack recording, you don't really want to
> continue...but if ecasound is providing a live feed to something, a XRUn
> is tough biscuits and we MUST MUST MUST continue, unless operator wishes
I've been meaning to add two new capabilities/hints to ecasound's realtime
devices:
1) strict_timing
- if ecasound is not able to keep up with the
device (xruns), device can stop operation
2) max_buffers
- device can utilize all its internal buffer space
- possibly more reliable operation, but can
negatively affect latency times
... these would be disabled by default. In other words, in the default
operation mode, xruns would be ignored. Now I'd still have to figure out
how to add these to the user-interface...
-- . 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 <ecasound-list-request@wakkanet.fi>.
This archive was generated by hypermail 2b28 : Wed Feb 07 2001 - 00:27:16 EET