fix some typos

This commit is contained in:
Robin Gareus 2013-02-15 23:26:46 +01:00
parent c8c2a5efae
commit 7a02ccdce1
2 changed files with 2 additions and 2 deletions

View File

@ -31,7 +31,7 @@ The concept of clock and timecode is reflected in JACK and Ardour:
<p> <p>
JACK provides clock-synchronization and is not concerned with time-code (this is not entirely true, more on jack-transport later). 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. 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. 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.
</p> </p>

View File

@ -61,7 +61,7 @@ Low-latency is not always a feature you want to have. It comes with a couple of
</p> </p>
<p> <p>
Reliable low-latency (≤10ms) on GNU/Linux can usually only be achieved by running <a href="https://rt.wiki.kernel.org/" title="https://rt.wiki.kernel.org/">realtime-kernel</a>. Reliable low-latency (≤10ms) on GNU/Linux can usually only be achieved by running a <a href="https://rt.wiki.kernel.org/" title="https://rt.wiki.kernel.org/">realtime-kernel</a>.
</p> </p>
<p> <p>