-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not working with latest Windows 10 update #8
Comments
Hey Are you using the 1909? I've tried, and this patch can work in 2004 or 10.0.19041.508 |
It's even working on every latest Preview Build of Windows (but on every big update: I have to run the .bat again to reconfigure V4W). |
According to my understanding, there are three group of AudioProcessingObjects in the way:
To make Viper4Windows work, the Registry Patch in this patcher:
Which effectively remove essential and other AudioProcessingObjects entries so Viper4Windows is the only audio processor in effective. Then, it seems the essential AudioProcessingObjects will regenerate when Restart Audio Service or restart Windows (if there's no audio after you Restart Audio Service, just restart Windows!), make the audio work again, but with working Viper4Windows. And those other AudioProcessingObjects entries will re-appear on every big update. For the essential ones, maybe they also get totally regenerated, maybe they are just be modified by a little, maybe the update will only regenerate the missing others, but, anyway, they make Viper4Windows stop working again. And thus we have to re-run this patch. I suggest looking into other audio effect programs that works on Windows 10 and found out how they made their program work on Win10. Like EqualizerAPO, Bongiovi DPS, FxSound, Rapture 3D and so on. |
I will try to make a new update on this in some days .. busy days ..😓😒 |
Guyz... issue fixed checkout the version.. |
Hey man, love ur work. I'm here to tell you that it dosnt work anymore, atleast for me.
Microsoft Windows [Version 10.0.18363.1082]
The text was updated successfully, but these errors were encountered: