
In Frame.io V4 Comparison Viewer, select the left or right asset header before leaving feedback on that asset. Watching the right-hand film or discussing its defect does not establish where the comment will be attached. Check the target asset as well as the frame being discussed.
Key Takeaways
- Either compared asset can receive comments.
- Choose the intended asset header before writing feedback.
- Verify the resulting note from the target revision, not only the comparison layout.
Establish the two asset identities first
Frame.io's Comparison Viewer documentation describes comparing selected assets or versions in a Version Stack. It explicitly tells reviewers to click the appropriate asset header to ensure feedback goes to the correct asset.
Before reviewing, identify both sides by their actual asset and revision. Two films may share a title while differing in timing, crop or soundtrack. A label such as newer is unclear if someone later changes the comparison selection.
Record which revision contains the issue and what visible change is requested. The approved-version record is useful for maintaining that association after the review session ends.
Keep playback synchronization separate from comment targeting
The viewer supports linked playback and zoom controls, but coordinated viewing is not the same as choosing the comment owner. Two sides can move together while a comment still needs a specific destination.
Use this proposed review sequence:
- Open the two intended assets or stack versions.
- Read the left and right headers and confirm the expected footage.
- Move to the relevant moment and select the header of the asset needing the change.
- Write an observable instruction, identifying the revision when ambiguity remains.
- Reopen that asset independently and confirm the note appears in the expected context.
For example, a reviewer comparing two fictional wedding cuts might ask to remove a half-closed eye from the right-hand revision. The note should identify that cut and interval, not merely say fix this one. This is a proposed example, not a reported review session.
Correct an already misplaced note carefully
Preserve the original wording and version context before changing a mistaken comment. If the interface and your permissions offer a suitable correction route, use it. Otherwise add a clearly identified correction in the proper asset's discussion and explain which earlier instruction it supersedes. Do not assume Frame.io automatically transfers notes between compared files.
Avoid deleting someone else's feedback merely to tidy the page. Obtain the appropriate editorial agreement and keep the correction understandable to the editor. A response on the wrong version can otherwise create a second, conflicting instruction.
Check the time reference after the target is correct
The right asset can still have the wrong timestamp. Identify the exact cut and interval, especially when earlier shots have been lengthened. The source and sequence timecode guide explains how those references locate different things.
Finally, confirm that the reviewed file supports the decision. A small proxy may be suitable for story order but inadequate for fine image defects; use the review-copy versus master guidance to state that limit. Accept the note when the receiving editor can find the correct asset, frame and requested change without guessing from its left or right position.
Related tasks
- Which Timecode Should I Send When Requesting a Premiere Shot Revision?
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
- Should I Send a Review Copy or the Final Master of an AI Video to a Client?
Sources and scope
- Frame.io: Comparison Viewer: Frame.io V4 supports feedback on either compared asset and instructs users to click the left or right asset header to choose the comment target. Linked comparison controls do not define the comment destination.
Based on the complete official Comparison Viewer source captured October 29, 2026. No comments were posted or moved and no account was tested. The correction note and recipient checks are proposed editorial procedures. No undocumented automatic reassignment capability is claimed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.