Subject: [ecasound] edi-22 progress - multitrack sync
From: Kai Vehmanen (k_AT_eca.cx)
Date: Mon May 13 2002 - 04:26:34 EEST
I just committed a new multitrack sync implementation to the CVS-tree.
I've done various tests with ALSA, JACK and OSS input/outputs - and using
different buffering parameter combinations. At least in my tests the new
sync code seems to work at least as well as the old code.
This is probably the single most important pending todo item that has kept
me from releasing 2.1dev8. The sync code rewrite was necessary to complete
edi-22 - "engine iteration from outside sources" - which is closely
related to ecasound's JACK-support (and possibly in the future other
similar callback-driven frameworks).
Please test this code (by doing multitrack recording) and report any
results (both success and failure!). Multitrack sync is part of
ecasound's core functionality so it needs to work reliably in all
circumstances. In other words a lot of testing is needed.
If you do have trouble, run ecasound with "-d:63" (or higher) and send me
the debug output (privately for long debug logs) and the exact
command-line (or .ecs) executed. Especially interesting debug lines are
for instance:
eca-engine.cpp: (eca-engine) Input latency for 'ALSA named PCM device' is 0.
eca-engine.cpp: (eca-engine) Output latency for 'ALSA named PCM device' is 12288.
eca-engine.cpp: (eca-engine) recording offset is 12288 samples.
... and ...
eca-engine.cpp: (eca-engine) Skipping rt-target output foorec_3.wav.
eca-engine.cpp: (eca-engine) Skipping rt-target output foorec_3.wav.
eca-engine.cpp: (eca-engine) Skipping rt-target output foorec_3.wav.
-- http://www.eca.cx Audio software for Linux!-- 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 : Mon May 13 2002 - 04:13:29 EEST