Re: [ecasound] LADSPA latency ouput value SOLVED

From: Julien <julien@email-addr-hidden>
Date: Thu Feb 19 2009 - 12:05:27 EET


It works ! Thanks you very much, I can manually offset the output file.
The latency unit is a number of sample (220 sample in this example).

So a simple sox call make the sync_out_file.wav really sync with source
file :
sox in_file.wav sync_out_file.wav trim 220

Best Regards,

ecasound ('h' for help)> ### Chain operator status (chainsetup
'command-line-setup') ###
Chain "default":
        1. Fast Lookahead limiter: [1] Input gain (dB) 12.000, [2] Limit (dB)
-0.100, [3] Release time (s) 0.010, [4] Attenuation (dB) -0.000, [5]
latency *220.000*
ecasound ('h' for help)> ecasound ('h' for help)> ecasound ('h' for
help)> ---

Le mercredi 18 février 2009 à 23:30 +0200, Kai Vehmanen a écrit :
> Hi,
> On Wed, 18 Feb 2009, Julien wrote:
> > It would be nice if you can "offset" the output file, or another way to
> > work around this issue is to just display the value return by the LADSPA
> > plugin on the "latency output".
> you can at least the display the "latency" param value at the end of
> processing by doing something like:
> echo -e "run \n cop-status \n quit" |ecasound -c -i foo.wav -o null -eli:1913,0,0,0.5
> Using this automatically to offset the chain latency is then another
> thing, and will require changes to ecasound.

Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
Ecasound-list mailing list
Received on Thu Feb 19 12:15:02 2009

This archive was generated by hypermail 2.1.8 : Thu Feb 19 2009 - 12:15:03 EET