In the world of live multi-camera broadcasting and virtual production (XR), one of the most common points of confusion for newer engineers and camera operators is the difference between Genlock and Timecode. They are often mentioned in the same breath, run over adjacent BNC cables, and both deal with "sync."
However, substituting one for the other is physically impossible. They serve two entirely distinct, yet perfectly complementary, functions. Think of Timecode as the calendar on the wall telling you what the date and time is. Think of Genlock as the metronome telling you the exact heartbeat rhythm at which you must tap your foot.
Understanding SMPTE Timecode (LTC)
SMPTE Timecode (Linear Timecode or LTC) is metadata. It is an audible audio screech sent over an analog cable (or embedded in SDI video as VITC) that formats a chronological stamp into a recognizable format: Hours : Minutes : Seconds : Frames.
If you connect a Timecode generator like a Tentacle Sync or an Ambient Lockit to four different cameras, you guarantee that when the editor drags all four video files into their Non-Linear Editor (Premiere, Resolve, etc.), they can instantly align all the clips by telling the software "snap all footage to matching timecode."
Why Timecode Isn't Enough for Live Switching
Timecode alone does not force a camera's sensor to actually scan light at a specific millisecond. It only labels the frame that the camera naturally produced. If Camera A hits the top of its 1/50th shutter exposure a few milliseconds before Camera B, Camera A might label its frame `10:04:22:15`, and Camera B might label its frame `10:04:22:15` as well. In post-production, this 4-millisecond drift is invisible.
But in a live production environment, pushing those two unsynchronized SDI signals into a hardware vision mixer (like a Sony XVS or Ross Carbonite) will cause the switcher to reject the feed, or rely on internal "Frame Synchronizers" to buffer and delay the video until the frames align. If you are calculating audio latency or dealing with A/V sync issues, relying on switcher frame-syncs is the quickest way to ruin your lip-sync offsets.
Understanding Genlock (Tri-Level Sync / Blackburst)
Genlock (Generator Locking) solves the physical phasing problem. A Master Clock generator outputs an analog reference signal (usually Tri-Level Sync for HD/4K production). This is not data. It is a pure, rhythmic electrical pulse.
When you plug Genlock into your broadcast cameras, switchers, and graphics engines, their internal quartz crystals lock onto the pulse. The Genlock signal essentially screams at every device: "DRAW FRAME... NOW!" followed by "DRAW NEXT FRAME... NOW!".
Black Burst vs. Tri-Level Sync
Depending on your video format, your genlock signal will take one of two forms:
- Black Burst (SD): A legacy composite video signal (NTSC/PAL) that includes a color burst and vertical sync. Used for SD and some 1080i productions.
- Tri-Level Sync (HD/4K): A dedicated analog sync pulse that swings from negative to positive. Because it crosses the 0V reference line twice per cycle, it is significantly more accurate and stable for high-definition sensors.
Genlock is an analog signal. If you "daisy chain" it through multiple cameras without proper termination, the signal will reflect off the end of the cable and ghost back, causing sync errors. Always ensure the last device in a genlock chain has its 75Ω termination switch set to ON.
Summary: When Do I Need Which?
| Scenario | Requirement |
|---|---|
| Shooting documentary clips for later post-production editing | Timecode Only. (Tentacles on every camera). |
| Live switching 3 cameras through a hardware vision mixer into a broadcast TX. | Genlock Only. (Timecode is nice to have for ISO recording, but Genlock prevents switcher delay). |
| LED Volume / Virtual Production XR stage using Unreal Engine. | Both. Genlock prevents scanline tearing. Timecode gives the tracking system a timestamp to calculate the tracking latency offset. |
Share with your camera department or subscribe for more engineering articles.