AMD, Intel and Nvidia driver issues and last recommended version

[Klaus1189]

It depends on your model and what you need, for example do you need 3D support? RTX or GTX model?

[xabregas]

GTX 1660 SUPER, no 3d support but i have 4k HDR screen even knowing i dont play a lot of HDR videos. But usually just watching bluray 1080p videos upscaled to 4k and im very confused about this studio vs gaming driver. What is the best for madvr? studio or gaming? I know my gpu is very new and only the last 2 drivers work.

[Klaus1189]

Use the latest GRD or SD, it shouldn't matter, as long as the version number is the same. GRD is updated more often, SD rarely.

[SamuriHL]

The latest nVidia drivers, knock on wood, have been pretty stable lately when it comes to video playback. No major issues with them on my RTX cards thankfully!

[Klaus1189]

I signed up at vanguard beta program, but didn't received an email :(

[mclingo]

i didnt either mate, guess thats a no then :)

[mclingo]

i think they've changed something in 20.2.2 AMD, colours look right but image doesnt have the right brightness, can somsone else install to see if you are seeing what i'm seeing.

[mclingo]

this might look fixed for people with low nit displays or projectors but the picture is very dim compared to Windows HDR turn on, this suggests its with still not outputting Bt2020 or its somehow sending the wrong meta data or something, this is really odd.

[SamuriHL]

Maybe someone with an hd fury can check what's being output for you.

[mclingo]

huhn is running a navi card but not sure what display, might be hard to see what i'm seeing without a bright display, ideally someone with a NAVI card and an OLED.

[oldpainlesskodi]

i think they've changed something in 20.2.2 AMD, colours look right but image doesnt have the right brightness, can somsone else install to see if you are seeing what i'm seeing.

It's busted, so don't bother - switch to Win HDR, press play...all fine...fast forward/skip, and it seems to flip to limited range (at least on my rig).


Back to the last lest busted version.......

Do they hire monkeys?

EDIT - and no, the AMD API still does not switch to BT2020, outputs 709....but they also manged to break the Win HDR toggle when you fast forward/skip, as explained above.

[Klaus1189]

the AMD API still does not switch to BT2020, outputs 709

How can I check that?

[mclingo]

I think you may have some issues with your rig mate, i'm seeing no issues at all apart from the image being a little bit dimmer than windows HDR. Toggle is rock solid here, tested KODI DS and MPC-HC, skips also fine in both.

if you have FSE turn off your movie might just be popping in and out of HDR mode if you move your mouse, put FSE on and try again, i see what you are seeing in MPC-HC with FSE turned off when i move my mouse, this is normal.

[mclingo]

lets see what DMU and Huhn report back, sure this is BT2020 now, just too dim.

[Klaus1189]

How can I check that?

I ask because the colors do look right to me, but that doesn't mean there could be still something wrong. I also think it is a bit dim too, but usable nevertheless. Fast forward does not produce any problem here.
Did you wipe the old driver? I used the AMD Cleanup Utility, linked in the first post.

But it looks like things are getting better now ;-)

[oldpainlesskodi]

Ok, I'll try again to rule out FSE. But my display was still reporting 709 with the AMD toggle, and 2020 with the Win HDR toggle, but i'll double check and report back.

[oldpainlesskodi]

Yep, rolling back to 20.1.4 - have double checked the variables I can think of, so, at the moment, my original post on this driver stands as is on my set up.....if it's working for you guys, would be good to understand the difference.

[mclingo]

you should not roll back just jet, you need to find out whats going on. its not really clear whats happening for you, is this all happening in KODI DS?, is windowed mode on or off in KODI, how are you determining what output is being sent to your TV?

[oldpainlesskodi]

1 - Kodi yes.
2 - Windowed in Kodi - no, always keep fullscreen, but tried FSE and windowed in Madvr.
3 - TV reports 709 in the latest AMD driver with HDR playback, and using the WinHDR toggle, like I said, it reports bt2020, and looks fine until in Kodi you press next chapter, and then it lose's all of the dark/lower detail, like its gone to limited range. No such issue with this on 20.1.4 - I have triple checked.

Like you said, lets see what others find.

[mclingo]

hi, your TV actually reports what colour space its receiving? and if you turn on windows HDR it reports bt2020 and with it off bt709?

[oldpainlesskodi]

Yep......

[mclingo]

there is an ongoing conversation about this issue here, this is how I found out there was a new driver, if you're sure its still not outputting BT2020 then I need to report this, I could do with final confirmation from someone else though as colours look right to me but I have no way of knowing what i'm sending to my TV.

https://github.com/GPUOpen-LibrariesAndSDKs/AGS_SDK/issues/33

[DMU]

lets see what DMU and Huhn report back, sure this is BT2020 now, just too dim.

I don’t understand what they did, but the colors began to look right! TV reports that the color space is BT.709, and HDFury says there is no flag 2020.

[huhn]

nothing good to say here i never tested HDR i don't have a HDR screen and i'm not going to add a HDR screen to the PC the card is in.

they "fixed" d3d11 scaling a bit but ruined d3d11 processing even more in general chroma is still NN.
so they touched it but made it worse...

[mclingo]

DMU, whats you guess as to why the colours now look right, this makes no sense if no BT2020 flag is being sent as you have now confirmed to AMD.

[DMU]

I don’t know why, instead of fixing errors, they complicate things even more. Now users will think that the AGS HDR (AMD Private API) is working correctly.

[mclingo]

I feels like the fudged it hoping that nobody will notice, or they just dont know what they are doing at all, either way this doesnt bode well for future HTPC use, just dont understand how they can get something so fundamental to this card wrong.

However MADSHI did suggest he might be able to put windows HDR toggle back into MADVR, when I asked he said "maybe", a private vs windows HDR switch in MADVR, wouldnt be hard to do I dont think.

[oldpainlesskodi]

From what it looks like to me, the latest driver over compensates by overblowing colours and contrast in HDR mode via the AMD API to try and compensate for the fact its not sending the BT2020 flag and it's still in BT 709 mode - total screw up in my book.

One day......

[clsid]

This Reddit topic (https://old.reddit.com/r/Amd/comments/favtfv/radeon_software_adrenalin_2020_edition_2022/) is a good place for bug reports. There is AMD support staff active there.

[mclingo]

thanks i've added a post to that, would be helpful all of us with AMD cards can contribute to this.

[DMU]

@mclingo
By the way, could you check the new driver with Polaris? It is believed that there will be oversaturated colors.

[mclingo]

hi, sorry i sold my RX580, just running a 5700 now.

[oldpainlesskodi]

Can you share link to your post in the reddit forum?

[DMU]

One more thing, with the new AMD driver the "Windows HDR switch" bug fix no longer works. He switches to the HDR mode, but does not set metadata; standard Windows metadata is used. So it makes no sense to ask madshi to implement the Windows HDR switch in madVR. The only way for AMD owners is to use WinAPI, as in Kodi (https://forum.doom9.org/showthread.php?t=177375).
Madshi planned to implement HDR support for Intel. This will be a solution for AMD owners as well.

[oldpainlesskodi]

That would explain what I saw when I mentioned it looked like the driver had flipped to limited, as it lost shadow and highlight detail.

So, sticking with 20.1.4 for now, as at least win hdr toggle seems to be working.

[mclingo]

i've been tinkering with this for the last couple of hours, i've been swapping between driver 20.1.3 and 20.2.2 and comparing LG TV tone mapping to MADVR tone mapping with windows toggle on and off. I'm going back to what i first said, everything is right but its just too dim, I'm even sure meta data is being pass as when I tone map using MADVR i can see that highlight recovery is definitely working.

The dimmed HDR output is also affecting my standard LG tone mapping, normally if I send meta data direct to my TV the faces in harry potter the goblet of fire about 2:09 are usually almost completely clipped, there is virtually no detail at all in the bright highlights of the ghost faces, with MADVR highlight recovery all the detail comes back, this is why I use it.

Whats different with 20.2.2 is that my standard LG tone mapped image now sits somewhere in between the two, there is a lot less clipping, i've no idea why this happening, this is odd.

i'm staying on 20.2.2 for now as i'm not seeing any other issues with it to be honest, i canty explain oldpainless's issue at all though, that only happens to me when i move my mouse when playing a HDR movie in MPC-HC and FSE is off.

[oldpainlesskodi]

On your system does the Win HDR toggle put madvr in windowed fullscreen mode even though FSE is enabled?

[mclingo]

Hi, whatever settings you or I are using it must be going into some sort of full screen mode as HDR wont trigger otherwise.

All I can tell you is how i've got mine setup. In MADVR windowed mode and FSE are unticked. In KODI DS i'm using Full SCREEN and "use windowed mode" is SYSTEM is turned off.

Does that help?

[oldpainlesskodi]

Sorry if this is a daft question, but how can windowed mode AND FSE be both unticked in MadVR?

[Klaus1189]

Sorry for interrupting, what issue is fixed now, or only half? Like HDR looks right, but not outputted as BT.2020 becuause philips TV reports video signal as BT.709
How are Hardware decoders now? ...


I want to collect infos, at least AMD is doing anything right now, so I hope I could point them to the right direction anyhow.

[oldpainlesskodi]

It's still BT 709....nothing has changed.

[mclingo]

something has changed, colours are now correct, picture is just dimmer compared to windows HDR which will be something to do with it still sending BT709.

[mclingo]

Sorry if this is a daft question, but how can windowed mode AND FSE be both unticked in MadVR?


Hi, i meant window overlay

[el Filou]

How can colours be 'correct' if the card is still flagging the output as BT.709? That would mean the driver is downconverting to BT.709 behind madVR's back, which is bad as you lose wide gamut colours.

[mclingo]

i think they've fudged it somehow yeah, the colours look right, the only issue is the picture looks dimmer, hard to explain, its quite subtle, so much so joe public wont even notice, they'll just think its fixed, and i cant capture it on my phone.

using windows HDR in conjuntion with MADVR still works as well which is odd, i've no idea whats going on really, DMU has a better handle on things than I do.

https://1drv.ms/u/s!AgvFafeelEBij9hlrbMjllvxvSibPA?e=FSDSab

[DMU]

I also think that AMD are cheating - сustomize the results for initially incorrect image output. Sounds like tone mapping. Some images show strong clipping in the highlights.
Pic. (https://drive.google.com/open?id=1gE5E65EOi0vlu3NvPEBFr4Wq5qwZy_4P)

But in general it looks VERY similar to the correct HDR.

[mclingo]

exactly !, i'm not losing my mind afterall :) OPK, you really need to have a look at your setup mate, something really odd going on there, you should be seeing what myself and DMU are, I think the drop to limited is something to do with your setup and its not a driver issue, although its really odd that going back to .4 solves that?

[oldpainlesskodi]

Out of curiosity, what version of madvr are you on? Using DVXA or DX11?

[mclingo]

Hi, its in my sig, latest version 92.17 + 113 beta copied over the top.

[oldpainlesskodi]

Ok, figured it ok. It's MadVR's tone mapping with HDR output kicking in. Strange it only happens on the one driver.

Anyways, all good.