Structuring a TouchDesigner performance rig as Control, World, Core, and UI containers separates concerns and speeds iteration

A reusable TD rig architecture divides the network into four top-level containers: Control (all incoming data — OSC, MIDI, audio, DMX), World (generative visual engines), Core (post-effects pipeline), and UI (operator-facing interface). This separation means you can swap engines without rewiring data routing, update post-effects without touching generators, and expose only clean parameters to a controller surface. The pattern was described as learned from the Amsterdam studio Wifive. It scales from solo gigs to multi-laptop setups because each layer has a defined responsibility and a well-known output format.

Examples

Control reads a Launchpad XL’s 9 encoders + 3 faders; World contains parallel visual engines (organic, geometric, camera); Core blends them and applies blur/color grading; UI presents only the parameters an operator needs mid-show.

Assessment

Given a TD project that mixes OSC parsing, shader generation, and output routing in one network, identify which nodes belong in each of the four containers and explain what boundary each crossing represents.