Premiere to Resolve XML: takes, multicam and speed changes

The timeline opens, but a take is wrong

Before reconforming, save the received project, interchange file and an edit reference. In a project copy, mark clips that show another take, use the wrong part of a take or are offline. These are different symptoms; choose the test based on what you see. If media is missing or will not play, start with the Media Offline guide (Spanish).

If a file plays from Media Pool but remains offline in the imported timeline, compare its identifiers and timecode with those requested by the interchange. Being able to place it manually does not prove that it matches the edited passage.

For a multicamera talk or concert, record the camera angle, session, path and a recognizable frame from each affected take. Also record which playback source you used. A similar shot from another moment can go unnoticed if you only check the thumbnail. The session recording plan helps organize this material from capture onward.

Compare file name, reel and timecode before broadening the match

The Resolve 20.3 manual, February 2026, pp.1173–1174, explains that timecode must be preserved across instances of the same file. With Assist using Reel Names off, XML and AAF use file names; EDL does not use those names. With the option enabled, reel names are involved. Check the setting and the values shown in Media Pool before changing it.

Compare the timeline’s requested media with the selected original or derivative: path, file name, reel, start timecode, duration and frame rate. If two cameras have files with the same name, separate candidates into bins by camera angle and session. Do not rename files or set every timecode to zero just to clear a warning: you would lose information needed to locate the edits.

Changing reel-name extraction through Assist using Reel Names can recalculate reel names globally. Clip Attributes lets you set them per clip; record any change in the project copy and check which other clips it affects. If you do not know the correct value, preserve the discrepancy for the person who prepared the interchange.

Conform Lock: choose the clip and check the source range

For a clip that will not conform even though it is in Media Pool, Resolve 20.3, p.1179, documents Conform Lock with Media Pool Clip. In the project copy, select the correct media in the pool; it must be at least as long as the timeline clip. Then open the unconformed timeline clip’s context menu and choose the command.

The command ignores file names and reel names but uses timecode for alignment. If timecode matches, it retains the source range based on that timecode. If it does not match, it aligns the media’s first frame with the timeline clip’s first frame and retains its duration. Before accepting, compare the in point, out point and a point in the middle with the reference: picture can appear while the edit is still offset.

The Resolve 19.1 manual, February 2025, p.1076, also describes first-frame alignment when timecode does not match. Check this behavior for the installed version.

Reconform only the clips and bins that need checking

With several candidates, Reconform From Bins, Resolve 20.3, pp.1181–1184, lets you narrow the media and matching criteria. In the project copy, select the affected timeline clips and uncheck Conform Lock Enabled for that selection. Open the timeline’s menu in Media Pool: Timelines > Reconform From Bins.

Choose Selected Clips, check the state of Set clips to Conform Lock Enabled after conform and enable only the bins for that camera angle/session. Timecode is the initial criterion; add file name, reel or other verified data when it helps distinguish candidates. Review the entire dialog before clicking OK. Clips with no match remain as they were; that does not mean they are correct.

When names or reels match and timecode overlaps, Resolving Clip Conflicts, pp.1187–1189, explains how to review alternatives. Disabling Conform Lock Enabled may reveal the conflict badge; double-click it and compare paths, thumbnails and metadata before applying a candidate. Locking again can hide the warning. A resolved badge still lets you change the match and does not certify the take.

If you transcode media, prepare and verify a new interchange

Identify the capture codec, camera, converter and Premiere version. Change one variable per test: transcoding an MP4 does not guarantee corrected timecode or a successful reconform.

Adobe, Export a project as a Final Cut Pro XML file, updated January 7, 2026, instructs you to save the project with linked media, export through File > Export > Final Cut Pro XML and review FCP Translation Results alongside the XML. Only some features and effects translate; that report helps identify what to review. The documentation does not specify a Premiere build.

Transcode a sample first and keep the original. Record timecode, frame rate, duration and audio before and after; replace it only in the edit copy. Export a new interchange and compare the affected cuts. If the derivative lost or changed metadata, agree on a correction with the editor; do not change timecode throughout the session to rescue one clip.

Compare the conform with the reference and record the results

If you test another interchange format, preserve the XML and previous project. Compare shots, in/out points, voices, duration and the attributes used in the edit. Choosing AAF or EDL changes how the edit is described and conformed; a successful import alone is not acceptance. Record losses or differences and agree on the delivery with the editor.

Use the table’s checks to compare the received edit with the reference. Fill in the conform worksheet with the actual result for each passage. Include it with the recording delivery. If audio also goes to Pro Tools, use the AAF and handles guide for that workflow.

Flatten multicam in a copy and keep the editable angles

Adobe, Simplify a sequence, updated August 18, 2026, describes Sequence > Simplify Sequence. It creates another sequence; Flatten Multi-Camera clips replaces multicam with its source clips and removes the ability to switch angles in that copy. Choose only the agreed options and check the edit before exporting.

Compare the simplified copy with the original edit: cuts, selected camera angle, scale, position and audio. Flattening multicam and resolving an ordinary nested sequence are different tasks. The nesting section of the Resolve 20.3 manual, p.1158, refers to Final Cut Pro X and Final Cut Pro 7; that scope does not guarantee interchange for every Premiere nest. If picture is still missing, record the structure and affected clip.

Keep the multicam edit for later changes. For sessions recorded from several camera angles, connect this preparation with the multicamera recording plan and editor handoff.

An imported speed ramp needs the same reference and an interpolation check

Identify the Premiere and Resolve versions, operating system and files in use before comparing the ramp. Keep a reference from that same edit.

Resolve 20.3, About Speed Effects, p.1158, supports constant and variable speed changes in Premiere XML. For EDL it documents only linear speed changes; the AAF support in that section refers to Media Composer/Symphony Timewarp. Do not extend that description to every Premiere AAF. The manual notes possible differences from the reference when the interpolation method changes.

Request a video of the same edit version and check that its start timecode matches the timeline. Under Verifying Imported Timelines, pp.1161–1164, the Source Viewer’s Offline mode supports synchronized comparison. You can assign a clip with matching timecode from Media Pool and select it through Timelines > Link Offline Reference Clip. Confirm a shared sync point before assessing ramps; a reference offset can look like an edit error.

In the test copy, compare the in point, out point, duration and moment when speed changes. If those points match but motion looks different, inspect the clip under Inspector > Retime and Scaling > Retime Process, pp.1087 and 1103. Record the initial mode, change one setting at a time and inspect the same passage. Optical Flow can create artifacts where objects cross or camera movement is unpredictable; it does not by itself correct a wrong take or edit point.

The table distinguishes Resolve 20.3 interpolation methods. Compare the same passage with each setting you test, and retain the previous mode so you can restore it.

Render and Replace does not cover every nest or time remap

Adobe, Render and replace media in a sequence, updated January 7, 2026, excludes nested sequences and adjustment layers from Render and Replace. It also states that Time Remapping, Opacity, transitions between clips and audio effects are not rendered by this command. Using it does not prove that a speed ramp was baked into the file.

If the interchange does not reproduce an agreed effect, decide with the editor whether to rebuild it in Resolve or deliver a file with the result already rendered. Preserve the project and original media. For a sample, record the passage, duration, frame rate, timecode, audio and color treatment. Also check any extra frames before and after the edit needed for later adjustments.

Compare the received sample with the reference before replacing anything in the copy. Document which controls are no longer available in the derivative and where the editable sequence is kept. The multicam and speed worksheet records the agreed method, received sample and comparison result.

Mixed frame rates: check the conform method before populating Media Pool

Before generating optimized media, check which files the timeline uses and repeat the import in a copy. Do not treat optimized media as a guaranteed fix for every XML error.

The Resolve 20.3 manual, February 2026, Mixed Frame Rates, pp.1153–1154, documents Mixed frame rate format and says to choose it before importing media into the pool. For Premiere XML it specifies Resolve. The application may select a method based on the interchange; check the displayed value and timeline frame rate before importing instead of assuming the automatic choice is correct.

With a method other than None, Resolve processes sources with different frame rates for playback at the timeline rate. None ignores their original rate and plays their frames at the timeline rate, which may speed up or slow down the footage. The manual allows None for certain DPX sequences with missing or incorrect metadata; that exception is not a general fix for multicamera footage.

If the test project already contains media and you need to compare another method, preserve that copy and create a new test project with the setting chosen before import. Load a sample of the same XML and identified media, align the reference and compare take, in point, out point, duration and voice. If the difference remains, record both states; do not change original timecode to hide the offset.

Reinterpreting frame rate changes duration: distinguish it from an instance’s speed

Adobe, Change the frame rate of a clip, updated January 7, 2026, places Modify > Interpret Footage in the Project panel. Assume this frame rate changes the project’s interpretation of the clip, its duration proportionally and its audio as well. For a single timeline instance, Adobe points to Speed/Duration. Record previous values and scope before changing them; the page does not identify a specific build.

In Resolve 20.3, Clip Attributes > Video Frame Rate, pp.455–456, changing the frame rate assigned to a source changes video duration and speed while leaving audio unaffected. This differs from choosing how frames are generated or blended through Retime Process. First check the metadata and whether the editor reinterpreted the source or applied a speed change to one instance; two files listed as 25 fps may have reached that rate through different processes.

The table distinguishes each control’s scope. Compare a sample using project copies: record the file frame rate, source interpretation, instance speed, timeline rate and state in Resolve. Check picture and voice at the beginning and end as well as across cuts. Preserve originals, derivatives and the previous project so you can restore changes. Use the frame rate and interpretation worksheet alongside the editor handoff guide and multicamera recording plan.