Syncing and Aligning a Live Performance Rig

Every alignment problem in a live rig is the same problem at three timescales: musical beats between laptops, milliseconds between loudspeakers, and code versions between your editor and the running host. This module builds toward running a small club-style set — two machines jamming in tempo, a custom OSC controller driving Ableton Live, mics open on stage, and a fill speaker covering the seats the mains can’t reach — where all three layers stay locked while the music plays.

Start supported: on a shared network, get two apps beating together using peer-to-peer beat/tempo/phase sync (no master clock), and notice how launch quantization lets a late joiner land on the downbeat. Next, wire a controller to Live via AbletonOSC and practice the fast iteration loop — edit a handler, send the reload message, test — until changing behaviour mid-session feels routine; this loop is the module’s part-task drill because on stage you will do it under pressure. Then move to the room: ring out the system and settle gain 6 dB under the feedback threshold, and dial electronic delay into the fill feed so its wavefront never beats the mains to the listener. The capstone combines all of it, unsupported, in one continuous performance.

The four required atoms are hard gates: without Link the machines drift, without the feedback margin the room howls, without fill delay the image collapses to the nearest box, and without hot-reload a controller bug means restarting Live mid-set. The supporting atoms deepen the why — the precedence/Haas threshold and comb filtering explain what misalignment sounds like and why “a few milliseconds” matters, while the MIDI protocol and WebSocket/OSC control-plane atoms situate AbletonOSC in the wider landscape of remote control.