madVRhdrMeasure115

Ok guys, a blessed xmas to everyone! And here comes a new test build:

http://madshi.net/madVRhdrMeasure115.zip

Sadly, after trying a lot of different ideas, I've not found a well working replacement for dumb desaturation. I did find some which worked well for skin tones, but then that algo destroyed ultra bright scenes like Mad Max explosions, desaturating them nearly completely. So for now I'm officially giving up on trying to replace dumb desaturation and I'm willing to "embrace" it (as an option).

The most important change in this build is a special "split screen" mode which allows you to compare saturation at 2 different brightness levels on one display. The left side shows the image normally. The right side simulates a darker display. So the right side actually is much darker. So if you test this on a flat panel display, the right side sort of simulates a projector, so to say. Here's how to use the split screen functionality:

• ideally test this on a very bright display which is perfectly calibrated using a 3DLUT
• enter the true measured "display peak luminance" value, as usual
• activate "split screen desat test"
• pick any split screen target nits value you like, you can go as low as 20 nits
• check if the saturation levels match, subjectively
• how much (if any) dumb desat do you have to add to achieve a subjective saturation match?
  

A few more changes:

1) Hopefully fixed some of the crash issues of the previous build (?).
2) Removed all the useless "lum method" and "desat method" options.
3) Added a couple new "lum method" options. Maybe you like them?
4) Added a "don't add peak nits" option, requested by Neo-XP.

The "don't add peak nits" changes the way the DTM calculates how bright to render each scene. If you activate this option, things may get slightly brighter. You may want to increase your "dynamic target nits" option a bit to counter this effect.

2 key questions for you guys to test and answer:

A) Do you think dumb saturation is needed to achieve a saturation match when comparing a bright image with a much darker image, using the split screen? If so, how much dumb desat do you think is needed? This may vary depending on the "split screen nits target", though I hope not.

B) Can you please check if "apply desat 2" is useful at all? I think if you do activate some amount of dumb desat, then probably "apply desat 2" does not help much? At least in the Mad Max explosion, disabling "apply desat 2" looks better to my eyes. So I hope that we can get rid of "apply desat 2"? If you do want more desat, I think adding some amount of dumb desaturation might achieve a better compromise?

On a side note, here's a little comparison screenshot from a different DTM product vs madVR/Envy.

madVR - LG Colors of Journey
other - LG Colors of Journey

Some people earlier claimed that Envy would have oversaturated skin tones, compared to that other product. But in my quick test that does not seem to be the case - provided you properly brightness match both products (!). Actually, madVR seems to desaturate more than the other product, even with only "desat i 1". That applies to the lady from The Greatest Showman, as well. Unless I messed up the test somehow?

这是madvr的1.15版本？我看网上现在最新的还是0.92.17？

HuangRuixiao 发表于 2020-12-26 15:35
这是madvr的1.15版本？我看网上现在最新的还是0.92.17？

这是测试版本，稳定版最新依然是0.92.17

这版全屏后居然点不亮，又换回上一版了

bujiholic 发表于 2020-12-26 16:02
这版全屏后居然点不亮，又换回上一版了

确保使用最新版本的LAV

其它问题的化，114版本尝试在Madvr安装目录下创建名为FastBlur的空文件夹。

你们有测试最新的don't add peak nits吗？

你们对比114版本，开启don't add peak nits后DTN数值要增加多少正常？或者说就不应该开启。
我简单测试了下，画面亮度大幅度的提升，在一些场景下看上去更好（主要是更好的暗部细节）但有些场景下明显能感觉出对比度的缺失。

这玩意不优化效率就彻底完蛋了，3080跑起来也吃力，啥2077都不算个事

Beatrice-Raws 发表于 2020-12-26 22:46
这玩意不优化效率就彻底完蛋了，3080跑起来也吃力，啥2077都不算个事

算法开低点就行

这个版本HDR Blur处理耗时增加不少，画面感觉没有变化


更新：增加FastBlur文件夹以后效能和114一致了，建议没有遇到崩溃问题的可以加上

选项越来越多..萌新直接裂开