A live performance patch should prioritise the most-used controls as always-visible with less-used controls accessible but hidden

In a live situation there is no time to search for missing controls. Interface design for live performance follows the same principles as HCI — hierarchy of access — but with higher stakes: a missed control during performance cannot be recovered. The most-used parameters (volume, blend mode, speed) must be permanently visible and quickly reachable; secondary controls can be in sub-patches or behind tabs. Open-architecture environments (Max/MSP, Isadora, PureData) allow full customisation of the interface, which is both a freedom and a responsibility. Colour coding, size differentiation, and text labels help the performer under pressure.

Examples

In an Isadora patch: map the most-used effect intensity sliders to the first visible actors; put complex parameter editors in sub-scenes activated by a single toggle.

Assessment

Design a one-page interface layout for a 3-channel live visual setup. Identify which controls must always be visible and which can be hidden. Justify each choice.