AMD, Intel and Nvidia driver issues and last recommended version

[j82k]

4000 nit metadata is passed correctly. HDR triggering when madVR is set to 8-bit works too. So far so good....

[Klaus1189]

Do custom refresh rates work on Win10 1809 without CRU in 430.39?

[nevcairiel]

Originally Posted by Klaus1189

Do custom refresh rates work on Win10 1809 without CRU in 430.39?

You should always prefer to use CRU in any case, it gives you far better control.

[SamuriHL]

I like this driver very much. It looks to me like they fixed the metadata but I have no real way to confirm. HDR triggers perfectly. I'm very pleased. I think we have a new baseline driver. Of course, others will need to chime in here.

[Manni]

Originally Posted by SamuriHL

I like this driver very much. It looks to me like they fixed the metadata but I have no real way to confirm. HDR triggers perfectly. I'm very pleased. I think we have a new baseline driver. Of course, others will need to chime in here.

Only checked briefly with my LG 4K monitor, the HDR metadata passthrough is fixed and it looks like it was able to switch to HDR in 8bits.

I'll report back if I see any issues with the JVC later tonight.

Looks like a good one though

[brazen1]

I've installed the new nVidia driver 430.39. It is now once again allowing madVR to switch HDR mode. It has also rectified the long lingering audio problem - Multi channel vs stereo auto switch dependent on AVR state on and off.

As expected, nVidia no longer supports 3D. It has been completely removed from the driver install. So far I have installed 3D vision from an older driver. I get a notice that 3D vision does not match the new graphics driver after installing it. I also ran the 3D .reg file in madVR. The 3D option no longer shows up in Windows display properties or NCP. I did attempt to play a 3DMVC.iso in PowerDVD. 3D mode does not engage. I also tried MPC-BE. It displays some strange SBS and then does engage 3D mode. This is a frame packed MVC iso. It shouldn't go into SBS mode imo.

I don't want to spend anymore time fussing with this new driver and I will be reverting back to 416.81 video drivers. Instead of editing those drivers and applying the 388.59 audio driver (bug free) as I've been doing in the past, I will be attempting to use the newer 430.39 audio driver which at this time appears to also be bug free. This combo will update me to the newest working audio and video drivers that meet my demands.

*edit*
The audio bug still exists using the 430.39 driver. It doesn't survive a reboot. I will be using 388.59 audio driver with 416.81 video driver as usual.

[SamuriHL]

Yea I've been watching Infinity War since I installed it and it's flawless. I'm also running 1903 so having a driver that truly supports it and works for everything else is great. And hopefully the RTX owners can chime in on how it works for them, as well. I landed a new job so I started a rebuild of my HTPC. At some point I'll likely get a 2070 for the new 9900k I'm building. Would love to know we have a new baseline driver that works for everyone.

[NoTechi]

Originally Posted by brazen1

As expected, nVidia no longer supports 3D.

This is crazy ... in other words no more driver updates from now on ....
Time to start to look for AMD

NoTechi

[hotripper]

Originally Posted by brazen1

*edit*
The audio bug still exists using the 430.39 driver. It doesn't survive a reboot. I will be using 388.59 audio driver with 416.81 video driver as usual.

Audio bug??? What is the issue? Just curious

[ryrynz]

One page back...

Originally Posted by brazen1

No auto switch from stereo to multiple speaker setup in Windows Audio considering if AVR state is On or Off.

[grendelrt]

I launched a couple HDR games in Windows on the new 430.39 driver and they both reported 1000/400 metadata. Looks like it still doesn't update per game, but its no longer 1000 /20 :/

[NoTechi]

What would be the best way to use an older audio driver? Not sure if it is the audio bug but from time to time windows audio is on stereo. Just a reboot fixes this.
Another problem is that I can't select Atmos anymore even though it was working for some time. Maximum I can select is 7.1. My guess is that this is also caused by communicating wrong EDIT information between AVR and Windows thats why I would like to try an older audio driver.

NoTechi

[clsid]

Has 430.39 fixed the stuttering problems that some were having with previous drivers?

[Manni]

Originally Posted by grendelrt

I launched a couple HDR games in Windows on the new 430.39 driver and they both reported 1000/400 metadata. Looks like it still doesn't update per game, but its no longer 1000 /20 :/

I don’t think the OS has ever reported dynamic HDR metadata. It’s always been fixed. Not sure if the games ask for various values or not.

I can only confirm that with film content, HDR passthrough works fine and reports the actual metadata sent by madVR.

It doesn’t solve any of the outstanding issues on the JVCs (mainly the forced YCC422 in 12bits in RGB or YCC444), but it doesn’t seem to make anything worse.

Apart from the zapping of 3D, it looks like a pretty good driver, and the only one that users of RTX cards can use if they want HDR passthrough to work with madVR.

[SirMaster]

Originally Posted by clsid

This is NVIDIA Profle Inspector tool with an optimized profile for MPC-HC/BE.

Download

Most important settings it uses:
Power management mode = Adaptive
VSync = on
GSync = off
SLI = off
Prefer NVIDIA on Optimus systems

Is there a way to check if this actually worked?

I tried running this on my system with RTX 2060 on 430.39 driver, but how do I know it actually did something?

I thought I would see something like vsync ON in my nvidia control panel settings, but even after running the .bat file it still says "use application setting" for vsync in my control panel for example.

[grendelrt]

Originally Posted by Manni

I don’t think the OS has ever reported dynamic HDR metadata. It’s always been fixed. Not sure if the games ask for various values or not.

I can only confirm that with film content, HDR passthrough works fine and reports the actual metadata sent by madVR.

It doesn’t solve any of the outstanding issues on the JVCs (mainly the forced YCC422 in 12bits in RGB or YCC444), but it doesn’t seem to make anything worse.

Apart from the zapping of 3D, it looks like a pretty good driver, and the only one that users of RTX cards can use if they want HDR passthrough to work with madVR.

Yeah I have no frame of reference since it has never worked correctly since I have had my hdr projector. I was hoping the metadata for each game would at least have the peak brightness output, such as 4000,1000,10k nits etc.

[Nicog]

Originally Posted by clsid

Has 430.39 fixed the stuttering problems that some were having with previous drivers?

Yes, at least better than previous driver (I didn't tried w/o vsunc ON).

[Klaus1189]

I updated some stuff in the first page, if something is missing or probably wrong, let me know

[clsid]

Originally Posted by SirMaster

Is there a way to check if this actually worked?

I tried running this on my system with RTX 2060 on 430.39 driver, but how do I know it actually did something?

I thought I would see something like vsync ON in my nvidia control panel settings, but even after running the .bat file it still says "use application setting" for vsync in my control panel for example.

You can use the NvidiaProfileInspector tool to view all application profiles on your system. The .bat file adjusts the settings of the "Media Player Classic" profile. It doesn't change your global defaults.

[Nicog]

Originally Posted by Nicog

Yes, at least better than previous driver (I didn't tried w/o vsunc ON).

Yesterday when I installed it it worked (no stuttering). Today it's dead (like previous drivers in fact, and also on non HDR content).

I'm back to 418.91, and now it's works fine...

I'm the only guy who has this issue?