Skip to main content
Participating Frequently
September 8, 2025

P: XML from Resolve crash Premiere when Lumetri is applied

  • September 8, 2025
  • 20 replies
  • 824 views

I'm running 25.4.1 and I am not able to import an XML from Resolve. When I try to import the file I get an error message without any details or explanation.

 

Has anyone else run into that lately?

Pinned Reply By jamieclarke

Updating Status to Fixed in Premiere version 26.0

20 replies

jamieclarke
Community Manager
Community Manager
February 17, 2026

Updating Status to Fixed in Premiere version 26.0

Participating Frequently
February 5, 2026

I tried this again today in Resolve 20.3 and Premiere 26.0 and it worked as it once did.

I exported my XML from Pr (with some temp Lumetri adjustments on the clips that I rarely remember to remove before exporting an XML), graded in Resolve, exported using the “Premiere XML” preset, then brought the new XML into Premiere and it loaded correctly. (I then deleted the temporary Lumetri adjustments that were no longer needed).

I’m back to my preferred workflow that includes handles on all my clips.

Thanks!

NoelRoss
Participating Frequently
November 9, 2025

Cannot identify any reason why some XMLs with mastered footage from Davinci Resolve cause premiere to crash immediately at import. Does not matter what format the footage is exported as. I always export prores 4444 with some handles. Sometimes the XMLs do not work to the point where I have to result to trying to color with Adobe's terrible software. Why is this happening? Why is premiere pro still buggy and using the same over 10 year old architecture when we are paying so much money for this every month? 

Participant
October 15, 2025

Hi @jamieclarke - I'm currently running into a similar issue with the latest update to Premiere. The interesting thing is, I've been able to import other XMLs from the same Resolve project, but XMLs from specific timelines out of Resolve are generating that generic error with no explanation.

 

I'm running 25.5

Joe_wpi
Inspiring
October 7, 2025

I can confirm at least on this last test that lumetri is the cause of the bug @jamieclarke
No one seems to be giving workaround instructions, so for others who are looking for workaround heres what I did that worked for me:

  1. I stripped my sequence of all lumetri effects in Premiere. You can select all and then Edit>Remove attributes, then in the popup window, deselect everything, but check off lumetri effect and select OK to remove.
  2. Then I reexported an XML and reimport it back into davinci resolve.
  3. I changed all of my color changes from "local versions" to "remote versions" in both the old and the newly imported lumetri free XML sequence, to get the color work I already did onto the reimported sequence.
  4. Then I Reexported a Premiere XML with ProRes to round trip it back into Premiere Pro and import as normal.

    Removing Lumetri effect is the only thing that has worked so far. All other tests with XML resulted in Premiere crashing.
jamieclarke
Community Manager
Community Manager
October 6, 2025

Hi @Joe_wpi - It looks like this issue occurs when Lumetri is applied in Premiere Pro before round tripping the project through Resolve and back again.

Joe_wpi
Inspiring
October 6, 2025

Still am unable to import an XML file. Crashes immidately. I gave up on this with the last project and had workaround in a bad way that took too long, but here I am again trying to meet another deadline with a totally different job and I'm stuck once again. @jamieclarke What is the work around???

 

jamieclarke
Community Manager
Community Manager
October 6, 2025

Hi @paulm65075959 - Just so I'm clear you are navigating to File > Export > Timeline and then choosing "FCP 7 XML V5 Files."?

Also, Are you using an XML from Premiere into Resolve and then XML from Resolve back to Premiere?

Participating Frequently
October 6, 2025

I'm using the standard "Premiere XML" preset in Resolve. 

jamieclarke
Community Manager
Community Manager
October 6, 2025

Hi @paulm65075959 - What XML settings are you using from Resolve?