Filmic Tone Mapping Questions

Started by
9 comments, last by Hodgman 10 years, 3 months ago

Indeed the graph has been very helpful. I have one (see my second screenshot in the OP), but it uses a linear scale. Do you mean that I should graph it with a log2 scale on the y-axis? Won't that look weird for values between 0-1?

The y-axis is from 0-1 and the x-axis is from 0-maxLuminance. I think MJP is suggesting to change the x-axis to be from 0-log2(maxLuminance).

e.g. here's my tone-mapper with luminance on x and final pixel value on y:

(left is 0-1, middle is 0-10, right is 0-1024 input range)

LZD2jbw.gifo0JquVJ.gif RMeEbnA.gif

Note how I need to zoom into the graph in order to see the detail at the bottom-end, and zoom out to see the detail at the top-end.

And here's the same function graphed with the x-axis changed to be logarithmic (still 0-1024 input range)

8f41SKR.gif

As you can see, the small bottom-end toe of the graph is now easily seen, along with the linear section and the top-end shoulder. It gives a better view on how the tone-mapper treats all inputs.

I don't know that I want the exposure to change that much just because a dark (or light) object moved into view. Is there a standard way of limiting the effect of the exposure control, or should I just get creative and fiddle with the formula a bit?

I'm not sure what the standard solution is to prevent your camera from having infinite sensitivity (a real camera has limits on exposure settings, or at least side-effects -- e.g. long-exposure photos introduce motion blur, or high-ISO settings increase image noise, or wide-apertures reduce the amount of depth that's in focus, etc). My solution was to give artists control over a minimum and maximum average luminosity value, which were used to clamp the actual average lum.

e.g. if the artists set the minimum-avg-lum to 0.5, but the actual measured avg-lum is 0.001, then the tone-mapper uses 0.5 as the avg-lum value.

This topic is closed to new replies.

Advertisement