madVR - high quality video renderer (GPU assisted)

[SirMaster]

Nope, I also thought that before and it may have been the case at some point in the past, but all the HDR features now work with DXVA native. You can check easily with ShowRenderSteps.
Luminance measure has to work because madshi himself recommends D3D11 native for the standalone measurement tool.
Highlights recovery is also easy to check even without ShowRenderSteps because it uses quite a lot of processing power (at least on my GPU :))

Excellent, thanks! Yes it must have changed somewhere along the line in newer builds than I am originally remembering.

[fourbigkids]

Hi all.

Having a bit of trouble with judder in certain circumstances. I have two HDMI outputs from my HTPC. One from an Nvidia RTX2060, which goes to a pre-pro and then to the TV, and the other from the on-board Intel 630 video which goes direct to the TV. VLC plays video without judder through either route to the TV. But with MPC-BE and MadVR, judder is present, but only when using the Intel video output. MadVR is set for pretty low performance. I have attached two snips, one for the Nvidia and the other for the Intel. I see that the only difference is in the rendering rate, the Nvidia being three times faster than the Intel. Could this be the cause of the judder? The Nvidia card is new and I hadn't noticed judder on the Intel card beforehand.

Ideally I want to be able to use MPC-BE for both outputs and have the capacity to upscale the many old DVD movie rips we have with MPC-BE, and for MPC-BE to work smoothly with the Intel output.

You might ask why do I need both outputs. Well, my wife prefers minimal engagement with the system. Turn it on and press play - hence Intel straight to the TV. However, I am prefer to enjoy the full surround sound experience and the quality of the MadVR upscaling, even if it requires more action on my part. The only alternative I can see is changing the default player to VLC for my wife and then manually opening files in MPC-BE when I want to watch something.

Any suggestions on how to resolve?

Cheers,

Allan

Nvidia Card:

https://1drv.ms/u/s!Ajkfvd4XPdI2iNx1jOLe-dF0TCtLZQ


Intel Video:

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


.................................................................

edit:

It appears that the judder was present because MadVR wasn't able to change the refresh rate to match the source with Windows doing the cloning of the displays (the AVR and the TV). I have resolved this problem by using two outputs on the nvidia GPU, rather than one on the nvidia and the other on the Intel GPU. One goes via the AVR to the TV and the the other goes direct to the TV. This way nvidia controls the 'cloning'. I have set it up in the Nvidia control panel so that the AVR is the source of the clone when both routes are active. When the AVR is switched on I am able to play a video with MPC/MadVR through the AVR to the TV and the refresh rate is able to be switched to match the source, but not HTPC-TV direct. If I turn off the AVR then MPC/MadVR is able to switch the refresh rate HTPC to TV direct. :-) This may be possible in Windows but I haven't checked - very easy to setup in nvidia control panel. Only downside is that I can't play UHD discs on my HTPC but this is a non-issue given that the licencing controls keep screwing things up and I have a BSOD more often than not. It is just not worth the trouble - just bought a Panasonic player for $250, works like a charm.

[fourbigkids]

Having trouble posting images from url. I'll try again:

Nvidia:

https://1drv.ms/u/s!Ajkfvd4XPdI2iNx1jOLe-dF0TCtLZQ

Intel:

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


Edit

Nah. Screw it. Not working.

[Asmodian]

How fast is the Intel GPU in ms? What framerate video are you playing?

[fourbigkids]

Hi Asmodian. The Average Stats show the Intel GPU rendering at 64.70ms in the video in the links above. It is a 23.976 fps movie in this case, but the judder is common to a range of sources.

Allan

[Asmodian]

Yes, the Intel GPU is too slow for your settings. A single 23.976 video frame is only displayed for 1000/23.976 = 41.70833 ms. This means you need the average rendering time to be below 41 ms, and there also needs to be some extra so I would target something lower, low enough madVR stops reporting dropped frames. Higher frame rates need to be rendered even faster.

[fourbigkids]

Thanks Asmodian. I thought that might be the case. Looks like I am going to have to run two players, one for each GPU. Cheers, Allan

[jmone]

I just updated that info here:
https://forum.doom9.org/showthread.php?t=176013

419.67 GRD 2019-03-25 stuttering issues
419.67 CRD 2019-03-20 stuttering issues
419.35 GRD 2019-03-05 stuttering issues
419.17 GRD 2019-02-22
418.91 GRD 2019-02-14 NO stuttering issues

Did anyone test 419.17 about the stutter issues?

I have no issues on 419.35 once I turned VSYNC ON.

[ryrynz]

Why are people even changing VSYNC in the control panel? Just use the default 'use the 3d application setting' and be done with it.

[huhn]

that's the issue it doesn't work with application controlled where it should use "on".

[ryrynz]

Would madVR be capable of forcing Vsync?

[huhn]

i don't have a turing card so i can't check this in "detail".
but i'm pretty sure madVR wants vsync to be on so it is "forcing" it but it looks like it is doing something else.

[Nicog]

Hi,

I'm facing another issue with MadVR (I suppose it comes from MadVR).

I would like to use the "zoom" function in windows in 2160p (from 100% to 200%).

When I do that, the picture displayed by MadVR is zoomed also of 200% and shrink then to fit to the screen. Conclusion : the native 2160p movie is displayed at 1080p !!! (MadVR OSD shows 2160p->1080p).


Is it normal? Any idea to solve this issue (my config in my signature)?

[huhn]

if you didn't try that already restart the PC. i had something similar some years ago.

what so ever madVR has no effect on this. madVR only changes the resolution with it's build in display modes and 3D.

[jmone]

Why are people even changing VSYNC in the control panel? Just use the default 'use the 3d application setting' and be done with it.

I was getting constant every second stuttering (that madvr was not reporting) with the default 'use the 3d application setting' and changing that to "on" fixes it when using Windowed Mode.

[Klaus1189]

I have no issues on 419.35 once I turned VSYNC ON.

Thanks, added in AMD, Intel and Nvidia driver issues and last recommended version (https://forum.doom9.org/showthread.php?t=176013)

[SirMaster]

Thanks, added in AMD, Intel and Nvidia driver issues and last recommended version (https://forum.doom9.org/showthread.php?t=176013)

Make sure you make it clear that its only no stuttering with v-sync forced ON.

I'm pretty sure there is no stuttering in any driver versions with vsync forced ON.

[clsid]

Hi everyone,

I have made an optimized NVIDIA profile for MPC-HC/BE. Might be helpful for those who struggle with the configuration. Try it out.

This is NVIDIA Profle Inspector tool with a profile file and a .bat to import that profile.

Download (https://www.sendspace.com/file/ohoudl)

Most important settings it uses:
Power management mode = Adaptive
VSync = on
GSync = off
SLI = off
Prefer NVIDIA on Optimus systems

[onekmilesbehind]

I'm pretty sure there is no stuttering in any driver versions with vsync forced ON.

On the RTX line at least, Vsync "On" does not seem to have an effect in MadVR in the latest driver release.

I run a 2070 and, like others, found the cure to the stutter issue via forcing Vsync to "On"; when I updated to 419.67, the issue appeared again. Seeing Vsync was still on in the NCP, I assumed the issue lay elsewhere. After hours of troubleshooting, I went back down to 418.81 and that fixed it.

FWIW I do clean installs with every driver release and just flip the settings back the way they were. Vsync is always set back to "On".

I'm curious if it works in 419.17. If it does, then it appears the 419.67 release botched Vsync. If it doesn't, the fact that it goes from working-->broken-->working-->broken...doesn't indicate this is something NVIDIA cares too much about. Man I wish they had a dedicated testing group for HTPCs. Something like a Theater Ready Driver with a much larger release window (2-3 releases a year). They clearly don't hone the releases around the needs of the HTPC market. I'm sure it's a smaller segment of the userbase, but jeez, these releases are just sloppy and reflect poorly on them.

[Nicog]

On the RTX line at least, Vsync "On" does not seem to have an effect in MadVR in the latest driver release.

I run a 2070 and, like others, found the cure to the stutter issue via forcing Vsync to "On"; when I updated to 419.67, the issue appeared again. Seeing Vsync was still on in the NCP, I assumed the issue lay elsewhere. After hours of troubleshooting, I went back down to 418.81 and that fixed it.

FWIW I do clean installs with every driver release and just flip the settings back the way they were. Vsync is always set back to "On".

I'm curious if it works in 419.17. If it does, then it appears the 419.67 release botched Vsync. If it doesn't, the fact that it goes from working-->broken-->working-->broken...doesn't indicate this is something NVIDIA cares too much about. Man I wish they had a dedicated testing group for HTPCs. Something like a Theater Ready Driver with a much larger release window (2-3 releases a year). They clearly don't hone the releases around the needs of the HTPC market. I'm sure it's a smaller segment of the userbase, but jeez, these releases are just sloppy and reflect poorly on them.

For me :
419.17 NOK (neither FSE nor Windowed) with Vsync ON
418.81 is OK with Vsync ON

[onekmilesbehind]

For me :
419.17 NOK (neither FSE nor Windowed) with Vsync ON
418.81 is OK with Vsync ON

Thanks and sorry if you had already posted the 419.17 status. So it appears NVIDIA is cycling between working-->broken then.

I'll jump on the next release when it's out to see if anything has changed. Hopefully this isn't another bug that's going to require a wait for the next major branch release (though I think that's due in April?). MadVR is absolutely amazing when the drivers don't muck things up.

[Klaus1189]

Thank you for the info. These are 2019 drivers:
419.67 GRD 2019-03-25
419.67 CRD 2019-03-20
419.35 GRD 2019-03-05
419.17 GRD 2019-02-22
418.91 GRD 2019-02-14
418.81 GRD 2019-02-04
417.71 GRD 2019-01-15

Can you RTX users copy the version (one line) he/she used and know that there is an issue with stuttering or maybe not?
So I can be sure if there is stutter or not.
I copy then the info to the dedicated thread AMD, Intel and Nvidia driver issues and last recommended version (https://forum.doom9.org/showthread.php?t=176013)

[ryrynz]

Nicog, you didn't need to quote the post directly above yours.

[Asmodian]

One day everyone will be trained. ;)

[jkauff]

One day everyone will be trained. ;)Except for the rebels, of course, who just enjoy annoying ryrynz. :devil:

[Jinkai]

devices -> right click on "your device name" ->create profile group -> check color & gamma -> right click profile group -> add profile.

add a shortcut and gamma to the profiles done.

Thank you, sir!

[el Filou]

Just noticed some new strange behaviour with NVIDIA driver 419.67 (Windows 1803).
When I start playback everything is normal but if I pause playback, after I un-pause the GPU clock goes down and render times shoot up until the average stats are consistently above the frame time but with madVR still not dropping frames. The downside is the render queue doesn't fill up anymore and I don't like this very much.
If I never pause playback, render times and GPU clocks stay the same as at playback start.
I never saw that behaviour before. Anyone else notice this on their NVIDIA?
See screenshot: https://drive.google.com/open?id=1_beUPfbcxcPCwpWo72telXfj9JIHsGdj (normally when playing 50i my rendering time is max. 7-8 ms and DXVA is 4-5 ms)
Power management in NVIDIA control panel is on Adaptive.

[ryrynz]

Not seeing this on my 1060 with 419.67, any particular reason why you bumped your values up to 32 and 16? It's probably not required for smooth playback and you're just creating additional workload.
I changed my setting to match, recon soft 1080 playback -> 1080 screen D3D11 fullscreen windowed on Adaptive, I just am not playing back 25fps on 50hz.
Are you sure it's the latest driver is doing this? Revert and check?

Originally Posted by Asmodian One day everyone will be trained. ;)

I see what you did there jkauff.

[el Filou]

Thanks for the check.
Update: After more tests I noticed it was somehow only happening in MediaPortal and not in MPC-HC, which is weird because there isn't even an NVIDIA app profile for it :confused:
Rolled back to 419.35 and it went away.
(Edit: I suspect it had something to do with the way madVR calculates the rendering times, as there is no way I could have 0 frame drops with the render time being constantly above frame time. Maybe a way the GPU flushes are handled by the application? (MediaPortal's GUI runs in Direct3D). Anyway, it is strange)

I use 32/16 for various reasons:
- my HTPC is old and I find having a longer render queue is more drop-proof if Windows/another app decides to hog resources in the background
- I watch DVB TV and sometimes there are signal breaks, and I have less stutter when that happens if I use longer queues.
- I still watch (PAL) DVDs from time to time and there is a bug that 'halves' the decode queue: https://forum.doom9.org/showthread.php?p=1832113#post1832113
- I have the (V)RAM :) and I don't see how it would create an additional workload except when the queues are filling up obviously. More frames are just decoded/rendered ahead of time, but there isn't more total work?

[whitestar999]

Planning on installing a new os on ryzen 1200+1050Ti+1080p TV system.Should I go with win 8.1,ltsb 2016 or ltsc 2019? I will upgrade to 4k tv/better nvidia card in future & would like to keep the current os for as long as possible.

[ryrynz]

I'll put my vote in for lTSC 2019.


I have the (V)RAM :) and I don't see how it would create an additional workload except when the queues are filling up obviously. More frames are just decoded/rendered ahead of time, but there isn't more total work?

Performance wise It doesn't appear to be quite as simple as only having higher usage when the queue needs to be fully sated and at all other times things being equal, test it for yourself.

If I lower queues to standard 16/8 my fan speed drops to nothing, my clocks lower, GPU usage is higher as a result and predicted wattage is around 10% with my setup as it is on Full HD content.
If I increase this to 32/16 my fan speed is now 20% my clocks are higher, GPU usage is lower but predicted watts are almost twice that of the standard queues.

[whitestar999]

I'll put my vote in for lTSC 2019.


Thanks! Any specific things I need to keep in mind like which driver version,any windows display settings & any win 10 specific madvr optimization. My tv is 1080p60Hz non-hdr & I currently use smooth motion option & most of my media is 720p/1080p SDR 23.76fps.

[chros]

Should I go with win 8.1,ltsb 2016 or ltsc 2019?
I vote for ltsb 2016, that's what I use and I don't upgrade it until LAV or madVR requires it.
The reason behind this is MS breaks stuff with every new version, so your older utils that you may use and haven't been updated for a while may break too. (E.g. Winaero Theme Switcher (http://winaero.com/comment.php?comment.news.209))

which driver version
Since you (will) have a Pascal card just use the old 385.28 driver.

[ryrynz]

Wait to see what others recommend, for drivers see if the latest works for you without issues, and stick with it until such time you feel it's worthwhile to upgrade and are prepared to take time to test it. The latest 419.67 apparently seems to be fine for the 10 series but 385.28 is the least problematic at time of writing.
Display settings, just what others have said.. Adaptive power mode and disable Focus Assist, pretty much everything else I can think of is fine with defaults. A 1050 is likely to have less issues with drivers (like the stuttering of recent drivers on some the newer cards)
If you can do 24Hz on your TV and create a display custom mode for it in madVR you may find that delivers the best experience, assess it vs your current setup with Smooth Motion enabled and decide for yourself.

[anta777]

how can you compare speed
rx590 vs rtx2060 vs gtx1080ti
FullHD in 4K

[Siso]

Since you (will) have a Pascal card just use the old 385.23 driver.

Is the driver 385.28 the same like 385.23?

[chros]

Is the driver 385.28 the same like 385.23?

:) 385.28, I managed to screw it up, sorry.

[katodevin]

The latest 419.67 apparently seems to be fine for the 10 series but 385.23 is the least problematic at time of writing.

That's what I'm seeing as well. My 1060 worked fine with new drivers, but my 1660 is stuttering like crazy unless I do fullscreen exclusive (even then I'm getting stutters every 45 seconds or so).

I tried downgrading drivers, but older drivers simply won't detect the 1660 as a compatible card. I'm totally pulling my hair out as my HTPC is pretty much garbage with UHD 4k content at this point.

[ryrynz]

Have you tried changing v-sync to on with the latest driver? That's apparently is the cause of the stuttering.

[el Filou]

If you want to keep the same Windows version for a long time (how long exactly?) but also upgrade to a more recent graphics card later, be aware that later hardware may need a minimum Windows 10 version to work. For example GeForce 20 series released 09/2018 need Windows 1709 minimum someone using LTSC 2016 would be out of luck. An hypothetical GeForce 21 or 22 series may or may not work on Windows LTSC 2019.

If I increase this [queues] to 32/16 my fan speed is now 20% my clocks are higher, GPU usage is lower but predicted watts are almost twice that of the standard queues.That's interesting. :thanks: My clocks are basically the same with 16/8 and 32/16, but my card is passively cooled and lower power so maybe the power management is different.

[katodevin]

Have you tried changing v-sync to on with the latest driver? That's apparently is the cause of the stuttering.

Yep, Vsync is set to on. Power is set to prefer max performance.

[TheProfosist]

Yep, Vsync is set to on. Power is set to prefer max performance.

just based on my own experience of not having fixed it yet do you have HDR enabled or are playing back HDR content? This seems to be my sticking point at the moment.

Right now I'm running 419.67 with an RTX2060

[Siso]

:) 385.28, I managed to screw it up, sorry.

No problem :D

[katodevin]

just based on my own experience of not having fixed it yet do you have HDR enabled or are playing back HDR content? This seems to be my sticking point at the moment.

Right now I'm running 419.67 with an RTX2060

Windows HDR is off. I'm using MPC-BE and MadVR to pass through HDR to my LG C8. Worked perfect before I upgraded to this 1660 GTX. I've tried both 419.67 and 419.35 (the only 2 drivers that support the 1660 at this point in time). They both have huge stuttering issues. It is a bit strange though, when I initially installed .35 and enabled vsync in Nvidia control panel, everything seemed fine. After a couple of reboots and various video files, the issues came back. Really frustrating!

[Limberjork]

Hoping you guys can help me get deinterlacing working better on my setup. I just ripped my Buffy the Vampire Slayer season 1 NTSC DVDs to MKV files (no re-encoding of video or audio) with MakeMKV and I'm trying to play them back with MPC-HC and madVR (using MPC-HC's internal LAV filters). I don't have much experience at all playing back interlaced content - it's 2019, after all - so bear with me.

My first problem is that I can see a lot of combing artifacts in certain spots, typically in frames with motion that come immediately after a cut: Episode 7 01:00.277 (https://i.imgur.com/5Oy0Y6E.png), Episode 11 00:11.713 (https://i.imgur.com/mMkqVej.png).

My second problem is that deinterlacing doesn't get activated on 3 out of the 12 episodes according to marVR's OSD. These happen to be the 3 episodes that start with a cold open (straight to the first scene of the episode), rather than the usual intro sequence. If I switch the deinterlacing setting in madVR from "if in doubt, deactivate deinterlacing" to "if in doubt, activate deinterlacing," then deinterlacing is activated on all 12 episodes.

Sample clips: First 15 seconds of episode 1 (https://drive.google.com/open?id=1skue8hfVJhcH7r-nk5Q4qdSb96Z_JXhX), Clip from episode 7 (I see a lot of combing when the guy lights the lighter) (https://drive.google.com/open?id=1uNYVF8fi0l3AA7vUsqjhq7a61sA_cJzV)

One last thing that I've noticed is that in every sequence except for the intro sequence, I get a ton of repeated frames. In fact, when I step through the video frame by frame, every frame is repeated once.

LAV Video settings (https://imgur.com/pbjq04D.png)
madVR deinterlacing settings (https://imgur.com/4XzNda6)

[Siso]

So the best driver for pascal cards is 385.28, also works good with madvr? I'm with 382.53, thinking about goin' for 385.28.

[chros]

For example GeForce 20 series released 09/2018 need Windows 1709 minimum
Are you sure about this? I haven't seen any restrictions with 2xxx series (note, I don't have such card).

So the best driver for pascal cards is 385.28, also works good with madvr? I'm with 382.53, thinking about goin' for 385.28.
That's the latest one that doesn't brake lot of stuff , not necessarily the best. I wouldn't upgrade if everything works for you now, until you are bored :)

[Siso]

That's the latest one that doesn't brake lot of stuff , not necessarily the best. I wouldn't upgrade if everything works for you now, until you are bored :)

Well, I don't have any issues with the version I'm using, so I guess I'll stick to 382.53 :D

[ryrynz]

Are you sure about this? I haven't seen any restrictions with 2xxx series


He is correct.

[DMU]

My first problem is that I can see a lot of combing artifacts in certain spots...

My second problem is that deinterlacing doesn't get activated on 3 out of the 12 episodes according to marVR's OSD. These happen to be the 3 episodes that start with a cold open (straight to the first scene of the episode), rather than the usual intro sequence. If I switch the deinterlacing setting in madVR from "if in doubt, deactivate deinterlacing" to "if in doubt, activate deinterlacing," then deinterlacing is activated on all 12 episodes.

One last thing that I've noticed is that in every sequence except for the intro sequence, I get a ton of repeated frames. In fact, when I step through the video frame by frame, every frame is repeated once.

Try to use ivtc (https://drive.google.com/open?id=1ZW6kHaU1aXa87xBdimnX02DCceR9xOSn) (force film mode). It will not completely solve problems with combing artifacts in certain spots, but will solve the problem with the duplication of frames.