AMD, Intel and Nvidia driver issues and last recommended version

[Manni]

Originally Posted by Asmodian

I don't have any of these issues with my 3090 so I don't think it is a general problem.

Windows 10 20H2 (19042.844)
Nvidia 461.72 (DCH) 10 bit YCbCr output
madVR FSW D3D11 10 bit

I don't have any issues tone mapping HDR to SDR or having madVR switch to 10 bit if I set my display to 10 bit. It tried G-sync on/off, 23Hz, and 120Hz. All using HDMI 2.1 to my LG CX.

Thanks, but I never said it was a general problem, I even specified it was only happening with RGB 8bits. It doesn't happen in 10bits, as reported above. I haven't tested YCC for this.

Unfortunately the levels are wrong with my JVC RS2000 when using 10bits (non-8bits levels have been broken for ages with the JVC with nVidia), plus due to an internal processing limitation the JVCs force YCC 4:2:2 when fed 4K 10/12bits content even at 23p, so 10bits isn't an option as this leads to a double chroma down/upscaling behind madVR's back.

Not using HDMI 2.1, neither my AVR nor my projector support this yet (so only 2.0).

Not sure how you get 10bits to work in madVR though, there was no way to get it to work here, even in 10bits. It used to work with the 1080ti, eventhough I was not using it. The JVCs support 10/12bits fine.
I'm extending the desktop to my LG 4K monitor that only supports 8bits, I'll try to disconnect it, maybe that's why I can't get madVR to work in 10bits. I didn't use to have this with the 1080ti.

Are you using YCC 422 or YCC 444?

Also which version of madVR are you using? The latest test build? I'm on 128, maybe something got broken along the way?

[Manni]

Update:

I have resolved the weird colors with d3d11 by reuploading my custom EDID to the HD fury maestro. [edit: nope, it’s back]

however, there are still weird issues with d3d11, for example it clips levels on patterns unless you right click on the screen. no such issue with d3d9 here.

i tried to get into 10bits mode in ycc, and only manage to do so briefly by enabling FSE on the fly. but if I enable FSE in options, its still 8bit on start; I have to go to window and back to fullscreen to get 10bits again.

Anyway, I dont have the time to debug madVR at the moment, so Ill just keep using d3d9 for now. Sorry for the off topic.

[can’t use d3d9 as I not only lose menus in jRiver, I also lose forced subs. So I’m just going to stop using the HTPC as a source]

[el Filou]

@Manni maybe try the .reg available here to disable Multi-Plane Overlay: https://nvidia.custhelp.com/app/answ...tail/a_id/5157
I know the KB article doesn't mention colors, but MPO is a feature of the newer driver, so who knows?

[Asmodian]

Originally Posted by Manni

Thanks, but I never said it was a general problem, I even specified it was only happening with RGB 8bits. It doesn't happen in 10bits, as reported above. I haven't tested YCC for this.

Sorry, I missed that it only happened with 8 bit. I was simply seeing if I could reproduce it.

I cannot, even using 23 Hz 8 bit full range RGB everything seems the same. I can still get madVR to output 10 bit too. Levels seem fine using test patterns.

I wonder what component is causing your system to behave so differently.

[Manni]

Originally Posted by el Filou

@Manni maybe try the .reg available here to disable Multi-Plane Overlay

Thanks but that wouldn't make a difference, I had already tried to go back to 460.89 and that didn't help.

Originally Posted by Asmodian

Sorry, I missed that it only happened with 8 bit. I was simply seeing if I could reproduce it.

No worries. So many variables in a HTPC... It could be my JVC, my AVR, my HD Fury Maestro, HDMI 2.0 vs HDMI 2.1, who knows?

If/when I find the time I'll try to connect the JVC direct to the 3090 to see if that makes a difference. In the meantime, I'll just give up and use another source.

[jkauff]

Originally Posted by Manni

No worries. So many variables in a HTPC... It could be my JVC, my AVR, my HD Fury Maestro, HDMI 2.0 vs HDMI 2.1, who knows?

Maybe you should just buy an Envy.

[chros]

He already has one

[Klaus1189]

After 8 days of testing Nvidia driver I got one dropout / flicker / short black screen just now. This is way better than before, but still not perfect. And I am not sure, but if I watch YouTube videos in Firefox, I think I can hear some crackling sometimes, but very little and very rare, but if I rewind to the point the crackling is also there at the time. So it could also be in the video itself. I don't know. If I watch quality sources with MPC-BE there is no issue as far as I am aware of. Same for foobar2000 with music there is no issue.

Again: If you are a Vega or Radeon VII user please let me know. I think I pin it on first post.

[DMU]

Originally Posted by Klaus1189

Again: If you are a Vega or Radeon VII user please let me know. I think I pin it on first post.

Vega iGPU (APU) here.

Originally Posted by Klaus1189

The Hardware Deinterlacer should be aware that the characters above "WWW.D88.COM" are progressive and should not be deinterlaced, otherwise you will see flickering like in this picture

There is no flickering now. But hardware deinterlacing is still broken.
Pic.

Originally Posted by Klaus1189

color levels (full 0-255 vs. limited 16-235) are broken, that means limited 16-235 which is the standard range for videos are interpreted as 0-255 and this leads to elevated blacks and dimm whites.

I don't see any issues with color levels.

PS: small addition:
• 20.3.1 2020-03-19 This version fixes all HDR issues with Navi and Vega based cards, like a RX 5700 (XT)

[Klaus1189]

Originally Posted by DMU

Vega iGPU (APU) here.

There is no flickering now. But hardware deinterlacing is still broken.
Pic.

How would a professional call this issue? I have never seen anything like that.

Originally Posted by DMU

I don't see any issues with color levels.

Could you test in MPC-BE or MPC-HC if setting the output range in video tab, where the video renderer is, does take effect, I mean if you set it to 0-255 and if you set it to 16-235, does it make a difference in black levels?

Originally Posted by DMU

PS: small addition:
• 20.3.1 2020-03-19 This version fixes all HDR issues with Navi and Vega based cards, like a RX 5700 (XT)

Added

[DMU]

Originally Posted by Klaus1189

Could you test in MPC-BE or MPC-HC if setting the output range in video tab, where the video renderer is, does take effect, I mean if you set it to 0-255 and if you set it to 16-235, does it make a difference in black levels?

I use mpc-hc/madVR. If I understand correctly, the output range settings in LAV video are ignored in this case. If I change levels in madVR devices -> properties, the changes in the black/white levels of the image change predictably.

[Klaus1189]

Change video renderer to evr cp and do then test. madVR is not affected by this issue.

After that select madVR in video renderer settings and you got back your original settings.

[Manni]

Just to conclude my off-topic, bd menus in jRiver works fine with d3d9, thanks to Nevcariel I realised that it was switching to d3d11 because I have only disabled d3d11 in my UHD profile, but Nev remarked that a 1080p screen was probably called first and then it stuck to d3d11. Disabling d3d11 in all my profiles resolved the issue.

So I haven't resolved the issues I have with d3d11, but at least I can get everything to work as it should with d3d9.

[DMU]

@Klaus1189
Level settings in LAV-video do not affect anything. I always see the right levels. iGPU - full, TV - full.
Pic.

[huhn]

as you already stated lavfilter is unrelated. the level settings are nearly near been used you need to force RGB output so it is used and there is no "reason" to do that.
this is what i get with AMD an 5700XT:
https://abload.de/img/blackjhk3h.png

this is not happening in madVR because madVR ask for limited range and does the level by itself.
and web browser are usually not triggering this bug too.

and as said before all setting regarding sharpness deint quality colors levels and so much more have been forgotten in the driver the page is still present but the options are missing.

there s no known driver that doesn't have this problem.
this is the biggest video related driver bug that has never been fixed.

[nsnhd]

Originally Posted by DMU

Vega iGPU (APU) here.


There is no flickering now. But hardware deinterlacing is still broken.
Pic.


I don't see any issues with color levels.

PS: small addition:
• 20.3.1 2020-03-19 This version fixes all HDR issues with Navi and Vega based cards, like a RX 5700 (XT)

It seems that AMD has improved a lot. How good or bad can your 2200G APU deal with HDR tone mapping or upscaling ?

[DMU]

Originally Posted by huhn

there s no known driver that doesn't have this problem.
this is the biggest video related driver bug that has never been fixed.

Can't figure out how do I get this bug?
Pic.

[huhn]

vega APUs doesn't seem to be affected which is good meaning the driver is in theory able to do this part correctly.

[DMU]

Originally Posted by huhn

vega APUs doesn't seem to be affected which is good meaning the driver is in theory able to do this part correctly.

Agree, but level settings in LAV-video do not affect anything. But they should?

Originally Posted by nsnhd

It seems that AMD has improved a lot. How good or bad can your 2200G APU deal with HDR tone mapping or upscaling ?

Much depends on the memory bandwidth. As an example the overclocked Vega7 (R5 4650G).

[Klaus1189]

Originally Posted by DMU

Agree, but level settings in LAV-video do not affect anything. But they should?

Originally Posted by Klaus1189

Could you test in MPC-BE or MPC-HC if setting the output range in video tab, where the video renderer is, does take effect, I mean if you set it to 0-255 and if you set it to 16-235, does it make a difference in black levels?

Not in LAV Filters, but in Options -> Video -> below selection of Video renderer there is Output range. Just to test if changing this setting from 0-255 to 16-235 does alter the black levels. It must change, otherwise there is an issue.
And you should use EVR cp for this test.