Welcome to our community

Be a part of something great, join today!

  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Premiere CC and Davinci Resolve 12.5 workflow XML

chris ware

Well-known member
Joined
Jul 1, 2016
Messages
163
Reaction score
1
Points
18
Location
Westchester, NY
Website
www.chriswaremedia.com
Hello

I have watched many round trip workflow tutorials on working with RED r3d files. Starting in DVR, exporting a proxy, importing in Premiere Pro CC, edit, then export XML from PPro CC. Finally, import the XML back into DVR while unchecking the automatic source clip box, so you can grade the RAW footage that has been edited. This seems to be the general workflow I find from watching tutorials. However, I'm wondering if users have changed their workflow based on PP's RED native abilities?

I'm about to get my hands on my first RED camera and I'm curious, what folks are doing?

1. Start in PPro CC, then export XML, then import into DVR with clips? Then grade and export from DVR a finished product?
2. Start in DVR, to PP w a proxy, edit, export XML, import into DVR without clips, grade, export a finished product?

Is there any advantages to option 2? Perhaps editing smaller proxy files? PPro CC handles RED raw natively, not sure why I'm not seeing a tutorial that follows option 1?

Thanks for sharing your workflows and thoughts....

chris......
 
Both can work. One key is: don't change file names, make sure you keep the reel names straight, and don't have overlapping timecode. Also be aware that speed ramps are problematic -- in general, I prefer to have any speed changes baked in by the editor, although I have had cases where very simple speed changes have been translated very well in Resolve. Sizing changes can also be problematic if the editor used proxy files but full-res R3Ds are used in Resolve.

It's always a good idea to test the workflow first. Try a short (1 minute or less) segment and see how well it conforms in Resolve. If that works, then it's a safe bet a longer project will most likely work. I've yelled and complained about people using H.264 files for editing, but I just got one over the weekend and damn if it didn't go together just fine in Resolve. (I still don't like the format in terms of picture quality, but if the conform is good and the client is happy, I'm happy.)
 
Actually the "roundtrip" workflow is commonly like this: edit in a editor, grade in resolve, finish in a editor.

So you render the graded clips out of Resolve (usually with handles) and bring those to the editing/finishing system.
 
Actually the "roundtrip" workflow is commonly like this: edit in a editor, grade in resolve, finish in a editor. So you render the graded clips out of Resolve (usually with handles) and bring those to the editing/finishing system.
You can also completely finish in Resolve for the most part. I generally hand off the textless version of the projects I work on and let them add titles and final audio and render that out. But you can do that as well in Resolve to some extent.
 
Back
Top