From 7a02ccdce1f9599b9ea5b1a08f53f913474eec25 Mon Sep 17 00:00:00 2001 From: Robin Gareus Date: Fri, 15 Feb 2013 23:26:46 +0100 Subject: [PATCH] fix some typos --- _manual/19_synchronization/01_on-clock-and-time.html | 2 +- .../19_synchronization/02_latency-and-latency-compensation.html | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/_manual/19_synchronization/01_on-clock-and-time.html b/_manual/19_synchronization/01_on-clock-and-time.html index 9a5bbae9..e0bf4699 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.

diff --git a/_manual/19_synchronization/02_latency-and-latency-compensation.html b/_manual/19_synchronization/02_latency-and-latency-compensation.html index 1aa78592..4e049d08 100644 --- a/_manual/19_synchronization/02_latency-and-latency-compensation.html +++ b/_manual/19_synchronization/02_latency-and-latency-compensation.html @@ -61,7 +61,7 @@ Low-latency is not always a feature you want to have. It comes with a couple of

-Reliable low-latency (≤10ms) on GNU/Linux can usually only be achieved by running realtime-kernel. +Reliable low-latency (≤10ms) on GNU/Linux can usually only be achieved by running a realtime-kernel.