Re: [ecasound] problems with cs-set-position

From: Kai Vehmanen <kvehmanen@email-addr-hidden>
Date: Wed Aug 17 2005 - 00:16:37 EEST

On Mon, 8 Aug 2005, Pedro Antonio Fructuoso Merino wrote:

>> disk i/o subsystem. You can minimize by disabling the double-buffer
>> (-z:nodb), but you will increase the risk of xruns.
> Now i haven`t "jump" and the time response is minimal. I`m not sure of the
> meanig on "xrun", is it a especial type of error? is related with alsa?

xrun is ALSA slang for "either overrun or underrun". When a disk i/o xrun
happens, the disk i/o subsystem is too slow to either read or write data.
The -z:db mode ensures that momentary slowness (for example a break of few
secs to disk i/o throughput while some other process is causing lots of
disk activity) does not cause breaks to the ecasound audio

> Now, with -z:nodb, i can listen better the error: when i make some
> successively cs-set-position the real position-time didn`t change but
> cs-get-position and ai-get-position gived me a change time position. Repeat,
> only happen with a little time jump, e.g., if it`s at the position 10 and
> made cs-set-position 100 work fine, the new cs position and ai position is
> 100 and the real position-time too, but it it`s at the position 107 and made
> cs-set-position 100 i could listen any change but a cs-get-position and
> ai-get-position give 100.

Hmm, that sounds strange. Are you using JACK? If yes, try
with "-G:jack,ecasound,notransport". Also try using ALSA instead of JACK.
If using ALSA, please try with OSS instead (or with ALSA's OSS-emulation)
=> "-o /dev/dsp".

  links, my public keys, etc at
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement *
Ecasound-list mailing list
Received on Wed Aug 17 04:15:05 2005

This archive was generated by hypermail 2.1.8 : Wed Aug 17 2005 - 04:15:05 EEST