X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fmonitor-signal-flow.html;h=84b4eef8269c678e1d3cb1968fca3c3442495f7c;hb=966470310470267121278f9d506a3182bb10e127;hp=4354c248af072f174336dd7f02cbdff8686b92f3;hpb=7a4c28bd8605e90876ebee619de364ab7001e405;p=ardour-manual diff --git a/include/monitor-signal-flow.html b/include/monitor-signal-flow.html index 4354c24..84b4eef 100644 --- a/include/monitor-signal-flow.html +++ b/include/monitor-signal-flow.html @@ -2,8 +2,14 @@

There are three basic ways to approach monitoring:

External Monitoring

- + +
+ External monitoring +
+ External monitoring +
+
+

When using external monitoring, 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 @@ -11,19 +17,33 @@ src="/images/external-monitoring.png" /> latency. On the other hand it requires external hardware, and the monitoring settings are less flexible and not saved with the session.

-

JACK-Based Hardware Monitoring

- +

JACK-Based Hardware Monitoring

+ +
+ Hardware Monitoring +
+ Hardware Monitoring +
+
+

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 hardware monitoring. - Furthermore, on some cards this function can be controlled by JACK. This is a nice arrangement, + Furthermore, on some cards this function can be controlled by JACK. This is a nice arrangement, if the sound card supports it, as it combines the convenience of having the monitoring controlled by Ardour with the low latency operation of doing it externally.

-

Software Monitoring

- +

Software Monitoring

+ +
+ Software Monitoring +
+ Software Monitoring +
+
+

With the software monitoring approach, all monitoring is performed by Ardour—it makes track inputs available at track outputs, governed by various controls. This approach will almost always have