Collapse diagrams/ into images/.

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

diff --git a/_manual/22_synchronization/02_latency-and-latency-compensation.html b/_manual/22_synchronization/02_latency-and-latency-compensation.html
index 28494a6f884d7357e2b18479e4a48e983cb5770b..c93b6849546c9af1229a2a08c9a3f358cf42f8b4 100644 (file)
--- a/_manual/22_synchronization/02_latency-and-latency-compensation.html
+++ b/_manual/22_synchronization/02_latency-and-latency-compensation.html
@@ -48,7 +48,7 @@ menu_title: Latency
 
 <h2>The Latency chain</h2>
 
-<img src="/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 
@@ -171,7 +171,7 @@ menu_title: Latency
   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="/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>