Update a few cue screenshots for 7.0/7.1

[ardour-manual] / include / io-plugins.html

diff --git a/include/io-plugins.html b/include/io-plugins.html
index 9a9299089b51e0e6f5ae10bbdc34b00294c74464..2a76031903744af01324f0fce021d27dd50bf245 100644 (file)
--- a/include/io-plugins.html
+++ b/include/io-plugins.html
@@ -18,8 +18,8 @@
   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
+  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>
@@ -101,3 +101,15 @@
   <img style="width:50%;" width="50%" src="/images/io-plugins-new-track-from-io-plugin.png" alt="New track connected to an I/O plugin">
   <figcaption>New track connected to an I/O plugin</figcaption>
 </figure> 
+
+<p>
+  On the <kbd class="window">Audio Connections</kbd> dialog, the ports of pre-
+  and post-process plugins are listed on dedicated tabs
+  (<kbd class="tab">I/O Pre</kbd> and <kbd class="tab">I/O Post</kbd>),
+  separately from all other ports.
+</p>
+
+<figure>
+  <img style="width:50%;" width="50%" src="/images/io-plugins-in-audio-connections.png" alt="I/O Plugins in the Audio Connections dialog">
+  <figcaption>I/O Plugins in the Audio Connections dialog</figcaption>
+</figure>