Knowledge Base / IRIG and SMPTE time code: formats and compatibility

IRIG and SMPTE time code: formats and compatibility

Understand IRIG DCLS/AM and SMPTE LTC, and check waveform, frame rate and date encoding when troubleshooting time-code compatibility.

Applies to: GMR, PCIe, RC, NTDS, TCDS, LUX, NTP100
Back to search

What the receiver must recognize

Time code carries encoded time in an electrical waveform. Successful decoding requires compatible signal format, electrical input and data encoding. A matching connector alone does not establish compatibility. A time-code reader acquires time from that waveform; a generator produces it. These are separate capabilities.

IRIG: pulse-coded time and carrier modulation

IRIG is the Inter-Range Instrumentation Group family of time codes. IRIG-B uses a one-second frame with 100 bit positions carrying time-of-year information, markers and optional additional data. The IRIG letter identifies the code format; it does not by itself specify the electrical waveform or all encoded fields.

Check that the source waveform matches the receiver input. A DCLS input and an AM input are not interchangeable merely because both signals are called IRIG-B. IEEE 1344 extensions can supply year and additional status/offset information; confirm that both ends support the required encoded fields.

SMPTE LTC: time and frame numbering

SMPTE time code is used in film and broadcast systems. Linear/longitudinal time code (LTC) carries hours, minutes, seconds and frame numbers in a serial electrical signal. It also has user bits that can carry additional information such as a date under a supported encoding scheme.

Match the frame rate and drop-frame/non-drop-frame mode. Drop-frame time code skips selected frame numbers to keep numbering aligned with elapsed time at rates such as 29.97 fps; it does not discard video frames. A receiver’s support for 30 fps non-drop-frame does not establish support for 29.97 drop-frame.

Time-of-day decoding alone does not establish the calendar date. Check the supported date encoding, such as Leitch/Masterclock user bits or SMPTE 309M, at both ends.

Compatibility checks for support

NTDS/TCDS display inputs

NTDS and TCDS displays use NTP, TC or dual controllers. LUX belongs to the NTDS family. Time-code input requires a TC or dual controller; only NTP and dual controllers expose NTP/network options. See the controller reference. Confirm the supported time-code format for the installed display controller.

Related references

For current product datasheets and manuals, visit Masterclock Resources.

Article ID: KB-TC-001
KB Version: