Premiere Pro crashing while importing xml from Davinci Resolve

Report · Sep 09, 2023

I've been using Resolve round tripping from Premiere for a few projects and usually it works ok. But on this project the return trip to Premiere keeps causing a crash. It imports the xml from Resolve to 85 percent and then freezes. Every single time.

I've followed this process. From PP File>Export>Final Cut Pro XML

In Resolve File>Import>Timeline (seleting exported xml file)

Doing my color grading in Resolve

In Delivery panel of Resolve, I select Premiere Pro XML and render using same specs as it came from PP.

Then in PP try to import the .xml file. Always reaches 85 percent then freezes. I have to force quite PP to do anything else

I'm using PP 23.6 and Davinci Resolve 18.5 on an iMac Retina 5K 27" 2017, using OS 11.7.2.

The files being processed are Apple ProRes 422 1080p

Thanks for any ideas!?

Report · Sep 11, 2023

Send us the .xml?
Do you see the same behavior, if the media referenced from within the .xml is unavailable?

Report · Dec 22, 2023

Hey Bruce,

I've tried everything at this point even exported FCP X and use the conversion tool and it's still hanging at 73 to 75%. Projects are coming due in the next week and I really need to find a solution -can you provide any guidance here?

Report · Dec 22, 2023

[Reached out directly to Chris]

Report · Nov 07, 2023

This is happening for me, but it's stopping at 74%. Did you figure out this issue?

Report · Nov 07, 2023

We saw (while investigating the issue, as DVAPR-4247418) that there is incomplete/incorrect frame rate information in the XML, associated with some media items.

Kody, anything interesting/special about the media items referenced in the XML, which you're trying to import? Send me an example .xml if you like; I can confirm it's the same issue, previously reported.

Report · Dec 22, 2023

Hi Bruce. Having the same issue with a xml round mtripping from premiere to resolve and back. Any solution?

Report · Dec 22, 2023

Bruce,

There's been several posts on this in the BM forum, I think LGG and elsewhere. A comment that got a lot of posts one place noted that Premiere was still using the FCP7 XML format, while many other apps ... including Resolve ... were adapting or already changed to the FCP-X format.

As someone who's a blithering idiot on those types of details, I have no clue. But that might be something you could check out.

Report · Dec 22, 2023

Like the other Adobe video apps, and most industry NLEs, PPro reads and writes FCP7 XML, not FCPX XML.

For FCPX interchange with PPro, see the fine offerings from Intelligent Assistance:

https://intelligentassistance.com/

Christopher K writes:

> Any solution?

The problem with the originally provided .xml file is that the frame rate of a still image was not declared in a way conformant with the FCP7 XML spec; removing stills from the source, and/or somehow forcibly setting the frame rate of stills in the source before exporting, may avoid the problem.

Report · Dec 22, 2023

Bruce,

I saw a post elsewhere with an editor trying to reconform a project back into Premiere after colorists work, from the XML out of Resolve.

It was hanging and problematic so he opened it up "manually" to take a look, and the XML version data wasn't what he was expecting. Said the numbers matched with FCP-X, not 7.

Which got worried comments from others, especially as to what Resolve version. Which was 18.4 I think.

I haven't verified this myself but you might do a test XML out of most recent Resolve.