Resolve FCPXML import fidelity #16

Closed
opened 2026-10-06 03:55:55 +00:00 by crowmaki · 1 comment
Owner

Part of #1

Question

Which FCPXML version and features does DaVinci Resolve's import honour? Cover bins/events, clip names, markers, clip notes/keywords, ratings or a "circled" flag, and linked audio. What is the best way to carry circled status and per-Take notes so they survive import?

Part of #1 ## Question Which FCPXML version and features does DaVinci Resolve's import honour? Cover bins/events, clip names, markers, clip notes/keywords, ratings or a "circled" flag, and linked audio. What is the best way to carry circled status and per-Take notes so they survive import?
Author
Owner

Resolution

Version. Resolve imports FCPXML 1.10 from Resolve 18, 1.11 from 18.6, 1.13 from 19.1.1, and FCP 12's FCPXML (1.14) from Resolve 21. Sources are the Blackmagic release notes and Apple's Final Cut Pro release notes. Emit FCPXML 1.10. Every Resolve from 18 onward reads it, and it is the newest version with a public Apple DTD we can validate against.

What survives. Blackmagic documents FCPXML import only as timeline import. The manual guarantees these:

  • cuts
  • linked clip audio, with an option to import stereo or multichannel audio as linked groups
  • still images (TIF/JPG/PNG/DPX/TGA/DNG longer than one frame)
  • transitions, speed effects, transforms and compound clips
  • referenced media is added to the Media Pool

That is enough for the Animatic.

No Blackmagic source says that FCPXML event, keyword-collection, keyword, rating, note or metadata become bins, keywords, flags or metadata. A forum report says FCPX markers do not come across. Since then, Blackmagic has added marker import for AAF and OTIO, but not for FCPXML.

Circled status and notes. Don't put them in FCPXML. Resolve has native Good Take ("good or circled take"), Comments, Keywords and Scene/Shot/Take fields, plus star ratings from Resolve 21. Fill them with a Media Pool metadata CSV: File > Import Metadata To > Media Pool matches rows by filename, and the import is safe to re-run.

Bins. Use per-Scene folders with Add Folder and SubFolders into Media Pool (Create Bins). The other documented route is FCP 7 XML Media from File import, which brings in bin hierarchy, clip markers and comments.

Clip names. Name the files 12A-3.mov. The Media Pool clip name defaults to the file name.

OTIO FCPXML adapter. It is not viable. It writes FCPXML 1.8 (old asset@src form), has no ratings and no bins, depends on ffprobe, and has been dormant since 2024. Write FCPXML 1.10 by hand instead. Another option is native .otio: the Resolve manual calls it "the most reliable" interchange, and Resolve imports OTIO clip markers.

Still open. Without a Resolve install, I could not test these. FCPXML marker, keyword, note and rating import; the exact CSV header strings; and how Good Take values are parsed. The findings file lists a short spike.

Context: branch research/resolve-fcpxml, file research/resolve-fcpxml.md.

## Resolution **Version.** Resolve imports FCPXML 1.10 from Resolve 18, 1.11 from 18.6, 1.13 from 19.1.1, and FCP 12's FCPXML (1.14) from Resolve 21. Sources are the Blackmagic release notes and Apple's *Final Cut Pro release notes*. **Emit FCPXML 1.10.** Every Resolve from 18 onward reads it, and it is the newest version with a public Apple DTD we can validate against. **What survives.** Blackmagic documents FCPXML import only as *timeline* import. The manual guarantees these: - cuts - linked clip audio, with an option to import stereo or multichannel audio as linked groups - still images (TIF/JPG/PNG/DPX/TGA/DNG longer than one frame) - transitions, speed effects, transforms and compound clips - referenced media is added to the Media Pool That is enough for the **Animatic**. No Blackmagic source says that FCPXML `event`, `keyword-collection`, `keyword`, `rating`, `note` or `metadata` become bins, keywords, flags or metadata. A forum report says FCPX markers do *not* come across. Since then, Blackmagic has added marker import for AAF and OTIO, but not for FCPXML. **Circled status and notes.** Don't put them in FCPXML. Resolve has native **Good Take** ("good or circled take"), **Comments**, **Keywords** and **Scene/Shot/Take** fields, plus star ratings from Resolve 21. Fill them with a **Media Pool metadata CSV**: *File > Import Metadata To > Media Pool* matches rows by filename, and the import is safe to re-run. **Bins.** Use per-Scene folders with *Add Folder and SubFolders into Media Pool (Create Bins)*. The other documented route is FCP 7 XML *Media from File* import, which brings in bin hierarchy, clip markers and comments. **Clip names.** Name the files `12A-3.mov`. The Media Pool clip name defaults to the file name. **OTIO FCPXML adapter.** It is not viable. It writes FCPXML 1.8 (old `asset@src` form), has no ratings and no bins, depends on `ffprobe`, and has been dormant since 2024. Write FCPXML 1.10 by hand instead. Another option is native `.otio`: the Resolve manual calls it "the most reliable" interchange, and Resolve imports OTIO clip markers. **Still open.** Without a Resolve install, I could not test these. FCPXML marker, keyword, note and rating import; the exact CSV header strings; and how Good Take values are parsed. The findings file lists a short spike. Context: branch `research/resolve-fcpxml`, file `research/resolve-fcpxml.md`.
Sign in to join this conversation.
No description provided.