madVR - high quality video renderer (GPU assisted)

[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]

Originally Posted by 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.

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]

Originally Posted by jmone

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

[SirMaster]

Originally Posted by Klaus1189

Thanks, added in AMD, Intel and Nvidia driver issues and last recommended version

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

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

[onekmilesbehind]

Originally Posted by SirMaster

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]

Originally Posted by onekmilesbehind

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]

Originally Posted by Nicog

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

[ryrynz]

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

[Asmodian]

One day everyone will be trained.

[jkauff]

Originally Posted by Asmodian

One day everyone will be trained.

Except for the rebels, of course, who just enjoy annoying ryrynz.

[Jinkai]

Originally Posted by huhn

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_b...telXfj9JIHsGdj (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 jkauff

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
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.p...13#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.