AMD, Intel and Nvidia driver issues and last recommended version

[mclingo]

I still dont understand whats happening mate, what win version are you on, i've stayed put on 1809 for now

[oldpainlesskodi]

On the latest fastring (need to update my sig)....

I've tried older drivers, and newer drivers....with Madvr HDR passthrough (no tone mapping), makes no difference regardless of driver. With Madr HDR passthrough AND tonemapping, apart from driver 20.1.4, all other drivers results in fine black levels, until you press pause or fast forward/back, and then it looks like it blacks levels become grey like/washed out...

Hope that makes sense. Maybe others can try and confirm (I dont think in it's Windows version issue - just a gut feeling).

K

[huhn]

amd doesn't even have a driver for the new WDDM so just layback.

[oldpainlesskodi]

Could be that hunn. Just odd that 20.1.4 is less broken lol.

[mclingo]

I also think that AMD are cheating -[/URL]

.


out of interest, as you have older NAVI hardware than my relatively recent 5700 card, is there a driver which does work properly with HDR that you can use , or has this never worked for you either, since day 1 on your hardware?

[huhn]

5700 and 5700 XT are the first navi based GPU.
the generations before that are vega and polaris.

[mclingo]

sorry yes i meant vega, I was just wondering if we could work out the point vega stopped working properly we could give AMD something to work with.

[DMU]

Starting with this version
• 19.5.1 2019-05-13 3840x2160 59/60Hz 4:2:0 10 bit doesn't work, but up to 50 Hz it works
there was no BT.2020 flag.
What happened to this version, I do not know, since I did not have HDFury.
Install version 19.4.3 does not work.

[Manni]

New nVidia driver V442.59 released today.

[mclingo]

[QUOTE=oldpainlesskodi;[/QUOTE]

hi, i put win 1909 on this weekend, no issues found if you are holding off for any reason.

[Manni]

hi, i put win 1909 on this weekend, no issues found if you are holding off for any reason.

Not with AMD, maybe, but with nVidia it breaks the NV control panel. It takes minutes to access the panel and to change some of the options. It's a real pain. I had no such issue with 1809. All I know if had I known, I'd have stayed with 1809.

It also breaks E-GPU compatibility for those with a macbook-pro and an E-GPU.

So if you're still on 1809 and have no reason to upgrade, I advise to stick with it.

[el Filou]

No problem opening NV control panel (441.12) on 1909 here.
Are you using the DCH driver by any chance? If yes then an idea is to try the standard one, or vice versa if you're using the standard.

[Manni]

No problem opening NV control panel (441.12) on 1909 here.
Are you using the DCH driver by any chance? If yes then an idea is to try the standard one, or vice versa if you're using the standard.

Thanks, I tried both when I started having the issue following the windows upgrade to 1909, it didn't make any difference.

I know that not everyone has this issue, but if you do, it's a real pain.

No amount of reinstalling, clean install, etc makes any difference. Even going to much older drivers (I have a 1080ti) doesn't help.

[huhn]

you have not by any chance installed the 3d fix?

[Manni]

you have not by any chance installed the 3d fix?

I might have at some point. Could that be the reason? Can I get rid of it?

[huhn]

it's a known issue with DCH driver disabling 3D in the driver lower the problem drastically.

uninstalling 3D vision should fix this to but installing it again is not fun... and madshi seems interested.

[Manni]

it's a known issue with DCH driver disabling 3D in the driver lower the problem drastically.

uninstalling 3D vision should fix this to but installing it again is not fun... and madshi seems interested.

I have done many clean install so 3D Vision hasn’t been installed for many moons. That’s not the issue.

[GoodGravyMan]

Is there a known issue with the RX580 with MadVR and outputting 10 bit color? If i enable 10 bit output in the AMD settings, every time i seem to go into D3D11 fullscreen window mode (10bit) my black levels get washed out. It seems fine in windowed mode (8bit).

I've tried a few versions of the driver and 20.1.4, 20.2.2, 19.7.5, 19.9.2 and they all seem to do the same thing.

If i set the output to 8bit in the AMD settings it seems like everything works.

you can see it clearly in the black clipping test here:

https://imgur.com/a/ES9Xtia

[oldpainlesskodi]

hi, i put win 1909 on this weekend, no issues found if you are holding off for any reason.

I'm on 19582.1001, but good to know you have no issues.

[NoTechi]

AMD Adrenalin 20.3.1 released (https://www.amd.com/en/support/kb/release-notes/rn-rad-win-20-3-1)

NoTechi

[DMU]

Congratulations to all AMD owners, finally, with the correct HDR BT.2020 flag.

[mclingo]

something aint right, I run my desktop in 1080p and i cant get full RGB, it keeps defaulting back to 444 ybcr

[mclingo]

yes HDR is fully working but I defo cant get full RGB for 1080p at all, anyone else?

[mclingo]

back to 2.2 for me with broken HDR, I cant achive 3d in KODI DS at all unless I drop my desktop to 1080p first which then washes out the deskop and kodi interface into a grey mess as its now ybcr444, it plays find after that, this is much more hassle for me than just turning on windows HDR before starting a movie.

The reason I run my desktop in 1080p is two fold, firstly playing a 3d movie in KODI DS and MADVR has always been a bit buggy both playing and stopping the movie, madvr makes a mess of dropping back from 1080p to 4k desktop which often results in loss of HDMI, running your desktop in 1080p is more stable.

the other reason is I connect to my PC from work via 1080p screen, if I run my desktop in 4k at home I have to log off and on again as windows messes with the DPI, its just easier all round to run a 1080p desktop with a 4k rig I find as movies and games will still load and play in 4k or whatever you set them to run in.

i'm now pining for my old RX580 which just... worked...

[oldpainlesskodi]

Congratulations to all AMD owners, finally, with the correct HDR BT.2020 flag.

Yep, all working great here...so far......

UPDATE - correct color flag, but the image is way undersaturated. I can compensate through adjustments, but...

Anyone else have this issue?

UPDATE 2 - scrub that, 2 reboots later and all good.

[Klaus1189]

Congratulations to all AMD owners, finally, with the correct HDR BT.2020 flag.

How do you test this? What do I need for it? special brand TV? ...


something aint right, I run my desktop in 1080p and i cant get full RGB, it keeps defaulting back to 444 ybcr

I use an UHD screen and switched to 1920x1080 -> restart -> switched from RGB full to YCbCr 4:4:4 and back to RGB full -> I can not confirm.
But I did wipe the old driver with AMD Cleanup Utility (https://www.amd.com/en/support/kb/faq/gpu-601), also listed in first post.


Yep, all working great here...so far......

UPDATE - correct color flag, but the image is way undersaturated. I can compensate through adjustments, but...

Anyone else have this issue?

UPDATE 2 - scrub that, 2 reboots later and all good.

So color flag is correct now and also saturation and all other stuff is fine? My "wooden eyes" can not see any issue ;-)

How about Vega cards? Everything fixed now? Was it already before?


I ask, because I want to summarize things in 1st post ;)

[oldpainlesskodi]

Yes, it now sends BT2020 flag in the AMD HDR API, so thats fixed with a NAVI card.

[DMU]

How do you test this? What do I need for it? special brand TV? ...
Samsung TV can show it. Picture -> Expert Settings-> Colour Space Settings.
And i have HDFury.


How about Vega cards? Everything fixed now? Was it already before?
Vega also had an issue like Navi cards. See my signature.

[Klaus1189]

Sorry, but can you please create a snapshot for me, where I can read the info about BT.2020 in Samsung OSD?

In the signature I see that there is Vega 8 but I need to know was it fixed already in the past or also with this new release, I remember a blown red or so with Vega?

[DMU]

Sorry, but can you please create a snapshot for me, where I can read the info about BT.2020 in Samsung OSD?
Pic. (https://drive.google.com/open?id=1WCioSIElyKfg51sn5zFc-oVLwUUA2VPm)

In the signature I see that there is Vega 8 but I need to know was it fixed already in the past or also with this new release, I remember a blown red or so with Vega?
This problem has been identified here a long time ago. NAVI cards were not there then.

[mclingo]

hi, please can someone with a 4k TV switch to 1080p 60hz and see if they can select full 4:4:4 FULL RGB please, dropping back to an old driver fixes this for me so cant just be me surely.

i've tried a full driver wipe with DDU no joy.

EDIT, I think this driver doesn't like my LG OLED, it works fine with my 4k samsung N8000, well cheesed off.

[DMU]

@mclingo
All OK here...

[mclingo]

Thanks DMU.

If I could get 3d to work with KODI DS i wouldnt mind but when my desktop and kodi gui is in 4k 3D just wont trigger at all. If I put KODI DS is 1080p it works but as gui is now in ybcr its all washed out and nasty, plus when I come out of KODI is more than often doesnt drop back to 4k so i'm forever swithing back to 4k, just a total nightmare.

3d plays fine in MPC from a 4k desktop so that bug is just with KODI DS which again will never get fixed unfortunately, i cant win, there is something wrong with every F**king driver, its infuriating.

[Klaus1189]

@DMU: I can only find an option to switch between Auto and Native. What am I missing? Please help me :)

[DMU]

@Klaus1189: You need to be in not the PC mode and choose Custom.

[Klaus1189]

Thank you

[webbo]

Any feedback, please for the latest nVidia driver, regarding HDR passthrough?
Highly appreciated
Especially regarding madVR passthrough, that's what i'm interested in

And how i can check myself within the CTRL+J display info OSD from madVR if the metadata is bogus or correct

Thanks a lot

[Klaus1189]

The latest Nvidia drivers are fine as far as I know.

In Display Stats you can‘t check it. You need to measure it. See the post I linked to in the first post with the broken Nvidia drivers.

[SamuriHL]

The latest nVidia drivers work fine for HDR, yes.

[Magik Mark]

Problem with the GForce v445.75

When running HDR videos, it switches back to SDR when UI of the player is activated.

Sometimes, it can no longer switch back to the right dynamic range

[VBB]

Confirmed. Seems to be a bug in the latest Nvidia drivers.

[VBB]

The issue is with the bit depth. Anything higher than 8-bit causes the display to drop out of HDR when a UI is triggered.

[tyguy]

Thank You, guys, CRU 1.4.1 with DisplayID also solved my above mentioned issue. That's what I did:
- wrote down the madvr timings, removed the madvr created custom resolution, then restart
- in CRU 1.4.1
-- add DisplayID to Extension blocks and set it as the 1st entry
-- set madvr timings and set Pixel clock and Native as well

It's a big help to get rid of a major annoyance, now I can set 23p as the default refresh rate of the TV :)

Couple of notes:

The difference between CRU and nvidia created (by madvr) custom timing is:
- nvidia adds a new one to the already existing ones: that can confuse applications which one to use (e.g. madvr)
- CRU replaces an existing one with the custom one on the OS level, so there won't be any confusion

When you create custom timings with madvr (http://madvr.com/crt/CustomResTutorial.html):
- always start from the default one (EDID) and pay special attention to the "sync" attributes (e.g. + , +):
-- don't select a mode that is different!
- don't deviate a lot from the default EDID values
-- remember, this approach is modifying "back porch" (horizontal and vertical values) only!
- the above 2 wrong settings can easily modify the response of the panel! (e.g. modifying gamma curve, causing black crush, etc.)
- if you get >= 10 hours after the first optimisation then it's already really good, you don't need to do more runs

Examples, original EDID timing:

EDID/CTA:
frontsywi backpixels sync
hor1276 882961660 34805500+
ver 8 10 72 90 21602250+
picl 296.70 mhz
23.9757575757576
OSD result: 23.97791Hz (~4.41 minutes)


Result after the first optimisation run:

Custom:
frontsywi backpixels sync
hor1276 88 3561720 3480 5560+
ver 8 10 72 90 21602250+
picl 299.94 mhz
23.9760191846523
OSD result: 23.97537Hz (~22 hours - 1 day)



About nvidia driver versions:
- some of them can block custom timings completely (doesn't matter how they were created)
- so always check in madvr OSD whether your timing is applied if you install a new driver

Btw, I still use the Display Changer II (https://forum.doom9.org/showthread.php?p=1863306#post1863306) util to easily manage 2 displays.
I was able to create a custom resolution but nvidia displays it as 24 hz and I have to manually activate it for it to work in mad vr. Madvr won’t automatically switch to this exact resolution. Is there a way to do that?

Edit: It looks like you use the hack direct 3D for 24 and 60 hz option.

[SamuriHL]

The issue is with the bit depth. Anything higher than 8-bit causes the display to drop out of HDR when a UI is triggered.

Oh that's going to irritate the hell out of me. I've not watched a movie since I upgraded to the latest driver and I've got the Star Wars UHD collection coming tomorrow (I hope). Guess I'll be rolling back cause um NO.

[VBB]

You'll be fine. Just don't trigger any overlay ;)

[SamuriHL]

Meh no thanks. :D I reverted the driver. I've been gaming on the new laptop anyway so I don't (currently) need the latest and greatest driver. I'm assuming at some point nVidia will fix it in an upcoming release. Not that my movies shipped on time anyway. Tracking numbers with no actual shipment should be illegal. LOL

[Cowboydude99]

Hi all,
I just found this thread...

I'm having issues with my NVIDIA GTX 1080 and JVC PJ.

I use MADVR and JRIVER.

What are the best drivers to use? I do like to game, but it might be a while before I get the chance to game anyway...

Any drivers kind of recent that would allow me to use 444:12bit?

I have a ton of UHD disks.... but can't get HDR working nicely.

Color space shows BT.709 (Best Guess) in MADVR display...

Very frustrating. I just updated to 445.75, then literally found this list/post.

[huhn]

best guess means the file doesn't have meta data so you have to fix this by hand.

that pretty much means the file is broken or the source filter/decoder can't read it doesn't. this is usually the file.

[NikosD]

Hello.

I'm using Win 10 x64 1909 (18363.752) with nVidia 1660 (442.74) connected on a UHD TV using HDMI 2.0.

When native 4K@60Hz resolution/ refresh rate is selected along with HDR from Windows settings, I get only 8bit option for color depth.
My other options selected are RGB for color format and Full RGB.

The diagnostics confirm the settings reporting "8bit with dithering"

If I turn HDR off from Windows settings, I get 8bit & 12bit color depth options.

a) Where is 10bit option, why is missing and I get 12bit with HDR off ?

b) How can I get 10bit using 4K@60Hz with HDR on ?

I mean using 4:2:2 or 4:2:0 options, because I think 4:4:4 is impossible using HDMI 2.0

[huhn]

for some reason nvidia doesn't like 10 bit as a format it does it but if 12 is possible it is doing 12.

you talk about full range RGB and that you know you need 4:2:0 or 4:2:2 to get 10 or 12 bit at 60 which is YCbCr.
just stick to 8 bit RGB it's "better" anyway.