- Notice that using the Pin Connection overrides the I/O config setting (Flexible vs Strict). A processor <em>can</em>,
- even in Strict I/O mode, have a different number of outputs than inputs. Non-customized plugins downstream
- will follow suit depending on the selected route mode. e.g. adding an additional output to a plugin on a
- track set to strict-i/o will trickle down the process chain until the output and result in the addition of
- an output port. This is useful for example in case of a mono to stereo reverb.
+ Using the Pin Connection overrides the I/O config setting (Flexible vs.
+ Strict). A processor <em>can</em>, even in Strict I/O mode, have a different
+ number of outputs than inputs. Non-customized plugins downstream will follow
+ suit depending on the selected route mode. e.g. adding an additional output
+ to a plugin on a track set to Strict I/O will trickle down the process chain
+ to the output and result in the addition of an output port. This is useful
+ for example in case of a mono to stereo reverb.
+</p>
+
+<p>
+ The window allows connection of the I/O ports to the plugin pins and other
+ I/O ports, provided they are compatible (MIDI vs. audio), just by dragging
+ & dropping the end connectors on top of one another. A dotted connector's
+ line is a "<em>thru</em>" line that directly connects an input to an output
+ without connecting to a pin on the plugin—hence without any audio
+ modification. These "thru" connections are latency compensated, with respect
+ to those being affected by the plugin, in order to avoid phasing issues.