madVR - high quality video renderer (GPU assisted)

[aquanash]

So resolution changing does not work correctly, in fact it often switches from 2160P to 1080P yet plays at 2160P when I enable such switching of refresh rates where only:
2160p23, 2160p24, 2160p25, 2160p29, 2160p30, 2160p50, 2160p59, 2160p60
are allowed.

It does not change refresh rate only resolution and then incorrectly, so this functionality seems to have been broken in Windows 11 on an Nvidia 1080TI.

ERIC

Sorry no logs, I took them, but they exceed 200K

If you have more than one device listed under madVR's device settings, please try removing all except the active one. This fixed the issue for me in Windows 11.

[KrazyLurt]

That fixed it for me as well. I now only have 2 devices in MadVR settings , and those are active. That’s my OLED TV and my reciever ( I do not use hdmi passthrough or eARC with my reciever)

[thighhighs]

No bugfixes have been released for several years. Will there be an update now? :confused:

[chros]

Probably not, no hlg passthrough either.

[mclingo]

No bugfixes have been released for several years. Will there be an update now? :confused:

Some of us still had some hope MADSHI would realease a final version V1.0 with some imporovements and bug fixes but this is looking very unlikely now, its been too long now with no contact at all from him on this thread.

There is still plenty of dev going on for HDR tonemapping but nothing else.

Sadly I think this is it for WINDOWS MADVR, its just great it still works very well for the majority of users.

[ashlar42]

Luckily I had no compelling reason to switch to Windows 11. Now I have compelling reasons not to. =D

[Virtualizer]

Luckily I had no compelling reason to switch to Windows 11. Now I have compelling reasons not to. =D

Or:
Everyone wants new Windows but nobody is willing to live with the consequences. :p

[ashlar42]

Or:
Everyone wants new Windows but nobody is willing to live with the consequences. :p
I swear I don’t want it at the moment. I have not seen anything that screamed “must have” to me.

[Siso]

Guys can anyone tell me, what "unknown format 24 bits" means in reclock, I was watching a HDR encode with madvr. I'm using madvr 0.92.17 - tone map HDR using pixel shaders, video drivers are 466.77. Lav video decoder is set to D3D11, tried and DXVA2 CB same result. https://thumbs2.imgbox.com/dc/27/SQwCDUH9_t.jpg (https://imgbox.com/SQwCDUH9) https://thumbs2.imgbox.com/d3/28/SkmDYmLm_t.png (https://imgbox.com/SkmDYmLm)

[ashlar42]

Guys can anyone tell me, what "unknown format 24 bits" means in reclock, I was watching a HDR encode with madvr. I'm using madvr 0.92.17 - tone map HDR using pixel shaders, video drivers are 466.77. Lav video decoder is set to D3D11, tried and DXVA2 CB same result. https://thumbs2.imgbox.com/dc/27/SQwCDUH9_t.jpg (https://imgbox.com/SQwCDUH9) https://thumbs2.imgbox.com/d3/28/SkmDYmLm_t.png (https://imgbox.com/SkmDYmLm)
Well, it might well be that Reclock can't "understand" HDR, since it's 30 bit and not 24?
But judging from your screen it's working with no problem, isn't it?

[Siso]

Well, it might well be that Reclock can't "understand" HDR, since it's 30 bit and not 24?
But judging from your screen it's working with no problem, isn't it?

Maybe the problem is in reclock? Otherwise I had compared the same movies in x264 and in x265 HDR, and they generally looks identical. The x264 look just a little bit darker, x265 with 100 nits look better, my monitor is calibrated to 100 nits, so I put that in madvr's target peak nits - is that ok?

[ashlar42]

Maybe the problem is in reclock? Otherwise I had compared the same movies in x264 and in x265 HDR, and they generally looks identical. The x264 look just a little bit darker, x265 with 100 nits look better, my monitor is calibrated to 100 nits, so I put that in madvr's target peak nits - is that ok?
If you have a non-HDR monitor, you need to tonemap HDR content. Are you doing that?
Have a look here: https://forum.doom9.org/showthread.php?t=171787

Reclock has no problem working with HDR content... it's an audio renderer, it could not care less about video content, as long as it can properly detect its framerate.

[egandt]

If you have more than one device listed under madVR's device settings, please try removing all except the active one. This fixed the issue for me in Windows 11.

Problem is I have 3 screens and I can not remove an active ones. Any other suggestions?

[Virtualizer]

Problem is I have 3 screens and I can not remove an active ones. Any other suggestions?

Delete the non-active ones, then restart, put it on one of the before deleted ones and delete the last one.

Just make sure that every display is at least one time deleted from the config.

[Siso]

If you have a non-HDR monitor, you need to tonemap HDR content. Are you doing that?
Have a look here: https://forum.doom9.org/showthread.php?t=171787

Reclock has no problem working with HDR content... it's an audio renderer, it could not care less about video content, as long as it can properly detect its framerate.

My monitor is not HDR, so I'm still wondering what number of nits should I write in target peak nits?

[huhn]

the one you measure with a colorimeter else you are just guessing.

[Asmodian]

Usually 100 to 200 nits looks good. 100 nits is the standard for SDR, but most monitors are higher than that. The setting is more about changing the look instead of finding the correct value anyway.

[Siso]

Usually 100 to 200 nits looks good. 100 nits is the standard for SDR, but most monitors are higher than that. The setting is more about changing the look instead of finding the correct value anyway.

I will experiment with these values.

[HillieSan]

I did a fresh install of Windows 11, madVR, LAV filters, mpc-be and nvidia drivers for the GTX 3060 Ti. So far so good. I have noticed no differences, except that Windows 11 has some cosmetic improvements over Windows 10. The problem, when I watch a non-HDR movie with mpc-be then the screen sometimes turns purple as if HDR wants to kick in, is still there. Every time I have to restart Windows to fix the problem. Is this problem madVR related?

[el Filou]

Guys can anyone tell me, what "unknown format 24 bits" means in reclock, I was watching a HDR encodeReClock reports the 'observed' number of bits, not the encoded nor displayed number of bits, e.g. for 8-bit 4:2:0 it will report 12 bits per pixel (this is not correct wrt to how the picture is sent, but it's a practical simplification). If it reports 24 bits it's probably because it's 4:2:0 10-bit that then gets padded to 16-bit, so 24 bits total.
Nothing to worry about as ashlar said.

[Siso]

ReClock reports the 'observed' number of bits, not the encoded nor displayed number of bits, e.g. for 8-bit 4:2:0 it will report 12 bits per pixel (this is not correct wrt to how the picture is sent, but it's a practical simplification). If it reports 24 bits it's probably because it's 4:2:0 10-bit that then gets padded to 16-bit, so 24 bits total.
Nothing to worry about as ashlar said.

Thanks, I thought there might be something wrong with the output of lav video decoder or the video card. :thanks:

[huhn]

Usually 100 to 200 nits looks good. 100 nits is the standard for SDR, but most monitors are higher than that. The setting is more about changing the look instead of finding the correct value anyway.

the nit numbers are actually made to be only accurate when matching.
so there are actually calibration reason behind the nit setting.

[pentagon]

Is it possible to setup madvr so that it only enables HDR mode when the player is in fullscreen? I want windowed mode to be SDR so that Windows isn't all washed out if I want to browse the internet while watching a windowed movie. I think I've tried every display mode option/hdr option there is, but as soon as it detects an HDR video, my projector flips over to HDR mode regardless if I'm windowed or fullscreen.

[ryrynz]

Is it possible to setup madvr so that it only enables HDR mode when the player is in fullscreen?

Nope.

[KrazyLurt]

I ran into the same issue after installing Windows 11 today and found that pressing ALT-TAB even just one time to switch windows causes 10bit to stop working in D3D11 fullscreen windowed seemingly forever until I reboot the machine, then it works fine until I press alt-tab again. I had this same issue in Windows 10 after pressing windowskey-tab and never found a solution.

I just found that setting AltTabSettings to 1 in HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer prevents the issue in Windows 11, but you get a really old legacy version of the switcher.

I'm curious if anyone else if having this same issue. Can you please try pressing alt-tab to switch windows and see if it breaks 10bit for you also?
I can confirm Alt-Tab causes the same issue for me as well.

[ashlar42]

Two questions.

1) Considering madVR cannot deinterlace when using DirectX 11, how do you deinterlace? Software through LAV? Other solutions?

2) Is there a way to activate different 3D LUTs through a key combination? Say one for day viewing and one for night viewing.

On this, secondary question: is the 3D LUT file loaded dynamically when a video start or does madVR save it in RAM when it's loaded at boot? Cause otherwise I could have a script exchanging files through a remote key, in case it's not possible directly through madVR.

Thanks!

[egandt]

Delete the non-active ones, then restart, put it on one of the before deleted ones and delete the last one.

Just make sure that every display is at least one time deleted from the config.

So I tried (of teh 4 call them A,B,C,D) I removed B, C, D (physically) then deleted them from madvr, and existed manager. Reconnected B and removed A, and started MadrVr and removed A
So now A,B,C,D had been removed once and I only had B present. Stopped MadVr and enabled all the remaining monitors (plugged them back in).

Upon restarting I see multiple devices, and every time madvr is restarted a new identification is created. Also resolution changing is still not working, nor is HDR passthrough.

I do have one work around using MCP-HC and having it change the resolution which seems to be working correctly, however it is not my preferred player, still it is an option. Note screenshot was while n progress so resolutions are not exact, but get point across.

ERIC

[JaylumX]

Two questions.

1) Considering madVR cannot deinterlace when using DirectX 11, how do you deinterlace? Software through LAV? Other solutions?

Thanks!

Madvr does deinterlace when using DirectX 11 in Lav filters, you just have to select your graphics card instead of using native in the "hardware device to use" drop-down-box.

[thighhighs]

every time madvr is restarted a new identification is created
Same problem on Windows 11. Device IDs stacking up. Looks like all users affected. Hope it GPU driver/Windows related bug and will be fixed in future. Otherwise madVR should be updated :scared:

[el Filou]

Madvr does deinterlace when using DirectX 11 in Lav filters, you just have to select your graphics card instead of using native in the "hardware device to use" drop-down-box.But then you lose the only benefit of D3D11 which is the lossless and high-performance/low load native mode.
I have to constantly switch decoders manually depending on what I'm watching to get the best quality out of madVR with my NVIDIA and it's a bit tedious, but no way around it.

[clsid]

You could let LAV Video do the deinterlacing. Then you should only get copyback for interlaced video. Assuming the interlaced stuff is 1080p and below, that shouldn't matter much for performance.

[SamuriHL]

Are they still interlacing 4k content???

[huhn]

they wanted to do that in french for broadcast they may have...

[SamuriHL]

I thought they got rid of that nonsense with 4k. Ughhhhhh

Sent from my SM-G998U1 using Tapatalk

[el Filou]

You could let LAV Video do the deinterlacing. Then you should only get copyback for interlaced video. Assuming the interlaced stuff is 1080p and below, that shouldn't matter much for performance.Do you mean with Yadif/Weston? Or with CUVID? Software deint isn't as good as CUVID's deint to me. But then if I leave the decoder on CUVID, it deinterlaces PAL film content too (I know people said it shouldn't, but it does) and I have no easy way to disable that with a hotkey like when controlling deinterlacing from madVR.
I have mapped .reg files to shortcuts to make my life easier, it's not that much of a hassle even if not super friendly.they wanted to do that in french for broadcast they may have...Currently the french UHD broadcast test is still 50p, so I hope they forgot about that for good.

[jmonier]

Same problem on Windows 11. Device IDs stacking up. Looks like all users affected. Hope it GPU driver/Windows related bug and will be fixed in future. Otherwise madVR should be updated :scared:

This problem and the one with HDR passthrough has identical symptoms to a bug that I reported several years ago. That bug occurred only with a Displayport connection but was on Windows 8.1.

I believe that madshi ignored it because the Displayport was so rare for HT. It's probably worth another look at this time.

[SamuriHL]

Currently the french UHD broadcast test is still 50p, so I hope they forgot about that for good.

God I really hope so. Interlacing should DIE a horrible death in fire.

[ashlar42]

God I really hope so. Interlacing should DIE a horrible death in fire.
Quoted for truth. In any case, I see there's no easy solution. I'll keep on re-encoding my stuff and deinterlacing it with QTGMC.

[CarlosCaco]

Hey guys im using madvr in my new notebook and i noticed the player dont enter on d3d11 exclusive mode, so i cannot use the 12bit mode, checked exclusive mode no matter what i do i only get d3d11 windowed, the gpu is a 1650 Windows 10 latest drivers... Do anyone knows what can be causing the player do not entering on exclusive mode? Thanks

[el Filou]

No guarantee but worth a try: right-click the executable (or the Start Menu shortcut to it) and in Compatibility tab, check Disable full-screen optimisations.

But I don't see why you would need exclusive to get 12-bit with NVIDIA.

[Whiskeyomega]

Where do you get the betas ? Really need to update as some files have bad AR on 92.17

[Asmodian]

I doubt the betas are going to change anything about AR handling.

They are updates for HDR tone mapping, nothing else as far as I know.
http://madshi.net/madVRhdrMeasure141.zip

[Whiskeyomega]

I doubt the betas are going to change anything about AR handling.

They are updates for HDR tone mapping, nothing else as far as I know.
http://madshi.net/madVRhdrMeasure141.zip

Thanks
Its definitely MadVR thats cropping the frame. It doesnt help the AR info on the file is broken but at least EVR doesnt crop the picture itself so I can just scale it down to 2:35:1 with MadVR it adds a massive one sided black bar at the top. EVR shows the whole picture no bars until you scale it manually its meant to be 2:35:1 and VLC displays it properly.

[el Filou]

madVR doesn't crop unless it is instructed to by its own configuration, player application, or automatic black bar detection.
Post a screenshot with the OSD showing (Ctrl+J), to see what madVR is doing to the picture.

[Whiskeyomega]

madVR doesn't crop unless it is instructed to by its own configuration, player application, or automatic black bar detection.
Post a screenshot with the OSD showing (Ctrl+J), to see what madVR is doing to the picture.

I gave up trying to get it correct really. Just seems these files I have were badly decoded and need redoing.

https://i.imgur.com/igX7vhP.jpeg

[SirMaster]

Is it possible to setup madvr so that it only enables HDR mode when the player is in fullscreen? I want windowed mode to be SDR so that Windows isn't all washed out if I want to browse the internet while watching a windowed movie. I think I've tried every display mode option/hdr option there is, but as soon as it detects an HDR video, my projector flips over to HDR mode regardless if I'm windowed or fullscreen.

Just make 2 profiles, one with HDR passthrough and 1 with HDR tone-mapping.

Set hotkeys for the 2 profiles and then when you switch between windowed and fullscreen you can press the hotkey to decide if you want HDR or SDR.

And you can set whichever profile to be the default that you prefer.

[ryrynz]

Just make 2 profiles

Nice solution

[flossy_cake]

Hello

There appears to be a serious bug related to the "composition rate" used by MadVR, which can cause intense frame rate stuttering in many scenarios.

The issue appears that "composition rate" gets stuck at the rate used by the previously played file.

I am able to reproduce this bug on two different systems, with two different motherboards and two different GPUs (AMD R9 380, NVidia 1070). However both systems use Windows 7 x64, so it may be a bug related to Windows 7's compositor. I do not have a Windows 10 machine at the moment, but if someone could check this on Win10 it would be much appreciated.

Steps to reproduce:

1. Use the latest MPC-HC 64bit v1.9.15.79 and MadVR v0.92.17, as provided with the latest K-Lite "full" codec pack.

2. Set your monitor to a 60hz mode, such as 1080p60 or 1440p60 etc. (I haven't tested this on a 4k60 monitor yet).

3. Ensure your monitor is capable of the 24hz equivalent, eg. 1080p24 or 1440p24.

4. In MPC-HC > view > options > Playback > Fullscreen > untick "Launch files in fullscreen"

5. In MadVR settings > devices > display modes:

a) tick "switch to matching display mode ... when media player goes fullscreen"
b) tick "restore original display mode ... when media player is closed"
c) in "list all display modes", type in the two modes, eg. "1080p24, 1080p60" or "2560x1440p24, 2560x1440p60" (text field must say valid)

6. In MadVR settings > rendering > general settings, untick "enable automatic fullscreen exclusive mode"

7. Apply, close and exit MPC-HC.

8. Open a p24 video and press Ctrl+J. Both display rate and composition rate should report 60hz (first two lines on Ctrl+J screen).

9. Alt+Enter to go full screen. Both display rate and composition rate should now report 24hz, and playback framerate should be flawless.

10. Esc to exit full screen and exit MPC-HC. This will trigger the display mode changing back to 60hz.

11. Open a p60 video and press Ctrl+J. Composition rate still reports 24hz and playback is stuttery.

I have discovered a workaround to this, and it seems to imply it is perhaps an issue with Windows compositor: between steps 10 and 11, open a window such as Windows file explorer, and drag it around the screen. On both my systems I observe the window movement is animating still at what appears to be 24hz despite the display mode having switched back to 60hz, as per previous step 10. However, after a few seconds of dragging the window around, releasing the mouse button in between drags, it starts animating smoothly again at 60fps, as if Windows compositor is finally realising it needs to animate at 60hz again to match the display rate. Then, after this, Ctrl+J composition rate reports the correct 60hz for a 60p video and there is no stutter.

So it appears to be something going wrong with Windows compositor getting stuck at the value used by the previous video -- is there perhaps some Windows API function that MadVR could call on exiting MPC-HC which could somehow reset or reinitialise Windows compositor?

Thanks for your time.

_______________________________________________________________________

Update: the issue appears to be resolved if I disable Windows desktop compositor. I say appears because without desktop composition the Ctrl+J composition rate is no longer reported, so I'm just eyeballing it to check the frame rate is smooth, and it does appear to be (and that issue with having to drag a window around to reset it, does not occur). Annoyingly, Direct3D 11 is not possible unless compositor is enabled, and am not sure if video fidelity is compromised by using D3D9 instead.

[huhn]

the composition rate is the refreshrate used by windows desktop there is no way for madVR to change it. it's a bug of the WDDM.

the orginal FSE mode ignores the composition rate(it may show it but does not present on it) so is overlay renderering.

this can happen on some win 10 version so have it fixed win 8 had this problem generally fixed. i have not sen it on 11 yet.

[flossy_cake]

Thanks, guess I'll be switching to Windows 10 then.

I realise we can work around it by using full screen mode -- either exclusive or not, doesn't matter, full screen always gets matching composition rate in my tests.

But as soon as we go back to windowed mode the problem persists, and the user has to manually drag windows around to restore the compositor rate.

eg. suppose the user finished playing a 24fps movie, exits MPC-HC and then wants to do some web browsing. The web browser will be all stuttery on scrolling and user must drag windows around to clear the bug.

I am still thinking there must be some API function that could automatically reset the bug on MPC-HC exit. Something that does the equivalent to dragging a window around, such as rendering a few frames of video at a higher rate?