In an open-architecture patch, objects are wired with cords carrying the video signal, and any break stops the output

Open-architecture environments (Max/MSP/Jitter, PureData, Isadora) let the artist build their own instrument as a ‘patch’: objects chosen from a library and connected to each other with cords, with parameters exposed as controls. The connecting cord is the metaphor for the video signal flowing through the chain — if the continuity of the signal is cut, there is no output. Because these environments sit on top of a programming language, the cord also stands for the continuity of the underlying code, so a single error breaks the patch. This signal-flow, node-and-wire model is the conceptual core shared by node-based visual tools generally (and the reason a broken link, not a syntax typo, is the usual failure a live visualist debugs on stage).

Examples

A Max/MSP/Jitter patch where a jit.movie feeds a jit.gl.render through effect objects; deleting one connecting cord blacks out the projection. TouchDesigner/vvvv/Hydra chains follow the same wire-the-signal model.

Assessment

Explain what happens to a patch’s output if one cord in the signal chain is disconnected, and why open-architecture tools expose the signal path as wires rather than hiding it.