|
|
樓主 |
發表於 2018-10-29 21:52:37
|
顯示全部樓層
本帖最後由 6hzzz 於 2018-10-29 09:55 PM 編輯
開啟動態映射模式
New test build:
http://madshi.net/madVRhdrMeasure24.zip
Sorry, guys, due to the bugs, you have to redo all measurements. Because of that I've now also taken the "opportunity" to modify the file format once more. I'm now storing almost all information I measure, including the measured peak and histogram for every frame. I'm currently not making use of the histogram in madVR (other than for the OSD). But having all information in the measurement file means we hopefully may not have to re-measure in the future (unless the resolution of the histogram isn't high enough for some reason).
The new measurements files get much bigger now, because I'm storing the histograms. Is that a problem for anyone?
There's a new option called "max dynamic scene adjustments". If you disable it, madVR will use an optimized but constant tone mapping curve for each scene, similar to how HDR10+ will work, and exactly the same as the previous madVR test builds behaved. If you enable the "max dynamic scene adjustments" option, madVR will dynamically adjust the tone mapping parameters within each scene in such a way, that darker time periods in each scene will be compressed less than brigher time periods. This is done in such a way that there will never ever be clipped highlights. The only possible disadvantages of this new algorithm compared to disabling it is that you might be able to see the change in tone mapping parameters. However, if you choose a relatively low % number, it should be pretty much invisible, but provide a fair brightness and pop boost, for long scenes that vary a lot in peak brightness. This new algo is something that HDR10+ will (as far as I understand it) *not* be able to do. So we may actually have a solution now which is better than HDR10+.
Of course the new algo needs serious testing to make sure there are no unexpected bugs. And we need to decide which config for the new algo is the "best". Let me know what you think!
A good scene for a quick test would be the "Mother" scene (posted earlier in this thread, IIRC) where Jennifer turns on a lamp in a dark zoom. The same scene starts at 6nits, but then goes up to almost 1,000nits, *without* a scene change. With the new option disabled, madVR tone maps the whole scene to nearly 1,000nits. With the new algo enabled, the beginning of the scene is rendered without any compression, and tone mapping then ramps up slowly (depending on the config) and smoothly, and early enough so that when the lamp is turned on, the tone mapping is already at 1,000nits, so there's zero clipped highlights.
原帖地址:
https://www.avsforum.com/forum/2 ... 3.html#post57028034
|
|
[複製連結]
狗仔卡
發表於 2017-12-4 12:45:46
