Quick answer
Use MIDI clock for section timing, not raw visual intensity. Let audio analysis drive energy and texture, while MIDI clock handles bar-level transitions, scene changes, and cue consistency. That split keeps the rig musical without becoming jittery.
Why competitor content leaves a gap
Current ranking pages above smaller niche sites are usually derivative docs, Reddit threads, or isolated tutorial videos. They explain how to receive clock, but they rarely show how to combine clock, FFT, fallback scenes, and operator safety in one repeatable patch.
Recommended workflow
- Receive MIDI clock in a dedicated sync COMP. Keep transport state separate from the visual network.
- Convert clock into bar and phrase markers. Use those markers for scene swaps, not for every parameter move.
- Run audio analysis in parallel. FFT, RMS, and transient detection should control texture, scale, color, and motion.
- Gate big changes to phrase boundaries. Drops, chorus entries, and camera swaps should happen on bars or phrases to avoid visual drift.
- Build a failover layer. If clock disappears, keep the patch alive on audio analysis alone so the output never freezes.
Operator checklist
- Test clock start and stop behavior before doors open.
- Keep one muted emergency scene mapped to a hotkey.
- Normalize audio input so low end spikes do not fake cue changes.
- Log BPM changes during rehearsal and build one version per song if needed.
- Route the final mix into REACT if you need a faster show-safe visual fallback.
Related guides
Need a faster live-ready path?
Use REACT when you want the audio-reactive output without maintaining a custom TouchDesigner graph for every show. Then keep getting workflow notes through the Compeller newsletter.