madVR - high quality video renderer (GPU assisted)

[FDisk80]

Originally Posted by Warner306

There is no secret for success with custom resolutions. You are at the mercy of the driver and the compatibility of your equipment. I was able to fix my issue by running DDU and reinstalling the drivers. But others haven't been so fortunate.

That's just it, I could apply the same timings I'm trying to apply with earlier nvidia drivers. But with all latest ones it is not possible anymore.

There is obviously some driver limitation. Even the error that pops out says exactly this.



The question is maybe it's possible to override those limitations with madVR or with some registry tweaks.

[Clammerz]

Originally Posted by FDisk80

The question is maybe it's possible to override those limitations with madVR

If it were possible, madshi would have implemented those overrides already.

As for other workarounds and "tweaks", you are at the mercy of the drivers as Warner states.
People have had success using DDU and re-installing. Others have had to use other versions, and some simply cannot get it to work at all.
One thing that you have probably already done: make sure to switch to a mode that you are not trying to modify/add. Switch to a completely different resolution in Windows before trying the custom resolution steps. Making sure to remove any existing customizations.

[FDisk80]

Originally Posted by Clammerz

If it were possible, madshi would have implemented those overrides already.

As for other workarounds and "tweaks", you are at the mercy of the drivers as Warner states.
People have had success using DDU and re-installing. Others have had to use other versions, and some simply cannot get it to work at all.
One thing that you have probably already done: make sure to switch to a mode that you are not trying to modify/add. Switch to a completely different resolution in Windows before trying the custom resolution steps. Making sure to remove any existing customizations.

Yes, tried DDU, clean installs... That didn't work.
Switch to a completely different resolution before applying the custom timings for 1080p. I did not try that. I only tried from a different refresh rate. That is a good idea. Will try that.

[ashlar42]

Originally Posted by jkauff

I think the suggestion was based on the fact that the 1050ti has an on-board hi-res decoder, while the 1060 does not.

This is not true.
Harware video decoding is exactly the same in 1060 and 1050Ti (VP8 generation).

Thanks to everybody chiming in in the 3GB vs. 6GB matter.

[huhn]

they have a relative small difference.

the 1030, 1050, 1050 ti and 1080 ti have a "better" decoder that can decode VP9 profile 2.

[Ver Greeneyes]

I've worked around the Windows 10 April 2018 Update problem (with the queues not filling up) by making some dummy profiles that use the inexpensive default scaling algorithms, and activating them "if (1 == 1)" (which is obviously always true). Hopefully madshi will be able to work around Microsoft's latest buffoonery.

[mrmojo666]

Originally Posted by Ver Greeneyes

I've worked around the Windows 10 April 2018 Update problem (with the queues not filling up) by making some dummy profiles that use the inexpensive default scaling algorithms, and activating them "if (1 == 1)" (which is obviously always true). Hopefully madshi will be able to work around Microsoft's latest buffoonery.

In my system, to get rid of problems introduced by last spring update i needed just to uninstall AMD 18.4.1 (they claim this driver is for spring update) using DDU, then reistalled latest official amd 18.2.1. Now all goes perfectly again and i see lower timing.

[Ver Greeneyes]

Originally Posted by mrmojo666

In my system, to get rid of problems introduced by last spring update i needed just to uninstall AMD 18.4.1 (they claim this driver is for spring update) using DDU, then reistalled latest official amd 18.2.1. Now all goes perfectly again and i see lower timing.

Interesting. Unfortunately I have an Nvidia card (GeForce GTX 1080) and I see the problems both with pre-update drivers (391.35) and post-update drivers (397.55).

[Betroz]

Originally Posted by Ver Greeneyes

Interesting. Unfortunately I have an Nvidia card (GeForce GTX 1080) and I see the problems both with pre-update drivers (391.35) and post-update drivers (397.55).

My solution has been to use an older MadVr build and use NNEDI3 128 settings. I hope Madshi have the time to look into this when I comes back.

[mclingo]

Originally Posted by mrmojo666

In my system, to get rid of problems introduced by last spring update i needed just to uninstall AMD 18.4.1 (they claim this driver is for spring update) using DDU, then reistalled latest official amd 18.2.1. Now all goes perfectly again and i see lower timing.

Ive had issues with everything 18.3x onwards, 18.2.2 is my current stable.

I tried 18.4.1 thought, its shafted FSE for me, black screens and loss of HDMI all over the place.

With not being a gamer though its fine to just sit on an old driver and just enjoy my HTPC.

[mrmojo666]

Originally Posted by mclingo

Ive had issues with everything 18.3x onwards, 18.2.2 is my current stable.

I tried 18.4.1 thought, its shafted FSE for me, black screens and loss of HDMI all over the place.

With not being a gamer though its fine to just sit on an old driver and just enjoy my HTPC.

yes i remember our discussions.
the 18.4.x are not only for games , they should support 1803 win10 and should activate DRM for 4k netflix. But they mess all things with 1803 plus netflix still 1080 lol

[FDisk80]

Originally Posted by Clammerz

Switch to a completely different resolution in Windows before trying the custom resolution steps. Making sure to remove any existing customizations.

Tried it now, no go. Still same error. "Rejected by driver."
Oh well, it was a long shot.

[jkauff]

Originally Posted by FDisk80

Tried it now, no go. Still same error. "Rejected by driver."
Oh well, it was a long shot.

I also have a GTX 1080. I get around this problem using the utility CRU (which stands for "Custom Resolution Utility"). I use it to create a 23.976 custom resolution (and others as well), which madVR can then use and optimize. It works at the OS level, not the GPU driver level, and so bypasses the Nvidia quirk.

[har3inger]

Guys, I found out the solution for the FSE flicker/freeze on 1803.

It's Focus Assist bugging out. Even if it's off, you need to make sure all the options underneath it are disabled. You can find the relevant page by typing focus assist into the start menu.

[FDisk80]

Originally Posted by jkauff

I also have a GTX 1080. I get around this problem using the utility CRU (which stands for "Custom Resolution Utility"). I use it to create a 23.976 custom resolution (and others as well), which madVR can then use and optimize. It works at the OS level, not the GPU driver level, and so bypasses the Nvidia quirk.

Hmm, I tried it before but I was getting the same error with madVR.
Can you share please what you did in CRU to override this issue?

Maybe I did something wrong in CRU.

[jkauff]

Originally Posted by FDisk80

Hmm, I tried it before but I was getting the same error with madVR.
Can you share please what you did in CRU to override this issue?

Maybe I did something wrong in CRU.

I don't do anything special, except make sure the OS is showing only the display's native resolutions--no madVR, Nvidia, or CRU custom ones--before I start. The CRU "reset-all.exe" will accomplish that.

I'm using a DisplayPort connection. If you're using HDMI, make sure the HDMI block is included in your CRU custom res. CRU should add it automatically, but double-check.

[FDisk80]

Originally Posted by jkauff

I don't do anything special, except make sure the OS is showing only the display's native resolutions--no madVR, Nvidia, or CRU custom ones--before I start. The CRU "reset-all.exe" will accomplish that.

I'm using a DisplayPort connection. If you're using HDMI, make sure the HDMI block is included in your CRU custom res. CRU should add it automatically, but double-check.

What do you mean by HDMI block?

[LigH]

Probably a display control data block...

[Siso]

Originally Posted by jkauff

I don't do anything special, except make sure the OS is showing only the display's native resolutions--no madVR, Nvidia, or CRU custom ones--before I start. The CRU "reset-all.exe" will accomplish that.

I'm using a DisplayPort connection. If you're using HDMI, make sure the HDMI block is included in your CRU custom res. CRU should add it automatically, but double-check.

In my case using displayport, I have to always add extension block, new CRU versions don't add it automaticly.

[Clown shoes]

Originally Posted by jkauff

I don't do anything special, except make sure the OS is showing only the display's native resolutions--no madVR, Nvidia, or CRU custom ones--before I start. The CRU "reset-all.exe" will accomplish that.

I'm using a DisplayPort connection. If you're using HDMI, make sure the HDMI block is included in your CRU custom res. CRU should add it automatically, but double-check.

Where does one check to see if the HDMI block is included?