madVR - high quality video renderer (GPU assisted)

[SamuriHL]

It is. That driver sucks for HDR. Most of us went back to 399 until nVidia can be bothered to fix it.

[chinobino]

All working great here, thx madshi!

LG 55" 4K TV
OS HDR Enabled 12-bit YCbCr 4:2:2 using HDMI 2.0a
GTX1060 on driver 411.63 WHQL
Windows 10 x64 1803
madVR v0.92.16 in D3D11 fullscreen Windowed mode (10-bit)

I was previously using 8-bit RGB Full range (via nvidia control panel) but when I switched over to 10-bit YCbCr 4:2:2 I noticed that all banding was completely gone.

I then tested 12-bit YCbCr 4:2:2 and had no issues so I'm going to stick with it for now (my TV panel is probably 8-bit with FRC, lol) even though I'm likely not gaining anything.

I have always had madVR set to remove banding artifacts (on 'high') and dithering with DX11 but the banding comes back when output is set to 8-bit RGB.

Colour accuracy vs no banding, I'll take the no banding option.

[hajosattila]

Interesting! I try this...Thanks! :)

How many bits of native display bit depth output in madVR?

sorry for my bad english...

[el Filou]

rules for that option:
1. never higher than what you set the display output of your graphics card to (the GPU itself would then dither down instead of madVR - bad)
2. the display output bit depth of your graphics card should be set to what you know your TV accepts and doesn't process down, otherwise your TV would also dither down instead of madVR (also bad). If you don't know for sure that second information, choose 8 bit everywhere.
(Edit: some people argue that some displays have temporal dithering (FRC) as good as madVR's dithering, but I would need to see a side-by-side test to be convinced)

[mclingo]

You are still protesting a color change that was fixed by setting madVR to BT.2020? How exactly will this get this issue fixed?

I can’t understand why you are interested in this hobby when your PC breaks every month or so. I just play stuff almost every day and watch it. I don’t know why you seem to have so many issues.

You would have to narrow down the exact driver version and all of the exact settings to reproduce the issue and madshi would to have somehow reproduce the problem.

@madshi, i'm not complaining with you, neither finger pointing. i'm just wondering if maybe it's possible to fine tuning something madvr side to make HDR auto switch more reliable.

wierd, since my problems the other day where I had to reinstall MADVR to v0.92.14, KODI DS and AMD to 18.8.1 my colour sat problem has gone away.

I've checked all my settings and nothing has changed, cant work it out at all.

[famasfilms]

Just did a clean reinstall of windows 10, MPC-HC, Lav and MadVR.

Everything was working fine before - now I can only get HDR passthrough to my LG OLED in windowed mode, going full screen turns it off.

Is this because of new Nvidia drivers? I'm about to go out so don't have time to read the last few pages.

i5-6600
GTX 970
LG 950/9500 OLED

Edit* ticking automatic fullscreen exclusive mode brought back HDR in full screen

[pirlouy]

Arf, too bad. I'm about to go out too, so I don't have time to answer you.
CU !

[Warner306]

wierd, since my problems the other day where I had to reinstall MADVR to v0.92.14, KODI DS and AMD to 18.8.1 my colour sat problem has gone away.

I've checked all my settings and nothing has changed, cant work it out at all.

There would be three likely reasons why BT.2020 would fix your color problem: madVR is sending BT.2020 to the display and your display is actually configured for a BT.2020/DCI-P3 color space; madVR is sending BT.2020 to the video driver and the video driver is sending BT.709 to the display; or madVR is sending BT.709 rather than BT.2020 to the video driver.

If you check the OSD, it should report what madVR thinks it is sending.

[wolfman2791]

I'm getting an error message trying to download the last version. Anyone else having a problem?

[LigH]

an error message

Why don't you quote it exactly?

I don't have any issues downloading.

[madshi]

second My TV set has HDR feature. So i don't think i will use any feature of HDR conversion to SDR.The purpose of using the feature 'process HDR content by using pixel shader math' is to improve image quality of HDR movies.
You will either want the TV to do tone mapping or madVR. It's probably not a good idea to let both tone map. So I'd suggest to either passthrough HDR to the display untouched. Or to let madVR do the tone mapping. The latter might give you the best quality. However, if you have an OLED display, maybe you'll not get the same brightness because from what I've read the OLED might switch to some sort of "overdrive" mode to squeeze out the last bit of possible brightness, when it receives HDR content. So if you let madVR do the tone mapping, you'll lose that overdrive mode (whether that is a good or bad thing is another question).

It's like I said in my post, processing via HDR -> SDR means my TV stays in SDR mode which has a lower peak brightness than the HDR mode.
Is there no way in the TV settings to get the same peak brightness in SDR mode? That would be sad!

It also means I have to change my SDR mode picture settings on the TV for the HDR content (Bt.2020) and then back again when I'm playing SDR content (Rec.709) instead of being able to have separate SDR and HDR picture modes like I do with the passthrough option.
I understand. Does the "report BT.2020 to display" option do anything for you? Maybe it allows you to use different presets in your TV for SDR vs HDR content, even if you let madVR do the tone mapping (HDR -> SDR conversion)?

What is the "send HDR metadata to display" box for in this mode, by the way? I kind of assumed it was meant to submit the "new" HDR metadata that madVR maybe generates from using it's tonemapping algorithm to the TV. A lot of this was just my assumption that this mode was to put the TV into HDR mode.
Your assumptions are fully correct. The problem is that many TVs are stupid and apply tone mapping if they receive HDR video, even if it's not needed. E.g. if madVR tells the TV that the peak brightness is actually only 100nits, the TV would not have to do tone mapping, but most TVs still do it, which can screw up image quality.

Increasing the nits doesn't fix the super strong red hue, but they have to be that low to avoid the intense black crush that also happens with the HDR process setting. It was also set to 150 / 400 to make it easier to see the red problem in the photos.
The red hue might be a bug in madVR, I'll check if I can reproduce that here.

Playing back 720p HD mkv, run into new issue since (including) madVR version 0.92.15 (WASN'T present with 0.92.14 and reverting still works).

When I engage vobsub (idx/sub) subtitles via XySubFilter in Zoom Player, video freezes though audio continues. I don't get any subs. In fact the freezing only occurs at the point when the next sub would have appeared. It's non recoverable - have to restart player to restart video.
VobSub filter still works.
Plain text (SRT) subs still work in either sub filter.

Using AMD RX460 with Adrenalin 18.9.2 (latest) driver. Output is direct HDMI to Samsung monitor, 1920x1080 resolution.

Sub filters previously installed (as pair) via ZP Install Centre - reported as 3.1.0.747 via that installer.
VSFilter.dll (VobSub) shows 3.0.0.306
XySubFilter.dll (XySubFilter) shows 3.1.0.747
Zoom Player is MAX v14.4b1 (latest)

----

UPDATE: same issue occurs on different PC w/ same software setup, but with older AMD Radeon HD5670
(again, reverting to madVR 0.92.14 works)

UPDATE2 (2018-09-21): issue confirmed in BOTH full-screen and windowed playback
The issue occurs when the *first* subtitle would normally appear, is that correct? You're saying the "next" subtitle, which confuses me a bit.

Is there an easy way for me to reproduce the problem? I'm not sure if I want to install lots and lots of stuff and carefully fine tune everything to match your setup, just to be able to reproduce the issue... :scared:

For what it's worth: I still had the render queue not filling correctly issue with 0.92.16, it only worked in FSE. However, it seems to have disappeared after a Windows restart. Maybe you want to keep an eye out on this.

Edit: The CPU load with HDR pixel shader conversion is also a bit high, especially with highlight reconstruction.
Highlight reconstruction uses DirectCompute. Waiting for DirectCompute to complete may push one CPU core to 100%. But it's a kind of busy wait state that basically tells the OS: "I want to wait, but if you need this CPU core for something else, go ahead and do that", so it's not that one CPU core would be blocked. It can be used by the OS for any task, but it just can't go to 0% until DirectCompute has run through. So IMHO not too much of an issue.

I'm probably going to continue using HDR pass-through as that seems the only way to utilize the higher brightness levels of my LG B7. HDR to SDR looks very good now for tone-mapping, but the brightness in SDR holds it back.
It's too bad that your LG doesn't seem to have an option to use the same brightness for SDR?

I also utilize the dynamic tone-mapping on the TV to bring it closer to how it would look like in Dolby Vision. Are there any plans to add dynamic tone-mapping (if even possible) for HDR pixel processing to HDR output?
It's already there! See "measure each frame's peak luminance".

Also, I didn't notice it in the profile variables, can display bitdepth output be added as a parameter?
Which display output bitdepth exactly?

I was previously using 8-bit RGB Full range (via nvidia control panel) but when I switched over to 10-bit YCbCr 4:2:2 I noticed that all banding was completely gone.
That's weird, shouldn't be happening. 8bit RGB Full Range should be totally banding free (unless the source contains banding, obviously).

You do have dithering enabled in madVR? Have you tried setting your display properties manually to 8bit in the madVR settings?

[famasfilms]

new version of MADVR has fixed the 23,076 playback issue with MPC-HC, no longer hangs with black screen, wierd but great !

unfortunately I was hoping that maybe a combination of new AMD drivers and new MADVR would fix the blown out reds issue with AMD 23hz SDR playback, this really needs fixing, had this for months now with 3 different AMD cards and muliple sets of drivers and LAV / MADVR versions.

https://1drv.ms/u/s!AgvFafeelEBigP8JoUs9wKjRu8Ajjw


Just a reminder of the issue.

all 23,976 playback of any SDR material has blown out reds as shown in picture, but only with MADVR renderer.

• If If I turn off refresh rate switching and play in 60hz the problem goes away
• if I put my TV in PC mode the problem goes away (bluray mode used for access to TV processing)
• if I turn off use DIRECT3D for presentation in MADVR the problem goes
• if If set calibration to BT2020 in MADVR the problem goes away
• HDR material plays fine.

surely the way this problem manifests itself must ring a bell for someone?


Your PC should be in PC mode for SDR content, and Home Theatre for HDR content.

I think I mentioned this a few months ago but the other way round and you replied back then - If I watch HDR content on PC mode the colours are washed out, and very vivid (almost increased reds) in Home Theatre.

So it looks like you have the reverse problem, not sure what TV processing you need

Also not sure why you need it fixing in MadVr when by your own admission changing MadVR settings fixes it

[magic144]

The issue occurs when the *first* subtitle would normally appear, is that correct? You're saying the "next" subtitle, which confuses me a bit.

Is there an easy way for me to reproduce the problem? I'm not sure if I want to install lots and lots of stuff and carefully fine tune everything to match your setup, just to be able to reproduce the issue... :scared:


Hi madshi,

by "next", what I meant was that I can start playing a video at any point and the playback is OK UNTIL the time when the next subtitle is to be presented, then the video hangs - i.e. if I started playing from the beginning, the video would hang at the first

For environment, all I have is Win10, AMD cards (as described), Zoom Player, LAV and XySubFilter versions as described. Playback is to monitor or TV (thru receiver) via HDMI.

Settings to use XySubFilter in ZP are:
Playback->Video->Video Renderer: MadVR
Playback->Video->Subtitles->Use XySubFilter...whenever possible: CHECKED

Extra Info:
I am NOT using MadVR Full-screen Exclusive (FSE) mode (enable automatic FSE: UNCHECKED)


Original Post (https://forum.doom9.org/showthread.php?p=1852375#post1852375)
Updated to show issue found with AND without LAV HW accel engaged, and also found on Intel GPU platform too.

[blu3wh0]

It's too bad that your LG doesn't seem to have an option to use the same brightness for SDR?


Yup, I just went ahead and measured peak brightness for both SDR and HDR modes. I was completely surprised how maxing out OLED light and contrast still maintained a good default calibration, which could easily be perfected like my normal SDR setup for 120 nits. Anyway, HDR measured around 750 nits calibrated and SDR was only 413 nits per-calibration. This is significant enough that I would choose HDR all the time. I also went ahead and did a quick comparison between HDR to SDR in BT.2020 (which I'm surprised worked in SDR, although PC mode on my TV didn't like it so I had to switch to the one I use for HDR) against dynamically tone-mapped HDR, and it was pretty darn close aside from the brightness. Thinking this way, I'm surprised my TV's tone-mapping is actually pretty decent.


It's already there! See "measure each frame's peak luminance".


Great! Unfortunately, it doesn't seem like it would do much to help output in HDR since it sounds like it'll fight with the TV's dynamic tone-mapping. BTW, HDR pixel tone-mapped HDR output is broken in the latest version, the colors are too dark and red toned.


Which display output bitdepth exactly?


The video card bit depth output. I want to configure it so that if nvidia outputs 12-bit, madVR configures for 10-bit display. If nvidia outputs 8-bit, such as for 60Hz, madVR would set the display for 8-bit. Right now I'm doing it with refresh rate, but sometimes nvidia would screw up and output 8-bit at 23Hz.

[madshi]

by "next", what I meant was that I can start playing a video at any point and the playback is OK UNTIL the time when the next subtitle is to be presented, then the video hangs - i.e. if I started playing from the beginning, the video would hang at the first

For environment, all I have is Win10, AMD cards (as described), Zoom Player, LAV and XySubFilter versions as described. Playback is to monitor or TV (thru receiver) via HDMI.

Settings to use XySubFilter in ZP are:
Playback->Video->Video Renderer: MadVR
Playback->Video->Subtitles->Use XySubFilter...whenever possible: CHECKED

Extra Info:
I am NOT using MadVR Full-screen Exclusive (FSE) mode (enable automatic FSE: UNCHECKED)


Original Post (https://forum.doom9.org/showthread.php?p=1852375#post1852375)
Updated to show issue found with AND without LAV HW accel engaged, and also found on Intel GPU platform too.
Can you create a debug log for me? Please try to reproduce the problem quickly, then let it stay that way for maybe 20 seconds, then close/terminate the media player.

Also, please create 2-3 freeze reports from this situation, please (Ctrl+Alt+Shift+Break, IIRC).

Anyway, HDR measured around 750 nits calibrated and SDR was only 413 nits per-calibration.
Ouch.

Thinking this way, I'm surprised my TV's tone-mapping is actually pretty decent.
Would be interesting to stress test with specific movie/demo scenes which are known to be problematic.

The video card bit depth output. I want to configure it so that if nvidia outputs 12-bit, madVR configures for 10-bit display. If nvidia outputs 8-bit, such as for 60Hz, madVR would set the display for 8-bit. Right now I'm doing it with refresh rate, but sometimes nvidia would screw up and output 8-bit at 23Hz.
That sounds like something I should automatically do in madVR.

[madshi]

So here's a little HDR tone mapping comparison:

1) "Old" algorithm (v0.92.14).
2) "New" algorithm (v0.92.16+).
3) "Dumb" algorithm (used by many TVs).

Old (http://madVR.com/doom9/hdrComparison/batmanVsSupermanOld.png) - | - New (http://madVR.com/doom9/hdrComparison/batmanVsSuperman200.png) - | - Dumb (http://madVR.com/doom9/hdrComparison/batmanVsSupermanDumb.png) - | - Batman vs Superman (1)
Old (http://madVR.com/doom9/hdrComparison/spearOld.png) - | - New (http://madVR.com/doom9/hdrComparison/spear200.png) - | - Dumb (http://madVR.com/doom9/hdrComparison/spearDumb.png) - | - Batman vs Superman (2)
Old (http://madVR.com/doom9/hdrComparison/gobletOld.png) - | - New (http://madVR.com/doom9/hdrComparison/goblet200.png) - | - Dumb (http://madVR.com/doom9/hdrComparison/gobletDumb.png) - | - Goblet of Fire
Old (http://madVR.com/doom9/hdrComparison/phoenixOld.png) - | - New (http://madVR.com/doom9/hdrComparison/phoenix200.png) - | - Dumb (http://madVR.com/doom9/hdrComparison/phoenixDumb.png) - | - Order of the Phoenix
Old (http://madVR.com/doom9/hdrComparison/lgChessOld.png) - | - New (http://madVR.com/doom9/hdrComparison/lgChess200.png) - | - Dumb (http://madVR.com/doom9/hdrComparison/lgChessDumb.png) - | - LG Chess Demo
Old (http://madVR.com/doom9/hdrComparison/lifeOfPiOld.png) - | - New (http://madVR.com/doom9/hdrComparison/lifeOfPi200.png) - | - Dumb (http://madVR.com/doom9/hdrComparison/lifeOfPiDumb.png) - | - Life of Pi
Old (http://madVR.com/doom9/hdrComparison/lifeUntouchedOld.png) - | - New (http://madVR.com/doom9/hdrComparison/lifeUntouched200.png) - | - Dumb (http://madVR.com/doom9/hdrComparison/lifeUntouchedDumb.png) - | - Life Untouched Demo
Old (http://madVR.com/doom9/hdrComparison/madMaxOld.png) - | - New (http://madVR.com/doom9/hdrComparison/madMax200.png) - | - Dumb (http://madVR.com/doom9/hdrComparison/madMaxDumb.png) - | - Mad Max
Old (http://madVR.com/doom9/hdrComparison/pan1_old.png) - | - New (http://madVR.com/doom9/hdrComparison/pan1_200.png) - | - Dumb (http://madVR.com/doom9/hdrComparison/pan1_dumb.png) - | - Pan (1)
Old (http://madVR.com/doom9/hdrComparison/pan2_old.png) - | - New (http://madVR.com/doom9/hdrComparison/pan2_200.png) - | - Dumb (http://madVR.com/doom9/hdrComparison/pan2_dumb.png) - | - Pan (2)
Old (http://madVR.com/doom9/hdrComparison/samsungWonderland2_old.png) - | - New (http://madVR.com/doom9/hdrComparison/samsungWonderland2_200.png) - | - Dumb (http://madVR.com/doom9/hdrComparison/samsungWonderland2_dumb.png) - | - Samsung Wonderland 2 Demo
Old (http://madVR.com/doom9/hdrComparison/sonyCampOld.png) - | - New (http://madVR.com/doom9/hdrComparison/sonyCamp200.png) - | - Dumb (http://madVR.com/doom9/hdrComparison/sonyCampDumb.png) - | - Sony Camp Demo
Old (http://madVR.com/doom9/hdrComparison/whiteDressOld.png) - | - New (http://madVR.com/doom9/hdrComparison/whiteDress200.png) - | - Dumb (http://madVR.com/doom9/hdrComparison/whiteDressDumb.png) - | - White Dress Demo
Old (Gamut Clip) (http://madVR.com/doom9/hdrComparison/atomicBlondeOld_gamutClip.png) - | - Old (RGB Clip) (http://madVR.com/doom9/hdrComparison/atomicBlondeOld_rgbClip.png) - | - New (http://madVR.com/doom9/hdrComparison/atomicBlonde200.png) - | - Dumb (http://madVR.com/doom9/hdrComparison/atomicBlondeDumb.png) - | - Atomic Blonde

Furthermore, I've tried to do a comparison between the latest madVR vs mpv builds (shinchiro, 2018-09-16). To level the playing field, I've added igv's SSimDownscaler script to mpv.

Interestingly, mpv shows pretty dramatic differences, depending on whether the "compute-peak" frame luminance measurements are enabled or disabled. For your interested, I'm showing you both variants. Generally, it seems that mpv produces rather dark results, at least for the stress test scenes I like to test with. So for the comparison to make more sense, I'm including not only madVR's and mpv's default target peak values, but I'm also adding a manually selected higher target nits value for madVR which roughly matches the darker images produced by mpv.

mpv 100 nits (http://madVR.com/doom9/hdrComparison/mpv/batmanVsSupermanOff.png) - | - mpv 100 nits with measurements (http://madVR.com/doom9/hdrComparison/mpv/batmanVsSupermanOn.png) - | - madVR 200 nits (http://madVR.com/doom9/hdrComparison/batmanVsSuperman200.png) - | - madVR 2000 nits (http://madVR.com/doom9/hdrComparison/batmanVsSuperman2000.png) - | - Batman vs Superman (1)
mpv 100 nits (http://madVR.com/doom9/hdrComparison/mpv/spearOff.png) - | - mpv 100 nits with measurements (http://madVR.com/doom9/hdrComparison/mpv/spearOn.png) - | - madVR 200 nits (http://madVR.com/doom9/hdrComparison/spear200.png) - | - madVR 0450 nits (http://madVR.com/doom9/hdrComparison/spear450.png) - | - Batman vs Superman (2)
mpv 100 nits (http://madVR.com/doom9/hdrComparison/mpv/gobletOff.png) - | - mpv 100 nits with measurements (http://madVR.com/doom9/hdrComparison/mpv/gobletOn.png) - | - madVR 200 nits (http://madVR.com/doom9/hdrComparison/goblet200.png) - | - madVR 1200 nits (http://madVR.com/doom9/hdrComparison/goblet1200.png) - | - Goblet of Fire
mpv 100 nits (http://madVR.com/doom9/hdrComparison/mpv/phoenixOff.png) - | - mpv 100 nits with measurements (http://madVR.com/doom9/hdrComparison/mpv/phoenixOn.png) - | - madVR 200 nits (http://madVR.com/doom9/hdrComparison/phoenix200.png) - | - madVR 1700 nits (http://madVR.com/doom9/hdrComparison/phoenix1700.png) - | - Order of the Phoenix
mpv 100 nits (http://madVR.com/doom9/hdrComparison/mpv/lgChessOff.png) - | - mpv 100 nits with measurements (http://madVR.com/doom9/hdrComparison/mpv/lgChessOn.png) - | - madVR 200 nits (http://madVR.com/doom9/hdrComparison/lgChess200.png) - | - madVR 0350 nits (http://madVR.com/doom9/hdrComparison/lgChess350.png) - | - LG Chess Demo
mpv 100 nits (http://madVR.com/doom9/hdrComparison/mpv/lifeOfPiOff.png) - | - mpv 100 nits with measurements (http://madVR.com/doom9/hdrComparison/mpv/lifeOfPiOn.png) - | - madVR 200 nits (http://madVR.com/doom9/hdrComparison/lifeOfPi200.png) - | - madVR 0800 nits (http://madVR.com/doom9/hdrComparison/lifeOfPi800.png) - | - Life of Pi
mpv 100 nits (http://madVR.com/doom9/hdrComparison/mpv/lifeUntouchedOff.png) - | - mpv 100 nits with measurements (http://madVR.com/doom9/hdrComparison/mpv/lifeUntouchedOn.png) - | - madVR 200 nits (http://madVR.com/doom9/hdrComparison/lifeUntouched200.png) - | - madVR 0700 nits (http://madVR.com/doom9/hdrComparison/lifeUntouched700.png) - | - Life Untouched Demo
mpv 100 nits (http://madVR.com/doom9/hdrComparison/mpv/madMaxOff.png) - | - mpv 100 nits with measurements (http://madVR.com/doom9/hdrComparison/mpv/madMaxOn.png) - | - madVR 200 nits (http://madVR.com/doom9/hdrComparison/madMax200.png) - | - madVR 1200 nits (http://madVR.com/doom9/hdrComparison/madMax1200.png) - | - Mad Max
mpv 100 nits (http://madVR.com/doom9/hdrComparison/mpv/pan1_Off.png) - | - mpv 100 nits with measurements (http://madVR.com/doom9/hdrComparison/mpv/pan1_On.png) - | - madVR 200 nits (http://madVR.com/doom9/hdrComparison/pan1_200.png) - | - madVR 1200 nits (http://madVR.com/doom9/hdrComparison/pan1_1200.png) - | - Pan (1)
mpv 100 nits (http://madVR.com/doom9/hdrComparison/mpv/pan2_Off.png) - | - mpv 100 nits with measurements (http://madVR.com/doom9/hdrComparison/mpv/pan2_On.png) - | - madVR 200 nits (http://madVR.com/doom9/hdrComparison/pan2_200.png) - | - madVR 1800 nits (http://madVR.com/doom9/hdrComparison/pan2_1800.png) - | - Pan (2)
mpv 100 nits (http://madVR.com/doom9/hdrComparison/mpv/samsungWonderland2_Off.png) - | - mpv 100 nits with measurements (http://madVR.com/doom9/hdrComparison/mpv/samsungWonderland2_On.png) - | - madVR 200 nits (http://madVR.com/doom9/hdrComparison/samsungWonderland2_200.png) - | - madVR 1300 nits (http://madVR.com/doom9/hdrComparison/samsungWonderland2_1300.png) - | - Samsung Wonderland 2 Demo
mpv 100 nits (http://madVR.com/doom9/hdrComparison/mpv/sonyCampOff.png) - | - mpv 100 nits with measurements (http://madVR.com/doom9/hdrComparison/mpv/sonyCampOn.png) - | - madVR 200 nits (http://madVR.com/doom9/hdrComparison/sonyCamp200.png) - | - madVR 1100 nits (http://madVR.com/doom9/hdrComparison/sonyCamp1100.png) - | - Sony Camp Demo
mpv 100 nits (http://madVR.com/doom9/hdrComparison/mpv/whiteDressOff.png) - | - mpv 100 nits with measurements (http://madVR.com/doom9/hdrComparison/mpv/whiteDressOn.png) - | - madVR 200 nits (http://madVR.com/doom9/hdrComparison/whiteDress200.png) - | - madVR 3500 nits (http://madVR.com/doom9/hdrComparison/whiteDress3500.png) - | - White Dress Demo
mpv 100 nits (http://madVR.com/doom9/hdrComparison/mpv/atomicBlondeOff.png) - | - mpv 100 nits with measurements (http://madVR.com/doom9/hdrComparison/mpv/atomicBlondeOn.png) - | - madVR 200 nits (http://madVR.com/doom9/hdrComparison/atomicBlonde200.png) - | - madVR 0280 nits (http://madVR.com/doom9/hdrComparison/atomicBlonde280.png) - | - Atomic Blonde

I've also tried tweaking mpv to produce brighter images, by reducing the target peak, but doing so results in clipping, so I can't recommend going lower than the default 100 nits. See here:

mpv 100 nits (http://madVR.com/doom9/hdrComparison/mpv/lifeOfPiOn.png) - | - mpv 50 nits (http://madVR.com/doom9/hdrComparison/mpv/lifeOfPiOn50.png) - | - Life Of Pi

[NoTechi]

I am getting the JVC magenta bug with DVBViewer (50Hz) now. The magenta bug was supposed to be fixed by not sending HDR meta data. But I still get it even though I unchecked "send HDR meta data". I also noticed the "apply" button does not get active when toggeling the "send HDR meta data" checkbox. Could this be a bug?


Beside that I love the HDR improvements :)


NoTechi

edit
should have noted that I am on sat3 testbuild

[mclingo]

Your PC should be in PC mode for SDR content, and Home Theatre for HDR content.

I think I mentioned this a few months ago but the other way round and you replied back then - If I watch HDR content on PC mode the colours are washed out, and very vivid (almost increased reds) in Home Theatre.

So it looks like you have the reverse problem, not sure what TV processing you need

Also not sure why you need it fixing in MadVr when by your own admission changing MadVR settings fixes it

not sure whats going on with yours to be honest but mines currently working ok after a full reinstall of MADVR, AMD drivers and KODI DS.

There was no way I was going to change my HDMI mode every time I wanted to play a HDR movie though mate, I would have still gone with the calibration in MADVR.

Update your SIG with your details.

give us some idea of your full setup and processing chain and lets see if we can get to the bottom of it.

Sound to me like you dont have something setup right somewhere, if colours are washed out, HDR has always worked fine in all modes for me.

[ABDO]

So here's a little HDR tone mapping comparison:

1) "Old" algorithm (v0.92.14).
2) "New" algorithm (v0.92.16+).
3) "Dumb" algorithm (used by many TVs).


WOW, the New" algorithm do great in hightlight Area

madVR vs mpv
i really like how the over all picture in madvr looke way more pop and more live than mpv, i have play some youtube hdr video with latest madVR build, and what i can say that you have to see to believe how stuning result that madvr tone mapping do, but Looks like madvr Insists as Always when doing thing it doing it in the best way ever, This is a wonderful work at all.

[Manni]

@Madshi which settings (and which target peak) were you using for the new algo in your comparison? It looks overprocessed/oversharpened and I don't like what it does to the grain in the picture, for example in the background of the BvsS shot. That's not what I see here, but it might be because I don't use extreme values in the settings (I use balanced/low). Just curious to know which settings cause this. And thanks again for all your good work, it's been quite a journey to get here!

[madshi]

I am getting the JVC magenta bug with DVBViewer (50Hz) now. The magenta bug was supposed to be fixed by not sending HDR meta data. But I still get it even though I unchecked "send HDR meta data". I also noticed the "apply" button does not get active when toggeling the "send HDR meta data" checkbox. Could this be a bug?
My JVC doesn't show magenta, I don't know exactly what's causing it. But IIRC you can workaround it somehow, don't remember the details, though.

WOW, the New" algorithm do great in hightlight Area

i really like how the over all picture in madvr looke way more pop and more live than mpv, i have play some youtube hdr video with latest madVR build, and what i can say that you have to see to believe how stuning result that madvr tone mapping do, but Looks like madvr Insists as Always when doing thing it doing it in the best way ever, This is a wonderful work at all.
:)

@Madshi which settings (and which target peak) were you using for the new algo in your comparison? It looks overprocessed/oversharpened and I don't like what it does to the grain in the picture, for example in the background of the BvsS shot. That's not what I see here, but it might be because I don't use extreme values in the settings (I use balanced/low). Just curious to know which settings cause this. And thanks again for all your good work, it's been quite a journey to get here!
You might dislike it because it's the default value of 200nits, which is quite bright, combined with conversion to BT.709. The other settings are standard, like "balanced" color fire & explosions and "medium" highlight recovery strength.

FWIW, I believe the grain in BvsS is in the source. You'd see the same grain strength on a perfect 10,000nits display. So madVR simply faithfully reproduces it.

[Manni]

You might dislike it because it's the default value of 200nits, which is quite bright, combined with conversion to BT.709. The other settings are standard, like "balanced" color fire & explosions and "medium" highlight recovery strength.

FWIW, I believe the grain in BvsS is in the source. You'd see the same grain strength on a perfect 10,000nits display. So madVR simply faithfully reproduces it.

That makes sense, especially if you use medium recovery strength (I use low) and a 200nits target.

I know the grain is in the source (and I don't mind that), I just don't like what MadVr does to it in that instance with the new algo. If you compare the new algo with either old or dumb, you'll see what I mean. It exacerbates the grain due to perceived oversharpening/overprocessing.

Anyway, I certainly don't see this here with my settings in BT2020/DCI-P3 (balanced/low/600nits), which is what I would use for a 4000nits title like BvsS on my 100nits projector, so all is good :).

[magic144]

Can you create a debug log for me? Please try to reproduce the problem quickly, then let it stay that way for maybe 20 seconds, then close/terminate the media player.

Also, please create 2-3 freeze reports from this situation, please (Ctrl+Alt+Shift+Break, IIRC).


Hi madshi,

I sent you a PM with links to the logs I just created.

I created the freeze logs in release (NOT debug) mode.

Curiously, in debug mode, the video did not hang, but instead turned purple when the first sub was presented!! In any case I generated the debug log from that condition when it occurred.

To gather the debug log, I enabled debug mode, then started up a video in the player and toggled the subtitles until the VobSub stream was active, saw it go purple, waited about 20s then exited the player.

Let me know if you need any more info. Thanks!

[j82k]

To anyone who has an LG Oled:
In the service menu at "13. Oled" there is an option called "Module HDR". By default it's set to "normal" and if you set it to "on" it will increase SDR peak brightness, though I'm not quite sure if it reaches HDR brightness.
I don't have a meter so I can only eyeball it and I feel like it's a hint below HDR peak.

But if anyone with a meter who can can access the service menu would be willing to measure SDR peak brightness with this tweak I'd be interested in hearing the results. With this it might be beneficial to use madVR's HDR to SDR instead of passthrough.

To access the service menu you need a phone with an IR blaster and the app AnyMote.

[creativeopinion]

You will either want the TV to do tone mapping or madVR. It's probably not a good idea to let both tone map. So I'd suggest to either passthrough HDR to the display untouched. Or to let madVR do the tone mapping. The latter might give you the best quality. However, if you have an OLED display, maybe you'll not get the same brightness because from what I've read the OLED might switch to some sort of "overdrive" mode to squeeze out the last bit of possible brightness, when it receives HDR content. So if you let madVR do the tone mapping, you'll lose that overdrive mode (whether that is a good or bad thing is another question).

Being on an OLED I can confirm that setting anything higher then 120 nits produces the picture that is simply too dark and doesn't look correct at all. At 120 it looks good but my understanding is 120 is too low and not being able to set anything higher probably defeats the purpose of using it. I'm not sure about my other settings, I would say I haven't changed anything in the 'calibration tab'. I've set my OLED Light to 100 even though TV stayed in SDR mode and HDR have not been activated.

When I was comparing passthrough with convert HDR to SDR at 120 nits + are you nuts. I had the feeling both pictures are actually very similar with madVR doing it better so I wouldn't say that peak brightness in HDR vs convert HDR to SDR was that big of a difference.

If I set the nits to 300-480 or even 200-250 content is unwatchable, just too dark and it's clear from the first look this is not how the picture is supposed to look. On the other hand setting this at only 120 nits seems like too low and pointless?

[madshi]

That makes sense, especially if you use medium recovery strength (I use low) and a 200nits target.

I know the grain is in the source (and I don't mind that), I just don't like what MadVr does to it in that instance with the new algo. If you compare the new algo with either old or dumb, you'll see what I mean. It exacerbates the grain due to perceived oversharpening/overprocessing.
No, it does not. It's quite the opposite. Tone mapping compresses a very wide dynamic range into a very small range. Which means that the distance between e.g. brighter and darker grain dots in bright image sections becomes compressed, too (both mathematically and perceptionally). Practically that means that grain becomes softened through tone mapping.

The new algo simply reconstructs the original distance (on a perceptional scale) between the grain dots. There's no exacerbation, no oversharpening and no overprocessing going on here at all. You can't use a softened image (old/dumb) as a reference for how grain should be reproduced.

To sum up: The new algo does not exacerbate the grain. The old algo and dumb mode soften it.

I sent you a PM with links to the logs I just created.
Thanks, I'll have a look.

[madshi]

To anyone who has an LG Oled:
In the service menu at "13. Oled" there is an option called "Module HDR". By default it's set to "normal" and if you set it to "on" it will increase SDR peak brightness, though I'm not quite sure if it reaches HDR brightness.
Good find! :) Any OLED owners out there able to measure/test this?

If I set the nits to 300-480 or even 200-250 content is unwatchable, just too dark and it's clear from the first look this is not how the picture is supposed to look. On the other hand setting this at only 120 nits seems like too low and pointless?
In the end your eyes are the judge of what looks good to you. If madVR's tone mapped images with 120 nits look good to you, I won't object to you using that. Although, personally, I think I would consider that too bright for my taste.

Technically, UHD Blu-Ray defines exactly how bright each rendered pixel should look like, and if you choose 120 nits, you're watching the content brighter than it was meant to be watched. However, it's your right to exceed the intended brightness, if you prefer it that way. And if you have a lot of ambient light in your room, it might make sense.

[Sunset1982]

Good find! :) Any OLED owners out there able to measure/test this?


I would if my colormeter weren't broken. I have to wait until I have a new one. Then I will test it. I am also very interested in madvr's tone mapping, but haven't tied it yet with my LG C8 oled



Any ideas whats good settings to start testing with on an oled? My TV's SD mode is calibrated to 140 nits. I think I heard about a setting for deactivating the tv's tone mapping. I will search for the solution and will let you know...


@madshi:

If there's a way to deactivate the tv's tonemapping in hdr mode, would it be possible to trigger the tv's hdr mode after madvr has done it's tonemapping? Does madvr does madvr completely convert the hdr signal to a sd colorspace and sends an sdr signal?

[Manni]

No, it does not. It's quite the opposite. Tone mapping compresses a very wide dynamic range into a very small range. Which means that the distance between e.g. brighter and darker grain dots in bright image sections becomes compressed, too (both mathematically and perceptionally). Practically that means that grain becomes softened through tone mapping.

The new algo simply reconstructs the original distance (on a perceptional scale) between the grain dots. There's no exacerbation, no oversharpening and no overprocessing going on here at all. You can't use a softened image (old/dumb) as a reference for how grain should be reproduced.

To sum up: The new algo does not exacerbate the grain. The old algo and dumb mode soften it.


Thanks for the explanation and the correction. I was wondering if the old algo / dumb were softening the picture with these settings, it looks like it's the case.

Just to clarify, I'm not used to look at pictures with these settings, and as I'm familiar with all the improvements in the new algo I was surprised to see what looked like a downside as I had not noticed/experienced it before, which is why I asked about the settings used.

If the old algo/dumb do indeed soften the picture with these settings, then it's one more benefit for the new algo :)

By the way, I apologize I only pointed this out and not how great the algo is. I have little time at the moment and was only continuing the discussion we've had over the last few months in the other thread, without realizing/remembering that this was fairly new here.

I didn't point or list the many benefits of the new algo because I thought they would be obvious to anyone (not only in this very example of BvsS, but in all the other screenshots you have selected), and because I'm familiar with them after weeks and months of testing.

I thought that thanking you for all your good work would make this obvious, but in case it isn't, I'd like to clarify for anyone who wasn't following the testing done in the other thread that I'm over the moon with the new algo, and that I'm neither using "dumb" or passthrough, nor the old algo anymore, and certainly don't regret them.

Just in case anyone could misread my comment for what it wasn't. :)

Keep up the good work, and thanks again for bringing us the best HDR to SDR conversion ever!

[suanm]

I get back again to MadVR 0.92.16 version due to cropping bars.The feature is really important,especially to 1080p or 720p movies.I have to give up MadVR0.92.14 version.
Now im gonna ask all of guys which image quality is better,30HZ luma>NGU soft(high) and 60hz luma>NGU soft(high)<Bicubic 150 AR ? Thanka a lot in advance.
=======================
Cpu 8450x3 ,video card 1050
4K HDR quantum dot TV set

[suanm]

@Madshi
Thank you very much,master.I try to do as you mentioned above.

[Warner306]

I am getting the JVC magenta bug with DVBViewer (50Hz) now. The magenta bug was supposed to be fixed by not sending HDR meta data. But I still get it even though I unchecked "send HDR meta data". I also noticed the "apply" button does not get active when toggeling the "send HDR meta data" checkbox. Could this be a bug?


Beside that I love the HDR improvements :)


NoTechi

edit
should have noted that I am on sat3 testbuild

If you think this issue is related to a stuck checkbox, you will have to reset your madVR settings. Not having an active "Apply" button does sound like this problem.

I'd first take out Notepad and copy any important madVR profile rules and save them. Then remove your settings.bin file and place it outside of the madVR installation folder. Finally, reset your madVR settings from the installation folder and see if the issue has been resolved. You can then paste your previous settings.bin back into the madVR installation folder to restore your old settings. The Notepad file is just there in case anything goes wrong.

[Warner306]

Any ideas whats good settings to start testing with on an oled? My TV's SD mode is calibrated to 140 nits. I think I heard about a setting for deactivating the tv's tone mapping. I will search for the solution and will let you know...


@madshi:

If there's a way to deactivate the tv's tonemapping in hdr mode, would it be possible to trigger the tv's hdr mode after madvr has done it's tonemapping? Does madvr does madvr completely convert the hdr signal to a sd colorspace and sends an sdr signal?

Try 400-500 nits.

You can't disable your display's tone mapping. You can disable dynamic tone mapping if it has this feature, but you can't disable the gamma (PQ) curve in the display, which is where the tone mapping occurs. You could calibrate the display with a colorimeter to follow the PQ curve as close as possible. That would be the closest to avoiding any form of tone mapping for pixels that are within the display's brightness capabilities. Even then, the display might change its curve to match the brightness of the content.

[Warner306]

Based on the photos posted, the tone mapping has improved considerably from the previous build. Some may miss some of the extra saturation, but the improved color accuracy and highlight detail makes up for it. If those images came from the recent test build, I would just put it to print and be done with it.

Those shots do make it look like saturation was slowly removed from the picture over a six month period:p Obviously, there was more to it than that. Trial-and-error is sometimes the best way to go when you don't know where you are going...

[mkl]

Playing back 720p HD mkv, run into new issue since (including) madVR version 0.92.15 (WASN'T present with 0.92.14 and reverting still works).

When I engage vobsub (idx/sub) subtitles via XySubFilter in Zoom Player, video freezes though audio continues. I don't get any subs. In fact the freezing only occurs at the point when the next sub would have appeared. It's non recoverable - have to restart player to restart video.
VobSub filter still works.
Plain text (SRT) subs still work in either sub filter.

Using AMD RX460 with Adrenalin 18.9.2 (latest) driver. Output is direct HDMI to Samsung monitor, 1920x1080 resolution.

Sub filters previously installed (as pair) via ZP Install Centre - reported as 3.1.0.747 via that installer.
VSFilter.dll (VobSub) shows 3.0.0.306
XySubFilter.dll (XySubFilter) shows 3.1.0.747
LAV Decoders 0.72.0 (video using DXVA2 copy-back)
Zoom Player is MAX v14.4b1 (latest, ZP is a 32-bit app)

----

UPDATE: same issue occurs on different PC w/ same software setup, but with older AMD Radeon HD5670
(again, reverting to madVR 0.92.14 works)
UPDATE2 (2018-09-21): issue confirmed in BOTH full-screen and windowed playback
UPDATE3 (2018-09-23): issue confirmed using LAV in BOTH (none) and DXVA2 (copy-back) acceleration (or not) modes
UPDATE4 (2018-09-23): issue confirmed on laptop w/ same software setup, but uses Intel HD GPU

I have the same issue with madvr 0.92.16 .
I'm using Windows 10, nvidia 1080ti, latest nvidia driver, Kodi DSplayer, latest LAV filters and XySubfilter.
The video plays fine until the first subtitle line should show up. It hangs before rendering the subtitle while the audio continues playing.

[magic144]

I have the same issue with madvr 0.92.16 .
I'm using Windows 10, nvidia 1080ti, latest nvidia driver, Kodi DSplayer, latest LAV filters and XySubfilter.
The video plays fine until the first subtitle line should show up. It hangs before rendering the subtitle while the audio continues playing.

Thanks for the confirmation. It's always good to know it's not just you it's happening to :)

I sent madshi a debug log and freeze reports as requested. Hopefully something will be apparent from them.

[chinobino]

That's weird, shouldn't be happening. 8bit RGB Full Range should be totally banding free (unless the source contains banding, obviously).

You do have dithering enabled in madVR? Have you tried setting your display properties manually to 8bit in the madVR settings?

Looks like the banding is in the source, x264 (AVC) 8-bit blu ray.

I guess dithering can only do so much?

[madshi]

If there's a way to deactivate the tv's tonemapping in hdr mode, would it be possible to trigger the tv's hdr mode after madvr has done it's tonemapping? Does madvr does madvr completely convert the hdr signal to a sd colorspace and sends an sdr signal?
In theory madVR's "process HDR content by using pixel shader math" should do exactly this. However, most TVs are too stupid to turn off their tone mapping, if madVR's metadata suggests that it's not needed. So it might not work as expected in real life. But I can't say for sure, without having tested such a TV myself.

(Besides, reportedly the "process HDR content" feature is currently broken. Will have to investigate.)

I'd like to clarify for anyone who wasn't following the testing done in the other thread that I'm over the moon with the new algo, and that I'm neither using "dumb" or passthrough, nor the old algo anymore, and certainly don't regret them.
Thank you, Manni! :)

I get back again to MadVR 0.92.16 version due to cropping bars.The feature is really important,especially to 1080p or 720p movies.I have to give up MadVR0.92.14 version.
Now im gonna ask all of guys which image quality is better,30HZ luma>NGU soft(high) and 60hz luma>NGU soft(high)<Bicubic 150 AR ?
I'm a bit confused. What does cropping bars have to do with selecting v0.92.16 vs v0.92.14? And how can you be "back to v0.92.16", if that's the newest build?

Not sure about your image quality question, either. Why would 60Hz contain a Bicubic downscaling step while 30Hz does not? What does refresh rate have to do with resolution or with up/downscaling?

Based on the photos posted, the tone mapping has improved considerably from the previous build. Some may miss some of the extra saturation, but the improved color accuracy and highlight detail makes up for it. If those images came from the recent test build, I would just put it to print and be done with it.

Those shots do make it look like saturation was slowly removed from the picture over a six month period:p Obviously, there was more to it than that. Trial-and-error is sometimes the best way to go when you don't know where you are going...
The screenshots are very near to what v0.92.16 would produce, with a small added tweak. But we're still testing some potential further improvements on AVSForum, so it's not time yet for a new official build.

v0.92.16 is using a different formula to calculate the final saturation compared to v0.92.14. In many cases the final saturation is a bit lower now, but in some cases, it can also be higher. Saturation is generally a very difficult parameter to dial in. Using more saturation is nice, but we have to avoid overcooked skin tones. Also, trading in some saturation for added luminance can sometimes help rendering highlights with more detail. I'm pretty happy with the algo now, in any case.

Looks like the banding is in the source, x264 (AVC) 8-bit blu ray.

I guess dithering can only do so much?
The primary purpose of dithering is not to remove banding. The primary purpose is to avoid adding new banding artifacts to the source. If you want to remove banding which is in the source, you need some sort of debanding filter. madVR has such a filter. Some TVs do, too.

I do wonder why you see the banding artifacts in RGB 8bit Full, and not in YCbCr 4:2:2, though? That doesn't make too much sense to me - unless your TV applies debanding for YCbCr 4:2:2 input, but not for RGB input?

[pirlouy]

About the screenshots comparison, I don't know anything at HDR (and I'm not really interested). In the end, the best images are the one with better contrast isn't it ?
Is it right to say it looks exactly like "dynamic contrast" options from TV ?

[Ver Greeneyes]

You might not be interested in HDR, but HDR is interested in you! Er, by that I mean that HDR is probably going to become more common as time goes on, so if you don't have an HDR display you'll need some way to display that content on an SDR display without it looking awful.

HDR basically just lets really bright things (like sunlight) be really bright. If you don't have a display that supports that kind of brightness, you need to reduce the brightness of the footage in a way that still looks natural - so you don't end up with a scene shot in daylight that looks like it was shot at night, or a scene where all the bright things are just pure white and you can't see any details. That's what madshi is currently working on.

[el Filou]

Old (http://madVR.com/doom9/hdrComparison/sonyCampOld.png) - | - New (http://madVR.com/doom9/hdrComparison/sonyCamp200.png) - | - Dumb (http://madVR.com/doom9/hdrComparison/sonyCampDumb.png) - | - Sony Camp DemoMaybe a stupid question, but I remember reading on this very forum that we shouldn't use the Sony Camp demo because its mastering metadata was rubbish.
Is there another, correctly encoded, source? Or does that not matter anymore with the newer madVR versions and it can handle material with incorrect metadata?

[mclingo]

To anyone who has an LG Oled:
I.......

not sure that would make any difference on my first gen 4k OLED EF9500 as SDR and HDR peaks are almost identical - see here.

https://www.rtings.com/tv/reviews/lg/ef9500

[j82k]

Yeah I probably should have said 2016 or newer LG Oled...

[SamuriHL]

No other way to get into the service menu? My 2018 C8 definitely treats SDR brightness different than HDR.

[ryrynz]

Maybe a stupid question, but I remember reading on this very forum that we shouldn't use the Sony Camp demo because its mastering metadata was rubbish.

I think the point is here that it clearly is far better than the other modes regardless of the source issues.

[nevcairiel]

Speaking about SDR brightness, how do you guys manage the different brightness between HDR converted to SDR, and actual SDR? Surely one doesn't want the same brightness levels there. Manually? TVs certainly don't have much automation to speak of.

[huhn]

2 hdmi connection into the TV.

i'm not aware of a TV that doesn't 2 have different settings per HDMI

[j82k]

No other way to get into the service menu? My 2018 C8 definitely treats SDR brightness different than HDR.

I have a C8 too.
As far as I know you'll need a service remote or a phone which has an IR blaster to access the service menu.
For an android phones the app is called AnyMote not sure about iphone.

I can understand why LG limited the brightness for SDR. There are more and more cases with burn-in and if people could watch CNN or whatever all day with 500+ nits they probably would...

[PirateIce]

just installed v0.92.16 and for the first time ever in full screen i can see the windows taskbar. this has never ever happened before in the 3 years i use madvr with mpc-hc.

anyone facing the same problem?
Hey I get this happening sometimes as well, on earlier versions as well, its explorer.
if you have this happen again all you have to do is open task manager and restart explorer and it is usually fixed immediately, media player can remain open during this.
you can look up otherways to restart explorer more conveniently, i recommend NOT using any of the "gracefull" commands as it sometimes stalls on closing.

[suanm]

I'm a bit confused. What does cropping bars have to do with selecting v0.92.16 vs v0.92.14? And how can you be "back to v0.92.16", if that's the newest build?

Not sure about your image quality question, either. Why would 60Hz contain a Bicubic downscaling step while 30Hz does not? What does refresh rate have to do with resolution or with up/downscalin?
Master,The cropping bars feature in madVR 0.92.14 seems not to work perfectly,i think so at least in my opinion.However the madVR0.92.16 works perfectly on my pc.So i gotta choose madVR 0.92.16 although the feature of process HDR by using pixel shader math can't work correctly on my quantum dot tv set.
Another reason why i ask masters here about 30hz and 60hz.
In 3840*2160,60hz standard
and luma>soft(high),chroma>soft(high) mode,the playback of 1080p moves drops frames.However,when i choose 3839*2160 60hz and luma>soft(high),chroma>soft(high) mode,No frames drop.
I looks up the madVR list,it displays the 3839*2160,60hz mode has been optimized by madVR.But 3840*2160,60hz is a standard mode,it's not been optimized by madVR yet.
So i guess this is why no frames drop in 3839*2160,60hz mode.Unfortunatedly,when madVR runs,luma value goes >soft(high)<Biscius 150 AR,not simplex soft(high).
When i switch to 3840*2160,30hz,chroma soft(high) and luma soft(high) mode,no frames drop yet.
So now i can't be sure which image quality is better between 3839*2160,60hz, luma>soft(high)<Biscuis 150 AR and 3840*2160,30hz,luma>soft(high).
Because i don't know if madVR makes 4:2:0 convert into 4:4:4 in 30hz mode,furthermore if luma quadrupling upscaling works correctly in the same 30hz mode.
Thank you,master,for reading my endless remarks