Video summary

The History and Science of Timecode

Main summary

Key takeaways

Technology

Summary (technological history + “how it works”)

Timecode’s origins (film era)

  • Early motion picture post-production relied on editor notes and physical markings, rather than frame-accurate timecode.
  • 1919 (Eastman Kodak): introduced Edge Numbers printed as a latent image on film.
    • These serve as machine-readable location references (starting at 0 up to 99,999, repeating).
  • Workflow:
    • Editors used work prints, then matched edge numbers to return to the camera negatives to create master negatives for release prints.
  • Why it worked:
    • Film editing was tactile, so editors could identify frames visually—making Edge Numbers “good enough.”

Transition to television + tape editing (1950s)

  • 1956: Ampex introduced a practical video tape recorder (VRX-1000, later Mark IV).
    • Enabled recording broadcasts for reuse (including time-zone playback) and improved quality over kinescopes.
  • Tape editing challenges:
    • Early editing required splicing analog tape at precise frame boundaries (e.g., via vertical blanking/trimming).
    • Mistakes could cause scrambled images and require rework.
  • NBC “Edit Sync Guide” (mid/late 1950s):
    • NBC created a frame-accurate audio track using beeps/voices counting down time.
    • The sync guide was used to cue tracks captured via kinescope, then converted into an edit list for precise splicing back to the master tape.
    • Cited example: Fred Astaire Special (1958).

Electronic video editing and early timecode competition (1960s–1970s)

  • Early 1960s:
    • Ampex developed Electronic Editor (electronic tape splicing).
    • Operators had to hit record at the correct moment—described as “Punch and Pray” due to limited error correction.
  • 1963: Editec improved workflow by recording edit pulses to the tape’s cue track based on operator-marked edit points.
  • Ongoing issue:
    • Clock drift persisted; Ampex offered compensation via Amtec Compensator.
  • Competing proprietary formats:
    • EECO (Santa Ana, CA):
      • Built timing for Air Force/NASA.
      • In 1967, introduced On-Time timecode and EECO-900 editors capable of reading it.
    • Others included formats from Central Dynamics Ltd and Datatron.
  • By ~1970, compatibility problems emerged:
    • Tapes from one studio’s system were often unreadable by another → market confusion.
  • SMPTE standardization:
    • SMPTE selected a universal format in 1970, largely based on EECO On-Time (with modifications).
    • 1975: SMPTE timecode was officially approved via ANSI.
    • Claim from the talk: the core system is highly stable and still widely used (including live theater/performance synchronization).

Core technical concepts: LTC vs VITC

The video explains two main analog timecode types:

LTC (Longitudinal Time Code)

  • Encoded onto an audio track as a square-wave using Differential Manchester / biphase mark code.
    • Encoding is self-clocking (it includes both data and clock).
  • Structure (80-bit word):
    • Hours:minutes:seconds:frames (26 bits)
    • User bits (32 bits)
    • Flags/markers (6 bits)
    • Sync word (16 bits)
      • A framing-identifying pattern that includes forward/backward direction info.
  • Practical note:
    • LTC typically requires the tape to be rolling to read reliably (because it’s audio-based).

VITC (Vertical Interval Timecode)

  • Uses the same 80-bit concept, expanded to 90 bits with a checksum replacing the LTC sync word.
  • Stored in the vertical blanking interval (between video fields).
  • Advantages:
    • Doesn’t steal the audio track.
    • Better for freeze frames and slow playback.
  • Tradeoffs:
    • More prone to distortion.
    • Less reliable during fast rewind.
  • The talk also mentions derivatives (e.g., DVITC) and notes that file-based metadata timecode largely replaced these analog methods in modern workflows.

Frame rates + drift correction (NTSC drop frame)

  • SMPTE initially supported limited frame rates:
    • NTSC options like 23.976 / 29.97
    • PAL 24 / 25
  • Drift problem for NTSC 29.97:
    • Timecode can drift (example cited: ~3.6 seconds per hour), accumulating to >1 minute per day, and far more over a month.
  • Drop-frame timecode:
    • Doesn’t “drop frames” from the recorded video itself.
    • Instead, it changes how timecode counts by skipping certain frame numbers (described as similar to a “reverse leap year” concept).
  • Formatting cue:
    • Semicolons vs colons indicate drop-frame vs non-drop-frame.
  • Guidance:
    • Drop-frame is mainly needed for broadcast.
    • For web/movie work, non-drop-frame is often sufficient.
    • Editing software can switch formats as needed.

Production implementation (generator/jam sync, not “auto-sync”)

Key workflow clarification

Timecode doesn’t automatically sync devices. It syncs their clocks using a shared reference.

Genlock vs timecode

  • For subframe precision (e.g., dual-camera 3D rigs):
    • Use generation locking (genlock):
      • Black burst in SD
      • Tri-level sync in HD
  • For typical scripted production:
    • Timecode jam sync is positioned as the practical solution.

Sponsored solution (Ambient) + tutorial-like setup

  • Product mentioned: Ambient NanoLockit timecode generator (plus Lockit Toolbox software).
  • Steps described:
    1. Connect NanoLockit to a computer.
    2. Sync it to the computer clock.
    3. Select the timecode format:
      • e.g., 23.98 vs 29.97 NTSC, 25 or 24 PAL
      • consider drop-frame options
    4. Disconnect:
      • Generates timecode for ~25 hours
      • charged ~2 hours
      • USB 5V charging
    5. Jam sync multiple devices:
      • Hold the green button on one generator to sync the others.
  • Feeding devices:
    • Recorders with timecode input:
      • Connect NanoLockit via the correct adapter and set the recorder to external sync / jam internal clock.
    • Cameras without dedicated timecode input:
      • Use adapters (e.g., Lemo-to-XLR or Lemo-to-mini jack) and feed LTC as an audio source.

Post-production decoding + editing workflow (tools mentioned)

LTC decoding support

  • Avid and DaVinci Resolve can read LTC audio timecode.

Premiere-focused workflow (tutorial portion)

  • Use DaVinci Resolve (free):
    • Import clips
    • Run an option like “Update timecode from audio LTC”
    • Export back for editing
  • Alternative:
    • Manually transfer starting timecode values into Premiere.
  • Premiere workflow:
    • Sort/organize files by timecode
    • Merge video + audio using timecode as sync
    • Supports dual-system audio, including short films / multicam workflows.

Example production uses

  • Short film “Outta Sync”:
    • NanoLockit into camera audio channel while recording externally
    • Digital slate used as additional reference
  • Multicam documentary:
    • Two cameras fed with shared timecode (two NanoLockits)
  • Classical concert recording:
    • Stage mics into an offstage recorder
    • Cameras far away receive the LTC feed so stage audio and camera audio remain aligned
    • Contrasts with unreliable syncing of “nat sound”

Reviews/guides/tutorials highlighted

  • A historical walkthrough presented as an educational course.
  • Practical sections covering:
    • Choosing timecode format (NTSC/PAL, drop-frame selection)
    • Jam syncing multiple devices
    • Feeding timecode as LTC audio when cameras lack timecode inputs
    • Decoding LTC and syncing in editors (DaVinci Resolve, Avid, and Premiere workflows)

Main speakers/sources

  • John Hess (FilmmakerIQ / FilmmakerIQ.com)
  • Sponsored equipment/source: Ambient
    • NanoLockit
    • Lockit Toolbox (and related products)

Original video