Containers as ‘Link modules’

Sometimes Plug In designers feel the need to have a linkage module using a container with IO modules and an internal link from Input to Output.

Something like the structure above, so you can combine and split some data connections and “hide the messy wiring” away to neaten the structure.
This is a perfectly legitimate use of a container, and does not use up any system resources as Synthedit just considers this to be a normal connection between modules So far so good.

However there are some things to be aware of.

GUI data connections. This is not going to work. The data connection through the container will be broken. This is because for the container to pass GUI data it MUST have a visible, and open control panel. Do not pass GUI data through a container.
Polyphony. If you insert a container into a control voltage line this can cause issues with polyphony further down the signal chain. This is because Containers are part of the SynthEdit Polyphony system. Beware!
MIDI to CV 2 connections. Any container that is connected to any plug on a MIDI to CV2 will automatically be considered as Polyphonic.
Note. If a module has an output that can only have one module connected to it, and you connect it to a “splitter” input, you can only connect one of the “split” outputs to a module, because Synthedit treats these connections inside the container as direct connections between modules it will still not allow multiple connections (anyway limiting a module’s plug to a single connection is usually done for a very specific programming reason and should not be circumvented with “hacks”.