X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=_manual%2F19_synchronization%2F01_on-clock-and-time.html;h=e0bf469912f6d7c6d8441660d3066f0dc0d9c50c;hb=7a02ccdce1f9599b9ea5b1a08f53f913474eec25;hp=9a5bbae96b03023973caddfd10816d56283e7546;hpb=c8c2a5efaecf4bda0fe18e0758697e6af345fa6f;p=ardour-manual diff --git a/_manual/19_synchronization/01_on-clock-and-time.html b/_manual/19_synchronization/01_on-clock-and-time.html index 9a5bbae..e0bf469 100644 --- a/_manual/19_synchronization/01_on-clock-and-time.html +++ b/_manual/19_synchronization/01_on-clock-and-time.html @@ -31,7 +31,7 @@ The concept of clock and timecode is reflected in JACK and Ardour:

JACK provides clock-synchronization and is not concerned with time-code (this is not entirely true, more on jack-transport later). Within software, jackd provides sample-accurate synchronization between all JACK applications. -On the harware side JACK uses the clock of the audio-interface. Synchronization of multiple interfaces requires hardware support to sync the clocks. +On the hardware side JACK uses 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 - Sample Rate Conversion) - which decreases fidelity.