Premiere, Resolve, or Final Cut: Getting AI Selects Into Your NLE Without Re-Cutting

Finding the moments is half the job. The other half is getting them onto a timeline without retyping timecodes. Every editing app speaks a different interchange dialect, and the differences decide whether your selects arrive as a usable rough cut or a list of numbers.

This is a field guide to the three formats Doza Assist exports, what each one carries into Final Cut Pro, Premiere Pro, and DaVinci Resolve, and what gets lost along the way.

The three formats at a glance

Doza Assist has an "Edit in" selector in the project header. Pick your platform once and every export button in the project switches to the right format. The choice persists per project and sets the default for new ones.

Final Cut Pro: FCPXML

This is the richest path. The export writes a pre-cut timeline where each select is an actual edit referencing your source media, plus keyword ranges on the source clip so you can filter the browser by select label, plus chapter markers for navigation. Import it and you have an Event with the media and a Project with the clips in order.

If the footage came in as a multicam or synchronized clip from an FCPXML export, use the FCPXML Round-Trip section instead of the plain export. It preserves the original multicam container and bookmarks so selects come back with video and synced audio intact. We covered why that matters in Tuesday's post on the round-trip.

Premiere Pro: Final Cut Pro 7 XML

Premiere doesn't read FCPXML. What it reads well is the older Final Cut Pro 7 XML format, which Adobe still recommends for third-party round-tripping. Doza Assist writes xmeml version 5 with integer frame timing, the rounded timebase (24, 25, 30) and the NTSC flag set for fractional rates like 23.976 and 29.97, exactly the way FCP7 itself produced it. Premiere has accepted that for years.

Import via File, then Import, and the selects land on V1 with A1 and A2. File references use absolute paths, so keep the media where it was when you transcribed, or relink once on import.

What you lose: keyword ranges and marker styles don't survive, because the format has no equivalent. Clip names do.

DaVinci Resolve: CMX 3600 EDL

EDL is the oldest format of the three and the most universal. It's plain text. Resolve rebuilds cuts cleanly from it as long as the source media is in the project bin and the reel name matches. Import via File, Import, Timeline, then Pre-Conformed EDL.

Doza Assist writes clip names and editorial notes as comment lines, so the context survives in a readable form even though EDL has no field for it. The format's limits are real, though: no multicam relationships, no color labels, and reel names are truncated to 32 characters. The app surfaces each of those as a warning at export time rather than silently dropping data.

Which to pick when you have a choice

If you're platform-agnostic, Final Cut's FCPXML carries the most. If you live in Premiere, the FCP7 XML path is solid and has been for a decade. If you're in Resolve, EDL works, and the tradeoff is that you'll re-apply labels by hand.

Whichever you use, the clips arrive in story order. Story Builder's one-click export puts a full sequence on the timeline, ordered the way the story was assembled, ready to refine. That's the point: the AI's job ends where your cut begins.

Chris Cardoza is a documentary filmmaker and the creator of Doza Assist. All three exporters are open source in Doza Assist Core.

Common questions