Timecode

Understanding Timecode

Timecode provides a universal time reference that allows multiple production systems to stay synchronized. For LED wall productions, timecode enables precise automation of video cues that would be difficult or impossible to trigger manually.

SMPTE Timecode Format

**Structure: HH:MM:SS:FF**

• Hours (00-23)
• Minutes (00-59)
• Seconds (00-59)
• Frames (varies by frame rate)

**Common Frame Rates:**

• 24fps: Film, cinema
• 25fps: PAL broadcast, European
• 29.97fps: NTSC broadcast (drop-frame/non-drop)
• 30fps: Non-broadcast video

Timecode Distribution

**LTC (Longitudinal Time Code):**

• Audio signal, usually XLR connection
• Easily routed through audio systems
• Can be recorded alongside audio
• Industry standard for live events

**MTC (MIDI Time Code):**

• MIDI-based format
• Used by DAWs and some servers
• Lower resolution than LTC
• Common in studio environments

Timecode Applications

**Concert/Touring:**

• Backing tracks include timecode
• Video cues fire at exact moments
• Lighting and automation sync
• Repeatable show night after night

**Corporate/Awards:**

• Video packages trigger on schedule
• Walk-in/walk-out music and video sync
• Teleprompter integration
• Broadcast integration

**Theater:**

• Scene-based triggering
• Complex cue sequences
• Integration with stage automation
• Precise fade timings

System Integration

**Timecode Sources:**

• Audio playback systems (QLab, Ableton)
• Video playback (media servers)
• Dedicated timecode generators
• Master clocks

**Timecode Consumers:**

• Media servers
• Lighting consoles
• Video switchers
• Automation controllers
• Camera systems

Programming Considerations

**Cueing Strategy:**

• Pre-roll time for system response
• Offset adjustments for latency
• Backup cue points
• Manual override capability

**Testing:**

• Verify timecode lock
• Test dropout recovery
• Confirm all systems sync
• Run full show tests

Troubleshooting

**Common Issues:**

• Frame rate mismatches
• Signal level problems (LTC)
• Dropout during source switching
• Cable/connection failures

**Solutions:**

• Verify consistent frame rates
• Check audio levels for LTC
• Use timecode regenerators
• Test backup procedures

Sync vs. Trigger

**Continuous Sync:** All systems reference the same running timecode for perfect synchronization throughout.

**Triggered Events:** Systems fire cues at specific timecode values but may not maintain continuous sync between triggers.

**Best Practice:** Use continuous sync for music/video and triggered events for discrete cues.