AMD, Intel and Nvidia driver issues and last recommended version

[SamuriHL]

Curious if the drivers expose any additional functionality over the 2xxx cards. I don't think we've yet seen anyone get their hands on a card so it'll be nice to see if the drivers are stable for them, what functionality hdmi 2.1 exposes in the driver if any, and the performance in madvr. Can't wait to see that kind of info.

Sent from my SM-G975U using Tapatalk

[Manni]

I've only tested 8bits RGB with 456.38 (Studio / Standard) as that's what I use and don't have the time to do any other tests at the moment, but at least with that I can confirm that HDR works fine (with nvAPI) and that if using passthrough the HDR10 metadata is sent properly.

I don't know how it behaves in 12bits or in YCC.

[EDIT: Also I'm still using CRU so I haven't tested native frame rate.]

I don't have the issue of the "double switch" for HDR. It switches seamlessly between SDR and HDR, or SDR BT2020 and HDR passthrough.

So at least at first sight, it seems good to go :)

I'll post if I find any issue.

My full config is in my sig, YMMV.

I experienced issues with this driver and the following ones. It now outputs weird null HDR metadata and I can't get auto SDR tonemappint without forcing passthrough first then going to SDR tonemapping.

I tried most drivers before that and had to revert all the way back to 442.74 to get predictable, reliable HDR<>SDR auto switch with NV API in madVR. Even 442.92 had some issues.

Not sure why the more recent drivers stopped working, maybe an OS update?

This is with 1909 and a GTX 1080ti (full config in sig). YMMV.

[chros]

Even 442.92 had some issues.
Not sure why the more recent drivers stopped working, maybe an OS update?
This is with 1909
Like this (https://forum.doom9.org/showthread.php?p=1922074#post1922074)? I'm on 1809, so it seems it's not the newer windows.
And what about this (https://forum.doom9.org/showthread.php?p=1921810#post1921810) audio issue?

[Manni]

Like this (https://forum.doom9.org/showthread.php?p=1922074#post1922074)? I'm on 1809, so it seems it's not the newer windows.
And what about this (https://forum.doom9.org/showthread.php?p=1921810#post1921810) audio issue?

I can’t remember exactly, I think it’s more that when you start an HDR clip, by default it is outputting HDR passthrough here, and you have to manually switch to SDR tonemapped. Unlike some of the newer drivers, you can get the right mode manually, while some of the newer drivers are stuck in this weird NULL hdr metadata mode that prevents the right mode from being selected (I use a Maestro to switch calibration automaticallly, so I need no HDR metadata for my SDR tonemapped calibration to be applied.

I don’t have these audio issues but I use HDMI bitstream as I need it for immersive sound.

Bottom line is that here, with 1909 and a GTX 1080ti, only 442.74 or earlier works fully as expected (and I’ve only tested RGB 8bits).

I use CRU so the better refresh rate of the new drivers doesn’t make a difference.

[Klaus1189]

That's a bummer. Please let me know if I should update the Nvidia section.
If you have a spare SSD laying around, would be nice if you could set up Windows 10 2004 fresh on it and test the new driver. Would be interesting if the driver behaves the same on 2004. You can just put the old one back in the pc and the pc will work as nothing would had happend. I did this before on my own.
I know it will be some time, but what what do we all for testing our stuff ;-)

[Manni]

That's a bummer. Please let me know if I should update the Nvidia section.
If you have a spare SSD laying around, would be nice if you could set up Windows 10 2004 fresh on it and test the new driver. Would be interesting if the driver behaves the same on 2004. You can just put the old one back in the pc and the pc will work as nothing would had happend. I did this before on my own.
I know it will be some time, but what what do we all for testing our stuff ;-)

I don't have the time to use another drive at the moment, but I'm probably going to cancel my 3090 order as it looks like their ETA of the 5th was BS and I'm close to number 100 in a waiting list that doesn't move. Plus, they have already charged my VISA! This is SCAN in the UK, and I'm not impressed by the way they handle this. If you don't know when a product ships, don't charge the customer!

So I think I'm going to cancel next week and wait until we know more about the 3080ti as it might be on TSMC 7nm according to rumours, which might make it a bit less power hungry than the 3090. I don't really believe they'll move the already released card to 7nm, but that's still a slight possibility.

This means that I might attempt to upgrade the OS anyway, but it's unlikely I'll find the time until early November due to work. I'll let you know as soon as I can test this. I image my drives before any big change, so I can always go back if there are more issues with 2004 and no improvement.

For now, I would update the nVidia session and mark 442.74 as last known fully working driver re HDR for GTX and 1909 or previous, at least if your video chain detects content and automatically switches to the correct calibration (HD Fury Vertex/Diva/Maestro or new JVCs). Unless anyone confirms a more recent driver works, we can't rule out something in my config for course.

[SamuriHL]

I'll check later this morning to see if they broke it again. They had fixed that in one of these recent driver versions. I'll need to find a working hdmi cable to hook the integral back up.

Sent from my SM-G975U using Tapatalk

[Manni]

I'll check later this morning to see if they broke it again. They had fixed that in one of these recent driver versions. I'll need to find a working hdmi cable to hook the integral back up.

Sent from my SM-G975U using Tapatalk

You have an RTX GPU, my report is only about GTX (1080ti).

I don't think the issue is the same with more recent GPUs (or maybe a more recent OS).

[SamuriHL]

You have an RTX GPU, my report is only about GTX (1080ti).

I don't think the issue is the same with more recent GPUs (or maybe a more recent OS).

I can't imagine it'd be different between GTX and RTX on the HDR metadata. I could be wrong I suppose but I've not checked the last 2 driver versions since they fixed it. Still trying to hunt down a working HDMI cable in the house somewhere but I'll check anyway. Then we'll know for sure if it's different.

EDIT: Found a working cable. Yes, on build 19042 of Windows 10 I am indeed getting proper metadata with 456.71. So there does appear to be a difference after all.

[chros]

456.71 is performing better than I anticipated.
The audio problem no longer exists! (Stereo vs Multichannel dependent on AVR On/Off state). This was problematic for years. I no longer have to modify the installation with an older HDAudio driver.

Bottom line is that here, with 1909 and a GTX 1080ti, only 442.74 or earlier works fully as expected (and I’ve only tested RGB 8bits).

mark 442.74 as last known fully working driver re HDR for GTX and 1909 or previous, at least if your video chain detects content and automatically switches to the correct calibration (HD Fury Vertex/Diva/Maestro or new JVCs).

OK, thanks, I went back as well to 442.74 + hdmi audio from 456.71 (by copying over "HDAudio" directory), I'll report back in a week if all is good here.

I noticed 1 issue (?) straight away, that I haven't before (not even with 442.92 SD):
- 12bit nv output
- madvr OSD is enabled
- mpc-be/hc fullscreen window: madvr reports 10bit
- but when seekbar comes up at the bottom: madvr reports only 8bit!

I don't remember whether it worked like this or not previously. :)

I don’t have these audio issues but I use HDMI bitstream as I need it for immersive sound.

Cheers, then I guess it's my Win10 version :)
The issue with HDMI audio is:
- you have setup speaker config (e.g. to 5.1) and properties (e.g. to 41kHz) of NV HDMI device in Windows (under Sound in CP)
- if you click on Configure again and cancel the dialog (or hit escape) then it reverts back to default (!) stereo 48kHz config :D

This doesn't happen when you do the same with the Properties dialog.

[Manni]

As I said, I only tested 8bits RGB :)

[SamuriHL]

I'm only using RGB 8 bit myself these days.

[Manni]

I'm only using RGB 8 bit myself these days.

I was replying to Chros :)

[SamuriHL]

I know you were. I'm just agreeing it's the way to go. :D

[chros]

I disagree, 12bit is the ultimate solution :D

[Manni]

I had to make an image of my SSD so I thought I'd give a quick try to 2004.

Bad news: the behaviour is the same with my 1080ti. 456.71 causes a fake HDR mode that prevents the SDR calibration to be selected.

456.71 was installed after the update, so I tried a full clean install with CRU, same results.

I had to revert to 442.74 to get the expected behaviour.

So the OS has nothing to do with this.

The good news (for me) is that the OS update finally resolved my super long start for the nVidia cPanel. I'm back to normal start time of a few secs.

So unless I find some unseen downsides, it looks like I'm going to stay on 2004. I'll update the thread if it wasn't the case.

Again, this is only for GTX as I haven't tested the new drivers with GTX.

I have also only tested RGB 8bits :)

[ryrynz]

The often unnecessary solution you mean.

[Manni]

The often unnecessary solution you mean.

No idea what you mean.

[SamuriHL]

That's seriously crazy that you have such wildly different HDR results on the 1080ti than I do on my RTX. What the hell is nVidia doing lately.....sigh

[ryrynz]

No idea what you mean.Was a reply to chros [emoji6]

Manni did you use madVRs calculated values with CRU for 24hz?

[JonnyVee]

Has anyone tested a 3080 or 3090 GPU yet with HDR - SDR? I can only get MPC-BE (1.5.5.5433) with its internal filters to convert HDR properly.

If I use anything with LAV filters such as MPC-HC or kodi DSplayer I get extreme blown highlights when in Fullscreen windowed and FSE. However, it’s fine when windowed. This is with the older internal LAV and newer 0.74.1 via external.

The attached pictures show the (1] excess highlights (not sure if this is the correct term) when fullscreen, (2) correction to normal when windowed, and (3) the correct conversion using MPC-BE’s internal filters.

This happens with MPC-BE as well when I use LAV External with 0.74.1. However, its fine with the included internal filters.

I’m using an EVGA 3080 FTW3 Ultra and this occurs with 456.38 and 456.71 drivers. I’ve also tried 8 and 10 bit, and RGB &YCbCr.

[Manni]

That's seriously crazy that you have such wildly different HDR results on the 1080ti than I do on my RTX. What the hell is nVidia doing lately.....sigh

Not really, it's a different architecture and most probably different drivers internally, even if the package is the same. Also they tend to spend more testing time on the more recent architecture with recent drivers, so it makes sense. There is often a point where it's preferable to stop updating, as only the new gens are improved, the older ones can get worse.

In the latest drivers, the 1080 GTX gen are the last supported.

Was a reply to chros [emoji6]

Manni did you use madVRs calculated values with CRU for 24hz?

Ah sorry, that makes sense :)

No I use my own values for the JVC rs2000. madVR has stopped working a long time ago re refresh rate optimisation here.

I get no drop/repeat for more than 3 hours or more (often no drop/repeat after a while) with 442.74 + CRU, so I'm a happy camper. :)

It's really nice to have the nVidial cPanel working normally again. Something had messed it up (I think one of the "bring 3D back" packages) and nothing could bring it back.

If there is no downside, that alone was worth the upgrade to 2004.

By the way, even with 442.74 I occasionally get the wrong HDR mode, but if I select HDR passthrough and then SDR pixel shader, I get the correct mode, contrary to the newest drivers that stay stuck in the wierg HDR null metadata mode.

[SamuriHL]

Not really, it's a different architecture and most probably different drivers internally, even if the package is the same. Also they tend to spend more testing time on the more recent architecture with recent drivers, so it makes sense. There is often a point where it's preferable to stop updating, as only the new gens are improved, the older ones can get worse.

In the latest drivers, the 1080 GTX gen are the last supported.


I suppose there is that but it's not like the 10xx cards are that old. Good god.

[chros]

By the way, even with 442.74 I occasionally get the wrong HDR mode, but if I select HDR passthrough and then SDR pixel shader, I get the correct mode, contrary to the newest drivers that stay stuck in the wierg HDR null metadata mode.
Really?! I just spent on it 2 hours this morning :) Bloody hell, what a mess :D Thanks for reporting, I'll keep an eye on it then.
Maybe we should go way back to 430.53... Unfortunately I can't easily test HDR metadata, if I could then I'd go back and try bunch of them.

@JonnyVee, upload the images to an external image host and link them here.

[VBB]

Manni is correct as far as support when it comes to the Nvidia Studio Drivers. The Game Ready Drivers still offer full support all the way back to the 600-series:

"Effective April 12, 2018, Game Ready Driver upgrades, including performance enhancements, new features, and bug fixes, will be available only for desktop Kepler, Maxwell, Pascal, Volta, Turing and Ampere-series, as well as for systems utilizing mobile Maxwell, Pascal, and Turing-series GPUs for notebooks."

[SamuriHL]

That's right I forgot he's using studio drivers. I've been using game ready lately cause I'm getting ready for Cyberpunk 2077.

[blu3wh0]

So I just upgraded from my 1080 Ti to a 3080 and finally got around to testing MadVR. Good news, the issues with HDR on my 1080 Ti where I had to open the file twice to get HDR properly working has been resolved, although it only seems to work in fullscreen and any opening of the menu or looking at the status bar breaks it, but at least it switches really quickly. However, the card introduced really annoying micro stutters when playing at 23Hz mode (fullscreen windowed mode, in normal windowed it's fine). The stutter becomes significantly worse if you just move the mouse or start bringing up the menu. Switching to 60Hz with smooth motion does seem to mostly remove the problem, but I think it still stutters a bit. At 100Hz it's no longer noticeable to me. I believe the solution previous brought up for the 20 series for a similar problem was to set present ahead frames to 1, and this appears to have alleviated the problem. For now, this setting and watching at 60Hz instead is a good solution, but this really should not be a problem. It seems like it's always one step forward and two steps back with these things...

[JonnyVee]

Really?! I just spent on it 2 hours this morning :) Bloody hell, what a mess :D Thanks for reporting, I'll keep an eye on it then.
Maybe we should go way back to 430.53... Unfortunately I can't easily test HDR metadata, if I could then I'd go back and try bunch of them.

@JonnyVee, upload the images to an external image host and link them here.

Here’s links to the full size images

https://imgur.com/e7S8uoQ

https://imgur.com/Fucko6q

https://imgur.com/pWeCDJ6

[ryrynz]

I suppose there is that but it's not like the 10xx cards are that old. Good god.

True but he has a point. Every update has that possibility to potentially break things that haven't been tested and given these changes are generally made for newer cards there's likely greater chance for breakage of functionality for older cards. Still on 1809 and 385.28 for exactly this reason, it just works.

[SamuriHL]

Sure but the alternative point of view is that it should be a very well known quantity at this point. But I get it.

[chros]

Still on 1809 and 385.28 for exactly this reason, it just works.
Really? Do you have multimonitors, e. g. TV + monitor? It didn't work here e.g. after sleep, I got blank screen on monitor if video played only on TV. This was flawless with 1607.
That's why I upgraded the driver when SamuriHL stated that 442.92 is good again.

[el Filou]

I went back as well to 442.74 [...] I noticed 1 issue (?) straight away, that I haven't before (not even with 442.92 SD):
- 12bit nv output
- madvr OSD is enabled
- mpc-be/hc fullscreen window: madvr reports 10bit
- but when seekbar comes up at the bottom: madvr reports only 8bit!I think it's normal behaviour because 10bit only works in fullscreen windowed, and once you display GUI elements it swtiches to windowed instead of fullscreen windowed. At least that was the case in 2018: https://forum.doom9.org/showpost.php?p=1838798&postcount=50141

[Klaus1189]

I think it will take some time till I get one ...
https://www.proshop.de/RTX-30series-overview

And I am still open for RDNA2

[SamuriHL]

I'll continue to wait until the cards actually exist in the real world. LOL

[chros]

Really?! I just spent on it 2 hours this morning :) Bloody hell, what a mess :D Thanks for reporting, I'll keep an eye on it then.
Maybe we should go way back to 430.53... Unfortunately I can't easily test HDR metadata, if I could then I'd go back and try bunch of them.
Yep, after a week without reboot the 442.74 is shite as well :)
Although I didn't have the SDR in HDR issue as before, but madvr doesn't change the metadata for sure when modifying the display peak nits (checked with the second code value (https://forum.doom9.org/showthread.php?p=1882713#post1882713) on B8).
So, what's next? :)

True but he has a point. Every update has that possibility to potentially break things that haven't been tested and given these changes are generally made for newer cards there's likely greater chance for breakage of functionality for older cards. Still on 1809 and 385.28 for exactly this reason, it just works.
You forgot to answer to the question below, thanks.
Really? Do you have multimonitors, e. g. TV + monitor? It didn't work here e.g. after sleep, I got blank screen on monitor if video played only on TV. This was flawless with 1607.

[Klaus1189]

Yep, after a week without reboot the 442.74 is shite as well :)
Although I didn't have the SDR in HDR issue as before, but madvr doesn't change the metadata for sure when modifying the display peak nits (checked with the second code value (https://forum.doom9.org/showthread.php?p=1882713#post1882713) on B8).
So, what's next? :)

What Nvidia driver is recommended now? :scared:

[SamuriHL]

I'm still recommending 456.71 which has proper metadata, good clocks, and a good audio driver. But I know not everyone agrees with that.

EDIT: FOR RTX CARDS cause who cares about GTX. :p :D LOLOLOLOL

[chros]

How would I know? :D That's what we try to find out...

[Manni]

I'm still recommending 456.71 which has proper metadata, good clocks, and a good audio driver. But I know not everyone agrees with that.

You can’t make the same recommendation for GTX and RTX...

[SamuriHL]

You can’t make the same recommendation for GTX and RTX...

Then Klaus1189 needs to understand that and will have to split the list. Which makes maintaining it slightly more complicated. I'm not saying I disagree, just that it needs to be well understood that RTX and GTX cards should be treated as completely different.

[Klaus1189]

That's no problem, just give the info and I update the Nvidia section ;)

[SamuriHL]

You see my recommendation for RTX. Manni and chros (or others) will have to give a definitive recommendation for GTX, as manni is very correct, they are not working right with the latest driver builds.

[Manni]

That's no problem, just give the info and I update the Nvidia section ;)

You have already added a note for 442.74, but 1909 is not related as I installed 2004 and confirmed that past 442.74 the issues were similar with 2004.

So my most recent driver recommendation for GTX is 442.72, but it works a little bit better with 1909 than with 2004.

However, I made it clear that it was my recommendation when using a HD Fury to select the correct calibration according to content for a JVC. Others with different needs or using different hardware might have different results and might be able to use different drivers.

HTPCs are so complex that it’s really hard to make blanket recommendations.

For now, I’m on 442.72 on 2004, but this might change as I have little time for testing.

I’m also hoping that I’ll be able to upgrade to RTX and use a more recent driver without having to do more tests with GTX :)

[SamuriHL]

I’m also hoping that I’ll be able to upgrade to RTX and use a more recent driver without having to do more tests with GTX :)

:D Most excellent. LOL

[huhn]

isn't RTX and GTX very misleading? isn't this more about turing and pascal. i mean there is the 1600 series and i have a hard time believing they behaviour different then the "RTX" cards. and who knows what't wrong with ampare in theory it exists but that's it for now.

[SamuriHL]

I don't know. Someone with a GTX 16xx card needs to chime in on that one. It's very possible it's a pascal vs turing thing but we need someone to test that theory.

[ryrynz]

Really? Do you have multimonitors


Just a TV, sleep functions fine here.
Waiting for someone to say they can get a 30 series running perfectly with no frame drops/repeats for almost 3 hours by whatever means.
Maybe next year.. Along with a new madVR version.. :eek:

[SamuriHL]

Wouldn't that all be nice. I'm wanting to do that myself but can't get a hold of a 3080. I think next year is probably realistic for the earliest on both of those wish list items. Let's hope they don't break the damn drivers in the meantime.

[glc650]

I don't know. Someone with a GTX 16xx card needs to chime in on that one. It's very possible it's a pascal vs turing thing but we need someone to test that theory.I have a 1660 and was stuck on 442.74 for the longest time due to the FS windowed 10 bit HDR issues documented on this site. I haven't noticed any issues with latest Windows 10 and latest nVidia drivers. Latest drivers (even before latest Windows 10) increased time before frames repeated/drop on 23/24p content (which doesn't matter to me since I use madVR to optimize my resolutions with most of them being fully optimized) and fixed the audio issue. And I like that mpc-hc now leaves HDR when pausing/seeking/right click menu - much easier on the eyes that way. I have a Sony 75Z9F and Marantz SR1812. My 1660 is connected directly to both (HDMI to TV and HDMI (via DP to HDMI adapter) to AVR) because I've had issues passing all resolutions/frame rates/etc through my AVR.

[Manni]

I have a 1660 and was stuck on 442.74 for the longest time due to the FS windowed 10 bit HDR issues documented on this site. I haven't noticed any issues with latest Windows 10 and latest nVidia drivers. Latest drivers (even before latest Windows 10) increased time before frames repeated/drop on 23/24p content (which doesn't matter to me since I use madVR to optimize my resolutions with most of them being fully optimized) and fixed the audio issue. And I like that mpc-hc now leaves HDR when pausing/seeking/right click menu - much easier on the eyes that way. I have a Sony 75Z9F and Marantz SR1812. My 1660 is connected directly to both (HDMI to TV and HDMI (via DP to HDMI adapter) to AVR) because I've had issues passing all resolutions/frame rates/etc through my AVR.

Thanks for the feedback, but are you using HDR passthrough or pixel shader tonemapping?

In any case yes I would expect the issue I experience with recent drivers to be a pascal vs turing issue (didn't think nVidia was stupid enough to call a pascal card RTX or a Turing card GTX, but I guess in the 16xx case they disabled raytracing, is that why?).

Anyway, there shouldn't be any issue with Pascal if you use HDR passthrough because that's the issue I have with my GTX 1080ti: HDR is incorrectly detectly by my video chain despite using pixel shaders (hence sending SDR content) because the driver sends bogus HDR metadata along with the tonemapped SDR content. I have to select HDR passthrough and then pixel shaders again to get the correct mode and calibration. It's only two buttons on the iPad, but still, it's annoying.

This almost never happens with 472.74 on 1909, it happens occasionally with 472.74 and 2004, but I can toggle manually as indicated above when it does.

Although the wrong mode is almost always selected by default with more recent drivers due to the bogus metadata, I can still toggle manually with some of them, but the most recent ones are stuck in HDR due to the bogus metadata and no amount of toggling will bring back SDR content detection (i.e. get the driver to stop sending the bogus HDR metadata). They keep sending bogus HDR metadata that force the HDR calibration to be selected. Hence why there is no problem if you use HDR passthrough, as this is the calibration you want anyway. You might even get the correct HDR metadata when using HDR passthrough.

Also, if your screen/display doesnt change calibration automatically according to content, either on its own or using an HD Fury device, then you might not notice any problem either.

I had tried to qualify this before, but as always with HTPCs you can't make generalisations...

@Klaus1189, maybe you could put a link to this post with your note that 472.74 *might* be the last driver to use for Pascal cards for pixel shader tonemapping (unless it's confirmed it's a GTX vs RTX issue, which is unlikely) with displays/video chains that automatically detect the content to select a calibration automatically, if you want to put such a longwinded warning. I honestly don't test drivers for all use cases, it's time-consuming enough to test them for my own use :).

[Manni]

https://developer.nvidia.com/blog/nvidia-turing-architecture-in-depth/



Turing & Ampere has native HDR processing display pipeline & tone mapping, maybe that's why you see differences in GPU generations.

I am not using the GPU for HDR processing/tonemaping. madVR is doing the tonemapping with pixel shader. But for some reasons recent drivers lead this SDR content to be sent with bogus HDR metadata, at least with my GTX 1080ti.

Anyway, I'm only reporting issues so that others are aware that post 442.74 drivers can cause issues with pascal GPUs. I'm not looking for solutions, it's not the first time nVidia breaks something with their drivers :)

[glc650]

Thanks for the feedback, but are you using HDR passthrough or pixel shader tonemapping?

passhtrough

[Manni]

passhtrough

That's what I thought, and that's why you're not having any issues.

Thanks for confirming :)

[SamuriHL]

Thanks for the feedback. That's helpful, if not fully depressing. :D Man, nVidia, seriously....

[VBB]

Another hotfix driver, apparently released quietly yesterday: https://nvidia.custhelp.com/app/answers/detail/a_id/5099/kw/hotfix

[VBB]

Out of curiosity, I left everything at defaults after doing a clean install of this latest hotfix driver. Strangely enough, "optimal" seems to act like "adaptive" now. I did not notice any power fluctuations. Frames were stable and at the same ms. Can anyone confirm this?

[huhn]

i reported something like this before. they seem to changed something about it. that why i found the stuck power managament mode.

[Klaus1189]

https://www.igorslab.de/en/3dmark-in-ultra-hd-benchmarks-the-rx-6800xt-without-and-with-raytracing/

[el Filou]

Please, we have this thread now for this: https://forum.doom9.org/showthread.php?t=181881 ;)

[Klaus1189]

Sorry.
Any news about the Pascal vs. Turing or GTX vs. RTX last recommended driver?

[VBB]

I can only comment on Maxwell and HDR pass-through, but I've had no issues with the new drivers, including the latest hotfix.

[SamuriHL]

Oh joy wonder what they broke this time. Lol

Sent from my SM-G975U using Tapatalk

[Manni]

Great news for the 3xxx series, 10bits over HDMI is finally unlocked, which means that 40gb/s is enough for 4K60p 4:4:4. I had missed that.

See https://www.youtube.com/watch?v=EtaMLPo3b8o

I'm waiting to hear more about the rumoured 3080ti with same 102 die as 3090, almost the same number of cores, full bus width and 12gb of VRAM. It's expected to cost under $1,000, possible as low as $899.

Depending on the clocks, it might end up as fast or even faster than the 3090 for much less money.

[EDIT: I grabbed a chance to pre-order a Zotac 3090 Trinity at non-scalping price expected to arrive on November 10. 24Gb still has an advantage over 12Gb for me, if I can get my hands on the card this year. We shall see!].

[QBhd]

there is one case with overblown HDR just chill for now.

edit: BTW. you complained about low YT quality right? there seems to be a major issue with the current AMD driver and web browser.
try this video https://www.youtube.com/watch?v=PRUrlZFty3A it looks horrific on my system if you load the same stream into let'S mpc-be it fine.
this is my last word about this in this topic if you want to discuss this in more detail feel free to do so in the driver thread.

So what are we supposed to be looking for? I just tested this clip and it looks fine to me... I have yet to see any "major issue" with AMD and web browser

QB

[Klaus1189]

edit: BTW. you complained about low YT quality right? there seems to be a major issue with the current AMD driver and web browser.
try this video https://www.youtube.com/watch?v=PRUrlZFty3A it looks horrific on my system if you load the same stream into let'S mpc-be it fine.

Yes I have one single video which looks awful. I used Firefox first and it is the same in MPC-BE. So I think it is encoded that way. Just to remember I was referring to the background:
https://www.youtube.com/watch?v=07FYdnEawAQ&t=47

this is my last word about this in this topic if you want to discuss this in more detail feel free to do so in the driver thread.

Why so harsh? I only read your vague comment in the madVR thread and asked for more details. I thought there might be something I missed.

[Klaus1189]

https://www.youtube.com/watch?v=PRUrlZFty3A it looks horrific on my system if you load the same stream into let'S mpc-be it fine.

I just watched that video. What issue(s) do you see?

[huhn]

extremely hard blocking on chromium based webbrowser in close to black details.
even using screenshoot fixes it so does playing it externally in a media player. i have no notice this on my nvidia system else i would not even assume AMD to be related to this issue.

my last word about webbrowser artefacts in the madVR thread not your general question compatibility.

Yes I have one single video which looks awful. I used Firefox first, and it is the same in MPC-BE.

ok should be a different issue.

[Klaus1189]

What is that "different" issue? How can I reproduce it?

[huhn]

you don't seem to have it. you really just have to watch the video and pause it is not impossible to miss.

i use vivaldi 3.4.2066.86 also tested a fresh install of chrome (has to go now) and the currently installed edge i'm on 19041 20H1 amd 20.10.1

[Klaus1189]

What info is displayed when you rightclick on the videoframe on your browser and click on "Statisiken für Nerds", sorry now it is "Interessierte". The video is available as MP4 with AVC encoded video and WebM with VP9 encoded video.
Perhaps that is also a point?

[huhn]

i tested these too it one of the first things i did. the browser uses VP youtubeDL in mpc-hc defaults to h264 mpc-be defautls to h264 so i DL the stream 248 and tested it locally.

what i just tested it in film and TV app it has the same issue a bit differently. taking a screenshoot and it's gone i have to move the player windows or go fullscreen to trigger it again.

that's such a mess. mpcVR is fine too with d3d11 (that kinda new BTW.) d3d9 is forced limited for me.

i guess reinstalling the system is faster then debugging this feels bad when i aim to replace it in 1-2 weeks.

does someone know if a program can know if a screen is taken from it?

[VBB]

After a clean install of 457.09, I noticed again that "optimal" behaves just like "adaptive". I've seen no reason to change it so far. YMMV

[SamuriHL]

Neat. I'm in the middle of doing a clean install right now. I was going to check HDR real quick and make sure they didn't break the metadata again. I've got the fury inline. I'll report back shortly.

[SamuriHL]

No change from previous drivers where HDR is concerned. Bringing up the player overlay will drop you back to SDR until you're back in full screen. Metadata is working as expected.

[angmav]

Can I ask a question are we nvidia owners that stupid that we need a thread with over 2000 posts to make sure our card works properly this is ridiculous that a massive company like nvidia cant hire someone to simply test this stuff I understand us home theatre pc owners are a small market share of sales but can any amd owners tell me if they have any issues because I think I am done with nvidia seriously every new driver fixes one thing and breaks another , now we have firmware that works different for different models then why release new firmware for it ,why not develop a different branch one for RTX , one for GTX , if I am wrong please tell me I am just over it


Sent from my iPhone using Tapatalk

[huhn]

for AMD the GPU driver where just dying for like 6 month when decoding VP9 they renamed this bug like 5 times in the known issue notes before fixing it and DXVA and D3D11 processing are utterly broken for like a year now(madVR doesn't really use this).

just to give you a reverence point nvidia user are currently complaining about HDR stops working when a player bar or something like this is presented something AMD was never capable of.

this was an issue that went under the radar: https://github.com/GPUOpen-LibrariesAndSDKs/AGS_SDK/issues/33

[webbo]

No change from previous drivers where HDR is concerned. Bringing up the player overlay will drop you back to SDR until you're back in full screen. Metadata is working as expected.

So HDR basically works correctly again, but the SDR to HDR flicking when overlay is brought up. Hmm
What would be the latest driver not to resort to this behavior ?
:(

I used to use 442.74 , but I might need a newer one for certain games to properly work

[SamuriHL]

Much older drivers. I don't even remember the branch much less the specific versions at this point that don't show the sdr behavior when the overlay is shown. Seems to be an intentional change.

Sent from my SM-G975U using Tapatalk

[el Filou]

It is intentional: https://forum.doom9.org/showthread.php?p=1925280#post1925280
Judging from the way they phrased it in that KB article, I don't think they'll change that behaviour again.

[Manni]

Nope. Been running the fall update for a few weeks now with no problems. Had 2004 since it went release as well.

Sent from my SM-G975U using Tapatalk

How about 20H2? :)

[VBB]

20H2 is the fall update.

[chros]

So HDR basically works correctly again, but the SDR to HDR flicking when overlay is brought up. Hmm
...
I used to use 442.74 , but I might need a newer one for certain games to properly work
Just a short note (I'll write more later), the 442.74 doesn't change hdr metadata without restarting the player!
I went through lot of drivers (about 10 of them), including the last one and none of them is perfect.
So I went back to the good old 385.28 with the old pascal card.

[Manni]

20H2 is the fall update.

I know, I was asking if he (or anyone else) had any issue with 20H2 vs previous builds. :)

[VBB]

Ah, gotcha. Can't speak for Samuri, but I've had it installed since it was released, and I haven't found any issues compared to previous builds. Fresh install.

[SamuriHL]

No, no issues for me at all. I've been running it for a while now.

[nevcairiel]

I know, I was asking if he (or anyone else) had any issue with 20H2 vs previous builds. :)

Which is weird because you quoted a post from him already saying that the Fall update runs fine. :)

[Manni]

Which is weird because you quoted a post from him already saying that the Fall update runs fine. :)

Thanks, my mistake, I missed the first half, I thought he was referring to 2004... :o

No, no issues for me at all. I've been running it for a while now.

Thanks (again) for the confirmation :)

[SamuriHL]

And really the Fall update was not a huge update at all. Nothing structurally changed under the covers. But yea it's safe to upgrade to.

[webbo]

Just a short note (I'll write more later), the 442.74 doesn't change hdr metadata without restarting the player!
I went through lot of drivers (about 10 of them), including the last one and none of them is perfect.
So I went back to the good old 385.28 with the old pascal card.

Much older drivers. I don't even remember the branch much less the specific versions at this point that don't show the sdr behavior when the overlay is shown. Seems to be an intentional change.

Sent from my SM-G975U using Tapatalk

Ok, so for PotPlayer usage, Exclusive PotPlayer Mode would be the only choice in order to address the out-of-HDR-when-mouse-moving-GUI-displaying scenario.

It ain't that bad, all things considered.

Thanks for your inputs!

[Asmodian]

I cannot use resolutions that require DSC with a Club3D CAC-1085 adapter on my 2080 Ti with 457.09. With 456.71 it works normally.

I have also seen reports of DSC monitors not working on 3000 series cards using the same drivers.

[peacetalks]

Hello everyone, New poster here. I've been following this thread to get HDR on Kodi 17.6 Krypton with Dsplayer and MadVR working.

I have a 1050TI gtx, My current windows build is 1809, and i'm using Nvidia driver 385.28. This combination allows me to watch HDR videos within kodi 17.6 dsplayer madvr with it auto switching to HDR when the film starts and ends. I also have it set to change the refresh rate to 24hz (my tv is a native 120hz tv)

The issue i'm having is i'm noticing some banding on certain tv shows. When i watch them on my PC (RTX 2070 SUPER) I don't see the banding. This leads me to believe it's something to do with the Nvidia drivers as I don't have any banding when i watch Tv or play video games.

On windows build 1809 I also attempted to use the following drivers with the results below:

441.66 (hdr doesn't switch off when video ends and video flickers)
441.87 (hdr switches off when video ends but video flickers)
442.19 (hdr switches off but video flickers)
442.50 (hdr doesn't switch off - video flickers)
442.72 (hdr doesn't switch off - video flickers)
456.71 (hdr doesn't switch off - no flickering)

Originally I had the latest windows build, 2004 with the latest nvidia driver installed, but it wasn't switching the HDR on when watching HDR content - so i went back to 1809.

I hope i've provided enough information for someone to chime in with their experience or a possible solution. Thank you for your time and have a nice weekend folks.

Is there a version of windows that works best with a combination of nvidia drivers for Kodi 17.6 with dsplayer and madvr?

[chros]

The issue i'm having is i'm noticing some banding on certain tv shows. When i watch them on my PC (RTX 2070 SUPER) I don't see the banding. This leads me to believe it's something to do with the Nvidia drivers as I don't have any banding when i watch Tv or play video games.
What TV is it and when you say "on the PC" is it also connected to the same TV or a different monitor?
If not then I bet it's the TV :)

On windows build 1809 I also attempted to use the following drivers with the results below:

441.66 (hdr doesn't switch off when video ends and video flickers)
441.87 (hdr switches off when video ends but video flickers)
442.19 (hdr switches off but video flickers)
442.50 (hdr doesn't switch off - video flickers)
442.72 (hdr doesn't switch off - video flickers)
456.71 (hdr doesn't switch off - no flickering)

I can confirm your findings, as I mentioned here:
Just a short note (I'll write more later), the 442.74 doesn't change hdr metadata without restarting the player!
I went through lot of drivers (about 10 of them), including the last one and none of them is perfect.
So I went back to the good old 385.28 with the old pascal card.

Here is a bit more details on Win10 1809 with a 1060 6GB:
- 385.28 - 398.11:
-- almost all is good, except for multimonitor support is broken after sleep :) (newer drivers fix this so something was changed in Win10)
- 398.36 - 425.31:
-- HDR output with bogus metadata
- 430.53 - 442.74:
-- HDR output metadata is only correct when the first HDR video is launched in the same player!!! If you open another one in the same player metadata doesn't get changed! (it means you can't test/compare anything with madvr anymore)
- 442.92:
-- same as above
-- plus sometimes SDR video stuck in HDR after playing it in the same player after an HDR video (reboot fixes the issue for a short time)
- 456.71:
-- finally correct metadata again all the time
-- weird washed out colors and glitches upon UI interaction with HDR video (right click, when interface is up, etc)
-- and the above mentioned SDR video stuck in HDR straight away

So, this is where we are: this is completely unacceptable :)
Note that I mentioned "HDR ouput" and not passthrough (madvr pixelshader is used most of the time in my case).

So I went back to 385.28 and tried to "fix" the broken multimonitor support:
- this is how it should work: when playback is on TV, PC switches TV off then PC goes to sleep, then after waking up the monitor should be use automatically
- what happens instead: for whatever reason after waking up, the TV is still used as the audio device and not the AVR! And this doesn't happen if I switch off the TV without putting the PC to sleep!

So, that told me it's some timing issue. So what I did was added extra delay between switching the TV off and sleep. But due to how Oled compensation cycles work (TV doesn't get actually turned off until the comp cycle is finished), I had to add 9 minutes instead of 30 seconds :D And of course this doesn't handle the big 1 hour comp cycle :D
This is the final script that works like a charm:

cd d:\Progs\MPC-BE\
mpc-be64.exe && aiopylgtvcommand 192.168.1.78 power_off && timeout 540 && C:\Windows\psshutdown.exe -d -t 00

[peacetalks]

[QUOTE=chros;1927705]What TV is it and when you say "on the PC" is it also connected to the same TV or a different monitor?
If not then I bet it's the TV :)

It's a Vizio M65-F0, It's connecting to my receiver (Onkyo NR-777) and my PC is connected to the receiver. I've set everything up in the Nvidia control panel, as well as MADVR and Kodi as guides have suggested.

MY 2070 Super RTX is connected to a different screen (Asus Predator XB271HU) So maybe you are right and it is my TV? I tried doing a banding test (http://www.lagom.nl/lcd-test/gradient.php) on my HTPC connected to my TV and I didn't get the "Banding Bad Monitor" affect.

Also thank you for taking the time and providing all that information in your last response. I really appreciate it.

Is there another recommended build of windows 10/Nvidia driver combo that has better results than 1809/385.28?

Thanks again and have a great weekend.

[webbo]

One more question, please

Updated from 442.74 to latest driver version 457.09 without checking the "clean install" box.
I was experiencing freezes in PotPlayer (madVR) , SDR playbacks as well as HDR
Freezes, meaning, complete PC freezes, had to hard-reset the PC to be able to use it again
Did anyone else experience this or had this something to do with my "dirty" installation?

Is the clean install option always recommended?
Reverted to 442.74 - for the time being, safety measure :)

[SamuriHL]

When moving between branches I typically clean install and reset my settings. There's only a handful of things I change so going in there after a clean install doesn't take long. Make sure on older drivers to set the power option to optimal. That's one area that can cause....issues.

EDIT: Oops....that was meant to say switch the power option from optimal to adaptive. I've not slept well for the past few days for some....odd....reason. LOL

[VBB]

I always do a clean install, and then adjust the few things necessary after. If you don't game and don't have any other issues with your card, there's really only the refresh rate and color space/bit depth to potentially mess with. With the latest drivers, I find that changing the power setting from "optimal" to "adaptive" is no longer necessary. YMMV.

[SamuriHL]

yes, on the latest driver versions the Power setting can be left alone. But for older drivers, you definitely want to change that to avoid issues. As for clean installing the driver, it never hurts to do so. And in fact, we've seen MANY cases where NOT doing it causes problems with left over settings that didn't get cleaned up properly by the installer. So, I could go with the always advice.

[jkauff]

I haven't seen it mentioned here lately, but the free utility DDU will do a more thorough driver uninstall than Nvidia's clean install. Sometimes useful if you're still having driver problems after a clean install.

[webbo]

One more question, please

Updated from 442.74 to latest driver version 457.09 without checking the "clean install" box.
I was experiencing freezes in PotPlayer (madVR) , SDR playbacks as well as HDR
Freezes, meaning, complete PC freezes, had to hard-reset the PC to be able to use it again
Did anyone else experience this or had this something to do with my "dirty" installation?

Is the clean install option always recommended?
Reverted to 442.74 - for the time being, safety measure :)

Well, still having the same issue and it's getting definately annoying, because I've never had these problems for more than 2 years of madVR usage.

MadVR appears to be freezing the whole playback & PC when doing tonemapping using pixel shaders settiong (for 4K HDR playback)
When playing SDR titles, everything seems fine. No crashes

On 457.09 right now

The scenario is almost identical to http://bugs.madshi.net/view.php?id=553



I haven't seen it mentioned here lately, but the free utility DDU will do a more thorough driver uninstall than Nvidia's clean install. Sometimes useful if you're still having driver problems after a clean install.

Ok, thanks, I will surely try this one too.

[chros]

It's a Vizio M65-F0, It's connecting to my receiver (Onkyo NR-777) and my PC is connected to the receiver. I've set everything up in the Nvidia control panel, as well as MADVR and Kodi as guides have suggested.
...
MY 2070 Super RTX is connected to a different screen (Asus Predator XB271HU) So maybe you are right and it is my TV?
...
Is there another recommended build of windows 10/Nvidia driver combo that has better results than 1809/385.28?
Yes, it can easily happen that the TV is the culprit (as with LG Oleds in PC mode). If you can move the 2070S PC to the TV then you can easily try this out.
As you can see above, I don't think so (although I haven't tried newer Win10 versions).
385.28:
- is perfect with 1607 LTSB (there's no OS HDR option yet)
- "only" has the multimonitor issue with 1809, but if you don't care about this then it's fine as well

[VBB]

Interesting open issue in those new drivers:

Windows 10 Issues - When setting the refresh rate higher than 100Hz, the color format switches from RGB to ycbcr422. [3053990]

[SamuriHL]

Oh joy. I wonder what else they broke. LOL I'll check the HDR stuff later.

[Grimsdyke]

I encountered this problem a few weeks ago when I tried to setup a nice little htpc with an Intel iGPU but also already at 48 Hz and 50 Hz !! Back then I thought that the hardware/driver had problems with CRU.

[huhn]

extremely hard blocking on chromium based webbrowser in close to black details.
even using screenshoot fixes it so does playing it externally in a media player. i have no notice this on my nvidia system else i would not even assume AMD to be related to this issue.

i now have a confirmation with a different user with the same issue.

[Furgiuele]

Hi.
Can someone tell me which is the best Nvidia driver for madVR with hdr passtrough sending metadata to the display?
I tried 442.74: it works fine on hdr but there is stuttering on 23.970 fps. Then I tried all the newer - perfect on 23.970 fps - but there is a bug after hdr playback stops...
None works fine at all?
What about AMD RX5700?
It works better? How are drivers?
Thanks in advance.

[VBB]

For pass-through, most of us have no issues with the latest Nvidia drivers. I'm on 457.30 myself.

[Furgiuele]

For pass-through, most of us have no issues with the latest Nvidia drivers. I'm on 457.30 myself.

Hi. The issue occurs only because I need to set hdr in passtrough - send metadata to the display.
After I stop hdr playback, the gpu continue sending hdr signal.
There is a known remedy?

[chros]

I reported this 2 times already noone replied. @VBB,can you test this? Thanks

[SamuriHL]

I use JRiver as my player and when I exit the player, it returns to SDR mode on all recent drivers.

[chros]

:) Yes this is how it works, but the question is what happens when you don't close the player but fire up an SDR video after an HDR10 one??? :)

[VBB]

It doesn't do that here, but I recall it used to with older drivers. Maybe six months ago or so. Playback stopped and the display would be stuck in HDR mode until you click somewhere with the mouse. Never bothered me enough to roll back. But again, I haven't seen this happen in a long time.

Note: I do have my player set to close after each playback, of course. Will test later with player not set to close.

[SamuriHL]

For me, in JRiver, when I hit stop, it shuts down HDR mode. I also have madvr set up to restore my resolution which probably has something to do with it.

[chros]

:) So the test case: hdr file is playing, you can hit pause or just let it play, then open an sdr video in the same window.

[SamuriHL]

Yes, stays in HDR. "Doctor, it hurts when I hit my hand with a hammer." "Yea, dumbass, don't do that." :D

[chros]

Thanks for the confirmation with rtx card, there is the bug in recent drivers, it started to happen in 442.92 :)

[funderburk]

Well, I'm always using the latest AMD and never had a problem so far.

[SamuriHL]

So given nVidia's extensive track record on fixing such things, we can expect the 3xxx super refresh cards to be out around the same time. LOL

[VBB]

I can confirm your bug now, chros :)

Set player to do nothing after playback stops -> play HDR file -> play SDR file -> TV will switch modes, but SDR content is extremely dark.

[chros]

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
And when the fix comes they start to FAQ up something else :) And amd drivers are crap, right? :)

[oldpainlesskodi]

Sorry,but for the price of 3090, you will get a much better payoff by upgrading the panel/display....

Just my 2 cents....

[SamuriHL]

The state of drivers is not what we'd call "awesome", no. I mean I'm happy enough with the latest drivers because playback on them is rock solid. HDR with metadata triggers correctly, audio driver finally works correctly, refresh rate is pretty damn stable out of the box.....that's a win in my book given how bad things CAN be with these things.

[chros]

Yes, it always can be worse :)

[ryrynz]

Sorry,but for the price of 3090, you will get a much better payoff by upgrading the panel/display.


Unless you already have a best in class display, which if you can splash out on a 3090 I'd think you'd already have.
Plus some of these people would have their own companies and just write it off as an expense.
If you're buying one of these chances are the least of your worries is disposable income.

[Asmodian]

I finally got a 3090 and it is crazy fast for madVR, as expected. I posted in the madVR thread too but I can do 4K -> 8K -> 4K with NGU very high in 26ms at stock clocks, ~1900 MHz. Not that I want to but that is fast!

Using 457.30. HDR seems to work properly with these drivers, I haven't noticed anything else wrong either. Native HDMI 2.1 is great, that adapter was painful.

[oldpainlesskodi]

@ ryrynz - true.

[Manni]

I finally got a 3090 and it is crazy fast for madVR, as expected. I posted in the madVR thread too but I can do 4K -> 8K -> 4K with NGU very high in 26ms at stock clocks, ~1900 MHz. Not that I want to but that is fast!

Using 457.30. HDR seems to work properly with these drivers, I haven't noticed anything else wrong either. Native HDMI 2.1 is great, that adapter was painful.

I also got a 3090 and not only is it fast, but I did some power use comparison during Bluray and UHD Bluray playback using the same settings as with my 1080ti, and as expected it uses around 90W less for bluray (290W to 200W at the wall playing Dunkirk upscaled to UHD) and 50W less for UHD bluray (280W to 230W at the wall playing Pacific Rim chapter 2 using pixel shader tonemapping) to get the same quality. It also gives me about 10ms rendering headroom that I can use as I wish (or not). Obviously not the same story at full GPU load... No undervoltage yet, so power use expected to get even better for little performance trade-off.

I didn’t buy the 3090 for madVR use (a 3080 would be more than enough and more appropriate for HTPC use), but it’s nice to have that headroom and be ready to use tensor cores when/if they become exploited by madVR at some point.

All the below is with Win10 Pro x64 20H2. It's still my old i7 rig (details in my sig) as I haven't built my Ryzen rig yet (waiting for the 5950X to arrive).

Re problems (coming from a 1080ti with 442.74), I had, as expected, to reduce the number of frames read ahead to avoid stutter.

It seems to send HDR metadata fine in passthrough (457.30), but if you go to passthrough and go back to Pixel shader, the picture is corrupted and you need to change resolution (or reset GPU or reboot) to resolve. I never had that with my 1080ti, but I was using 442.74 so not sure if it’s the recent driver or the 3090.

I tried to go back to the earliest driver usable for the 3090/80 (456.38) and the last Studio driver (456.71) and it does it too, so I went back to 457.30.

One dropped/repeated frame per hour with the default drivers (no CRU), which is nice. CRU doesn’t seem to make a difference so I’m not using it for now.

As known, you drop out of HDR when right clicking to get the menu during HDR playback in MPC-BE, but you go back to HDR when the menu goes away.

As long as I don’t use passthrough and go back to pixel shader, I don’t have a problem switching between HDR and SDR. I get back to SDR when I return to desktop, which is what I want.

The 3xxx series supports 10bits over HDMI which is a nice addition, but unfortunately for JVC users it doesn’t help with the chroma up sampling issue, so 8bits is still recommended.

There are levels mismatch between SDR and HDR depending on the bit depth used, so you need to test both.

I used RGB Full in driver, full in madVR and full in the JVC and with RGB 8bits at 23p that seemed to work fine for SDR and HDR but I’m going to have to recalibrate as black are crushed a bit in HDR.

These are just first impressions after one evening checking the basics. I’ll post some impressions and basic benchmarks in the other thread when/if I find the time, but this is all I have currently re driver issues.

For JVC users with 3xxx I recommend for now to use 457.30 with RGB 8bits, full/full/full and pixel shader tonemapping. I was using build 113 for these tests. I’ll post back here if this recommendation changes.

For 1080ti (Pascal) users, I still recommend to use 442.74. I was using full/limited/limited but I was only using madVR. I plan to do other things with this 3090 so I need correct levels for desktop work and games.

[videoh]

Thank you for your reports on the 3090, Asmodian and Manni. Wish I could get my hands on one!

[ryrynz]

Wish I could get my hands on one!

So say we all.

[mrmojo666]

Hi guys,

just in case i repost here:
yestrerday i got a rx5700 xt but seems i lost totally deinterlacing capabilities, at the start i thought it was Madvr but even with vmr9 it's the same ..... anyone have similar experience with that card ?
I noticed that before with rx460 i had more option under driver video custom setting, now there is only brightness.
Already tried with DDU


driver 20.9.2
software deconding with software deint is working
any other tip is appreciated
thank you

[SamuriHL]

I finally got a 3090 and it is crazy fast for madVR, as expected. I posted in the madVR thread too but I can do 4K -> 8K -> 4K with NGU very high in 26ms at stock clocks, ~1900 MHz. Not that I want to but that is fast!

Using 457.30. HDR seems to work properly with these drivers, I haven't noticed anything else wrong either. Native HDMI 2.1 is great, that adapter was painful.Holy God that's insane. That'll be fun for you to play around with!

Sent from my SM-G975U using Tapatalk

[aufkrawall]

No idea if there was a workaround in ffmpeg or if it was fixed in AMD driver, but D3D11VA VP9 now works in mpv on Navi. Playback seems to be fine at low power consumption, afaict.

[huhn]

AMD didn't fix it it still doesn't work with lavfilter 74.1 the workaround to ignore the flag that says it can't do it in bitstreaming is still needed.

tested on 2020.10.1

[aufkrawall]

It now also works with regular ffmpeg + ffplay build by gyan.dev though.

[huhn]

and why shouldn't they add the same workaround?

[Klaus1189]

I finally got a 3090 and it is crazy fast for madVR, as expected. I posted in the madVR thread too but I can do 4K -> 8K -> 4K with NGU very high in 26ms at stock clocks, ~1900 MHz. Not that I want to but that is fast!

Using 457.30. HDR seems to work properly with these drivers, I haven't noticed anything else wrong either. Native HDMI 2.1 is great, that adapter was painful.

:confused: -> https://www.techpowerup.com/gpu-specs/geforce-rtx-3090.c3622

[huhn]

that's been the case since pascal.
they clock far higher than the specs say.

1900 is "low" for the card it's not even trying.

[Klaus1189]

If I compare different cards, i mean different AIB 3080s or 3090s. How do I get the „best“ binned? Or at least better than average?

[huhn]

you don't.

without OC they end up at pretty much the same boost clocks.
a good binned GPU is only useful for OC and without OC testing the card you will not know.

[Klaus1189]

So just get one I can and if that card works, no defect or anything, it will be good? Just a thought: Alternate prices for 6800XT were ridiculus +200 € over MSRP

[huhn]

the 6800 is a paper release just ignore it for the next weeks the real price fight start when demand is delivered. currently nvidia has no reason to lower prices because AMD has to stock.
they a very compative and unlike nvidia perform good at 1440 and show "issues" with UHD. maybe a bandwidth issue so time to see if we see a bandwidth issue or a Vram limitation first.

get a card with a good cooler and good is everything else is out of your hand.

[Klaus1189]

good is everything else is out of your hand.

Sorry, what do you mean by that? :)


I could have gotten a RX 6800XT but for that price - no thank you.

[huhn]

if you get a defect card you get one if it has coil whine like crazy happens.if you want Samsung Vram and not micron for application X it's random and out of your hand.

[el Filou]

Would it be possible to add a note to the first post that hardware deinterlacing is either not working at all (apparently with DXVA2) or if it works (apparently with D3D11VA) it gives very bad quality i.e. not motion adaptive, on Radeon RX 5000 series?
Sources:
https://forum.doom9.org/showthread.php?p=1928601#post1928601 and https://forum.doom9.org/showthread.php?p=1928515#post1928515

I know deinterlacing isn't used much, but for some people who need it can be an important information.

[huhn]

they are both broken in the complete same way.

want DXVA2 "not" to combine just use DXVA2 scaling for everything and you will get the same low end quality as with the video app because it is doing the same.

i'm testing and reporting on this for like 13 month now.

[Klaus1189]

Of course ;) Which version is first affected?

I got another question to you all if you open taskmanager and look for vram, do you also have stated dedicated VRam of your GPU but also sytem ram that is used for GPU if it is needed? Is that a feature of any kind? I never set it up that way.

I know integrated GPUs in CPUs use system RAM, but I do only have CPU without integrated GPU and a dedicated GPU.

[huhn]

all driver version with no exception.

[el Filou]

I got another question to you all if you open taskmanager and look for vram, do you also have stated dedicated VRam of your GPU but also sytem ram that is used for GPU if it is needed? Is that a feature of any kind? I never set it up that way. Yes I have that on all my machines. Windows 10 allows up to half of system memory to be shared with a discrete GPU.

[Klaus1189]

Does that help in certain circumstances?

[aufkrawall]

and why shouldn't they add the same workaround?
I'd rather assume that it was added in upstream ffmpeg (though I didn't check your claim with upstream LAV Filters), but I can't find a corresponding commit.

The broken Navi deinterlacing is a bummer, though my impression with Polaris was that its quality was crap vs. Intel anyway. Good thing mpv has automatic copyback for yadif by default when enabling deinterlacing.

[chros]

Thanks for the confirmation with rtx card, there is the bug in recent drivers, it started to happen in 442.92 :)
I've sent madshi a pm on avs to let his nvidia contact kmow about this, we will see what happens...

[aufkrawall]

I've tested with LAV Filters 0.74.1 and Adrenalin 20.11.2 driver: D3D11VA VP9 decoding is definitely fixed, it's now reported via "Video Codec 0" load in Task Manager instead of encode.

[el Filou]

Does that help in certain circumstances?I would imagine it's the modern equivalent of AGP Texturing in the old days: it can allow running a game/app that has absolute minimal memory needs bigger than your VRAM, but you would incur a big performance hit compared to VRAM-only.
I may try a GPU queue of 24 when I'm back on my HTPC this evening just to check how much that has an impact. :)
IIRC, people have tried running 4K madVR on a GeForce 1030 and encountered that issue: it would work but would drop frames due to "overflowing" into system RAM.

Edit: well, render queue of 24 didn't trigger it, but decode queue of 128 with native hardware decode did. It's really weird, total used memory was around 4,5 GB but instead of using all VRAM and a bit of system RAM it used only 1.3 GB VRAM and 3.2 GB system RAM. When looking at GPU-Z it caused massive traffic over the PCIe bus but all usage was very bursty and it dropped frames like crazy. As huhn said below, never ever count on that and always make sure you don't max out dedicated VRAM.

[huhn]

I'd rather assume that it was added in upstream ffmpeg (though I didn't check your claim with upstream LAV Filters), but I can't find a corresponding commit.

The broken Navi deinterlacing is a bummer, though my impression with Polaris was that its quality was crap vs. Intel anyway. Good thing mpv has automatic copyback for yadif by default when enabling deinterlacing.

they fixed it in 20.11.2. i tested 20.10.1
AMD deint was the best in my opinion(one of the reasons i usually got an AMD card as a HTPC GPU) beware polaris(if not all AMD cards) had a similar issue for many month where a really low quality deint was used not as bad as this but they fixed it one day. they broke it in the first crimson driver if you want to test that.

yadif is sadly not frame adaptive that's why it not hard to beat.

the nightly 0.74.1.59 was the first with the work around if you want to test it with an older driver or find the commit.

@ at the share memory stuff. showing shared memory in the taskmanager doesn't mean it new this was pretty much always possible and should pretty much always be avoided in a running program

[aufkrawall]

GPU deinterlacing btw. still works on Navi with VAAPI and I'd say it looks exactly like Polaris D3D11VA/VAAPI, which I find ugly due to aliased look vs. yadif.

Well, but screw deinterlacing. Hopefully AV1 works the same as VP9 with RDNA2. Tests sound positive, but they only try browsers.

[huhn]

you mean it "works" like this: https://abload.de/img/amddeint2mji2.jpg

or not at all?

[aufkrawall]

Drop me a cartoon sample, please.

[huhn]

you can force deint on everything for testing even an image.

i can still make you sample later.

[chros]

Hopefully AV1 works the same as VP9 with RDNA2. Tests sound positive, but they only try browsers.
Coreteks showed a slide in his review that only stated av1 8k@30 decoding (and no av1 encoding). Can this be true?

[aufkrawall]

While it's "only" 8k 30fps, it's still a rather convenient surprise that they've managed to support a new codec at the same time as their competitors. Intel & Nvidia don't support AV1 encoding either and only Intel support VP9 encoding.

[huhn]

sample: https://filehorst.de/d/dqmHnyet

[el Filou]

Isn't that sample a 3:2 telecine?

Anyway you made me want to test my old HD 7870 deinterlacing under D3D11 with true 576i and I confirm that the quality is awful even on such an old card, so it looks that both:
- DXVA2 deinterlace is broken on Navi (but still good on older cards even with modern drivers)
- they didn't even bother implementing good quality deinterlacing/scaling under D3D11 VP for any cards

I also noticed when doing comparisons, that the NVIDIA chroma issue is also present under D3D11 VP which is a shame, and that its deinterlacing quality isn't better than with DXVA2. It is markedly better on AMD cards when it works.
NVIDIA also shows a lot of artifacts on interlaced SD (at least 576i), and there are more of them when copyback decoding is used which makes no sense to me but that's how it is, still some of them can be seen with native but not as much.
Anyway SDTV is on its way out even on my cable provider who makes the least effort but it's sad they never got that totally right like AMD did.

[huhn]

yes it is telecine and there is an alternative to deal with this file.

nvidia needs a couple of frames before it start working so make sure that it get's them.

[el Filou]

Yes I make sure to let it play for a bit and then I play frame by frame instead of skipping directly to frame number, but it doesn't change anything, it's still lower quality than AMD's (but at least it's not buggy).
I only tested true video 576i from TV as I hardly ever watch any NTSC, I only have one DVD with 3:2.

[huhn]

can you make me a screen plz and name the hardware.
the screen i made is literal the best i can get out of amd under any situation and i'm not aware of a situation where nvidia falls apart.

[el Filou]

Here's a zip file with all the PNGs: https://filehorst.de/d/dfxxbqnl
It's from a vertically rolling credits and horizontally rolling news ticker (this one also showing bad chroma and artifacts).
I displayed at 100% (just stretched horizontally for 16:9 SD)

Here's a comparison of a small part where differences are obvious: https://abload.de/img/comparisono4ky9.png

Hardware is HD 7870 and 1050 Ti. I've not included NVIDIA D3D11 screens as it's identical quality to DXVA2.
I wouldn't say NVIDIA is really falling apart, it's just there are random artifacts in the image that look like errors, small one pixel high contrasted horizontal lines, and there's a different amount of them depending on if copyback or native decode is used. I don't think it comes from madVR itself because this doesn't happen on AMD with identical settings but it is weird.
Obviously it's much more visible on SD than HD.
Best possible quality is AMD DXVA2 with madVR, but if it's broken on Navi I don't have much hope they will fix it seeing how slow they are at fixing even more important stuff.

[Calvi]

Try the 1050 with CUVID for comparison,
Select also adaptive/hw and hq processing.

[huhn]

HQ processing is not supposed to work on windows 10 with CUVID AFAIK.

and AFAIK HG processing is the "IVTC" option in the driver.

[SamuriHL]

Oh God what have they broken now??

I mean, oh, GOOD, a new driver! LOL

[VBB]

Something new to play with tonight. Samuri, you go first!

[SamuriHL]

Joy. LOL Yea, I'll check it after work. They better not screw this up. I got (some) LOTR movies to watch!

[kostik]

The new driver works great with RTX 3080 . Watched 4k HDR movie with all settings maxed on madVR and works great (on 4k resolution RGB 10bit 120Hz) . This 3080 RTX is a beast. Max GPU Temp reached to 61C after 1 hour of watching a movie

The only 'issue' I see is the same as previous driver. When you bring the seek toolbar up, the colors become strange (but no flashes as before), once the seek toolbar is down, the colors are back as they should. Also there are flashes when you open madVR settings and when you change a setting in madVR while playing HDR but they are fast

[Manni]

The new driver works great with RTX 3080 . Watched 4k HDR movie with all settings maxed on madVR and works great (on 4k resolution RGB 10bit 120Hz) . This 3080 RTX is a beast. Max GPU Temp reached to 61C after 1 hour of watching a movie

Apparently you might not be getting RGB at 120hz, there is a known issue in the release notes stating that any content above 100hz switches automatically to YCC 4:2:2.

I haven’t verified as I have no need for anything above 60hz, but worth checking in your case.

[kostik]

Apparently you might not be getting RGB at 120hz, there is a known issue in the release notes stating that any content above 100hz switches automatically to YCC 4:2:2.

I haven’t verified as I have no need for anything above 60hz, but worth checking in your case.

When playing HDR in madVR ?

I have 65CX and when I check in the hidden HDMI diagnostic menu , I definitely see that I am on RGB 10BIT and 120HZ . Also madVR report that I am on RGB 10bit NVHDR .

I also know for sure that I am on 120Hz because the scrolling on the browser is super smooth .

I know this issue you talk about. I had this when I had GTX 1080 and was using the the DP->hdmi 2.1 adapter from Club3D , it was always defaulting to ycbcr 4:2:0 even when choosing 10bit RGB but I had a workaround to fix this (enable or disable AMD FreeSync or Game Response and then change to 10bit RGB ). But now, there are 0 issues of this sort (with RTX 3080) . Maybe its still an issue on 10XX and 20XX series but works perfectly on RTX 30XX

I use 120Hz because I love the super fluid and smooth browsing and also for gaming of course . I just leave it on 120Hz when playing movies using madVR because I am too lazy and also see no benefit changing the display to 60 or 24Hz.

For movies, I also don't see any improvement or change in motion using 120Hz, its same as 60hz

[SamuriHL]

I can't possibly stress enough how jealous I am of that 3080 on that panel. DROOL.

[Crimson Wolf]

When you bring the seek toolbar up, the colors become strange (but no flashes as before), once the seek toolbar is down, the colors are back as they should.

I don't have HDR, but I do have a 10-bit panel, so I encountered this while using the seek bar which causes to go into 8-bit mode when using it. I know the "enable automatic fullscreen exclusive mode" isn't true exclusive mode anymore in the latest windows 10 version, but it switches into the mode extremely quickly and if you use the "show seek bar" from the exclusive mode, madvr doesn't switch from 10-bit to 8-bit while using the seekbar. Can you test if HDR mode is fine if you try this method? Just curious. The seek bar in exclusive mode is different.

[kostik]

I don't have HDR, but I do have a 10-bit panel, so I encountered this while using the seek bar which causes to go into 8-bit mode when using it. I know the "enable automatic fullscreen exclusive mode" isn't true exclusive mode anymore in the latest windows 10 version, but it switches into the mode extremely quickly and if you use the "show seek bar" from the exclusive mode, madvr doesn't switch from 10-bit to 8-bit while using the seekbar. Can you test if HDR mode is fine if you try this method? Just curious. The seek bar in exclusive mode is different.

Enable automatic fullscreen exclusive mode is disabled on my madVR setup and 'show seek bar' is ticked under rendering->exclusive mode .

What option to turn on\off to test what you ask for ?

BTW I use the latest madVR 114 ver.

[VBB]

@ Crimson Wolf - It does work like you described in both SDR and HDR modes. With proper FS exclusive mode, which you get when checking "disable fullscreen optimizations" in the properties of an executable, the panel will not switch into windowed 8-bit mode. The disadvantage is that you don't get the player's seek bar with chapters, etc. Either way works for playback, though.

In my opinion, it's best to leave the compatibility settings alone, and uncheck "automatic fullscreen exclusive mode" in madVR. FS exclusive doesn't work anymore like it used to, and has no real advantages over windowed FS.

[chros]

I just leave it on 120Hz when playing movies using madVR because I am too lazy and also see no benefit changing the display to 60 or 24Hz.

For movies, I also don't see any improvement or change in motion using 120Hz, its same as 60hz
Yes, 120 Hz is almost good for everything except for 25/50 fps content, that saves a lot of refresh rate switching.
What interval does madvr report for frame drops with 23p at 119/120Hz without SmoothMotion?

[VBB]

Latest Nvidia drivers are good. No new issues to report at this time.

[Magik Mark]

Using DSPlayer, the driver doesn't switch back to sdr after playing a HDR video.
Do you have any work around?

[kostik]

Yes, 120 Hz is almost good for everything except for 25/50 fps content, that saves a lot of refresh rate switching.
What interval does madvr report for frame drops with 23p at 119/120Hz without SmoothMotion?

1 frame repeat every 41 seconds and it grows. This is what you meant ?
If not, where do I see or how do I calculate the interval ?

[VBB]

Not owning a C9/CX myself, I would assume you want to still use refresh rate switching at 120Hz. I'd use 2160p100, 2160p119, 2160p120. madVR should then switch to 100 for 25/50 fps content, 119 for 23/29/59 fps content, and 120 for 24/30 fps content. That should cover all bases.

[VBB]

Using DSPlayer, the driver doesn't switch back to sdr after playing a HDR video.
Do you have any work around?

Mark, that's one of the ongoing issues. The workaround would be to have the player exit/close after each playback.

[chros]

1 frame repeat every 41 seconds and it grows. This is what you meant ?
If not, where do I see or how do I calculate the interval ?
Yes, that is what I meant, thanks. That's bad, how much is it e. g. after 3 minutes of playback? And as VBB says, how much is it at 119Hz?

[Asmodian]

With a 3090 and a CX I don't have a 119 Hz option, nothing above 60 Hz besides 100 and 120 Hz, both in the PC section.

Smooth motion basically required for >60Hz. :p

[VBB]

Oh, wow. That's a big oversight on LG's part to not include that in the EDID. Shouldn't come as a surprise, I guess, when all people care about these days is gaming ;)

[chros]

CRU to the rescue? :D

[Manni]

CRU to the rescue? :D

CRU doesn’t seem to work with the latest drivers. At least not in my super brief tests. Will test more after I build my Ryzen rig this week-end...

[mpchelp10]

MPC-HC version 1.9.8
madVR version v0.92.17

madVR is set to "passthrough HDR to display" with "send HDR metadata to display" checked

Monitor: Lenovo Legion Y27q-20
GPU: RTX 2070 Super
Connected via display port

Windows "Use HDR" and "Stream HDR Video" settings are both on.

When I try to play a HDR video with MPC-HC + madVR, the colors are extremely dark. Watching HDR videos in YouTube on Chrome works fine. Is this a driver related issue or did I configure something wrong?

[el Filou]

CRU doesn’t seem to work with the latest drivers. At least not in my super brief tests.I've something in the release notes like "admin rights now required for EDID override", maybe this is related, they changed something in the driver maybe? I've never used CRU so it's just an idea.Try the 1050 with CUVID for comparison,
Select also adaptive/hw and hq processing.So:
- Using CUVID just for decode and letting madVR handle deinterlacing produces the same artifacts as DXVA2 copyback
- Enabling CUVID deinterlacing in LAV produces no artifacts at all, this is the best mode but unfortunately this means I can't control deint anymore with madVR hotkeys and have to open LAV settings to switch between film/video which is a pain.
So it looks like the artifacts come from something in madVR, as they don't show up using other renderers or with CUVID deint. Maybe madshi isn't using the correct DXVA deint mode. I will try to do more tests with DXVA Checker.
In both scenarios, the deinterlacing quality itself (apart from the artifacts) isn't any better than with DXVA (no 'HQ processing' anymore in current LAV).
I've also tested the other software deint options in LAV, YADIF is horrible and has even more artifacts than madVR DXVA, probably because it's not motion adaptive. Weston is really good, I'd say better quality than NVIDIA hw deint but still not as good as AMD's. Unfortunately uses a lot of CPU on my old system, and same inconvenience as CUVID which is not controllable from madVR.
I hope when madshi implements his planned motion adaptive deint for the Envy, that he asks us to test it. :D
I could also re-encode all my SD interlaced stuff to 50p on my desktop using AMD's deinterlacing, SDTV won't last eternally, but it takes time I'd rather use for something else.

[huhn]

madshi is aware of issues with DXVA deint he simply doesn't know why they exist:
http://bugs.madshi.net/view.php?id=652

maybe forcing YV12 instead of NV12 helps or so.
but i'm not even close to what you call artifacts...

[Manni]

I've something in the release notes like "admin rights now required for EDID override", maybe this is related, they changed something in the driver maybe? I've never used CRU so it's just an idea.

Thanks, I saw that but I'm an admin so shouldn't be the reason.

I'll do more tests when my rig is up.

[VBB]

Windows "Use HDR" and "Stream HDR Video" settings are both on.

Turn those off and let madVR do the switching. Let us know if that fixes it.

[mpchelp10]

Turn those off and let madVR do the switching. Let us know if that fixes it.
I'm still getting really dark colors. Windows HDR is off and hdr in madVR has been set to "let madVR decide".
Here are my NVIDIA control panel settings & madVR info (Ctr+J)
https://i.imgur.com/2WIpVsz.png

HDR playback using my laptop connected to my monitor does work, so I'm 100% sure this is a software/driver issue...

Something interesting I noticed:
When I press ALT+Enter to make MPC-HC fullscreen, there is a brief "hang"/lag before it actually enters fullscreen. During this brief delay, I can see the actual HDR colors/brightness, but once entering fullscreen it goes back to being super dark.

[VBB]

I'm still getting really dark colors.

One thing I would change still is to set madVR to 10-bit. Your monitor seems to handle that well, so you might as well use it throughout the video chain. Also, you should enable smooth motion in madVR, since you're outputting at 165Hz. This will remove any judder.

As for why HDR is not working properly, that's a tough one. Are you on Windows 10, and if so, which version? Judging by your screenshot, LAV is set to "none" for the decoder. You could try switching that to D3D11 native (automatic) to see if that makes a difference.

Lastly, what's your Nvidia driver version? Try the latest, if you haven't already, to see if that makes a difference.

[SamuriHL]

Speaking of drivers I forgot to post that the latest Nvidia driver has proper metadata. Basically no change from the previous driver in any behavior.

Sent from my SM-G975U using Tapatalk

[mpchelp10]

One thing I would change still is to set madVR to 10-bit. Your monitor seems to handle that well, so you might as well use it throughout the video chain. Also, you should enable smooth motion in madVR, since you're outputting at 165Hz. This will remove any judder.[/spoiler]
"the native display bitdepth is:" is set to "10 bit (or higher)" under Devices->Properties

[QUOTE=VBB;1929890]As for why HDR is not working properly, that's a tough one. Are you on Windows 10, and if so, which version? Judging by your screenshot, LAV is set to "none" for the decoder. You could try switching that to D3D11 native (automatic) to see if that makes a difference.
Windows 10 Pro 19042
MPC-HC>Options>Internal Filters>Video Decoder
It was originally set to D3D11. Changing to DXVA2 (copy-back) or DXVA2 (native) don't fix anything.

Lastly, what's your Nvidia driver version? Try the latest, if you haven't already, to see if that makes a difference.
457.30
My laptop is running a much older version of NVIDIA drivers...

One more thing I noticed: When I play the HDR file with MPC-HC, it's not just MPC-HC that ends up with darker colors - my entire monitor seems to go into some darker display mode...

[Calvi]

- Enabling CUVID deinterlacing in LAV produces no artifacts at all, this is the best mode but unfortunately this means I can't control deint anymore with madVR hotkeys and have to open LAV settings to switch between film/video which is a pain.

I just leave it on Video and it seems to always switch correctly itself. i.e. if I play film it does not deinterlace but if DTV it switches on automatically (I assume decided within nvidia hw).

I find CUVID with MadVR also to have the least artifacts.

[SweetLow]

That's a big oversight on LG's part to not include that in the EDID.
Even C9 version has this modes in EDID. Why do you think that CX does not have?

[VBB]

Are you saying the C9 has 119 as an option? That's great then, and even more of a head-scratcher as to why the CX doesn't.

[kostik]

Are you saying the C9 has 119 as an option? That's great then, and even more of a head-scratcher as to why the CX doesn't.

What is this 119 option you talk about? 119Hz?

CX has 119.880Hz option but you can select it on the Advanced Graphics options in Windows Settings on the Dev build (MS added refresh rate selection in display settings few builds ago )

119.880/23.976= 5 (exactly 5)

For movies I guess it is better to select 119.880 over 120Hz

https://imgur.com/BSbO8ES.png

[VBB]

If you go back a page, Asmodian told us that he doesn't have 119Hz as an option for refresh rate, and that he has to use smooth motion at 120Hz because of this. 119Hz is what you want for proper 23.976 fps playback, yes. Thanks for your screenshot. That's great news then.

[kostik]

If you go back a page, Asmodian told us that he doesn't have 119Hz as an option for refresh rate, and that he has to use smooth motion at 120Hz because of this. 119Hz is what you want for proper 23.976 fps playback, yes. Thanks for your screenshot. That's great news then.

Too bad this option is not present in NVIDIA control panel .

[VBB]

But it's usable regardless, no? Does madVR switch to it?

[kostik]

But it's usable regardless, no? Does madVR switch to it?

Yes. 119Hz is listed in madVR with Native resolutions only is ticked.

When 120Hz selected, madVR OSD shows Display : 119.99999HZ and decomposition: 120HZ

When 119.880Hz selected madVR OSD shows Display: ~119.8794 and decomposition : 119.758

[chros]

Nice, thanks, what's the interval for frame drops that madvr reports on the OSD after about 2 minutes?

[Asmodian]

If you go back a page, Asmodian told us that he doesn't have 119Hz as an option for refresh rate, and that he has to use smooth motion at 120Hz because of this. 119Hz is what you want for proper 23.976 fps playback, yes. Thanks for your screenshot. That's great news then.

Too bad this option is not present in NVIDIA control panel .

Wow, the option is present in Advanced display settings on my CX as well. I wonder why it doesn't show up in the Nvidia control panel. :(

edit;
At 119 I see 119.87880 Hz in madVR, settling down to a estimate of 1 frame repeat every ~2 hours.

[huhn]

check under SD, HD, UHD.
1080p120 and such are usually placed under PC because they are not broadcast standard TV use. with HDMI 2.1 that's different and the EDID could be different for this too placing them into the default TV timings.

[Asmodian]

There are only two sections for resolutions in the Nvidia control panel and nothing above 1920x1080 under Ultra HD, HD, SD goes above 60 Hz. It seems like that section is limited to 2.0b resolutions, except it allows 10 bit too so that isn't it.

Just weird I guess. :p

[huhn]

that's a driver bug then.

i don't have a 2.1 card yet to test it my self sorry.
you could check the EDID and where it is listed to know where it should be listed but that will not tell us why it is not listed in the driver so i don't see much worth in that.

[SweetLow]

Are you saying the C9 has 119 as an option? That's great then, and even more of a head-scratcher as to why the CX doesn't.
I think CX has too.
P.S. It would be nice if anybody post dumps of CX EDIDs (and I suppose it has options for EDID with and without HDMI 2.1 on).

[Asmodian]

Yes, the CX has it too. I was fooled by only looking in the Nvidia control panel.

[SweetLow]

Can you dump CX EDIDs (moninfo or madvr raw edid data)? For my curiosity - i will compare with C9. And I can post decoded info (if someone interested in).

[Asmodian]

Sure, LG_CX_EDID.bin (http://www.mediafire.com/file/04htbyg096e2jut/LG_CX_EDID.bin/file)

[SweetLow]

Thanks, but the second part of EDID (high 128 bytes) zeroed :(

[kostik]

Can you dump CX EDIDs (moninfo or madvr raw edid data)? For my curiosity - i will compare with C9. And I can post decoded info (if someone interested in). @SweetLow


Here is mine:
http://www.mediafire.com/file/0rvwhwdgiof8tuo/OLED65CX.bin/file

This is the EDID of my CX. I just copied from madVR window =\


00 FF FF FF FF FF FF 00 1E 6D C8 C0 01 01 01 01
01 1E 01 03 80 A0 5A 78 0A EE 91 A3 54 4C 99 26
0F 50 54 A1 08 00 31 40 45 40 61 40 71 40 81 80
D1 C0 01 01 01 01 08 E8 00 30 F2 70 5A 80 B0 58
8A 00 40 84 63 00 00 1E 66 21 50 B0 51 00 1B 30
40 70 36 00 40 84 63 00 00 1E 00 00 00 FD 00 18
78 1E FF 77 00 0A 20 20 20 20 20 20 00 00 00 FC
00 4C 47 20 54 56 20 53 53 43 52 0A 20 20 01 AA

02 03 64 F1 5E 61 60 76 75 66 65 DB DA 10 1F 04
13 05 14 03 02 12 20 21 22 15 01 5D 5E 5F 62 63
64 3F 40 2C 09 57 07 15 07 50 57 07 01 67 04 03
6E 03 0C 00 10 00 B8 3C 24 00 80 01 02 03 04 6A
D8 5D C4 01 78 80 53 22 28 78 E2 00 CF E3 05 C0
00 E3 06 0D 01 E2 0F FF EB 01 46 D0 00 2A 1A 03
51 8B 67 73 6F C2 00 A0 A0 A0 55 50 30 20 35 00
40 84 63 00 00 1E 00 00 00 00 00 00 00 00 00 40

[Asmodian]

Here is my CX from madVR, my second block is pretty different.
00 FF FF FF FF FF FF 00 1E 6D C8 C0 01 01 01 01
01 1E 01 03 80 A0 5A 78 0A EE 91 A3 54 4C 99 26
0F 50 54 A1 08 00 31 40 45 40 61 40 71 40 81 80
D1 C0 01 01 01 01 08 E8 00 30 F2 70 5A 80 B0 58
8A 00 40 84 63 00 00 1E 66 21 50 B0 51 00 1B 30
40 70 36 00 40 84 63 00 00 1E 00 00 00 FD 00 18
78 1E FF 77 00 0A 20 20 20 20 20 20 00 00 00 FC
00 4C 47 20 54 56 20 53 53 43 52 0A 20 20 01 AA

02 03 5B F1 5E 61 60 76 75 66 65 DB DA 10 1F 04
13 05 14 03 02 12 20 21 22 15 01 5D 5E 5F 62 63
64 3F 40 23 09 57 07 6E 03 0C 00 40 00 B8 3C 24
00 80 01 02 03 04 6A D8 5D C4 01 78 80 53 22 28
78 E2 00 CF E3 05 C0 00 E3 06 0D 01 E2 0F FF EB
01 46 D0 00 2A 1A 03 51 8B 67 73 6F C2 00 A0 A0
A0 55 50 30 20 35 00 40 84 63 00 00 1E 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5B

Edit:
I also re-exported from Moninfo and updated the file I linked above, not sure why the second part was zeroed.

[SweetLow]

Here is mine:

Thanks.
This is decoded info (in parts where moninfo does not decode correctly):


Extension ID: 2 (CE)
Version: 3
Capabilities: F1h

Tag: 2 (Video Data Block)
*See "Supported CE Standard Video Modes"
Hex Dump: 616076756665DBDA101F0413051403021220212215015D5E5F6263643F40

Tag: 1 (Audio Data Block)
Hex Dump: 095707150750570701670403

Tag: 3 (Vendor-Specific Data Block)
Vendor OUI: 000C03 (HDMI 1.x / HDMI LICENSING, LLC)
Hex Dump: 1000B83C24008001020304

Tag: 3 (Vendor-Specific Data Block)
Vendor OUI: C45DD8 (HDMI 2.x / HDMI Forum)
Version: 1
Maximum TMDS Character Rate: 600 MHz
3D OSD Disparity Indication: No
3D Dual View signaling: No
3D Independent View signaling: No
Less than or equal to 340 Mcsc scrambling support: No
Color content bits per component indication: No
Initiating an SCDC Read Request: No
SCDC functionality: Yes
10-bits/component Deep Color 4:2:0 Pixel Encoding: Yes
12-bits/component Deep Color 4:2:0 Pixel Encoding: Yes
16-bits/component Deep Color 4:2:0 Pixel Encoding: No
Max Fixed Rate Link (FRL): 5 (3 and 6 Gbps per lane on 3 lanes, 6, 8 and 10 Gbps on 4 lanes)
FAPA in blanking after first active video line: No
Auto Low-Latency Mode (ALLM): Yes
Fast as Possible V-active (FVA): No
Negative Mvrr values: No
Media rates below VRRmin (CinemaVRR): No
Mdelta: Yes
VRRmin: 40
VRRmax: 120
Hex Dump: 01788053222878

Tag: 7 (Use Extended Tag)
Extended Tag: 00h (Video Capability Data Block)
Hex Dump: CF

Tag: 7 (Use Extended Tag)
Extended Tag: 05h (Colorimetry Data Block)
xvYCC601: No
xvYCC709: No
sYCC601: No
opYCC601(Adobe): No
opRGB(Adobe): No
BT2020cYCC: No
BT2020YCC: Yes
BT2020RGB: Yes
DCI-P3: No
Metadata Profile: 0
Hex Dump: C000

Tag: 7 (Use Extended Tag)
Extended Tag: 06h (HDR Static Metadata Data Block)
Traditional gamma - SDR Luminance Range: Yes
Traditional gamma - HDR Luminance Range: No
SMPTE ST 2084: Yes
Hybrid Log-Gamma (HLG): Yes
Static Metadata Type 1: Yes
Hex Dump: 0D01

Tag: 7 (Use Extended Tag)
Extended Tag: 0Fh (YCbCr 4:2:0 Capability Map Data Block)
*See "Supported CE Standard Video Modes"
Hex Dump: FF

Tag: 7 (Use Extended Tag)
Extended Tag: 01h (Vendor-Specific Video Data Block)
Vendor OUI: 00D046 (DOLBY LABORATORIES, INC.)
Hex Dump: 2A1A03518B6773

Supported CE Standard Video Modes:
61h: 3840x2160p; 59.94Hz/60Hz; 16:9; *YCbCr 4:2:0 Supported
60h: 3840x2160p; 50Hz; 16:9; *YCbCr 4:2:0 Supported
76h: 3840x2160p; 119.88/120Hz; 16:9; *YCbCr 4:2:0 Supported
75h: 3840x2160p; 100Hz; 16:9; *YCbCr 4:2:0 Supported
66h: 4096x2160p; 59.94Hz/60Hz; 256:135; *YCbCr 4:2:0 Supported
65h: 4096x2160p; 50Hz; 256:135; *YCbCr 4:2:0 Supported
DBh: 4096x2160p; 119.88/120Hz; 256:135; *YCbCr 4:2:0 Supported
DAh: 4096x2160p; 100Hz; 256:135; *YCbCr 4:2:0 Supported
10h: 1920x1080p; 59.94Hz/60Hz; 16:9
1Fh: 1920x1080p; 50Hz; 16:9
04h: 1280x720p; 59.94Hz/60Hz; 16:9
13h: 1280x720p; 50Hz; 16:9
05h: 1920x1080i; 59.94Hz/60Hz; 16:9
14h: 1920x1080i; 50Hz; 16:9
03h: 720x480p; 59.94Hz/60Hz; 16:9
02h: 720x480p; 59.94Hz/60Hz; 4:3
12h: 720x576p; 50Hz; 16:9
20h: 1920x1080p; 23.98Hz/24Hz; 16:9
21h: 1920x1080p; 25Hz; 16:9
22h: 1920x1080p; 29.97Hz/30Hz; 16:9
15h: 720(1440)x576i; 50Hz; 4:3
01h: 640x480p; 59.94Hz/60Hz; 4:3
5Dh: 3840x2160p; 23.98Hz/24Hz; 16:9
5Eh: 3840x2160p; 25Hz; 16:9
5Fh: 3840x2160p; 29.97Hz/30Hz; 16:9
62h: 4096x2160p; 23.98Hz/24Hz; 256:135
63h: 4096x2160p; 25Hz; 256:135
64h: 4096x2160p; 29.97Hz/30Hz; 256:135
3Fh: 1920x1080p; 119.88/120Hz; 16:9
40h: 1920x1080p; 100Hz; 16:9


Max Fixed Rate Link (FRL): 5 (40Gbit/s) (48Gbit/s in C9), no DSC, all HDMI 2.1 modes present. Nothing new, i can say :)

my second block is pretty different.

Thanks. Your and kostik's EDIDs are different in audio blocks only. Video parts are equal.

[mikahawkins1]

I am surprised that I haven't encountered any driver problems so far.

[el Filou]

Added Background Application Max Frame Rate controlThis is nice, may install this one just to try this.

[kostik]

This is nice, may install this one just to try this.

The more interesting feature is Color Accuracy Mode:

https://imgur.com/Ou8mAMB.png

[VBB]

This has been fixed: When setting the refresh rate higher than 100Hz, the color format switches from RGB to
ycbcr422

This as well (wasn't awere of it): [MPC-HC]: The video player crashes when playing 1088 pixel-width videos

Seems to me like the new Color Accuracy Mode is best left at the default Reference.

[chros]

What about the SDR video is stuck in HDR issue?

[VBB]

Just close the damn player! ;)

All kidding aside, I doubt this will get fixed, but at least there is a workaround.

[chros]

And through out the baby with the bath water... :D

[VBB]

Seems to me like the new Color Accuracy Mode is best left at the default Reference.

Quoting myself here, because Reference is actually not the default. Accuracy is, so I guess we'll have to wait and see what's best here. I forced Reference anyway.

[JaylumX]

Only just realised that with the 460.79 drivers Nvidia fixed the annoying switching when playing HDR content. Now it is seamless.

[VBB]

Care to give some more detail? You mean this issue?

What about the SDR video is stuck in HDR issue?

[chros]

Care to give some more detail? You mean this issue?
So for the 4th time (https://forum.doom9.org/showthread.php?p=1928383#post1928383) :D

[VBB]

So for the 4th time (https://forum.doom9.org/showthread.php?p=1928383#post1928383) :D

Oh, this wasn't directed at you, sorry. I know the issue, but it wasn't clear what the poster above me (JaylumX) meant.

[chros]

That's why I was confused since you quoted me :)

[JaylumX]

Oh, this wasn't directed at you, sorry. I know the issue, but it wasn't clear what the poster above me (JaylumX) meant.

What I meant was that when I used MPC-BE to play HDR content, there would be a display change (1 second black screen) to activate HDR mode, again to go into full screen, then if I change an option in MadVR another 1 second black screen, when I exit fullscreen and finally when I exit the video. This only occurs with NV HDR and not OS HDR (As a temporary fix to limit the amount of 1 second black screen I set MPC-BE to open videos in fullscreen).

It never used to happen with NV HDR until Nvidia posted a fix for MadVR's HDR activation that it broke with a previous driver update.

Now with 460.79 the display changes once and that is it till I exit the video with no 1 second black screen just like it was before Nvidia's driver changes affected MadVR.....nice and simple.

[SamuriHL]

Latest driver looks good to me. Metadata's correct. No changed behavior from the last couple.

[IngramAU]

Just close the damn player! ;)

All kidding aside, I doubt this will get fixed, but at least there is a workaround.

Just tried this with Media Portal playing HDR tv show. While playing I hit alt+f4 shut it down back to desktop and... TV still reports HDR is on. So I guess this isn't a fix.

Back to using MPC-HC.

I don't understand this issue, a few weeks ago I never had this problem until I updated Windows to H20 whatever it is and also updated Media Portal.

After alt+f4 to desktop if I open up display settings my screen gets washed out, a quick toggle of HDR on/off puts things back to normal.

[Andy o]

Anyone with Nvidia getting audio dropouts? I recently just upgraded to a 3070, and both with this new and previous driver, I'm getting dropouts bitstreaming audio, most prominently with TrueHD Dolby Atmos, on CLSID's MPC-HC 64-bit 1.9.8 with both internal LAV 0.74.1.75 and external nightly 0.74.1.92. Rest of my hardware is in my sig. LAV external tried at default settings, except ticking the bitstreaming checkboxes, and switching to DXVA2 (to avoid presentation glitches, but dropouts don't improve when switching video decoders anyway).

A bit more info, I was using a GTX 1650 Super previously, without issues. eARC into the LX503. Also I'm running 119.88 Hz 12-bit into the C9, but I also tried switching to 8-bit, like it was with the 1650 and there's still dropouts. I've tried the CableMatters 48Gbps (not certified) and now I'm using the Zeskit 3m 48Gbps certified cable, with the same results.

Edit: Intel i7-4770, Gigabyte GA-Z87MX-D3H, RTX 3070, Win 10 64

[SamuriHL]

Is this in MKV's? Or directly playing discs? Because MKV ATMOS issues are well documented and is a ripping problem.

[VBB]

@Andy o - Can't say I've ever had audio dropouts. Not with MKVs, not with Atmos or any other format. Is the audio renderer set to internal? Do you have exclusive/bitstream ticked?

One weird issue I've now encountered twice very recently is that out of the blue channels will get reassigned. Voices will suddenly come out of the rear speakers, for example. At first, I thought it was mixed like that. I was watching an episode of Westworld at the time. Then last night it happened with The Desolation of Smaug. Pausing and resuming made the channels go back to normal.

[Andy o]

I'm also seeing it in the m2ts of the same content, and in other content as well. I was getting very subtle pops in DD+ content also. I do have the renderer set to internal, and to bitstream/exclusive. You just reminded me about it so I also just tested with not using the internal renderer, only directly to the Nvidia device, with the same results. It's been a bit of a hassle to test though, a couple of times I think I had it solved (like at first for some reason it was giving me dropouts almost in sync with the presentation glitches and switching to DXVA2 seemed to get rid of both, but the dropouts came back later).

Now I've disconnected the HTC Vive Cosmos from the DisplayPort and it seems OK, but it doesn't make sense that it would be it cause IIRC I was getting dropouts before I even installed it as well.

But in any case I'm glad to hear it's not widespread and I'm in the process of upgrading the whole rig anyway, just waitin for those damn 5900x to be in stock again.

[clsid]

Change the Power management mode to "Adaptive" in NVIDIA settings.

That helps solve video rendering glitches, but sometimes also issues with audio dropouts.

[Andy o]

I don't have "adaptive" as an option, just "normal" and "prefer maximum performance", it was already set to "normal".

[clsid]

Does anyone know is which driver version they replaced Optimal/Adaptive choices with Normal choice?

[Manni]

Does anyone know is which driver version they replaced Optimal/Adaptive choices with Normal choice?

It might be more complex than that. I still have optimal as a choice with the latest in a 3090.

[Asmodian]

Weird. I have only Normal/Prefer maximum performance with a 3090 and 460.79. I think it was the previous version that changed it.

[VBB]

I haven't even noticed that change in the latest driver, because it's been fine to leave it at the default for a while now. That default used to be "optimal", and I guess it's now "normal".

[Manni]

Weird. I have only Normal/Prefer maximum performance with a 3090 and 460.79. I think it was the previous version that changed it.

My apologies, I didn’t test that one if it’s such a recent change. Looks like I’m a couple versions behind, or didn’t check that option recently enough.

[SamuriHL]

I'm with VBB, since the past I don't know 5 or so drivers I've not changed that setting, either. I didn't even go look. Leaving it set to what is it now, "normal"?, should be fine. In theory.

[Asmodian]

I hope that is the case. I certainly wouldn't want to use prefer maximum performance all the time. Normal does seem to be working well for me.

[Andy o]

I'm experimenting with this setting, but it's still super annoying to test. I forced "normal" in mpc-hc.exe and it seemed to work... for a while. I also tried with max performance and it also seemed to work, but it was consuming around 20W extra at the wall which I'd like to avoid if possible.

This whole thing reminds me a long long time ago in the HTPC infancy some ATI drivers were causing popups and it was because of the clocks jumping up and down. When DXVA was engaged it was supposed to fix the clocks to a low-ish setting, but it wasn't doing it, so it had to be done manually by editing some obscure text file.

[VBB]

Thanks GTPVHD. This time around they listed this as an open issue:

[HDR]: With HDR enabled, black levels are incorrect. [200682795]

A lot of people, mostly gamers, have been reporting this, although I have not encountered it myself. I think this only applies to those who use the Windows HDR switch.

[VBB]

GeForce Hotfix Driver Version 460.97

https://nvidia.custhelp.com/app/answers/detail/a_id/5145

Fixed: With HDR enabled, black levels are incorrect. [200682795]

[SamuriHL]

Oh for the love of.....

[VBB]

Don't know about you, but I get all excited when I see the word "hotfix" (or "firmware", "beta", even plain old "update"). I faint at "major new version" :D

[SamuriHL]

God no. Hotfix means they haven't done all the testing and signing. Consider this "developer got drunk in the afternoon and threw this out to fix the mistakes he made last week."

[VBB]

I'm cool with that!

[garb]

Hello all.

Long time lurker and long time madVR user.
Ever since upgrading to the latest Nvidia driver (460.79 at the time), I've been having HDR issues.
Specs:
GTX 1070
i7-6700k
16GB DDR4
Windows 10-64 Pro 1903 Build
TV:
Samsung NU7100. 4k display.
Software:
MPC-BE + LAV Filters + madVR + ReClock

Windows HDR setting is set to off. madVR set to passthrough HDR to display. Also checked "set HDR metadata to the display".

Whenever I playback an HDR source, the screen goes black for a second and comes back with much lower brightness. The media displayed also has washed out colors. When I go to fullscreen, the colors are no longer washed out and the media being played is displayed correctly. However, when I hover over the seek bar, the screen goes black for a second and then I'm back to the washed out colors in fullscreen. When I no longer hover over the seek bar, it goes black again for a second and the colors are back to normal.

Anyone with similar experiences or fixes?
I thought the latest driver (460.79 at the time) fixed all the prior issues associated with HDR and madVR, but in my experience it hasn't. Really tempted to rollback drivers again.

[SamuriHL]

Garb that's the new normal behavior for the past I don't know half a dozen or more drivers now. It's not a bug. Appears to be intentional on nvidia's part. Everything is fine if you're fullscreen and don't touch it. Otherwise it drops back to sdr temporarily.

Sent from my SM-G975U using Tapatalk

[VBB]

And the workaround for that behavior is to use full-screen exclusive mode by checking that option in madVR and also checking "disable fullscreen optimizations" in the media player executable properties (right-click on file or shortcut -> properties -> compatibility). This is not really recommended, though, because you lose the GUI and seek bar, and FSE can cause other issues in Windows 10.

[QBhd]

I love FSE... but I also don't want a GUI or a seek bar :) I still use the skin for PotPlayer that Cruncher did sooo many years ago :)

http://qbstorrents.erebus.feralhosting.com/Doom9/Cruncher.Skin.jpg

QB

[garb]

Thanks for the replies people!

It's a real shame that it is so finnicky with HDR. Really ruins the whole experience. I've got a LG B6 that has been sleeping for almost a year now because of this HDR mess, and I'm not willing to sacrifice any burn-in possibility while fiddling around with the optimum settings.

I'm at a point in a life where Plug N' Play seems to be my calling.

The Nvidia Shield Pro looks very tempting. Granted it's definitely inferior when upscaling, but waiting for driver fixes (and then break something all over again) is just getting tiresome.

Thanks again everyone.

[angmav]

Hi there I can confirm new hot fix driver 460.97 using latest windows 20h2 seems to work fine except if you are using 3d fix manager to install 3d drivers if you have 3d enabled in Nvidia control panel hdr won’t kick when using Madvr Mpc be
I never noticed before if it exhibited the same behaviour
At first I thought latest driver was not working


Sent from my iPhone using Tapatalk

[brandon78]

Hello.

I just built my first HTPC primarily to use MadVR for DTM. I am running a GTX 1660 Ti. Which firmware should I be using? I reviewed the OPs but am not sure what to use. Thank you and sorry for my ignorance!!


Sent from my iPhone using Tapatalk

[VBB]

The latest hotfix driver 460.97 will work just fine for most use cases: https://nvidia.custhelp.com/app/answers/detail/a_id/5145/~/geforce-hotfix-driver-version-460.97

[brandon78]

The latest hotfix driver 460.97 will work just fine for most use cases: https://nvidia.custhelp.com/app/answers/detail/a_id/5145/~/geforce-hotfix-driver-version-460.97


Thank you!


Sent from my iPhone using Tapatalk

[webbo]

Hello mates & everyone
Does the new hotfix 460.97 - also fix the annoying within-Windows (desktop) flicker of the screen?
Or did my display went rogue on me?

Anyone else experience these while on 460.89 ?
Thank you

[Klaus1189]

Merry Christmas everyone :)

I encountered today a black screen/flicker ??? with my new RTX30 card with installed 460.89 :eek:


I installed 460.97 and look if it happens again. Never had this on a Nvidia card, but I must admit, it has been a while ... 4 years since I have owned one.

[Klaus1189]

just happened again, yeah. Nvidia ....

[VBB]

@both of you guys: Is this when watching a video or playing a game? HDR or SDR? No flickering here with any driver version.

And to everyone: It would be really, really helpful if you could put ALL your gear in your sig...

MERRY XMAS and HAPPY HOLIDAYS!

[Klaus1189]

Desktop usage, watching video in browser or playing video in windowed MPC-BE, doesn‘t matter which Renderer - EVR, MPC VR or madVR

[Aleksoid1978]

Using Nvidia 1650 + 460.89 + MPC VR + HDR passthrough - all good. MPC VR do on/off HDR mode in system.

[webbo]

@both of you guys: Is this when watching a video or playing a game? HDR or SDR? No flickering here with any driver version.

And to everyone: It would be really, really helpful if you could put ALL your gear in your sig...

MERRY XMAS and HAPPY HOLIDAYS!

Flickering while on using the desktop / browsing / just randomly. Actually, when watching any videos on the HDTV (2nd output form GPU), nothing like is happening.

[clsid]

Desktop flickering is a known driver bug. Just look at nvidia forum.

[Klaus1189]

Using Nvidia 1650 + 460.89 + MPC VR + HDR passthrough - all good. MPC VR do on/off HDR mode in system.

Thanks for reply. It only happens randomly and only after many hours of pc running. It is like a black screen but only for very short time. One can call it flickering, just like webbo described it.

Today I haven't had a flicker. We will see.

[quietvoid]

I've installed 460.89 and it totally broke my playback. After a couple seconds, it starts repeating/dropping frames and it's unwatchable.
Back to 441 for me. On a 970, madVR and MPC-BE.

It also made the player take much longer to close, and sometimes it just doesn't close at all and stays in HDR.

[SamuriHL]

You should try the hotfix. It fixes a lot of things.

[Klaus1189]

Yesterday no flicker, but it just flickered 3 times in 15 minutes, so I DDUed and installed latest HF 460.97 new. We'll see.

[SamuriHL]

My advice was for quietvoid but maybe it'll help you, too. I really wish nvidia could get it's s*** together on these drivers and cards.

Sent from my SM-G975U using Tapatalk

[Klaus1189]

Can I help Nvidia with this issue, I mean can I open an issue and deliver them a log file created by the driver or else? I mean Nvidia seems to be more serious about their stuff.
I created some stuff on AMD site and I got ignored and still isn't fixed months later. Although minor stuff but also more important ones.

Funny thing, I can buy whatever I like, I get crap all the time. I got another RTX30 card and it showed the same issues (short blackscreen/flicker and the playback issues I mentioned on MPC-BE thread), so the card I still have is not a defective one, it will be a driver issue. But gaming is really, really nice with that one, I must admit that :D

[SamuriHL]

Don't make me "respond" to that, Klaus! :P I've been trying to get my hands on a 3080 since they came out. I stopped looking a couple weeks ago and am going to try to get myself a 3080 ti for my b-day in February. As for the driver issues, who knows how to help them help you. Definitely open an issue with them if you can.

[quietvoid]

The 460.97 hotfix does fix the issue I had, however now it completely changes when HDR is enabled :(
It's going to be harder to compare since it's now necessary to go into fullscreen, otherwise there's no HDR.

[SamuriHL]

Oh great! Thus proving my point about hotfix updates. For crying out loud nVidia.....

[webbo]

Desktop flickering is a known driver bug. Just look at nvidia forum.

Well, looking at nVidia's forum didn't fix this, only reverting back to 442.74 helped & fixed the flickering

Tbh, i'm so sick with nVidia. I would like to ask about Radeon alternative? I'm talking about video playback, especially 4K with HDR situations. Does the madVR & Radeon fare better or... ?
Thanks for your input on this

[Manni]

The 460.97 hotfix does fix the issue I had, however now it completely changes when HDR is enabled :(
It's going to be harder to compare since it's now necessary to go into fullscreen, otherwise there's no HDR.

The hotfix broke HDR here (nvAPI with madVR). I had to revert to the latest studio 460.89.

I left all the default settings (including "normal" for power) and with 1 frame in advance it seems to be working fine, though I only have limited testing time at the moment. I was just trying to put my HTPC back in action on the Ryzen, and it's mostly there.

[justcheeze]

Anyone with Nvidia getting audio dropouts? I recently just upgraded to a 3070, and both with this new and previous driver, I'm getting dropouts bitstreaming audio, most prominently with TrueHD Dolby Atmos, on CLSID's MPC-HC 64-bit 1.9.8 with both internal LAV 0.74.1.75 and external nightly 0.74.1.92. Rest of my hardware is in my sig. LAV external tried at default settings, except ticking the bitstreaming checkboxes, and switching to DXVA2 (to avoid presentation glitches, but dropouts don't improve when switching video decoders anyway).

A bit more info, I was using a GTX 1650 Super previously, without issues. eARC into the LX503. Also I'm running 119.88 Hz 12-bit into the C9, but I also tried switching to 8-bit, like it was with the 1650 and there's still dropouts. I've tried the CableMatters 48Gbps (not certified) and now I'm using the Zeskit 3m 48Gbps certified cable, with the same results.

Hi, did you ever got this issue fixed?

Coincidentally, I've been having sporadic audio drop outs too particularly with Atmos and sometimes even DTS HD tracks. The drops are very brief, like half a sec tops and it happens very randomly. There is no way to accurately reproduce the problem because seeking back to the frame where audio drops doesn't repeat the issue.

It's weird that lossy tracks (DD, DD+, DTS) are fine and even PCM has no issue.

[*MidnightWatcher*]

Have you tried the official stable 0.74.1 LAV filters?

[Klaus1189]

When using RX 5000 cards with EVR (CP) or MPC VR (without D3D11 checked!) then the blacks are elevated (0-255 vs 16-235). This has always been the case. I want to summarize it and need to know how exactly I could write it. Is this problem D3D9 in the the drivers or what is the common background?

I will test my old RX480 8GB card in this case today, but I already know that the deinterlacer works just fine on the RX480, it is motion adaptive. Good testvideo:
https://drive.google.com/file/d/12wO8NJbIrfa2MD4yVaA38RrBBdziCda8/view
Watch for flickering like https://de.wikipedia.org/wiki/Zeilensprungverfahren#/media/Datei:Indian_Head_interlace.gif on the logo:
https://wst.tv/wp-content/uploads/2018/06/D88.com_.jpg
On RX 5000 cards the deinterlacer is not working good and is not motion adaptive.

[justcheeze]

Have you tried the official stable 0.74.1 LAV filters?

Yes. I tried from 0.74.1 latest stable version and EVERY nightly release all the way up to 0.74.1-92. Also have tried with every Nvidia driver since 446.14. Have also tried with MPC-BE, MPC-HC and PotPlayer. All exhibits the audio drop issue.

It's frustrating because I can't pin point the issue to what is causing it.

[huhn]

the level bug changed multiply times over the year.
it was broken for d3d11 too depending on other factors like P010 SDR.
the deintlacer is not really working at all. the combination of deint and DXVA scaling is just an insult there is no way they even have a QA that ever look at this even once.
for me currently everything that uses AMD video processing(browser EVR-CP and such) is utterly broken.
the preset are undefeatable there is currently no option to disable the magic video stuff: https://www.amd.com/en/support/kb/faq/dh2-006
under custom there is simply nothing. the reason i posted about the video blocking issue that is not shown in screenshoots.

a logo is BTW. a very bad test to test a deinterlacer.

[Klaus1189]

I don't have another one :(
But nevertheless I can see if the video is being deinterlaced and if the logo flickers I know the deinterlacer is not motion adaptive.
Do you or anybody else have a good testvideo for motion adaptive deinterlacer?

[huhn]

i posted a telecine video sample here before but sure:
https://www.hdpvrcapture.com/wordpress/?page_id=97
first ones i could found EVR none CP deals with them not totally bad.

i can still reproduce this insult of image quality with https://abload.de/img/amddeint2mji2.jpg with mpcVR.

[Klaus1189]

i posted a telecine video sample here before

The thread grew a lot bigger than I thought and can now not find anything fast anymore :(


Can you send me a link to the video source file of the last screenshot, so I can test with my RX480, my RX5700XT and my new RTX30 card? If needed also per PM? Would like to test that and see the differences. :)

I took always the *.M2TS and *.TS file, right? MP4 container is strange for interlaced video, isn't it? I mean MediaInfo posts strange things about it.

[huhn]

https://forum.doom9.org/showpost.php?p=1928782&postcount=2167

the container shouldn't matter i'm not aware of modern codecs that needs the container information to identify if the stream is interlaced bff or tff first it is legal to change this in the middle of the video so i guess it has to be part of the video stream.

[Aleksoid1978]

i posted a telecine video sample here before but sure:
https://www.hdpvrcapture.com/wordpress/?page_id=97
first ones i could found EVR none CP deals with them not totally bad.

i can still reproduce this insult of image quality with https://abload.de/img/amddeint2mji2.jpg with mpcVR.

SD to UHD :)
Disable DXVA2/D3D11 video processor formats and other checkbox.

P.S. Upload this file.

[huhn]

you did nothing wrong it's AMD fault.
the file is linked there.

if i disable the DXVA scaler it just stops deinterlacing so i get the same results as madVR.

[Klaus1189]

@huhn:
Which file do you think is best from your linked testclips (https://www.hdpvrcapture.com/wordpress/?page_id=97)to test frame adaptive feature? To be sure also which container, so we don't talk past each other.

I tried with my Nvidia RTX30 card and use its frame adaptive deinterlacing and then if I use YADIF in LAV, which is a very good deinterlacer, but it is not frame adaptive. I can see it flickering with YADIF, but not with the one of Nvidia.

[huhn]

just use m2ts (used on BD which use interlacing quite a bit). try the Black Ops clip.it has static objects like the UI with moving parts around it these are good to test frame adaptive deint the moving parts should "flciker" a bit but the UI should be static.

BTW. i just got frame adaptive deint working with madVR no clue how...

[Aleksoid1978]

you did nothing wrong it's AMD fault.
the file is linked there.

if i disable the DXVA scaler it just stops deinterlacing so i get the same results as madVR.

You can disable just "Use for resizing" - MPC VR will be use shaders for resize but DXVA2/D3D11 VP for convert & deinterlace.

https://i.imgur.com/gzlgeP1.png

[huhn]

AMD disagrees:
https://abload.de/img/deintpujab.png

[Aleksoid1978]

AMD disagrees:
https://abload.de/img/deintpujab.png

Ha-ha :)

[Klaus1189]

On a RX 5700 XT? How? I never achieved that.

I tested that clip, yes same flickering of the ammunition counter when using YADIF in LAV, just like the logo. But I still keep this snooker clip nevertheless, I can clearly see if the deinterlacer works motion adaptive ;)

I tested the RX480 and frame adaptive is indeed working, despite when using Repeat function in MPC-BE then during the second, third, ... playback deinterlacing is off. But with the RTX30 card it is applied as it should. Would be a driver issue, i think.

During I write that, I think I just test it again with MPC-BE set it up to play 5 instead of default 1 in options. I am gonna see. What it does then. So much hassle to do that much testing with different GPUs - Nvidia vs AMD.

[huhn]

just use control+left arrow key you should find it.

do that with yadif too so you will very fast understand why i don't like it.

[Klaus1189]

I don't understand. CTRL + left is 1 frame backwards. What should I find? Which one do you not like? Yadif or Framedaptive deinterlacing of GPU. Sorry :o

[huhn]

did i say left try right.
if you can'r find it well what should i say.

[Klaus1189]

What file should I try? I saw that on my Nvidia RTX30 deinterlacer got hiccup and wasn't applied during frame steps, but during normal playback it is fine. What do you expect me to see?

[huhn]

nvidia works after a couple of fields the first ones are suppar.
yadif doesn't like the sample.mkv weston three field does better by having generally more artefacts but not as destructive.

after that you can try madVR film mode and than madVR video mode.
if you try it with mpcVR d3d11 all VP modes on except scaling you should even be able to find my screen.

yet again please don't blame the renderer it just has more options like d3d11 VP.

[Klaus1189]

Sorry had to shop groceries, now I am back.


yet again please don't blame the renderer

I never blamed the renderer, it was just your post which led Aleksoid1978 to react:
i can still reproduce this insult of image quality with https://abload.de/img/amddeint2mji2.jpg with mpcVR.

SD to UHD :)
Disable DXVA2/D3D11 video processor formats and other checkbox.
P.S. Upload this file.

I know you didn't blamed MPC-VR but it would help to be more precise ;)

just use control+left arrow key you should find it.

do that with yadif too so you will very fast understand why i don't like it.

the left vs. right thing:
did i say left try right.

if you can'r find it well what should i say.

I just don't know what exactly I had to do, no need to be so harsh to me.
I have three different GPUs here, several video renderer and several testvideos which show different issues of some cards. Bear with me if I can not follow so quickly. But not an issue. Just be more patient with me and more precise with your posts :)

suppar

What does that mean? :)

yadif doesn't like the sample.mkv weston three field does better by having generally more artefacts but not as destructive.

after that you can try madVR film mode and than madVR video mode.
if you try it with mpcVR d3d11 all VP modes on except scaling you should even be able to find my screen.

I will do some tests. What do you mean with:
you should even be able to find my screen.

Reproduce the screenshot with sample.mkv (https://filehorst.de/d/dqmHnyet)?

[*MidnightWatcher*]

Yes. I tried from 0.74.1 latest stable version and EVERY nightly release all the way up to 0.74.1-92. Also have tried with every Nvidia driver since 446.14. Have also tried with MPC-BE, MPC-HC and PotPlayer. All exhibits the audio drop issue.

It's frustrating because I can't pin point the issue to what is causing it.
Hmmm. Have you tried another HDMI cable and input? (Sorry if already answered).

[justcheeze]

Hmmm. Have you tried another HDMI cable and input? (Sorry if already answered).

Yup absolutely.

In fact, I've tried different GPUs now too. I was on the 1070Ti before and now I'm on a 3080. Same results. So I'm sure it's not the GPU then. I don't think it's got to do with Windows 10 either because it seems like you guys aren't having problems?

It's also not the file of any particular movie, because it happens on all movies.

:confused::confused::confused:

[VBB]

@justcheeze - In the LAV Splitter, what is the "Stream Analysis Duration" set to? I used to have issues with the HD audio formats, pausing and resuming mainly, but recently clsid changed that value from 1000 to 2100 (built-in LAV in MPC-HC), and I haven't had any problems since. This might not be related to what you're experiencing, but it's worth a shot.

Disclaimer: Nev says that this change shouldn't affect my dropouts at all, but I am now able to pause a file with TrueHD/Atmos or DTS-HD for a long time, and the audio will pick right up when I resume. Before, only video would play, audio would not come back.

[huhn]

I never blamed the renderer, it was just your post which led Aleksoid1978 to react:
not sure why that would be needed in a GPU driver thread where it was over and over clarified that the AMD deint is not doing what it should be doing.

I just don't know what exactly I had to do, no need to be so harsh to me.
I have three different GPUs here, several video renderer and several testvideos which show different issues of some cards. Bear with me if I can not follow so quickly. But not an issue. Just be more patient with me and more precise with your posts :)

has nothing to do with you we should get the same result if we don't there could be quite a lot of possibilities to why.
i don't know what to say is it even worth investigating?

What does that mean? :)
subpar


I will do some tests. What do you mean with:


Reproduce the screenshot with sample.mkv (https://filehorst.de/d/dqmHnyet)?
the problem is "should be". if you don't get the same results all you can do is make a screen to show the difference.

[Klaus1189]

BTW. i just got frame adaptive deint working with madVR no clue how...

Do you already know how? Is it still working?


RDNA2 - will it have similar issues like RDNA or is that dependent on something else? Like the old polaris RX480 is working fine, but my RX5700XT has the two major problems - elevated black in EVR and D3D9 in MPC-VR but I repeat it is AMDs fault not from MPC-VR devs. And the hardware deinterlacer, it never worked for me, not frame adaptive and poor quality.

I tried to set EVR to 16-235 but it is still not the same like the the elevated black levels. But it has to do with 0-255 vs. 16-235 but I think on another level, if you know what I mean.

I watched the sample.mkv and saw the artefacts of YADIF. I saw it best at the black drawed lines of the characters. Very bad. Nvidias deinterlacer is fine for my eyes. Not perfect, progressive is perfect, but I am happy with it.

[huhn]

this should be just a software problem. RDNA2 could be perfectly fine.

i got it to work in madVR by chance it sometimes work when i pause and restart the video with the blackops sample. the UI stops flickering.
the nvidia deint has a bug too for many many years now. it's just very small compared to this but it was one of 2 major reason why i got the 5700 XT instead of the 2070.

the thing that really get's me from AMD this how they treat this issue with a "that doesn't sound important". the GPU driver option are just dead and elevate black except for cinema classic that crushes black levels. of cause everything else is messed up... yeah there are work arounds like mpcVR and madVR you can't really play everything with these renderer under every condition.

i mean just go into the radeon driver -> settings -> display -> custom color -> color temperature control -> disabled.
so with custom colors disabled AMD do nothing and it is fine.
and with custom colors enabled and color temperature control disabled AMD change the white point when an option is disabled?
did anyone at AMD every tried that option and said "works as intended" disable means actively changing the whitepoint...

[Klaus1189]

What is the little bug in Nvidia deinterlacer?
What were the reasons for you to get the RX 5700 XT over the 2070?

[justcheeze]

@justcheeze - In the LAV Splitter, what is the "Stream Analysis Duration" set to? I used to have issues with the HD audio formats, pausing and resuming mainly, but recently clsid changed that value from 1000 to 2100 (built-in LAV in MPC-HC), and I haven't had any problems since. This might not be related to what you're experiencing, but it's worth a shot.

Disclaimer: Nev says that this change shouldn't affect my dropouts at all, but I am now able to pause a file with TrueHD/Atmos or DTS-HD for a long time, and the audio will pick right up when I resume. Before, only video would play, audio would not come back.

Hmmm interesting, okay I'll check it out. I believe it's still at the default 1000.

Thanks for giving me a lead.

[huhn]

nvidia generally misplaces chroma when DXVA processing is used i have not checked d3d11 for this.

the 5700 XT is the better card in terms of price/performance.

[DMU]

Perhaps I missed something, but why are you not satisfied with IVTC in madVR?
Pic (https://drive.google.com/file/d/13vBcnvcc34l7Om_uBffs9VBd2zxvH4Kn/view?usp=sharing).

[huhn]

because i use that file to show issues with the deinterlacer.

[bouwew]

Just FYI, I've just installed the Nvidia 460.97 hot-fix-driver. I'm coming from 460.79.

Result: HDR is no longer working: I'm seeing SDR-colors when playing a HDR-video.
After some experimenting I found out that I had to toggle the Windows HDR-switch to ON to make HDR work again.
With this setting both SDR- and HDR-videos are displayed with the correct colors.

Windows 10 20H2, MPC-BE latest nightly, LAV latest nightly, MadVR 0.93.17+v117
LG OLED55C7V, Yamaha RX-A2020

[justcheeze]

@justcheeze - In the LAV Splitter, what is the "Stream Analysis Duration" set to? I used to have issues with the HD audio formats, pausing and resuming mainly, but recently clsid changed that value from 1000 to 2100 (built-in LAV in MPC-HC), and I haven't had any problems since. This might not be related to what you're experiencing, but it's worth a shot.

Disclaimer: Nev says that this change shouldn't affect my dropouts at all, but I am now able to pause a file with TrueHD/Atmos or DTS-HD for a long time, and the audio will pick right up when I resume. Before, only video would play, audio would not come back.

Welp following back up on this, watched a few movies since... no dice. Audio drop outs still happen.

It's starting to get very frustrating because there is NO WAY to pin point the issue.

[Klaus1189]

Audio drop outs still happen.

I beg to further investigate the issue. It must not be fast, but continuously. I have to do this also on my own. What changes were made to the system? AVR in chain to TV? Firmware update made of AVR? Any settings changed in AVR? Bitstreaming vs PCM any difference?

[bouwew]

Welp following back up on this, watched a few movies since... no dice. Audio drop outs still happen.

It's starting to get very frustrating because there is NO WAY to pin point the issue.
I did experience audio dropouts when using MPC-BE from within the early Kodi 18 versions. After rolling back to Kodi 17 the dropouts where gone.

Since recently I'm back to Kodi 18.9 and 19 betas 1&2: no audio dropouts until now.

It took me a long time to come to this conclusion, I had never expected that Kodi could be the culprit...

[VBB]

Just FYI, I've just installed the Nvidia 460.97 hot-fix-driver. I'm coming from 460.79.

Result: HDR is no longer working: I'm seeing SDR-colors when playing a HDR-video.
After some experimenting I found out that I had to toggle the Windows HDR-switch to ON to make HDR work again.
With this setting both SDR- and HDR-videos are displayed with the correct colors.

Windows 10 20H2, MPC-BE latest nightly, LAV latest nightly, MadVR 0.93.17+v117
LG OLED55C7V, Yamaha RX-A2020

What do you mean by SDR colors? Does the TV not trigger HDR mode anymore? With madVR, you should never have to switch on the Windows HDR setting.

I've been reading about people having issues with this hotfix driver and even the one before, but I can only go by my own experience. I've used them all, and I've never had to trigger HDR manually.

[brazen1]

I did experience audio dropouts when using MPC-BE from within the early Kodi 18 versions. After rolling back to Kodi 17 the dropouts where gone.

Since recently I'm back to Kodi 18.9 and 19 betas 1&2: no audio dropouts until now.

It took me a long time to come to this conclusion, I had never expected that Kodi could be the culprit...

I doubt Kodi is your audio dropout problem. How could it be when your handing off all tasks to an external player and any associated components?

[justcheeze]

I beg to further investigate the issue. It must not be fast, but continuously. I have to do this also on my own. What changes were made to the system? AVR in chain to TV? Firmware update made of AVR? Any settings changed in AVR? Bitstreaming vs PCM any difference?

Alright first off, my system's specs:

- Ryzen 9 3900x
- Asus Crosshair 8 Hero
- GSkill 16GB 3600mhz CL16
- Asus TUF RTX 3080
- Yamaha RXA850 AVR
- LG OLED C9 65"
- Speakers are all SVS Ultras and dual SB3000 subs

So I'm sure it's got nothing to do with not hitting specifications. All HDMI cables are also 2.0 certified and they are used within the chain from connecting the PC to AVR to TV.

I watched an episode of The Grand Tour season 3 EP1 yesterday, it's only in DD+ and I got no drops. Then I also watched the UHD release of Ghost in the Shell (1995) in the original JP PCM track, but I used DSU to upmix it to the rest of my speakers, no audio drops as well. I don't have time to watch another movie yet until the weekend perhaps, but the last movie I watched which was Wonder Woman 84, that suffered some drops. All movies are played off the HDDs in the PC, they're just Seagate 4TB NAS drives.

Like I've mentioned before, it's impossible to reproduce the error just by going back to the frame the audio dropped because by doing so - the audio just plays fine. It's extremely random and it's impossible to tell when it'll happen.


I did experience audio dropouts when using MPC-BE from within the early Kodi 18 versions. After rolling back to Kodi 17 the dropouts where gone.

Since recently I'm back to Kodi 18.9 and 19 betas 1&2: no audio dropouts until now.

It took me a long time to come to this conclusion, I had never expected that Kodi could be the culprit...

The funny thing is that earlier in the year 2020, I was having drop outs with MPC-HC. I tested with JRiver, not only I had audio drop outs there I also had frame drops. So I switched to PotPlayer and the drop outs went away for a while, then out of no where it happened again. I had not change a single thing. After that, I switched to MPC-BE and the drop outs stopped again for a while... until, out of no where it happens again.

At first I suspected Win10 updates caused issues, but it would make no sense because I've only ever updated my system ONCE the entire year of 2020.

On the Kodi thing, I'm not sure how that has anything to do with the players when you're using an external player to launch a movie within Kodi? I mean... Kodi really is just a front end, no?

[Klaus1189]

Since I have a RTX30 card now, too, I can test myself:
I tried to play HDR video files in passthrough mode and it just works fine. But I need fullscreen, not exclusive fullscreen, but at least any kind of fullscreen. I do get washed out colors if I am in windowed not fullscreen mode.
But I watch movies in fullscreen and have set MPC-BE to close itself after playback, so for me everything is still working fine. This thread is meant for HTPC usage and this is HTPC usage. If you have other opinion about it, let me know and I add it to first page.

[justcheeze]

Borderless windowed (fullscreen windowed as reported in madvr) works for me, no issues with HDR nor SDR. Color space is correct too.

I guess I could try exclusive fullscreen to see if that changes anything in regards to audio drops, but I doubt so.

[Klaus1189]

Forgot to say, I tested with latest GeForce Hotfix Driver Version 460.97 (https://nvidia.custhelp.com/app/answers/detail/a_id/5145/~/geforce-hotfix-driver-version-460.97)
So I can not confirm the issues.

[justcheeze]

I'm still on driver 460.79. But to be frank, the issue has existed with every driver.

But anyways, exclusive fullscreen doesn't fix the issue either. Really out of ideas now. I've checked ALL my settings from head to toe, about a hundred times now and there is nothing amiss about it.

[Klaus1189]

@justcheeze:
I was testing just HDR video issues, not your audio drop issue. Your audio drop issue is very interesting. I know sometimes you think it is impossible to find the reason, but do some more tests.
What Video player and Audio Renderer do you use? WASAPI, ...
I can only recommend MPC-BE. Enable MPC Audio Renderer. You can also wasapi mode from event to push. Please try change these settings for testing puposes and report back, but it will take some time, because this issue only appears sometimes. I know that kind of stuff.

[Grimsdyke]

Have you looked for possible bottlenecks on the OS side ?? Drive to full ? Last time of defrag ? To high or to low settings of VRAM ? Etc.

[justcheeze]

@justcheeze:
I was testing just HDR video issues, not your audio drop issue. Your audio drop issue is very interesting. I know sometimes you think it is impossible to find the reason, but do some more tests.
What Video player and Audio Renderer do you use? WASAPI, ...
I can only recommend MPC-BE. Enable MPC Audio Renderer. You can also wasapi mode from event to push. Please try change these settings for testing puposes and report back, but it will take some time, because this issue only appears sometimes. I know that kind of stuff.

Using MPC-BE 1.5.5 x64.
Video renderer = madvr.
Audio renderer = MPC Audio Renderer.

I'm already using WASAPI, but it's in Event mode. I will try changing it to Push and see how that goes.

LAV filters are also used of course, on the latest nightly version now.


Have you looked for possible bottlenecks on the OS side ?? Drive to full ? Last time of defrag ? To high or to low settings of VRAM ? Etc.

If you read my specs a few posts up, specs wise - there are absolutely no bottlenecks.

As for HDDs, they are defragged. I've even put movies on the NVME drive and the same issue occurs.

[VBB]

Thanks! So, basically the hotfix rolled into a new release :)

[bouwew]

I doubt Kodi is your audio dropout problem. How could it be when your handing off all tasks to an external player and any associated components?

I was as surprised as you but after extensive testing I'm quite sure it was the root cause. When playing several movies and series-episodes with MPC-BE from within Kodi, resulting in occasional audio drops, and with MPC-BE stand-alone, no audio drops, the situation became clear to me.
This issue was present up to version 18.3 if I remember correctly. It was gone with version 18.8, again if I remember correctly. Again, when downgrading Kodi to v17.6, the audio drops were gone.

[el Filou]

It can happen if there is some plugin/extension for Kodi or a background task that suddenly causes a peak in CPU use or I/O.
It shouldn't have that much of an impact if the system is recent but you never know.
Do you use the option to set MPC to use "Above normal" priority and if not, can you try?
Maybe start Windows' Resource Monitor and check the Disk tab with filtering on Kodi's process to see if files other than the movie you're playing are being accessed.

[brazen1]

Food for thought to those that rarely update GPU drivers because they think it might introduce problems. I feel the same about not updating the O/S too.

https://news.thewindowsclub.com/nvidia-fixes-gpu-vulnerabilities-through-latest-display-driver-update-104798/

[Andy o]

Hi, did you ever got this issue fixed?

Coincidentally, I've been having sporadic audio drop outs too particularly with Atmos and sometimes even DTS HD tracks. The drops are very brief, like half a sec tops and it happens very randomly. There is no way to accurately reproduce the problem because seeking back to the frame where audio drops doesn't repeat the issue.

It's weird that lossy tracks (DD, DD+, DTS) are fine and even PCM has no issue.

I'm still getting them even with the newest 461.09 driver. It's been pretty awful to try to troubleshoot, since sometimes it seems fixed if I change one thing, then it starts happening again, then I change the thing back, and it doesn't happen. I've tried closing the player and opening again without changing anything and sometimes it gets fixed. It's sporadic and semi-random but it happens most of the time. Yesterday it happened with a DTS-HD 7.1 movie.

I'm still in the process of building a new HTPC from scratch now with an 5800x and x570 board so I'll see if it happens then. I notice you're using a C9, which seems to be one of the few things we have in common, how is it connected to the AVR, via eARC (PC -> TV -> AVR)? That's how I have it. Also what resolution and refresh rate are you running the TV at? It could be the new-ish firmware for the C9 (hopefully not!).

[Klaus1189]

I have reconsidered I mention the HDR passthough issue on recent Nvidia drivers and mention also the workaround. What version was the first which causes the need to close the player?

Anybody got the 6800 / 6800XT / 6900XT already? Would like to do some tests with it, if anybody has one card and is willing to test for some minutes.

[chros]

I have reconsidered I mention the HDR passthough issue on recent Nvidia drivers and mention also the workaround. What version was the first which causes the need to close the player?
Which issue are you referring to?

[Klaus1189]

This one:
https://forum.doom9.org/showthread.php?p=1930413#post1930413

[chros]

That is with any HDR output not just passthrough, see it here (https://forum.doom9.org/showthread.php?p=1927705#post1927705), it started with 442.92.

[aron7awol]

I think the other thing worth noting in the list is the much improved 23p default timings on the 45x.xx branch. It's a shame we don't have a build that doesn't have some sort of HDR issue in that branch, because it's a very nice improvement.

[Klaus1189]

Yes, you are right, what was the exact first driver version which made 23p refresh rate way better than it was before on Nvidia cards?

[Klaus1189]

I have added the info. Is it correct this way?

[aron7awol]

Looks good to me.

[mattl0]

I have a 1050ti card , with windows 10 up to date.

I have downloaded the 398.11 driver exe and unziped it to change the hd audio driver to the newest.
Like that I get proper hdr metadata if I understand the second post correctly?

Newer drivers after 398.11, all introduce faulty metadatas? If I want to get a more powerful card , shall I stay with gtx card (1080ti) to be able to run this specific driver?

Just need to validate theses points too . Is there a non bogged hdr driver for rtx 20xx or rtx 30xx?
If the answer is no, does any amd card have proper metadata? I do not care to change if the is no issues with hdr on amd side.

Thank you
Thank you

[VBB]

You can use the latest Nvidia driver. HDR works, metadata gets passed through. It's been like that for quite a while.

[VBB]

GeForce Hotfix Driver Version 461.33

https://nvidia.custhelp.com/app/answers/detail/a_id/5152

Nothing HTPC related...

[mattl0]

You can use the latest Nvidia driver. HDR works, metadata gets passed through. It's been like that for quite a while.

Thanks. It does works .

Maybe the second topic need to be edited to remove the green remark concerning hdr metadata on 398.11

[mattl0]

You can use the latest Nvidia driver. HDR works, metadata gets passed through. It's been like that for quite a while.

Thanks. It does works . So I may be able to get a 3060ti or 3070 then :D

Maybe the second topic need to be edited to remove the green remark concerning hdr metadata on 398.11 @Klaus1189

[Klaus1189]

Now also in "Intel® Graphics - Windows® 10 DCH Drivers" there is "Support for Intel® Iris® Xe Max Graphics (DG1)"

Why did Intel create a dedicated driver before and then add support in the other package? Then the dedicated package will see no more updates, is it?

[Klaus1189]

first AMD driver of 2021

[Yups]

Now also in "Intel® Graphics - Windows® 10 DCH Drivers" there is "Support for Intel® Iris® Xe Max Graphics (DG1)"

Why did Intel create a dedicated driver before and then add support in the other package? Then the dedicated package will see no more updates, is it?


It wasn't a dedicated driver, I could install it on Tigerlake. It's the same chip, there is no need for a separate release anymore.

[Klaus1189]

Ok, i do not have any intel cpu with integrated graphics here to test, but Intel listed and still lists the two independently:
https://downloadcenter.intel.com/product/80939/Graphics

[Yups]

I know, the listed Xe Max driver there can be installed on Tigerlake as well. There is no real separate driver which wouldn't make sense, it's the exact same chip. The newest driver release supports both officially.

[justcheeze]

I'm still getting them even with the newest 461.09 driver. It's been pretty awful to try to troubleshoot, since sometimes it seems fixed if I change one thing, then it starts happening again, then I change the thing back, and it doesn't happen. I've tried closing the player and opening again without changing anything and sometimes it gets fixed. It's sporadic and semi-random but it happens most of the time. Yesterday it happened with a DTS-HD 7.1 movie.

I'm still in the process of building a new HTPC from scratch now with an 5800x and x570 board so I'll see if it happens then. I notice you're using a C9, which seems to be one of the few things we have in common, how is it connected to the AVR, via eARC (PC -> TV -> AVR)? That's how I have it. Also what resolution and refresh rate are you running the TV at? It could be the new-ish firmware for the C9 (hopefully not!).

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.

[hans.gruber]

Hello,

Is there a way to configure madVR to not use AMD's proprietary API calls, ie just DirectX?
I want to try this because madVR works for me in exclusive mode exactly once after a system reboot
and if I try the 2nd time the colors are off (yellow tint).
In windowed mode it also has this tint until I point the mouse at the seek bar and then back to the movie (to make the seek bar disappear).
After I do this the yellow tint disappears.

The reason I'm asking is because Kodi 19 RC works every single time in windowed and it is not using any proprietary calls, just pure DX AFAIK.
I'm using 20H2, APU 4650G, tried multiple drivers starting with Oct 19 driver. March 2020 drivers don't support Renoir APUs.

Regards

[huhn]

is your OS is in HDR mode it will not use the AMD API.

[DMU]

I'm using 20H2, APU 4650G

I have the same APU, there are no issues in the FSW (Full Screen Windowed) mode on any driver.

[hans.gruber]

I have the same APU, there are no issues in the FSW (Full Screen Windowed) mode on any driver.

do you also have to show/hide seek bar in FSW for the colors to be correct?

[DMU]

@ hans.gruber
At the start of video playback, the colors are correct; when you call the seek bar, they are not correct.

[hans.gruber]

@ hans.gruber
At the start of video playback, the colors are correct; when you call the seek bar, they are not correct.

that is expected afaik, however for me i have to show and hide seek bar otherwise i get yellow tint with the bar hidden.
my apu is somewhat newer than 2200g, the newer driver may behave differently for this hardware or have diff bugs :/

[DMU]

my apu is somewhat newer than 2200g, the newer driver may behave differently for this hardware or have diff bugs :/

I have both.

[VBB]

New Nvidia driver 461.40:

Standard - https://us.download.nvidia.com/Windows/461.40/461.40-desktop-win10-64bit-international-whql.exe

DCH - https://us.download.nvidia.com/Windows/461.40/461.40-desktop-win10-64bit-international-dch-whql.exe

No HTPC-related changes or fixes

[SamuriHL]

If I get a minute I'll see if it breaks anything HTPC related.

[Klaus1189]

Well, at least prices are going to normalize
https://www.alternate.de/Grafikkarten/NVIDIA-Grafikkarten/html/listings/1486466143032?s=price_desc

[Klaus1189]

https://www.youtube.com/watch?v=aAJXQXOCw14
And the english review:
https://www.igorslab.de/en/set-with-xe-intel-iris-xe-max-grahics-in-exclusive-teardown-and-with-massive-driver-problems-at-benchmarks-leak/

[quietvoid]

For some reason Windows Update decided to update my NVIDIA driver to 456.71 from 441 something.
Pretty sure I had DDU disable the updates..

[VBB]

GeForce Hotfix Driver Version 461.51

HTPC relevant fix (sorta LOL) - "LG CX OLED TVs (2020) are not recognized as G-SYNC Compatible displays"

https://nvidia.custhelp.com/app/answers/detail/a_id/5158

[Bello]

something is similar happened to me when I tried to update my all drive I am having issue's in updating it and I have also search a lot but I doesn't found anything which is helpful but now after visiting this post I think I got solved my issue.

[GTPVHD]

https://nvidia.custhelp.com/app/answers/detail/a_id/5159/

Something Nvidia users should read.

[Asmodian]

Yes, the recommendation for madVR has always been to leave the driver V-sync set to "Use the 3D application setting"

Edit:
It sounds like a nice upgrade for the Windows DWM.

[huhn]

microsoft is working for a while now to improve mix refreshrate setups this maybe the final fix this is really big.

[SamuriHL]

I've always had vsync on. I've never had any success with stable refresh rates in madvr with it disabled.

[Asmodian]

How about with it set to "Use the 3D application setting"?

That has always been the most trouble free option in my experience.

[VBB]

These days, I don't touch anything in the 3D settings.

[darksen]

I had to go back to 457.51 again after installing 461.40 because I had crackling in audio, lately all drivers have issues, don't they? I remember with 460.79/89 I had audio desynchronization in all the video players and crackling too (I haven't tested playing videos with 461.40 but chances are the desync still remains in that version).

[Asmodian]

I have never had audio desync or crackling audio due to Nvidia's drivers. :confused:

[ryrynz]

I had to go back to 457.51 again after installing 461.40 because I had crackling in audio

457.51 uses audio driver version 1.3.38.35, 461.40 uses 1.3.38.40.

Install the new driver then afterwards revert the audio driver in the driver manager to the old version.

[el Filou]

That's strange, does the crackling/desync happens with all audio or only with bitstream? On what card? If it also happens with system/browser/games audio, what format is set in Windows audio config?
I don't have any problems with 1.3.38.40 but I'm only using LPCM at 24/48 (still on Windows 1909).

[Klaus1189]

Please let me know if there is anything to add on first page regarding the crackling audio.

Is there a RX6000 user out there who reads this thread? I need some info.

[clsid]

Audio crackling/desync can be due to DPC latency issues.
https://www.resplendence.com/latencymon

[Snowknight26]

Is there a RX6000 user out there who reads this thread? I need some info.

Let me know what you need.

[Klaus1189]

The RX5000 series has a 0-255 vs 16-235 bug. A workaround for it is to use madVR or MPC-VR with D3D11 option checked.
If you could check if this issue is also present in RX6000 would be awesome. And to check the deinterlacer of it would be good.

Make sure you have a TV in pc mode which wants 0-255 and play a video in MPC-BE or also MPC-HC and check the black levels. Are the blacks elevated or black as it should be. In MPC-BE, probably also in MPC-HC there is an option in "Video" Tab in options which lets you override the output range. Does this setting make a difference if you choose 0-255 and then 16-235?

For the deinterlacer test you need to download:
https://drive.google.com/file/d/12wO8NJbIrfa2MD4yVaA38RrBBdziCda8/view
Play it and check the charakters above "www.D88.com" for flickering:
https://wst.tv/wp-content/uploads/2018/06/D88.com_.jpg
Flickering like here:
https://upload.wikimedia.org/wikipedia/commons/f/f0/Indian_Head_interlace.gif
If you use LAV Filters use DXVA2 copyback, but not D3D11 for deinterlaing test.

[Snowknight26]

The flickering when using GPU deinterlacing is still there. Haven't tested the black level issue, I'll check another time.

[Klaus1189]

Thanks for deinterlacing test. I am looking forward for the elevated black level test. Do it when you want to do it. Cheers ;)

[Klaus1189]

Did you disable Software Deinterlacing in LAV Filters? This is mandatory for GPU Deinterlacing test.

[Snowknight26]

Did you disable Software Deinterlacing in LAV Filters? This is mandatory for GPU Deinterlacing test.

I did. As I was testing it I even noticed the flickering with YADIF though it was very subtle.

Edit: Just tested black levels, they're still elevated when using EVR CP.

[Klaus1189]

Thank you for the test. I really appreciate it :)

[darksen]

I have never had audio desync or crackling audio due to Nvidia's drivers. :confused:

Me neither, this is the first time it happened to me, in fact this is the first time I have any problems with the nvidia drivers.

457.51 uses audio driver version 1.3.38.35, 461.40 uses 1.3.38.40.

Install the new driver then afterwards revert the audio driver in the driver manager to the old version.

That's strange, does the crackling/desync happens with all audio or only with bitstream? On what card? If it also happens with system/browser/games audio, what format is set in Windows audio config?
I don't have any problems with 1.3.38.40 but I'm only using LPCM at 24/48 (still on Windows 1909).

I'm not using bitstream, that's what is strange, I'm using the motherboard's built in audio, Nvidia has nothing to do with my system's audio and I don't know why updating the driver makes the sound play like that. The GPU is a 1650 S.

Audio crackling/desync can be due to DPC latency issues.
https://www.resplendence.com/latencymon

I will check this but I don't think this is the problem as this has started ever since I updated the driver and it happens every time I update it, the moment I downgrade all the problems disappear.

----------------------------------------------------------------------------------------------------

The audio desync is still happening with the latest drivers, Windows updated the driver to 461.40 by itself after a reboot and I tried playing a movie in Netflix but the audio desyncs a lot, before this I have to say I had already played the same movie with 457.51 and everything was alright after rebooting and the driver upgrading the problems returned. I have even updated my CPU to a Ryzen 7 3800X but the problem still persists.

[clsid]

DPC latency issues are often due to a driver. If it shows the nvidia driver as culprit then you have confirmation that the driver is responsible.

[Klaus1189]

@darksen:
So last working driver for you is 457.51?
Every newer driver is affected?
Can you make screenshots of the installer? I mean the differences in versions of packages like HD Audio driver version, ...

But how can a grafic driver be the culprit, if you are not using the HD Audio Driver?
Since you are using the analog outputs of your mainboard, right?

[ryrynz]

What about reverting or updating the motherboard audio drivers? Sounds like something you may with to take up with Nvidia/Realtek?/Your motherboard manufacturer.

[Andy o]

Can anyone with a RX6000 card and an LG C9/CX OLED corroborate that it can do QMS, not blanking out for frame rate switches, like this user at AVS has experienced? https://www.avsforum.com/threads/2019-lg-c9%E2%80%93e9-dedicated-gaming-thread-consoles-and-pc.3123168/page-260#post-60426761

[SamuriHL]

[Blu-ray][HDMI]: Flickering occurs in Blu-ray playback when played over HDMI. [3221611]

Ain't that fantastic. At least it's fixed....I guess?

LG CX OLED TVs (2020) are not recognized as G-SYNC Compatible displays.[3244055]

LOL woopsie! :D

[Notebook]: On some Notebooks, the 'Maximum Graphics Power' information missing in the
NVIDIA Control Panel > System Information page. [200697069]

SIGH...

[KrazyLurt]

Nvidia GeForce 461.72 solved 24hz vsync issues for me using Mpv with Vulkan coming from 461.40, not with d3dx11 though.

[Klaus1189]

[Blu-ray][HDMI]: Flickering occurs in Blu-ray playback when played over HDMI. [3221611]

Ain't that fantastic. At least it's fixed....I guess?

I tested the new driver with just updating, no DDU or at least the checked the option to do a clean install and I got screen flickers/ drop out almost one per minute now ... hmm ... at least a change from one per three days to one per minute :D
Now I just installed the new driver with checked clean install and I am gonna see what happens then ... so far no drop out/ flicker on Desktop.

[SamuriHL]

Oh boy that's "encouraging" LOL I haven't installed it on my HTPC yet. I did do my laptop though.

[Warlock]

Driver 461.72

Several desktop applications flicker when Vertical Sync is set to the default “Use the 3D application setting”. [3252186]

Who is using mpc-hc with madvr, this driver solved the problem of stutterings and presentation glitches for which has turing series video card?

[brazen1]

I've been using 461.72 for a couple days now. I've watched several mixed content videos and used many, many desktop applications. The only Manage 3D setting I've changed is Power Management Mode set to Adaptive. With and without madVR fwiw. The flickering and other complaints must be exclusive to elaborate conflicted setups, alpha/beta software, display type and/or choice of GPU. I constantly read complaints yet never experience any of them and the GPU driver is always to blame. Driver works fine here fwiw.

[Klaus1189]

I've been using 461.72 for a couple days now.

Yesterday released :confused:

What GPU do you have? This flickering/dropout/short blackscreen on Desktop and low usage like web browsing is (hopefully was) exclusive to Ampere only to my knowledge. Older generations are fine.

[brazen1]

I got the new driver the evening of the 24th where I am. I used it that evening, yesterday, and today as well. My info including GPU is in my sig where it should be. As stated, The flickering and other complaints must be exclusive to elaborate conflicted setups, alpha/beta software, display type and/or choice of GPU. Furthermore, all these problems could be a bad combination of any of those variables.

[Klaus1189]

So you got a 960 with 4GB VRam? This card should not be affected by the bug. I am testing latest 461.72 and so far it looks very promising :)
Never had any issue with that display with my heater RX480 then the RX5700XT had this drop outs (everybody had these) and also this new Nvidia RTX 30 card, probably not so new anymore, but 700 € more expensive now.
But the issue seems tobe gone in this new driver version. Look in one of my older posts, yesterday I installed without ddu or clean install in installer and got one flicker/dropout per Minute. :D
I was happy because that means they did something to the driver and I only must do a clean install or ddu it. Very happy now, but 23Hz refresh rate of AMD is so good out of the box...

[brazen1]

I should add, for many driver versions going way back, I still have the audio problem I had in the past beginning after 388.59. It's frustrating but fixable as usual. This is why I'm on-top-of every new driver release... for me personally using my setup. I don't think there's anything weird, strange or elaborate with my components or my setup. I've never received a reply from anyone if they experience the same thing though I've brought it up a few times here and elsewhere. I'll throw it out here again...

To duplicate:

Clean install a new driver. DDU or whatever.
Windows audio properties reports it's in stereo even though the AVR is turned on. So make the changes for 5.1, 7.1, etc. to match what you use.
Turn the AVR off. Windows Audio will switch back to stereo as it should. Leave the AVR off.
Now reboot. Windows audio will report 5.1, 7.1 or whatever you set it to earlier. Except the AVR is still off and a display, for example, should be using its internal speakers instead of the AVR's external speakers.
Now go to a desktop application like YouTube and play a video. There is no audio from the TV speakers.
Of course you turn on the AVR and use its external speakers but what if you don't want the AVR on and you prefer the TV speakers while surfing desktop apps?

Windows audio isn't auto switching dependent on the Off/On AVR state fed by the audio driver.

The fix is to replace the present nVidia HDAudio driver with the older one from back when it worked by editing the installer package. Then everything performs perfectly as it should. Now I know this doesn't apply to everyone since most folks use an AVR on for everything. I only want my AVR on when watching movies and such. Not so much when using the Windows desktop but I still need audio. Some say never to adjust Windows audio properties and just leave it at stereo so the AVR does the decoding. I don't even know what that means because my AVR is still decoding even if Windows Audio properties matches my audio format. Furthermore, 'some' audio formats such as AAC will not convert to multi channel if stereo is set. They simply output stereo because they haven't been told to output any differently.

[brazen1]

For me, nVidia 23Hz refresh rate and all other refresh rates are good out of the box too. Here's some screens with the madVR OSD showing I posted elsewhere the other day.

https://www.avsforum.com/threads/madvr-player-support-thread.2215490/post-60511664

Tbh, newer GPU's, and all the micro stutter, flutter, and other complaints of late, considering their prices too, the 960 remains the apple of my eye. But then, I don't need to madVR tone map thank goodness. That would be impossible.

[Klaus1189]

I get ~50 minutes in 23 Hz mode but that is nowhere near AMD :) Every other refresh rate is good imho. It was always the 23 Hz refresh rate (not 24 Hz or any other one) which was about 4 minutes out of the box.

But isn't that fixed? I added a note to Nvidia section:
Every Nvidia driver after 388.59 has a faulty updated HD Audio driver in the newer Windows driver installer packages. 456.71 fixes that issue.
https://forum.doom9.org/showpost.php?p=1913991&postcount=1319
https://forum.doom9.org/showpost.php?p=1925217&postcount=1978

[Klaus1189]

Correction: ~53 minutes for my Nvidia.

Since I do not have a Intel CPU with Intel HD 630. How does this one do for a simple small HTPC. Any issues known?

[brazen1]

I get ~50 minutes in 23 Hz mode but that is nowhere near AMD :) Every other refresh rate is good imho. It was always the 23 Hz refresh rate (not 24 Hz or any other one) which was about 4 minutes out of the box.

But isn't that fixed? I added a note to Nvidia section:
Every Nvidia driver after 388.59 has a faulty updated HD Audio driver in the newer Windows driver installer packages. 456.71 fixes that issue.
https://forum.doom9.org/showpost.php?p=1913991&postcount=1319
https://forum.doom9.org/showpost.php?p=1925217&postcount=1978

That driver and my report was jumping the gun. I remember now. I always reboot after installing new drivers including that one to the best of my memory. I was so excited to see it remained working after the reboot (unlike other drivers) I reported here.

Unfortunately, after the next reboot, it failed. I spent time duplicating what I always do but never got it to work again. I chalked it up to I did something wrong in my 1st test that was off... possibly even not rebooting but thinking I did. Not sure? I definitely forgot to report back here to correct my post. Totally on me and my bad. Sorry. You can remove that 2nd 'fixed' update on the 1st page. The damn thing still doesn't work.

[el Filou]

Can anyone with a RX6000 card and an LG C9/CX OLED corroborate that it can do QMS, not blanking out for frame rate switches, like this user at AVS has experienced? https://www.avsforum.com/threads/2019-lg-c9%E2%80%93e9-dedicated-gaming-thread-consoles-and-pc.3123168/page-260#post-60426761QMS 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.

[Warlock]

I've been using 461.72 for a couple days now. I've watched several mixed content videos and used many, many desktop applications. The only Manage 3D setting I've changed is Power Management Mode set to Adaptive. With and without madVR fwiw. The flickering and other complaints must be exclusive to elaborate conflicted setups, alpha/beta software, display type and/or choice of GPU. I constantly read complaints yet never experience any of them and the GPU driver is always to blame. Driver works fine here fwiw.

Has it just changed in the global settings tab?

[VBB]

'Adaptive' is the default now anyway, since they got rid of 'Optimal'. From an HTPC perspective, there is nothing to change in 'Manage 3D Settings'.

[Asmodian]

Now it is called 'Normal' not 'Adaptive'.

But it does work well for me, no benefit to 'Prefer maximum performance' for HTPC.

[VBB]

There you go. Shows how often I check those settings these days ;)

[el Filou]

I think it depends on the GPU. I still have Optimal, Adaptive, Max perf with a Pascal card even after DDU.

[VBB]

With the 46*.** drivers? I have a Maxwell card, and it shows only Normal and Max Perf.

[Klaus1189]

Only Normal and max Performance here too for an Ampere card

[SamuriHL]

On my 2070 it still shows adaptive. I just did a clean install of the driver.

[Manni]

Weird. Only normal and max perfect with my 3090.

[Klaus1189]

@VBB - "Maxwell":
• Normal
• Prefer maximum performance

@el Filou - "Pascal":
• Optimal power
• Adaptive
• Prefer maximum performance

@SamuriHL - "Turing"
• Optimal power
• Adaptive
• Prefer maximum performance

@Manni & @Klaus1189 - "Ampere":
• Normal
• Prefer maximum performance

I installed on my current Windows fresh install only:
1.) 461.40 from 2021-01-26, then
2.) 461.51 from 2021-02-05 and last
3.) 461.72 from 2021-02-25.

That is a really strange distribution between the architectures :confused:

[Klaus1189]

Is there is a Vega and/or Radeon VII user, who followes this thread?
If so, please test Hardware deinterlacer and color range - see details in first post of this thread. I do not know, but I think Vega and Radeon VII were both fine and the issues started in RX 5000 series. I still have my RX 5700 XT and can test myself.
I want to collect as much info as possible. Perhaps I can get AMD to recognize these video related bugs.

[SamuriHL]

To your question yes optimal is there and default for my 2070.

Sent from my SM-G998U1 using Tapatalk

[brazen1]

461.72 and all previous GRD versions I've always shown

• Optimal power
• Adaptive
• Prefer maximum performance

Maybe it's the difference between SD and GRD versions?

[Klaus1189]

@SamuriHL:
Thanks :)

@brazen1:
I have only installed 461.40 GRD, then 461.51 Hotfix and then 461.72 GRD on a complete fresh windows installation, I deleted all previous partitions during installation.

[el Filou]

With the 46*.** drivers? I have a Maxwell card, and it shows only Normal and Max Perf.Yes, 461.09. Maybe it depends on the Windows version? I'm still on 1909. (Edit: Game Ready Driver)

[Manni]

In case it makes a difference, I'm using studio drivers (461.72) and I'm on 20H2.

[SamuriHL]

I'm using GRD on whatever the hell version of windows is installed on that machine now. It's at least 20h2 but it might be something later than that at this point as I don't know what branch I have that machine set to at the moment.

[huhn]

just check the windows version number.

[Klaus1189]

search for "winver"

[VBB]

Perhaps there is a difference between Standard and DCH drivers?

"Standard" packages are those that do not require the DCH driver components.

"DCH" (Declarative, Componentized, Hardware Support Apps) refers to new packages preinstalled by OEMS implementing the Microsoft Universal Driver paradigm.

DCH drivers cannot be installed over a standard system, and Standard drivers cannot be installed over a DCH system.

To confirm the type of system you have, locate Driver Type under the System Information menu in the NVIDIA Control Panel.

I have always installed the standard version of every driver, including hotfixes. DCH installs the entire control panel via the Microsoft Store. I never liked that idea.

[Klaus1189]

I know that I have installed the Standard non DCH on my system.

[SamuriHL]

Yes guys I know how to find the version lol. I'm just not on that machine right now and won't be today. I always install the DCH version of the driver.

[VBB]

Aha! Looks like we're getting somewhere ;)

[Manni]

I always install DCH as well.

[VBB]

...and back to square one :P

[oldpainlesskodi]

@Klaus1189 - what colour issues are you referring too ? Full-Full-Full chain I see no issues at all.

[Klaus1189]

This issue can only be be observed in EVR (CP) and MPC VR in D3D9 mode, D3D11 is fine and also madVR is always fine. Setting doesn’t matter in madVR.

AMD states that Windows 10 App is fine and declare it is fine but it is NOT.

Yes guys I know how to find the version lol. I'm just not on that machine right now and won't be today. I always install the DCH version of the driver.

Haha :D :D

[Calvi]

461.72 Stutters for me unless I force v-sync on in Nvidia settings.
Rtx2070, dch, 20h2

I have always turned it on(so earlier drivers are probably all the same here), but tried with this version in response to the comments about not having to set anything.
Stutter is also prevented by reducing frames to 1 in mad-Vr but with v-sync on I can leave mad-vr at default settings.

[VBB]

That's the point, though. For the Nvidia 2-series and newer, set madVR frames presented in advance to 1. Then you can leave all Nvidia settings at defaults.

[SamuriHL]

My machine is 10.0.19042 for the record.

[SamuriHL]

As for the present frames in advance being set to 1, madshi somewhat alluded to the fact that the Envy is doing that, as well. Or something like it anyway.

[VBB]

I think he meant queue sizes in general are much smaller with Envy, but yeah, probably frames presented in advance as well.

[SamuriHL]

He may have but given that it's 2xxx based (and upgrading to 3xxx) I suspect the frames presented in advanced is very low.

[oldpainlesskodi]

@Klaus1189 - ok, understood.

[Calvi]

That's the point, though. For the Nvidia 2-series and newer, set madVR frames presented in advance to 1. Then you can leave all Nvidia settings at defaults.

Yes, agreed.

Comes down to which you prefer, driver at defaults or madvr at defaults (or more than 1 frame in advance).

I figure 3 frames in advance is more useful than v-sync off as i only watch video on the pc.

Would perhaps be good if there was a MadVR setting or it defaulted to request vsync on from the driver then it would make sense to leave the default leave up to application setting in driver.

I guess another option is to set an application profile if gaming on same pc and there is a desire for v-sync off for some applications.

[Manni]

Not sure if this is a known bug or not, so I thought I'd report it anyway. I let madshi know but he isn't aware of it and doesn't know the cause (driver and/or OS).

D3D11 rendering in fullscreen windowed doesn't work anymore for me (3090, 8bits full).

When tonemapping HDR to SDR, colors are completely wonky in full screen windowed (think Andy Warhol).

Until recently, I was able to deal with this by staying with 460.89.

Unfortunately, something changed (OS update? 20H2?) and I have this issue with any driver supporting 3090.

If you get out of fullscreen windowed (hover the mouse on the playbar, right click, move the player from full screen to window), colors are fine.

If you use D3D9 new path, colors are fine too even in full screen windowed.

Anyone else experiencing this? Do we know what broke it and when?

The only fix is to use D3D9, which isn't ideal.

I only have the issue with madVR as I think MPC-VR uses D3D9, so doesn't have the issue.

[Klaus1189]

I only have the issue with madVR as I think MPC-VR uses D3D9, so doesn't have the issue.

What happens if you enable D3D11 in MPC-VR settings?
Play video -> rightclick -> Filters -> MPC Video Renderer.

I'll take a look at it, but not now, I am so tired from work. Other users can check that issue also in the meantime.

[VBB]

Manni, you're not the first one to report this, but I haven't heard of a fix for those affected. Very strange issue indeed.

[Manni]

What happens if you enable D3D11 in MPC-VR settings?


Thanks, no issue with MPC-VR when using D3D11, so it's a madVR bug.

Manni, you're not the first one to report this, but I haven't heard of a fix for those affected. Very strange issue indeed.

Good to know it's not just me. Very weird indeed, and sorry it's the wrong thread as it's a madVR bug apparently, given that MPC-VR doesn't show the issue when using D3D11.

[huhn]

did you try the different FSE modes?

[Manni]

did you try the different FSE modes?

No difference, the only option that makes a difference is d3d11 vs d3d9.

[Klaus1189]

What different FSE modes?

[huhn]

you can get the old real FSE mode back with some compatibility changes.

[Manni]

you can get the old real FSE mode back with some compatibility changes.

I don’t use FSE and I don’t know how to get the old mode back. The only thing I can say is that enabling/disabling FSE in madVR makes no difference.

[Klaus1189]

Ok thanks

[huhn]

I don’t use FSE and I don’t know how to get the old mode back. The only thing I can say is that enabling/disabling FSE in madVR makes no difference.

even if you are not planning on using it are you still willing to test it? may have something todo with the wddm and that could avoid it.

unlikely to help just to make that clear.

[Manni]

even if you are not planning on using it are you still willing to test it? may have something todo with the wddm and that could avoid it.

unlikely to help just to make that clear.

I am willing to test if you provide detailed instructions regarding how to bring the old FSE back. I won’t use it, but it could be an interesting test.

[huhn]

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

that's know it works with mpc-hc.

[Manni]

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]

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]

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.

[Manni]

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]

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.

[Manni]

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]

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/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]

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]

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

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 :D

[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]

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]

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]

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

[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]

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]

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]

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

[DMU]

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]

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]

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

[Klaus1189]

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]

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]

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]

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]

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]

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]

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]

2031. cause nVidia and AMD suck. :D

[Manni]

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.

[huhn]

2031. cause nVidia and AMD suck. :D

you forgot intel!

[SamuriHL]

Everyone does. ;)

[jkauff]

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]

I’ll wait for the next studio driver.

Time has come. Today new studio driver :)

[Manni]

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]

Time has come. Today new studio driver :)

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

[KrazyLurt]

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]

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]

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]

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.

[VBB]

Same here. Didn't notice any change. Everything works just like before.

[chros]

So what benefits does 398.18 get over 385.28 at all? Does 3D still work well incase you're using it ?
I don't use 3d, I guess it was removed before :)
And there's only 1 benefit: madvr b113 was broken with the older driver, due to FastBlur implementation, and that is working with this newer one.

[nsnhd]

3D MVC is working well with 385.28 by MPC-HC/madVR b113 and GTX 1060.
What's broken with b113, maybe I'm using tone mapping to my SDR displays hence don't notice that ?
But now I have issues with Kodi19 hardware decoding, it shows green screens (Kodi 18.9 doesn't), disable HW decoding solves it, maybe I have to wait for a Kodi fix.

[Klaus1189]

So what benefits does 398.18 get over 385.28 at all? Does 3D still work well incase you're using it ?
Thanks
I guess it was removed before :)

430.39 from 2019-04-23 drops 3D support according to my info ;)

[brazen1]

3D MVC is working well with 385.28 by MPC-HC/madVR b113 and GTX 1060.
What's broken with b113, maybe I'm using tone mapping to my SDR displays hence don't notice that ?
But now I have issues with Kodi19 hardware decoding, it shows green screens (Kodi 18.9 doesn't), disable HW decoding solves it, maybe I have to wait for a Kodi fix.

I doubt Kodi is going to fix anything to accommodate 2 - 3 yr old drivers. Are you using Windows 10 20H2? Also did you install JAVA for Kodi 1:1 rips? If you use them and you didn't, that might lead to green screens. I understand you need to use older drivers for 3D but honestly and sadly everyone else has moved on.

[nsnhd]

No, I'm not using JAVA and haven't installed them. But I'm also not using Windows 10 20H2 because newest version might break some things according to posters here, maybe I should upgrade to it if Kodi not fixing the issue, v19 just released and they may need some time.
Thanks

[chros]

But now I have issues with Kodi19 hardware decoding, it shows green screens (Kodi 18.9 doesn't), disable HW decoding solves it, maybe I have to wait for a Kodi fix.

It was this green and black acreen with b113 when you used d3d11-native, it didn't happen with dxva-copyback (as far as remember). Try this out in mpchc and lavfilters.

[brazen1]

Matrix is really nothing new except the official release of it recently. I was using Kodi v19 for over a year with and without JAVA. Now I'm using v20 with. I'm also using Windows 20H2 and all the previous O/S's. If you're on W7 or something, upgrading might help. If you're one or two Windows builds behind, that won't make any difference because myself and others used them with no problems either. I've no idea what 20H2 broke for other users here? Didn't break anything for me or others here afaik. I have to assume your green screen problem is something else upstream. More details and specifics in user signatures would help. I'm just curious why 18.9 works for you and 19 doesn't given both work perfectly for me and others. In other words, there is nothing for Kodi devs to fix imo.

[nsnhd]

It was this green and black acreen with b113 when you used d3d11-native, it didn't happen with dxva-copyback (as far as remember). Try this out in mpchc and lavfilters.
The issue happens only on Kodi19, the rest including Kodi 18.9 is fine.

If you're one or two Windows builds behind, that won't make any difference because myself and others used them with no problems either. I've no idea what 20H2 broke for other users here? Didn't break anything for me or others here afaik. I have to assume your green screen problem is something else upstream. More details and specifics in user signatures would help. I'm just curious why 18.9 works for you and 19 doesn't given both work perfectly for me and others. In other words, there is nothing for Kodi devs to fix imo.
I'm using WinPro 1909, so maybe not much different from 20H2.
Lots of complains here are about breaking switching frame rates, HDR, 8-bit/10-bit...etc. when mixing drivers updates with windows updates.
As I read in Kodi forum, there is a huge change from Kodi 18.9 to Kodi 19, so maybe that affects my usage. Even devs there suggest to install Kodi 19 in Portable Mode and wait for stability.

[VBB]

GeForce Hotfix Driver Version 462.07 (https://nvidia.custhelp.com/app/answers/detail/a_id/5174)

GeForce Hotfix display driver version 462.07 is based on our latest Game Ready Driver 461.92.

The hotfix addresses the following issues:
[Vulkan][X4: Foundations 4.00/X4: Cradle of Humanity] The game may crash on GeForce RTX 30 Series

Nothing to see here. Move along...

[the_jaguar]

3D MVC is working well with 385.28 by MPC-HC/madVR b113 and GTX 1060.
What's broken with b113, maybe I'm using tone mapping to my SDR displays hence don't notice that ?
But now I have issues with Kodi19 hardware decoding, it shows green screens (Kodi 18.9 doesn't), disable HW decoding solves it, maybe I have to wait for a Kodi fix.

430.39 from 2019-04-23 drops 3D support according to my info ;)

Yes, 425.31 is the last official version with 3D MVC support. That being said, by using the 3D fix tool available on another forum, I was able to get 3D MVC to work on 452.06 (I am sure it will work on later versions too). One thing to note is that beta 113 of madVR will not work (due to a bug), so you will have to use beta 114. This will introduce the time limitation constraint of madVR, which I have overcome using a windows tool that changes date just for madVR.

In my case, Windows forced an OS version upgrade, which forced a Nvidia driver upgrade, so had to go through this process to get 3D MVC to work again :)

[Klaus1189]

by using the 3D fix tool available on another forum, I was able to get 3D MVC to work on 452.06 (I am sure it will work on later versions too).

Do you mean the "3D Fix Manager", that is mentioned in Notes of Nvidia section? Or is it another tool?

[the_jaguar]

Do you mean the "3D Fix Manager", that is mentioned in Notes of Nvidia section? Or is it another tool?

Yes, that works too, but there is also another script that's written by Losti that automates the entire process (https://www.mtbs3d.com/phpbb/viewtopic.php?f=105&t=25361)

[SamuriHL]

Oh no. I mean, hurray! LOL

[el Filou]

PCI Express Resizable BAR is now supported on RTX 3000 with the new driver. I'm curious if this could improve performance of copyback DXVA decoding with 10-bit UHD.
Could anyone who has hardware that has official support for that feature (apparently there are multiple requirements https://www.nvidia.com/en-us/geforce/news/geforce-rtx-30-series-resizable-bar-support/) do before/after benchmark with DXVA Checker?

Edit: apparently from what I understand support has to be enbled by NVIDIA on a game by game basis? :(

[SamuriHL]

I wouldn't stress too much about it.


NVIDIA CUVID and Intel QuickSync are deprecated, not recommended for usage, and will be removed in a future version.

However, there is some light at the end of the tunnel. A replacement for the old CUVID implementation, which had serious deficiencies, will hopefully be available at the same time, based on FFmpegs NVDEC hardware acceleration support, which solves many of the shortcomings (like missing HDR metadata, among other things), while still providing deinterlacing out of the box. And maybe even with D3D11 interop, which means that it could devlier d3d11 native frames to the renderer, and avoid the copy-back overhead.


Help is coming at some point in the future. That's LAV Filters in case it wasn't obvious.

[huhn]

resizable bar shouldn't matter for decoding.

if a new frame is done decoding it is uploaded frame by frame so it is always much smaller than the current size limitation and is by design sending "small" data.

i have a 5600x, b550, 5700 XT combo so i could test it in theory.

[Klaus1189]

How can I note this in the first post? :confused:
Same version number, ... How can user know to have the new package?

[Ejziponken]

There is a Windows update (KB5000842).

Highlights:
Updates an issue that makes high dynamic range (HDR) screens appear much darker than expected.

I wonder if this has any effect playing up video with madvr?

[ryrynz]

Not many have their desktop set up in HDR mode anyway.

[jkauff]

Not many have their desktop set up in HDR mode anyway.
The Win10 release coming next quarter, with its considerable UI changes, will encourage you to do it if you have a 4K HDR-capable monitor.

[el Filou]

What UI changes are considerable?
I only read the Insider Blog to follow what they change and it seems like it's mostly cosmetic changes like new icons and even more white space.

[huhn]

you may should add this line in 21.3.1 and newer:
Radeon RX 400 and 500 series graphics products may experience a TDR during extended periods of video playback.
this is an official known bug and user should know about this in term of video playback and nearly for sure not new.

TDR is a special term for a driver crash.

BTW. there are also pro driver for AMD: https://www.amd.com/en/support/kb/release-notes/rn-pro-win-21-q1-1

[jkauff]

What UI changes are considerable?
I only read the Insider Blog to follow what they change and it seems like it's mostly cosmetic changes like new icons and even more white space.
As I understand it, new UI elements (like the icons) will take advantage of the increased color space in HDR if it's turned on. Of course, they'll still work fine without HDR.

I believe this was the reason for adding HDR to Win10. I doubt if many people watch HDR movies and home video using just the Windows player.

[brazen1]

@Klaus1189

I've installed NVidia 465.89. The lingering HDAudio driver problem present all these years is no longer an issue. I have toggled the AVR on/off several times and Windows Audio Properties now cooperates. I have tested results that were working fine and then rebooted no less than 6 times between checks. I have played a few SDR and HDR titles briefly. I have checked YouTube audio with the AVR on/off. I've compared driver versions and some functions using notepad ++. I don't want to appear to jump the gun so if I don't report back here within the next few days, it means they're still working. Someone else should confirm if they too have been struggling and modding the install with an older HDAudio driver. (Windows Audio Properties - Stereo vs Multi-Channel dependent on AVR on/off state) I should note, I didn't use DDU. I usually save that for when this audio test fails but it hasn't this time. Now I'm afraid to DDU but in the next few days I will :eek:

*EDIT*

Well, this is ridiculous. Today I turn on my PC and the audio doesn't work properly. This after repeatedly turning my PC off/on yesterday. It's like the bug is on a 12hr timer. I regress back to HDAudio driver 388.59 which is about 4 yrs old but still works as intended.

[el Filou]

When you said you rebooted your PC and turned your AVR On/Off the first time when you thought it had been fixed, did you also turn off your TV at some point? Maybe that's what triggered the issue.

Did you notice if it behaved differently when the AVR and TV were on when you turned the PC on Vs only the TV on, or even both TV and AVR off and then turn them on after the PC?

[brazen1]

Thanks for your interest @el Filou.

I don't think this is an EDID handshake issue? I use a Harmony remote (they just announced they are discontinuing making Harmony remotes anymore btw). From a single button press all my equipment turns on and adjusts. It doesn't deviate. So, when I start my PC activity environment, or quit it, all the devices and adjustments for them react accordingly. Same with any other activity like HTPC activity.

The difference between my PC activity and my HTPC activity are very different. One I have setup to use my panel speakers instead of my AVR and it's speakers. The AVR is off. I don't want to use my AVR all the time. The other activity uses the AVR and it's speakers and the panel speakers are off (auto turned down to zero).

I know all my equipment turns OFF completely because all of it is right in front of me. Same with ON depending the activity I've selected. Of course I can manually turn things off/on too. I've been doing exactly all of this for years.

So, during test day, I turned off all my equipment for a few minutes and turned back on using different activities exactly as I always do it - multiple times, testing many different scenarios like YouTube with AVR on. YouTube with AVR off. SDR/HDR movie playback with AVR on/off. Front end GUI sounds. I challenged the driver many different ways repeatedly rebooting and turning off/on all the equipment between test and retests to make sure registry entries would stick.

It all worked fantastic and I was convinced NVidia had finally addressed this niche issue. Why it's niched, I don't know? I must be the only user that sometimes wants to use the stereo panel speakers only and other times full blown multichannel surround sound. Anyway, I turned off all my equipment as usual and called it a night. The next day when I turned my system on, nothing worked anymore. I didn't do anything differently I'd done previously the day before. The only variable was the longer time the equipment was turned off.

Here's the rub though... everything works perfectly using the old HDAudio driver so I don't see how user error or equipment error (including EDID) is responsible and can be circumvented or worked around. With the AVR on, Windows audio properties should report multichannel output. With the AVR off, it should report stereo. If Windows doesn't report the correct state of output, things don't work correctly or even at all. YouTube will have zero audio. Video will have no audio. These are challenges when using an HTPC as a desktop workstation and/or a video player depending the activity that mostly the AVR dictates. A user should simply be able to toggle an AVR off or on. Windows audio should oblige and set the output to stereo or multichannel automatically. New drivers don't. Old drivers do.

Let's assume your AVR is on right now. Right click your audio icon in the tray. Speaker setup will say the multichannel you have going. Now turn the AVR and check again. It will still say multichannel. It should say stereo. Now go to YouTube and play any video. There will be no sound coming from your panel speakers. The video might not even play and you'll get a YouTube error window in the video area.

Now turn the AVR back on. All is well. This is what new HDAudio drivers do. Older ones don't. Reboot when you think everything is ok. Better yet, turn everything off and leave it that way overnight like I did. Surprise!

[el Filou]

Here's something you may want to try.

Recently I noticed a problem in the NVIDIA driver where if I played 2 channel and then 5.1 material in succession with exclusive mode, the audio driver would fail to map the audio channels correctly with 5.1 (my speaker config is set to stsreo in Windows for Web stuff, and I rely on the media player to switch config for surround). It's like the driver was 'stuck' in sending stereo even though the audio renderer was sending multichannel (I wouldn't hear the center channel and the surrounds at all).

Now, normally each time I update the audio driver I immediately disable the energy saving timeouts in the registry because it's getting on my nerves cutting off the audio after 4 seconds, and that time I had forgot to do that because the audio driver version hadn't changed and I assumed this meant the installer didn't change anything, but in reality it reinstalled the same version and reset the settings, so I had to redo the registry changes but I didn't notice at first.

Try to change this: in regedit, open HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e96c-e325-11ce-bfc1-08002be10318}\<***put your NVIDIA High Definition audio driver entry here***>\PowerSettings and change the PerformanceIdleTime value to 00 00 00 00 then reboot (if for some reason you are using the "power savings" energy plan, change the ConservationIdleTime value instead).
This will disable the graphics card turning off the audio connection to save power.

I can't give any guarantee that this will fix anything, but in my case it fixed the issue I was having.
Note that this will prevent the AVR from turning off the amp to the speakers when there's no audio being played, which isn't a problem if you're not leaving it on without using it but something to keep in mind.

[brazen1]

Interesting. Thank you for that. Currently I'm using the old HDAudio driver from 388.59 which I replaced using 465.89 in the installer package fwiw. My PerformancIdleTime value is already 00 00 00 00. I guess because I'm using the older driver? I'm using high perf energy plan already too so my ConservationIdleTime value is 1e 00 00 00. I will compare once I install 465.89 with the current HDAudio driver and make the registry changes. Should I use the same values I reported here especially the 1e 00 00 00 since that value is working and I'm not using a power savings adjustment afaik? I'm a little concerned about your last sentence but I'll see if it affects my usage. I'll need to system image and get done with some other tests I'm doing elsewhere so this will take a bit. Thank you for this suggestion.

[el Filou]

I don't think there's a need for a whole system backup or anything like that just for this tweak, as just reinstalling another version of the audio driver resets the values or at best you can save a .reg of that key and re-import it.

My default value with 1.38.40 is 04 00 00 00 and the audio switches off after 4 seconds, so I think with your version it should switch off after 30 seconds in power saving mode, and never in high performance/balanced, but I think there was a mistake in NVIDIA inf files in old driver versions because they added those values but using a wrong type so they didn't work in practice. They fixed it at one point and that's when I nearly became crazy because the audio connection was turning off even when I was pausing playback for 4 seconds like in the bad old days of ATI's "silent stream" issue.

Here's what's in the .inf for 1.38.40:[NVHDA_D3cold.AddReg]
...
HKR,PowerSettings,ConservationIdleTime,1,04,00,00,0 ; 4 seconds for idle power management when on battery - enabled
HKR,PowerSettings,PerformanceIdleTime,1,04,00,00,00 ; 4 seconds for idle power management when on AC power - enabled
HKR,PowerSettings,IdlePowerState,1,03,00,00,00 ; go to D3 for idle power management
I don't think you need to be concerned about my last warning, as it's clear that in your current config and driver the power saving is already inactive, so it wouldn't change much. This feature has the same effect as manually muting an HDMI audio output in Windows, except it does it automatically and then brings it back up when an app plays audio again but you miss the first few samples while the HDMI connection re-establishes the stream.

[Mordred]

Long story short, I was on some version of the nVidia driver (I believe from January-ish) and when I updated both Windows and nVidia at the same time my HDR broke. I was able to get HDR, but could not solve another problem I had in DSPlayer Kodi when exiting HDR (https://www.youtube.com/watch?v=Ss0DcYJ6U2s&t=86s). I rolled back to 445.87 and everything is fine... except now I've got a new and harder to reproduce problem that seems similar to what Brazen is experiencing.

Occasionally when I turn on the receiver and TV, my audio device (listed as DENON-AVRHD) is "partially" invalidated. In a true device invalidation, like after installing a driver, I have to manually reselect the device in all my programs I want to enable audio playback as the old device settings have been automatically cleared since the device ID no longer exists. In my case, the device is still listed... it's just somehow not really valid? Foobar reports the device was invalidated, but it's still shown (and selected) and reselecting it does nothing. It does not show up in the Windows Volume Mixer, but if I right click on the Audio icon and go to "Sounds" to bring up the old Windows 7 style Sound dialog, I can switch to the playback tab and there's my DENON-AVRHD still listed as default device. I then have to right click on it, select "Test Speakers" and after about a second, the chimes start coming through my speakers. At that point I can close the dialog, and now Kodi, Foobar and anything else all work correctly again without needing any changes. A reboot also fixes it, but that's a pain in the ass.

The HTPC is on 24/7. The issue only seems to occur when the Denon (maybe the TV too?) have been turned off for at least half an hour, but that might be random variance. It happens every morning when I turn the TV on. It happens when I come back from lunch sometimes. If I turn everything off, wait 5-10 minutes and turn it back on I've never had problems. Anybody seen anything like this before?

[VBB]

Fixed Issues in this Release

 Some displays may show incorrect color levels after booting into Windows. [3285148/3287063]

Some people over at AVS had experienced this bug.

[brazen1]

@el Filou

Fwiw, I installed 466.11 today. Windows audio properties wasn't in sync with AVR off/on 100% of the time (reboots, cold starts, panel/AVR states, etc.)

I went ahead and changed PerformanceIdleTime from 04 00 00 00 to 00 00 00 00. It's still not in sync 100% of the time but I (think) things have improved. When it isn't in sync I'm now able to turn panel/AVR off/on and then it syncs. There are a lot of different variables - Turning panel/AVR on prior to booting PC, turning on after booting, toggling on/off while booted into Windows, state of panel/AVR on/off when shutdown awaiting next PC cold start, etc. None of that matters using the old HDAudio driver fwiw.

I'm going to continue trying your edit until either I gather more ammo to help isolate or I can't live with it anymore. As has happened a couple times in the past testing newer drivers, once this all parks shutdown overnight it could reveal a whole new behavior. I just wanted you to know I appreciate your efforts and sharing while I give this a go.

[el Filou]

It's always so difficult to diagnose HDMI audio as it's also linked to the GPU itself and Windows architecture.
For example since Windows 1803 I have a big popping sound every time I switch refresh rate. I never had this before so it's not the AVR, and now even if I install a really old (like from 2017) HDMI audio driver it still happens. HDMI has provisions to automatically mute the audio stream when initializing/resetting the connection to specifically avoid this kind of thing, but who knows what part of the chain fails to instruct it to do that now... and everyone says it's normal to have pops in that situation so I just gave up trying to report it.

[aron7awol]

The HTPC is on 24/7. The issue only seems to occur when the Denon (maybe the TV too?) have been turned off for at least half an hour, but that might be random variance. It happens every morning when I turn the TV on. It happens when I come back from lunch sometimes. If I turn everything off, wait 5-10 minutes and turn it back on I've never had problems. Anybody seen anything like this before?
Every so often I have an issue where my audio device stops working and shows a red x in my system tray volume icon. Rather than rebooting, I've found the quickest fix is to go into Device Manager and disable then enable NVIDIA High Definition Audio device. Not sure if this helps you, but figured I'd mention it.

[clsid]

Restarting the Windows Audio service might solve that as well.

.bat file:

@echo off
net stop audiosrv
pause
net stop AudioEndpointBuilder
pause
net start AudioEndpointBuilder
pause
net start audiosrv
pause
Right-click and run as admin.

[Calvi]

I use the windows audio driver: “High Definition Audio Device” (instead of nvidia) as I find it works 100% for my receiver through hdmi and maintains atmos correctly, switches to 3 channel etc.

Just right click “NVIDIA High Definition Audio Device” in device manager and uninstall driver. Then rescan and it will add the windows one.

I make nvcleaninstall drivers with the hdmi audio driver removed so as to avoid the nvidia included audio driver.

Every now and then I try a new version but always end up reverting.

[alleway]

I use the windows audio driver: “High Definition Audio Device” (instead of nvidia) as I find it works 100% for my receiver through hdmi and maintains atmos correctly, switches to 3 channel etc.

Just right click “NVIDIA High Definition Audio Device” in device manager and uninstall driver. Then rescan and it will add the windows one.

I make nvcleaninstall drivers with the hdmi audio driver removed so as to avoid the nvidia included audio driver.

Every now and then I try a new version but always end up reverting.


i am using hdmi audio via earc but when i try to use your method there is no sound from the windows driver.

[Calvi]

I don’t use e-arc so can’t comment on that.
Not sure why it would be any different though.

[darksen]

Hey, guys, you can disregard my previous comments as it seems the audio crackling and desync were happening because a bogus LightBulb release (See #198 (https://github.com/Tyrrrz/LightBulb/issues/198)). For some reason all the problems didn't happen with 457.51.

[VBB]

These include an updated HD Audio Driver - 1.3.38.60

[SamuriHL]

I'll install the driver later. I've been on the windows update for a while now already.

[Andy o]

Is anyone still getting the washed out colors on HDR when taking it out of full screen with NV and madVR? It's not happening here anymore, I'm on madVR 0.92.17 and MPC-HC 1.9.11 by CLSID, NV drivers above 466.47 game ready. I also recently updated to Windows 21H1 so not sure what fixed it.

Edit: never mind I just realized this is when RGB output is set to 8 bit, when I set it to 10 or 12 bit, it still washes out the image, not that it's a huge issue.

[VBB]

GeForce Hotfix Driver Version 466.55

The hotfix addresses the following issues:
[RTX 20 series][GTX 16/10 series][HDMI] 4K @ 120Hz display mode is not available from display settings [3312401]
If GPU is connected to a 4K UHD TV, system may freeze when launching a VR game [3313315]

https://nvidia.custhelp.com/app/answers/detail/a_id/5196

[huhn]

the deint issue is nearly for sure a driver issue the same happened with the release of the first crimson driver for all cards.

i reported over 1.5 years ago.

[kasper93]

AMD Radeon

Known limitations of Radeon RX 5000 and 6000 GPUs (older generations are fine, like my good old "heater" RX 480 :D):
If you are a Vega or Radeon VII user, please let me know, you could test 2 things for me. It will only take 2 minutes.

• Hardware deinterlacing is broken in every driver version -> It is poor quality when applied to interlaced video and it is not adaptive anymore, which is a NO-GO for HTPC usage.
You can check this issue yourself: Download this short MBAFF sample file (https://drive.google.com/file/d/12wO8NJbIrfa2MD4yVaA38RrBBdziCda8/view)
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:
https://upload.wikimedia.org/wikipedia/commons/f/f0/Indian_Head_interlace.gif
See here (https://forum.doom9.org/showpost.php?p=1928654&postcount=2155) for more details
• 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.
This issue can be best seen on displays which want full range 0-255, like TVs in PC Mode (PC mode for full 4:4:4/RGB support, so you do not use color subsampling like 4:2:2 or 4:2:0)
Also overriding the range for test purposes in MPC-BE (video tab -> Output range) does not take effect.

Did someone contact AMD for clarification about those issues? Deinterlacer issue is probably harder to fix if they messed up it on hardware level, who knows.

But the color levels is more interesting. In driver settings there are video presets and "cinema classic" has proper levels, ever other have wrong levels. This cannot be intentional, but at least there is workaround to select one preset that works... or well use madVR like sane person. EDIT: nvm, levels are still wrong, it is just way closer to proper image.

[Klaus1189]

https://youtu.be/1Kio8Hn8f3U

[el Filou]

Do you know if there's something interesting for video playback/processing in that one hour long presentation? :) (they could at least have added chapters... :rolleyes:)

[Klaus1189]

Sadly no, we are „smol“ niche ;)

[Klaus1189]

And also new Studio driver 462.65
Both new drivers with support for the new 3080 Ti or "Tie" just like the Rasperry Pi or: https://www.youtube.com/watch?v=bvlK_Wc_aYo :D

[SamuriHL]

No one's really stupid enough to buy that thing at 1200USD are they? I mean.....good god.

[el Filou]

Well, didn't some people buy the 3090 at even higher MSRP even though they didn't need that much VRAM?

[chros]

... the new 3080 Ti or "Tie" just like the Rasperry Pi or: https://www.youtube.com/watch?v=bvlK_Wc_aYo :D
:D Just watched this (https://youtu.be/Vtkk-_0jrPU) the other day: "... robbery... insane... waste of silicon..." :D

[SamuriHL]

Well, didn't some people buy the 3090 at even higher MSRP even though they didn't need that much VRAM?

Yes, but at least that's somewhat understandable. The TI is an overpriced 3080 that doesn't come CLOSE to filling the mid-gap between the 3080 and 3090. 12 gigs of ram vs 10 and a 1-2% speed bump doesn't exactly warrant 500 bucks difference in price.

[videoh]

I feel so bad for poor people that can't afford bleeding-edge technology. It's not fair!

And the sour grapes are off the charts!

[brazen1]

Affordable or not... Fools and their money are soon parted.

[el Filou]

Nobody's criticizing people buying expensive bleeding edge tech, it's just that there's not much bleeding edge tech in the 3080 Ti: it's like a 3080 but 71% more expensive for 17% more theoretical compute power.

[Klaus1189]

it's like a 3080 but 71% more expensive for 17% more theoretical compute power.

We have same sources :)

[huhn]

the source simple math?

[SamuriHL]

And that's the point. I don't begrudge anyone buying a 3090. I considered it myself but opted against it. I'd buy a 3080 at 700 bucks could I find one. The 3080 TI is something that shouldn't exist. It's a money grab by nVidia that provides no real value to consumers. THAT is what I don't like.

[Manni]

And also new Studio driver 462.65
Both new drivers with support for the new 3080 Ti or "Tie" just like the Rasperry Pi or: https://www.youtube.com/watch?v=bvlK_Wc_aYo :D

Apparently there is a fork in drivers. 462.65 support the 3080ti but not the 3090.

462.59 supports the 3090 but (obviously) not the 3089ti.

So if you look for the studio drivers for the 3090, it's still 42.59 that comes up, not 462.65.

The latest GRD for 3090 is 466.63. That one supports all models.

[videoh]

More GPU memory really opens the doors for performing filter chains on the GPU, rather than moving results back to the CPU for every filter in the script. It's something I call CUDASynth. It's not for poor people. Sorry!

[el Filou]

Isn't "filter chains" already what renderers like madVR are doing? How many different filters and VRAM usage are we talking about?

[alleway]

hi there, is anyone having issues with sound if connected via earc on nvidia drivers after version 466.27 if 12bpc colour is selected. i have a c9 and rtx3080 with my audio on earc. using mpc hc and madvr

[Klaus1189]

hi there, is anyone having issues with sound if connected via earc on nvidia drivers after version 466.27 if 12bpc colour is selected. i have a c9 and rtx3080 with my audio on earc. using mpc hc and madvr

What issues exactly?

[VBB]

GeForce Hotfix Driver Version 466.74

https://nvidia.custhelp.com/app/answers/detail/a_id/5200

[alleway]

What issues exactly?

no sound output if i select 12bpc in nvidia. 10bpc works fine. i tested on othe media player (eg. potplayer) same problem with the earc audio problem. not sure why

[Klaus1189]

The summary in the first two posts are getting to big to fit. So I decided to release a pdf file. What do you think about posting a link like this one in the first post?

GPU driver issues (https://drive.google.com/file/d/1ofot7mr8so6Mf-Lz9KPs8iKP4AMZh3eb/view?usp=sharing)

[pirlouy]

Will it be indexed by web crawlers ?
Your nice work deserves to be found on search engines. If you lack space, maybe you should create a new thread with the 10 first posts for you. You could remove your posts from this thread, then a moderator could close this thread.

[Klaus1189]

I don‘t know. How can it be indexed? Any things necessary?

[pirlouy]

This forum is indexed by bots, but in general, google drive files are not. That's why I think it would be better if content stayed on this forum.

[SamuriHL]

Yea well these new drivers SUCK! I just went to finally watch a movie and HDR is completely borked for me. I'm about to restart my machine. If that doesn't work I'm going to have to downgrade. NOT amused, nVidia, it was working perfectly before they screwed this up!

EDIT: A reboot fixed it. That was MESSED UP though. Wow

[huhn]

you noticed that windows just released/showed WDDM 3.0.
so expect some hick ups.

[SamuriHL]

Ah you have a valid point there. I forgot windows just did a massive update on my HTPC. I was thinking it was nVidia. Thanks, MS. Jackasses. LOL The reboot fixed it so that's good at least.

[huhn]

i have zero prove it was windows could be either or both.

but windows was in pretty hot water with some WDDM changes in the past month combined with bad user practice and the need for these bad practice...

[SamuriHL]

The timing makes perfect sense, sadly. Very possibly windows.

[Manni]

Got fed up with the driver / OS dance. My HTPC is a gaming rig / video editing workstation now, with the latest studio driver installed without testing.

I do all my film watching with a Dune Vision 4K Pro Solo (using MyMovies on an iPad as a front end), a new ATV for streaming, and an Envy for video processsing / calibration. Not a solution for everyone, but movie playback just wasn’t stable enough or reliable enough on my HTPC since I upgraded to the 3090.

I think an HTPC is still a great option if you can have a dedicated machine with the OS and driver frozen in time, but that’s not an option with my new rig as I use it primarily for work (and the occasional gaming) now.

I’ll reconsider when/if madVR is developed actively again as a software (with the release of non-time limited stable versions and not just as a test bed for Envy), but for now Envy is where things happen. HLG support came a couple of days ago for example.

[chros]

I'm happy for you guys, really, but for tons of us it's not an option :)

[Manni]

I'm happy for you guys, really, but for tons of us it's not an option :)

Yes, I know and said so :)

[el Filou]

The timing makes perfect sense, sadly. Very possibly windows.Are you on Windows Insider? The new WDDM 3.0 huhn is talking about is only available in the latest insider builds (21xxx).

[SamuriHL]

Are you on Windows Insider? The new WDDM 3.0 huhn is talking about is only available in the latest insider builds (21xxx).

That machine could be. Depends on if I pulled it out of the insider builds when the new official build was released or not. I know for a fact it just did a build update the other day so my guess is I didn't. Stupid me for not paying attention.

[SamuriHL]

These latest drivers aren't entirely stable. On my laptop with the 2080 I had a driver crash earlier just using outlook. Gotta love that.

[Shinobu]

Hello.
I use Win10 + Core i7-3770 + NvGTX960 + 8go ram + SSD + MPC-HC + Madvr as my HTPC.
It's connected to an epson 2700w.

Nevermind the settings i use in mpc nor the setting in nv driver, i got random micro stutter.

If i use software/cuvid/dvxa... in lavfilter, it's the same

No frame drop/dup/presentation in madvr information.

Thoses stutter are most of time not showing, but in slow smooth travelling it's realy distrubing.

Same in 23.976fps or 47.952fps.
I use 47.952fps with S.V.P frame double to get the best possible result and it's looking great but the stutter are even more visible (there's not more stutter but as the travelling are way smoother with S.V.P the stutter are even more distrubing)

I've logged cpu/gpu/ram/hard drive (ssd) usage and no bottleneck too and madvr control pannel never show frame drop/dup

Any suggestions ?

Thanks a lot ^^

[Klaus1189]

Perhaps it also helps you with your card:
• If you have a Nvidia 20xx/30xx video card and you encounter micro stutter while using madVR without actually dropping frames, please try the following:
• In the Nvidia control panel, go to Manage 3D Settings, scroll all the way down and set Vertical Sync to 'On'. You can do this either globally or just for the media player exe.
• In the madVR settings, go to rendering -> general settings, and uncheck 'enable automatic fullscreen exclusive mode'
• In the madVR settings, go to rendering -> windowed mode settings, and set 'how many video frames shall be presented in advance' to 1 or a maximum of 3

[jkauff]

I use 47.952fps with S.V.P frame double to get the best possible result and it's looking great but the stutter are even more visible (there's not more stutter but as the travelling are way smoother with S.V.P the stutter are even more disturbing)

I've logged cpu/gpu/ram/hard drive (ssd) usage and no bottleneck too and madvr control panel never show frame drop/dup

Any suggestions ?

It's been a couple of years since I played around with SVP, but at that time the GPU demands for certain features were pretty high. Maybe your older GTX card is not up to the task.

[Shinobu]

@Klaus1189
Already tryied that but no luck

@jkauff
As i said, i have the stutter without SVP, SVP only make them more visible as the motions are way smoother with it

[Klaus1189]

Perhaps if you add your player.exe in Nvidia driver and change power management? What entries can you choose from with your GPU?

[Shinobu]

A disabled all power management from this computer (control panel + NV driver)

[Klaus1189]

http://nvidia.s3.amazonaws.com/aid_3130/adaptive_performance.jpg

[Shinobu]

As a said already done ^^

[Klaus1189]

Max performance does not help?

[Shinobu]

not at all

[clsid]

Press Ctrl+J to display the madVR statistics overlay. Check if the rendertime does not exceed the frame time.

Make a screenshot. Upload it to external image host, then copy link here.

[el Filou]

I think it would show in drop/repeat/present stats if it went above frame time.

Have you tried disabling fullscreen optimisations in the player's .exe properties and using fullscreen exclusive in madVR? Some people say FSE is not really exclusive anymore but some other have said it gives better results for them, so worth a try.

[Shinobu]

@clsid
Here's the caps

Without SVP
http://yatoshicom.free.fr/SVPoff.jpg

With SVP
http://yatoshicom.free.fr/SVPon.jpg

I'm using a custom resolution (cru) of 47.952fps even for 23.976fps, because the native 23.976fps mode in NVidia driver sux (got a repeated frame about all 5 minutes with it)
Using MPC-HC 1.9.13 and lastest madvr, lastest windows, lastest nv driver .... but i have those micro stutter for month, i tried all i could think about, but no luck T_T

@el Filou
Already tryied but no luck

Thanks all for try to help ^^

[clsid]

Your present queue has size 3.
Set "how many frames shall be presented in advance" to 1 in madVR.

[Shinobu]

already tested and same result T_T

[el Filou]

Radeon GCN 1-3 moved to legacy support: https://www.amd.com/en/support/kb/faq/gpu-630

(some R 400 and R 500 models use GCN 3 and are not in the list, but they are OEM only models, so maybe they're not being considered for this note and are out of support by the OEMs anyway? It's not clear)

My HD 7870 had quite a long support life! :)Nvidia GeForce 471.11 WHQL driver released, new driver branch.Issues: DPC latency is higher when color mode is set to 8-bit color compared to 10-bit color. [3316424]Oh wow.

[ashlar42]

Oh wow.What's DPC latency?

[huhn]

very simplified and wrong:
is the time to call a device driver to do something.

if it is "high" nothing usually happens there is simply no limited to how high it could get and here is where the problems can start.

a really really high value can create audio issue (cracking) to displaying issues (delayed frames) and such.

i got 20k ms not us spikes with MPDN back in the days a number below 1000 us should be totally save

[ryrynz]

What's DPC latency?

Literally the second result in Google.. c'mon man.
https://www.reddit.com/r/windows/comments/11itqe/dpc_latency_and_why_you_should_care/

[el Filou]

Does anyone have any updates on DXVA2 deinterlacing support on recent AMD cards? Is it still broken? Have there been reports with the 6000 series cards (IIRC only owners of RX 5700 gave reports)?

With nevcairiel possibly removing CUVID in a future LAV version and madVR support of D3D11 VP probably never happening, I'm considering upgrading to an AMD card instead of NVIDIA to keep best quality for 1080i (when prices become reasonable again), but it would be no use if their deinterlacing is still broken in DXVA2.

EDIT: Oh, I forgot about Intel. Maybe when they release their 'high-performance' dGPU. Does Intel work good in DXVA2 deinterlacing with madVR?

[huhn]

in the past intel worked very good.

5700 XT deint is still utterly broken currently it's just weaving for the most part with madVR this is the worse it ever has been.

[Grimsdyke]

I am thinking about building a new HTPC with the upcoming AMD 5700G or 5700GE. Is refresh rate adjusting with CRU and/or MadVR working on AMD right now ? Thanks.

[huhn]

yes should work else you can just use the driver.

beware they are vega with most likely dated decoder.

[NoTechi]

5700 XT deint is still utterly broken currently it's just weaving for the most part with madVR this is the worse it ever has been.

As a I own a 5700XT what would be your advice for settings (madvr/lav,..) to mitigate the broken deint (beside buying a different gpu :p)

NoTechi

[huhn]

buy a new GPU.

lavfilter with copyback decoder or software with yadif.

[Grimsdyke]

beware they are vega with most likely dated decoder.

Yes, I know - but I am hoping to just upgrade the system then with a RDNA2 APU (hopefully also with PCI 4.0-support) on AM4 sometime in late 2022 or 23.
Assumed that AMD keeps supporting AM4 for a few more years.

[NoTechi]

buy a new GPU.

lavfilter with copyback decoder or software with yadif.

:thanks:

[huhn]

Yes, I know - but I am hoping to just upgrade the system then with a RDNA2 APU (hopefully also with PCI 4.0-support) on AM4 sometime in late 2022 or 23.
Assumed that AMD keeps supporting AM4 for a few more years.

AM4 is dead this should be the last series of CPU for it.
maybe a refresh. not saying that there isn't going to be a RDNA2 APU with zen 3 but that's the best you can hope for and the CPU just like with intel is over kill.

AM5 with drr5 is pretty much confirmed.

[SoySauceWDF]

I've got a weird issue using madvr that's been happening for a while. If I pause or sometimes randomly during playback, the render queue drops to 3-4/8 and I start getting dropped frames. It fills up if I backup a little bit and start playing again. I've messed with queue sizes, vsync, present frames in advance, etc, almost every setting I could think of.
Running windowed with D3D11, output in sdr bt.2020 and 10 bit, display set to 12 bit. Happened on both my 2080 ti and 3090, latest drivers. Wondering if its an issue with nvidia outputting 12 bit?

[VBB]

https://nvidia.custhelp.com/app/answers/detail/a_id/5212?linkId=100000052818903

GeForce Hotfix display driver version 471.22 is based on our latest Game Ready Driver 471.11.

The hotfix addresses the following issue:

Doom Eternal may crash to desktop during gameplay [3331270]
League of Legends [Tencent] may fail to launch [200744747]
Mouse cursor color may shift when connected to certain DSC monitors in HDR mode [200741796]
[HDMI 2.1][8K] HDMI audio playback may become distorted after changing display modes [3268312]
Some displays screen resolution limited to 640x480 after driver update [3330750]

[SamuriHL]

So wish I had a video card to use it on. Thanks, nVidia. :rolleyes:

[Klaus1189]

Anybody else has trouble with new Nvidia driver when using 120 Hz refresh rate? Aspect ratio ...

[SamuriHL]

nVidia RMA'd my 2070. There's hope yet that I can get my HTPC working again.

What kind of problems? I have a GSync screen on my Alienware with my 2080. Not seeing any issues at 144hz.

[nevcairiel]

Fine at 144Hz GSYNC here as well, or 120Hz 4K on the TV.

[huhn]

240 freesync and 120/144 are working as usual.

[Asmodian]

Anybody else has trouble with new Nvidia driver when using 120 Hz refresh rate? Aspect ratio ...

Do you have "Adjust desktop size and position" set to perform scaling on GPU? If I do it messes up the aspect ratio even if I set it to no scaling, I have to set it to perform scaling on Display.

It works normally at 60 Hz. :p

[Klaus1189]

Do you have "Adjust desktop size and position" set to perform scaling on GPU? If I do it messes up the aspect ratio even if I set it to no scaling, I have to set it to perform scaling on Display.

It works normally at 60 Hz. :p

Thank you. That is exactly what I had to do. But why is this on 100Hz and higher?

[Klaus1189]

I don't get it. I played around with these settings and now it is also fine with "GPU" selected. Very strange.

EDIT: never mind, it ist squished a bit then.

[Shinobu]

Hello.
I use Win10 + Core i7-3770 + NvGTX960 + 8go ram + SSD + MPC-HC + Madvr as my HTPC.
It's connected to an epson 2700w.

Nevermind the settings i use in mpc nor the setting in nv driver, i got random micro stutter.

If i use software/cuvid/dvxa... in lavfilter, it's the same

No frame drop/dup/presentation in madvr information.

Thoses stutter are most of time not showing, but in slow smooth travelling it's realy distrubing.

Same in 23.976fps or 47.952fps.
I use 47.952fps with S.V.P frame double to get the best possible result and it's looking great but the stutter are even more visible (there's not more stutter but as the travelling are way smoother with S.V.P the stutter are even more distrubing)

I've logged cpu/gpu/ram/hard drive (ssd) usage and no bottleneck too and madvr control pannel never show frame drop/dup

Any suggestions ?

Thanks a lot ^^

Found a solution !!!
Hope it could help other user.
I tryied tons of settings, drivers version, cpu/gpu clock, projector setting, full windows installation (2 differents versions).... nothing was working.
Then i tryied to "kill" all background process one by one to try to found a culprit..... and i found the culprit, it's the "NVDisplay.Container.exe"

To properly kill this process the only way i found was to renamme the exe in "NVDisplay.Container.exe.old", then rename the Display.NvContainer folder in Display.NvContainer.old to avoid the NVDisplay.Container.exe to self restaure.

Of course i don't have accès to nv control pannel anymore, but at least not a single micro stutter in 5 full movies ^^

So if you have a dedicated pc for your movies , give it a try ^^

[Calvi]

You can just disable the service - NVIDIA Display Container LS.

[doffen]

What does this service do?

[ryrynz]

What does this service do?Basically telemetry. You should report this to Nvidia they've had problems with this service before affecting system performance.

[el Filou]

Well, thanks for the idea @Shinobu! I've been having small hiccups (like a few frames) for quite some time but not showing any pattern wrt format or container, and it was totally random: if I skipped backwards the drop didn't happen at the same timestamp.
The difference is my drops were showing in the stats, as I could see the decoding queue of madVR get lower, so one workaround I had found was to set it to 32 but it was causing other problems, but after seeing your message I tried disabling the NVIDIA service and whadayaknow, no drops anymore! :eek:

I have no idea how I would report this as I can't even reproduce it deterministically, it doesn't even happen on all videos.

[Shinobu]

Same here, it was realy random.
Cool that it helped you ^^

[Tiraga]

Hi. I follow this thread a long time now but got a bit confused recently about which drivers to us for my different setups. Maybe you can help me.

1. Setup: LG OLED 65B8 Kodi DS-Player with MADVR Beta 113 on a GTX 1650 using driver 456.38 if i get it right there is no benefit in a newer or older driver or am i’am wrong? I still need the old audiodriver with this one?

2. Setup: JVC DLA-X500 Kodi DS-Player with MADVR Beta 113 on a GT1030 using driver 385.28 at the moment and wonder if i could use for example 451.48 to get the better 23p handling or should i stay at my current driver?

What Windows Version is the best to use currently?

[el Filou]

I don't use HDR but seeing as nobody has answered your question...

1. You only need an old HDMI audio driver if you have issues with a newer one, like if you switch between outputting to a display in stereo and an AVR in multichannel or other stuff like that.
2. Old video drivers are only needed if you either need 3D (reportedly there are ways to hack newer drivers but I don't follow that) or need the old HDR switching behaviour.
3. Windows 10 20H1(2004)/20H2/21H1 is fine (it's all the same version architecturally).

Anyone please correct me if I said something wrong.

[aufkrawall]

Same here, it was realy random.
Cool that it helped you ^^
There are, once again, reports that _NvTopps.dll, which is loaded by NVDisplay.Container.exe, causes weird write to disk activities by that process. Maybe this is causing your issue and it's enough to just delete this particular DLL (there are also telemetry and auto driver profile updater DLLs, which one might find expendable too...).

[el Filou]

Once again NVIDIA released security fixes in some driver version, and only documented them in the release notes of the next driver released 3 weeks later, I wish they'd stop doing that. :mad:

[SamuriHL]

And I wish their stupid 2070 cards would stop dying on me but here we are. Got my replacement. Worked for 2 weeks. Dead...again. SIGH

[huhn]

this sounds more like your PSU is on a killing spree.

[Asmodian]

Have you monitored your Memory Junction Temperature, as reported by HWiNFO? Some OEMs are not cooling the memory well enough. :(

Edit: Oops, that is only on the GDDR6X GPUs, it shouldn't be an issue on the 3070s (or 2070!).

These GPUs do have high power spikes, so power supplies need to be more robust, but I am still thinking 3000 series. :o

[SamuriHL]

I have an evga gold 800 watt PSU so that shouldn't be the issue. However at this point anything is possible. I pull the card and the system runs completely fine. The same exact issue happened 3 times now....watching a movie with madvr, I get graphics glitches, and the machine hard locks. After that it no workie until I pull the card. The first time was in a different machine right after I got the card and they replaced it. The second time was a little over a month ago and they replaced it again. And it just did it again a couple nights ago. I've not spoken to nVidia but I can't think they're going to accept yet another RMA at this point. Who knows. I'm annoyed enough about it that I don't even want to deal with it at the moment. I've got other real world things going on at the moment that require more attention unfortunately.

[SamuriHL]

And to top it off, since this is the driver thread, I can't get the 9900k Intel GPU to work in HDR. It doesn't recognize that my TV is HDR compliant and windows doesn't show the option to enable HDR. Just awesome.

[ashlar42]

And to top it off, since this is the driver thread, I can't get the 9900k Intel GPU to work in HDR. It doesn't recognize that my TV is HDR compliant and windows doesn't show the option to enable HDR. Just awesome.
Wow... a virtual hug for you. I shudder at reading about all your problems. When my HTPC doesn't work properly I feel bad throughout the day until I solve stuff.

[ryrynz]

this sounds more like your PSU is on a killing spree.Yeah that was my thoughts too.. bit rough. Feel for u bro.

[SamuriHL]

I'll get it worked out eventually. Right now I don't have time or money to mess with it. I'm dropping a pretty coin on a new ductless mini split HVAC system for the house and I'm trying to get everything ready for the installers. A month from now when that's (hopefully) done, I'll get back to dealing with this irritating problem. I'll use the SHIELD for now. At least the machine is running as my plex server for now. I may re-setup my bedroom's SHIELD as an alternative plex server until this HTPC nightmare is fixed. I rule out nothing at this point, though. The PSU would break my heart as that thing's been ROCK solid since I got it. However, ANY issue with components right now sucks because pretty much nothing is easy to get. I'd love to upgrade to a 3080, but, ummmmm, yea, I'm not paying scalping prices. Especially right now.

[ryrynz]

I bought a MSI Trident 3 with a 3060 for MadVR and it's slightly faster than the 1080 Ryzen 7 system I had before. Less than half the size of my previous PC. Have decided to switch to Smooth Motion and 60Hz to improve panning scenes, was hoping to have a 120Hz set when I did this but that'll come eventually. A bit sad about the state of madVR right now with no real updates to speak of. Was getting some stuttering when jumping through films but I think the sleep options help here need to look into it, did need to drop frames ahead to 1 like everyone else to have things playing smoothly. Updated to 20H2 as well and operating in HDR which 1809 couldn't do.

[aquanash]

Was getting some stuttering when jumping through films but I think the sleep options help here need to look into it, did need to drop frames ahead to 1 like everyone else to have things playing smoothly.

After upgrading from nvidia 10 to 30 series, I was having occasional micro stuttering issues (with v-sync forced on) and tried many different combinations of "windowed mode" frames ahead and gpu flush settings without any luck. In most cases the issue was even worse. The thing I finally found to fix all my issues was disabling Multiplane Overlay Support (MPO) in the Windows registry. HDR only works in full screen with MPO disabled, but that's ok with me and matches the behavior I had with the 10 series card (MPO is not supported and disabled pre-20 series).

With MPO disabled, I can run madVR with the default rendering settings and all default nvidia driver settings on my 30 series card without any micro stuttering or other issues. I'm running 21H1 with latest patches and the latest nvidia driver (471.68). I also used DDU and NVCleanstall to install only the base graphics driver without telemetry and other bloat that others have reported may cause micro stuttering, but MPO was the real culprit in my case.

Here's the nvida support site link with registry patches to disable/enable MPO (make sure to reboot after changing the registry setting):

https://nvidia.custhelp.com/app/answers/detail/a_id/5157

[ryrynz]

Luckily I haven't had to do that. Things are working perfectly here with a small change to flush settings and keeping frames rendered in advance to 1. Quite impressed with getting almost the same results as the 1080 with the 3060 with barely any noise. I keep the card limited to about 40% load to achieve this, things should improve a touch I think after I upgrade to faster dual channel RAM.

[aufkrawall]

did need to drop frames ahead to 1 like everyone else to have things playing smoothly.
Works fine with default prerender of 8 here with MPO off on RTX 3060. The MPO fix is now more ore less promised for next driver branch...

[ryrynz]

Works fine with default prerender of 8 here with MPO off on RTX 3060. The MPO fix is now more ore less promised for next driver branch...Haven't noticed any obvious problems with it enabled, was a couple of areas where things felt slightly less smooth while watching last night so I might turn it off just to see if anything improves until the new branch is released but overall very happy with the way things are looking so far

[VictorLS]

Guys with powerfull computers - test please my record of TURKSAT_8K channel from 42e SAT https://www.flysat.com/8k.php 20210828_0434 FTS-12605V CrazyScan.TS (1 GB, 1min13s) https://transfiles.ru/jqn13 - is audio and video synced until the end of file (played smoothly)? I get only ~1min well audio then silence or stuttering sound (because audio plays faster than video) MPC MPEG Splitter some better than LAV Splitter - old records from that 8K channel are played with well audio in many minutes...

[huhn]

the file plays fine with nvidia hardware decode even on old pascal cards.

software decoding should be ignore for 8k just the transfer to the GPU is to much.

[VictorLS]

huhn
Thanks (I guess Pascal-based beginning on GTX1050Ti with minimum 4GB RAM), so my GTX750 GM206 Maxwell-based videocard can't hardware decoding of 8K I used MPCVideoDec_skip_non_I-frames.7z (7,2 МБ) https://disk.yandex.ru/d/ZBA-K2-6UUV4TQ and with it I watched slideshow with normal audio directly from SAT in many minutes but now it isn't work - it seems bandwidth has increased - I'll check it.

[webbo]

Where's the "summary list" with the drivers - that used to be initially in the OP? Did it got moved?
Thank you

[VBB]

Klaus put it in a PDF. Link is at the bottom of the first post.

[NoTechi]

Adrenalin 21.9.1 released (https://www.amd.com/en/support/kb/release-notes/rn-rad-win-21-9-1)

NoTechi

[huhn]

AMD Smart Access Memory on Radeon™ RX 5000 Series Graphics
you didn't is already been working for about a year great you noticed.

[SamuriHL]

I've been testing it. Works fine.

[ryrynz]

I've been testing it. Works fine.[emoji23] It is RTM after all so you'd expect that. And yes all good here too.

[KrazyLurt]

[emoji23] It is RTM after all so you'd expect that. And yes all good here too.

I've been testing it. Works fine.

Me too, been testing different builds leading up to the release.
One issue for me is that madVR is reporting 8-bit even when 10 or 12-bit is selected in nvidia controlpanel. How is it for you?

Using RTX 3080.

[aquanash]

Me too, been testing different builds leading up to the release.
One issue for me is that madVR is reporting 8-bit even when 10 or 12-bit is selected in nvidia controlpanel. How is it for you?

Using RTX 3080.

Please see my findings in the main madVR thread: https://forum.doom9.org/showthread.php?p=1954008#post1954008

In my case pressing alt-tab in Windows 11 breaks 10bit until I reboot. I posted a registry workaround to disable the new task switcher UI that seems to be the culprit. I wonder if you may be running into the same issue. Please test by rebooting then starting playback before even pressing alt-tab a single time. If 10bit is now working, press alt-tab to switch to another window, then press it again to switch back and check if it went back to 8bit.

[KrazyLurt]

Please see my findings in the main madVR thread: https://forum.doom9.org/showthread.php?p=1954008#post1954008

In my case pressing alt-tab in Windows 11 breaks 10bit until I reboot. I posted a registry workaround to disable the new task switcher UI that seems to be the culprit. I wonder if you may be running into the same issue. Please test by rebooting then starting playback before even pressing alt-tab a single time. If 10bit is now working, press alt-tab to switch to another window, then press it again to switch back and check if it went back to 8bit.
I got it working, and I think I know why. Like a poster in the MadVR thread I removed a display device in MadVR settings. That was my main 8bit monitor that I don’t use when using MadVR.

So know I have only my Oled and my reciever as devices in MadVR.

[maxkolonko123]

So what drivers are recommended to use with madvr? I'm still 1060gpu though

[ryrynz]

So what drivers are recommended to use with madvr? I'm still 1060gpu thoughMost just use the latest unless you have specific use case that isn't working for example custom refresh rates. I'm not aware of any broken functionality with madVR with the latest drivers and that's really what we care about most.

[SamuriHL]

Good luck all :)

[ashlar42]

No more Standard driver release, only DCH release is available.
What does this mean?

[SamuriHL]

It's just how they package the drivers. They've been moving away from the standard packaging for a while so this is not a surprising move.

[huhn]

the DCH drtiver isn't shipped with the control panel and the windows store version is needed with that driver which creates very odd issues like a very laggy control panel and such.

[ashlar42]

the DCH drtiver isn't shipped with the control panel and the windows store version is needed with that driver which creates very odd issues like a very laggy control panel and such.
Oh, wow. And to think that the current control panel was such a speedy beast... they clearly had margins to slow it down.

NOT

[SamuriHL]

LOL yea. It's a good time. These changes are something MS has been pushing for not nVidia.

[el Filou]

One thing I find curious is on my old Radeon, after I did a clean install of the last ever driver for it (21.5.2 "Legacy"), both the Radeon software and GPU-Z say the driver is now DCH, but I did not have to open the Store to install the control panel, and it doesn't appear in the installed Store apps either.
Has AMD found a 'loophole' that allows to sideload their control panel with DCH drivers?

[claw]

https://www.nvidia.com/en-us/geforce/news/back-4-blood-game-ready-driver/
https://www.nvidia.com/download/driverResults.aspx/181095/en-us

Nvidia GeForce 496.13 WHQL driver released, new R495 driver branch, no longer supports Nvidia Kepler GPUs. No more Standard driver release, only DCH release is available.

From the EVGA user forum, not confirmed...

An important fact about this driver is that Windows 8.1/8/7 are no longer supported with this driver. If you have those old operating systems this driver will not work for you.

--------------------------------------------------------------------------------------------------------------

Updated Win11, RTSS, and the nVidia driver, rebooted, and FFXIV capped out at 24 FPS.

Turns out, the power limit had been set to the minimum. Dragging the slider back in Precision X1 and applying fixed it. Weirdly, the temp limit seems a bit lower than it used to be while linked to the power slider at 105% but I'm not sure if that means anything.

[huhn]

LOL yea. It's a good time. These changes are something MS has been pushing for not nVidia.

nvidia followed they didn't had to.
amd doesn't do it even if they use an DCH driver you don't have to seperate the control panel. on one hand the AMD driver is more like geforce experience and you can bet nvidia nor AMD is not going to remove that from the driver on the other hand it can't even change the refreshrate on AMD side.

removing kepler support is a bad move right now with the shortage but it's not even remotely as bad as removing GCN 1-2 support by amd month ago before fidelityFX "super becubic".

[SamuriHL]

https://nvidia.custhelp.com/app/answers/detail/a_id/4777/~/nvidia-dch%2Fstandard-display-drivers-for-windows-10-faq

Just for anyone interested in nVidia's official stance on this nonsense.

[SamuriHL]

nvidia followed they didn't had to.


No I know. I'm simply saying MS has been "encouraging" GPU driver mfg's down this path. nVidia could have flipped them the one finger salute but they've chosen to push this path at MS' behest. God only knows why. I'm sure there's some kind of monetary incentive. I've been using the DCH drivers on my laptop since I got it with no real ill impact. I know others have had performance issues with the control panel. Maybe it's all fixed now. :D LMAO

[nevcairiel]

removing kepler support is a bad move right now with the shortage

Kepler is so old, new drivers don't really benefit it anymore anyway. Its not like old hardware instantly stops working now, even if the internet wants you to believe that.
You barely hear of anyone even running a 600 or 700 card anymore these days.

[huhn]

statistics say soemthing else:
https://store.steampowered.com/hwsurvey
the immortal 750 TI.

i wouldn't even blink about that if there wouldn't be a new OS right now and a stortage.

in general the driver support time is outstanding.

[nevcairiel]

statistics say soemthing else:
https://store.steampowered.com/hwsurvey
the immortal 750 TI.

750 and 750 Ti is Maxwell. So lets just skip that one, since its still supported.

You really need to go to the bottom of the list to find anything actually Kepler, even if you add them all up you probably won't even break 2%.

[huhn]

the 750 TI is are both. GM206, GM107 and GK106. but it is still listed so it doesn't matter as you said.

2-3 % is a lot.

this WHQL driver for win 11 would have been nice plus a couple more upcomming fixes just for win 11.

[Asmodian]

Kepler is over 9 years old now... that is a pretty good run for driver support. :p

[huhn]

as said outstanding
700 series kepler refresh is 8 years which is still great.

and my win 11 argument killed itself by forcing TPM 2.0 i was under the impression they where backing of of that. you really don't need driver for an OS you mostlikely can't install anyway even on some new machines.

[nevcairiel]

You also need UEFI without CSM and Secure Boot, did NVIDIA even add UEFI support to those old cards? :D

[huhn]

yes "they" did. https://www.hardwareluxx.de/community/threads/how-to-uefi-gop-bei-kepler-gpus-nachr%C3%BCsten.1044351/

does microsoft really think the AVG user can enable secure boot, TPM or worse update the bios...

[ryrynz]

as said outstanding

700 series kepler refresh is 8 years which is still great.



and my win 11 argument killed itself by forcing TPM 2.0 i was under the impression they where backing of of that. you really don't need driver for an OS you mostlikely can't install anyway even on some new machines.

You can run it with TPM 1.2. I do think any system running older hardware has limited benefit by installing W11 through. Overall I think everything is fine in terms of support from major manufacturers here. I was expecting Kepler removal from a new driver about a year ago, so yes very good support.

[huhn]

they double down on it they state TPM 2.0 not 1.2 anymore while it is still possible to install win 11 even on system without TPM that's now the official requirement.

[SamuriHL]

yes "they" did. https://www.hardwareluxx.de/community/threads/how-to-uefi-gop-bei-kepler-gpus-nachr%C3%BCsten.1044351/

does microsoft really think the AVG user can enable secure boot, TPM or worse update the bios...

No. They think they can push sales of new machines. They are mistaken, of course. I upgraded my Alienware laptop to W11 but I have a 2080 in it. Maybe look on the bright side...with nVidia only having to focus on "modern" GPU's now, their drivers will TOTALLY improve and become rock hard stable. :rolleyes: :D

[nevcairiel]

they double down on it they state TPM 2.0 not 1.2 anymore while it is still possible to install win 11 even on system without TPM that's now the official requirement.

Any system with a supported CPU should have fTPM support (thats just Ryzen 2000+ and Intel 8th Series and up), unless your mainboard is totally stupid. Older CPUs then that are not on the compatibility list anyway, so TPM is the least of your problem.

[huhn]

they are totally stupid.
https://www.dell.com/support/kbdoc/de-de/000132583/dell-systems-die-von-tpm-version-1-2-auf-2-0-aktualisiert-werden-koennen

and well the new bios version are adding windows 11 support if that's just TPM on by default or something more is somehting i can't judge but creating a new bios with "adds windows 11 support" is not something they should add for fun.

the TPM 1.2 thing is an issue because of that people where getting add cards/chips for somewhat older machines like zen 1 and now they are worthless.

[ryrynz]

become rock hard stable. :rolleyes: :D

Wow.:p

[Asmodian]

and well the new bios version are adding windows 11 support if that's just TPM on by default or something more is somehting i can't judge but creating a new bios with "adds windows 11 support" is not something they should add for fun.

I think this is just the defaults for CSM, Secure Boot, and TPM. I have a new X570 board and Asus did an update for Win11 that changed all those default settings. They used to all be wrong for Win11. The changelog even says:
1. Support Windows 11 by default, no settings changes required in the UEFI BIOS.

But of course they might have changed something else too.

[ashlar42]

the TPM 1.2 thing is an issue because of that people where getting add cards/chips for somewhat older machines like zen 1 and now they are worthless.

To be honest, people were doing that before Windows 11 had been released. While specifications were still up in the air. Why were they doing this? Because they were afraid of a shortage of components, maybe? So they wanted to be "smarter" than the average consumer?

All this to abandon an OS that has guaranteed support for a minimum of another 4 years (and I wouldn't be surprised if that gets extended).

I am not overly concerned about that behavior. That's basically on them if they have bought something that is worthless. If you want to be the earliest of early adopters... well, risk is on you, in my opinion.

[clsid]

The TPM/CPU requirement can easily be bypassed (for now). I have Win11 running inside VirtualBox on a 2nd gen i7. Even Windows updates are coming in.

But it is understandable that MS only offers official "support" for modern hardware. It is usually old hardware/driver that is giving troubles.

By the time Win10 goes EOL, the currently supported hardware is already 5-8 years old already.

[el Filou]

Does this new 495 branch support new Windows 11 features (WDDM) that the last 472.12 did not? Because that one already officially supported Windows 11 and also still supported Kepler.

[oldpainlesskodi]

Think I'll be staying on Win10 with AMD for a bit then, or buy a dedicated Media Player with DV support etc.

[Balling]

Nobody needs no TPM for windows 11. That is BS. This script workarounds the tempertrantum from Micro. https://gist.github.com/AveYo/c74dc774a8fb81a332b5d65613187b15

As for Secure Boot, it is a must have feature, if you are signing the kernel and its modules yourself. Also UEFI means no grub is needed, kernel can load natively in 4K resolution (grub also supports 4K now, but on some destributives it is commented out). For microsoft it also means GPT, since Microsoft thought that they do not need to follow the UEFI spec that allows MBR too. At least NTFS works usually.

[distobj]

Most just use the latest unless you have specific use case that isn't working for example custom refresh rates. I'm not aware of any broken functionality with madVR with the latest drivers and that's really what we care about most.

I've been using 442.74 since it came out. Any recent driver update, including the latest, displays washed out colours despite properly switching to HDR on my LG OLED. I'm even running Win10 21H1.

Suggestions?

[ryrynz]

I've been using 442.74 since it came out. Any recent driver update, including the latest, displays washed out colours despite properly switching to HDR on my LG OLED. I'm even running Win10 21H1.



Suggestions?Aside from looking to see whether there's extra devices that have been loaded in MadVR that might be affecting this and changing output bitrate in the graphics settings and trying an earlier driver nothing else springs to mind. Anyone else have these issues?

[Chouonsoku]

Just to verify, is everyone else seeing only 8 bpc as an option for NVIDIA GPUs under Windows 11? Using driver 496.13 on Windows 11 build 22000.258 with a GTX 1070 Ti. Had options for both 10 bpc and 12 bpc in Windows 10.

[brazen1]

12bit using W11 here. Did you set it for resolutions 30Hz and under?

[Chouonsoku]

12bit using W11 here. Did you set it for resolutions 30Hz and under?

I set the TV to 23 Hz and only 8 bpc was offered, it's the same for other frequencies. I tried creating a custom resolution but nothing gives me 10 or 12 bpc.

https://i.imgur.com/270YR95.png

What GPU are you using? Wonder if it's a weird query bug or something because I'm on an HDMI 2.0 device.

[Asmodian]

What GPU are you using? Wonder if it's a weird query bug or something because I'm on an HDMI 2.0 device.

That does seem possible, but weird. Have you tried deleting all your displays, and letting it be re-detected, using CRU?

Custom resolutions do not offer >8 bit modes. :(

https://hosting.photobucket.com/images/dd496/asmodian3/Nvidia_10-bit.png?width=960&height=720&fit=bounds

[Chouonsoku]

That does seem possible, but weird. Have you tried deleting all your displays, and letting it be re-detected, using CRU?


Is that as easy as opening CRU, hitting delete next to each display in the drop down, saving and then running restart64.exe? If so, no dice. :( Might try a clean install of the drivers next.

Edit: Clean installed the latest studio driver with DDU, no change.

[nsnhd]

Something has changed in windows 10, FSW mode is creating ghosting and artifacts in 3D frame packing and FSE has to be used with mpc-hc/madVR.

[Balling]

You need to set YCbCr obviously.

[Chouonsoku]

You need to set YCbCr obviously.

That actually does work in Windows 11 (thank you!) but that doesn't exactly fix the problem I'm seeing. HDMI 2.0 has more than enough bandwidth for 3840x2160p @ 12-bit RGB @ 24 Hz. Forcing chroma subsampling to get 10/12 bpc should not be necessary.

https://images.idgesg.net/images/article/2017/12/formatdataratetable-100743742-large.jpg

Again, doing this works fine in Windows 10.

Edit: Hah, I fixed it. Deep color wasn't enabled on the HDMI input, swapping that on enabled 12 bpc RGB. ��

[huhn]

without the "deep color"(or what ever they name it) your TV runs in a compatible mode where it is actually 1.4.

this problem just bandwidth issue.

[SamuriHL]

Now what the hell did they break...er, I mean, oh good! :D

[ryrynz]

Now what the hell did they break...er, I mean, oh good! :DThere's always something. Chances are the majority of breaking happened with the new branch so if you were running the previous set these *should* be good. As long as it's not MadVR that's broken.. Anyway worry about getting your system sorted before u worry about the drivers for it [emoji39]

[SamuriHL]

Oh that system is dead. Not to be resurrected any time soon. But I still have my laptop with the 2080 in it so I do care about drivers. I didn't have any issues that I saw with the last driver, but, then I'm not using madvr at the moment. I've switched to playing with JRVR which is still in its infancy but has a lot of potential.

[huhn]

we also got new AMD driver for the same reason:
https://www.amd.com/en/support/kb/release-notes/rn-rad-win-21-10-3

[ryrynz]

I'm not using madvr at the moment.

Blasphemy [emoji50]

[Manni]

Blasphemy [emoji50]

I’m not using madVR at the moment either :)

Too many issues with drivers / OS versions, especially with HDR, I don’t have the time to debug/maintain and now that my HTPC isn’t just a HTPC but a video editing and gaming machine, I use a Dune 4K vision pro solo or an Oppo 203 clone as a player.

I use MyMovies on my iPad as a movie wall, select the film there, choose which player and the title is played automagically. No OS or drivers issue. The picture quality is the basically same on my 88” diag 16/9 screen as I use source direct on both and Envy as a processor, and with the new calibration options only available on Envy, that sealed the fate of madVR on the HTPC for now.

Obviously not an option for everyone, but don’t be surprised if You don’t see me around as often as I used to be. I might come back if/when there is a working version of madVR with latest OS/drivers, but for now I’m going to take a break.

[ryrynz]

Manni: MADVR was so 2010, so I got an Envy. Holiday profile activated [emoji41] Be Envy-ous.

[SamuriHL]

I wish. Can't afford one so I'm stuck with my laptop and streaming devices for now. I can't even afford to rebuild my htpc. Then again I should get cyberpower to pay for it since the battery dying in my ups is what destroyed the htpc. Sigh

Sent from my SM-G998U1 using Tapatalk

[ashlar42]

Then again I should get cyberpower to pay for it since the battery dying in my ups is what destroyed the htpc. Sigh
Since I have a CyberPower UPS for my main workstation I read these lines with dread... care to explain what went wrong (and sorry for the offtopic)?

[SamuriHL]

Since I have a CyberPower UPS for my main workstation I read these lines with dread... care to explain what went wrong (and sorry for the offtopic)?

A lot. Very specific to my setup and house. The battery died without warning me of such (showed 100% power at all times). And because the electrical circuit that the HTPC was on was overloaded at the time (since corrected by an electrician) I had power problems that essentially spiked the circuit, overloading the UPS with a dead battery, and essentially annihilating my HTPC's components. I've only traced a few of the dead parts but the power supply, memory, and GPU are all toast for sure. Mobo might be ok but not entirely sure at this point. I will (probably) eventually rebuild an entirely new machine but not until next year some time. Needless to say I'm unamused that the dead battery wasn't detected by the UPS but really what can you do. I've since replaced the battery and it's back to working properly. Plus rewiring the circuit will prevent any future issues. IOW, this is not something you should concern yourself with because it's a lot of failure points that you can't simply point to one and go "geeze that sucks".

Apologies for the off topic.

[huhn]

your PSU should have catched that.

if your UPS failed already why would you ever use it again. it did the opposite of what it's made for.

[SamuriHL]

Well, you can't fault it TOO much for having a dead battery on a messed up electrical circuit. Yes, I agree that it should have caught the dead battery situation and not lied to me about having 100% capacity when in fact it had 0. When I rebuild the HTPC, I'm likely to include a new UPS, as well. Right now it's just got my tivo and ATV on it so I'm not terribly worried about it.

As for my PSU, yea, I tend to agree there. It's an 850 eVGA gold so it's not some cheap low quality PSU. That'll have to get replaced when I build out a new machine.

Having the circuit fixed is nice, though. That was more problematic than the HTPC as it was a risk to the entire house. Yes, it was that bad.

[Balling]

Yes, here RGB 12 bit works with hdmi 2.0b on 24 Hz. SDR and HDR.

[ashlar42]

As for my PSU, yea, I tend to agree there. It's an 850 eVGA gold so it's not some cheap low quality PSU. That'll have to get replaced when I build out a new machine.
This gets funnier and funnier... what do I have inside my HTPC?

https://www.evga.com/products/product.aspx?pn=220-G3-0750-X1

:D

Ok, sorry everyone... ;-)

[Balling]

This gets funnier and funnier... what do I have inside my HTPC?

https://www.evga.com/products/product.aspx?pn=220-G3-0750-X1

:D

Ok, sorry everyone... ;-)

Hey, you should have bought normal Titanium 80 PLUS PSU that is recommended by Intel with all kind of ErP low level stuff and always awake mode.

[ryrynz]

New audio driver 1.3.38.94 as part of 496.76

[Klaus1189]

Anybody has a new 12 gen intel cpu already?
I am interested in iGPU, especially in Hardware deinterlacing.
If you have one play this sample file: https://drive.google.com/file/d/12wO8NJbIrfa2MD4yVaA38RrBBdziCda8/view
Please tell me if the logo "www.d88.com"
Any other issues?

[SamuriHL]

Maybe doom eternal will stop giving me nasty messages about how screwed up the nVidia drivers are after a certain revision now. LOL

[aufkrawall]

I wish you better luck than I had with RDR2 Vulkan. The last hotfix already mentioned a fix, yet it crashed the driver for me within minutes...

That being said, this driver still forces me to turn off MPO to avoid stutter with madVR/mpv in fullscreen.

[SamuriHL]

SIGH....it's clearly too much to ask for OS and driver MFG's to play nice together...

[ryrynz]

SIGH....it's clearly too much to ask for OS and driver MFG's to play nice together...

I don't quite understand why you can't just design your hardware to an open interface standard that's inside every OS and everything just works? No more driver updates breaking things.
Surely there's a better way the complete cluster f*ck that is current driver development.
People waste so much time testing, benchmarking and problem solving basically every new version, it's just ridiculous.

[Asmodian]

People waste so much time testing, benchmarking and problem solving basically every new version, it's just ridiculous.

It is one of those "too late now" situations. Backwards compatibility is nuts at this point. How many different versions of the DirectX API are still supported today? It is all a very complex software stack at this point.

Software features cannot simply stop changing, at least the next new one will get a lot of adoption so anything competitive is by definition pretty new. Humans have NOT perfected graphic APIs, DWMs, etc. The good and bad of this weird tool we call software. :confused:

Any new "everyone just use this" project would simply be adding another complication in the complex environment.

[nevcairiel]

Even in an ideal world that would never work, unless you want both hardware and software to stop evolving. Evolution means change, and change can present issues. No matter how open your design is.

You can see similar issues in the Linux world, even when you exclude drivers entirely. Software packages update, break compatibility with each other, and it all turns into a mess. All open-source, not even hardware related. The same principle holds. If you want new features and advancements, you need to be open to change, and anything that comes with that.

Besides, the majority of these "issues" are niche cases that affect a minority of users on specific setups, and often have simple work-arounds. Is it really worth it getting worked up about a theoretical issue you can potentially fix with a press of a button should it even affect you? My HTPC plays video flawlessly with zero drops or glitches without changing any settings, for what its worth. :)

[KrazyLurt]

Maybe doom eternal will stop giving me nasty messages about how screwed up the nVidia drivers are after a certain revision now. LOL
Via steam I assume, same for me, it bother the hell out of me for, but I read a while ago how to remove the warning.

If this update doesn't help then you can navigate to:
"xxx:\xxx\Steam\steamapps\common\DOOMEternal\launcherData\launcher.cfg"

edit launcher.cfg, line to a 0 value

rgl_showNvidiaStartupWarning 0

[SamuriHL]

Thanks for that.

As for video, yes, me as well, Nev. [emoji846] things are working very well on that front on my laptop.

As for just leaving things where they are I can't for quite a few reasons. The biggest being security. Yes, even with gpu drivers security comes into play. It's all well and good if you can isolate your machine offline then sure you can leave it alone and never touch it again. I can't do that. I require it to be online. As such I have no choice but to keep it up to date. And all the problems that brings.

Sent from my SM-G998U1 using Tapatalk

[aufkrawall]

You can see similar issues in the Linux world, even when you exclude drivers entirely.

Though components (e.g. user and kernel space drivers) are more or less developed independently from each other. Which is why it is usually much easier to deduce which component actually broke (unlike on Windows, where Windows and driver updates can cause all sorts of issues that are hard to identify) and with proper git practices, often single commits can be easily identified as culprit (and users can try fixes and provide feedback before they land on the main branch).

It also seems to be really beneficial for software quality if companies don't just dump giant code drops with hardly enough testing vs. single commits that undergo proper (and likely more strict) reviewing processes. I found upstream amdgpu Linux kernel driver and Mesa to be much more reliable than the bugged stuff AMD ships with their Windows driver, in fact also often/usually better than the Nvidia Windows driver.

It might be that traditional proprietary development practives aren't simply sufficient anymore for today's complex software. Also, Linux and Mesa development was hardly hit (if at all) by the pandemic.

[SamuriHL]

It might be that traditional proprietary development practives aren't simply sufficient anymore for today's complex software.

As a professional software engineer, I find that offensive! :P It's not that the development practices aren't sufficient, it's that they aren't followed. Part of the SDLC is in testing. In the commercial world, time crunches are artificially created by unrealistic business demands. The first thing that gets cut is testing. It should all be automated but often isn't. And because of that, things are the way they are now where end users end up being testers. As Nev mentioned, those niche edge cases that impact us the most, those aren't tested for. So they escape.

Bringing this back to driver development, it's clear the pressure to release at least one driver per month, focused on adding support for new games and new monitors takes priority over any other functionality within a driver. And that pressure leaves little time for the niche stuff. We have a lucky month when they simply leave our stuff untouched. That's really the best we can hope for most months. Once a year we tend to get a push that actually helps us like when they made 23Hz stable. Most months it's "please don't break s***".

[aufkrawall]

You're probably right that also proprietary software could be way better. But look at Microsoft: They drown in money more than ever, but software quality (who likes Windows 11, recent Outlook, Teams etc...) can hardly compete with that of gilded Windows 7 era (apart from security, perhaps).
Proper git development doesn't magically solve all issues, but I think there is a tendency of it enabling better software quality. Especially for complex/hard stuff like kernel or driver.

[SamuriHL]

You're preaching to the chore on the merits of git. I push for it in every company I work for. Proper source management is critical. Branching strategy plays a LARGE role in the quality of large development projects. Proper branching strategy would also allow for different release types. Yes, we have the studio vs gamer drivers now. But imagine if they had a dedicated "HTPC" driver that only changed when needed. Security updates? Yes. Updates for when the OS changes? Yes. Updates for HTPC functionality, hell yes. But other than that, leave it the F alone. LOL By having proper branching strategy, you could do that by merging the critical code to the branch, properly test it for the use case the branch exists for, and release it separately from the more popular gaming branch. Even the studio branch is technically closer but wildly different than what we would want from an "HTPC" branch. That's geared more toward content creation. We want something geared toward content consumption. :)

[nevcairiel]

There is no studio branch, actually. It's the same driver, they just release it more infrequently after more testing, so it's typically older, eg. more stable. It's not fundamentally different to GRD drivers otherwise.

Nvidia has typically two active driver branches, the "new feature" driver which is currently 496, and the "stable" driver which is 471. For marketing they get fancy names, but they don't differ other then by age - the older one has more fixes and less new things that break again.

[SamuriHL]

Well, they SHOULD. LOL That way they could keep an updated HTPC style driver devoid of all the BS that the game drivers go through. Proper branching strategy really would solve a lot of issues.

[nevcairiel]

The problem is how specific do you get? If you got a big screen TV with a reasonably powerful PC attached... wouldn't many people also want to couch-game on that, because why not? Why can't I have a driver that has video and gaming working fine? Instead I have to switch between two? :D

[aufkrawall]

I think that's why the aim should be to break less in the first place and then deal with breakage more transparently.
At least chances are you can still get a human response when reaching out to Nvidia and get improvements in the wake of it. I don't think AMD Windows team has any kind of support at all, they just despise their Windows customers. Can't explain that blunt ignorance and 0 communication otherwise.

[SamuriHL]

The problem is how specific do you get? If you got a big screen TV with a reasonably powerful PC attached... wouldn't many people also want to couch-game on that, because why not? Why can't I have a driver that has video and gaming working fine? Instead I have to switch between two? :D

The real world answer to that is already known. Too many variables. I get it, I have for years tried to have a machine that "does it all" myself. The reality is that you either spend an enormous amount of time fighting one side of the equation (game stability) or the other (HTPC stability) in order to strike that balance. You're right....we SHOULD be able to have both. The reality is that if the driver MFG's don't see HTPC functionality as a priority, introducing breaking changes in order to fix game stability is considered an acceptable risk. We've seen it many, MANY times.

Now, we're developers, so you know what I would say to this. Have an install that has the ability to "switch" between stable drivers under the covers based on which profile is selected at any given time. It's the equivalent of switching between a gaming driver and a stable HTPC driver, only done automagically based on a profile selection. :D

[SamuriHL]

I think that's why the aim should be to break less in the first place and then deal with breakage more transparently.
At least chances are you can still get a human response when reaching out to Nvidia and get improvements in the wake of it. I don't think AMD Windows team has any kind of support at all, they just despise their Windows customers. Can't explain that blunt ignorance and 0 communication otherwise.

The problem is that it's not a priority for them to test for breakage in the HTPC space. It's truly niche. Maybe a couple percent of their user base. When they've got the majority of their customers clamoring for support for Game X of the month, this niche space is just not a priority for testing, much less stopping the release of a driver that includes a breaking change.

Personally I like my idea of profile driver selection. But it, too, will never happen. Unless Nev decides to take me up on that idea and include private known stable driver versions in JRiver MC and have the ability to on the fly overlay those for playback and then revert to your gaming driver upon exit. BAHAHAHAHA :D

[Balling]

Once a year we tend to get a push that actually helps us like when they made 23Hz stable. Most months it's "please don't break s***".

You mean 24/1.001 stable as in EDID when it is in VIC timing that supports both with /1.001 and without? Yeah, but that is still quite broken in some players like in Chrome, it does some strange dropping and duplicating of frames even though both file and display are 24/1.001.

[Klaus1189]

511.09 SD has new new HD Audio Driver (https://drive.google.com/file/d/1zwdlJFG3trlchAGVVxvf_RoPk_PGeJPX/view?usp=sharing)

[SamuriHL]

That looks scary. LOL

[Charky]

Now, we're developers, so you know what I would say to this. Have an install that has the ability to "switch" between stable drivers under the covers based on which profile is selected at any given time. It's the equivalent of switching between a gaming driver and a stable HTPC driver, only done automagically based on a profile selection. :D
I use a non-dev solution that IMO seems wayyy easier : dual boot ;)

[SamuriHL]

Dual boot is certainly an option for some.

[ryrynz]

That looks scary. LOLRan with it last night on the 3060, all was well. System latency looks to be improved considerably based on what I and others have seen with LatencyMon.

[aufkrawall]

As with all Ampere driver updates so far, I notice zero difference with this one. Nothing broke, nothing was fixed, nothing runs better or worse. Could be better, could be worse. Excitement.

[SamuriHL]

Well that's good at least. They're getting better.

[mclingo]

having some issues with AMD drivers after 21.8.2, all seem to have some issues playing "some" HEVC movies, I cant track down what it cant play though, here are the details of the movie it wont play, major screen corruption.


General
Complete name :
Format : MPEG-4
Format profile : Base Media
Codec ID : isom (isom/iso2/mp41)
File size : 1.90 GiB
Duration : 2 h 2 min
Overall bit rate : 2 230 kb/s
Movie name :
Encoded date : UTC 2021-12-31 14:14:58
Tagged date : UTC 2021-12-31 14:14:58
Writing application : Lavf58.20.100
Comment :

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L4@Main
Codec ID : hev1
Codec ID/Info : High Efficiency Video Coding
Duration : 2 h 2 min
Bit rate : 2 000 kb/s
Width : 1 800 pixels
Height : 1 080 pixels
Display aspect ratio : 5:3
Frame rate mode : Constant
Frame rate : 24.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.043
Stream size : 1.71 GiB (90%)
Writing library : x265 3.3+4-rarbg-30eb4de83092:[Linux][GCC 8.3.1][64 bit] 10bit
Encoding settings : cpuid=1111039 / frame-threads=4 / wpp / no-pmode / no-pme / no-psnr / no-ssim / log-level=2 / input-csp=1 / input-res=1800x1080 / interlace=0 / total-frames=0 / level-idc=0 / high-tier=1 / uhd-bd=0 / ref=4 / no-allow-non-conformance / no-repeat-headers / annexb / no-aud / no-hrd / info / hash=0 / no-temporal-layers / open-gop / min-keyint=24 / keyint=250 / gop-lookahead=0 / bframes=4 / b-adapt=2 / b-pyramid / bframe-bias=0 / rc-lookahead=25 / lookahead-slices=4 / scenecut=40 / hist-scenecut=0 / radl=0 / no-splice / no-intra-refresh / ctu=64 / min-cu-size=8 / rect / no-amp / max-tu-size=32 / tu-inter-depth=1 / tu-intra-depth=1 / limit-tu=0 / rdoq-level=2 / dynamic-rd=0.00 / no-ssim-rd / signhide / no-tskip / nr-intra=0 / nr-inter=0 / no-constrained-intra / strong-intra-smoothing / max-merge=3 / limit-refs=3 / limit-modes / me=3 / subme=3 / merange=57 / temporal-mvp / no-frame-dup / no-hme / weightp / no-weightb / no-analyze-src-pics / deblock=0:0 / no-sao / no-sao-non-deblock / rd=4 / selective-sao=0 / no-early-skip / rskip / no-fast-intra / no-tskip-fast / no-cu-lossless / no-b-intra / no-splitrd-skip / rdpenalty=0 / psy-rd=2.00 / psy-rdoq=1.00 / no-rd-refine / no-lossless / cbqpoffs=0 / crqpoffs=0 / rc=abr / bitrate=2000 / qcomp=0.60 / qpstep=4 / stats-write=0 / stats-read=2 / cplxblur=20.0 / qblur=0.5 / ipratio=1.40 / pbratio=1.30 / aq-mode=3 / aq-strength=1.00 / cutree / zone-count=0 / no-strict-cbr / qg-size=32 / no-rc-grain / qpmax=69 / qpmin=0 / no-const-vbv / sar=1 / overscan=0 / videoformat=5 / range=0 / colorprim=2 / transfer=2 / colormatrix=2 / chromaloc=0 / display-window=0 / cll=0,0 / min-luma=0 / max-luma=1023 / log2-max-poc-lsb=8 / vui-timing-info / vui-hrd-info / slices=1 / no-opt-qp-pps / no-opt-ref-list-length-pps / no-multi-pass-opt-rps / scenecut-bias=0.05 / hist-threshold=0.01 / no-opt-cu-delta-qp / no-aq-motion / no-hdr10 / no-hdr10-opt / no-dhdr10-opt / no-idr-recovery-sei / analysis-reuse-level=0 / analysis-save-reuse-level=0 / analysis-load-reuse-level=0 / scale-factor=0 / refine-intra=0 / refine-inter=0 / refine-mv=1 / refine-ctu-distortion=0 / no-limit-sao / ctu-info=0 / no-lowpass-dct / refine-analysis-type=0 / copy-pic=1 / max-ausize-factor=1.0 / no-dynamic-refine / no-single-sei / no-hevc-aq / no-svt / no-field / qp-adaptation-range=1.00 / no-scenecut-aware-qpconformance-window-offsets / right=0 / bottom=0
Encoded date : UTC 2021-12-31 14:14:58
Tagged date : UTC 2021-12-31 14:14:58
Codec configuration box : hvcC

Audio
ID : 2
Format : AAC LC
Format/Info : Advanced Audio Codec Low Complexity
Codec ID : mp4a-40-2
Duration : 2 h 2 min
Duration_LastFrame : -11 ms
Bit rate mode : Constant
Bit rate : 224 kb/s
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 kHz
Frame rate : 46.875 FPS (1024 SPF)
Compression mode : Lossy
Stream size : 196 MiB (10%)
Language : English
Default : Yes
Alternate group : 1
Encoded date : UTC 2021-12-31 14:14:58
Tagged date : UTC 2021-12-31 14:14:58

[quietvoid]

having some issues with AMD drivers after 21.8.2, all seem to have some issues playing "some" HEVC movies, I cant track down what it cant play though, here are the details of the movie it wont play, major screen corruption.


The video is 5:3. I've personally had issues with hardware decoding on my 5500 XT in the past with similar aspect ratios.
As of now they play fine with current Linux 5.16 amdgpu drivers.

[aufkrawall]

AMD Linux and Windows drivers are vastly different, especially when it comes to hardware decoding. Might be broken for good, it's AMD Windows driver team.

[DMU]

Give a link to a similar video, please.

[mclingo]

sorry i dont have a small enough sample to provide a test video, i've also moved back to 21.8.2 to solve the issue, I will try the next version released and report back.

[mclingo]

I fixed this issue but using this setting but not sure what it is, havent seen this before, only D3D11 - does D3D11(cb) it mean copy back maybe?

Any ideas?


https://1drv.ms/u/s!AgvFafeelEBiqbY-q1llWgVCn2tdBQ?e=MIewLw

[Asmodian]

Yes, cb means copy back.

[mclingo]

wonder why it fixes the rendering problem then?

[IngramAU]

I give up on fixing my bitstreaming audio issues. I'm getting drops in audio less frequently now but it's happening on DD+ Stereo files not just Atmos files. PCM from here on out.

[mclingo]

i found audio drops using copy back d3d11 with mpcbe, you tried a different decoder?

[EpsilonX]

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.
This issue can be best seen on displays which want full range 0-255, like TVs in PC Mode (PC
mode for full 4:4:4/RGB support, so you do not use color subsampling like 4:2:2 or 4:2:0)
Also overriding the range for test purposes in MPC-BE (video tab -> Output range) does not
take effect.
Dear AMD, if any of your driver programmers read this: Please fix this fundamental video
bugs .These are there since RX 5000 series launch.

Have AMD fix this in the latest driver for the 6000 series card..?
Thank you

[mclingo]

Have AMD fix this in the latest driver for the 6000 series card..?
Thank you

doubt it still broken on 5700 series

[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.
This issue can be best seen on displays which want full range 0-255, like TVs in PC Mode (PC
mode for full 4:4:4/RGB support, so you do not use color subsampling like 4:2:2 or 4:2:0)
Also overriding the range for test purposes in MPC-BE (video tab -> Output range) does not
take effect.
Dear AMD, if any of your driver programmers read this: Please fix this fundamental video
bugs .These are there since RX 5000 series launch.

Have AMD fix this in the latest driver for the 6000 series card..?
Thank you

doubt it still broken on 5700 series

Can users who have a RX 5000 / RX 6000 card please test this?
I sold my RX 5700 XT, so I can't test anymore.

[mclingo]

I guess a sample of 1 (me) is not representative of everyone but its highly unlikely anyone's is fixed if mine isnt, AMD are useless at fixing movie playback bugs, it is also only present in some renderers, I dont see it in MADVR, only MPC HC / BE using EVR, but i'm not using PC mode on my TV as use TRUMOTION which is disabled in PC mode on my LG OLED.

[EpsilonX]

IIRC. Nvidia used to have this kinda problem with color range with HDMI right..?
Though it can be 'fixed' by the user through registry.
For me personally, I can live with the deinterlacing problem...
But my PC is always connected to my TV (PC Mode RGB of course), to watch movies (MPC-HC + MadVR), YT from bed when I'm lazy... :D
So this 'simple' bug is very annoying.

[QBhd]

I have no idea what this "problem" is. I have had flawless playback on my 5700XT for well over a year.

QB

[mclingo]

if you play an SDR movie in MPC-BE or HC using the !!! EVR renderer !!! the wrong colour space it output so you have to add a filter to switch it between 16/235 / 0-255 - no issues on HDR.

If you dont use this renderer you'll never see the issue, I only use it for previewing videos, I do all my playback using MADVR and KODI-DS

[QBhd]

So why do you think it is an AMD driver issue? Sounds like an MPC to me.

QB

[huhn]

because normal EVR is part of windows and the problem is also present with windows media player.

AMD also has a problem that there presets are forced on all the time there is no off option. you can move a small piece in fort of it liek a windows explorer as long as you didn't release the left mouse button it uses no image corrupting stuff.

https://abload.de/img/amdcijpo.png
these are all options.

hdr has wrong ranges since the release of windows 11 (it was fine in the beta) even even computer games using AGS are totally messed up.

[Snowknight26]

Can users who have a RX 5000 / RX 6000 card please test this?
I sold my RX 5700 XT, so I can't test anymore.

Seems to be fixed with an RX 6800 XT running 22.1.2.

Tested with a limited-range H.264 video, MPC-HC using EVR-CP. Forcing the output range to 0-255 (right click video -> Renderer Settings -> Output Range -> 0-255) results in washed out colors, while setting forcing the output range to 16-235 results in correct colors (matching madVR).

If you consider forcing the output range to be a fix, then yes it's fixed.

[clsid]

Does your monitor/tv expect limited range input?
Have you configured madvr to also output limited range?

[huhn]

i did a test on win 11 so don't take these findings seriously there are massive issues with win 11 and AMD.

D3D11 processing is using correct ranges (i didn't test P010).
you can make it use bob deint if d3d11 processing is active else it'S not doing it. scaling with deint at the same time is NN.

DXVA processing is still using wrong ranges.
Deint is now even more broken it's simply not done at all.
also i got this the first time in my life: https://abload.de/img/wowifk06.png
don't worry that error crashed and got stuck there.

[clsid]

What do you mean with the error got stuck? Were you unable to click on the message box buttons?

Can you also test with a HDR video? So people are having driver crash issues with D3D11 rendering + HDR with the AMD 21.12.x/22.1.1 drivers. I am not sure if it also requires HDR passthrough to trigger.

[huhn]

no sorry i can't test HDR anymore with the new AMD driver.
it was buggy but still working with the last driver but with this one it doesn't enter HDR at all and games are so messed up there are no word for it.

HDR to sdr with mpcVR works here.

it got completely endless loading mouse icon nothing was clickable.
this is not the newest mpc-hc version (i still have desktop for subtitle resolution) and i'm on the dev build for win 11 which stops shutting down because it can't close the taskmgmt.

after killing it in the taskmgmt it was running's a windows error report without asking me. i would not be shocked that this was the reason it got stuck in the first place.
so don't think to much about it. on the last dev build i got like a 100 TPM errors... it's just not a stable system.

[Snowknight26]

Does your monitor/tv expect limited range input?
Have you configured madvr to also output limited range?

It's a monitor so 0-255 naturally. madVR was configured so that the monitor was set to expect 0-255. Changing the monitor to expect 16-235 resulted in washed out colors.

[clsid]

Then setting 16-235 for EVR is wrong, and there obviously is a bug in the driver.

[Klaus1189]

511.65 has new new HD Audio Driver (https://drive.google.com/file/d/1RCwl6XTxhcsbxv18IX89ejZJilo28IH4/view?usp=sharing)

[kostik]

511.65 has new new HD Audio Driver (https://drive.google.com/file/d/1RCwl6XTxhcsbxv18IX89ejZJilo28IH4/view?usp=sharing)

but still has this issue:

[NVIDIA Ampere GPU]: With the GPU connected to an HDMI 2.1 audio/video receiver, audio may drop out when playing back Dolby Atmos. [3345965]

[v0lt]

The driver for Intel UHD 770 (30.0.101.1191) has different behavior depending on the name of the executable file. (https://sourceforge.net/p/mpcbe/tickets/912/)

[Aleksoid1978]

The driver for Intel UHD 770 (30.0.101.1191) has different behavior depending on the name of the executable file. (https://sourceforge.net/p/mpcbe/tickets/912/)

Intel 30.0.101.1340 - the same issue, Intel UHD 730.

[huhn]

maybe you should ask the user with the problem if 1340 fixes the issue.
this is the biggest "bug" i have seen in a while...

[v0lt]

maybe you should ask the user with the problem if 1340 fixes the issue.
this is the biggest "bug" i have seen in a while...
30.0.101.1340 does not solve the problem.

[DinaMoe]

Very late to the party. Just getting up to speed with regard to Nvidia drivers not passing through HDR correctly.

Has that been fixed with any of the 500.00 WHQL drivers?

[SamuriHL]

What's the issue with pass through on HDR? I just today finished my new HTPC build with a 3080 and I've got a VRROOM so I can validate anything you want. I'm using the very latest drivers.

[DinaMoe]

@SamuriHL: Maybe there isn't a problem anymore. You would know better than I.

[SamuriHL]

Seems to work just fine for me. Not really sure. It doesn't work for me on my laptop with my 2080 but who knows why that is.

[nevcairiel]

I use HDR pass-through every day, and its fine. I also verified metadata with HDFury Arcana. Granted though, I don't use madVR for it.

[DMU]

Granted though, I don't use madVR for it.
What renderer are you using for this?

[SamuriHL]

He's using his own. Lol jrvr. I've tested both jrvr and madvr with the vrroom and everything is working as expected on the latest drivers.

Sent from my SM-G998U1 using Tapatalk

[Polopretress]

Hello.

I see some user of 6800XT.
On my side, already 2 people using this GPU have seen their rendering time increased a lot compared to their previous GPU.
One has previoulsly a Vega64 and the other had a GTX1080.

Normally, rendering time should be highly below the previous boards and we cannot find a solution so far to explain the issue and i suppose that most of users have no issue.
So, i post to ask if there is a known tip about that to fix this problem before to send back the GPU. (some settings inside the driver configuration ?)

Than you very much.
For information, i have provided some specific settings.bin of madvr and video to test and compare the rendering time and we confirm the problem.
GPU Benchmark test are OK (no problem highlighted) - scan with GPU-Z are correct.
Their driver software are updated.
The PCHCs use standard software such as Lav filters 0.76, MPC-BE, MadVR 0.92.17 with and without the beta 157. One is in 32 bits configuration, the other is full 64 bits (same result)

I am really at the end of investigation to understand/identify the issue...

[Klaus1189]

@Polopretress:
Welcome in my thread :)
Can you test something for me? I am interested in hardware capabilities of Vega64 and RX6800XT.
So please just do the following:
Make sure you have a TV in pc mode which wants 0-255 and play a video in MPC-BE or also MPC-HC and check the black levels. Are the blacks elevated or black as it should be. In MPC-BE, probably also in MPC-HC there is an option in "Video" Tab in options which lets you override the output range. Does this setting make a difference if you choose 0-255 and then 16-235?

For the deinterlacer test you need to download:
https://drive.google.com/file/d/1Zs2T4-Nlu-16H0aCBWWxLn5pTVK4ftwV/view?usp=sharing
Play it and check the charakters above "www.D88.com" for flickering:
https://drive.google.com/file/d/1Sq5aspz8ikCTZdBKcUV4h27kLzgufgoN/view?usp=sharing
Flickering like here:
https://de.wikipedia.org/wiki/Datei:Indian_Head_interlace.gif
If you use LAV Filters use DXVA2 copyback, but not D3D11 for deinterlaing test.
Disable Software deinterlacing in LAV Filters, if it is enabled.

Since you know someone who has a Vega64, would you mind to ask him/her to test this with the Vega64, too.

That would help me a lot ;)

If a Radeon VII user is reading this, please test this also for me and let me know the results.

[Polopretress]

I will ask since it is 2 contact of me (on my side i have still a GTX1080) and i think one of the both has already returned RX6800XT for a RTX2080TI...

i have another contact who has still a Vega64 and i am sure at nearly 100% that he is connected to the VP (Epson EH-LS10500) in RGB 0-255 and it works fine for him.(in SDR FullHD or UHD HDR with DTM output in SDR)
I will confirm with him as well. Is it necessary to have a TV instead of a VP ? because sure , he will not be possible for him to test with a TV since he has no TV in its HC room.
For deinterlaced video, i think he use lav filters software such as Yadiff.

[Polopretress]

@Klaus1189

Find below the answer of my contact who has a Vega64

I am playing MPC-BE + LAV 0.76.0 + madVR 0.92.17 .
My HTPC is connected to Denon AVR-X4300 then to Epson EH-LS10500.

1/ My video stream is in RGB 4:4:4 10bit 0-255.
I have perfect blacks and whites.
If I switch madVR from 0-255 to 16-235 (Devices/Properties), then it does what is supposed to happen : Blacks are lifted, and whites dimmed.
In the "video tab" of Options in MPC-BE, Output Range is greyed using madVR (only available for VMR-9 and EVR-CP).

2/ I did the deinterlacer test :
I normaly do not use hardware acceleration in my process.
I use software YADIF deinterlacement of LAV decoder. No flicker.
If I select "no software deinterlacing", there is a strong comb effect, but still no flicker at all on the chinese sponsor (camera does not move).
I cannot use HW/GPU deinterlacing whatever is selected in HW acceleration. It's always greyed, and seems to work only for "(CUVID/QS only)".

Hope that can help.

[Klaus1189]

@Klaus1189

Find below the answer of my contact who has a Vega64
I am playing MPC-BE + LAV 0.76.0 + madVR 0.92.17 .
My HTPC is connected to Denon AVR-X4300 then to Epson EH-LS10500.

1/ My video stream is in RGB 4:4:4 10bit 0-255.
I have perfect blacks and whites.
If I switch madVR from 0-255 to 16-235 (Devices/Properties), then it does what is supposed to happen : Blacks are lifted, and whites dimmed.
In the "video tab" of Options in MPC-BE, Output Range is greyed using madVR (only available for VMR-9 and EVR-CP).

2/ I did the deinterlacer test :
I normaly do not use hardware acceleration in my process.
I use software YADIF deinterlacement of LAV decoder. No flicker.
If I select "no software deinterlacing", there is a strong comb effect, but still no flicker at all on the chinese sponsor (camera does not move).
I cannot use HW/GPU deinterlacing whatever is selected in HW acceleration. It's always greyed, and seems to work only for "(CUVID/QS only)".

Hope that can help.



1. That is good to know
2. That is impossible. If for this special MBAFF file YADIF is truely active, it will flicker, because YADIF is not frame adaptive. That is the hole point of this test.
Only the Hardware deinterlacer is frame adaptive, at least should be, not on RX 5000 series, but it possible AMD has changed something, but I sold my crap 5700XT for good money :) and got a 3090 before high prices (still much lower price than as of this week) and can't test it anymore.
Could you please tell him/her to set LAV Filters Software deinterlacer to none and as I already pointed out:
@Polopretress:
If you use LAV Filters use DXVA2 copyback, but not D3D11 for deinterlaing test.
Disable Software deinterlacing in LAV Filters, if it is enabled.
This is important for this test!

He/She should also test with Hardware acceleration enabled and disabled. I doubt is will make a difference, but we test here, so I need input :)

Please also add both testes with the RX 6800XT. I really need that info. ;)

[ryrynz]

Please also add both testes with the RX 6800XT. I really need that info. ;)

[emoji6]

[Snowknight26]

Results haven't changed since early 2021 (https://forum.doom9.org/showthread.php?p=1936390#post1936390).

[Klaus1189]

I was expecting a change after a year.

[Klaus1189]

I was hoping for fix, because it is not so long to the next generation of AMD cards, not the RX 6000 refresh but the next generation. What if they are ignoring basic video stuff again, for the third time?

RX 5000 is not fixed either, right? That would be a miracle.

[mclingo]

amd users could so with spamming the AMD forums with both faults, i'm going to log it myself today just to see what they come back with, i havent logged anything for ages on there as nothing every happens, plus I dont notice either problem as I dont have any interlaced videos and I dont use PC mode on my TV as I use all motion processing if I do.

[CZ Eddie]

I'm replacing my 2060 Super with a 3080 tomorrow.
Looks like they both use the same driver download from Nvidia.
Do you guys think it's necessary to do a clean uninstall and reinstall of the driver after the swap?

Also, has Nvidia really gone three months without a driver update?
This is the most recent I'm finding:

Version: 472.84 Studio Driver
Release Date: 2021.12.13

[huhn]

no. you are clearly no trying hard enough.
https://www.nvidia.com/Download/driverResults.aspx/187098/en-us

it's never necessary to do a clean install but always recommended.

btw pretty much all nvidia GPU use the same driver.

[ryrynz]

Sometimes necessary, would do it for a major driver update or changing cards. Lots of issues can be fixed by a proper clean install
which involves usually removing the driver using ddu first. Even nVidia recommended this to my brother and it fixed his gaming issues.

[clsid]

Yes, always use Display Driver Uninstaller (DDU) when swapping GPUs.

[CZ Eddie]

Thanks, guys. I'll use the DDU just in case.
no. you are clearly no trying hard enough.
hahahah

Wow, okay the Nvidia "advanced driver search" page sucks.
https://i.ibb.co/pdTydJx/Untitled.jpg

[Klaus1189]

Please upload your picture to google drive or similar, otherwise it will take some days till we can watch it.

[CZ Eddie]

Hah, and now it's too big.

[Klaus1189]

Only post the link here of google drive and we can open it in a new tab.

[SamuriHL]

People might want to look at the issues list on this one. Specifically this:

[NVIDIA Ampere GPU]: With the GPU connected to an HDMI 2.1 audio/video receiver, audio may drop out when playing back Dolby Atmos. [3345965]

That seems, you know, bad.

[ryrynz]

That seems, you know, bad.

"May" is the important part here. Just install & live dangerously eh?

[huhn]

that's a good thing the issue is most likely older and part of older driver acknowledging it is just the start to get it fixed.

[nevcairiel]

People have been reporting issues with Atmos before, this is definitely not new to this driver - issues rarely are new when they start showing up in the list, they just started tracking them then.
They also rarely affect everyone.

[SamuriHL]

As long as they fix it. And of course I'll install it and live dangerously. Lol

Sent from my SM-G998U1 using Tapatalk

[huhn]

you may add this information in the notes.

d3d9 overlay rendering broke in ~479 and was removed in 511 as a "fix" at least on pascal.

[mclingo]

HI, as some of you know there is an issue with the EVR renderer where it outputs wrong colour space so you have use a filter when watching SDR material to convert 16.235 to 0-255, it has been suggested this is an AMD driver issue but why does MADVR not have this issue if it is?

is this the same issue as reported on the PDF and if so is it really a driver issue if other renderers are working fine?



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.
This issue can be best seen on displays which want full range 0-255, like TVs in PC Mode (PC
mode for full 4:4:4/RGB support, so you do not use color subsampling like 4:2:2 or 4:2:0)
Also overriding the range for test purposes in MPC-BE (video tab -> Output range) does not
take effect.

[huhn]

because madVR isn't a DXVA2 video renderer it nearly for sure even ask for limited range when DXVA2 is used so the issue will not happen.

[mclingo]

yes bu that means MADVR is doing something differently and so maybe not an AMD driver issue per sey, or at least its the EVR renderer which needs to be updated or changed?

[nevcairiel]

EVR uses the drivers video processing capabilities, other renderers usually try to avoid that because its often low quality and troublesome. So if EVR misbehaves, its typically the drivers video processing screwing something up.

[mclingo]

EVR uses the drivers video processing capabilities, other renderers usually try to avoid that because its often low quality and troublesome. So if EVR misbehaves, its typically the drivers video processing screwing something up.

ah right, I understand now. Thanks :)

[Klaus1189]

you may add this information in the notes.

d3d9 overlay rendering broke in ~479 and was removed in 511 as a "fix" at least on pascal.

OK, I add this, but I can not find 479.XX, maybe you mean this one: 497.29 2021-12-20 only DCH available!

Should I use the first 511.XX, which would be 511.09 2022-01-04 first SD which is only available as DCH!
Or the first GRD: 511.23 2022-01-14

These is not a single driver between these two. I need this info, so I can do it right.

[huhn]

466.77 broken
477.12 broken
496.49 feature disabled
512.15 feature disabled

it will test a couple older driver soon but they may work form time to time because i'm pretty sure 466 worked in the past.

[Klaus1189]

466.77 broken
477.12 broken
496.49 feature disabled
512.15 feature disabled

it will test a couple older driver soon but they may work form time to time because i'm pretty sure 466 worked in the past.

472.12 perhaps? I added it to 472.12
If it is wrong, please let me know.

[pirlouy]

For those who know, is it possible to send audio only with HDMI (without dual monitors, just a fake image) with latest drivers/OS or is it planned ?

[JaylumX]

For those who know, is it possible to send audio only with HDMI (without dual monitors, just a fake image) with latest drivers/OS or is it planned ?

If you are using an Nvidia card then the short answer is yes.

Long answer to give you an explanation, is I connect my Nvidia RTX to my Panasonic soundbar using a displayport to hdmi adapter (passive). As long as you install the Nvidia HD audio drivers that are supplied with the graphics drivers, the Nvidia card will send audio to the soundbar be it 7.1 LPCM or bitstreaming Atmos or DTS X.

The soundbar will register like a second display and the mouse will extend there so the solution is to align the "soundbar" display (virtual) diagonally so that it does not span to it.

I am sure the process is similar for AMD and Intel Graphics cards.

Does that answer your question?

[pirlouy]

Well, not really. I hoped with time Windows/OEM would find a solution where you would not need "dual monitors".
"Dual monitors" comes with some drawbacks.
I know the real culprit is HDMI which can't do what SCART was able to do (video or audio or both) but I hoped Windows 11 and GPU OEM would find a solution. Disappointing.

[Klaus1189]

@pirlouy:
What do you want to achieve exactly?

[mclingo]

anyone else noticed rendering corruption and audio dropouts in recent AMD drivers with EVR and MPC renderer, mainly when using MPC-BE / HC, some movies wont play at all unless I change to D3D11 cb but I then go dreadful audio dropouts, some movies just show corruption when skipping through scenes, AMD drivers seems to be a total mess at the moment for HTPC users, oddly, and thankfully MADVR + LAV + KODI DS has no problems whatsoever which is my main player.

Starting to think about a move to NVIDIA but no native 3D / 23,976 has always put me off, if they break something with my main player then i'm defo going green, I had enough problems with 3D when it was supported with NVIDIA cars, cant image its any better now using a workaround?

additional:

not sure when the video corruption started, I cant really be arsed to install one driver after another to find out which one it started with, all I know right now is I moved back to 20.4.1 and that doesnt have the corruption issue, this driver is quite old though.

You will however only see this with EVR and MPC renderer with certain videos, I'm not even sure if its a certain type of encode.

[QBhd]

ZERO problems here with AMD. PotPlayer+madVR+LAV

Not sure why anyone with a modern computer needs to use anything other than software decoding

QB

[mclingo]

Hi, is it possible to get pot player to act a bit more like MPC, double clickanywhere on screen maximse / minmise and one click to pause?

[pirlouy]

@pirlouy:
What do you want to achieve exactly?
1)
Plug a TV to PC with HDMI
Plug AV receiver to PC with HDMI
-> Play sound on AV receiver and image on TV WITHOUT DUAL MONITORS (in Windows > Display settings or GPU Drivers Control Panel)
And obviously I don't want to use the HDMI out from AV receiver.

2)
Plug a monitor to PC with Display Port (for example)
Plug AV receiver to PC with HDMI
-> Play sound on AV receiver and image on Monitor WITHOUT DUAL MONITORS

Rest assured it's not a mad demand. It has been asked for years from various people. I was hoping it would come with years.

[huhn]

ZERO problems here with AMD. PotPlayer+madVR+LAV

Not sure why anyone with a modern computer needs to use anything other than software decoding

QB

ok how do i get it to deint.

at this point i take this personal.
and while i'm at it how do i disable the video processing for web browser?

[JaylumX]

1)
Plug a TV to PC with HDMI
Plug AV receiver to PC with HDMI
-> Play sound on AV receiver and image on TV WITHOUT DUAL MONITORS (in Windows > Display settings or GPU Drivers Control Panel)
And obviously I don't want to use the HDMI out from AV receiver.

2)
Plug a monitor to PC with Display Port (for example)
Plug AV receiver to PC with HDMI
-> Play sound on AV receiver and image on Monitor WITHOUT DUAL MONITORS

Rest assured it's not a mad demand. It has been asked for years from various people. I was hoping it would come with years.

I see what you mean. I only recently started doing what you described above but with a soundbar and I found it annoying that the soundbar showed up as a monitor and my mouse kept on spanning there. You are righting in thinking why there has not been a solution for it.

I did try an app to prevent mouse spanning to next display but it was just simpler to arrange both displays diagonally without the app.

I also tried duplicating displays which actually worked and got rid of the dual monitor issue but I found out I could not use HDR. My guess is that it duplicates to the lowest display so for my my soundbar uses HDMI 2.0 and my display is 2.1.

I hope there is a solution for this annoying problem.

[el Filou]

For those who know, is it possible to send audio only with HDMI (without dual monitors, just a fake image) with latest drivers/OS or is it planned ?A long time ago (I don't remember exactly, but something like two/three years I think) I opened an improvement suggestion on Insider Hub for exactly this (using secondary display interfaces and their hardware features but without them being included in the user desktop), without much hope of achieving anything with MS being MS, and to my surprise they actually added it *but* concluded this is something only professionnals need (e.g. doctors using a pro app that displays radio scans on a secondary display), and so they restricted this feature to Windows for Workstations... :rolleyes::rolleyes::rolleyes:

[pirlouy]

Too bad but nice try though ! :)

[CZ Eddie]

I'm on the driver below with my new RTX and 4K60.
I'm using DisplayPort for the first time and finding I cannot get Full Range 0-255. It's only allowing me Limited Range color.
Is this normal for DisplayPort or an issue with the driver (or cable)?

512.15-desktop-win10-win11-64bit-international-dch-whql.exe

Works fine at 1080P, it just greys out the Output Dynamic Range with 4K60.
Switch from DisplayPort to HDMI and it works fine.

ATMOS and 4k60 passes through the DisplayPort so I'm not understanding why the dynamic range is getting greyed out.

[huhn]

passive DP to hdmi can only do about 9 gbit/s close to HDMI 1.4.
or with other words because it can't do more to do it in RGB so with full range it would need double the bandwidth like present on HDMI 2.0 or native DP 1.2.

there are active DP to HDMI converter but they a bit iffy.
GPU with 2 HDMI connector are not that rare just make sure they also have the HDMI version you want.

[el Filou]

:confused:
But full range and limited range only change the reference values used for black/white, the video bandwidth used is the same in both cases.

[huhn]

it using YCbCr 4:2:0 which is allways limited.

[SamuriHL]

Figures. I have my HTPC's disconnected at the moment awaiting a TV upgrade. I'll update them all later tonight I guess.

[Klaus1189]

I added some stuff to first page, so it hopefully shows up in internet searches.
If you have anything to add, please let me know, I am ready for more.

[ryrynz]

Awaiting a tv upgrade.

LG G2 77" OLED

:eek:

[SamuriHL]

LG G2 77" OLED

:eek:

Yup. Hanging on the wall. It's gorgeous.

[nevcairiel]

I couldn't fit 77" in my current place, hence I only got the G1 in 65" last year, but smaller place also means sitting closer, so its still quite an experience.

[SamuriHL]

The C8 got moved to my bedroom. And the G2 is in my living room. Both are mounted to an echogear that pulls out 22" from the wall. :D

[*MidnightWatcher*]

Haven't visited in a long time. What the latest consensus regarding which Win10 driver for the RTX 2070S works best with madVR? :thanks:

[ryrynz]

What's the latest consensus

Everything's been good for a while now. There is nothing that's any better than the rest so just go with the latest that works for your setup.

[lazostat]

Is version 496.49 ok for madvr and hdr or should i install a newer version? I don't understand from your PDF list what is the latest recommended version.

[Klaus1189]

No issues in recent Nvidia drivers, just install latest one ;)

[SamuriHL]

I'll throw it on my 3080 later as I have a new movie coming shortly that I'll be watching tonight.

[Selur]

Installed GeForce Game Ready-Drivers Version: 516.40 with the result that my main display (5k HP27z) didn't work any more, going back to NVIDIA Studio-Drivers 516.96 display works again.

[Klaus1189]

Thanks for feedback :)

[Sunspark]

Not sure if this counts as an Intel driver issue or a hardware issue, but I have discovered that on my old monitor setting a CVT-RB2 timing manually will work for everything EXCEPT HDCP as used by Amazon. The outcome will be a black screen requiring a power off. All the other timing standards work.

Curious, changing 2 of the 4 polarities combos works.

H V
+ + = Works
- - = FAILS HDCP
+ - = FAILS HDCP (also refresh rate slightly higher than the other 3)
- + = Works

[Sunspark]

This is definitely some kind of Intel issue IMO..

I was able to get the refresh rate I was after using CRU. Restart the computer, no problem. Power the computer on from shutdown, no problem. Change to another resolution/refresh and then return to the defined one, no problem.

Sleep mode and then wake the computer, it LOSES the original defined 60 Hz resolution and switches to 59.876 and switching to another resolution/refresh doesn't resolve the issue.

The only fix is to run CRU's restart64.exe to restart the graphics driver, restart the computer, or never let it sleep.

This is one of the odder bugs I've run into.. why would waking up from sleep mode cause a refresh rate issue where it doesn't resume as it was?

[el Filou]

So much stuff can go wrong in drivers.
One driver for my old Radeon would make DXVA hang after resuming from sleep, which would freeze all media players but also web browsers on any page containing video i.e. nearly all of them nowadays.

[brazen1]

https://www.nvidia.com/en-us/geforce/news/f1-22-rtxon-game-ready-driver/
https://www.nvidia.com/download/driverResults.aspx/190552/en-us/

Nvidia GeForce 516.59 WHQL graphics driver released.

FYI, this driver creates noise when windowed for every video format video for me. Fullscreen is fine. I've never experienced anything like this before. I did not try installing it twice but I didn't do anything different than any other driver upgrade. Fwiw, I used DDU as usual. I installed a previous driver and all works fine again. YMMV.

[SamuriHL]

What does "creates noise" mean?

[brazen1]

Speckles all over the screen including black bars.

[huhn]

did you check the signal type send it may have reset.

[Noobius]

TrueHD or DTS-HD MA seems not to work at 23hz or 24hz at all regardless of MadVR so the NVIDIA drivers must be broken?

Any player I use at 23hz or 24hz refresh rates gives an error "audio device not found 0x8889000f".

My old GTX 970 worked fine no issues :/.


I tried all the latest driver versions, same issue.
Not related to mediaplayer either - all crash at 23h or 24hz and all play TrueHD without issue with higher refresh rate.

I wan 23.976hz playback with TrueHD.

Any advice?

[clsid]

The known issues list of NVIDIA driver contains this for a long time already:
[NVIDIA Ampere GPU]: With the GPU connected to an HDMI 2.1 audio/video receiver, audio may drop out when playing back Dolby Atmos.

You can submit bug report to NVIDIA HERE (https://forms.gle/kJ9Bqcaicvjb82SdA).

[ryrynz]

Try performing a proper uninstall of your Nvidia drivers with DDU.

[Filmgeek47]

Any issues with the latest nvidia driver? Just clean installed kodi/MadVR and now the system seems to be stuck outputting srgb color space instead of BT2020 or 709.

[huhn]

sRGB and bt 709 have the same colorspace so you have to be more detailed when you share information.

[SamuriHL]

Sweet. That's a welcome fix.

[clsid]

AMD Adrenalin 22.8.1 has this in its changelog:
HDR is no longer compatible with 10-Bit Pixel Format. For the best user experience with HDR displays, it is recommended to disable 10-Bit Pixel Format in AMD Software: Adrenalin Edition Graphics Settings.
To clarify, this does not refer to or apply to the "color depth" setting in display settings.
It refers to "10-Bit Pixel Format" in Graphics > Advanced, which is for legacy OpenGL applications.
So not relevant for video playback.

[mclingo]

cheers for the info

[Goeggel]

Are there any known issues with the Nvidia GameReady 516.94 driver?

I have been using 511.79 for the last couple of months in gaming and watching MKVs without any issues whatsoever (RTX 2070 Super, Win10).
After updating to 516.94, gaming is fine, but MKVs are stuttering randomly from time to time.

Update: I am now back to 511.79 with just installing them over the 516.94 drivers -> no more stuttering in MKVs.

[Balling]

The known issues list of NVIDIA driver contains this for a long time already:


You can submit bug report to NVIDIA HERE (https://forms.gle/kJ9Bqcaicvjb82SdA).

This is a completly different bug and anyway this is due to dumb people not understanding that EARC is pc --> TV -> AVR, not PC -> AVR -> TV, besides bug is not present with Intel gpu going to AVR.

[Balling]

Any issues with the latest nvidia driver? Just clean installed kodi/MadVR and now the system seems to be stuck outputting srgb color space instead of BT2020 or 709.

How would you know that? HDMI mandates BT.2020 primaries when doing PQ (DCI-P3 and P3-D65 are only when SDR curve is used, PQ prohibits it per spec). So there is no way to know that. Also desktop is still not color managed on the input side, now thankfully we have SDR -> HDR upconvert including primaries change, but if you use WCG image it will not be applied! Even my dumb galaxy S21 FE does it on Natural profile! Not talking about MacOS that always supported it in every app and on desktop.

In fact samsung browser correctly does those https://www.wide-gamut.com/test and soon css will support p3 color too in Chrome (Safari already supports it)!

[mclingo]

dont feed the troll

[Plutotype]

Hi folks,
Thanks for the PDF, but reading it and the last 10 pages of this thread I could not figure out what is the last recommended Nvidia, AMD and Intel driver version ( madvr / JRVR user here ) and for which GPU/OS.
Thanks
Pluto

[Klaus1189]

Latent Nvidia is fine. AMD has Problems described in Post 1, other than that nothing to worry now.

Back when I startet the thread both Nvidia and AMD hat lots of problems.

[chros]

Take a look.at my signature what I use on Win10 1809.

[StainlessS]

Is there perhaps an error in OP PDF version number for 472.47 (there are two of them).
https://i.postimg.cc/nsv4CzC0/a3.jpg (https://postimg.cc/nsv4CzC0)

And from here [Official Advanced Driver Search | NVidia]:- https://www.nvidia.com/Download/Find.aspx?lang=en-uk#
https://i.postimg.cc/SjXvxLmr/b4.jpg (https://postimg.cc/SjXvxLmr)

472.84 from 2nd image seems to be latest standard WHQL Studio Driver, and given same date as the latest 472.47 in pdf, ie 13 Dec 2021.

EDIT: To Below, thanks :)

[Klaus1189]

You are right, I correct it soon, some problems now.

[GTPVHD]

https://blogs.windows.com/windowsexperience/2022/09/20/available-today-the-windows-11-2022-update/
https://www.microsoft.com/software-download/windows11

Windows 11 2022 Update Version 22H2 released, WDDM 3.1 and Shader Model 6.7.

[Balling]

22H2 also has support for HDR calibration with ICC profiles, finally! Color.org people are so slow.

WHY IS THE APP CALIBRATION ONLY min 0.005 NITS!??? Useless, my TV is 0.000006! Yes, PQ 65 is also below 0.00001 and 64 is black body 0 nits perfectly! Crazy!

[SamuriHL]

Only until Arc dies off. :)

[cesar73]

Recommendation needed for Nvidia firmware version without madvr HDR not switching off issue for geforce RTX 3060ti.

My HTPC configuration: Windows 10 LTSC 21H2, Kodi 17.7 dsplayer, madvr 0.92.17, lavfilter 0.76.1.25.
and LG oled G1 TV
Madvr settings: hdr passthrough, windowed mode ( had display issue with full screen exclusive)

I tried randomly different versions of nvidia firmwares compatible with rtx3060 ti cards ( with clean ddu driver deletion in between): 462.65 , 512.96 , and latest 516.94

Always same hdr issue: hdr activated correctly when video starts but remained enabled when video stops making kodi gui color saturated.

Any help will be appreciated

[brazen1]

Recommendation needed for Nvidia firmware version without madvr HDR not switching off issue for geforce RTX 3060ti.

My HTPC configuration: Windows 10 LTSC 21H2, Kodi 17.7 dsplayer, madvr 0.92.17, lavfilter 0.76.1.25.
and LG oled G1 TV
Madvr settings: hdr passthrough, windowed mode ( had display issue with full screen exclusive)

I tried randomly different versions of nvidia firmwares compatible with rtx3060 ti cards ( with clean ddu driver deletion in between): 462.65 , 512.96 , and latest 516.94

Always same hdr issue: hdr activated correctly when video starts but remained enabled when video stops making kodi gui color saturated.

Any help will be appreciated

Using Nvidia 517.48 with official Kodi v20 passing through madVR HDR mode engages when MPC-BE video is started and disengages when video has stopped.

Fwiw, I use the official Kodi internal VideoPlayer for HDR because there is no need for madVR when passing through. HDR mode engages and disengages using Windows HDR and/or Nvidia HDR and video is identical because it's passed through.

Besides, official Kodi handles iso's complete with menus. 17.7 DSP is getting pretty long-in-the-tooth. Expect problems imo.

[jayer]

I'm trying to figure out if any of the Nvidia drivers will work with my combination of Windows 10 21H1 and an RTX 3080 (12GB version) without breaking HDR? So far, every driver I've tried presents the 442.92 bug where SDR videos opened after playing an HDR video get played as HDR too. Makes me miss my old RTX 2080 (well, not really).

If non of the approved drivers for my 3080(12GB) can correctly handle the HDR/SDR switching, could I modify the installation file for one of the older drivers, like 442.74? Or would I likely cause even worse problems with my graphics card by trying to force it to use an older driver that isn't officially supported for my hardware?

Thanks in advance for any help/suggestions!

[nevcairiel]

This sounds like the good old madVR bug, not really a driver failure.

[Klaus1189]

Are the RX 5000 issues still present? Also do RX 6000 cards also still have these? I am referring to the ones described in first post.

[mclingo]

I have an RX5700 and have no issues with it at the moment at all, everything works as it should using LAV filters, EVR renderer, MPC renderer, MADVR , HDR SDR etc, however I dont run my TV is PC mode as I use TRUMOTION, this option is greyed out in PC, when i've tried PC mode in the past the colour space is all wrong but I havent tried it for ages, I doubt it will be fixed.

on latest driver, win10

[QBhd]

Same here... 5700XT, no PC mode on the TV (Banding is the main issue for me with PC mode)... everything works amazing

QB

[huhn]

you listed issues are still present.

there are even new ones very very odd ones.
if you take mpc-vr and set it to more than 8 bit internal bit deep the d3d11 and DXVA2 processing falls apart except if you downscale a lot.

this is the driver thread btw. so the pc mode part is well just that.
but nice to see that user here on this forum are now lying into other people faces.

i can only speak for 5000 series issue the 6000 may actually be perfectly fine just like the polaris series.

[Klaus1189]

So is it possible that the issues are also present in new RX 7000 series? All RDNA had these issues.
I just tested my old heater RX480 a few days ago and deinterlacing works, also frame adaptive, but if I watch a interlaced DVD I get some portions of the image where I see interlacing artefacts. These are strage roundly shaped areas. So not good deinterlacer and also bugged. There was or still is a screenshot in this thread, but I must look for it. I don‘t want to put the shitty Polaris back in just for a sreenshot.

I still do not know if those are hardware issues or „only“ software issues.

Also the Intel issue mentioned in post 1 … still present in new Intel driver?

I have also to mention that the Intel versions are driving me crazy! I don’t have an Intel CPU with iGPU here, just an old HEDT 4930k, so if anybody wants to test it, please let me know.

About the versions of Intel drivers, let me know if I should do anything different, I don‘t know any other way, but I don‘t like it that way.

[mclingo]

you listed issues are still present.

there are even new ones very very odd ones.
if you take mpc-vr and set it to more than 8 bit internal bit deep the d3d11 and DXVA2 processing falls apart except if you downscale a lot.

this is the driver thread btw. so the pc mode part is well just that.
but nice to see that user here on this forum are now lying into other people faces.

i can only speak for 5000 series issue the 6000 may actually be perfectly fine just like the polaris series.

whos lying, about what?

[huhn]

So is it possible that the issues are also present in new RX 7000 series? All RDNA had these issues.
I just tested my old heater RX480 a few days ago and deinterlacing works, also frame adaptive, but if I watch a interlaced DVD I get some portions of the image where I see interlacing artefacts. These are strage roundly shaped areas. So not good deinterlacer and also bugged. There was or still is a screenshot in this thread, but I must look for it. I don‘t want to put the shitty Polaris back in just for a sreenshot.

I still do not know if those are hardware issues or „only“ software issues.
you can easily assume a software issue the driver was always able to do bob or just weave(do nothing) and they simple don't care to change that. it was an option back in the CCC days.

the current state deint on win 11 22h2 with amd 22.10.1 5700 xt is:
madVR weave sometimes simple bob
mpc-hc EVR CP weave
mpc-hc EVR weave
mpcvr weave but different with massive ringing (i will retest with a current version)
windows media player bob
windows movies app bob
mpc-be EVR "working" atleast sometimes or it does this: https://abload.de/img/mpc-benhfej.png 16 bit format float.
with 10 bit int it works on the first playback doesn't artifact.

so the deintlacer is still available somewhere.

the level issue is now a different beast. it's now full range all the time. even when set to limited range only tested in mpc-be. so still broken but in a far more acceptable state.

it's kinda odd to see the "best" realtime deinterlacer work after all these years...

BTW. nvidia is also generally buggy with all DXVA and D3D11 processing with RGB output.
they move the chroma to the wrong position it's half or a quarter a subpixel to far to the right. like they move the image by half a subpixel before scaling instead of after scaler.
this bug is very old and very hard to explain to nvidia most user will never see an issue in it.

only tested on a 1060.

[el Filou]

whos lying, about what?I wouldn't say 'lie', but rather incorrect feedback.
Someone asks if the issues listed in the first post are solved, but deinterlacing isn't and some people respond with "everything works", but when you say that it may include things you're not using/have not tested.

[mclingo]

I wouldn't say 'lie', but rather incorrect feedback.
Someone asks if the issues listed in the first post are solved, but deinterlacing isn't and some people respond with "everything works", but when you say that it may include things you're not using/have not tested.

people can only give feedback from their own perspective and if whatever you're playing doesn't exhibit any problems then from your perspective there are no problems and it should not be implied or stated I'm a liar or have even given incorrect feedback, especially as I never actually said the weren't any other problems I just said I didn't have any.

[huhn]

no you have a very specific question with a sample and your answer is everything works general which plain lie.

you don't even have the decency to test this... and mention you didn't test it. but still good enough for a "everything works as it should be" statement.

[mclingo]

The question was - "Are the RX 5000 issues still present", I gave a subjective answer to that question and it was clear to anyone it was, you are the only one losing you childish Sh*t about this as you dont know how to have a grown up conversation with anyone.

[huhn]

thanks for confirming to troll have a nice day.

[Calvi]

I found HDR only worked on the first video play with 526.47 (i.e. would switch to HDR on first play of video, but after closing and opening again would not switch to HDR automatically again)
Going back to 525.25 has fixed it.

I need to install 526.47 again to make sure it wasn’t due to some other issue and haven't done exhaustive testing but wondering if anyone else is seeing the same issue?

Note: Windows 11 22H@ - RTX2700 - MadVR 0.92.17 32bit

[ryrynz]

Might be best to use DDU first if you want to upgrade to that particular driver on your system.

[Calvi]

Always do so that can’t be the cause.

[aquanash]

I just installed 526.47 and HDR switching is working fine, it switches on when playing and switches off when closing without issue multiple times in a row. Maybe the issue is the Win11 22H2 update? I am still running 21H2. After I update to 22H2 I will let you know if it breaks HDR switching for me. One other thing you can try is disabling MPO in the registry.

[aquanash]

I updated my Win11 install to 22H2 and HDR switching is still working fine with the 526.47 driver.

[huhn]

if you have an issue with win 11 h2 please try to install beta 165 and see if it goes away.
the driver version shouldn't matter to the fix bug but still worth a try.

[Calvi]

Thanks for the update, maybe it was something else.
I’ll try again.

[StainlessS]

I updated my Win11 install to 22H2 and HDR switching is still working fine with the 526.47 driver.

There is a later standard than 526.47,
Is there perhaps an error in OP PDF version number for 472.47 (there are two of them).
https://i.postimg.cc/nsv4CzC0/a3.jpg (https://postimg.cc/nsv4CzC0)

And from here [Official Advanced Driver Search | NVidia]:- https://www.nvidia.com/Download/Find.aspx?lang=en-uk#
https://i.postimg.cc/SjXvxLmr/b4.jpg (https://postimg.cc/SjXvxLmr)

472.84 from 2nd image seems to be latest standard WHQL Studio Driver, and given same date as the latest 472.47 in pdf, ie 13 Dec 2021.

EDIT: To Below, thanks :)
And the reply
You are right, I correct it soon, some problems now.
So the Opening post PDF is not yet updated. [I checked it]

Latest Std is
NVIDIA Studio Driver WHQL 472.84 13.12.2021

Advanced nvidia search [better than consumer search <more options> ]:- https://www.nvidia.com/Download/Find.aspx?lang=en-uk#

[Klaus1189]

Updated. Sorry I simply forgot about it. Everything is fine now. :)

[smithjohny039]

Welcome!

In this thread you can check for issues with graphic drivers from AMD, Intel and Nvidia.
This thread is meant for use with madVR and its compatible players like Zoom Player, PotPlayer, KMPlayer, MPC-HC and my personal favourite MPC-BE (https://forum.doom9.org/showthread.php?t=165890).

I had to create an external file, because the first two posts are limited and had no more space for new driver releases.

View PDF (https://drive.google.com/file/d/1gQZLfJ0w5KT7tBHCKZASSVU8vTnyPe2n/view?usp=sharing)

But hey, maybe some Driver Dev may stumble over my thread here, please read this:

AMD
Known limitations of Radeon RX 5000 and 6000 GPUs (older generations are fine):
• Hardware deinterlacing is broken in every driver version -> It is poor quality when applied to
interlaced video and it is not adaptive anymore, which is a NO-GO for HTPC usage.
You can check this issue yourself: Download this short MBAFF sample file (https://drive.google.com/file/d/12wO8NJbIrfa2MD4yVaA38RrBBdziCda8/view)
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 (https://thecapcut.com/capcut-mod-apk/)
See here (https://forum.doom9.org/showpost.php?p=1928654&postcount=2155) for more details
• 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.
This issue can be best seen on displays which want full range 0-255, like TVs in PC Mode (PC mode for full 4:4:4/RGB support, so you do not use color subsampling like 4:2:2 or 4:2:0)
Also overriding the range for test purposes in MPC-BE (video tab -> Output range) does not take effect.
Dear AMD, if any of your driver programmers read this: Please fix this fundamental video bugs .These are there since RX 5000 series launch.

I just tried the Windows default app "Movies and TV" and this app does not support frame adaptive deinterlacer at all. So best is to download MPC-BE and play the sample file. Windows default app "Movies and TV" really sucks.

Sorry Micro$oft, but with all the skilled and well paid developers you can only achieve this? This is ridiculous.

Intel
iGPU Intel UHD 770 in 12 gen CPU is broken for MPC-BE in use with EVR and EVR custom presenter. You get audio but the video is black.
To "solve" the issue is to rename MPC-BE to MPC-HC. Are you serious Intel? Do you really think that is the way of fixing bugs? That is ridiculous for the well paid developers of Intel!
See here for details:
https://sourceforge.net/p/mpcbe/tickets/912/

Nvidia
I am really impressed of what you have done to fix all the HTPC issues of the last 3 years, but I think a little more tweaking of the 23.976 Hz (called 23 Hz, but not 24 Hz!) to get more than 10 hours of no framedrop/repeat like AMD would be nice. I know you can do that.

If the issues still prevail, just try the old version.

[Klaus1189]

If the issues still prevail, just try the old version.

What do you mean? We tested lots of drivers through the months and the issues still persist.
Also on the first version which added support the GPU, so no way to get and older version than FIRST version which supports the GPU.

[x7007]

I've read about MPO , it's a stupid power-saving mode.

https://www.kernel.org/doc/html/next/gpu/amdgpu/display/mpo-overview.html


Note
Keep in mind that MPO is all about power-saving; if you want to learn more about power-save in the display context, check the link: Power.

[Ejziponken]

I found HDR only worked on the first video play with 526.47 (i.e. would switch to HDR on first play of video, but after closing and opening again would not switch to HDR automatically again)
Going back to 525.25 has fixed it.

I need to install 526.47 again to make sure it wasn’t due to some other issue and haven't done exhaustive testing but wondering if anyone else is seeing the same issue?

Note: Windows 11 22H@ - RTX2700 - MadVR 0.92.17 32bit

I'm having the same issue.

3080 12GB
Latest Win 10 Pro 22H2.
Nvidia 526.61 and 526.98
madVRhdrMeasure165

[Klaus1189]

I have just tested with latest 526.98 GRD on my system. I use MPC-BE latest stable (1.6.5.3) with madVR (latest stable 0.92.17). Works like it should. Open file, display switches to HDR, close, open another HDR file, working just fine.

Maybe DDU and install latest driver new? Try latest madVR stable?

Win 10 22H2, with all latest and also optional updates.

[Ejziponken]

I just rebooted and tested, it does seem to work now. Opening and closing and opening and HDR switching works... Hm.. Maybe its something else triggering it because It did not auto switch to HDR before my reboot.

I did install the latest Win 10 update tho.
https://support.microsoft.com/en-us/topic/november-15-2022-kb5020030-os-builds-19042-2311-19043-2311-19044-2311-and-19045-2311-preview-237a9048-f853-4e29-a3a2-62efdbea95e2

So either that update fixed it or something else is triggering the bug/issue.

[Calvi]

Yes, was not consistent for me either, seems ok after a reboot.
Am staying in 525.25 for now though as lots of other bugs in newer drivers being reported and I have no issues with this driver on a 2070.

[Klaus1189]

Which bugs? Should I include them?

Did you both a restart right after driver installation? Or later which fixed it then?

[Ejziponken]

After a few hours, playing games and browsing, the issue is back when I start a movie...

[Ejziponken]

Which bugs? Should I include them?

Did you both a restart right after driver installation? Or later which fixed it then?

I had the issue since the last two nvidia updates and I might have skipped one between those (im not sure). But yes I did multiple restarts since the installs and the issue comes back.

[Klaus1189]

Already tried DDU? What card do you have? Perhaps an issue of a single generation like Ampere, Pascal, ...

But if it goes away and comes back, that is not good. I also played games before testing, but no issue here.

[Calvi]

Which bugs? Should I include them?

Did you both a restart right after driver installation? Or later which fixed it then?

526.47:
Desktop Window Manager (dwm.exe) service may report higher GPU usage on some RTX 30- series configurations [3830387]
Workaround: disable Hardware-accelerated GPU Scheduling from the Windows Settings

Lots of people/gamers in the reddit thread with the above and stability issues that go away when rolling back to 525.25

526.98
Is not detecting 3060Ti cards.

You can include these if you wish.

I always install after DDU in safe mode so always a restart as well.

I’ll wait for the next release that’s more stable, I have a 2070 anyway so unless there’s any improvement related to video or windows 11 etc, no point me upgrading for new cards and games.

[Klaus1189]

OK, thanks for feedback. I add this asap.

I did some more tests. So your issue is that the display does not show that it is receiving HDR metadata (no HDR notification on display OSD)?
I ask because with madVR (latest stable 0.92.17) the image looks washed out despite the display showing HDR OSD info and madVR NV HDR in statistics.

When using MPC-VR the colors look OK, so is this a driver issue or a madVR issue? Or combination of both. Should I update to a newer madVR version to test? If yes, which one?

[Calvi]

OK, thanks for feedback. I add this asap.

I did some more tests. So your issue is that the display does not show that it is receiving HDR metadata (no HDR notification on display OSD)?


In my case the display did not show it was receiving HDR metadata and it was not, as the colours were washed out. I can tell easily anyway as the OSD on zoomplayer goes funky colours when in HDR mode.
If I force HDR in windows then it works again , but it’s forced so does not work for SDR, so no good esp when it worked automatically and faultlessly before.

It switched many times and then stopped at some point while I was showing someone HDR vs SDR demo’s.
525.25 and all earlier drivers do not do this for me.

Of course it could be MadVR, but MadVR and nvidia drivers have worked seamlessly since version 456.38 so I would say highly unlikely.

[Ejziponken]

OK, thanks for feedback. I add this asap.

I did some more tests. So your issue is that the display does not show that it is receiving HDR metadata (no HDR notification on display OSD)?
I ask because with madVR (latest stable 0.92.17) the image looks washed out despite the display showing HDR OSD info and madVR NV HDR in statistics.

When using MPC-VR the colors look OK, so is this a driver issue or a madVR issue? Or combination of both. Should I update to a newer madVR version to test? If yes, which one?

In my case, Im pretty sure it did show the HDR logo on my TV but it didnt switch to HDR colors.

[Whiskeyomega]

just to say I have the same issue with HDR colours not appearing sometimes. I have to reboot. im on 526.98 on a 3090. It just so happens to be at the same time I got a new TV replacement in the Samsung QN700B and until I found this thread thought it was the TV. Been looking for the problem for ages.

[Ejziponken]

To anyone with issues with HDR switching in the latest drivers:


Can you please fill out the driver feedback form an so that we can look into this?

https://forms.gle/kJ9Bqcaicvjb82SdA

Can you also download MediaInfo and export the codec information from one file that shows this issue and email it to driverfeedback@nvidia.com in case it is specific to certain video formats?
https://mediaarea.net/en/MediaInfo

[EpsilonX]

Hi, is this setting available in latest AMD Driver..?
It's for HDMI content reporting to display, these are the available options though not all always available (depends on display)...

Auto Select (Recommended)
Desktop Programs
Photos
Movies
Games
Full Screen-Videos


https://i.imgur.com/AQiJ1iq.png


It's not available for the RX580...
Thank you...

[huhn]

as far as i know no.

these usually only change the device picture mode to the matching name.
i personally only ever saw this working on panasonic TV other had this option but it did nothing.

i'm kinda happy AMD doesn't have it. on less point of failure.

[EpsilonX]

as far as i know no.

these usually only change the device picture mode to the matching name.
i personally only ever saw this working on panasonic TV other had this option but it did nothing.

i'm kinda happy AMD doesn't have it. on less point of failure.

For my desktop monitor, I always set it to Desktop Programs...
It's working with my Sony TV...
If I set it to Auto Select, my TV switch to Graphics picture mode on Desktop, and change to Game picture mode when I start a game...
With my RX580, the TV is set to Graphics picture mode all the time with no option to change it, that's why I ask... :D

I have this setup with 2 presets, one with image processing for video playback, and one without to lower input lag for gaming...
So far no solution if I opted for AMD for my next GPU... :D

[Klaus1189]

527.37 fixes HDR passthrough on 526.98 GRD and perhaps older drivers, but not many. So 522.25 was fine as far as I remember and also 526.47.

-> The only one affected could be 526.86.

I personally use only GRD, because I use my machine primarily for gaming and a new driver is always welcome :)

[SamuriHL]

WHY they keep breaking passthrough is beyond me...

[Klaus1189]

I tested with original Kodi (not DS or anything special) and it was fine with 526.98 GRD. So the HDR passthrough issue which sometimes returns at some new versions seems to be limited to madVR. It is strange, but Nvidia fixes it and that is all I care.

[SamuriHL]

To be fair, part of that is the fact that madvr has not really been updated to handle HDR "properly". The nVidia fix is to keep putting in a fix specifically for madvr. But it's not like they don't know it's needed each time they release a driver.

[Ejziponken]

Same HDR switching issue with latest driver.

[Klaus1189]

Not for me, it is working with latest 527.37, but I tried various things and tested again and again ... and now I can confirm that something is not fully fine, because after I launched GTA V the HDR stopped working, a restart fixes this. And again the Display reports HDR info OSD but not actual the true colors. But as mentioned, a restart "fixes" this.

[Ejziponken]

Not for me, it is working with latest 527.37, but I tried various things and tested again and again ... and now I can confirm that something is not fully fine, because after I launched GTA V the HDR stopped working, a restart fixes this. And again the Display reports HDR info OSD but not actual the true colors. But as mentioned, a restart "fixes" this.

A PC reboot always fixed the issue for me, even in the other two drivers. Its still an issue because it comes back after a few hours.

[Klaus1189]

The other drivers never worked for me. Even after restart.

[Klaus1189]

I tested new 527.56 GRD and it loks like HDR passthrough is fixed completely for madVR. Kodi HDR switching worked fine also on "affected" drivers. I tested a few games (also GTA V like before), no changes what so ever on my system like ghames settings or anything else, just new driver and it works fine for me.

I can also test, if the issue comes back after many hours of pc running and test then, but not today, maybe tomorrow, how many hours should I test? -> @Ejziponken

I get more and more the idea that a dev at Nvidia is reading this thread ... :)

[huhn]

if you really think nvidia reads this let me try this:

can you please not move the chroma by half a subpixel in DXVA before chroma scaling but after while this is 4x faster it places the chroma in the wrong position. if it is done before chroma scaling it needs to be 0.25.

this bug is about a decade old maybe longer.

[Goeggel]

Are there any known issues with the Nvidia GameReady 516.94 driver?

I have been using 511.79 for the last couple of months in gaming and watching MKVs without any issues whatsoever (RTX 2070 Super, Win10).
After updating to 516.94, gaming is fine, but MKVs are stuttering randomly from time to time.

Update: I am now back to 511.79 with just installing them over the 516.94 drivers -> no more stuttering in MKVs.

I have made a new attempt at updating from 511.79 to 522.25 GDR (read somewhere in this thread that this was a version supposedly without any issues). But I now get the micro-stutters in MKVs again.
Maybe every couple of minutes, it's hardly noticeable, but they are defnitely there. Rewinding the affected scene, and they are gone. So it seems completely random.

Anyone having an idea where this issue could be coming from or how to tackle it?

[huhn]

power settings
none forced vsync i my first guesses.

[Klaus1189]

@huhn: could you post screenshots of sample video which shows the differences when using the wrong method and the right method? And of course the samplefile itself, so I and probably NVIDIA can test. Not a specialist in this topic. But I am interested, maybe we are lucky :)

[el Filou]

if you really think nvidia reads this let me try this:

can you please not move the chroma by half a subpixel in DXVA before chroma scaling but after while this is 4x faster it places the chroma in the wrong position. if it is done before chroma scaling it needs to be 0.25.

this bug is about a decade old maybe longer.I think they don't care about this because it only happens with DXVA2 and not D3D11 and Microsoft says apps are supposed to migrate to D3D11 at least or something like this.
Just like AMD and their DXVA2 deinterlacing/scaling.

[huhn]

happens with d3d11 too.
and AMD is deint is broken on d3d11 too.

i make images later.

[huhn]

mpcVR is used here:
image is take from here: https://forum.videohelp.com/threads/294144-Viewing-tests-and-sample-files

subsampled using lavfilter by forcing nv12 output.
catmull-rom: https://abload.de/img/catmull-romd7cu2.png
d3d11: https://abload.de/img/d3d11sbicq.png

i could now go and turn this png into a 420 still video but nope.

[senzaparole]

Hi guys. I have a problem. After allowing several updates I noticed that my TV no longer automatically switches to HDR mode.
I have a PC connected to LG TV. does anyone know how i can fix it?

Edit
I solved. It was an AMD driver update (Adrenalin 22.5.1). I unistalled them and now everything works fine. I installed AMD driver older... About a year ago.

[Goeggel]

I have made a new attempt at updating from 511.79 to 522.25 GDR (read somewhere in this thread that this was a version supposedly without any issues). But I now get the micro-stutters in MKVs again.
Maybe every couple of minutes, it's hardly noticeable, but they are defnitely there. Rewinding the affected scene, and they are gone. So it seems completely random.

Anyone having an idea where this issue could be coming from or how to tackle it?

I am still troubleshooting this issue. What settings are recommended for LAV Video (DXVA2 etc.) and MadVR (Rendering general settings) with Nvidia drivers?

Currently I am using these settings: https://imgur.com/a/P2Boj4f

[huhn]

the lav filter settings depend on what you want.
your current ones are just fine.
you could use d3d11 native which will break deint and blackbar detection but else could be faster while everything will work with DXVA2 copyback.

the difference between D3D11 copyback and DXVA2 copyback is trivial.
i'm not ware of a single real world test where this shows a difference.

your stutter issue should be part of madVR and nvidia setting try to force deint and use a presentation buffer between 1-3.
it should go away.

[EpsilonX]

the level issue is now a different beast. it's now full range all the time. even when set to limited range only tested in mpc-be. so still broken but in a far more acceptable state.


So, if all my monitors and TV (especially) are set to Full Range, I wont have any problem right..?

[huhn]

assuming your display is setup correctly yes.

or you use a video renderer that doesn't care about DXVA stuff like mpcVR or madVR.

there are allso issue with forced post processing with ruins levels and such but these heavily depends on the application.

for vivaldi is was unbeatable on mpc-be using EVR is was not present last time i checked but again just sue mpcVR or madVR.

[EpsilonX]

assuming your display is setup correctly yes.

or you use a video renderer that doesn't care about DXVA stuff like mpcVR or madVR.

there are allso issue with forced post processing with ruins levels and such but these heavily depends on the application.

for vivaldi is was unbeatable on mpc-be using EVR is was not present last time i checked but again just sue mpcVR or madVR.

Nice, I use mainly PotPlayer/MPC-BE with MPCVR/MadVR... :D
Currently testing PotPlayer+MPCVR+LAV...
Thank you for the very swift response... :D

[clsid]

MPCVR uses the DXVA2/D3D11 video processor by default.

[EpsilonX]

MPCVR uses the DXVA2/D3D11 video processor by default.

It won't matter if the GPU driver and TV are both set to Full Range, right..? :confused:
PotPlayer + MPCVR (Jinc2m) + LavFilters (D3D11)...
Getting a 6800XT, now this reply makes me confused as hell..

[huhn]

MPCVR uses the DXVA2/D3D11 video processor by default.

volt recommend to disable it. and it is for reasons unknown to me not affect by the GPU driver video settings.
the GPU driver video setting don't have a off function or a preset that doesn't do anything. typical AMD issues which are truely just dumb oversights...

disable video processing in mpcVR you are save from everything that the GPU driver does. my 5700 XT has only odd bugs but the video settings from the driver are ignored. also think about activating deint in lavfilter or something because without a hardware video processer you lose that option.

this is really confusing stuff that shouldn't exist in the first place. these issue where fixed for nvidia cards a decade ago where they final snap out of it and set video stuff to off by default.

don't remind me of jinc2 what have i done...

[EpsilonX]

volt recommend to disable it. and it is for reasons unknown to me not affect by the GPU driver video settings.
the GPU driver video setting don't have a off function or a preset that doesn't do anything. typical AMD issues which are truely just dumb oversights...

disable video processing in mpcVR you are save from everything that the GPU driver does. my 5700 XT has only odd bugs but the video settings from the driver are ignored. also think about activating deint in lavfilter or something because without a hardware video processer you lose that option.

this is really confusing stuff that shouldn't exist in the first place. these issue where fixed for nvidia cards a decade ago where they final snap out of it and set video stuff to off by default.

don't remind me of jinc2 what have i done...

MPCVR have only have 2 "primary" options right..?

"Use Direct3D11" checked = D3D11 VP
"Use Direct3D11" unchecked = DXVA2 VP

"use for resizing" checked = D3D11/DXVA2 scaling
"use for resizing" unchecked = Shaders scaling (Jinc2m,Lanczos,etc)

What do you mean by disable..?
In my case, I must enable "Use Direct3D11", or else it won't activate HDR...

[huhn]

you go to DXVA2 and D3D11 video processor and disable everything under "use for:"

[EpsilonX]

you go to DXVA2 and D3D11 video processor and disable everything under "use for:"

Only 1 "use for"... :confused:

https://i.imgur.com/HlcBjaA.png
https://imgur.com/HlcBjaA

This is my current settings, D3D11 with Shaders scaling

[huhn]

disable nv12 p010/p016 yuy2 other supported formats

[EpsilonX]

disable nv12 p010/p016 yuy2 other supported formats

What, never knew we can disable all of that and still play... :stupid:
Thank you for the new knowledge :D

[EpsilonX]

OK, what is the 100% fool proof combination to show the elevated black caused by 16-235..?
MPC-BE + EVR-CP + DXVA..?

[huhn]

but limited range output doesn't have to be elevated blacks.

setting the GPU to limited and the playback software should show a major difference between a normal image and the same image loaded in the player that is set to output limited.
http://www.lagom.nl/lcd-test/black.php

your you just get a meter.

[EpsilonX]

Brief testing using simple MPC-HC + EVR + DVXA, the output shown in my TV is correct (not washed out or too dark)... :D
This is with 6800XT driver "Pixel Format" setting matching the TV's setting, Full-Full or Limited-Limited, both 4:4:4...
And yeah, the deinterlacer is useless...

@huhn
Remember when you said you prefer AMD didn't have the HDMI content setting..?
Well now they have it, but Auto only... :rolleyes:
Everytime an app uses 3D textures fullscreen (e.g Games, Media Player), it AUTOMATICALLY engages ALLM mode with TV/AVR that supports it (HDMI 2.1), and automatically LOCKED the TV setting to GAME... :eek:
So if the TV have a poor Game mode color accuracy / dimming quality, then you can't change to other mode... :cool:

[huhn]

i have no word except did you expect better?
trust my there even was a developer that wrote the forced auto type and hit him self on the shoulder for this good work.

[aquanash]

Is anyone else still seeing HDR passthrough issues with nvidia driver 527.56? It stops working for me randomly every few days and I have to restart to get HDR working again. The previous driver it happened more often, but the newest driver doesn't seem to completely fix it and it still happens every so often. I'm seeing this on 2 different machines both running 527.56.

[Klaus1189]

No, not for me, but it could be a Game or program which could lead to this behavior. Check what game or program you started after it worked and before it didn't work anymore.

[Klaus1189]

Does HDR auto switch of madVR work with Intel GPUs? I want to fiddle around/experiment with an Intel ARC :D

[ryrynz]

Does HDR auto switch of madVR work with Intel GPUs? I want to fiddle around/experiment with an Intel ARC :DLooks like you're the first [emoji23]
Report back ur findings.

Sent from my Pixel 7 Pro using Tapatalk

[aquanash]

No, not for me, but it could be a Game or program which could lead to this behavior. Check what game or program you started after it worked and before it didn't work anymore.

On both machines I didn't open any games (since last reboot) before it happened. I used basically only Chome and MPC-HC (latest clsid2 version) so I'm not sure what could trigger the issue. I wonder if the Win11 22H2 update could be the cause since I updated both machines recently also.

[Klaus1189]

I am still on Windows 10 on my main machine

[AuRiMaS666]

Hello everyone,

So, I'm also having this HDR passthrough randomly not working anymore problem. In addition to people a few pages back on this thread, I have found a few reports on AVSForum and Reddit (links below) as well. I've made a more detailed post about it in a link below.

I have moved to Win11 at the start of December, but I do remember this happening at least a couple of times while still on Win10, so it doesn't seem to be Win11 exclusive thing. Also another thing I noticed, that pretty much all people reporting in have RTX 30 series cards, if that matters in any capacity.

https://www.avsforum.com/threads/madvr-hdr-passthrough-shows-incorrect-colors-if-display-has-been-turned-off-requiring-reboot.3260442/

https://www.reddit.com/r/htpc/comments/zps4wb/hdr_passthrough_only_partly_working_sometimes/

https://www.reddit.com/r/htpc/comments/yt60h5/mpcbemadvrgeforce_rtx_3080_tiwindows_10_hdr/

[Klaus1189]

https://www.youtube.com/watch?v=kN_hDw7GrYA&t=1330s
The gloating smile on his face to make fun of Nvidia, Karma is a bitch:
ENGLISH: https://www.youtube.com/watch?v=26Lxydc-3K8
GERMAN: https://www.youtube.com/watch?v=_2ggdOyzpYQ

[aquanash]

Also another thing I noticed, that pretty much all people reporting in have RTX 30 series cards, if that matters in any capacity.

I'm seeing the issue on my machine with a 10 series card also and it happens just as much as my other machine with a 30 series card. I don't think the issue is specific to a certain series. Both my machines are running Win11 22H2 and I didn't see the issue happen on either until recent nvidia driver and the Win11 22H2 updates. I updated both the driver and to Win11 22H2 (from Win11 21H2) at the same time on both so I'm not able to narrow down which one is the culprit. I may try downgrading the driver on one of them to see if it's the driver.

[Klaus1189]

22H2 can be Win 10 or Win 11. Please specify more.

[aquanash]

22H2 can be Win 10 or Win 11. Please specify more.

I updated my last post with more info to specify exactly which version of Windows I'm referring to. On both machines I went from Win11 21H2 to Win11 22H2 when the issue started. I also went from nvidia driver 516.93 to 527.56 on both at the same time I updated Windows. I just downgraded my series 10 machine back to 516.93 and will report back if I see the HDR passthrough issue happen again or not with the old driver on Win11 22H2.

[ryrynz]

Wouldn't surprise me if a proper DDU process fixed these HDR issues. I've had zero issues with the 3060 and W11.

Sent from my Pixel 7 Pro using Tapatalk

[Klaus1189]

Update for Vapor Chamber RX 7900 XT(X)
ENGLISH: https://www.youtube.com/watch?v=rxaDZ6n2MNo
GERMAN: https://www.youtube.com/watch?v=W2clMKAxL1c

[Klaus1189]

Don't get me wrong, I got also one of these Reference RX 7900 series and it is fine. Hotspot is 78° C and only 12° C Delta. So it is fine. I don't want to bash AMD.

[Calvi]

7900…
Does deinterlacing work?
How does it perform with MadVR?

[Klaus1189]

Please wait :), too much other stuff I must do

[Calvi]

No, problem.

Also curious about HDR switching, 23Hz etc when you get a chance to test.

[Ejziponken]

I just tried the new 528.02 driver and I still get the HDR switching issue. Still fine once I go back to an older driver like the 522.25.

I watched a HDR movie with mpc+madvr and it was fine. After that I watched some SDR content and a few hours later I tried HDR content again and it wouldnt switch. Just like all the latest drivers.
I didnt even play any games today so its not a game that triggers the issue from what I can tell.

[Klaus1189]

Anybody has an RTX20 series card who is willing to test?
RTX30 series is affected.

[Klaus1189]

I test my 7900 XTX this week. Just chilling now from work and from sanitizing the third room in one week.

https://youtu.be/pQDnwpc_k4E

[Calvi]

Anybody has an RTX20 series card who is willing to test?
RTX30 series is affected.
I have this issue with RTX2070, Drivers >525.25.
I haven’t specifically tested 528.02 but take Ejziponken‘s word for it as symptoms are identical to previous drivers I tried.

[Calvi]

Wouldn't surprise me if a proper DDU process fixed these HDR issues. I've had zero issues with the 3060 and W11.

Sent from my Pixel 7 Pro using Tapatalk

I always DDU/Safemode every driver update.

The HDR switching can work for quite a while before it breaks.
I was showing someone SDR vs HDR and after viewing about 10 different videos it stopped switching.

No doubt it could also be something very specific causing it that you may not have. Be good to know what it is, it’s just time consuming to DDU and then test multiple files to try and replicate.

[aquanash]

The HDR switching issue is most definitely a bug in the newer nvidia drivers (>525.25 as Calvi pointed out) that is now confirmed on 10, 20 and 30 series cards (doesn't seem hardware specific). After I rolled back my 10 series machine to an old driver (516.93) the issue no longer happens after many days without a reboot and playing many SDR and HDR videos. I originally thought it may be related to the new Win11 22H2 update, but after downgrading the nvidia driver the issue went away, even with Win11 22H2.

I'm guessing a lot of people don't see this issue because they don't leave their machines running for days at a time. You'll never see the issue if you shutdown/reboot every couple days. I have to leave my machines running continuously for a few days before the bug is triggered, but this has never been an issue with older nvidia drivers (<=525.25).

[Calvi]

Exactly, my HTPC hibernates whenever we close Kodi so effectively (almost) never reboots.

[ryrynz]

I always DDU/Safemode every driver update.


I shutdown my pc after every use so could be that..

[Ejziponken]

The HDR switching issue is most definitely a bug in the newer nvidia drivers (>525.25 as Calvi pointed out) that is now confirmed on 10, 20 and 30 series cards (doesn't seem hardware specific). After I rolled back my 10 series machine to an old driver (516.93) the issue no longer happens after many days without a reboot and playing many SDR and HDR videos. I originally thought it may be related to the new Win11 22H2 update, but after downgrading the nvidia driver the issue went away, even with Win11 22H2.

I'm guessing a lot of people don't see this issue because they don't leave their machines running for days at a time. You'll never see the issue if you shutdown/reboot every couple days. I have to leave my machines running continuously for a few days before the bug is triggered, but this has never been an issue with older nvidia drivers (<=525.25).

I get the issue after just a few hours. So people should notice. :P

[Calvi]

I shutdown my pc after every use so could be that..

Maybe, would be good to know. I only watch typically 3 shows a night (and rarely more than 1 HDR) so if I shut down after each time probably wouldn’t trigger the issue myself.

Shame this bug has crept in as everything was improving nicely with new driver versions generally.

[ryrynz]

I upgraded to 528.02, didn't use any DDU in the process. Last night I saw two random black screens for a second or so, Ive switched back to 527.56.

[Klaus1189]

That are not good news :(

Too many issues right now.

I test my 7900 XTX today or tomorrow

[Ejziponken]

I switched over to mpv player and HDR seems to work with latest driver. Its a hassle to set up... But I guess Its worth it to be able to run the latest driver. Who knows when Nvidia/Madvr is gonna fix the issue.

[Klaus1189]

Kodi works for sure also

[mclingo]

Hi, i've been noticing some audio dropouts on my system recently, seem to be a similar issue to here where it mainly happens when connected to an AUDIO receiver, seem to be all 5700 series cards and possible 6000 too. I'm getting one of two momentary dropouts per movie, sometimes 3. I was getting none at all when using KODIDS/MADVR/bitstreaming but i've had one or two there now as well. I've tried a few things to resolve this but nothing works, seems to be an issue on a hardware level.

does anyone else have any issues with AMD 5000 / 6000 series cards connect to a receiver either using bitstreaming or just PCM?

I was going to pop and old AMD card in by the side of it and use the audio from that over HDMI but my motherboard doesnt seem to want to recognise a second card. Just have to hope they finally fix it with the 7000 series but I think its unlikely, i'd move to NVIDIA but the 3D fix looks unreliable and I've never managed to get 23,976 timings anywhere near good enough for me.

this seems to be the main thread on the issue:

https://community.amd.com/t5/graphics/rx5700-and-hdmi-sound-problem/td-p/308252?messageTarget=all&mode=comments&start=0

[SirMaster]

Hmm, I wish I had more info to contribute...

However I can say that I am on Windows 10, latest drivers with RTX 3080 and have had 0 issues with HDR passthrough and automatic switching between HDR and SDR via MPC-HC and madVR.

I have never seen an issue with it and I update to each new driver normally.

[Ejziponken]

Upgraded to win11. Still broken HDR switching. xD

[Klaus1189]

Exacty same or any different behavior?

[Klaus1189]

A bit late, but I finally found time to build together a rig from spare parts and I tested hardware deinterlacer of 7900 XTX and it works. But only when using DXVA2 not when using D3D11cb or D3D11. Hardware acceleration for SD MPEG 2 does not work, also not deinterlacing. But I must investigate it further. But not today, on some other day. Tired from work.

[aquanash]

I just found that restarting the nvidia display device after the HDR switching bug happens will also clear up the issue if you don't want to do a full reboot.

Unfortunately the Windows keyboard shotcut (win+ctrl+shift+b) doesn't clear it up, but if you restart the video card with the "pnputil" command line utility it will clear it up and HDR switching should work fine again for awhile without having to reboot.

If you want to try this workaround, first run this command to get the "Instance ID" of your nvidia display device:

pnputil /enum-devices /class Display

Then run the following command in a command prompt with admin rights, replacing <instance id> with your cards id, to restart it:

pnputil /restart-device "<instance id>"

Example:
pnputil /restart-device "PCI\VEN_10DE&DEV_1B80&SUBSYS_62863842&REV_A1\4&fa0c5&0&0008"

The restart command can be saved in a batch file if you want a quick way to run it. Just make sure it runs as administator by right clicking that bat file and selecting "Run as administator" or setup a shortcut to it that will run as admin automatically.

[Klaus1189]

What happened to latest AMD driver for 7900 series? I got an Email for 23.1.2, but I can not find the driver to download on offical site. I found a link on changlog site but not of product site.
Just curious, have a better Nvidia too, but strange ...

[AuRiMaS666]

I just found that restarting the nvidia display device after the HDR switching bug happens will also clear up the issue if you don't want to do a full reboot.

Unfortunately the Windows keyboard shotcut (win+ctrl+shift+b) doesn't clear it up, but if you restart the video card with the "pnputil" command line utility it will clear it up and HDR switching should work fine again for awhile without having to reboot.

If you want to try this workaround, first run this command to get the "Instance ID" of your nvidia display device:

pnputil /enum-devices /class Display

Then run the following command in a command prompt with admin rights, replacing <instance id> with your cards id, to restart it:

pnputil /restart-device "<instance id>"

Example:
pnputil /restart-device "PCI\VEN_10DE&DEV_1B80&SUBSYS_62863842&REV_A1\4&fa0c5&0&0008"

The restart command can be saved in a batch file if you want a quick way to run it. Just make sure it runs as administator by right clicking that bat file and selecting "Run as administator" or setup a shortcut to it that will run as admin automatically.

This is a golden tip for guys like me who hate doing full reboots, very grateful! Will make it much easier to deal with this while waiting for a fix, if it ever comes.

[mclingo]

it was there when I looked, have you tested the card yet, anything fixed?

[Klaus1189]

Yes, deinterlacer is frame adaptive. So much better than RX 5000 and 6000 series.
My 7900XTX is very strong, but so i my 4090 FE ;)

[mclingo]

interesting, I might look at a 7700XT when the finally come out.

[Betroz]

I am upgrading my computer soon and was wondering if Windows 10 still is better for MadVr use over Windows 11? Anyone tested the 528.49 WHQL driver?

[ryrynz]

I am upgrading my computer soon and was wondering if Windows 10 still is better for MadVr use over Windows 11? Anyone tested the 528.49 WHQL driver?

Nothing wrong with 11 and yes, just upgraded and it's working fine.

[huhn]

if you are not planning on using the beta version upgrading to win 11 could be the biggest mistake you could make.

depending on how lucky you are you may end up with a totally broken device page.

[Betroz]

if you are not planning on using the beta version upgrading to win 11 could be the biggest mistake you could make.

depending on how lucky you are you may end up with a totally broken device page.

Beta version of what?

[ryrynz]

Beta version of what?Beta tonemapping builds of MadVR. If you use the stable version it has a bug where devices keep being added on Windows 11 and you have to manually remove them at some point. Wasn't that big of a deal but if you want to use the stable then 10 would be less hassle.

[Betroz]

Beta tonemapping builds of MadVR. If you use the stable version it has a bug where devices keep being added on Windows 11 and you have to manually remove them at some point. Wasn't that big of a deal but if you want to use the stable then 10 would be less hassle.

That was new to me, but ~90% of my content are SDR. Well I will install Win11 and take a backup image with Acronis, so if I get any problems I can roll back. Or install Win10 again if things get really bad.

Too bad no new versions of MadVr will be coming out... So it is what it is.

[ryrynz]

They are being released, just nothing without a few month time limit on them. A quality of life bug fix build would be welcome but that could be years away if ever, I use the betas just for those fixes.

[Betroz]

They are being released, just nothing without a few month time limit on them. A quality of life bug fix build would be welcome but that could be years away if ever, I use the betas just for those fixes.

Sorry if I were unclear, but I was NOT talking about this MadVR hdr Measure program/add on. The lastest MadVr release v0.92.17 from 2018 is what I meant. But whatever, it works still so.

[ryrynz]

Sorry if I were unclear

These are new versions of madVR not the measurement program.

[Betroz]

These are new versions of madVR not the measurement program.

Are you trolling me...? On Madvr.com v0.92.17 is the newest.