Skip to main content
Known Participant
May 14, 2017
Question

Workflow with Premiere Pro and DaVinci Resolve // Xavc files with different frame rates

  • May 14, 2017
  • 3 replies
  • 4370 views

So, this is something that I've been struggling with for some time now. I've been solving this with some hefty work-arounds but time has come to find a permanent solution, hoping someone out there can be of help.

Project finished in Premiere > export XML > import XML in DaVinci > too many files not found in DaVinci

After doing some research in the web I've found that this is becoming an usual problem with many users, the most common solution seems to be conforming the footage. This is something that I would like to avoid because one of Premiere's strength is the ability to edit pretty much all native formats.

So, the question is: Is there someone out there that has found a way to make DaVinci recognize the "files not found"?

    This topic has been closed for replies.

    3 replies

    andymees@aje
    Legend
    May 15, 2017

    If the primary issue you're facing is due to format support then one solution would be to make use of Premiere's "Ingest" functionality to transcode the media you import into Premiere into a common format (ie one that's supported by Resolve).

    Legend
    May 14, 2017

    time has come to find a permanent solution

    Mine was to eliminate Premiere Pro altogether.

    Blackmagic Design: DaVinci Resolve 14

    What's new in DaVinci Resolve 14

    Inspiring
    January 14, 2018

    I have been experimenting with DaVinci Resolve 14 free version.  The one feature that is missing that Adobe Premiere has is List, View, Sort.  When I have many clips, Premiere places them in the correct order.  I do not see this feature in Resolve.

    Legend
    January 14, 2018

    Resolve can show you List or Icon view.  Sorting can also be done in either view via File Name, Timecode and a host of other parameters.

    Like Premiere Pro, Resolve is not easy to "figure out", even for someone already trained.  Do read the manual.

    R Neil Haugen
    Legend
    May 14, 2017

    Conforming is considered a standard part of the process for nearly all colorists working in Resolve when working with any NLE's imported projects. The guys at mixinglight.com have a series in their site on the conforming process of a short film shot in PrPro. There's a number of hassles ... some even caught Patrick Inhofer, a very experienced colorist, by surprise. Not because PrPro is worse than any other NLE at this, but ... just because the way the editor had done a couple things meant the options that he's been typically using in Resolve caused a real mishap with the timeline.

    By figuring out how to change his settings ... this involved some speed-ramps, some scaling of 4k media into a 1080 sequence, that sort of thing ... so that Resolve made the right guess when meeting the info in the PrPro XML, he got the project conformed. And had some comments about settings within PrPro that definitely make it easier to conform in Resolve, and some that ... didn't. And the settings in Resolve to better suit the XML that PrPro delivers.

    With the thorough comment that this is a major learning process to work with any NLE on a regular basis.

    Being a one-man shop, I thought the Direct Link to SpeedGrade was incredibly wondrous. And was rather ... disturbed ... when rather than migrate SpeedGrade forward with a needed new build, they de-linked it from PrPro 2015.3 (first of the 10.x builds) and forward ... effectively sidelining SpeedGrade. I can easily demonstrate how to do about anything that can be done with Lumetri ... including some things never imagined by the developers ... but compared to an actual grading app, it's ... limited, slow, and not suited for shot-matching. To be polite.

    If I've got much shot-matching or precise work or just need a number of HSL keys, I still use the Ntown Productions PrProBCC applet to auto-mod a PrPro 2017 project file so that Sg 2015 can "see" it as in Direct Link process ... and then auto-mod the project file back to PrPro 2017 numbers. It's a change of one (1!) character in the file header.

    That's not an option if you're using any AE comps ... those would need to be replaced with a full-media export from AE ... and for a lot of major shops, probably. It also is PC specific.

    You might consider a month of subscription to mixinglight.com just to study the about 45 minutes of the three videos Patrick Inhofer has on conforming the Giants project from PrPro into Resolve. May help you a lot.

    Neil

    Everyone's mileage always varies ...