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

Grade in Resolve Not Matching Render

Ty Hunt

Well-known member
Joined
Jun 20, 2017
Messages
133
Reaction score
0
Points
0
Location
US
Hey everyone!

I'm running into a strange problem, and cannot seem to find the answer anywhere.

I did my color grade in Resolve (.edl from Premiere CC) and everything looks perfect. Render it out, POOF! All of my grades are gone. The shadows are super bright, the colors are off, etc.

Not sure how to fix. Thoughts?

TECH STUFF
Camera: Scarlet-W
Color Space: RC4/RedLogFilm

Resolve Color Management: ACEScc, 1.0.2, Input Transform: RC4/RLF, Output Transform: Rec. 709

Delivering to YouTube for this particular project. Anything I missed (tech setup wise), just let me know.

Thanks!
Ty
 
Hey Ty,

I was running into a similar problem before. My issue was fixed by deselecting "Use Mac Display Color Profile." Its located in the color management section in the settings. I also found that viewing the renders in VLC rather than QuickTime displayed the colors and contrast closer to what I was seeing in Resolve.

Marcus
 
You might also want to check whether you have full or video checked in the video output settings, versus what you are viewing on. If you aren't bringing RAW footage you should also double check to see what Resolve is seeing your files as in the metadata... it tends to get a bit confused!


Chris
 
And as I always say: render out a second or two of SMPTE color bars and a grayscale ramp as part of the file, then take the rendered file and import it back into Resolve and compare it to the original using the scopes. If the scopes don't change, there is no difference. Don't try to make qualitative judgements on uncalibrated computer displays.
 
I'm glad you said it again. That is an excellent suggestion.
 
And if the test signals do change on the scopes, then and only then you have a problem, and you need to retrace the workflow and figure out why it's coming out wrong. (It's rare, but it happens.)
 
Back
Top