madVR - high quality video renderer (GPU assisted)

[menac1ty]

I have a GTX 980Ti and a Ryzen 2600x
1080p
When playing a video file with madVr, the whole system restarts within 10 seconds. I've tried 32bit and 64bit, different settings, updated LAV filters, nothing.
I have no issue in games or any type of stress testing the GPU.
What's the problem?

[KrazyLurt]

Updating to 461.40 indeed changes how vsync acts and for me it introduces small stutters ( no drops in the OSD).

The solution for me is to again check fullscreen exclusive mode in the MadVR settings. This works with mpc-hc.
Sadly not with PotPlayer, let me know why or how to solve it.

- Sidenote for mpv users -
Same issue , solved with using opengl, I use these flags:
# no vsync issues
gpu-api=opengl
opengl-swapinterval=1
fbo-format=rgba16f # required for fsrcnnx with opengl

I usually use d3d11 or vulkan so a solution to this as well is welcomed.

[Warlock]

I was having a lot of stutterings with the rtx 2060, no drop frames, driver v460,79. Presentation glitches were many, just open the video on the mpc-hc and it was already 4 ~ 5 and it kept increasing. It only solved the problem when the vsync was turned off on the nvidia control panel for the mpc-hc and the madvr executable, then it solved the problem of stutterings, it's over, now everything flows perfectly. In short, vsync active at least for me only causes problems with madvr, if you don't want to turn it off for the whole system, do the test only with the video player and madvr, at least it's working very well for me.

[Asmodian]

Did you try "application controlled" instead of on or off?

[KrazyLurt]

I was having a lot of stutterings with the rtx 2060, no drop frames, driver v460,79. Presentation glitches were many, just open the video on the mpc-hc and it was already 4 ~ 5 and it kept increasing. It only solved the problem when the vsync was turned off on the nvidia control panel for the mpc-hc and the madvr executable, then it solved the problem of stutterings, it's over, now everything flows perfectly. In short, vsync active at least for me only causes problems with madvr, if you don't want to turn it off for the whole system, do the test only with the video player and madvr, at least it's working very well for me.

Yeah tried that, no vsync removes the stutters but introduces tearing.

Did you try "application controlled" instead of on or off?
Yeah I have tried all three, all combinations with above applications+madvr. Application controlled is the recommended by Nvidia going forward but it's a shame that the vsync is acting up. I've tried a bunch of different things like turning on HAGS to nu avail.

[KrazyLurt]

Well I solved my issue, I hope this post will be useful.
As mentioned earlier, had vsync issues, solved in mpc-hc with fullscreen exclusive but it didnt work with PotPlayer.

Well this is solved in MadVR settings:

EDIT: Asmodian corrected my error of reasoning, so this is my solution after adjusting as Asmodian explained below

Lower the vaule "present several frames in advanced" to "1", this work under "window mode" and "exclusive mode"

I previously had it 8 frames in advanced. The only value working for me is "1".



Only thing left now is getting d3d11 and vulkan APIs working in MPV, I havent found any flag for editing how many frames presented in advance, maybe its somewhere in the io manual or it doesnt work the same. Anyway, input is welcomed as usual.

[Asmodian]

I previously had it checked and 8 frames in advanced. The only value working is 1 or (of course, same thing) toggle it off.

This is not the same thing at all!

If you turn it off it uses a very old method to present the frames. Notice how it changes to "how many backbuffers shall be used:" instead of "how many video frames shall be presented in advance:"?

I have been recommending <=3 frames presented in advance for a long time now. I definitely had stuttering with values >3 well before this driver update. Many users report best results with it set to 1.

Using backbuffers instead is not recommended, though I am not sure exactly why. Slower? :p

[KrazyLurt]

Okay, sorry about writing it as the same thing, to the not too experienced eye it looked like it would behave the same way.

Thanks for the heads-up , I will adjust my settings accordingly. :)

[Siso]

This is not the same thing at all!

If you turn it off it uses a very old method to present the frames. Notice how it changes to "how many backbuffers shall be used:" instead of "how many video frames shall be presented in advance:"?

I have been recommending <=3 frames presented in advance for a long time now. I definitely had stuttering with values >3 well before this driver update. Many users report best results with it set to 1.

Using backbuffers instead is not recommended, though I am not sure exactly why. Slower? :p

Is the recommended 3 frames in advance or less for turing and ampere cards only? What about pascal cards?

[Asmodian]

It seems to be everything with more recent drivers but I only have personal experiance with Turing and Ampere.

[Siso]

It seems to be everything with more recent drivers but I only have personal experiance with Turing and Ampere.

I see, maybe it is a new driver thing. I'm with 456.71 drivers.

[Warlock]

Well I solved my issue, I hope this post will be useful.
As mentioned earlier, had vsync issues, solved in mpc-hc with fullscreen exclusive but it didnt work with PotPlayer.

Well this is solved in MadVR settings:

EDIT: Asmodian corrected my error of reasoning, so this is my solution after adjusting as Asmodian explained below

Lower the vaule "present several frames in advanced" to "1", this work under "window mode" and "exclusive mode"

I previously had it 8 frames in advanced. The only value working for me is "1".



Only thing left now is getting d3d11 and vulkan APIs working in MPV, I havent found any flag for editing how many frames presented in advance, maybe its somewhere in the io manual or it doesnt work the same. Anyway, input is welcomed as usual.
I did what the Asmodian said, I went back to the default settings for vsync and power on the nvidia control panel. I will follow your tips for mpc-hc, in case just activate the automatic full exclusive mode option in general setttings, and then set the value "1" in present several frames in advanced, both in windowed and exclusive mode?

[KrazyLurt]

I will follow your tips for mpc-hc, in case just activate the automatic full exclusive mode option in general setttings, and then set the value "1" in present several frames in advanced, both in windowed and exclusive mode?
I did adjust the value in both windowed and exclusive, not because it mattered, but I saw no reason to have a value beyond that now when vsync, going forwards, is implemented the way it is, unless Nvidia see it as a bug and make some adjustments.

[Greenhorn]

Well I solved my issue, I hope this post will be useful.
As mentioned earlier, had vsync issues, solved in mpc-hc with fullscreen exclusive but it didnt work with PotPlayer.

Well this is solved in MadVR settings:

EDIT: Asmodian corrected my error of reasoning, so this is my solution after adjusting as Asmodian explained below

Lower the vaule "present several frames in advanced" to "1", this work under "window mode" and "exclusive mode"

I previously had it 8 frames in advanced. The only value working for me is "1".



Only thing left now is getting d3d11 and vulkan APIs working in MPV, I havent found any flag for editing how many frames presented in advance, maybe its somewhere in the io manual or it doesnt work the same. Anyway, input is welcomed as usual.

so it's kinda offtopic for madVR, but MPV uses backbuffers like madVR's old DX9 and DX9 Windowed Overlay modes. set it with swapchain-depth in your mpv config.

Since it's not presentation in advance I'm not sure if the same logic applies. I know the old Windowed Overlay mode in madVR is actually stutter-free for me with 3 backbuffers on a Turing card. (And this stuttering nonsense started for most people when Turing came out.)

[ang3l]

is there anyone with an amd rx6000 series (6800/6900) ? before I had an rx480 and the hdr switching was working perfectly now there is no way to make it work

letest amd driver Adrenalin 2020 Edition 21.2.2 Optional

tried with both madvr 92.17 and latest beta madVRhdrMeasure123b, outputting full rgb or ycbcr 4:4:4

https://i.postimg.cc/zGygyGjd/amd.png

EDIT

ok it seems related to the latest madvr beta, with normal 92.17 it works now, my old gpu didn't have enough strength to do tone mapping with madvr so I had never installed a beta versions of madvr before

anyone had problem with newer beta and amd?

[KrazyLurt]

so it's kinda offtopic for madVR, but MPV uses backbuffers like madVR's old DX9 and DX9 Windowed Overlay modes. set it with swapchain-depth in your mpv config.

Since it's not presentation in advance I'm not sure if the same logic applies. I know the old Windowed Overlay mode in madVR is actually stutter-free for me with 3 backbuffers on a Turing card. (And this stuttering nonsense started for most people when Turing came out.)
Thanks buddy, I must have skimmed over swapchain-depth when doing another dig at the reference manual yesterday. :thanks:

swapchain-depth=1 solved the vsync issue with the d3d11 API.

Not when using the Vulkan API though. I tried vulkan-queue-count=N with several values (default 1) with and w/out vulkan-swap-mode=fifo and/or swapchain-depth=1.

Doesn't matter that much, it's more a curiousity thing at this point, d3d11 is fine .

[Warlock]

After reading several comments and tips from you guys, the best configuration I got to eliminate the stutterings / glitches on my rtx2060, using mpc-hc, lavfilters and madvr was to leave vsync in the default settings, set value "1" in present several frames in advanced.

Even with these changes, I still noticed some glitches and stutterings, which were completely solved when I configured it on the nvidia control panel, exclusively only for the mpc-hc and madvr, in the power option for preference for maximum performance, with that resolved definitely the problem of stuttering / glitch in the system, now everything runs perfectly, everything is soft, but there is a catch, the consumption and temperature of the vga increases a little and maybe, depending on the profile used in madvr, the user may need to reduce some things for vga to hold the performance.

But I'm seriously considering abandoning madvr permanently and start using mpcvr with standard video renderer, because I found it much better than madvr, it is light, works for videos encoded in 10bit and is very simple to configure. I am testing it at the moment, no stutterings / glitches using it, I will do some tests, but it is likely that it will definitely stay on it, just not having stuttering in the videos is already perfect, without having to do or configure anything.

[Asmodian]

I will follow your tips for mpc-hc, in case just activate the automatic full exclusive mode option in general setttings, and then set the value "1" in present several frames in advanced, both in windowed and exclusive mode?

FSE is also not useful in current Windows 10 with current drivers.

It is being emulated in the current Windows 10 so it does not provide the same benefits as it used to. There really isn't a point to use it anymore and it often causes problems. If it doesn't cause problems on your system it is fine to use, of course, but it is not an option I would enable anymore.

works for videos encoded in 10bit and is very simple to configure.

madVR works for 10 bit too. :confused:

But feel free to use MPCVR if you don't need the other features of madVR, less hassle is a good enough reason. :)

[quietvoid]

FSE can be used with latest NVIDIA drivers to keep HDR enabled, because any windows UI element would disable tonemapping on the TV otherwise.

[Asmodian]

Ah, nice, that could be useful.

I still don't like FSE and I don't use the UI elements when I want the tone mapping to work anyway. ;)

[Maryoum]

HDR looks great in Windowed mode but it gets very dim in fullscreen. Any ideas?

[Siso]

But feel free to use MPCVR if you don't need the other features of madVR, less hassle is a good enough reason. :)

The thing about MPCVR for me is that it doesn't support 3dlut, and it lacks more scallers.

[menac1ty]

I have a GTX 980Ti and a Ryzen 2600x
1080p
When playing a video file with madVr, the whole system restarts within 10 seconds. I've tried 32bit and 64bit, different settings, updated LAV filters, nothing.
I have no issue in games or any type of stress testing the GPU.
What's the problem?

anyone?

[huhn]

you should check the event manager why this is happening.
a video renderer is not really capable of doing this.

[tp4tissue]

anyone?

980ti doesn't have the HEVC decoder, so if you're running 4K, it's using CPU decode, if that's on the AVX path, it could lead to overheat / instability if you have an overclock.

Anything NOT running avx path won't crash the pc, but avx load would.

[mclingo]

anyone?

you havent given us much to go on here, does it only BSOD when you are playing a movie with the MADVR renderer, if you switch to stock renderer does not not crash?

have you done a full drive wipe and reinstall using the NVIDIA cleanup suggested here?

https://forum.doom9.org/showthread.php?t=176013

have you analyzed the memory dump?

[menac1ty]

980ti doesn't have the HEVC decoder, so if you're running 4K, it's using CPU decode, if that's on the AVX path, it could lead to overheat / instability if you have an overclock.

Anything NOT running avx path won't crash the pc, but avx load would.

I'm only doing 1080p and CPU is not overclocked.

you havent given us much to go on here, does it only BSOD when you are playing a movie with the MADVR renderer, if you switch to stock renderer does not not crash?

have you done a full drive wipe and reinstall using the NVIDIA cleanup suggested here?

https://forum.doom9.org/showthread.php?t=176013

have you analyzed the memory dump?
It doesn't BSOD, it straight up restarts the PC. without any kind of error.
With stock settings it doesn't crash at all. Also yes, I have read the thread you mentioned.
I used to have this issue before with my old GTX 970, after I installed MPC x86 it was solved.
Then I had RX570 it didn't have a problem with either x64 or x86
And this GTX 980ti has problems with both.

[chros]

Power related, maybe? Power supply, etc...

[menac1ty]

Power related, maybe? Power supply, etc...

I managed to monitor GPU power draw while playing using madVr.
It consumes about 300watts.
During gaming, or even furmark test, it consumes well over 340watts and there's absolutely no crashing.
Although I will test with a different power supply to see if anything changes.

[mclingo]

if its not even writing a MEMORY.DMP or MINIDUMP it suggests a hardware fault on some level but i have had this a couple of times way back in the past with my RX480 with a couple of driver packages where is would just restart the PC randomly with no dumps, so it is possible for a driver to cause this.

so it only happens in MADVR right?, have you definately done a full driver wipe or both NVIDA and AMD packages, you may still have some driver remnants from bother if you've had other cards installed.

so if you put the RX570 back in its ok?

[menac1ty]

if its not even writing a MEMORY.DMP or MINIDUMP it suggests a hardware fault on some level but i have had this a couple of times way back in the past with my RX480 with a couple of driver packages where is would just restart the PC randomly with no dumps, so it is possible for a driver to cause this.

so it only happens in MADVR right?, have you definately done a full driver wipe or both NVIDA and AMD packages, you may still have some driver remnants from bother if you've had other cards installed.

so if you put the RX570 back in its ok?
The answer to all your questions is yes :))

[traykov77]

Did you clock your ram speed or changed ram settings, I had crashes before and think that is videocard, but when I put ddr ram to 1333 instead of 1600Mhz I have no problems at all.

[mclingo]

The answer to all your questions is yes :))


you reported similar issues march last year when you were overclocking a 970, have you clocked this one too?

have you tried installing a quick fresh OS build on spare hard drive to test your OS, could just be windows needs a fresh install.

does it do it in all players, have you tried both HC and BE, and KODI DS, or others?

are you running MADVR at stock settings after a nvidia full driver blitz?

Try removing MADVR completely and install it in another location on a different hard drive, ideally not OS drive just as a test.

I think i've had issues like this before a long time ago but I'm sure i managed to fixed them with a combination of driver / MADVR wipe, I did once have to refresh my OS but I cant remember exactly why that was, I think it was when I had issues upgrading from win8 to win10, I wiped at that stage.

[biship]

If I want my Nvidia GPU to do all the work, must I set LAF Video to one of the 2 DXVA2 options?

And then MADVR Image Scaling Options to DVXA2?

What about Chroma upscaling? I don't see a DXVA2 option there.

[huhn]

except for some very small exception madVR entirely runs on the GPU.

it "get" DXVA chroma scaling you either set it to bilinear and use DXVA image scaling or you use DXVA2 native decode with default trade quality for performance.
i highly recommend you to avoid DXVA2 native and DXVA "scaling" it's really bad.

[biship]

Oh ok, so If I use NGU Sharp, it'll still use my GPU?
I thought anything other than DXVA2 settings in MadVR was a CPU based algorithm.

Ah, I see how to change chroma scaling - thanks!

[Asmodian]

Oh ok, so If I use NGU Sharp, it'll still use my GPU?
I thought anything other than DXVA2 settings in MadVR was a CPU based algorithm.

Yes, NGU Sharp is run on the GPU, there are no CPU scaling algorithms in madVR.

DXVA2 uses the GPU's hardware scaling, which is very fast, but everything else uses the GPU's FP32 capabilities.

In madVR only black bar detection and IVTC runs on the CPU.

[mclingo]

Hio, turned my HTPC on today to find a really odd problem i've not seen before with MADVR and KODI DS, i'm posting here as its only MADVR that has this issue and its happening with all builds of KODI DS, DS and DS BG.

when I play a movie it plays but the movie is shifted to the right and not centered on screen, I also have no focus on the movie and I can see my KODI gui at the bottom and the focus is on that, its like windowed / FSE is all broken on my machine, it was working fine last night and nothing has changed, i've chucked everything at it bar a new windows build.

I've just done a system restore to yesterday which hasnt fixed it either suggesting it may not actually be my PC, its odd though, it only happens with MADVR and KODI DS, if I play the movie in MPC/HC /BE its fine, if a use the standard renderer in KODI DS its fine.

I've also tried wiping MADVR and using base settings, doesnt even work if I use a base MADVR/KODI DS install.

Any ideas?

[mclingo]

turned out to be an issue with the test build I was using, when I went back to stock .17 it was ok, very odd, its like MADSHI put a timeout lock in this build, it just stopped working, I thought it was working in MPC/BE and HC but they had both defaulted to standard renderer and MADVR wasnt loading at all, I had been just ignoring the UPDATE MADVR message, it cant be that though I guess, i've been using this 117 build for ages.

i'll try 118

[mclingo]

is latest 123b?

[SirMaster]

is latest 123b?

Builds as of 114 have expiration dates.

They will start by popping up a message, and then later stop working.

Latest as of right now is build 128.

madshi said that he will always release a new build well before the previous build expires.

He also said if you want to run an expired build to just change your system clock. There are also ways to just change the system time that an individual program (madVR in this case thinks that it is).

[mclingo]

ffs, I didnt know they were going to actually stop working, you'd think there would be a message saying MADVR is now disabled or something, plus he doesnt actually post the updates centrally anywhere, there is nothing on the MADVR website.

[VBB]

http://madshi.net/madVRhdrMeasure128.zip

Latest test build. Keep that URL and simply check for newer builds every once in a while by changing the last digit.

[SamuriHL]

Here's the thing....they aren't official builds. They are test builds meant to help improve the HDR tone mapping code. That is why they aren't listed anywhere but that particular thread. So while you can use them, they aren't necessarily meant for daily use. The timeout was put in place because madshi was concerned that companies were creating madvr HTPC's that they were selling to customers. That isn't what it was designed for. Please note I'm not arguing for or against, here, simply stating the information.

[SirMaster]

ffs, I didnt know they were going to actually stop working, you'd think there would be a message saying MADVR is now disabled or something, plus he doesnt actually post the updates centrally anywhere, there is nothing on the MADVR website.

They are posted in the 1 place they should be.

The HDR tone-mapping development thread as that is all they are meant for.

They are meant only for testing, not for daily use or general public consumption.

[lanzorg]

Is the latest test version working with Dolby Vision MKV files?
Some samples are available here: https://www.makemkv.com/download/dvtest/

[haggis999]

At the moment, I don't have a PC capable of running madVR at anything other than the most basic settings. I can't even use it to activate HDR when playing rips of my Planet Earth II UHD Blu-rays, which rather ruins the picture quality.

I'm now planning to buy a new PC and would appreciate guidance on what configuration would offer the best madVR performance without causing much fan noise. Would a GPU that's more powerful than madVR requires run more quietly than a lower powered GPU that just meets madVR's high end needs?

No doubt such matters have already been discussed in this forum, but I don't have the stamina to wade through 3066 pages :)

[SamuriHL]

No. And it's not likely to, either.

[SirMaster]

It works fine with them. It just ignores the DV data and uses the HDR10 data.

[huhn]

DV is not that simple the DV on UHD BD is backward compatible but DV in general doesn't have to be it can even use HLG or even SDR.

here is more "information":
https://web.archive.org/web/20200929014520mp_/https://professional.dolby.com/siteassets/content-creation/dolby-vision-for-content-creators/dolbyvisionprofileslevels_v1_3_2_2019_09_16.pdf