Collapse diagrams/ into images/.

[ardour-manual] / _manual / 16_recording / 01_monitoring / 02_monitor-signal-flow.html

diff --git a/_manual/16_recording/01_monitoring/02_monitor-signal-flow.html b/_manual/16_recording/01_monitoring/02_monitor-signal-flow.html
index 20a9f9a35d2f41ddb12efcbac379856238bcdd8b..9cbe08863d42a3ea9a40f00fe644b9e032fca737 100644 (file)
--- a/_manual/16_recording/01_monitoring/02_monitor-signal-flow.html
+++ b/_manual/16_recording/01_monitoring/02_monitor-signal-flow.html
@@ -8,7 +8,7 @@ menu_title: Signal Flow
 
 <h3>External Monitoring</h3> 
 <img class="right"
-src="/diagrams/external-monitoring.png" />
+src="/images/external-monitoring.png" />
 <p>When using <dfn>external monitoring</dfn>, Ardour plays no role in
   monitoring at all. Perhaps the recording set-up has an external mixer which
   can be used to set up monitor mixes, or perhaps the sound-card being used
@@ -17,7 +17,7 @@ src="/diagrams/external-monitoring.png" />
   settings are less flexible and not saved with the session.</p> 
 
 <h3>JACK-Based Hardware Monitoring</h3> 
-<img class="right" src="/diagrams/jack-monitoring.png" />
+<img class="right" src="/images/jack-monitoring.png" />
 <p>Some sound cards have the ability
   to mix signals from their inputs to their outputs with very low or even zero 
   latency, a feature called <dfn>hardware monitoring</dfn>.
@@ -28,7 +28,7 @@ src="/diagrams/external-monitoring.png" />
 </p> 
 
 <h3>Software Monitoring</h3> 
-<img class="right" src="/diagrams/ardour-monitoring.png" />
+<img class="right" src="/images/ardour-monitoring.png" />
 <p>With the <dfn>software monitoring</dfn> approach, all monitoring is
   performed by Ardour &mdash; it makes track inputs available at track
   outputs, governed by various controls. This approach will almost always have