AMD, Intel and Nvidia driver issues and last recommended version

[JonnyVee]

Has anyone tested a 3080 or 3090 GPU yet with HDR - SDR? I can only get MPC-BE (1.5.5.5433) with its internal filters to convert HDR properly.

If I use anything with LAV filters such as MPC-HC or kodi DSplayer I get extreme blown highlights when in Fullscreen windowed and FSE. However, it’s fine when windowed. This is with the older internal LAV and newer 0.74.1 via external.

The attached pictures show the (1] excess highlights (not sure if this is the correct term) when fullscreen, (2) correction to normal when windowed, and (3) the correct conversion using MPC-BE’s internal filters.

This happens with MPC-BE as well when I use LAV External with 0.74.1. However, its fine with the included internal filters.

I’m using an EVGA 3080 FTW3 Ultra and this occurs with 456.38 and 456.71 drivers. I’ve also tried 8 and 10 bit, and RGB &YCbCr.

[Manni]

Originally Posted by SamuriHL

That's seriously crazy that you have such wildly different HDR results on the 1080ti than I do on my RTX. What the hell is nVidia doing lately.....sigh

Not really, it's a different architecture and most probably different drivers internally, even if the package is the same. Also they tend to spend more testing time on the more recent architecture with recent drivers, so it makes sense. There is often a point where it's preferable to stop updating, as only the new gens are improved, the older ones can get worse.

In the latest drivers, the 1080 GTX gen are the last supported.

Originally Posted by ryrynz

Was a reply to chros

Manni did you use madVRs calculated values with CRU for 24hz?

Ah sorry, that makes sense

No I use my own values for the JVC rs2000. madVR has stopped working a long time ago re refresh rate optimisation here.

I get no drop/repeat for more than 3 hours or more (often no drop/repeat after a while) with 442.74 + CRU, so I'm a happy camper.

It's really nice to have the nVidial cPanel working normally again. Something had messed it up (I think one of the "bring 3D back" packages) and nothing could bring it back.

If there is no downside, that alone was worth the upgrade to 2004.

By the way, even with 442.74 I occasionally get the wrong HDR mode, but if I select HDR passthrough and then SDR pixel shader, I get the correct mode, contrary to the newest drivers that stay stuck in the wierg HDR null metadata mode.

[SamuriHL]

Originally Posted by Manni

Not really, it's a different architecture and most probably different drivers internally, even if the package is the same. Also they tend to spend more testing time on the more recent architecture with recent drivers, so it makes sense. There is often a point where it's preferable to stop updating, as only the new gens are improved, the older ones can get worse.

In the latest drivers, the 1080 GTX gen are the last supported.

I suppose there is that but it's not like the 10xx cards are that old. Good god.

[chros]

Originally Posted by Manni

By the way, even with 442.74 I occasionally get the wrong HDR mode, but if I select HDR passthrough and then SDR pixel shader, I get the correct mode, contrary to the newest drivers that stay stuck in the wierg HDR null metadata mode.

Really?! I just spent on it 2 hours this morning Bloody hell, what a mess Thanks for reporting, I'll keep an eye on it then.
Maybe we should go way back to 430.53... Unfortunately I can't easily test HDR metadata, if I could then I'd go back and try bunch of them.

@JonnyVee, upload the images to an external image host and link them here.

[VBB]

Manni is correct as far as support when it comes to the Nvidia Studio Drivers. The Game Ready Drivers still offer full support all the way back to the 600-series:

"Effective April 12, 2018, Game Ready Driver upgrades, including performance enhancements, new features, and bug fixes, will be available only for desktop Kepler, Maxwell, Pascal, Volta, Turing and Ampere-series, as well as for systems utilizing mobile Maxwell, Pascal, and Turing-series GPUs for notebooks."

[SamuriHL]

That's right I forgot he's using studio drivers. I've been using game ready lately cause I'm getting ready for Cyberpunk 2077.

[blu3wh0]

So I just upgraded from my 1080 Ti to a 3080 and finally got around to testing MadVR. Good news, the issues with HDR on my 1080 Ti where I had to open the file twice to get HDR properly working has been resolved, although it only seems to work in fullscreen and any opening of the menu or looking at the status bar breaks it, but at least it switches really quickly. However, the card introduced really annoying micro stutters when playing at 23Hz mode (fullscreen windowed mode, in normal windowed it's fine). The stutter becomes significantly worse if you just move the mouse or start bringing up the menu. Switching to 60Hz with smooth motion does seem to mostly remove the problem, but I think it still stutters a bit. At 100Hz it's no longer noticeable to me. I believe the solution previous brought up for the 20 series for a similar problem was to set present ahead frames to 1, and this appears to have alleviated the problem. For now, this setting and watching at 60Hz instead is a good solution, but this really should not be a problem. It seems like it's always one step forward and two steps back with these things...

[JonnyVee]

Originally Posted by chros

Really?! I just spent on it 2 hours this morning Bloody hell, what a mess Thanks for reporting, I'll keep an eye on it then.
Maybe we should go way back to 430.53... Unfortunately I can't easily test HDR metadata, if I could then I'd go back and try bunch of them.

@JonnyVee, upload the images to an external image host and link them here.

Here’s links to the full size images

https://imgur.com/e7S8uoQ

https://imgur.com/Fucko6q

https://imgur.com/pWeCDJ6

[ryrynz]

Originally Posted by SamuriHL

I suppose there is that but it's not like the 10xx cards are that old. Good god.

True but he has a point. Every update has that possibility to potentially break things that haven't been tested and given these changes are generally made for newer cards there's likely greater chance for breakage of functionality for older cards. Still on 1809 and 385.28 for exactly this reason, it just works.

[SamuriHL]

Sure but the alternative point of view is that it should be a very well known quantity at this point. But I get it.

[chros]

Originally Posted by ryrynz

Still on 1809 and 385.28 for exactly this reason, it just works.

Really? Do you have multimonitors, e. g. TV + monitor? It didn't work here e.g. after sleep, I got blank screen on monitor if video played only on TV. This was flawless with 1607.
That's why I upgraded the driver when SamuriHL stated that 442.92 is good again.

[el Filou]

Originally Posted by chros

I went back as well to 442.74 [...] I noticed 1 issue (?) straight away, that I haven't before (not even with 442.92 SD):
- 12bit nv output
- madvr OSD is enabled
- mpc-be/hc fullscreen window: madvr reports 10bit
- but when seekbar comes up at the bottom: madvr reports only 8bit!

I think it's normal behaviour because 10bit only works in fullscreen windowed, and once you display GUI elements it swtiches to windowed instead of fullscreen windowed. At least that was the case in 2018: https://forum.doom9.org/showpost.php...ostcount=50141

[Klaus1189]

I think it will take some time till I get one ...
https://www.proshop.de/RTX-30series-overview

And I am still open for RDNA2

[SamuriHL]

I'll continue to wait until the cards actually exist in the real world. LOL

[chros]

Originally Posted by chros

Really?! I just spent on it 2 hours this morning Bloody hell, what a mess Thanks for reporting, I'll keep an eye on it then.
Maybe we should go way back to 430.53... Unfortunately I can't easily test HDR metadata, if I could then I'd go back and try bunch of them.

Yep, after a week without reboot the 442.74 is shite as well
Although I didn't have the SDR in HDR issue as before, but madvr doesn't change the metadata for sure when modifying the display peak nits (checked with the second code value on B8).
So, what's next?

Originally Posted by ryrynz

True but he has a point. Every update has that possibility to potentially break things that haven't been tested and given these changes are generally made for newer cards there's likely greater chance for breakage of functionality for older cards. Still on 1809 and 385.28 for exactly this reason, it just works.

You forgot to answer to the question below, thanks.

Originally Posted by chros

Really? Do you have multimonitors, e. g. TV + monitor? It didn't work here e.g. after sleep, I got blank screen on monitor if video played only on TV. This was flawless with 1607.

[Klaus1189]

Originally Posted by chros

Yep, after a week without reboot the 442.74 is shite as well
Although I didn't have the SDR in HDR issue as before, but madvr doesn't change the metadata for sure when modifying the display peak nits (checked with the second code value on B8).
So, what's next?

What Nvidia driver is recommended now?

[SamuriHL]

I'm still recommending 456.71 which has proper metadata, good clocks, and a good audio driver. But I know not everyone agrees with that.

EDIT: FOR RTX CARDS cause who cares about GTX. LOLOLOLOL

[chros]

How would I know? That's what we try to find out...

[Manni]

Originally Posted by SamuriHL

I'm still recommending 456.71 which has proper metadata, good clocks, and a good audio driver. But I know not everyone agrees with that.

You can’t make the same recommendation for GTX and RTX...

[SamuriHL]

Originally Posted by Manni

You can’t make the same recommendation for GTX and RTX...

Then Klaus1189 needs to understand that and will have to split the list. Which makes maintaining it slightly more complicated. I'm not saying I disagree, just that it needs to be well understood that RTX and GTX cards should be treated as completely different.