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

Manni

1st March 2021, 23:09

properties of your player executable-> compatibility -> check disable fullscreen optimisation.

that's know it works with mpc-hc.

Thanks, I tried with MPC-BE and it makes no difference. FSE, old or new, doesn't help.

However I noticed that I only had the issue on HDMI at 23p.

My 4K monitor on DP at 60p doesn't have the issue (but has it if I use its HDMI input at 23p).

I also noticed that it doesn't seem to happen in 10 bits, but then you have to deal with the levels issue, and the fact that the renderer seems stuck in 8bits, even if the driver is set to 10/12bits and madVR is set to 10bits or more. I haven't used 10/12bits in a while, but my memory was that you could get 10bits in windowed full screen. I tried FSE and it's also locked to 8bits, so no idea what's going on.

Doesn't make much sense, but that's what I noticed.

/i'm going to stick to D3D9 for now, the main downside is that I lose BD Menus in jRiver, as it needs D3D11 for that.

doffen

1st March 2021, 23:17

My monitor (TV) does not support 4:4:4 on 23Hz, and will go down to (i think) 4:2:2.
Maybe your monitor behaves similar, and the issue is related?

huhn

1st March 2021, 23:19

Manni

1st March 2021, 23:28

there was or is a bug in the nvidia driver with 10 bit which madshi worked around.

the GPU has to output 10 bit to make 10 bit work in madVR.

i don't have a nvidia GPU at the moment so nothing i can check right now.

Yes, the 3090 outputs can output 8/10/12, but madVR is still stuck in 8bits, even when the GPU is set to 10bits.

Anyway, 10bits isn’t ideal with my JVC and the levels are all over the place, so I’ll stick to 8bits D3D9 for now I guess.

Asmodian

2nd March 2021, 04:42

Manni

2nd March 2021, 10:56

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

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

2nd March 2021, 12:49

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

2nd March 2021, 18:44

@Manni maybe try the .reg available here to disable Multi-Plane Overlay: https://nvidia.custhelp.com/app/answers/detail/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

2nd March 2021, 20:29

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. :scared:

Manni

3rd March 2021, 01:25

@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.

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

3rd March 2021, 17:10

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

3rd March 2021, 17:36

He already has one :D

Klaus1189

3rd March 2021, 19:40

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

4th March 2021, 11:11

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.

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 (https://drive.google.com/file/d/1eLMrszqYzkKa5FU4mSR-7EBuFJUG5eOR/view?usp=sharing).

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

4th March 2021, 19:13

Vega iGPU (APU) here.

There is no flickering now. But hardware deinterlacing is still broken.
Pic (https://drive.google.com/file/d/1eLMrszqYzkKa5FU4mSR-7EBuFJUG5eOR/view?usp=sharing).

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

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?

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

4th March 2021, 21:24

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

4th March 2021, 21:27

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

5th March 2021, 01:09

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

5th March 2021, 07:24

@Klaus1189
Level settings in LAV-video do not affect anything. I always see the right levels. iGPU - full, TV - full.
Pic (https://drive.google.com/file/d/1Gy_2UCXunYM15hI0AMSTdg3o9U7wg0h7/view?usp=sharing).

huhn

5th March 2021, 11:30

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

5th March 2021, 11:39

Vega iGPU (APU) here.

There is no flickering now. But hardware deinterlacing is still broken.
Pic (https://drive.google.com/file/d/1eLMrszqYzkKa5FU4mSR-7EBuFJUG5eOR/view?usp=sharing).

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

5th March 2021, 12:06

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 (https://drive.google.com/file/d/10EV3hI6QG7ZTZfppB3oBNwJIlIRaMkVf/view?usp=sharing).

huhn

5th March 2021, 12:19

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

DMU

5th March 2021, 12:58

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?

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 (https://drive.google.com/file/d/1ZeJcJH81_H6zJE5RZuK1tOKw2SDGVPr1/view?usp=sharing) the overclocked Vega7 (R5 4650G).

Klaus1189

5th March 2021, 13:26

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

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.

DMU

5th March 2021, 16:46

Thanks, figured it out.
Pic (https://drive.google.com/file/d/12tL94htAi-QmK67Kn1YN3NNHNqK_1wbK/view?usp=sharing).

Klaus1189

5th March 2021, 16:58

There is no flickering now.

So Vega based GPUs do have a working adaptive hw deinterlacer just like my Polaris based RX480.

But hardware deinterlacing is still broken. Pic (https://drive.google.com/file/d/1eLMrszqYzkKa5FU4mSR-7EBuFJUG5eOR/view?usp=sharing).

But what deinterlacing issue is that?

What are your LAV Filters video settings? I mean copyback, ...

DMU

5th March 2021, 17:11

But what deinterlacing issue is that?
Don't know (https://forum.doom9.org/showthread.php?p=1918678#post1918678).

What are your LAV Filters video settings? I mean copyback, ...
Yes, but it does not matter.

VBB

5th March 2021, 19:40

GeForce Hotfix Driver Version 461.81

https://nvidia.custhelp.com/app/answers/detail/a_id/5168/~/geforce-hotfix-driver-version-461.81

Nothing HTPC related...

el Filou

8th March 2021, 18:14

https://community.intel.com/t5/Graphics/AV1-DXVA2-decoding-broken-27-20-100-9033/m-p/1250542#M93831"DirectX 9 support for AV1 decoding has been disabled in the latest drivers since Intel is on its way to deprecate native DirectX 9 support." :(
I hope this doesn't mean soon with newer hardware you'll have to use D3D11 to get any hardware decode or processing in apps.

Andy o

10th March 2021, 10:46

QMS uses HDMI VRR internally, so this is strange. Do PC graphics cards support HDMI VRR?
It would need to at least be on for QMS to work.

Sorry, didn't see this before. Yes, both AMD and NV new gen cards support VRR, not just FreeSync and G-Sync respectively. I've seen a few posters who are pretty sure that QMS works, but the source seems to be that rather ambiguous post that I linked. I have a 3070 so I'm wondering if anyone with a RX6000 is experiencing the same as that person.

Andy o

10th March 2021, 11:10

Sorry for the late reply Andy.

Yup same vein with me, it's now even happening on lossy Dolby Digital and Dolby Digital+. Even had a skip with PCM last night (was watching anime)!

Mind blown at these issues. I'm lost actually, if it isn't a hardware problem, isn't an OS problem, isn't a player problem, then wtf else is it??? :angry:

I have the receiver connected exactly as you said, but all the inputs are handled on the receiver instead of on the TV. eARC is just enabled when I decide to watch netflix/prime through the TV's app instead (which is better than the trash windows 10 netflix app). Firmware on my C9 is 5.00.03. Thing is, the audio drop out has happened all the way back since 4.71.25. Doubt it's the TV causing any issues since the audio stops at the receiver anyways.
OK this might be a long shot but by any chance you have the Dolby Access app installed? I read a couple (https://www.reddit.com/r/nvidia/comments/jyrh39/any_30803090_lg_c9_users_doing_4k120hz_dolby_atmos/) of posts (https://www.reddit.com/r/OLED_Gaming/comments/jmyfx3/lg_c9_audio_cutting_out_on_pc_with_dolby/) that suggest there's issues with the app, and uninstalling it seems to have worked for me, but I still need to test it more cause I've been here before with something that seemed to work and then it didn't. The second post in particular is talking about gaming, which is what the Dolby Access app works for, but one doesn't need it for DirectShow players like we're using. Of course now I can't game in Atmos, but right now I'm just testing to see if MPC-HC works fine without dropouts, and if I'm convinced it's definitely the Access app, I'll probably make another user profile with the app installed just for gaming.

This didn't even affect only Atmos audio, even the DTS-HD dropouts seem to be gone (again, crossing fingers). I'll come back to eat my words if I start getting them again, but just putting it out there so there's more people to corroborate.

EDIT: well that was a bust, the dropouts are still there. On the bright side I don't have to wait until Dolby fixes its app, it's more likely the solution is something else.

Klaus1189

16th March 2021, 20:23

I installed the hotfix driver 461.81 earlier and got still one dropout after several days, I think there is no difference between 461.81 and 461.92, but I am gonna see. Perhaps this issue is fixed...

When do you think the GPU market is back to "normal"? Reasons?

SamuriHL

16th March 2021, 20:55

2031. cause nVidia and AMD suck. :D

Manni

16th March 2021, 21:06

huhn

17th March 2021, 00:12

2031. cause nVidia and AMD suck. :D

you forgot intel!

SamuriHL

17th March 2021, 01:12

Everyone does. ;)

jkauff

17th March 2021, 17:21

I had to revert to an older driver as I was getting BT2020 forced even when I should have been in SDR 709 ( for example on the desktop). I didn’t try the latest though. I’ll wait for the next studio driver.
I must be having the same issue. When I boot up, the screen shows "HDR". My GTX 1080 is in an eGPU box attached with Thunderbolt, so I thought that might have something to do with it.

What older drive worked for you, Manni?

Klaus1189

17th March 2021, 17:48

I’ll wait for the next studio driver.

Time has come. Today new studio driver :)

Manni

17th March 2021, 19:48

What older drive worked for you, Manni?

I don’t think it’s the same issue as I checked and was not in HDR mode, just BT2020. Also I have a 3090, so quite different. I have lost track of which driver I used with my 1080ti before the upgrade unfortunately. Currently I use the one listed in my sig, 460.89.

Manni

17th March 2021, 19:49

Time has come. Today new studio driver :)

Drat, I was hoping they would give me a bit more time :)

KrazyLurt

18th March 2021, 15:48

Updating to Nvidia GeForce 461.92 made NV HDR in MadVR unusable. NV HDR is activated in the OS but HDR isn't applied to the video i.e washed out.

Regular OS HDR is working like before.

This is with a RTX 3080 using mpc-hc and pot player

quietvoid

18th March 2021, 15:51

I updated to 461.92 and the only time HDR is wrong is when madVR isn't in fullscreen, so just like the previous 46x version I was on.
I think however that outside of fullscreen, the whole desktop is wrong now instead of being correct SDR?

nsnhd

18th March 2021, 16:18

Thanks guys, that's what I meant in my summary before, that this is nuts. Literally the last driver that is good (not perfect :)) for madvr is the 398.18. And that is 2 and a half years old!!! :D

Hi,
If I remember correctly you've changed from 385.28 which I'm using now for GTX 1060 6gb. But that version might have issues with the new Kodi 19 dxva2 decoding, I'm not so sure but may try to update.
So what benefits does 398.18 get over 385.28 at all? Does 3D still work well incase you're using it ?
Thanks

brazen1

18th March 2021, 16:44

Using GRD 461.92 now. NV HDR still has the fullscreen to windowed and GUI access problem (HDR goes into SDR mode). Still has the Windows audio switch depending on AVR on/off state problem. The desktop SDR is correct for me. SDR and HDR via madVR with MPC-BE still working well including timings. Official Kodi v20 VideoPlayer SDR and HDR full menu playback (iso's) still working correctly. Fwiw, because Kodi uses Windows HDR, there is no HDR to SDR malfunction when the player is Windowed or accessing the player GUI. Still passing through using madVR v0.92.17 with a GTX 960.