That is just because I got "new" LCD monitor recently (for free) with lower nits peak than my other monitors/TV, and after testing it with 150 as "no compression limit", I preferred FALL algo all the way.Hey Neo, I have been working through the last 20ish pages trying to get an idea of how the settings have progressed with the builds. I was wondering on this post, "no compression limit" changed from 150 to 0 all of sudden (and still are using that value). Prior to this, you , Fer, and others were using 150. Why did you drop down to 0, was it based on something specific changing in the test builds?
And since my OLED TV is calibrated to 150 nits, I use 0 for all madVR profiles now (easier).
I don't think so, but if you have time, you can find all the answers in this thread: https://www.avsforum.com/forum/26-home-theater-computers/3040072-madvr-tool-madmeasurehdr-optimizer-measurements-dynamic-clipping-target-nits.htmlAlso is there a term definition list somewhere for the settings that are under HDR?
Best, but only for me and only for now:
The issues I still have are :
- Flashes causing big luminance adaptations (can't be fixed now, but hopefully in a future version with a "looking ahead" algo)
- Real scenes (but very few) not detected with the "subtraction of previous frame" option, because they happen just after frames with big metric1 and metric2 values.
I don't know what could be done for this one, even with the "looking ahead" algo (how to know it is a new scene after a few frames with big changes?).