X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fio-plugins.html;h=7e9043ca8453108f945d575be02f83c92094c643;hb=88b8130ec83209b2db4cb837ab77156aa4bab6a0;hp=7a2d952ea693de5e5192bd003cd073fdb94877f3;hpb=a7940376c59412250b5ebb488f5f353617f7254d;p=ardour-manual

diff --git a/include/io-plugins.html b/include/io-plugins.html
index 7a2d952..7e9043c 100644
--- a/include/io-plugins.html
+++ b/include/io-plugins.html
@@ -11,8 +11,17 @@
   number of tracks or busses in Ardour. This is a lot like doing some of the
   processing with a chain of guitar pedals, then feeding the signal to an Aux In
   port on a mixing console or an input port on a multi-effects digital
-  pedalboard. The rationale for pre-processing with I/O plugins is that it's a
-  more lightweight way to do it as compared to busses.
+  pedalboard.
+</p>
+
+<p>
+  The rationale for pre-processing with I/O plugins is that it's a more
+  lightweight way to do it as compared to busses. Much of that is because busses
+  have automatable parameters such as fader and panner positions, as well as
+  plugins' parameters. Evaluating parameter automation (even when there's none)
+  adds additional load to the CPU. However I/O plugins are not automatable, so
+  there's no evaluation happening. As far as Ardour is concerned, they are
+  almost like JACK audio server clients running alongside Ardour.
 </p>
 
 <p>
@@ -22,6 +31,11 @@
   IP to a receiver for broadcasting.
 </p>
 
+<figure>
+  <img style="width:50%;" width="50%" src="/images/io-plugins-ndi-input.png" alt="NDI Input plugin loaded as a pre-processing I/O plugin">
+  <figcaption>NDI Input plugin loaded as a pre-processing I/O plugin</figcaption>
+</figure>
+
 <p>
   It's also possible to use the post-processing section to load plugins for room
   correction or signal analysis (VU meters, spectrum analyzers etc.).