X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;ds=sidebyside;f=include%2Flatency-and-latency-compensation.html;h=f14fc0e917bcc2b59562018251549a8dc00a10d5;hb=976060f5e2c2064c0574f2f8764721452679db53;hp=e323059956ef2b04e0f51f33086bcae1449e058c;hpb=3c0bdbab01a9900147a5f794026960040f0f9e0c;p=ardour-manual
diff --git a/include/latency-and-latency-compensation.html b/include/latency-and-latency-compensation.html
index e323059..f14fc0e 100644
--- a/include/latency-and-latency-compensation.html
+++ b/include/latency-and-latency-compensation.html
@@ -45,6 +45,11 @@
The Latency chain
+
+
+ Note! the rest of this document assumes the use of jackd for the audio
+ backend. While many of the concepts are true, the specifics may be different.
+
@@ -66,7 +71,7 @@
processed and played back.
- It is important to note that processing latency in a jackd is a matter of
+ It is important to note that processing latency in Ardour is a matter of
choice. It can be lowered within the limits imposed by the hardware (audio
device, CPU and bus speed) and audio driver. Lower latencies increase the
load on the system because it needs to process the audio in smaller chunks
@@ -156,7 +161,7 @@
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 is heared on the speakers (and is not where Ardour
+ to the audio signal that is heard on the speakers (and is not where Ardour
reads files from disk).