X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fon-clock-and-time.html;h=2e221e2f5e4c5e9230ae3ef49ab8f8707634b251;hb=a61fbacdfcb7a76fe425fada61f49fc85751e47a;hp=9e3d95a007cd48c123b23cfeb60ac1ec8f84b232;hpb=8b72d27963928a6d72d0f171a24d53d46840088d;p=ardour-manual

diff --git a/include/on-clock-and-time.html b/include/on-clock-and-time.html
index 9e3d95a..2e221e2 100644
--- a/include/on-clock-and-time.html
+++ b/include/on-clock-and-time.html
@@ -11,7 +11,8 @@
   <a href="https://en.wikipedia.org/wiki/Word_clock" title="https://en.wikipedia.org/wiki/Word_clock">Word Clock</a>.
   It does not carry any absolute reference to a point in time: A clock is
   used to keep a system's sample rate regular and accurate.
-  Word clock is usually at the frequency of the sample rate&mdash;at 48&nbsp;kHz, its period is about 20&nbsp;μs. Word Clock is the most
+  Word clock is usually at the frequency of the sample rate&mdash;at 48&nbsp;kHz,
+  its period is about 20&nbsp;μs. Word Clock is the most
   common sample rate based clock but other clocks do exist such as Black and
   Burst, Tri-Level and DARS. Sample rates can be derived from these clocks as well.
 </p>
@@ -34,16 +35,17 @@
 </p>
 
 <p>
-  JACK provides clock synchronization and is not concerned with time code
+  JACK (Ardour does this internally if using the ALSA backend) provides
+  clock synchronization and is not concerned with time code
   (this is not entirely true, more on jack-transport later).
   On the software side, jackd provides sample-accurate synchronization
   between all JACK applications.
-  On the hardware side, JACK uses the clock of the audio-interface.
+  On the hardware side, JACK and Ardour use the clock of the audio-interface.
   Synchronization of multiple interfaces requires hardware support to sync
   the clocks.
   If two interfaces run at different clocks the only way to align the
   signals is via re-sampling (SRC&mdash;Sample Rate Conversion), which is
-  expensive in terms of CPU usage and may decreases fidelity if done
+  expensive in terms of CPU usage and may decrease fidelity if done
   incorrectly.
 </p>
 
@@ -65,3 +67,4 @@
   clock and time. It is possible to extract absolute position data
   and speed from it.
 </p>
+