Quick Answer
Timecode labels frames so systems can agree on where they are in time. Genlock aligns devices to a common timing reference so they capture or output frames in phase. In post workflows, timecode may be enough. In live switching, XR, and other timing-sensitive systems, a timing reference is usually needed as well.
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 does not solve the same engineering problem. They serve two distinct, yet 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 timing rhythm devices should follow.
What It Is: SMPTE Timecode
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 give post-production a much better chance of aligning clips quickly by matching timecode values inside the NLE. That still depends on the devices holding sync well over the duration of the shoot.
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.
What It Is: Genlock
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.
How to Use It
If you are shooting for later editorial sync, timecode may be the main requirement. If you are switching live sources, feeding LED processors, or trying to avoid downstream frame-sync delays, a common timing reference is typically just as important as time stamping. In hybrid or all-IP systems, that timing role may be handled differently, but it still needs to be designed deliberately.
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. | Typically Genlock First. Timecode is still useful for ISO and post alignment, but timing reference is what prevents avoidable switcher delay. |
| LED Volume / Virtual Production XR stage using Unreal Engine. | Often both. Timing reference helps keep capture and display stable, while timecode can support alignment and tracking workflows such as tracking latency compensation. |
Common Mistakes
- Assuming matching timecode means two cameras are phase-aligned.
- Treating genlock like metadata rather than a timing reference.
- Assuming all-IP timing replaces every SDI or baseband sync workflow automatically.
- Applying one rule from a camera chain to a switcher, XR, or replay system without checking the full pipeline.
Related Tools & Next Step
Use the Genlock vs Timecode visual tool for a quick comparison, and use the SMPTE Timecode Calculator when you need to convert, add, or verify actual timecode values.
Share with your camera department or subscribe for more engineering articles.