AMD, Intel and Nvidia driver issues and last recommended version - Page 37

nevcairiel · 4th November 2019, 10:37

Quote:

Originally Posted by huhn

on default your sony TV needs limited range like every other screen too anyway.

I think only I know how my screen actually behaves.

Because its actually smart and fully adapts to the input signal, I've never had to change the range config in the screen, and if I change in the control panel from full to limited the visual look doesn't change because it auto-adapts. HDMI has all the image properties in metadata, unfortunately the majority of TVs quite simply ignore it and expect some default mode.

huhn · 4th November 2019, 10:47

not saying your screen doesn't but the only ways for a screen to change a setting in the nvidia control panel is by pretending to be a new different screen or by HDMI content type which is again not properly supported. there is a very good reason not to do that.

auto level support is not that rare but not the point what nvidia choices to send.

kostik · 4th November 2019, 16:27

Quote:

Originally Posted by GTPVHD

https://www.nvidia.com/en-us/geforce...-ready-driver/

Nvidia Geforce 441.12 WHQL driver.

This latest GeForce Game Ready driver ( 441.12) enables G-SYNC Compatible support on LG’s 2019 B9, C9 and E9 4K OLED TVs.

Klaus1189 · 4th November 2019, 17:30

I heard G-Sync shouldn't be used with madVR. It is designed for gaming, but brings trouble with madVR or general video playing, isn't it?

Should I leave the elevated level info on the two drivers or should I remove it, or maybe add only when using 12 bit if I understood it correctly.

cremor · 4th November 2019, 18:43

Quote:

Originally Posted by nevcairiel

Sounds to me like black levels work as expected, but people get messed up Full vs Limited for some reasons, which in my experience is primarily an issue only on TVs which dont advertise full range support on their edid

If that's the case, why would those same people report that going back to older driver versions fixes the elevated blacks?

Quote:

Originally Posted by Klaus1189

I heard G-Sync shouldn't be used with madVR. It is designed for gaming, but brings trouble with madVR or general video playing, isn't it?

Yes, G-Sync messes with madVR and should be disabled. But you don't have to disable it completely. The driver actually automatically disables it for some known executables of media players like MPC-HC. For players that are not handled by the driver by default you can use nvidiaProfileInspector.

Quote:

Originally Posted by Klaus1189

Should I leave the elevated level info on the two drivers or should I remove it, or maybe add only when using 12 bit if I understood it correctly.

According to this post 8 bit is affected too. You can more clearly see it in the older version of the post, which is still available in the quote here.

edit:
Found a new post: https://www.avsforum.com/forum/40-ol...l#post58773938
So Nvidia officially confirmed the black level bug and 441.12 is still affected, but it seems like it only affects LG OLEDs.

Klaus1189 · 4th November 2019, 22:05

AMD released new Radeon Driver 19.11.1

Nastenka · 7th November 2019, 15:26

Quote:

Originally Posted by cremor

Yes, G-Sync messes with madVR and should be disabled. But you don't have to disable it completely. The driver actually automatically disables it for some known executables of media players like MPC-HC. For players that are not handled by the driver by default you can use nvidiaProfileInspector.

Is the automatic disabling a new thing? I noticed that with an older Studio driver I had to set MPC-HC to Fixed refresh rate manually, while on this current driver set the option is greyed out and says "not supported for this application".

cremor · 7th November 2019, 17:48

I don't know when this was added to the driver. I've bought my first G-Sync monitor in December 2018 and back then it was already there. Since "studio" drivers are way newer, they should have already supported that.

Decalicatan_Decalicatan · 9th November 2019, 14:48

Hi!

Do you know if there an issue with the recent nvidia drivers when playing a HDR video with "Compromise on HDR tome & gamut mapping accuracy" unchecked?

I was previously using Nvidia Driver 430.53 for my GTX 1070 and everything was fine when I played a HDR file (mpc-be with madvr "Compromise on HDR tome & gamut mapping accuracy" unchecked | SDR monitor)

I have updated the drivers to 436.48, and now when I play a HDR file the image is nearly completely dark. If I check "Compromise on HDR tome & gamut mapping accuracy" the image is watchable again.
But of course I'd prefer not compromise on HDR tome & gamut mapping accuracy.

madvr version is the latest one available on avsforum.

Thanks in advance.

Manni · 9th November 2019, 15:20

Quote:

Originally Posted by Decalicatan_Decalicatan

Hi!

Do you know if there an issue with the recent nvidia drivers when playing a HDR video with "Compromise on HDR tome & gamut mapping accuracy" unchecked?

I was previously using Nvidia Driver 430.53 for my GTX 1070 and everything was fine when I played a HDR file (mpc-be with madvr "Compromise on HDR tome & gamut mapping accuracy" unchecked | SDR monitor)

I have updated the drivers to 436.48, and now when I play a HDR file the image is nearly completely dark. If I check "Compromise on HDR tome & gamut mapping accuracy" the image is watchable again.
But of course I'd prefer not compromise on HDR tome & gamut mapping accuracy.

madvr version is the latest one available on avsforum.

Thanks in advance.

This is because you have not disabled measurements files.

I use the latest nVidia driver and there is no issue with that option.

Just disable all measurements files in the configuration section at the end of MadVR settings. They are not supported with the latest test builds.

If you don't use measurements files, then it might be something else, but it's not the driver.

Grimsdyke · 9th November 2019, 16:48

If Manni's advise does not solve this you should also check if 'don't measure HDR frame peak luminance' is also unchecked.

Decalicatan_Decalicatan · 9th November 2019, 17:53

Quote:

Originally Posted by Manni

This is because you have not disabled measurements files.

Just disable all measurements files in the configuration section at the end of MadVR settings. They are not supported with the latest test builds.
.

Thank you! You were absolutely right.

I didn't get the news about the measurements files. Change occurs so fast with MadVR beta in the "other forum" so it is very easy to miss relevant info.

Regards

TechnoPeasant · 10th November 2019, 20:09

I wonder if the recent issues with the Nvidia drivers are what I'm experiencing too. I'm unable to watch any HDR content using RGB at all. No matter what I do, the black levels wash out. Instead, I have to switch to ycbr 4:4:4, 12-bit, limited to maintain correct black levels, which I'm sure is less than ideal.

I think this all happened after a Windows update, but I'm not entirely sure. Unfortunately, on my Vizio PQ65, I'm only able to change color space manually, and not video levels.

Sucks when you have everything setup just right, and some crap Windows update ruins things.

If any of you have any suggestions, as to how I can better work around this issue, please let me know. I saw someone mentioned having to choose "PC" resolutions instead of the UHD stuff, but that category of resolutions doesn't show up in NVCP.

Warner306 · 11th November 2019, 01:37

"Color Space" in the Vizio picture menu should be set to "RGB." That is all I know. I don't know if that setting currently exists on the newest Vizio models, though.

TechnoPeasant · 11th November 2019, 01:46

Yeah, color space is there, and I can set it to RGB, but unfortunately the result is still washed out.

Warner306 · 11th November 2019, 11:52

This is with the Nvidia control panel set to output RGB 0-255?

Maybe the display now has some type of levels adjustment?

TechnoPeasant · 11th November 2019, 14:49

Yeah, RGB 0-255. That's what I'm thinking, that the TV is trying to be too helpful. That said, the Nvidia driver issues sound very similar.

TechnoPeasant · 12th November 2019, 05:04

Can confirm, the latest Vizio 4.0 firmware did nothing. I suspect the latest Windows 10 update has something to do with this, and the nvidia driver hasn't accounted for it. Bummer.

huhn · 15th November 2019, 10:36

AMD got a new driver too: https://www.amd.com/en/support/kb/re...ad-win-19-11-2
the changes are minimal at best. i will test DXVA2 stuff later.

edit: DXVA2 levels are broken
deint is still broken
i don't test dxva2 native decode anymore until they fix the very obvious stuff.

NikosD · 15th November 2019, 18:50

Quote:

Originally Posted by huhn

I don't test dxva2 native decode anymore until they fix the very obvious stuff.

As long as AMD says that "Movies & TV" works fine with HW acceleration, they will probably don't bother much to comply with other players.
The other players should comply to AMD, according to AMD.

11th November 2019, 01:37	#734 \| Link
Warner306 Registered User Join Date: Dec 2014 Posts: 1,127	"Color Space" in the Vizio picture menu should be set to "RGB." That is all I know. I don't know if that setting currently exists on the newest Vizio models, though. __________________ HOW TO - Set up madVR for Kodi DSPlayer & External Media Players

11th November 2019, 11:52	#736 \| Link
Warner306 Registered User Join Date: Dec 2014 Posts: 1,127	This is with the Nvidia control panel set to output RGB 0-255? Maybe the display now has some type of levels adjustment? __________________ HOW TO - Set up madVR for Kodi DSPlayer & External Media Players

15th November 2019, 10:36	#739 \| Link
huhn Registered User Join Date: Oct 2012 Posts: 7,922	AMD got a new driver too: https://www.amd.com/en/support/kb/re...ad-win-19-11-2 the changes are minimal at best. i will test DXVA2 stuff later. edit: DXVA2 levels are broken deint is still broken i don't test dxva2 native decode anymore until they fix the very obvious stuff. Last edited by huhn; 15th November 2019 at 13:51.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

4th November 2019, 10:47	#722 \| Link
huhn Registered User Join Date: Oct 2012 Posts: 7,922	not saying your screen doesn't but the only ways for a screen to change a setting in the nvidia control panel is by pretending to be a new different screen or by HDMI content type which is again not properly supported. there is a very good reason not to do that. auto level support is not that rare but not the point what nvidia choices to send.

4th November 2019, 17:30	#724 \| Link
Klaus1189 Registered User Join Date: Feb 2015 Location: Bavaria Posts: 1,667	I heard G-Sync shouldn't be used with madVR. It is designed for gaming, but brings trouble with madVR or general video playing, isn't it? Should I leave the elevated level info on the two drivers or should I remove it, or maybe add only when using 12 bit if I understood it correctly.

4th November 2019, 22:05	#726 \| Link
Klaus1189 Registered User Join Date: Feb 2015 Location: Bavaria Posts: 1,667	AMD released new Radeon Driver 19.11.1

7th November 2019, 17:48	#728 \| Link
cremor Registered User Join Date: Jun 2011 Posts: 81	I don't know when this was added to the driver. I've bought my first G-Sync monitor in December 2018 and back then it was already there. Since "studio" drivers are way newer, they should have already supported that.

9th November 2019, 14:48	#729 \| Link
Decalicatan_Decalicatan Registered User Join Date: Jan 2016 Posts: 5	Hi! Do you know if there an issue with the recent nvidia drivers when playing a HDR video with "Compromise on HDR tome & gamut mapping accuracy" unchecked? I was previously using Nvidia Driver 430.53 for my GTX 1070 and everything was fine when I played a HDR file (mpc-be with madvr "Compromise on HDR tome & gamut mapping accuracy" unchecked \| SDR monitor) I have updated the drivers to 436.48, and now when I play a HDR file the image is nearly completely dark. If I check "Compromise on HDR tome & gamut mapping accuracy" the image is watchable again. But of course I'd prefer not compromise on HDR tome & gamut mapping accuracy. madvr version is the latest one available on avsforum. Thanks in advance.

9th November 2019, 16:48	#731 \| Link
Grimsdyke Registered User Join Date: Nov 2013 Location: Hannover, Germany Posts: 292	If Manni's advise does not solve this you should also check if 'don't measure HDR frame peak luminance' is also unchecked.

10th November 2019, 20:09	#733 \| Link
TechnoPeasant Registered User Join Date: Apr 2019 Posts: 16	I wonder if the recent issues with the Nvidia drivers are what I'm experiencing too. I'm unable to watch any HDR content using RGB at all. No matter what I do, the black levels wash out. Instead, I have to switch to ycbr 4:4:4, 12-bit, limited to maintain correct black levels, which I'm sure is less than ideal. I think this all happened after a Windows update, but I'm not entirely sure. Unfortunately, on my Vizio PQ65, I'm only able to change color space manually, and not video levels. Sucks when you have everything setup just right, and some crap Windows update ruins things. If any of you have any suggestions, as to how I can better work around this issue, please let me know. I saw someone mentioned having to choose "PC" resolutions instead of the UHD stuff, but that category of resolutions doesn't show up in NVCP.

11th November 2019, 01:46	#735 \| Link
TechnoPeasant Registered User Join Date: Apr 2019 Posts: 16	Yeah, color space is there, and I can set it to RGB, but unfortunately the result is still washed out.

11th November 2019, 14:49	#737 \| Link
TechnoPeasant Registered User Join Date: Apr 2019 Posts: 16	Yeah, RGB 0-255. That's what I'm thinking, that the TV is trying to be too helpful. That said, the Nvidia driver issues sound very similar.

12th November 2019, 05:04	#738 \| Link
TechnoPeasant Registered User Join Date: Apr 2019 Posts: 16	Can confirm, the latest Vizio 4.0 firmware did nothing. I suspect the latest Windows 10 update has something to do with this, and the nvidia driver hasn't accounted for it. Bummer.