INTERACTIVE GUIDE

Genlock vs Timecode

A conceptual visualizer for the different roles of a genlock phase reference and timecode frame labels. It does not simulate device timing or certify a synchronised chain.

Camera A (Master)
Camera B (Free Run)
DRIFTING Neither active. The sources have no shared timing reference or common frame labels in this conceptual view. Real switchers may buffer or frame-synchronise such inputs; behaviour and added delay depend on the device.

When Do You Need Each?

Scenario Genlock Timecode
Live multi-camera switching (ATEM, vMix)Often required*Workflow dependent
XR LED volume — camera on Unreal EngineTiming design required*Workflow dependent
Multi-cam post-production sync (Premiere, Resolve)Optional✅ Required
Broadcast studio — master control facility✅ Required✅ Required
Single camera ENG / documentaryNot neededGood practice
Bookmark this tool

Save this for your next project or share with your engineering team.


What is Genlock?

Genlock (Generator Lock) provides a reference that compatible devices can use to align video timing. Actual sensor exposure, processing delay, reference offsets, and switcher behaviour remain device- and configuration-dependent; verify lock and timing on the real chain.

Without a shared reference, sources may arrive with unrelated timing. A switcher may use input frame synchronisers or other buffering, and the visible/latency result depends on the exact device and configuration.

What is SMPTE Timecode?

SMPTE Timecode is a metadata standard that stamps each video frame with a unique address: hours, minutes, seconds, and frames (HH:MM:SS:FF). It has nothing to do with when the sensor fires — it only identifies what the frame is called. Linear Timecode (LTC) is embedded in audio channels; Vertical Interval Timecode (VITC) is embedded in the video signal itself.

Timecode is useful in post-production because it gives recordings comparable frame addresses. Two cameras can carry identical timecode labels and still expose at different instants or have different processing delay; timecode alone does not solve LED scan or sensor-timing artifacts.

Why Both Matter for XR & LED Volumes

XR LED stages normally require a coordinated timing design across camera, render, processor, and LED system. Genlock, frame lock, scan configuration, shutter, phase offsets, and buffering are implementation-specific and must be commissioned on the real stage. Read the full technical guide →

PTP (Precision Time Protocol), with the appropriate profile and network design, distributes accurate timing in IP-based broadcast facilities. ST 2110 systems commonly use the ST 2059 profile; achieved accuracy and device alignment remain implementation-dependent.


Frequently Asked Questions

What is the difference between genlock and timecode?

Genlock is a reference that compatible devices can use to align video timing. Timecode labels frames with an address. They solve different problems; whether a workflow needs either or both depends on switching, recording, post, and device design.

Can timecode replace genlock?

No. Timecode tells you which frame it is. Genlock controls when the sensor fires. Two cameras with identical timecode can still be completely out of phase, causing visible tearing on live cuts or LED flicker in XR setups. They solve different problems.

What is Tri-Level Sync (TLS)?

Tri-Level Sync is the HD version of Blackburst. It's the reference signal distributed across a studio that cameras lock to for genlock. The signal has three voltage levels (hence "tri-level") and runs at the production frame rate. Most professional broadcast cameras and switchers support Tri-Level Sync input via BNC.

Do I need genlock for an NDI or IP video workflow?

NDI and other software workflows may buffer or synchronise inputs differently by implementation. ST 2110 systems commonly use PTP as the facility time reference, but profiles, boundary/transparent clocks, endpoint behaviour, and media alignment must all be engineered and verified.