Why markers land an hour away from the intended shot
Broadcasters and post facilities commonly use sequences or masters that begin at 01:00:00:00, while web review files may begin at zero. A reviewer sees 00:12:18:10, but the matching editorial frame may be 01:12:18:10. Both timecodes can be internally correct and still refer to different clocks.
Frame rate and drop-frame notation matter too. An hour-shaped error points to a start offset; drift that increases over time can indicate a timebase or drop-frame mismatch and should not be treated as a simple offset.
Use a batch offset instead of editing every note
The Add notes page reports the detected format, note count, and timing warnings before Premiere changes. MarkerBuddy then accepts a signed HH:MM:SS:FF offset in Review. Each change is recalculated from the preserved original note timecodes instead of stacking on the previous offset. A missing, invalid, or out-of-range timecode remains visible in source order for correction or exclusion.
For a repeated delivery workflow, save the offset with the rest of the Review options as a preset. Keep Add original note timecode to comment enabled when the team needs the source timecode for traceability.
Verify the correction before committing
Review shows Total, Included, Ready, and Attention counts before the notes in source order. Check a note near the beginning, one in the middle, and one near the end. If all three positions match after the same shift, the offset is probably correct. If the first matches but the last drifts, use Back to Notes and verify the source and sequence frame rates.
Use All, Needs attention, Ready, and Excluded filters or Review next issue to find missing, invalid, or out-of-range timing. Choose Merge two notes only when two comments belong together. Its compact instruction card wraps without stretching across Review, and each high-contrast Select for merge control appears at the far left of the note header before Include. Selected controls change to Merge note n; after two selections the remaining controls become visibly locked. The selection is separate from Include, previews comments in source order, asks which timecode to retain when both notes are timed, automatically uses the only usable timecode, and requires a valid timecode when neither is timed. Cancel changes nothing.
Clear any Include row that should not be created, then click Import n Markers. A zero-row selection stays disabled. Because the approved subset is one undoable batch, a mistaken sign or offset can be rolled back.
Workflow
A practical four-step process
-
01
Compare known frames
Find one unmistakable note and compare its review timecode with the matching frame in the sequence.
-
02
Calculate the difference
Subtract the review clock from the sequence clock and keep the positive or negative sign.
-
03
Enter the TC Offset
Loaded files open Review automatically; pasted notes use Review n Notes. Apply the HH:MM:SS:FF value and confirm the recalculated rows.
-
04
Approve and import
Inspect beginning, middle, and end Timecode values, use the status filters to correct or exclude unresolved notes, then click Import n Markers.
Good fit
Use this workflow for
- One-hour broadcast versus web-review start differences
- Client notes that are uniformly early or late
- Imports that need source and result timecodes recorded
- Recurring offset setups saved as presets
Important limit
What this workflow does not assume
A constant TC Offset fixes a constant difference. It does not correct cumulative drift caused by a wrong frame rate, mixed drop-frame and non-drop-frame sources, speed changes, or notes taken against a different edit.