Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 62261: Time Code for Professional Video Recording — Synchronization Standards
IEC 62261 is the international standard that defines the time code format used in professional television and video recording systems. It ensures frame-accurate synchronization across multi-camera shoots, editing suites, and broadcast playout chains.
1. Overview of IEC 62261
IEC 62261, aligned with SMPTE 12M and EBU Tech 3097, specifies the encoding, transmission, and recovery of time code signals in professional video environments. Time code is an essential metadata stream that labels every video frame with a unique address (hours:minutes:seconds:frames), enabling deterministic editing, synchronization, and logging.
The standard addresses two primary physical transport mechanisms: Longitudinal Time Code (LTC), recorded on an audio track or dedicated channel, and Vertical Interval Time Code (VITC), embedded in the vertical blanking interval of the analogue video signal. Modern digital interfaces such as SDI and AES3 also carry time code as ancillary data packets.
2. LTC vs VITC — Physical Layer Comparison
| Parameter | LTC (Longitudinal Time Code) | VITC (Vertical Interval Time Code) |
|---|---|---|
| Transport medium | Audio track / dedicated channel | Vertical blanking interval (lines 12-20) |
| Bit rate | 80 bits per frame (2,400 bps @ 30 fps) | 90 bits per field (including sync and CRC) |
| Read-while-shuttle | Yes (0.1x-100x variable speed) | No (requires stable vertical sync) |
| Error detection | Phase-encoding parity | Cyclic Redundancy Check (CRC) |
| Drop-frame support | Yes, via bit 10 (drop frame flag) | Yes |
| VTR head contact required | Yes | No (embedded in video) |
| Editing accuracy | ±1 frame typical | ±0 frames (field-accurate) |
When shuttling tape at high speed (>50x), LTC may become unreadable due to bandwidth limitations of the reproduce head. In such cases, VITC is the fallback, but only if the transport can maintain a valid vertical lock.
3. Drop-Frame vs Non-Drop-Frame
A critical nuance in 29.97 fps colour NTSC systems is the discrepancy between real time and frame count. At 29.97 fps, there are 107,892 frames per hour instead of 108,000. Drop-frame time code compensates by skipping two frame numbers (0 and 1) at the start of each minute except minutes divisible by 10. This ensures the time code matches wall-clock time within 0.1 ppm.
| Property | Non-Drop-Frame (NDF) | Drop-Frame (DF) |
|---|---|---|
| Frame count per hour | 108,000 | 107,892 |
| Time drift per hour | +3.6 sec relative to real time | < 1 ms |
| Typical use | Film transfer, 24p projects | Broadcast playout, live TV |
| Separator character | Colon (HH:MM:SS:FF) | Semicolon (HH;MM;SS;FF) |
4. Engineering Design Insights
4.1 Time Code Regeneration and Re-timing
In large facilities, time code distribution over long cable runs introduces jitter and skew. A robust design employs dedicated time code distribution amplifiers (TCDAs) with re-timing PLLs that lock to the house reference (genlock / black burst). The re-timer should have a holdover accuracy of ±1 frame over 24 hours to survive reference loss.
For critical multi-room synchronisation, use a master time code generator synchronised to GPS/GNSS (stratum-1 accuracy). Distribute via AES3 embedded time code or dedicated LTC over balanced audio lines with 600 Ω termination.
4.2 Time Code in IP Workflows (SMPTE ST 2110)
IEC 62261 concepts extend naturally to IP-based production. SMPTE ST 2110-30 (PCM audio) and ST 2110-40 (ancillary data) carry time code as RTP payloads. The same 80-bit LTC structure is packetized, but engineers must account for network delay variation (jitter buffers) and PTP (IEEE 1588) grandmaster clock alignment. A typical jitter buffer of 1 ms at 48 kHz adds ~48 samples of latency, which is negligible for time code but critical for lip-sync.
Do not rely on best-effort NTP for time code distribution in live production. Use PTPv2 with a profile compliant to SMPTE ST 2059-1. The maximum time error (MTE) must be kept below ±1 µs for frame-accurate operations.
5. Frequently Asked Questions
Q1: Can LTC and VITC coexist on the same tape?
Yes. Most professional VTRs record both simultaneously. LTC is recorded on the cue/address track, while VITC is inserted into the video vertical interval. The reader auto-senses which source has better SNR.
Q2: Why does drop-frame time code skip frame numbers 0 and 1?
To correct the 0.1% speed error inherent in 29.97 fps. Skipping two frames per minute (except every 10th minute) yields exactly 107,892 frames per hour, matching real-time clocks. The error would otherwise accumulate to 3.6 seconds per hour.
Q3: What is the maximum cable length for LTC at 2,400 bps?
Over balanced 110 Ω audio cable (AES3 grade), LTC can be reliably transmitted up to 300 m. Beyond that, use a TCDA or convert to AES3 embedded time code for longer runs.
Q4: Is IEC 62261 still relevant in the age of file-based workflows?
Absolutely. Time code is embedded in MXF, MOV, and MP4 containers as metadata tracks. While the physical LTC/VITC layer is less common in IT-centric workflows, the addressing scheme (HH:MM:SS:FF), drop-frame rules, and user-bit conventions remain identical.
