AMD, Intel and Nvidia driver issues and last recommended version [Archive] - Page 28

VBB

19th June 2020, 02:58

Updated Windows 10 to v2004. Kept all drivers and software settings intact, but reset display resolution, gamut, and bit depth to Nvidia defaults. Haven't run into any issues, other than the ones associated with the latest Nvidia drivers (see 1st post in this thread).

SamuriHL

19th June 2020, 16:00

I've been running 2004 for a few weeks now and I'm using it with the latest studio driver with no issues.

littleD

24th June 2020, 16:17

https://www.nvidia.com/en-us/geforce/news/directx-12-ultimate-game-ready-driver/

Nvidia GeForce 451.48 WHQL WDDM 2.7 driver, new driver branch so will need testing.Finally new features:

Supports DirectX 12 Ultimate
Supports Vulkan 1.2
Supports hardware-accelerated GPU Scheduling.
Supports CUDA 11.0.

SamuriHL

24th June 2020, 17:37

Ah damn! I'll see if I can test those out tonight if no one gets to it first. Those look fun!

littleD

24th June 2020, 18:42

Ah damn! I'll see if I can test those out tonight if no one gets to it first. Those look fun!Be careful i ve lost "add run with graphic processor" to context menu. I still look for fix.

Microsoft's shit again https://nvidia.custhelp.com/app/answers/detail/a_id/5035

kostik

24th June 2020, 18:52

VBB

24th June 2020, 19:07

@kostik Could you give us a little more detail? What color space does it launch in? What does it say instead of NV HDR when it first does this? Are you using 10-bit?

kostik

24th June 2020, 19:31

@kostik Could you give us a little more detail? What color space does it launch in? What does it say instead of NV HDR when it first does this? Are you using 10-bit?

I am using 12bit RGB 24Hz. . . If you disable "send hdr metadeta to the display" in madVR settings and turn on HDR in windows display settings , play an HDR movie, you will see the exact phenomenon I get launching hdr movie first time with this driver (and some of other 45X drivers) .
It uses OS HDR. While the movie plays, if you open it again (file->open) , it switches to the right mode.

WEIRD ... 446.14 works fine, also the studio drivers work good. Maybe I will try the Studio version of this 451.48 driver but I guess its an issue with this branch and will have to wait for a fix

Klaus1189

24th June 2020, 19:36

Maybe I will try the Studio version of this 451.48 driver

Is there difference between Studio Driver and Game Ready Driver, when the number is identical? I thought it's the same, but I was already mind blown by minor things ;)

kostik

24th June 2020, 19:38

Is there difference between Studio Driver and Game Ready Driver, when the number is identical? I thought it's the same, but I was already mind blown by minor things ;)

I also think its basically the same, maybe they just add some profiles for pro editing software and that's it. Well, will try anyway . I think I will stay with these drivers... I don't mind opening movie twice, it takes a second and works fine afterwards.

chros

24th June 2020, 19:46

How is the new GPU scheduler? Is there any performance impact compared to the previous drivers with the same settings? :)

nevcairiel

24th June 2020, 20:01

Nvidia GeForce 451.48 WHQL again the same issues I've seen with the last drivers... wrong colorspace when launching HDR with madVR ... to fix this, after launching the movie first time, in the same mpc-hc window , I click open file and pick the same movie file and it switches to NV HDR and to the correct colorspace.

To be honest madVR is likely just a bit out of date when it comes to HDR handling. Multiple years of driver and OS HDR development - an area that was never fully fleshed out before, and no madVR updates to speak of.

kostik

24th June 2020, 20:10

To be honest madVR is likely just a bit out of date when it comes to HDR handling. Multiple years of driver and OS HDR development - an area that was never fully fleshed out before, and no madVR updates to speak of.

Would you suggest using OS HDR?

clsid

24th June 2020, 22:31

to fix this, after launching the movie first time, in the same mpc-hc window , I click open file and pick the same movie file and it switches to NV HDR and to the correct colorspace.Tip: you can press Ctrl+E to quickly reload the current file in MPC-HC.

VBB

24th June 2020, 23:12

I am using 12bit RGB 24Hz. . . If you disable "send hdr metadeta to the display" in madVR settings and turn on HDR in windows display settings , play an HDR movie, you will see the exact phenomenon I get launching hdr movie first time with this driver (and some of other 45X drivers) .
It uses OS HDR. While the movie plays, if you open it again (file->open) , it switches to the right mode.

WEIRD ... 446.14 works fine, also the studio drivers work good. Maybe I will try the Studio version of this 451.48 driver but I guess its an issue with this branch and will have to wait for a fix

I guess your reply is confusing me a little. If you disable "Send HDR metadata" in madVR, and then manually flip the HDR switch in Windows, doesn't madVR normally say OS HDR in that case? Wouldn't it only say NV HDR if madVR was actually sending the metadata?

SamuriHL

25th June 2020, 01:20

Studio driver is no different. Remember a few weeks ago when I was complaining about the Windows supplied driver and asking why no one saw the issue I was seeing? Yea, the current drivers are exactly what I was seeing but I didn't know at the time that you could just restart the video and it'd kick it into the proper HDR mode. That works for me for now. I guess. Not seeing any adverse effects from turning the new option on in Graphics Settings for windows. The reduce latency and improve performance option.

kostik

25th June 2020, 07:02

I guess your reply is confusing me a little. If you disable "Send HDR metadata" in madVR, and then manually flip the HDR switch in Windows, doesn't madVR normally say OS HDR in that case? Wouldn't it only say NV HDR if madVR was actually sending the metadata?

It says OS HDR when launching the file for the first time, when reloading the movie again, it switches to NV HDR. My comment was only to describe how it looks when playing HDR movie and not my real setup . If you do what I wrote , you will see how the movie looks with the new driver on a normal setup

VBB

25th June 2020, 07:32

So, here's my experience with this latest driver:

First off, only a DCH version is available at this time. Perhaps that's how it's gonna be from now on. That means the control panel (NVCP) component of the driver will be installed (and updated) from the Microsoft store. I am not a fan of that, but oh well. Did a clean install, reboot, then configured as usual. The only change I made, other than color space and bit depth, is the switch from "Optimal" to "Adaptive" power. Played an HDR test clip and noticed that on first try, it says NV HDR in the OSD, and everything looks washed out. On subsequent tries, OSD shows OS HDR, and everything looks as it should. That alone was enough for me to not use this driver, but it turns out that, at least with my 960, performance was also almost cut in half. madVR seemed to add around 20ms on average, regardless of the decoder in use. Tried FS exclusive, thinking that might make a difference, but nope. That caused such bad flickering, it was unusable.

After wasting almost two hours, I did a clean install of the previous driver. All good.

VBB

25th June 2020, 07:46

That is good to know. For some reason those do not come up in my results, like they normally do.

VBB

26th June 2020, 01:51

Anyone else try this latest Nvidia driver? I'd love to know why my card's performance was affected like that. Made it entirely unusable for me.

SamuriHL

26th June 2020, 02:25

I have it installed and do not see any performance issues. I did enable the new windows option in the graphics settings. I also changed power to adaptive as we all do.

nsnhd

26th June 2020, 04:41

The reason why you update to the latest driver is that you're playing games ? I don't see other ones because I believe that newer versions couldn't improve madVR performance, is that right ?

VBB

26th June 2020, 04:42

@SamuriHL That new option seems to be for newer cards only. It did not show up for me with 451.48/W10 v2004. Did you install the standard or DCH version?

VBB

26th June 2020, 04:47

@nsnhd Being a seasoned gamer/admin/geek, I tend to always use the latest version of everything, knowing the risks, of course. I don't recall the last time a new driver actually improved madVR performance, but I like to test things. This latest Nvidia package also included a newer audio driver, for example. Unfortunately, Nvidia has been catering almost exclusively to gamers for as long as I can think back (Bought my first RIVA in the late 90s).

SamuriHL

26th June 2020, 11:14

@SamuriHL That new option seems to be for newer cards only. It did not show up for me with 451.48/W10 v2004. Did you install the standard or DCH version?Dch. Of the studio driver not that it makes a difference in this case. And yeah I've got my 2070 founders edition in that machine. I enabled it on my 2080 on my laptop as well using the gaming driver but I've not tried madvr yet. The laptop tone maps to sdr though.

Sent from my SM-G975U using Tapatalk

el Filou

26th June 2020, 20:00

@SamuriHL That new option seems to be for newer cards only. It did not show up for me with 451.48/W10 v2004.Yes, HAGS is for Pascal+.

SamuriHL

28th June 2020, 01:38

I had to go back to a working driver. It just simply stopped outputting HDR for me. My HD Fury was showing no HDR metadata, but, the C8 went into HDR mode. The usual trick of stopping it and reloading the file no longer worked for me. This is a mess. Went back to the previous studio driver for now.

ShadowVlican

6th July 2020, 03:01

Can confirm that Nvidia 451.48 breaks MadVR HDR passthrough... Many thanks to this thread! I thought I had screwed up something then I googled the problem and realized it was Nvidia's fault!

Downgrading back to an older driver because I had passthrough working just fine before...

VBB

9th July 2020, 17:59

Gonna wait for someone else to test this time around ;)

kostik

9th July 2020, 20:13

Gonna wait for someone else to test this time around ;)

Same as previous 451 drivers

tyguy

9th July 2020, 22:23

Is there a bug in latest drivers regarding hdr playback? NV HDR is all grey and washed out, but my tv says HDR is on. Using OS HDR looks proper. I’m using madvr tonemapping with pixel shaders for what it’s worth.

VBB

9th July 2020, 22:47

tyguy

9th July 2020, 23:06

Yes, the last two do not work properly with madVR's HDR implementation. This is due to changes in the way Nvidia handles HDR, so not really a bug in the driver, but something that needs to be fixed in madVR.
Okay thanks for letting me know. Im assuming it will be awhile before this is fixed in madvr since development seems to be on hold. Having to toggle HDR isn't the end of the world.

huhn

10th July 2020, 00:33

a new test build is expected every day now. there is a good chance it will be complain with the API changes.

VBB

10th July 2020, 00:42

As much as I'd like to see one, I wouldn't get my hopes up. Mathias is simply too busy with finalizing Envy. Once it ships, any further madVR development will also benefit Envy, so that should be good for us here. What I'd really like to see in addition to bug fixes is support for Dolby Vision, especially now that single layer rips without compromising audio are possible.

huhn

10th July 2020, 00:58

i have bad news for you.
this may never ever happen without papers.
you need a decoder first to even output it to madVR.

SamuriHL

10th July 2020, 01:33

There are decoders on the PC if you can figure out how to use them. And Dolby Vision has been added to the MKV standard in the past couple weeks. Things have been progressing quite nicely outside of the PC world for DV.

VBB

10th July 2020, 03:32

Well, hopefully Nev will find it worthy of his time, but I know we've discussed this before. The problem with DV is that it's closed pretty tightly. It will happen eventually.

Klaus1189

10th July 2020, 05:24

@brazen1: I think I read somewhere that there is a new Audio driver version in recent Nvidia drivers, does that fix this issue?
https://forum.doom9.org/showpost.php?p=1913991&postcount=1319

SamuriHL

10th July 2020, 13:51

Well, hopefully Nev will find it worthy of his time, but I know we've discussed this before. The problem with DV is that it's closed pretty tightly. It will happen eventually.Some of the docs have been released. Still can't properly encode but the reason so much progress was made on mkv is because they got access to the profile docs and had the mp4 muxer Dolby released. They were able to piece everything together from that. All of my dv movies are sitting on my nas in ts format as profile 04.06 for playback on my shield. Those Intel drivers that were released in May have a decoder. And Nvidia drivers have had a beta decoder for a while... I'm guessing for games. So it's not impossible anymore. Just time consuming and difficult.

Sent from my SM-G975U using Tapatalk

fairchild

11th July 2020, 00:55

Any testing done on 20.7.1 drivers, how can i help to test compatibility? I'm running them currently on my RX 56 Vega.

Klaus1189

11th July 2020, 11:41

...

I am glad you want to help, but sadly I don't understand what you mean with testing compatibility?

fairchild

11th July 2020, 21:49

I am glad you want to help, but sadly I don't understand what you mean with testing compatibility?

Well since that driver hasn't been verified, I was willing to run whatever test you do to check if the passthrough for HDR is working. I have an HDR MKV file I use.

LG Colors of Journey HDR UHD 4K Demo.mkv

Does show HDR passthrough working as my TV switches to HDR mode and appropriate Mode on my TCL Roku 4k TV with latest MadVR and 20.7.1 drivers

Klaus1189

12th July 2020, 10:07

Something like this would be really nice, since I don't have equipment or knowledge to do tests like this:
https://forum.doom9.org/showthread.php?p=1865444#post1865444

I use my RX 5700 XT to check if the passthrough works, but please keep on checking with your Vega (other generation Navi) if the HDR switch still works and if there is anything please report here.

solidservo

13th July 2020, 15:53

so what is the recommended nvidia driver for madVR with HDR content?
442.74?

Klaus1189

13th July 2020, 16:53

For now with madVR I recommend one of the following:
Last working GRD: 446.14
Last working SD: 442.92
Please keep in mind the issue introduced in 445.xx drivers:
This version and all 445.XX and higher: Playback at greater than 8-bit drops back to 8-bit (and out of HDR) in FS windowed mode when player GUI is triggered, regardless of bit-depth of the file. Can be circumvented by using FSE mode or by setting madVR to 8-bit.

solidservo

14th July 2020, 06:10

Klaus1189

14th July 2020, 11:01

I would go with SD 442.92 over GRD 442.74, but if you really want to go with GRD only and need/want prevent the 445.xx issue mentioned in my former post yes. Because there are workarounds mentioned but with drawbacks, like no player gui in exclusive mode.

Filmgeek47

16th July 2020, 07:40

I’ve got a frustrating issue that I’m hoping someone can help me with. I’m running a GTX 1660ti and I’m trying to get working 3D and 4k. I’m really close with the 425.31 driver. The only issue I’ve got is that every time I reboot, my bit depth settings reset back to the default of 8 bit, which on my projector makes everything go magenta. If I set the bit depth to 12 bit at 24hz, it’ll switch back and forth correctly between 24/60hz and 8/12bit, but on reboot I have to reset those bit depths again. Is there a solution to this? Was this a common issue with earlier drivers? The bit depth is persistent on the newer drivers, but then 3d doesn’t work.