finicky NVIDIA audio filters

[wrathofflan]

I run Windows 11 with a 3070 and have installed the NVIDIA Studio Driver (576.52) and NVIDIA SDK audio effect version 1.6.1

The NVIDIA Noise Removal filter is a complete headache! It either works or it doesn't and I can't for the life of me figure out why. I may have to restart OBS anywhere from 2 to 7 times before the filter finally kicks in. (It is always present in the filter list every time I open OBS, it is just that the filter often times doesn't actually do any filtering.)

Sometimes launching OBS through NVIDIA App will make it work. Other times opening the OBS directly and leaving the NVIDIA app closed is what makes it work.

The one thing that seems consistent is that 31.0.3 is far worse (with respect to this one particular issue) than 31.0.2--but I've had this problem for a year now, so it didn't start with 31.0.3

[Fenrirthviti]

This sounds more likely to be a support request, and we are not currently accepting support requests on GitHub Discussions. Make sure you read any pinned posts on discussion boards before opening a new discussion. Please use our forums or Discord for further assistance.

Thank you!

[wrathofflan]

Thanks for taking the time to tell me what you think "sounds more likely to be" the case, Joel. All the best, a

…

On Sun, May 25, 2025 at 11:09 PM Joel Bethke ***@***.***> wrote: Closed #12206 <#12206> as outdated. — Reply to this email directly, view it on GitHub <#12206>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BJJQXJHSQXPOJK6RUKBYVE33AKAXVAVCNFSM6AAAAAB54PS7BOVHI2DSMVQWIX3LMV45UABFIRUXGY3VONZWS33OIV3GK3TUHI5E433UNFTGSY3BORUW63R3GE4TMMRQGAYQ> . You are receiving this because you authored the thread.Message ID: <obsproject/obs-studio/repo-discussions/12206/discussion_event/1962001@ github.com>

[Quadnick]

Idk if you'll see this wrathofflan, but I have the same issue and have found a work around. Every time I launch OBS, I delete it NVIDIA Audio Effects from my filter list and reapply it and my settings. It's still a headache, but it's a consistent way to get it to work for the recording session.

[wrathofflan]

Thanks, Quadnick!

You're right on both counts: (1) It's a bit of a headache to have to remove a filter every time you open OBS--only to reapply the filter right after you just removed it, but (2) it takes 2 seconds and it's consistent!!

I take it that bringing my question here to Github after I had been ignored on forums for 8 months is considered clutter. So I'm going to mark this as "answered" and (per Fenrirthviti's request) provided the link to the relevant forum (the one that has been ignored for over a year now)

Quadnick, I'm going to copy and paste your answer over there. Thanks for taking the time to share your workaround!!

https://obsproject.com/forum/threads/nvidia-noise-removal-isnt-doing-anything.175841/

[Fenrirthviti]

The post you linked, while a similar sounding issue, was actually a bot spam post (it's now been removed, but it was removed because the original post contained a link to spam that had gone unnoticed). As it stands, if you have fully reproducible steps for this, and can confirm it's happening for more than just your system, then a GitHub Issue Report is the correct place. However, we recommend users go through our support channels first to ensure that it's not a configuration or environment issue, and is indeed something worth reporting as a bug. We do not want to have those conversations on GitHub, as it is just not the right place in our community for those conversations. Our Discord is the most active place for this, and forum activity (as you have discovered) moves quite a bit slower. You just happened to post on the wrong thread (generally you want to make your own thread to avoid confusion) that was actually a spam bot. Unfortunate!

Thanks for your understanding.

[Quadnick]

I was just looking to help someone that had a similar problem. I'm not that worried about it. But thank you for letting me know.

…

On 10/15/2025 7:22 PM PDT Joel Bethke ***@***.***> wrote: The post you linked, while a similar sounding issue, was actually a bot spam post (it's now been removed, but it was removed because the original post contained a link to spam that had gone unnoticed). As it stands, if you have fully reproducible steps for this, and can confirm it's happening for more than just your system, than a GitHub Issue Report is the correct place. However, we recommend users go through our support channels first to ensure that it's not a configuration or environment issue, and is indeed something worth reporting as a bug. We do not want to have those conversations on GitHub, as it is just not the right place in our community for those conversations. Our Discord is the most active place for this, and forum activity (as you have discovered) moves quite a bit slower. You just happened to post on the wrong thread (generally you want to make your own thread to avoid confusion) that was actually a spam bot. Unfortunate! Thanks for your understanding. — Reply to this email directly, view it on GitHub #12206 (reply in thread), or unsubscribe https://github.com/notifications/unsubscribe-auth/A4HOFFLXWHDA3VTGORPWBKL3X36PFAVCNFSM6AAAAAB54PS7BOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINRZGMZDANQ. You are receiving this because you commented.Message ID: ***@***.***>