AMD, Intel and Nvidia driver issues and last recommended version

[SamuriHL]

My setup is through a vrroom. The 3080 is input to the vrroom. Hdmi audio out from vrroom to my hdmi 2.0 avr. Audio to the hdmi 2.1 display muted through the vrroom. I have dropouts.

Sent from my SM-G998U1 using Tapatalk

[Klaus1189]

With LAV Filters and/or MPC-BE internal Filters

[Manni]

Nevcairiel confirmed in the jRiver thread I linked to above that the LAV improvements in the recent version had already been fixed in jRiver MC in a different way, and that the issue fixed (same Atmos drop in the same scene with all hardware) would have happened with the 1080ti as well. So that won't change the drop outs I experience with jRiver with the 3090 (or the 4070) as I was using jRiver to test and the drops don't happen in the same place all the time. However, it might have been why the dropouts in John Wick 3 stopped, as these were always in the same place (and more frequent), so that was indeed an improvement, but it was brought to jRiver MC before this latest LAV Filter version.

In other words, the latest LAV filters would only bring an improvement if you don't use jRiver. If you do, these improvements were brought in earlier.

[SamuriHL]

I use JRiver so the newest LAV version probably didn't change anything. I still get dropouts randomly as well. Something about these new RTX cards is just whacked with audio.

[Klaus1189]

So do you test MPC-BE internal Filters?? Not LAV or JRiver?

[SamuriHL]

I don't have MPC-BE installed and really have no need to. I use JRVR for every day watching which is only in JRiver. I'm sure others can test MPC-BE internal filters. if it changes the equation, that would be interesting.

[Klaus1189]

Using only one approach and conclude it is a driver issue is not the way to go.
MPC-BE can be installed portable.
Another good choice is Kodi.

[SamuriHL]

I didn't conclude anything in my case. I simply commented that I get dropouts in my setup. Whether it's a jriver thing, lav filter thing, driver thing, configuration thing, avr thing, or some phase of the moon problem remains to be seen. I'll wait for others to make conclusions about the cause.

Sent from my SM-G998U1 using Tapatalk

[Manni]

Using only one approach and conclude it is a driver issue is not the way to go.
MPC-BE can be installed portable.
Another good choice is Kodi.

The only one concluding it’s the driver is Jim at jRiver. I certainly don’t, given that the same driver works flawlessly with my 1080ti and doesn’t prevent the 3090 or the 4070 from causing ATMOS drop outs.

The problem with testing other software that you don’t use routinely (like MPC-BE in my case or in SamuriHL’s case) is that tests can be inconclusive or deceptive unless you actually watch many films with that software.

I only watch films with jRiver (apart from bd menus support, though it’s connected) because I want the right forced subs to be played from my bd folders. I’m not going to spend hours and hours watching the same content to test a software that I’m never going to use otherwise.

I did try, and (possibly incorrectly) concluded that there was no drop outs with MPC-BE simply because I had no drop outs at the time for 30-40 minutes, but it doesn’t mean that there is no drop outs.

I even managed to watch a couple of LOTR movies with the 3090 and experienced no drop outs, before they came back with a vengeance.

So apart from spending a week testing and watching many films, there is no way to know.

Someone might want to do this to test your theory, but I won’t. I spent weeks testing this, and I’ll put the 3090 back only when someone reports that it works, and provides all their settings.

Until then, for whatever reason (lost likely an incorrect able hardware issue in ampere and Lovelace as far as I’m concerned) bitstreaming ATMOS isn’t possible on these without drop outs.

No one has come forward saying they have no issue with these. That speaks volume.

[nevcairiel]

General rule of the internet, people without problems wont usually come to complain :D

[Manni]

General rule of the internet, people without problems wont usually come to complain :D

Sure, but at least you or someone else could know a friend who is able to bitstream Atmos through an AVR with a 3xxx or 4xxx GPU without any issue... You see what I mean?

Usually when you post about a problem that isn't for everyone, you get at least one person stepping forward and saying "Works fine for me". Nothing like that with this Atmos bitstreaming issue with 3xxx and 4xxx GPUs.

The problem is that the user base is small: you have to have a 3xxx or 4xxx GPU, use a HTPC as a source and bitstream ATMOS through a 2.1 AVR (or a 2.1 switch that goes to a 2.0 AVR and a 2.1 display, as for SamuriHL). How many people fit that description?

That's probably why no one is in a hurry to fix this.

[SamuriHL]

I wonder if it's related to FRL at all. In my configuration I use my HTPC for gaming so I have gsync/vrr enabled. JRiver sets it to 23.976 when a movie starts but gsync/vrr is still technically enabled. Just throwing another possible idea out there.

[Manni]

I wonder if it's related to FRL at all. In my configuration I use my HTPC for gaming so I have gsync/vrr enabled. JRiver sets it to 23.976 when a movie starts but gsync/vrr is still technically enabled. Just throwing another possible idea out there.

I disable Gsync in the nVidia CP settings and have vertical sync on. I still have the Atmos drop outs issue with the 3090/4070, even when going through a HDMI 2.0 input in the AVR.

Nothing to do with FRL given that it also happens with 18Gbs speeds (TDMS) and no VRR. Though the bug in the recent nVidia drivers with 4K23 12bits in that configuration (HDMI 2.1 GPU going through HDMI 2.0 AVR input) adds insult to injury and should be avoided, until fixed by nVida (that's DEFINITELY a driver issue).

[SamuriHL]

I figured I'd at least throw out a possible idea given that it's happening on 3x and 4x series cards. I'm using 10 bit RGB FULL right now for my settings. With gsync enabled.

[Charky]

3090 (latest drivers) -> Denon X2800H -> LG 65C2.

Atmos setup with dedicated speakers. Everyhing is bitstreamed.

Everything seems to be working normally. No "dropouts", whatever that means. My AVR still display "Atmos" and I didn't hear anything wrong. That goes with both MPC-BE/madvr and Jriver/JRVR (I currently use both, haven't decided on a favorite yet, but I like having several options, considering madvr is dead).

[Manni]

3090 (latest drivers) -> Denon X2800H -> LG 65C2.

Atmos setup with dedicated speakers. Everyhing is bitstreamed.

Everything seems to be working normally. No "dropouts", whatever that means. My AVR still display "Atmos" and I didn't hear anything wrong. That goes with both MPC-BE/madvr and Jriver/JRVR (I currently use both, haven't decided on a favorite yet, but I like having several options, considering madvr is dead).

Thanks Charky for stepping forward :)

Assuming that you've played a full Atmos film many times (it currently often takes at least one hour to get an Atmos drop out in jRiver), please could you provide more details:
Exact OS version (Win 10 or Win 11, Pro or not, build etc)
Exact Driver version and type (standard or DCH, game ready or studio)
Exact settings in the nVidia Cpanel, especially vsync, gsync, power
Exact settings for resolution (4K, refresh rate, bit depth, RGB or YCC)
Exact setting for bitstreaming in jRiver (which audio device do you select, is it using WASAPI or Direct Sound)

Please focus on jRiver with JRVR. As Nevcairiel/Hendrik requested a log in the jRiver thread, I've done more tests today with both jRiver (using JRVR to rule out madVR) and MPC-BE.

See all the details here: https://yabb.jriver.com/interact/index.php/topic,136525.100.html from post #128.

I get Atmos drop outs around the one hour mark with jRiver, worst results with MPC-BE with internal filters and best results (least dropped frames, no Atmos audio drop) with MPC-BE using the latest version of LAV Filters (0.77.2.3).

This seems to point to an issue specific to jRiver rather than a driver issue, so I suggest you post all the info requested above in the jRiver thread linked above, once you've confirmed that you don't get any audio drop outs, so that NevCairiel/Hendrik gets all the info in the same place.

That way, those interested (most likely jRiver users, like myself, yourself or SamuriHL) can follow that thread and we won't spam the others here as it's likely irrelevant.

Of course, if anyone gets Atmos drop outs using the latest version of LAV 0.77.2.3 and MPC-BE and the latest nVidia drivers, feel free to post here or even to create another thread and link it here.

[SamuriHL]

Manni do you get any dropouts in DTS formats? I was watching Atomic Blonde last night and I got a bunch of dropouts in the DTS:X track. I've never usually had an issue with DTS based audio.

[Manni]

Manni do you get any dropouts in DTS formats? I was watching Atomic Blonde last night and I got a bunch of dropouts in the DTS:X track. I've never usually had an issue with DTS based audio.

I could try watching Atomic Blonde, there are worse films to watch again and I'm getting tired of John Wick 3 :)

I haven't experienced dropouts with DTS:X yet, but there are much less DTS:X titles than Atmos titles, so it could just be statistics. I'll re-watch Atomic Blonde with the E-GPU setup that includes the 3090 and I'll let you know.

I assume this was with jRiver using WASAPI, correct? I get dropouts all the time with Direct Sound, even using the 1080ti, so I only use WASAPI with the Denon/nVidia out.

[Charky]

Here we go.

Exact OS version: Win 11 Pro 22H2 22621.2283
Exact Driver version and type: game ready, 537.42
Exact settings in the nVidia Cpanel: everything default
Exact settings for resolution: 2160p23, RGB 12 bits
Exact setting for bitstreaming in jRiver: default [Wasapi]

I've got a copy of Indiana Jones 5 with an Atmos track i'm supposed to watch this evening. I'll use Jriver and update if I see/hear anything out of the ordinary.

[SamuriHL]

I could try watching Atomic Blonde, there are worse films to watch again and I'm getting tired of John Wick 3 :)

I haven't experienced dropouts with DTS:X yet, but there are much less DTS:X titles than Atmos titles, so it could just be statistics. I'll re-watch Atomic Blonde with the E-GPU setup that includes the 3090 and I'll let you know.

I assume this was with jRiver using WASAPI, correct? I get dropouts all the time with Direct Sound, even using the 1080ti, so I only use WASAPI with the Denon/nVidia out.

Yup, always WASAPI for me and definitely JRiver. I was testing it with the new madvr settings Javs found and man, what a picture now! If we can get this audio thing figured out that'd be even better.

[Manni]

Yup, always WASAPI for me and definitely JRiver. I was testing it with the new madvr settings Javs found and man, what a picture now! If we can get this audio thing figured out that'd be even better.

I watched Atomic Blonde, details in the jRiver thread.

Please post any follow-up question or info there, it's a jRiver issue as far as I'm concerned and it's better for Nev/Hendrik if all the info is in the jRiver thread.

Annoying for me to repeat everything in two threads, and here we're spamming those who are not interested in jRiver.

[Mordred]

I've been running nvidia driver 536.23 for over a week now and everything appears to be okay except they still haven't fixed the HDR switching issue that's been happening in every version after 525.25. I still have to restart the video card every few days to keep HDR switching working. I made sure to use DDU (safe mode) when upgrading.
Just confirming that this is STILL happening with 537.42. Don't know how NVidia still hasn't fixed this issue yet.

[Manni]

Just confirming that this is STILL happening with 537.42. Don't know how NVidia still hasn't fixed this issue yet.

Did you try to reset your madVR settings to default?

[Mordred]

Did you try to reset your madVR settings to default?No, but how would that help? Switching in and out of HDR mode works fine for about a week or more and then suddenly it just won't do it. Falling back to 522.25 (the quoted post references a 525.25 that doesn't exist) it'll work perfectly for months without a reboot. I'm sticking with 537.42 for now to see if I can disable the graphics card and then re-enable to get switching back.

[Manni]

No, but how would that help? Switching in and out of HDR mode works fine for about a week or more and then suddenly it just won't do it. Falling back to 522.25 (the quoted post references a 525.25 that doesn't exist) it'll work perfectly for months without a reboot. I'm sticking with 537.42 for now to see if I can disable the graphics card and then re-enable to get switching back.

I'm only telling you that I had the same issue after swapping GPUs, and that resetting the madVR settings resolved it. It now works fine with the latest drivers (after DDU and clean install).

You can always export your madVR registry settings and save the settings.bin somewhere before deleting them and resetting to default. If it doesn't help, then go back to your previous settings. If it does, redo your settings.

There is something rotten with madVR settings that goes wrong randomly, even when you combine the EDIDs. Resetting and starting from scratch, especially after a GPU swap, is the only thing that worked for me.

[Manni]

No, but how would that help? Switching in and out of HDR mode works fine for about a week or more and then suddenly it just won't do it. Falling back to 522.25 (the quoted post references a 525.25 that doesn't exist) it'll work perfectly for months without a reboot. I'm sticking with 537.42 for now to see if I can disable the graphics card and then re-enable to get switching back.

Apologies, I just realised that we were in the drivers thread and not in the madVR thread. If you're talking about switching in and out of HDR mode in the OS, then it has indeed nothing to do with madVR settings.

[Mordred]

Apologies, I just realised that we were in the drivers thread and not in the madVR thread. If you're talking about switching in and out of HDR mode in the OS, then it has indeed nothing to do with madVR settings.So I'm experiencing this issue with DSPlayer Kodi using madVR, so maybe there is something there. Will try exporting madVR settings and resetting to see if that fixes anything.

I also had tried manually enabling HDR mode in Win10 settings because I'd heard that would work, but that just gave me a black screen/no-signal with no way to disable. I had to boot into safe-mode and uninstall the display driver to get a display back. Old Nvidia driver didn't have that problem either.

[Manni]

So I'm experiencing this issue with DSPlayer Kodi using madVR, so maybe there is something there. Will try exporting madVR settings and resetting to see if that fixes anything.

I also had tried manually enabling HDR mode in Win10 settings because I'd heard that would work, but that just gave me a black screen/no-signal with no way to disable. I had to boot into safe-mode and uninstall the display driver to get a display back. Old Nvidia driver didn't have that problem either.

DSplayer Kodi with madVR support is now quite long in the tooth, so is Windows 10.

I use Windows 11 and the latest drivers, and have no issues switching the OS or madVR to HDR mode.

I occasionally have issues getting madVR to do HDR to SDR tonemapping properly, and that's when resetting madVR defaults to defaults resolves the issue (for a while). Rebooting also helps.

I use jRiver MC as a player, and I never have any of these issues with JRVR as a renderer, so once you've resolved the switching to HDR with the OS, you might want to try a supported, up-to-date player and renderer, it might help you to pinpoint the issue more precisely.

If you have issues switching to HDR with the OS, I'd start with resolving that.

[Mordred]

Well I'm not going to abandon DSPlayer Kodi since I have it setup exactly the way I want, it works and I don't really need any of the newer features in Kodi. Also not looking to upgrade to Win11 anytime soon.

It's clearly an Nvidia driver problem, and maybe it only affects people like me, but there are definitely others out there since Aquanash from this forum was how I discovered which drivers worked in the first place.

[nevcairiel]

You can call it a driver problem, but madVR using legacy methods to do HDR output certainly doesn't help it. madVRs focus has been on tone mapping ever since it was created, and pass-through got little to no love.

[alexmain]

https://www.nvidia.com/en-us/geforce/news/call-of-duty-modern-wafare-3-pc-beta-game-ready-driver/
https://www.nvidia.com/download/driverResults.aspx/212701/en-us/

Nvidia GeForce 537.58 WHQL graphics driver released.

Thanks for sharing it. I hope it will resolve the issue for me, since I still have version 537.42 of my Nvidia drivers.

[KrazyLurt]

Tried 545.84 just now, it broke scrolling in both Firefox and Chromium for me. Probably a v-sync issue, it usually is. Reverted back to prev. drivers , and it works fine again.

[Klaus1189]

Windows 10 transparency effects are borked for me with new driver. If enabled the taskbar is deepblack. Which was always the other way round. It was deep black when disabled.
Also the effects do not appear when enabled.

Latest Win10 22H2 19045.3570

[Klaus1189]

The issues was right there after display flickered during driver install. I did a restart and issues persisted. Today I started normally and issue is gone. strange.

However I discovered that HDR passthrough (yesterdasy and still today) next to fullscreen exclusive/windowed now laos plain windowed works too. Up to now the HDR metadata wouldn't be applied in this mode.

[Klaus1189]

Stay away from 545.XX branch :(

[Manni]

Stay away from 545.XX branch :(

Can you be more specific?

[Klaus1189]

Wrong color on Desktop, deep black taskbar when transparent effects are on. These effects are also not working. Way more dropped frames and presentazion glitches with any renderer and/or filter combo. Same for Kodi. I switched back to latest 537.xx Studio driver. Hope Nvidia doesn't rush out Studio drivers like last 545.xx drivers. This has to be seen by a tester.

I have RTX40xx FE, if that matters.

[nevcairiel]

What does "wrong color on desktop" even mean?

Its all been perfectly smooth for me with a 40 series card.

[Klaus1189]

Colors are oversaturated and hurt my eyes. It doesn't make a difference if I use limited or full. It is always the same, same for RGB vs. YCbCr 4:4:4
LG TV adjusts accordingly so image always looks the same. But going back to latest 537.xx driver everything is fine like it was for the past months (over a year) since I have it - day one :)

Much more trouble are the dropped frames, which get worse when I play a 1080i60 file ripped from a blu-ray and use hardware deinterlacer. I get so many dropped frames, but using software deinterlacer and software decoder it is fine. Also in Kodi 21 beta 1.
Same here - going back to 537.xx -> issues are fixed.

Very strange branch ...

[huhn]

did you ever use an VR application?

i have only queue issues on this driver using a 4060.

[whitestar999]

I have gone through the driver issues list. I recently got a 2060 & as per my understanding v527.37 game ready driver should be fine for my usage on win 10 22h2. Is this correct or did I miss something/should be aware of? Usage is only going to be playing mainly 1080p sdr videos/hdr videos & some 420p/720p sdr videos(animated content & legacy stuff for which higher resolution not available) on a 1080p non-hdr TV screen for now & on a 4k hdr TV screen in future. If any tips/info then please let me know that too. I currently use 1050Ti with NGU luma upscaling as the most resource heavy option in madvr last official build.

[Klaus1189]

did you ever use an VR application?

i have only queue issues on this driver using a 4060.

No, I didn't use any VR app/game.

What do you mean with queue issues?

[Klaus1189]

I have gone through the driver issues list. I recently got a 2060 & as per my understanding v527.37 game ready driver should be fine for my usage on win 10 22h2. Is this correct or did I miss something/should be aware of? Usage is only going to be playing mainly 1080p sdr videos/hdr videos & some 420p/720p sdr videos(animated content & legacy stuff for which higher resolution not available) on a 1080p non-hdr TV screen for now & on a 4k hdr TV screen in future. If any tips/info then please let me know that too. I currently use 1050Ti with NGU luma upscaling as the most resource heavy option in madvr last official build.

Latest 537.xx is fine for me.

[whitestar999]

Latest 537.xx is fine for me.
So no issues with 537.xx on 22h2 & everything works fine except for that "HDR passthrough works also in window (metadata is used) (besides Fullscreen exclusive + Fullscreen windowed)" fix in 545.84 & the issues in win 10 transparency & worse performance as reported by you in previous posts?

[Klaus1189]

537.xx is fine, 545 will make trouble, yes.
But in 545.xx HDR colors are also correct in small window, which was never the case before.
(HDR passthrough)
But other major issues there so I do not recommend.

Latest 537.xx Studio and you can use latest and greatest driver, but it is Studio driver.

[whitestar999]

537.xx is fine, 545 will make trouble, yes.
But in 545.xx HDR colors are also correct in small window, which was never the case before.
(HDR passthrough)
But other major issues there so I do not recommend.

Latest 537.xx Studio and you can use latest and greatest driver, but it is Studio driver.
Got it. So any specific thing/fact I should know about studio driver other than the fact that it updates less frequently than game ready driver.

[Klaus1189]

No, it is better tested and so more stable and reliable.

[huhn]

No, I didn't use any VR app/game.

What do you mean with queue issues?

the presentation or renderer queue sometimes glitch out a restart usual fixes this issue. could be utterly unrelated to the driver such issue are not uncommon with madvr for years now.

[Klaus1189]

OK, how do I notice this behavior? Dropped frames, no video no audio, ...?
Restart of player or pc?

[huhn]

ahh the video stutters?
just player restart on my side.