TouchDesigner audio reactive latency guide for live sets

Latency targets that feel musical

Visual latency is not just a technical number. It changes whether the room feels locked to the track or slightly detached from it.

Common delay sources

• Audio interface buffer settings. Oversized buffers add delay before TouchDesigner or any visual engine sees the transient.
• Wireless routing hops. Every extra capture, stream, or wireless link can add instability.
• Heavy GPU scenes and frame drops. A visual that looks good at home can miss beats when the output resolution or projector chain changes.
• Cloud-dependent processing during a show. Anything that depends on remote generation is risky for live sync.

Quick 120fps test method

1. Feed a metronome click or a sharp kick sample into the same audio path used for the show.
2. Trigger a high-contrast flash on transients.
3. Record the speaker and screen together at 120fps or faster.
4. Count the frame offset between the click and flash.
5. Lower buffer size, simplify scenes, or remove routing hops until sync is repeatable.

TouchDesigner-specific checks

In TouchDesigner, watch cooking time, dropped frames, audio device settings, and any TOP chain that spikes when the scene changes. If the scene only hits your target when idle, it is not show-ready.

For production, keep a fallback scene that is visually simpler but rhythmically reliable. The audience forgives simpler visuals faster than late visuals.