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 :)

Just got Avid 6, to transcode or not to transcode...

When color correcting in Resolve, none of the decisions made translate back as metadata - so correction such as power windows, blurs, secondary color correction, etc. all need to be "baked in" to the media, and this is done by rendering into the format you need for whatever downstream use you have for it. If for broadcast, then in Rec.709 color space in whatever codec format needed (in this case, DNxHD). If for theatrical, then perhaps XYZ color space and DPX, etc.

Michael

Hmm, this makes me wonder if I have been doing it wrong then... I've been just following these instructions to a T: http://www.youtube.com/watch?v=60vSLLekX6Q

THat doesn't have me do any sort of specific export from Davinci that selects a color scheme (when you pick the Avid export)...

Is there something else I should be doing? This stuff is so confusing to me, it amazes me that you guys can wrap your heads around it so easily.
 
When you pick DNxHD from Resolve, it knows it is a Rec.709 codec. But that doesn't take away from the fact that you need to mindful of that during the color correction process to stay within legal limits (waveform and vectorscope). If legal broadcast is not a deliverable, then you have more wiggle room.

Michael
 
going back to the OP question

I think a lot of power of r3d files is in them staying r3d files as long as possible through the post process. Jim says it, Reducation says it, and by not baking in a color early you leave more wiggle room, period. That being said it makes the workflow need a halfway decent computer/storage/gpu/bells/whistles

So I am going to attempt to go the AMA route myself, less storage, more coloring options, its a pretty good workflow IF it runs. Think I am going to replace my system once I start trying this since mine is long in the tooth, Am hopeful some of the newest systems out there can run a halfway decent AMA edit, I mean typically I shoot 3k or less anyway for overcranks so hoping its not a total bottle neck unplayable clusterfrack of an edit
 
I think a lot of power of r3d files is in them staying r3d files as long as possible through the post process. Jim says it, Reducation says it, and by not baking in a color early you leave more wiggle room, period. That being said it makes the workflow need a halfway decent computer/storage/gpu/bells/whistles

Yes and no. I agree that having access to the full RAW color metadata at time of color correction for the mastering process has value. But during the creative editorial process it does not. During that process, performance trumps color for me. Once creative is done, I can go back to original R3D as needed.


Michael
 
Back
Top