Timecode to Frame Converter

Timecode gives every frame a unique address in the form HH:MM:SS:FF, and converting it to a frame index is ordinary base arithmetic: total frames equal the elapsed seconds multiplied by the nominal frame rate plus the frame field. At 24 fps the code 01:30:15:12 resolves to 5415 times 24 plus 12, or 129,972 frames. The frame field always counts in whole frames of the nominal integer rate, which is why a 29.97 fps recording still labels frames 0 through 29. Dividing the frame count by the true rate returns real elapsed time, and multiplying that by 48,000 or 44,100 gives the corresponding audio sample position - exactly 2000 samples per frame at 48 kHz and 24 fps, but about 1601.6 at 29.97 fps, a non-integer that has to be tracked to avoid cumulative drift. The complication is that NTSC-derived rates are not integers. Running 30-frame timecode over material at 29.97 fps makes the label fall behind the wall clock by about 3.6 seconds per hour, roughly 108 frames. Drop-frame timecode corrects this by skipping the labels 00 and 01 at the top of every minute except minutes divisible by ten, discarding 18 labels every ten minutes and holding the error to a couple of frames per hour. No picture is lost, only numbering, and the convention is to write drop-frame with semicolons and non-drop with colons. Two caveats bite in practice. There is no standard drop-frame scheme for 23.976 fps, so those projects run non-drop and accept the offset from clock time. And mixing drop and non-drop material, or crossing the 24-hour rollover at 23:59:59:29, is a common cause of sync and conform errors.

Videotape editing before timecode meant developing the tape with magnetic solution to see the control track pulses and cutting the tape physically with a razor, a method used on the Ampex quadruplex machines introduced in 1956. Electronic addressing followed: EECO and other manufacturers developed frame-addressing schemes in the mid-1960s, and the Society of Motion Picture and Television Engineers standardized the result in 1969 as SMPTE time and control code, now maintained as SMPTE ST 12. The standard defines an 80-bit word per frame carrying the hours, minutes, seconds and frames in binary-coded decimal along with user bits and a synchronizing pattern. Drop-frame exists because of a decision made for color television. When the NTSC committee added color to the monochrome system in 1953, the color subcarrier had to be interleaved without beating against the sound carrier, so the field rate was reduced by a factor of 1000/1001, turning 30 fps into 29.97 and 60 into 59.94. Timecode inherited the mismatch, and the drop-frame counting rule was devised to keep programme durations honest for broadcasters selling advertising time by the second. The code itself took several physical forms: LTC, or longitudinal timecode, recorded as an audio-band biphase signal readable while shuttling; VITC, embedded in the vertical blanking interval and readable on a still frame; and MIDI Timecode, added to the MIDI specification in 1987 to lock music sequencers to picture. File-based workflows now carry the same values as metadata in MXF and QuickTime containers.