[Ardour-Dev] 2.8.12 testing

Paul Davis paul at linuxaudiosystems.com
Wed Sep 21 17:33:01 PDT 2011

On Wed, Sep 21, 2011 at 7:42 PM, Axel 'the C.L.A.' Müller
<axel-mueller-74 at web.de> wrote:

> Better. :)
> When adding/removing plugins the change in latency is now recognised
> immediately. Only when changing the latency in the arificial latency
> plugin the change somehow causes a "dirty" start on first transport
> start and it needs a second transport start for a clean run.
> When only hitting play it looks (from the playhead position vs. audio
> playback) as if the change isn't recognised at all. When doing a
> recording the beginning of the recorded audio is somewhat messed up. In
> my test I switched back and forth between 500 ms and 2500 ms in the
> artificial latency plugin and the recorded audio was messed up up to
> about 10 ms into the recorded audio file. The rest of the file was ok
> and well aligned.

not sure what you mean by "somewhat messed up". if you mean the fade
in applied to the audio - this reflects a global transport declick
applied whenever the transport starts up. it wouldn't affect the
actual recording of external performance.

but i guess you might mean something else.

the AL plugin is a bit dangerous to use for this kind of testing,
because it doesn't actually create any real latency at all. it merely
*reports* latency.

More information about the Ardour-Dev mailing list