From 05ccd18414f5b9e21c92b223676a96de0e5c3969 Mon Sep 17 00:00:00 2001
From: Robin Gareus
@@ -79,12 +79,12 @@ During tracking it is important that the sound that is currently being played ba
-This is where latency-compensation comes into play. There are two possibilities to compensate for latency in a DAW: read-ahead the DAW actually starts playing a bit early (relative to the playhead), so that when the sound hits the speakers a short time later, it is exactly aligned with the material that is being recorded. -And write-behind since we know that the sound that is being played back has latency, the incoming audio can be delayed by the same amount to line things up again. +This is where latency-compensation comes into play. There are two possibilities to compensate for latency in a DAW: read-ahead the DAW starts playing a bit early (relative to the playhead), so that when the sound arrives at the speakers a short time later, it is exactly aligned with the material that is being recorded. +And write-behind; since we know that play-back has latency, the incoming audio can be delayed by the same amount to line things up again.
-As you may see the second approach has various issues implementation issues regarding timecode and transport synchronization. Ardour uses internal read-ahead to compensate for latency. The time displayed in the Ardour clock corresponds to the audio-signal that you hear on the speakers (and is not where ardour reads files from disk). +As you may see, the second approach is prone to various implementation issues regarding timecode and transport synchronization. Ardour uses read-ahead to compensate for latency. The time displayed in the Ardour clock corresponds to the audio-signal that you hear on the speakers (and is not where ardour reads files from disk).