Hey all-
Yes, the documentation for this particular issue is certainly lacking. We've created a ticket here to add block diagrams to the User Guide, and clean up the explanation.
Here's how the routing works in each format:
Mono-In -> Mono-Out:
The mono input is fed to both the Left (yellow) and Right (red) input blocks. Both of these signal paths operate independently inside of the patching section. The Left and Right output blocks are then mixed at the output of the plugin (with proper gain staging applied). Thus, the two attached screenshots (MonoMono1 and MonoMono2) are identical in terms of sound.
Mono-In -> Stereo-Out:
Similarly the mono input is fed to both the Left (yellow) and Right (red) input blocks. Both of these signal paths operate independently inside of the patching section. The Left and Right output blocks are in stereo and thus correspond . Thus, the two attached screenshots (MonoStereo1 and MonoStereo2) are identical in terms of sound.
Stereo-In -> Stereo-Out:
The Left and Right inputs correspond to the left/right channels of the stereo track, similarly with the outputs. Both of you are correct in guessing that each of the signal paths are "dual-mono", and operate independently of each other. Of course, they could be mixed/modulated/affected in any way inside of the patching seciton, but the yellow/red paths are totally independent of each other.
So, if you wanted to set up only a signle mono delay or pitch block, it would depend on what IO format of the plugin you are using. In Mono-In -> Mono-Out or Mono-In -> Stereo-Out, you could just patch the Left input through a block, and then the output of that block to both Left/Right outputs.
For Stereo-In -> Stereo-Out, you'd have to use two delay or pitch blocks, with identical settings, if you wanted to preserve the stereo image. One way you could do this is to map the desired parameters (e.g. delay time) of both delay or pitch blocks to a soft key, so that they could be controlled together (see attached preset). This preset would work in all IO configurations as well.
Hopefully that clears up some of the confusion. It's definitely not straightforward, and we'll update the documentation to be more helpful.
-Tom
