X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fio-plugins.html;h=9a9299089b51e0e6f5ae10bbdc34b00294c74464;hb=e66a7d50d6be2d32ca1201da916913543e653776;hp=64a06eb09fb19aa203653a3909b57b9d8a4d214b;hpb=cc56be149ee4c334fe411dac099dafb717590d1e;p=ardour-manual

diff --git a/include/io-plugins.html b/include/io-plugins.html
index 64a06eb..9a92990 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 automation (even when there's none) is
+  expensive in terms of CPU use. 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>