Video Timecode Conformer
Audit timecode addresses already written down for a clip or edit. Set the source and record start addresses and each side's frame rate, then compare observed record addresses to the frame-accurate mapping expected from elapsed source time. This does not edit video or create an EDL.
Key features
- Parse strict HH:MM:SS:FF non-drop and HH:MM:SS;FF drop-frame addresses
- Validate skipped 29.97 drop-frame labels at non-tenth minute boundaries
- Map source elapsed frames to record frames using exact 24000/1001 or 30000/1001 rates where selected
- Show the expected record timecode and signed frame mismatch for each supplied reference
- Distinguish a constant observed offset from varying discrepancies without assuming a cause
- Export a local CSV or JSON audit of at most 200 references
How to use
- Choose the source and record frame-rate modes, including drop-frame only for 29.97.
- Enter each side's known start timecode address.
- Paste one source,observed-record pair per line, or load the boundary example.
- Analyze and inspect expected labels, frame differences, and any invalid row.
- Export the comparison report as CSV or JSON.
Use cases
- Investigate a two-frame offset at a 29.97 drop-frame minute boundary
- Check whether copied source and record logging points share one fixed start offset
- Compare 24 fps source references to a 29.97 drop-frame record clock
- Document timing assumptions before rebuilding an edit decision list
Frequently asked questions
Does drop-frame timecode remove video frames?
No. At 29.97, labels ;00 and ;01 are skipped at the start of each minute except minutes divisible by ten. The frames remain; only their time addresses jump.
What does a positive frame difference mean?
The observed record address is that many frames later than the expected address under your selected rates and start references. It does not by itself identify whether the logger, start offset, or frame-rate assumption is wrong.
Can source and record rates differ?
Yes. Source elapsed frames are converted to elapsed physical time using the chosen rational rate, then rounded to the nearest record frame with half frames away from zero. The report records the rounding residual.
Can it import or make an EDL or inspect video files?
No. It audits pairs of timecode references that you supply. It does not parse media timecode tracks, write EDL/OTIO, rearrange clips, or prove that a video file matches these addresses.
Does a lower discrepancy prove perfect synchronization?
No. The report checks only the listed points and selected assumptions. An offset can vary between points; a constant difference is a clue, not a diagnosis. Check original metadata and playback independently.
What limits apply?
Up to 200 nonempty lines and 20,000 characters. Time addresses must be within one 24-hour day with two-digit fields. Wraparound, negative addresses, 59.94 drop-frame, field/subframe timecode and variable-frame-rate media are not supported.
Privacy
Entered timecodes stay in this browser's page state and are not uploaded or stored. Downloads are generated locally.
Comments & questions