Editorial Conform: Verify Media, Timing, and Timeline Exchange

Editorial conform recreates an edit against the intended source media, often in another non-linear editor or finishing system. Exporting an XML, AAF, or EDL is only one step. A usable handoff requires checking media identity, timing, picture, sound, and unsupported effects against an agreed reference. Record what passed, what changed, and what still needs repair before accepting the destination timeline.

This guide was checked against official documentation on November 5, 2026. It is a verification method, not a new cross-editor test or a compatibility guarantee. The result should be an auditable handoff record, not an assumed success because a file imported.

1. Define the Handoff Before Exporting

Agree on the source application and version, destination application and version, selected timeline, intended media, and delivery requirements. Distinguish three jobs:

• Finding a candidate shot: locating footage that might suit the edit.
• Identifying the correct media: establishing which recording, take, file version, and range the approved edit uses.
• Recreating the edit: transferring and checking the timeline, source relationships, timing, and finishing decisions.

Visual similarity helps the first job. It does not by itself prove the second or complete the third. Keep verified production identifiers and approval records separate from AI descriptions; see metadata versus semantic search.

Save a named copy of the source project and a reference export of the agreed timeline. Record the reference version and timebase. For material with speed changes, nests, multicamera choices, graphics, or unusual audio routing, identify those cases before choosing an interchange format. Avoid destructive simplification of the only source project.

2. Choose a Specific Format and Direction

“XML support” is not a complete compatibility statement. Name the dialect or version, exporter, importer, and settings. Do not rank formats as universally most complete.

Format / documented example	What the official source establishes	What still needs checking
Premiere Final Cut Pro XML export	Adobe documents a Final Cut Pro 7-style exchange and a translation-results log	Only some effects translate; inspect the log, merged-clip handling, audio adjustments, and the actual destination timeline
Final Cut Pro FCPXML	Apple documents a specialized format for exchanging library, event, project, and clip information; the export version can be selected	Confirm that the receiving application understands that FCPXML version; it is not the same dialect as Final Cut Pro 7 XML
Premiere AAF export	Adobe documents its tested Avid Media Composer and Pro Tools workflows and export options	Do not extend those tests to every AAF importer; check media linking/embedding, channel settings, and unsupported clip structures
Premiere CMX3600 EDL export	Adobe describes EDL export for a simpler sequence exchange	Verify the structure and fields the receiving application preserves; do not assume a complex project is reproduced in full

Read the current Adobe XML, AAF, and EDL instructions for the chosen route. Adobe's AAF guidance identifies merged clips as unsupported; its XML guidance describes translation limitations. These are reasons to inspect the specific sequence, not a promise that another format will preserve everything.

Apple's XML transfer guide explains choosing a version recognized by a third-party application. Renaming a file extension does not convert an interchange dialect.

Blackmagic's DaVinci Resolve 20 Editor's Guide demonstrates route-specific delivery and validation: printed pages 548–550 discuss an AAF handoff for Pro Tools with reference media, and pages 608–613 cover export checks and reimporting a timeline. This is a versioned training example, not evidence that every present-day Resolve exchange works without loss. Check the official training resources for the application version in use.

3. Use a Source-to-Destination Verification Table

Fill this table for the actual project. The right-hand column is a decision criterion, not a report that this guide performed the test.

Check	Source record	Exchange-file or export check	Destination acceptance criterion
Media identity	Source filename, production ID, take/version, original location; checksum when comparing identical copies	References identify the intended sources; record any transcodes or renamed files	Relink to the intended recording and version, not merely a similarly named or looking clip
Sequence timing	Start timecode, frame rate/timebase, duration, and expected cut positions	Record the exported sequence settings and any translation warnings	Cut points and duration match the agreed reference under the correct timebase
Source ranges	Required first/last frames and source timecode interpretation	Confirm how the selected route represents ranges and handles	Inspect frames at edit boundaries, including speed changes; do not copy rounded seconds as exact In/Out points
Picture and framing	Aspect ratio, crop/reframe, orientation, relevant color settings	Identify effects or transforms that may not translate	Compare the actual picture with the reference; rebuild or approve differences explicitly
Audio	Required tracks/channels, sync reference, sample rate, and routing	Check whether audio is linked, embedded, rendered, changed, or omitted	Listen in the destination and verify channel content and sync across the relevant duration
Complex structures	Nests, multicamera choices, transitions, titles, plugins, and retiming	Review route-specific limitations and the prepared copy	Record each preserved, rendered, rebuilt, or missing item; a successful import is insufficient
Missing media	List unavailable originals and authorized replacements	Keep the missing-media report with the package	Unresolved files stay visible; a proxy is not silently accepted as the approved master
Delivery state	Project/reference version and intended recipient	Include settings, logs, known exceptions, and file inventory	A named reviewer can reproduce the check and accepts any remaining exceptions

A checksum can establish that two files have identical bytes. A proxy and its camera original normally have different bytes, so their relationship needs a reliable mapping and visual/timing checks. Neither a filename match nor an AI similarity score establishes that mapping on its own.

4. Test a Representative Excerpt First

1. Duplicate the source project or timeline and identify a small excerpt containing the structures that matter to the delivery.
2. Export the agreed interchange file and reference media. Save the settings and any translation warnings with them.
3. Import into the actual destination version. Relink only to the intended, accessible media.
4. Check the table above, including both picture and sound. Inspect boundary frames and sections likely to expose sync or timing problems.
5. Record failures and the chosen remedy. Repeat the affected checks after a changed export setting or source preparation step.
6. Apply the verified route to the required timeline, then perform the full delivery check. A successful excerpt does not validate untested parts of the project.

Do not estimate conform time from a universal minutes-per-timeline-minute rule. Use the actual media availability, sequence complexity, failed checks, and repair work to plan the handoff. This checklist has no measured percentage of problems prevented.

5. Diagnose a Mismatch Before Changing the Media

Symptom	First things to inspect	How to record the result
Wrong take or similar-looking replacement	Production identifiers, proxy-to-original mapping, source range	Mark identity unresolved until the correct recording is established
Timing offset or drift	Source and sequence timebases, source interpretation, retiming, audio sync	Record where the discrepancy starts and whether it changes over time; do not assume every cause is variable frame rate
Missing or changed sound	Export options, linked media, channel layout, destination routing	Identify the missing track or changed behavior; a waveform alone does not replace listening
Different crop, title, transition, or effect	Export warnings, unsupported structures, destination settings	List what must be rendered, rebuilt, or explicitly accepted
Missing source	Paths, connected drives, available originals, package contents	Restore authorized source access or record a gap; cached metadata is not replacement media

Keep the original project intact while diagnosing. A new interchange file, a changed import setting, and a transcoded source are different interventions; record which one was used. Recounting clips or comparing text files can reveal differences, but matching counts alone do not prove an edit is correct.

6. Where ShotAI Fits—and What It Does Not Verify

ShotAI can help discover candidate shots in a processed footage library. Its search guide requires reviewing the source and returned range. Its similar-shot guide starts from a shot already in the library; it does not establish an external reference-frame-to-master identification workflow. A related result does not prove exact recording identity, take number, ownership, or approval.

The review and export guide documents selections of whole detected shots, separate clip exports, and simple timeline options. Precise trims belong in the destination editor. The current guide, covering version 1.2.0, records a basic FCP7 XML video handoff checked in Resolve, with omitted audio clips and a 30 fps sequence. That is a documented limitation of that check, not a new test performed for this article or a general compatibility claim.

Read privacy and connectivity before processing restricted footage: originals remain local, while derived visual and possible audio data and semantic query encoding involve cloud services. Do not infer fully offline processing or access controls from collection scope.

For an initial source-and-export check, use Export your first shot. For editorial candidate choices before handoff, use the script-to-footage candidate table. Neither replaces the destination acceptance checks in this guide.

FAQ

Is conform the same as relinking?

Relinking reconnects a project to media. Conform also requires verifying that the intended edit, source relationships, timing, picture, and sound survive the handoff. A timeline may link successfully to the wrong version.

Which is best: XML, AAF, or EDL?

There is no universal winner. Use the format and version supported by the actual source/destination route, then check the structures and media your project needs. FCPXML and Final Cut Pro 7 XML are distinct dialects.

Does a successful import prove a lossless transfer?

No. Check warnings, source identity, frame boundaries, audio, effects, and the reference comparison. Mark unresolved differences rather than treating an import-complete message as acceptance.

Can visual search identify the exact master when metadata is missing?

It may help find candidates, but visual similarity is not proof of recording identity. Establish the source with verified production records and source checks. This article does not demonstrate automatic master identification or measured time savings.

Sources

• Adobe Premiere: Export a project as a Final Cut Pro XML file.
• Adobe Premiere: Export AAF files.
• Adobe Premiere: Export a project as an EDL file.
• Apple Final Cut Pro: Use XML to transfer projects.
• Blackmagic Design: DaVinci Resolve 20 Editor's Guide, printed pages 548–550 and 608–613; a versioned training reference.
• ShotAI: Search, similar shots, review and export, and privacy.

Published by ShotAI. Author: Sandy, Seeknetic founder. Drafting, factual checks, and translation consistency review were AI-assisted; no personal review by Sandy or human product-team review is claimed. Official documentation was checked November 5, 2026. No new product or cross-editor test was performed for this update.