|

樓主 |
發表於 2019-9-6 19:21:54
|
顯示全部樓層
http://madshi.net/madVRhdrMeasure87.zip
Changes:
1) The Highlight Recovery bug reported by Neo-XP should be fixed (I hope).
2) The "apply target nits selection" feature has been modified a bit. The "no compression limit" and "max target nits" options are gone (hard coded to 0 and 10000 now), replaced by a new "use alternative FALL Knee algo" checkbox and a new "FALL threshold" control.
"FALL threshold" basically is a nits number which is substracted from FALL measurements, before calculating the final target nits value. The purpose of this option is that we probably don't want the dynamic target algo to darken the image if the measured FALL values are rather low. So by setting a specific "FALL threshold" number, you can tell madVR to only start increasing the target nits value if the measured FALL value exceeds a certain value. If you keep the default value of 0, the algo should behave mostly the same way as the previous build (which some slight modifications). If you use a value higher than 0, that will tend to make the image a bit brighter overall. So you may want to increase the dynamic tuning value a bit, to counter that effect (if you want).
"use alternative FALL Knee algo" was suggested by Soulnight and is available in this latest tool (see the other thread). I thought it was an interesting idea, so you can now try it with the live algo, as well. This algo will make some different decisions compared to the default FALL algo. I suppose that by choosing carefully tuned "FALL threshold" and "dynamic tuning" values it should be possible to make both the new "FALL Knee" algo and the old default FALL algo behave identical on average (while being sometimes slightly brighter or darker than the other algo), but I didn't have the time to find proper values for that. So I'll leave that to you guys.
|
|