Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums DaVinci Resolve Another crash and burn with V10.

  • Another crash and burn with V10.

    Posted by Jake Blackstone on October 23, 2013 at 5:01 am

    I decided to give another try with V10, as I was doing an unsupervised session.
    Originally I conformed this session in V9, which I then opened for grading in V10. Upon finishing my grading I exported the new XML for the roundtrip and opened the new XML in FCP7. Unfortunately, upon opening it I saw nothing there but just two events. So, just to check, I opened the same session in V9, obviously ungraded session and upon exporting that XML I opened that project in FCP7 successfully. So, XML out of V10 doesn’t work, but the same project with V9 works fine. So now the question is how do I get this graded project into V9 for creating the XML for the roundtrip? I have the sinking feeling, that 6 hours of work is down the drain. And yes, I did try to open V10 Project in V9 and it doesn’t work, which is expected…

    Jake Blackstone replied 12 years, 6 months ago 8 Members · 14 Replies
  • 14 Replies
  • Andrei Savchuk

    October 23, 2013 at 7:06 am

    Yes. XML out in v10 is not working.

    https://icolorist.ru

  • Boris Tivchev

    October 23, 2013 at 8:52 am

    I use XML out in v10.0.0b.054(Full) all the time with no issues at all.

  • Harris Charalambous

    October 23, 2013 at 1:34 pm

    I haven’t had any luck with XML out yet in v10.

  • Mike Most

    October 23, 2013 at 2:40 pm

    If you’re outputting a Final Cut Pro X XML from Resolve, then no, it won’t work in Final Cut 7. I’m not near a machine at the moment, but I believe that the FCPX file is the default.

  • Eric Johnson

    October 23, 2013 at 4:15 pm

    Does v10 use the same naming convention as v9?

    If so, render out in v9. Generate Xml. Then reconnect to the v10 renders. Or just replace the v9 render directory with the v10 directory before opening the FCP7 XML…

    Not a great fix, but likely quicker then redoing all of the work.

    eric b johnson
    online editor | colorist | workflow
    https://vimeo.com/39073239

    Some contents or functionalities here are not available due to your cookie preferences!

    This happens because the functionality/content marked as “Vimeo framework” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

  • Eric Chase

    October 24, 2013 at 2:39 am

    for what it;s worth, I had the same problem.
    What i did to fix is delete the fist 2 or 3 edits in the DR10 edit timeline, then export the XML,
    this cleared up the glitch, and I pasted in the opening shots that were deleted after the fact.

    Hope this helps.

  • Jake Blackstone

    October 24, 2013 at 2:39 am

    I tried to open it with FCPX and it still no go.

  • Jake Blackstone

    October 24, 2013 at 2:44 am

    From what I can see in the new XML, Resolve 10 writes original .MXF names instead of new QT .mov names. I could do the find and replace, but frankly I had enough, I’m just going to re-do it in 9.

  • Boris Tivchev

    October 24, 2013 at 9:47 am

    Thought I’d try this…

    Opened a v9 project with Alexa files in v10. Rendered out the graded shots using “Final Cut Pro XML Round-Trip”. Exported “XML Files”. Import to FCP7 – Perfect!

  • Michael Stirling

    October 24, 2013 at 12:39 pm

    Export all stills from 10 and load into 9 with their drx.

    That will give you your grades just need to reapply shot by shot and redo the tracking – might at least drop the recreation time down to an hour or 2.

    M

Page 1 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy