Basics: Containers – Theory

I think it’s helpful to show you the container’s theory with the aid of some simple diagrams. Basics: Containers – Practice will show you later, how it looks and what to do in SynthEdit itself.

It’s easy to lose track of a project with many modules and connections. Containers help you to keep track of bigger synthesizer or effect structures.
basics_containers_theory_diagram1

If you have an effect like a delay for example, made out of a group of modules(grey modules), a container makes sense, because you could work on it in a separate window, without having other confusing modules and connections arround.
basics_containers_theory_diagram2

A container is displayed like a single module in the window where you initialized the container.
basics_containers_theory_diagram4

Inside the container is the modules you moved from module window(labeled SynthEdit). The content (what’s inside the container), will be displayed in a separate window(panel edit window, called Main).
basics_containers_theory_diagram3

Inside the container you need an in and an out, to connect the container stuff with the source window modules. This special connection module, used to connect the container with the source window modules, is called IO Mod. In and out for sure means, you need 2 of them.
basics_containers_theory_diagram5

You have read: SynthEdit Tutorials / Basics: Containers – Theory