TidalCycles uses Ableton Link by default for BPM synchronization with other performers and applications

TidalCycles supports Ableton Link as its default synchronization mechanism, which means two TidalCycles instances on the same local network will automatically lock BPMs. This enables multi-performer algorave setups without any manual clock patching. A known gotcha: Link is on by default, so joining the same WiFi network as a performing live coder — even as an audience member setting up — can accidentally sync with and disrupt a live set. Strudel (the browser port) does not yet implement Link, only MIDI clock output.

Examples

Two performers at an algorave both run TidalCycles over the venue’s WiFi. Without any configuration, their patterns align to the same beat grid via Link. A third person in the audience opens TidalCycles on the same network and accidentally joins their session.

Assessment

What is Ableton Link and why is it the preferred sync method for multi-performer live coding rather than MIDI clock? Describe the ‘accidental sync’ risk and how a performer should mitigate it.