ardour/manual
13
0
Fork 0
Code Pull Requests Releases Activity

fix some typos

Browse Source
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
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
_manual/19_synchronization/01_on-clock-and-time.html
View File

@ -31,7 +31,7 @@ The concept of clock and timecode is reflected in JACK and Ardour:
<p>
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.
</p>

2
_manual/19_synchronization/02_latency-and-latency-compensation.html
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>
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>