madVR - high quality video renderer (GPU assisted)

[Asmodian]

The last time I tested it (a long time ago now) f.lux did not get along well with madVR.

[curael]

Hey guys,
I've been trying to browse and search for this issue and I sometimes find someone speaking about it but I can't find a clear answer;
I got an RTX 4070, previously had a 2080. I have an LG C2 and an Onkyo RZ70 AVR in the chain.
I got 2.1 cables and am able to set PC mode 120Hz in nVidia and get 10-bit full RGB.
How ever, when I do this, madVR no longer switches refresh rate to my set 2160p23, etc, etc, etc. I sticks to 59 or 119Hz. In custom modes when I try to test 23Hz it says the GPU driver rejected it. It's as if when I put the receiver into 8K enhanced mode and am able to get 120Hz on the desktop, all frame rate switching goes haywire inside of madVR. When I do 4K enhanced setting I can pick 60Hz 8 bit, and even then, madVR can then switch to 23 10bit in HDR mode.

But can someone explain a bit more about why going into PC mode 120Hz 4K suddenly makes madVR unwilling to switch to the correct movie framerate? I'm at a loss here. I've tried disabling FSE mode and then the refresh rate changes as expected but them I get serious stutter in the image - which is not present when I use 4K enhanced mode on the AVR and FSE and corrctly changes to 23Hz. I'd like to utilize the higher framerate in gaming and such and also have madVR actually working and switching refresh rate. But it seems like fundamentally the GPU rejects these lower Hz modes when I run in 120 PC mode. What gives?

Sorry if this has been answered but I couldn't find anything conclusive or if there's an option I can change somewhere.

I'm on Windows 10 by the way and I have been using madVR on many cards now and I've never experienced this before but it's the first time I've been running on 120Hz and chosen a "PC" option in nvidia panel as I've never been able to run more than 4K60 at 8 bit until now.

Any help or explaining would be greatly appreciated.

[Amuat]

What do you find to be a better option for softening: reduce compression artifacts or reduce random noise? And at what strength (mainly asking this regarding the former, as I think going beyond 1 for the latter is a bit too much)? And how meaningful it is to process chroma channels also?

For extra sharpness (after already using NGU sharp), do you prefer SuperRes, enhance detail, LumaSharpen or AdaptiveSharpen, or some combination? And again, at what settings (if SuperRes, do you also use it for chroma upscaling and not just for upscaling refinement)? And what about refining the image: after every 2x upscaling step or once after upscaling is complete?

[Asmodian]

SuperRes is not really meant for combination with NGU... and isn't really a sharpener.

Which sharpener is best seems to depend on the content, that is why they are all options. I like enhance detail and adaptive sharpen at low strengths with once after upscaling is complete, but it seems like everyone has their own preference.

[mark0077]

What are you guys using with madVR to switch into HDR mode of your TVs. I'm trying to use the option to 'passthrough HDR to display' and 'send HDR metadata to the display'. But it almost always looks washed out when I watch HDR content. If I press windows+alt+B I can sometimes fix it, but when madVR does switch to HDR, the TV does always shows the HDR icon so it does look to be at least telling the TV to switch to HDR mode.

I'm using an LG C1 77" and RTX 4090 with latest drivers. Even after a fresh Win 11 reinstall and uplift to the latest drivers the switch from Windows SDR mode to madVR -> HDR mode is very flaky. I don't see errors, just I can see the TV switch to HDR, but the image is crazy flat/washed out. I hope I'm not the only one seeing it. Anyone know a way to fix this? Using latest madVR beta 169.

[huhn]

yes i have this issue too but also no solution.

[e-t172]

Just keep in Windows in HDR mode permanently, so you never have to switch. There is no real downside in doing that with an LG OLED display (as opposed to some other displays which do not display SDR-in-HDR optimally).

[huhn]

but my cx is dimming this way all the time the white is way to bright and my color management system is deactivated that's all pretty big deal here.

and not forget that microsoft is literally messing everything up that is not HDR and the gamma of SDR like 1.8.

[Shark007]

Some, if not most of you, may benifit from the Microsoft supplied Windows HDR Calibration app
The above requires Windows display setting set to use HDR and a monitor already in HDR display mode

[Manni]

Re failure to switch correctly in hdr mode, this is often caused by botched settings after a gpu swap. Delete your settings.bin in the madvr folder, delete your madvr settings in the registry, run the “reset to default settings” batch file in admin mode and reenter your settings. That always solves it (as well as the key shortcuts for profiles not working) for me.

[e-t172]

Originally Posted by huhn

but my cx is dimming this way all the time the white is way to bright

You can adjust the level of SDR white in the Windows HDR settings. The TV is only dimming because you are displaying bright whites, not because it's doing so in HDR mode.

Originally Posted by huhn

and my color management system is deactivated

Windows supports color management in HDR; in fact, there is a whole new color management pipeline that is much smarter than the old stuff and can apply a matrix profile directly on the GPU output of all apps (sadly not a 3DLUT though, it seems). Unfortunately that feature requires an ICC profile with the Microsoft-specific "MHC2" tag, and I'm not aware of any tools that can produce one. Hopefully that will change over time.

(These ICC profiles do exist though - modern laptops with wide gamut displays often come bundled with them, so that sRGB apps display correctly even in wide gamut mode.)

Originally Posted by huhn

microsoft is literally messing everything up that is not HDR and the gamma of SDR like 1.8.

That's not true. I have personally measured (using a color sensor and my LG G1) Windows SDR-to-HDR conversion and found it to be quite accurate. It is true that it assumes the input is sRGB (including sRGB gamma), which makes sense since since Windows doesn't know your app is a video player. There are Windows APIs to tell Windows what the actual input colorspace is so that it can do a better job at converting to HDR, or an app could also do the conversion itself and output in HDR colorspace, but sadly madVR doesn't seem to do any of this when playing SDR content. You can work around that by measuring madVR's SDR output in Windows HDR mode and then correcting it using an SDR-only madVR 3DLUT, which is what I'm doing.

[huhn]

Originally Posted by e-t172

You can adjust the level of SDR white in the Windows HDR settings. The TV is only dimming because you are displaying bright whites, not because it's doing so in HDR mode.

does matter even 8 8 8 is pumped to visible 30

Windows supports color management in HDR; in fact, there is a whole new color management pipeline that is much smarter than the old stuff and can apply a matrix profile directly on the GPU output of all apps (sadly not a 3DLUT though, it seems). Unfortunately that feature requires an ICC profile with the Microsoft-specific "MHC2" tag, and I'm not aware of any tools that can produce one. Hopefully that will change over time.

(These ICC profiles do exist though - modern laptops with wide gamut displays often come bundled with them, so that sRGB apps display correctly even in wide gamut mode.)

my CX6 color management not windows it can't handle HDR at all.

That's not true. I have personally measured (using a color sensor and my LG G1) Windows SDR-to-HDR conversion and found it to be quite accurate. It is true that it assumes the input is sRGB (including sRGB gamma), which makes sense since since Windows doesn't know your app is a video player. There are Windows APIs to tell Windows what the actual input colorspace is so that it can do a better job at converting to HDR, or an app could also do the conversion itself and output in HDR colorspace, but sadly madVR doesn't seem to do any of this when playing SDR content. You can work around that by measuring madVR's SDR output in Windows HDR mode and then correcting it using an SDR-only madVR 3DLUT, which is what I'm doing.

that's nice for your G1 my CX falls apart.

[flobo09]

Hey all, is anyone having a weird issue with nvidia graphic cards & madVR.

It suddenly stopped working last Friday for me.

For every single video, after 2 minutes, it crashes with "exception message : Access violation at address $12b7825c in module 'nvwgf2um.dll'. Read of address $a0."

Tried rolling back madvr measure to normal madvr, tried rolling back nvidia drivers. Eventually fully reinstalled Windows in frustration but no go.

I'm using old EVR as renderor in the mean time.

[ryrynz]

Nope. Use SFC to check Windows n do a DDU.

[flobo09]

Already clean installed windows (this is an HCPC just for video playback so that was fast) so more than a DDU was already done.

Investigating a bit more, i discovered it's frequency related.

Playing video @ 60 hz display>> no crash, all work perfectly.

Playing video @ 24 hz display>> crash after 2 minutes.

That is quite strange as smooth motion isn't activated yet atm so it shouldnt be different, i'm not sure why it would do that.

[huhn]

there are two known crashes with some version and only one should still be encounterable.

so this is more likely the 113 sm bug. but that should crash immediately.
the other crash is about 15 sec into playback and has todo with the time out warning but these version should be timed out.

try the newest beta and just hope...

you can also report this bug but to be honest you are wasting your time.

[clsid]

Those issues are crashes in madvr itself. He clearly mentioned it was the nvidia driver that was crashing.

[flobo09]

It's seems to be reclock related.

I'm still using it for 24 // 23.976 fps /// 60 / 59.94 fps acceleration and the good old pal speedown / pitch correction for some older media (maybe there is a better 64 bits solution today but having done that for over 15 years on my hcpc, i was used to it).

It has always worked perfectly with your latest mpc-hc, lav & the latest madvr from here.

Apparently, something changed / broke somewhere somehow now it breaks with 24 // 23.976 fps content when reclock and madvr are activated.

Not a "big" deal in the end. Might actually be a good time for me to let it go.

[Amuat]

What might be the settings (or maybe some other cause) that seem to block deinterlacing? Even though I have enabled the "when in doubt..." option and watch VOB files, the ctrl+J info screen always shows "deinterlacing off (dxva11)".

[nevcairiel]

You are using D3D11 decoding, deinterlacing is not implemented with that combination.