Wrestling with round-trip workflows
Roundtripping between post production software applications is complex and ever-evolving, especially as all of our software platforms get updated independently of each (and generally with little regard for competing platforms). It’s nearly impossible to generate a broad set of rules for moving timelines between different applications that work 100% of the time.
That’s exactly why I have to emphasize that everything in this insight is evolving and the recommendations found are based on the specific versions of the software utilized in the test, at this moment in time.
Throughout this series, I’ll be approaching application-specific issues and will attempt to boil them down to a simplified set of recommendations that you can follow for optimal results. If at some point in the future you follow these recommendations and the workflow breaks down, let me know in the comments! I will revisit this topic in the future on an as-needed basis.
Today, we’re deconstructing the often problematic rendering from DaVinci Resolve into Premiere Pro.
For years, colorists and editors have been complaining about shifts in contrast when importing Resolve renders into Premiere. And for years, the advice has been changing. Guess what? My advice is changing again!
A word of caution
This insight is filled with assumptions based on my current run of these workflow tests. In fact, while recording this Insight I had to completely revise my workflow advice, since recent updates to both DaVinci Resolve and Premiere Pro made that advice 100% wrong and I found a new problem!
The advantage of being in a community like Mixing Light is that we can alert each other to these changes and then update our shared documentation. Consider this Insight an update to our shared documentation!
Key takeaways from this Insight
By the end of this Insight, you should understand how:
- On MacOS, the ‘data vs. video levels’ issue between Premiere Pro and DaVinci Resolve is fixed if you select Auto for your DaVinci Resolve exports using 444 codecs.
- Important note: While this should be consistent with the Windows version, there could be slight differences between operating systems. If you find any differences, please share them in the comments section.
- There’s a new issue with 422 exports, which exhibit visible color shifts! My recommendation is: Only export 4444 media when rendering to Premiere Pro.
- This Insight currently applies to software versions:
- Premiere Pro v23.10 or later
- DaVinci Resolve 18.1.2 or later
Questions or Comments? Leave a comment!
Is this Insight useful to you? Let us know! Mixing Light is all about community discussions and we’re curious if you found this helpful, if you have something to add, or if you have more questions you need answered?
Also – if you find different results in later versions of Resolve or Premiere, please let us know in the comments! I want to keep all of us current on this very important topic.
Finally, are there roundtrip issues you’re wrestling with? Use the comments to let me know and I’ll try to address them in an Insight.
Sorry... the rest of this content is for members only. You'll need to login or Join Now to continue (we hope you do!).
Need more information about our memberships? Click to learn more.Membership options
Homepage › Forums › Update! DaVinci Resolve ‘Levels’ Setting For Premiere Pro Renders
This is the discussion thread for the Insight: Update! DaVinci Resolve ‘Levels’ Setting For Premiere Pro Renders
Log in to reply.