Skip to content
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

Open
MaxtheIV opened this issue Sep 9, 2020 · 5 comments
Open

Not working with latest Windows 10 update #8

MaxtheIV opened this issue Sep 9, 2020 · 5 comments

Comments

@MaxtheIV
Copy link

MaxtheIV commented Sep 9, 2020

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]

@Becods
Copy link

Becods commented Sep 12, 2020

Hey

Are you using the 1909?

I've tried, and this patch can work in 2004 or 10.0.19041.508

@NelsonGomesNeto
Copy link
Contributor

NelsonGomesNeto commented Sep 17, 2020

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

@Crystal-RainSlide
Copy link

Crystal-RainSlide commented Jul 7, 2022

According to my understanding, there are three group of AudioProcessingObjects in the way:

  • the essential ones (for Windows to output audio)
  • one for Viper4Windows itself
  • the others.

To make Viper4Windows work, the Registry Patch in this patcher:

  • literally deletes:
    • HKLM\SOFTWARE\Classes\AudioEngine\AudioProcessingObjects and
    • HKCR\AudioEngine\AudioProcessingObjects
  • and (re)create the entry of Viper4Windows at:
    • HKLM\SOFTWARE\Classes\AudioEngine\AudioProcessingObjects\{DA2FB532-3014-4B93-AD05-21B2C620F9C2} and
    • HKCR\AudioEngine\AudioProcessingObjects\{DA2FB532-3014-4B93-AD05-21B2C620F9C2}

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.

@metaspook
Copy link
Owner

I will try to make a new update on this in some days .. busy days ..😓😒

@metaspook
Copy link
Owner

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]

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:

  • the essential ones (for Windows to output audio)
  • one for Viper4Windows itself
  • the others.

To make Viper4Windows work, the Registry Patch in this patcher:

  • literally deletes:

    • HKLM\SOFTWARE\Classes\AudioEngine\AudioProcessingObjects and
    • HKCR\AudioEngine\AudioProcessingObjects
  • and (re)create the entry of Viper4Windows at:

    • HKLM\SOFTWARE\Classes\AudioEngine\AudioProcessingObjects\{DA2FB532-3014-4B93-AD05-21B2C620F9C2} and
    • HKCR\AudioEngine\AudioProcessingObjects\{DA2FB532-3014-4B93-AD05-21B2C620F9C2}

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.

Guyz... issue fixed checkout the version..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants