AMD, Intel and Nvidia driver issues and last recommended version

[kostik]

Originally Posted by omgi0wn

I'm using 430.53 with my LG C8, but I don't seem to get the 10-bit or 12-bit options in the control panel anymore. Was looking to play movies with the 23Hz option in RGB Full @ 12 bpc in HDR.

I'm only getting the 8 bpc option, any ideas? In the past I thought I had the 12 bpc option.

Check if Deep Color is enabled on your C8 (Settings->Picture->Additional Settings->HDMI ULTRA HD Deep Color )

[SamuriHL]

Yea working fine for me on the C8 with my 1060 and 430.53.

[omgi0wn]

Originally Posted by kostik

Check if Deep Color is enabled on your C8 (Settings->Picture->Additional Settings->HDMI ULTRA HD Deep Color )

Originally Posted by SamuriHL

Yea working fine for me on the C8 with my 1060 and 430.53.

Very strange. I do have Ultra Deep Color enabled, but still only getting the 8 bpc option. Do you get the option when only HDR is enabled or SDR too?

Also, are you getting it with 60 Hz or at lower framerates?

I'm wondering if the sound bar I'm plugged into is limited me to 8 bpc, although I can't imagine why it would since I thought I had seen 12 bpc in the past. I'll try checking a few more things again.

I guess one last question, is it displayed as your primary monitor or extended?

[SamuriHL]

You won't get it with 60 as that's not possible on HDMI 2.0. You'll only get the option for 12 bit when you've got 23Hz selected. HDR/SDR doesn't matter.

[Asmodian]

You need to be actually running 30 Hz or below to see the 12 bit option. You cannot just select the refresh rate, you have to apply it.

[omgi0wn]

Originally Posted by SamuriHL

You won't get it with 60 as that's not possible on HDMI 2.0. You'll only get the option for 12 bit when you've got 23Hz selected. HDR/SDR doesn't matter.

Originally Posted by Asmodian

You need to be actually running 30 Hz or below to see the 12 bit option. You cannot just select the refresh rate, you have to apply it.

I do have 23 Hz selected, and applied, but I'm still not seeing the option.

Windows Advanced Display Properties shows that the screen is displaying at 23 Hz, as does mpc-be if I view the stats. Still not seeing the option in Nvidia Control Panel though.

I'll take some screenshots when I'm home, maybe I'm missing something.

[SamuriHL]

Really not sure what's happening in your case but at this point I'd use driver cleaner, nuke the thing, and install clean.

[Manni]

Originally Posted by omgi0wn

I do have 23 Hz selected, and applied, but I'm still not seeing the option.

Windows Advanced Display Properties shows that the screen is displaying at 23 Hz, as does mpc-be if I view the stats. Still not seeing the option in Nvidia Control Panel though.

I'll take some screenshots when I'm home, maybe I'm missing something.

That can be because you're using a recent driver with a custom resolution. You need to select a standard resolution to be able to select 12bits even at 23p in the nVidia control panel. 385.28 (if GTX) allows to select 12bits even with a custom res. I forgot when that got taken away. Otherwise DDU and driver reinstall as suggested might help.

[el Filou]

x7007 on the madVR thread saying NVIDIA driver 430.64 reverts the output dynamic range to Limited when TV is turned off/on: https://forum.doom9.org/showthread.p...02#post1874202Edit: works fine on my system too

Originally Posted by GTPVHD

Nvidia GeForce 430.64 WHQL driver with the fix for the high CPU usage bug in 430.39.

It also includes security fixes for those vulnerabilities:https://nvidia.custhelp.com/app/answ...tail/a_id/4797

[VBB]

Originally Posted by el Filou

x7007 on the madVR thread saying NVIDIA driver 430.64 reverts the output dynamic range to Limited when TV is turned off/on

Works fine here, as with previous driver.

[Jeff R 1]

Originally Posted by Manni

Go back to an earlier driver (385.28 recommended) or upgrade the projector.

The magenta bug is gone on the new (2019) 4K models, it doesn't happen in 8bits or 12bits, at any frame rate, which makes using 8bits an option again.

With older models, 385.28 only has the magenta bug at 4K60 8bits. There is no magenta bug at 12bits (though colorspace is forced to YCC 422 internally when using RGB or YCC444, irrespective of the frame rate, which hopefully will be solved on the new models, it won't be on the old ones).

Every driver post 385.28 breaks something. The only advantage to using a more recent driver with a GTX card is 3D. Otherwise stick to 385.28.

I think 391.24 is the last driver where the magenta bug is not with 12bits as well as 8bits, at all frame rates. However the video levels are borked in 12bits if using video levels, and you can't select 12bits in a custom res. Of course 3D only improved with 391.35, so it's one or the other. Then after 398.11 you lose HDR passthrough as well.

Again, 385.28 is the driver to use with GTX (not an option with RTX), unless you really have to use a more recent driver for whatever reason, or a frame drop in 3D every 13min instead of every 3 minutes is good enough motivation to deal with all the other issues.

Hopefully the next major driver branch coming up this month should allow at least some of us to upgrade, especially if HDR passthrough is supported again.

Klaus1189, if you think it's useful, please could you link to this post in the first post, as a "note to JVC projector owners with nVidia GPU"? Thanks!

The Magenta bug us gone for the JVC 2019 projector modesl, so I'm assuming that a firmware update for my 2018 model will fix that, or is it a physical problem that can't be fixed with a firmware update ?
And yes, I find that if I use any of the NVIDIA drivers where the meta date is correct, I get no HDR pass-through, I have to use one of the borked drivers so I can use the "slider" control in the Gamma settings.
Any other driver that isn't borked and the setting is gone, it's not even "greyed" out.

Why is that, do the drivers have to be defective to enable HDR pass-through to work properly and have the projector switch automatically between SDR and HDR ?

[Klaus1189]

Did you try fullscreen exclusive (madVR settings) for HDR passthrough on your Nvidia?

[Manni]

Originally Posted by Jeff R 1

The Magenta bug us gone for the JVC 2019 projector modesl, so I'm assuming that a firmware update for my 2018 model will fix that, or is it a physical problem that can't be fixed with a firmware update ?
And yes, I find that if I use any of the NVIDIA drivers where the meta date is correct, I get no HDR pass-through, I have to use one of the borked drivers so I can use the "slider" control in the Gamma settings.
Any other driver that isn't borked and the setting is gone, it's not even "greyed" out.

Why is that, do the drivers have to be defective to enable HDR pass-through to work properly and have the projector switch automatically between SDR and HDR ?

385.28 works fine if you have a GTX. You get HDR passthrough and the slider works. If you have an RTX, you need 430.64.

I highly doubt that JVC will release a f/w fix for the magenta bug on the 2018 models (and earlier ones). They have never done that in the past (fixing things on an older model once new models are released). Given the issues they have with the new models, the chances that they would spend any development time on an older model to fix such a bug (supposing it's not a hardware issue) is close to zero. Of course, I hope for you that I'm wrong.

[Jeff R 1]

Originally Posted by Klaus1189

Did you try fullscreen exclusive (madVR settings) for HDR passthrough on your Nvidia?

Not in that case where the other drivers don't work with the HDR switching.
I don't care for fullscreen exlusive mode though, but I will see, just to satisfy my curiosity.

All the chapters in the movie are gone and I like to see how many frames per second, etc...

[Jeff R 1]

Originally Posted by Manni

385.28 works fine if you have a GTX. You get HDR passthrough and the slider works. If you have an RTX, you need 430.64.

I highly doubt that JVC will release a f/w fix for the magenta bug on the 2018 models. They have never done that in the past (fixing things on an older model once new models are released. Given the issues they have with the new models, the chances that they would spend any development time on an older model to fix such a bug (supposing it's not a hardware issue) is close to zero. Of course, I hope for you that I'm wrong.

I have a GTX 1080ti, so I will try again with 385.28, I had to get NVIDIA to give me a link as it did not show up in the list of old drivers.
I restored the HTPC back to a restore point and it messed things up a bit, the NVIDIA control panel could not be accessed afterwards.

When you say the 2019 models, are we talking about late of 2019 or the new NX/RS series that have just been released ?

EDIT:
That was 398.11 that wouldn't work with HDR switching, I'll have to contact them again to get 385.28

EDIT:
I Googled it and it came up. :-)

[Jeff R 1]

Originally Posted by Manni

385.28 works fine if you have a GTX. You get HDR passthrough and the slider works. If you have an RTX, you need 430.64.

I highly doubt that JVC will release a f/w fix for the magenta bug on the 2018 models. They have never done that in the past (fixing things on an older model once new models are released. Given the issues they have with the new models, the chances that they would spend any development time on an older model to fix such a bug (supposing it's not a hardware issue) is close to zero. Of course, I hope for you that I'm wrong.

Hmmm.
With driver 385.28 installed, the mapping level slider for the auto tone mapping is not there, at this point it only appears when I install an NVIDIA driver with the bogus metadata, does the slider appear.
I have only what is boxed in, in green when I install driver 385.28, and nothing else.
The red box only shows when I install a driver with bogus metadata, but I do have the option of switching what is in the green box.

When I use my Panasonic UB900 (not UB9000), the option in the red box is also gone.
Not sure what's going on.

Is it because the Panasonic player and the driver with the correct metadata is sending the right metadata, is the reason I don't have the option in the red box ?
I suppose in the end it doesn't really matter, but sometimes it would be nice to use the "auto tone mapping slider.

Maybe I need to upgrade the firmware on the projector for things to work properly.
I guess that's the next step.

[Manni]

2019 models = new 4K native models
2018 models (and previous) = older eshift models (not native 4K).

Which model do you have?

With a 2019 RS2000, I don't have any of the issues you are mentioning and we have the same GPU. That's with the latest publicly available f/w (2.01), and Windows 10 Pro x64 1809.

It sounds like you are not sending passthrough, so the JVC isn't detecting HDR10. Make sure that you have enable the automatic HDR10 detection in the JVC and that the user mode selected has a PQ gamma selected..

All of this works fine with 385.28 (with 3D) or the latest 430.64 (no 3D).

Be careful when you install 385.28, windows will replace it at the next update with a slightly more recent driver. You have to roll that driver back, and then 385.28 will stay.

[Jeff R 1]

I need to update my firmware, and maybe that will solve the problem; I have a RS1000 _ should have mentioned that earlier.

I'm pretty sure it's switching to HDR, when I play a 4K UHD movie with MPC-HC and MadVR, the screen goes black for a moment and I can hear the projector adjusting things (I'm assuming the iris).
Plus when MPC-HC is not in full screen mode, the desk top is totally blown out and over saturated with colour indicating that the projector is in HDR mode.
At any rate I will make sure that the auto HDR detection mode on the JVC is turned on.

I'm running W10 Home edition x64 1809.

And about the Windows auto driver update.
Type in "Control Panel" in search and look for "System" in the old control panel.
Go to "Advanced System Settings" in the left pain.
In that window, click on "Hardware" and then "Device Installation Settings"
Click on "NO" in that box to keep Windows from updating any drivers.

Thanks !
I will report back.

[Manni]

Originally Posted by Jeff R 1

And about the Windows auto driver update.
Type in "Control Panel" in search and look for "System" in the old control panel.
Go to "Advanced System Settings" in the left pain.
In that window, click on "Hardware" and then "Device Installation Settings"
Click on "NO" in that box to keep Windows from updating any drivers.

That doesn't work here.

Even asking CRU not to update the driver doesn't work here.

But after asking the roll-back, it stays at 385.28.

I'm testing 430.64 at the moment to see if I can live with it.

[SamuriHL]

I've got 430.64 stable on my 2070 so far. It seems like nVidia hasn't broken anything since they released the useful fixes in the first 430.xx driver for us. I'm using windowed mode and it's working quite well for me.