AMD, Intel and Nvidia driver issues and last recommended version

[whitestar999]

The list at the first page mentions drivers needed for RTX series but what about 16xx series & 16xx super cards.

[el Filou]

16 series use the same architecture as 20 series, just with raytracing disabled. The display output features are the same.

[aufkrawall]

16 series use the same architecture as 20 series, just with raytracing disabled.
Tensorcores are missing too, but they seem to be useless for realtime calculations anway.

[whitestar999]

Is it possible to run 16xx series card on win 8.1 with a driver having correct hdr pass-through to use with madvr or does it necessarily needs win 10?

[Klaus1189]

The list at the first page mentions drivers needed for RTX series but what about 16xx series & 16xx super cards.

Added to first post ;)

@all:
Nvidia seems to have fixed the micro stutter issue in newer driver versions, does anybody know, which version excactly?
I want add this info to the first page.

[huhn]

how do you add an information about this if it is not a universal issue?

[Klaus1189]

I thought of adding the info, because of post #701, #702 and #703. I thought I should let users know in the summary that Nvidia seems to have fix it. But if other Nvidia users still have issues with micro stutters, of course I can not add it.

So people with an Nvidia RTX card please let me know if you have still micro stutter issues with 436.48 and above.

[whitestar999]

Added to first post ;)

@all:
Nvidia seems to have fixed the micro stutter issue in newer driver versions, does anybody know, which version excactly?
I want add this info to the first page.
Thanks :) One more query,size of drivers with same version number is different for win 10 & win 7/8 so does this mean the list applies to all or specifically only to win 10.

[SamuriHL]

Added to first post ;)

@all:
Nvidia seems to have fixed the micro stutter issue in newer driver versions, does anybody know, which version excactly?
I want add this info to the first page.

That was my question, as well, and I don't think we got a definitive answer. I'm just happy it's fixed. For sure the latest driver is working very well.

[Calvi]

Stutter gone for me with 441.08 (cannot say exactly which version before fixed it though)

[cremor]

I've read some more and it seems like both 440.97 and 441.08 have elevated black levels in HDR. This should be noted in the first post.

Sources:
https://www.avsforum.com/forum/40-oled-technology-flat-panels-general/3057634-2019-c9a-e9-owner-s-thread-no-price-talk-268.html#post58721970
https://www.avsforum.com/forum/40-oled-technology-flat-panels-general/3057634-2019-c9a-e9-owner-s-thread-no-price-talk-270.html#post58724510
https://www.avsforum.com/forum/40-oled-technology-flat-panels-general/3057634-2019-c9a-e9-owner-s-thread-no-price-talk-281.html#post58747886
https://www.avsforum.com/forum/40-oled-technology-flat-panels-general/3057634-2019-c9a-e9-owner-s-thread-no-price-talk-283.html#post58750740

[Klaus1189]

@cremor:
Thanks for the info, I added it to the first post

[VBB]

I've been using the latest drivers with RGB full 8-bit, non-PC mode, and black levels are spot on in both SDR and HDR.

[Manni]

I've been using the latest drivers with RGB full 8-bit, non-PC mode, and black levels are spot on in both SDR and HDR.

That's one of the main reasons for using 8bits. Levels are often hosed in 12bits, and often different between SDR and HDR.

[nevcairiel]

Sounds to me like black levels work as expected, but people get messed up Full vs Limited for some reasons, which in my experience is primarily an issue only on TVs which dont advertise full range support on their edid

[Manni]

Sounds to me like black levels work as expected, but people get messed up Full vs Limited for some reasons, which in my ezpet is primarily an issue only on TVs which dont advertise full range support on their edid

Not in 12bits. There is often a mismatch between the HDR and SDR levels, and you have to actually change the range in madVR to get the proper levels in most of the recent drivers and set it to the WRONG setting in madVR to get the correct levels. I use limited so I don't rely on full range support to get the correct levels. Mostly it s case of keeping GPU on full and setting madVR to 0-255 when the display is actually expecting 16-235. Not ideal, but if you don't do that the levels are simply wrong, at least here in 12bits with any driver more recent than 398.11 (possibly even 385.28).

I haven't tested this recently as I've been using 8bits for a while, but it's a known issue with 12bits. nVidia just has crap drivers and is unable to fix something without breaking (or retiring in the case of 3D) something else.

They are very lucky that others are not significantly better. :rolleyes:

[Klaus1189]

nVidia just has crap drivers and is unable to fix something without breaking (or retiring in the case of 3D) something else.

They are very lucky that others are not significantly better. :rolleyes:

Couldn‘t have said it better :devil:

[huhn]

Sounds to me like black levels work as expected, but people get messed up Full vs Limited for some reasons, which in my experience is primarily an issue only on TVs which dont advertise full range support on their edid

nvidia ignores this.

nvidia choices limited or full range for HDMI device on only one thing the head line where the resolution is listed in there driver.
if it is listed under SD, HD, UHD it will by default use limited range even on gaming screens if the resolution is selected under "PC" it will use full range by default.

[nevcairiel]

nvidia ignores this.

nvidia choices limited or full range for HDMI device on only one thing the head line where the resolution is listed in there driver.
if it is listed under SD, HD, UHD it will by default use limited range even on gaming screens if the resolution is selected under "PC" it will use full range by default.

Except thats not true. On my Sony TV, which reports proper Full range support, it'll always pick Full range, even on typical TV resolutions like 1080p, which is listed in the section you speak of.

[huhn]

beware it will remember it to trigger it again you have to ddu.

i have tested it on about 10 screens a sony TV was that list too well 2 but very very similar from the same year.

on default your sony TV needs limited range like every other screen too anyway.

[nevcairiel]

on default your sony TV needs limited range like every other screen too anyway.

I think only I know how my screen actually behaves. :p
Because its actually smart and fully adapts to the input signal, I've never had to change the range config in the screen, and if I change in the control panel from full to limited the visual look doesn't change because it auto-adapts. HDMI has all the image properties in metadata, unfortunately the majority of TVs quite simply ignore it and expect some default mode.

[huhn]

not saying your screen doesn't but the only ways for a screen to change a setting in the nvidia control panel is by pretending to be a new different screen or by HDMI content type which is again not properly supported. there is a very good reason not to do that.

auto level support is not that rare but not the point what nvidia choices to send.

[kostik]

https://www.nvidia.com/en-us/geforce/news/red-dead-redemption-2-pc-game-ready-driver/

Nvidia Geforce 441.12 WHQL driver.

This latest GeForce Game Ready driver ( 441.12) enables G-SYNC Compatible support on LG’s 2019 B9, C9 and E9 4K OLED TVs.

[Klaus1189]

I heard G-Sync shouldn't be used with madVR. It is designed for gaming, but brings trouble with madVR or general video playing, isn't it?

Should I leave the elevated level info on the two drivers or should I remove it, or maybe add only when using 12 bit if I understood it correctly.

[cremor]

Sounds to me like black levels work as expected, but people get messed up Full vs Limited for some reasons, which in my experience is primarily an issue only on TVs which dont advertise full range support on their edid

If that's the case, why would those same people report that going back to older driver versions fixes the elevated blacks?

I heard G-Sync shouldn't be used with madVR. It is designed for gaming, but brings trouble with madVR or general video playing, isn't it?
Yes, G-Sync messes with madVR and should be disabled. But you don't have to disable it completely. The driver actually automatically disables it for some known executables of media players like MPC-HC. For players that are not handled by the driver by default you can use nvidiaProfileInspector.

Should I leave the elevated level info on the two drivers or should I remove it, or maybe add only when using 12 bit if I understood it correctly.

According to this post (https://www.avsforum.com/forum/40-oled-technology-flat-panels-general/3057634-2019-c9a-e9-owner-s-thread-no-price-talk-268.html#post58721970) 8 bit is affected too. You can more clearly see it in the older version of the post, which is still available in the quote here (https://www.avsforum.com/forum/40-oled-technology-flat-panels-general/3057634-2019-c9a-e9-owner-s-thread-no-price-talk-270.html#post58724510).

edit:
Found a new post: https://www.avsforum.com/forum/40-oled-technology-flat-panels-general/3057634-2019-c9a-e9-owner-s-thread-no-price-talk-295.html#post58773938
So Nvidia officially confirmed the black level bug and 441.12 is still affected, but it seems like it only affects LG OLEDs.

[Klaus1189]

AMD released new Radeon Driver 19.11.1

[Nastenka]

Yes, G-Sync messes with madVR and should be disabled. But you don't have to disable it completely. The driver actually automatically disables it for some known executables of media players like MPC-HC. For players that are not handled by the driver by default you can use nvidiaProfileInspector.


Is the automatic disabling a new thing? I noticed that with an older Studio driver I had to set MPC-HC to Fixed refresh rate manually, while on this current driver set the option is greyed out and says "not supported for this application".

[cremor]

I don't know when this was added to the driver. I've bought my first G-Sync monitor in December 2018 and back then it was already there. Since "studio" drivers are way newer, they should have already supported that.

[Decalicatan_Decalicatan]

Hi!

Do you know if there an issue with the recent nvidia drivers when playing a HDR video with "Compromise on HDR tome & gamut mapping accuracy" unchecked?

I was previously using Nvidia Driver 430.53 for my GTX 1070 and everything was fine when I played a HDR file (mpc-be with madvr "Compromise on HDR tome & gamut mapping accuracy" unchecked | SDR monitor)

I have updated the drivers to 436.48, and now when I play a HDR file the image is nearly completely dark. If I check "Compromise on HDR tome & gamut mapping accuracy" the image is watchable again.
But of course I'd prefer not compromise on HDR tome & gamut mapping accuracy.

madvr version is the latest one available on avsforum.

Thanks in advance.

[Manni]

Hi!

Do you know if there an issue with the recent nvidia drivers when playing a HDR video with "Compromise on HDR tome & gamut mapping accuracy" unchecked?

I was previously using Nvidia Driver 430.53 for my GTX 1070 and everything was fine when I played a HDR file (mpc-be with madvr "Compromise on HDR tome & gamut mapping accuracy" unchecked | SDR monitor)

I have updated the drivers to 436.48, and now when I play a HDR file the image is nearly completely dark. If I check "Compromise on HDR tome & gamut mapping accuracy" the image is watchable again.
But of course I'd prefer not compromise on HDR tome & gamut mapping accuracy.

madvr version is the latest one available on avsforum.

Thanks in advance.

This is because you have not disabled measurements files.

I use the latest nVidia driver and there is no issue with that option.

Just disable all measurements files in the configuration section at the end of MadVR settings. They are not supported with the latest test builds.

If you don't use measurements files, then it might be something else, but it's not the driver.

[Grimsdyke]

If Manni's advise does not solve this you should also check if 'don't measure HDR frame peak luminance' is also unchecked.

[Decalicatan_Decalicatan]

This is because you have not disabled measurements files.

Just disable all measurements files in the configuration section at the end of MadVR settings. They are not supported with the latest test builds.
.

Thank you! You were absolutely right.

I didn't get the news about the measurements files. Change occurs so fast with MadVR beta in the "other forum" so it is very easy to miss relevant info.

Regards

[TechnoPeasant]

I wonder if the recent issues with the Nvidia drivers are what I'm experiencing too. I'm unable to watch any HDR content using RGB at all. No matter what I do, the black levels wash out. Instead, I have to switch to ycbr 4:4:4, 12-bit, limited to maintain correct black levels, which I'm sure is less than ideal.

I think this all happened after a Windows update, but I'm not entirely sure. Unfortunately, on my Vizio PQ65, I'm only able to change color space manually, and not video levels.

Sucks when you have everything setup just right, and some crap Windows update ruins things.

If any of you have any suggestions, as to how I can better work around this issue, please let me know. I saw someone mentioned having to choose "PC" resolutions instead of the UHD stuff, but that category of resolutions doesn't show up in NVCP.

[Warner306]

"Color Space" in the Vizio picture menu should be set to "RGB." That is all I know. I don't know if that setting currently exists on the newest Vizio models, though.

[TechnoPeasant]

Yeah, color space is there, and I can set it to RGB, but unfortunately the result is still washed out.

[Warner306]

This is with the Nvidia control panel set to output RGB 0-255?

Maybe the display now has some type of levels adjustment?

[TechnoPeasant]

Yeah, RGB 0-255. That's what I'm thinking, that the TV is trying to be too helpful. That said, the Nvidia driver issues sound very similar.

[TechnoPeasant]

Can confirm, the latest Vizio 4.0 firmware did nothing. I suspect the latest Windows 10 update has something to do with this, and the nvidia driver hasn't accounted for it. Bummer.

[huhn]

AMD got a new driver too: https://www.amd.com/en/support/kb/release-notes/rn-rad-win-19-11-2
the changes are minimal at best. i will test DXVA2 stuff later.

edit: DXVA2 levels are broken
deint is still broken
i don't test dxva2 native decode anymore until they fix the very obvious stuff.

[NikosD]

I don't test dxva2 native decode anymore until they fix the very obvious stuff. As long as AMD says that "Movies & TV" works fine with HW acceleration, they will probably don't bother much to comply with other players.
The other players should comply to AMD, according to AMD.

[huhn]

it effects windows media player.

[hotripper]

Added to first post ;)

@all:
If that does not eliminate the stutter for you, set how many video frames shall be presented in advance to 1 (madVR settings->rendering->windowed mode and/or exclusive mode).

I found that fix.
Not that I want a cookie but yeah :D

[littleD]

it effects windows media player.What is your OS? On my win 10 machine WMP is half working garbage and i got used to this.

[huhn]

w10 1909.
i personally don't vare about WMP but that doesn't mean AMD shouldn't specifically if they have broken it and there QA is none existent.

[hogtop]

i have 441.20 nvidia 1050ti

and the Samsung Q9FN HDR TV screen
i must point out that HDR looks bad with MPC-HC x64
is the player can playing HDR ?

In Blue Ray the situation is much better

[Klaus1189]

You need madVR and can choose what you want:
- passthrough the HDR metadata to the screen (OSD will show HDR)
- tonemap the HDR metadata with madVR (OSD will not show HDR, becuase the TV isn'T receiving HDR metadata anymore, because madVR did the tonemapping)

MPC-BE can also convert HDR to SDR with internal filters, without the need of madVR and MPC-BE development is very active. See its thread for more infos or questions:
Media Player Classic - BE Win32/x64
Here you can download latest Nightly build, don't worry -> rocksolid
https://yadi.sk/d/r7JYQ2NjHvE4lA/Beta/1.5.4
https://yadi.sk/d/hlf1lfC8mKU58

[Klaus1189]

Nvidia released 441.28 Studio driver

[Klaus1189]

AMD released new Radeon Driver 19.11.3

[zapatista]

looking at the driver feedback information: for my nvidia 1060 gfx card, would this still be the best driver to use for madvr ? (win 8.1 64 bit)

398.11 2018-06-05 last version with correct HDR passthrough newer versions passthrough bogus metadata, for details see here | Notice: It seems that madVR doesn't switch to HDR mode anymore with newer updates of Windows 10

i mainly send video to my sony 1080 tv over hdmi in RGB Full

with my gfx card now being a 2 yo model, i would assume newer driver versions would mainly add features for the newer card models

[huhn]

why would you care about HDR passthrough if you don't have a HDR device.

if you want the last version with 3D support use that old driver and if not the newest is fine for SDR playback as far as everyone knows.

BTW. 3D is still "possible" with the newest driver but i said that before.