Why does frame-based feedback point to the wrong moment in my product video?

Identify which clock the reviewer used

An editor’s timeline may start at an offset, while a standalone player begins at zero. A trimmed export also has a different starting point from the source. Ask which file and clock produced the feedback. Do not assume that frame 120 means the same moment in every export.

For an illustrative label change, record that the problem appears near four seconds in the downloaded source and describe the first letter that changes. That information remains useful even when a review tool displays a different frame count.

Adobe distinguishes the original source timecode from a zero-start display and allows different frame-count bases. Record which one a comment uses. Changing a display label is different from changing the media’s playback rate; neither operation should silently redefine the evidence being reported.

Create a portable defect note

Use actual values from the file rather than copying this worksheet’s illustrative description. A screenshot can clarify the symptom but should not replace the identified source version.

Check conversion before blaming the clip

Compare the original and delivered export at the reported moment. A frame-rate conversion may repeat or interpolate frames; a trim may move the event earlier. Inspect the export settings in your external editor. This review method records timing in the actual player or external editor; it does not establish which annotation or conversion features a selected CartVisual workflow provides.

When generating a new clip, retain its own identity and quote record. Do not carry the old timecode into the replacement task as if the movement will occur at the same moment. Review the new file from its actual beginning.

Close the feedback loop

After a correction, provide a new file identifier and ask the reviewer to check the same visible relationship. Mark whether the source changed or only the export changed. If the defect is a real product mutation, smoother playback or a new frame rate does not repair its meaning.

Use source-versus-export diagnosis and actionable defect reports for the surrounding workflow. The deliverable is an unambiguous review note, not an unsupported claim of word- or frame-perfect synchronization.

Fictional fixture: source S-v1 has constant30fps and zero-based frame indices. Index120 begins at120/30=4.000 seconds from its beginning. A separate constant24fps export places index120 at5.000 seconds. Those two frame numbers alone do not identify the same instant; this arithmetic does not cover variable rates, drop-frame labels or retiming.

Keep a visual symptom with the timing. If the recipient cannot find the detaching cap in the identified file, resolve that mismatch before requesting another generation. Regeneration can change the action itself, so its timing requires a new record rather than an automatic offset. No video file was created for these examples.