Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • 2
    $\begingroup$ There are several problems with this approach, not the least of which is that there is a clear division between Scene Referred and Display Referred, which is lost in the node chain. Further, the arbitrary middle grey point (typically mapped to around 0.18-0.2), ends up compressed to a non-middle grey Scene Referred value here. $\endgroup$ Commented Feb 14, 2016 at 1:54
  • 4
    $\begingroup$ I don't think it's confusing - far from it, the original post is very much about the difference between scene and display colors; the main functional difference (aside from exact numbers) is using ocio configs to get a wider range, vs. using the compositor - one issue with the latter is you don't see composited colors in live lighting preview, so you have no idea what you're doing while lighting $\endgroup$ Commented May 14, 2016 at 22:51
  • 2
    $\begingroup$ Coming from a background in film I really can appreciate this answer. However "Photorealistic" isn't about film anymore (sadly)... $\endgroup$ Commented May 19, 2016 at 18:39
  • 1
    $\begingroup$ I am trying to save my rendering results in 16-bit PNG files. After loading the PNG files in Python I noticed that the highest number for all pixels is never more than 255 (8-bits). I posted a question here. I would appreciate if you can take a look and tell me if I'm doing anything wrong. I may note that I wanted to initially save my rendering results in OpenEXR but due to this issue, I cannot do this as of now. So I decided to continue with PNG to get some preliminary results until Blender people fix the OpenEXR bug. $\endgroup$ Commented Mar 31, 2018 at 1:47