Initial cleanup of content, new images & content added.

[ardour-manual-diverged] / _manual / 19_synchronization / 02_latency-and-latency-compensation.html

diff --git a/_manual/19_synchronization/02_latency-and-latency-compensation.html b/_manual/19_synchronization/02_latency-and-latency-compensation.html
index 6b11a6be8fefeb00e36642ac43ac699c4a99d0e1..5eeb342e7919666163aea894aec3b5d611fbbef5 100644 (file)
--- a/_manual/19_synchronization/02_latency-and-latency-compensation.html
+++ b/_manual/19_synchronization/02_latency-and-latency-compensation.html
@@ -48,7 +48,7 @@ menu_title: Latency
 
 <h2>The Latency chain</h2>
 
-<img src="/ardour/manual/html/diagrams/latency-chain.png"  title="Latency chain" alt="Latency chain" />
+<img src="/images/latency-chain.png"  title="Latency chain" alt="Latency chain" />
 <p>
   <em>Figure: Latency chain.</em> 
   The numbers are an example for a typical PC. With professional gear and an 
@@ -152,6 +152,7 @@ menu_title: Latency
   to the audio-signal that you hear on the speakers (and is not where Ardour 
   reads files from disk).
 </p>
+
 <p>
   As a side note, this is also one of the reasons why many projects start at 
   timecode <samp>01:00:00:00</samp>. When compensating for output latency the 
@@ -167,14 +168,18 @@ menu_title: Latency
   To achieve sample accurate timecode synchronization, the latency introduced 
   by the audio setup needs to be known and compensated for.
 </p>
+
 <p>
   In order to compensate for latency, JACK or JACK applications need to know 
   exactly how long a certain signal needs to be read-ahead or delayed:
 </p>
-<img src="/ardour/manual/html/diagrams/jack-latency-excerpt.png"  title="Jack Latency Compensation" alt="Jack Latency Compensation" />
+
+<img src="/images/jack-latency-excerpt.png"  title="Jack Latency Compensation" alt="Jack Latency Compensation" />
+
 <p>
   <em>Figure: Jack Latency Compensation.</em>  
 </p>
+
 <p>
   In the figure above, clients A and B need to be able to answer the following 
   two questions: