AMD, Intel and Nvidia driver issues and last recommended version

[clsid]

The known issues list of NVIDIA driver contains this for a long time already:
[NVIDIA Ampere GPU]: With the GPU connected to an HDMI 2.1 audio/video receiver, audio may drop out when playing back Dolby Atmos.

You can submit bug report to NVIDIA HERE (https://forms.gle/kJ9Bqcaicvjb82SdA).

[ryrynz]

Try performing a proper uninstall of your Nvidia drivers with DDU.

[Filmgeek47]

Any issues with the latest nvidia driver? Just clean installed kodi/MadVR and now the system seems to be stuck outputting srgb color space instead of BT2020 or 709.

[huhn]

sRGB and bt 709 have the same colorspace so you have to be more detailed when you share information.

[SamuriHL]

Sweet. That's a welcome fix.

[clsid]

AMD Adrenalin 22.8.1 has this in its changelog:
HDR is no longer compatible with 10-Bit Pixel Format. For the best user experience with HDR displays, it is recommended to disable 10-Bit Pixel Format in AMD Software: Adrenalin Edition Graphics Settings.
To clarify, this does not refer to or apply to the "color depth" setting in display settings.
It refers to "10-Bit Pixel Format" in Graphics > Advanced, which is for legacy OpenGL applications.
So not relevant for video playback.

[mclingo]

cheers for the info

[Goeggel]

Are there any known issues with the Nvidia GameReady 516.94 driver?

I have been using 511.79 for the last couple of months in gaming and watching MKVs without any issues whatsoever (RTX 2070 Super, Win10).
After updating to 516.94, gaming is fine, but MKVs are stuttering randomly from time to time.

Update: I am now back to 511.79 with just installing them over the 516.94 drivers -> no more stuttering in MKVs.

[Balling]

The known issues list of NVIDIA driver contains this for a long time already:


You can submit bug report to NVIDIA HERE (https://forms.gle/kJ9Bqcaicvjb82SdA).

This is a completly different bug and anyway this is due to dumb people not understanding that EARC is pc --> TV -> AVR, not PC -> AVR -> TV, besides bug is not present with Intel gpu going to AVR.

[Balling]

Any issues with the latest nvidia driver? Just clean installed kodi/MadVR and now the system seems to be stuck outputting srgb color space instead of BT2020 or 709.

How would you know that? HDMI mandates BT.2020 primaries when doing PQ (DCI-P3 and P3-D65 are only when SDR curve is used, PQ prohibits it per spec). So there is no way to know that. Also desktop is still not color managed on the input side, now thankfully we have SDR -> HDR upconvert including primaries change, but if you use WCG image it will not be applied! Even my dumb galaxy S21 FE does it on Natural profile! Not talking about MacOS that always supported it in every app and on desktop.

In fact samsung browser correctly does those https://www.wide-gamut.com/test and soon css will support p3 color too in Chrome (Safari already supports it)!

[mclingo]

dont feed the troll

[Plutotype]

Hi folks,
Thanks for the PDF, but reading it and the last 10 pages of this thread I could not figure out what is the last recommended Nvidia, AMD and Intel driver version ( madvr / JRVR user here ) and for which GPU/OS.
Thanks
Pluto

[Klaus1189]

Latent Nvidia is fine. AMD has Problems described in Post 1, other than that nothing to worry now.

Back when I startet the thread both Nvidia and AMD hat lots of problems.

[chros]

Take a look.at my signature what I use on Win10 1809.

[StainlessS]

Is there perhaps an error in OP PDF version number for 472.47 (there are two of them).
https://i.postimg.cc/nsv4CzC0/a3.jpg (https://postimg.cc/nsv4CzC0)

And from here [Official Advanced Driver Search | NVidia]:- https://www.nvidia.com/Download/Find.aspx?lang=en-uk#
https://i.postimg.cc/SjXvxLmr/b4.jpg (https://postimg.cc/SjXvxLmr)

472.84 from 2nd image seems to be latest standard WHQL Studio Driver, and given same date as the latest 472.47 in pdf, ie 13 Dec 2021.

EDIT: To Below, thanks :)

[Klaus1189]

You are right, I correct it soon, some problems now.

[GTPVHD]

https://blogs.windows.com/windowsexperience/2022/09/20/available-today-the-windows-11-2022-update/
https://www.microsoft.com/software-download/windows11

Windows 11 2022 Update Version 22H2 released, WDDM 3.1 and Shader Model 6.7.

[Balling]

22H2 also has support for HDR calibration with ICC profiles, finally! Color.org people are so slow.

WHY IS THE APP CALIBRATION ONLY min 0.005 NITS!??? Useless, my TV is 0.000006! Yes, PQ 65 is also below 0.00001 and 64 is black body 0 nits perfectly! Crazy!

[SamuriHL]

Only until Arc dies off. :)

[cesar73]

Recommendation needed for Nvidia firmware version without madvr HDR not switching off issue for geforce RTX 3060ti.

My HTPC configuration: Windows 10 LTSC 21H2, Kodi 17.7 dsplayer, madvr 0.92.17, lavfilter 0.76.1.25.
and LG oled G1 TV
Madvr settings: hdr passthrough, windowed mode ( had display issue with full screen exclusive)

I tried randomly different versions of nvidia firmwares compatible with rtx3060 ti cards ( with clean ddu driver deletion in between): 462.65 , 512.96 , and latest 516.94

Always same hdr issue: hdr activated correctly when video starts but remained enabled when video stops making kodi gui color saturated.

Any help will be appreciated

[brazen1]

Recommendation needed for Nvidia firmware version without madvr HDR not switching off issue for geforce RTX 3060ti.

My HTPC configuration: Windows 10 LTSC 21H2, Kodi 17.7 dsplayer, madvr 0.92.17, lavfilter 0.76.1.25.
and LG oled G1 TV
Madvr settings: hdr passthrough, windowed mode ( had display issue with full screen exclusive)

I tried randomly different versions of nvidia firmwares compatible with rtx3060 ti cards ( with clean ddu driver deletion in between): 462.65 , 512.96 , and latest 516.94

Always same hdr issue: hdr activated correctly when video starts but remained enabled when video stops making kodi gui color saturated.

Any help will be appreciated

Using Nvidia 517.48 with official Kodi v20 passing through madVR HDR mode engages when MPC-BE video is started and disengages when video has stopped.

Fwiw, I use the official Kodi internal VideoPlayer for HDR because there is no need for madVR when passing through. HDR mode engages and disengages using Windows HDR and/or Nvidia HDR and video is identical because it's passed through.

Besides, official Kodi handles iso's complete with menus. 17.7 DSP is getting pretty long-in-the-tooth. Expect problems imo.

[jayer]

I'm trying to figure out if any of the Nvidia drivers will work with my combination of Windows 10 21H1 and an RTX 3080 (12GB version) without breaking HDR? So far, every driver I've tried presents the 442.92 bug where SDR videos opened after playing an HDR video get played as HDR too. Makes me miss my old RTX 2080 (well, not really).

If non of the approved drivers for my 3080(12GB) can correctly handle the HDR/SDR switching, could I modify the installation file for one of the older drivers, like 442.74? Or would I likely cause even worse problems with my graphics card by trying to force it to use an older driver that isn't officially supported for my hardware?

Thanks in advance for any help/suggestions!

[nevcairiel]

This sounds like the good old madVR bug, not really a driver failure.

[Klaus1189]

Are the RX 5000 issues still present? Also do RX 6000 cards also still have these? I am referring to the ones described in first post.

[mclingo]

I have an RX5700 and have no issues with it at the moment at all, everything works as it should using LAV filters, EVR renderer, MPC renderer, MADVR , HDR SDR etc, however I dont run my TV is PC mode as I use TRUMOTION, this option is greyed out in PC, when i've tried PC mode in the past the colour space is all wrong but I havent tried it for ages, I doubt it will be fixed.

on latest driver, win10

[QBhd]

Same here... 5700XT, no PC mode on the TV (Banding is the main issue for me with PC mode)... everything works amazing

QB

[huhn]

you listed issues are still present.

there are even new ones very very odd ones.
if you take mpc-vr and set it to more than 8 bit internal bit deep the d3d11 and DXVA2 processing falls apart except if you downscale a lot.

this is the driver thread btw. so the pc mode part is well just that.
but nice to see that user here on this forum are now lying into other people faces.

i can only speak for 5000 series issue the 6000 may actually be perfectly fine just like the polaris series.

[Klaus1189]

So is it possible that the issues are also present in new RX 7000 series? All RDNA had these issues.
I just tested my old heater RX480 a few days ago and deinterlacing works, also frame adaptive, but if I watch a interlaced DVD I get some portions of the image where I see interlacing artefacts. These are strage roundly shaped areas. So not good deinterlacer and also bugged. There was or still is a screenshot in this thread, but I must look for it. I don‘t want to put the shitty Polaris back in just for a sreenshot.

I still do not know if those are hardware issues or „only“ software issues.

Also the Intel issue mentioned in post 1 … still present in new Intel driver?

I have also to mention that the Intel versions are driving me crazy! I don’t have an Intel CPU with iGPU here, just an old HEDT 4930k, so if anybody wants to test it, please let me know.

About the versions of Intel drivers, let me know if I should do anything different, I don‘t know any other way, but I don‘t like it that way.

[mclingo]

you listed issues are still present.

there are even new ones very very odd ones.
if you take mpc-vr and set it to more than 8 bit internal bit deep the d3d11 and DXVA2 processing falls apart except if you downscale a lot.

this is the driver thread btw. so the pc mode part is well just that.
but nice to see that user here on this forum are now lying into other people faces.

i can only speak for 5000 series issue the 6000 may actually be perfectly fine just like the polaris series.

whos lying, about what?

[huhn]

So is it possible that the issues are also present in new RX 7000 series? All RDNA had these issues.
I just tested my old heater RX480 a few days ago and deinterlacing works, also frame adaptive, but if I watch a interlaced DVD I get some portions of the image where I see interlacing artefacts. These are strage roundly shaped areas. So not good deinterlacer and also bugged. There was or still is a screenshot in this thread, but I must look for it. I don‘t want to put the shitty Polaris back in just for a sreenshot.

I still do not know if those are hardware issues or „only“ software issues.
you can easily assume a software issue the driver was always able to do bob or just weave(do nothing) and they simple don't care to change that. it was an option back in the CCC days.

the current state deint on win 11 22h2 with amd 22.10.1 5700 xt is:
madVR weave sometimes simple bob
mpc-hc EVR CP weave
mpc-hc EVR weave
mpcvr weave but different with massive ringing (i will retest with a current version)
windows media player bob
windows movies app bob
mpc-be EVR "working" atleast sometimes or it does this: https://abload.de/img/mpc-benhfej.png 16 bit format float.
with 10 bit int it works on the first playback doesn't artifact.

so the deintlacer is still available somewhere.

the level issue is now a different beast. it's now full range all the time. even when set to limited range only tested in mpc-be. so still broken but in a far more acceptable state.

it's kinda odd to see the "best" realtime deinterlacer work after all these years...

BTW. nvidia is also generally buggy with all DXVA and D3D11 processing with RGB output.
they move the chroma to the wrong position it's half or a quarter a subpixel to far to the right. like they move the image by half a subpixel before scaling instead of after scaler.
this bug is very old and very hard to explain to nvidia most user will never see an issue in it.

only tested on a 1060.

[el Filou]

whos lying, about what?I wouldn't say 'lie', but rather incorrect feedback.
Someone asks if the issues listed in the first post are solved, but deinterlacing isn't and some people respond with "everything works", but when you say that it may include things you're not using/have not tested.

[mclingo]

I wouldn't say 'lie', but rather incorrect feedback.
Someone asks if the issues listed in the first post are solved, but deinterlacing isn't and some people respond with "everything works", but when you say that it may include things you're not using/have not tested.

people can only give feedback from their own perspective and if whatever you're playing doesn't exhibit any problems then from your perspective there are no problems and it should not be implied or stated I'm a liar or have even given incorrect feedback, especially as I never actually said the weren't any other problems I just said I didn't have any.

[huhn]

no you have a very specific question with a sample and your answer is everything works general which plain lie.

you don't even have the decency to test this... and mention you didn't test it. but still good enough for a "everything works as it should be" statement.

[mclingo]

The question was - "Are the RX 5000 issues still present", I gave a subjective answer to that question and it was clear to anyone it was, you are the only one losing you childish Sh*t about this as you dont know how to have a grown up conversation with anyone.

[huhn]

thanks for confirming to troll have a nice day.

[Calvi]

I found HDR only worked on the first video play with 526.47 (i.e. would switch to HDR on first play of video, but after closing and opening again would not switch to HDR automatically again)
Going back to 525.25 has fixed it.

I need to install 526.47 again to make sure it wasn’t due to some other issue and haven't done exhaustive testing but wondering if anyone else is seeing the same issue?

Note: Windows 11 22H@ - RTX2700 - MadVR 0.92.17 32bit

[ryrynz]

Might be best to use DDU first if you want to upgrade to that particular driver on your system.

[Calvi]

Always do so that can’t be the cause.

[aquanash]

I just installed 526.47 and HDR switching is working fine, it switches on when playing and switches off when closing without issue multiple times in a row. Maybe the issue is the Win11 22H2 update? I am still running 21H2. After I update to 22H2 I will let you know if it breaks HDR switching for me. One other thing you can try is disabling MPO in the registry.

[aquanash]

I updated my Win11 install to 22H2 and HDR switching is still working fine with the 526.47 driver.

[huhn]

if you have an issue with win 11 h2 please try to install beta 165 and see if it goes away.
the driver version shouldn't matter to the fix bug but still worth a try.

[Calvi]

Thanks for the update, maybe it was something else.
I’ll try again.

[StainlessS]

I updated my Win11 install to 22H2 and HDR switching is still working fine with the 526.47 driver.

There is a later standard than 526.47,
Is there perhaps an error in OP PDF version number for 472.47 (there are two of them).
https://i.postimg.cc/nsv4CzC0/a3.jpg (https://postimg.cc/nsv4CzC0)

And from here [Official Advanced Driver Search | NVidia]:- https://www.nvidia.com/Download/Find.aspx?lang=en-uk#
https://i.postimg.cc/SjXvxLmr/b4.jpg (https://postimg.cc/SjXvxLmr)

472.84 from 2nd image seems to be latest standard WHQL Studio Driver, and given same date as the latest 472.47 in pdf, ie 13 Dec 2021.

EDIT: To Below, thanks :)
And the reply
You are right, I correct it soon, some problems now.
So the Opening post PDF is not yet updated. [I checked it]

Latest Std is
NVIDIA Studio Driver WHQL 472.84 13.12.2021

Advanced nvidia search [better than consumer search <more options> ]:- https://www.nvidia.com/Download/Find.aspx?lang=en-uk#

[Klaus1189]

Updated. Sorry I simply forgot about it. Everything is fine now. :)

[smithjohny039]

Welcome!

In this thread you can check for issues with graphic drivers from AMD, Intel and Nvidia.
This thread is meant for use with madVR and its compatible players like Zoom Player, PotPlayer, KMPlayer, MPC-HC and my personal favourite MPC-BE (https://forum.doom9.org/showthread.php?t=165890).

I had to create an external file, because the first two posts are limited and had no more space for new driver releases.

View PDF (https://drive.google.com/file/d/1gQZLfJ0w5KT7tBHCKZASSVU8vTnyPe2n/view?usp=sharing)

But hey, maybe some Driver Dev may stumble over my thread here, please read this:

AMD
Known limitations of Radeon RX 5000 and 6000 GPUs (older generations are fine):
• Hardware deinterlacing is broken in every driver version -> It is poor quality when applied to
interlaced video and it is not adaptive anymore, which is a NO-GO for HTPC usage.
You can check this issue yourself: Download this short MBAFF sample file (https://drive.google.com/file/d/12wO8NJbIrfa2MD4yVaA38RrBBdziCda8/view)
The Hardware Deinterlacer should be aware that the characters above "WWW.D88.COM" are progressive and should not be deinterlaced, otherwise you will see flickering like in this picture (https://thecapcut.com/capcut-mod-apk/)
See here (https://forum.doom9.org/showpost.php?p=1928654&postcount=2155) for more details
• Color levels (full 0-255 vs. limited 16-235) are broken. That means limited 16-235 which is the standard range for videos are interpreted as 0-255 and this leads to elevated blacks and dimm whites.
This issue can be best seen on displays which want full range 0-255, like TVs in PC Mode (PC mode for full 4:4:4/RGB support, so you do not use color subsampling like 4:2:2 or 4:2:0)
Also overriding the range for test purposes in MPC-BE (video tab -> Output range) does not take effect.
Dear AMD, if any of your driver programmers read this: Please fix this fundamental video bugs .These are there since RX 5000 series launch.

I just tried the Windows default app "Movies and TV" and this app does not support frame adaptive deinterlacer at all. So best is to download MPC-BE and play the sample file. Windows default app "Movies and TV" really sucks.

Sorry Micro$oft, but with all the skilled and well paid developers you can only achieve this? This is ridiculous.

Intel
iGPU Intel UHD 770 in 12 gen CPU is broken for MPC-BE in use with EVR and EVR custom presenter. You get audio but the video is black.
To "solve" the issue is to rename MPC-BE to MPC-HC. Are you serious Intel? Do you really think that is the way of fixing bugs? That is ridiculous for the well paid developers of Intel!
See here for details:
https://sourceforge.net/p/mpcbe/tickets/912/

Nvidia
I am really impressed of what you have done to fix all the HTPC issues of the last 3 years, but I think a little more tweaking of the 23.976 Hz (called 23 Hz, but not 24 Hz!) to get more than 10 hours of no framedrop/repeat like AMD would be nice. I know you can do that.

If the issues still prevail, just try the old version.

[Klaus1189]

If the issues still prevail, just try the old version.

What do you mean? We tested lots of drivers through the months and the issues still persist.
Also on the first version which added support the GPU, so no way to get and older version than FIRST version which supports the GPU.

[x7007]

I've read about MPO , it's a stupid power-saving mode.

https://www.kernel.org/doc/html/next/gpu/amdgpu/display/mpo-overview.html


Note
Keep in mind that MPO is all about power-saving; if you want to learn more about power-save in the display context, check the link: Power.

[Ejziponken]

I found HDR only worked on the first video play with 526.47 (i.e. would switch to HDR on first play of video, but after closing and opening again would not switch to HDR automatically again)
Going back to 525.25 has fixed it.

I need to install 526.47 again to make sure it wasn’t due to some other issue and haven't done exhaustive testing but wondering if anyone else is seeing the same issue?

Note: Windows 11 22H@ - RTX2700 - MadVR 0.92.17 32bit

I'm having the same issue.

3080 12GB
Latest Win 10 Pro 22H2.
Nvidia 526.61 and 526.98
madVRhdrMeasure165

[Klaus1189]

I have just tested with latest 526.98 GRD on my system. I use MPC-BE latest stable (1.6.5.3) with madVR (latest stable 0.92.17). Works like it should. Open file, display switches to HDR, close, open another HDR file, working just fine.

Maybe DDU and install latest driver new? Try latest madVR stable?

Win 10 22H2, with all latest and also optional updates.

[Ejziponken]

I just rebooted and tested, it does seem to work now. Opening and closing and opening and HDR switching works... Hm.. Maybe its something else triggering it because It did not auto switch to HDR before my reboot.

I did install the latest Win 10 update tho.
https://support.microsoft.com/en-us/topic/november-15-2022-kb5020030-os-builds-19042-2311-19043-2311-19044-2311-and-19045-2311-preview-237a9048-f853-4e29-a3a2-62efdbea95e2

So either that update fixed it or something else is triggering the bug/issue.