Re: Normal / Full Range

why is it that this issue always comes up from time to time?
because its a huge fundamental issue.
Why do we have monitoring range and render range?
Why isn't what you see is what you get (i hate that phrase), but
why isn't it?

If I'm grading and displaying for P3 DCI then it should be unscaled
and so should the renders (which they are) unless you render a 422
codec. Therefore in this instance does the 422 render look like what
Im grading. No!

So why, because the 422 codec doesn't handle the headroom of the P3
colorspace.

Why doesn't Resolve take care of this correctly.

If you grade a TVC for broadcast (rec709) and monitor on a normal CRT or LCD that cant handle the headroom, then why should I be able to render a result that doesn't reflect what I'm viewing.
For example, if I render the above grade TVC out to poorer 422 and bring that file back in, it looks the same. But render that out to prorez444 RGB and we're talking a different color.

I was recently doing a dailies job, viewing on a projector and monitor config was unscaled, looked great, but rendering for offline, the images looked a little under contrast, blacks up, whites down..
NOT what you see is what I got..

This thread has gone on long enough, what do we have two options to change this setting, monitor and render (auto, unscaled or scaled)

It really is time for this to be sorted technically,
so if I'm grading for P3 display, resolve should auto correct the out put when rendering a 422 codec…or in turn have it correct when rendering a 444 or RGB codec.

Davinci Resolve Control Surface
MacPro
Cubix desktop 4
2 Red Rockets
GTX470+GTX470+GTX285
24GB RAM
HP Dreamcolor