Syncing to music with the Tempo node
The Tempo node connects Scope to an external beat source, either Ableton Link or a MIDI clock device. Once connected, it outputs real-time BPM and beat-phase values you can wire to any pipeline parameter to create music-reactive visuals for live performances, installations, or studio sessions.Adding a Tempo node
Connecting to a beat source
Choose your source
Select Link (Ableton Link) or MIDI Clock.For MIDI Clock, select your MIDI device from the device dropdown that appears.
Ableton Link
Ableton Link works over your local network. Any app on the same network with Link enabled will be discovered automatically, no manual configuration required.MIDI Clock
Your MIDI device must be connected and powered on before opening Scope. Scope reads the MIDI clock stream and derives BPM from the timing messages.If your MIDI device is not appearing in the dropdown, try closing Scope, connecting the device, and relaunching.
Output handles
| Handle | Type | Description |
|---|---|---|
bpm | number | Current tempo in beats per minute |
beat_phase | number | Position within the current beat: 0.0 (downbeat) to 1.0 (next downbeat) |
beat_count | number | Cumulative beat counter since sync started |
bar_position | number | Position within the current bar (depends on beats-per-bar setting) |
is_playing | boolean | Whether the beat source is actively playing |
Wiring beat values to parameters
Connect any output handle to a pipeline’s numeric parameter to make it react to the beat:- Denoising strength on the beat: Wire
beat_phaseto the denoising slider of a StreamDiffusion V2 node. The strength pulses with each beat. - Switch prompts on bars: Connect
bar_positionthrough a Math node to threshold logic, then into a Prompt List trigger. - Quantized parameter sweeps: Use
beat_countto drive a Math node that computes a cycling value.
Quantization and lookahead
Advanced settings in the Tempo node let you fine-tune how beat values interact with your pipeline:- Beats per bar controls how many beats make up one bar (default 4).
- Quantize mode snaps parameter changes to beat boundaries, preventing changes from landing between beats.
- Lookahead triggers parameter changes slightly early to compensate for AI inference latency. This ensures that the visual change actually lands on the beat rather than a few frames late.
Example: Beat-reactive prompt blending
See also
Scheduler Node
Set up fixed-tempo trigger sequences without a live beat source
Workflow Builder
Learn the basics of composing node graphs