Syncing a live stream to automated video feeds isn’t a “plug‑and‑play” task—if it’s off by a beat or a second, the audience sees a glitch and the brand suffers. Start with a single, authoritative clock source: NTP for all networked gear, SMPTE‑timecode for audio and video, and a Genlocked video switcher that locks every incoming feed. Tie the audio interface’s digital clock to the same NTP/PTP pool and feed the live audio into a capture card that injects the timecode into the RTMP stream. The video server (e.g., OBS, vMix, or a dedicated media server) must read that timecode and schedule playback of pre‑encoded clips exactly on cue.

Your automation stack is the backbone. Use a broadcast‑automation system that can emit OSC or SysEx triggers to your video server. For example, an Enigma play‑point can push a “clip‑start” command to vMix, which then uses the incoming timecode to align the video clip with the live audio. Store all your automated clips in a central media library tagged with the same SMPTE code so the server can pull the right frame at the right time. Keep the media paths short and redundant; any hop increases latency and the risk of a drift.

Latency and jitter are the enemy of tight sync. Keep all links under 5 ms if possible—measure with a timecode analyzer, and set the audio buffer size to the minimum that still keeps the DSP stable. If the video stream is arriving over IP, use a low‑latency protocol like WebRTC or low‑bandwidth RTMP with a buffer of 2–3 frames. When the live feed dips into a freeze, have a fallback loop in the media server that automatically takes over, and program the automation to detect the drop‑in and cue the backup clip instantly.

Finally, test the whole chain in a live rehearsal before the show. Push a test signal through the audio path, feed it into the video server, and use a log of timestamps to confirm that the video frames line up with the audio samples. Automate those checks with a script that compares the timecodes from the media server and the broadcast automation; any discrepancy larger than 10 ms should trigger an alarm. Consistent, rigorous testing is what keeps the live stream and video feed dancing in lockstep.