-
Convert Premiere XML to Davinci compatible XML, without Final Cut?
Hi again guys!
I have been ripping my hair off trying to figure out my workflow, and it is killing me that Resolve cannot understand XML files from Premiere.
I know I can import the XML files to Final Cut and then export new XML files from Final Cut, but this is quite time consuming when you have 50 XML files to roundtrip through Final Cut for one client. I need flow in the workflow, it is all about trying to get rid of timeconsuming intermediate steps.
Isn´t there a easier way, with a XML converter that works?
I mean it can´t be that difficult to convert from a older version of XML to a newer version. Even the dead old software formally knows as Final Cut can do it. 😉 -
9 Replies
-
Maybe you can take a look at XML repair from Digital Rebellion? Didn’t have a chance to play with it but from what I understand it may convert XML between PP and FCP format.
https://www.digitalrebellion.com/promaintenance/
Cheers,
M -
Thanks for the suggestion! I will contact them and ask if it can convert to a newer version of XML. From their webpage it just states that it can convert to older versions, for backwards compability:
“can convert XML files to different XMEML versions for compatibility with earlier versions of Final Cut Pro. ”
The interesting question is if it can convert to newer versions, for future-compability (or whatever you´d call it). I will check with them and get back to the forum with their response.
-
I assume using the export final cut xml from premiere doesnt’ work? worst case davinci also works with the AAF option i think too.
-
No, exporting XML from Premiere does not work, because Premiere is using XML version 4, and Resolve only wants to read XML version 5.
By the way, I got a response and it is possible with the XML repair tool, but sadly not in batch-mode (this is planned for a future update). Still searching for a batch-tool, as we will have over hundred XML files to convert on a daily basis, and converting manually file by file would obviously be bad for the workflow… 🙁
-
Kent,
i know Adobe is aware of the issue, and from what i last read, they’re working on it.
Any reason you don’t/can’t use the AAF option out of premiere? I don’t think you would need to have it reference MXF files. (so the extra DNxHD plugin might not be required).
I wonder if Clip Finder would change it for you..
https://www.daun.ch/hamingja/ -
Hmm, when I tested AAF earlier it didn´t work, but back then I had some settings in Resolve incorrect too, something about the timecodestuff. I will make another test with AAF and see how it goes, now that those settings are correct.
I know Adobe is aware of the problem, the problem is that they are not likely to answer any questions regarding if this will be fixed within the next days, weeks, or after six months. And I´d need a solution sooner than six months, so…
-
Kent, I recieved an email from Hans (maker of Clip finder) he asks,
“has anybody tried just changing the version number at the top of the XML file before importing into Resolve?”
almost too easy if it works
-
Yesss!
Exported AAF actually works, but I cannot export audio within the AAF because the audio is stretched (constant speed change at 31.99% over the whole timeline). And stretched audio is not AAF compatible.
But because Resolve is cannot export audio this is “not a problem” at this point. Because I wouldn´t get audio from Resolve anyway. It´s not a bug, it´s a feature…
Thanks, now I actually believe I can start working with Premiere and Resolve with a pretty good workflow! Bye bye Final Cut, for good! 🙂
-
I don´t know if anyone has tried that… But now I found out that AAF works, and as long as Resolve won´t export audio I think I will stick to AAF. When Resolve supports exporting with embedded audio, the I will pick up the XML-fight again. 🙂
Reply to this Discussion! Login or Sign Up