Waves plugins do crash during initialization
A system-wide equalizer for Windows 7 / 8 / 8.1 / 10 / 11
Brought to you by:
jthedering
Menu
▾
▴
Hello,
Since two days, I can no more load plugins like "Abbey Road Studio 3", "CLA Nx" and "Nx Ocean Way Nashville" - all of them are the direct DLLs (no "waveshell" involved) and they were working fine before. Of these kind of plugins, currently only "Sienna Rooms" works fine in EqualizerAPO.
I'm not sure what has changed on my system and all troubleshooting steps I could find on the web so far haven't fixed the problem. Minidumps are available, What I gathered from there is:
`SYMBOL_NAME: EqualizerAPO!DllUnregisterServer+35d27
MODULE_NAME: EqualizerAPO
IMAGE_NAME: EqualizerAPO.dll
STACK_COMMAND: ~6s ; .ecxr ; kb
FAILURE_BUCKET_ID: INTEGER_DIVIDE_BY_ZERO_c0000094_EqualizerAPO.dll!DllUnregisterServer
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10`
So I'm a bit lost and would appreciate any pointers to address this issue.
Thanks much in advance,
Cheers!
Do you have the config file available holding the preset strings for these plug-ins giving this error (look sections starting as like: VSTPlugin: Library .... )?
Certainly (attached).
Now, with this config file, the EqualizerAPO will load but crash instantly (<.dll> crashed during initialization.) until I remove the last entry from the config file.
Windows event log only states "Faulting module name: Editor.exe, version: 1.2.1.0, Exception code: 0xc0000094"
After some more tests, I now came to the suspicion that it may not at all be a problem with EqualizerAPO but rather some Waves specific issue.
As mentioned earlier, this setup worked very well, even for some months.
I'll dig deeper into that direction for now.
Thank you.
Yes, it is plug-in compatibility issue ... .
Are those plug-ins upgraded lately?
Is path "H:\VSTest\Waves\NX Stereo.dll" same as before these issues (IIRC, as default, Waves installs to different location (maybe also stores something into system registry) )?
Last edit: Juha 2021-09-15
The plugins are all at latest version, so nothing has changed there. BUT I did some totally different things (NAS installation) and in that process, something seemingly unrelated (CERT of the machine, NIC info etc.) may have affected other things.
It's definitely a Waves issue, as I now confirmed that the mentioned plugins won't even load in my DAW (Cakewalk), so I'm now reinstalling all that stuff and expect that it'll fix the issue.
As for default install path, that's correct. The VST3s are usually accessed by their wrappers like C:\Program Files\Common Files\VST3\WaveShell1-VST3 12.10_x64.vst3 BUT these WaveShells failed to load into the EqualizerAPO when I first tried it out some months ago.
However, there's a tool "shell2vst" which can get all the individual DLLs out of that shell and store them separately, ready to be scanned as VSTs. This was my work around and it was flawless, I had three different room environments in the EqualizerAPO for mix checking etc. .
Finally, I'm convinced that it's an external problem and nothing is to do at this page here. I'm sorry for the noise, I was a bit in panic but now I'd book it as false alert.
Anyways, if somebody got a Waves issue in the future, some of the mentioned details may be of help anyways. Cheers!
I'm happy to report that EqualizerAPO is back to operating in all its glory!
After hours of digging files and registry, re-installing of things without luck, the cause of problem is still unknown to me.
However, the issue was fixed by going to C:\Program Files\Waves Central\resources\res\external\Redistributables and run all the files in there, most in "repair mode".
All is well, Cheers!
So you found the resolution ... actually, I bumped to this 'fix' suggested by Waves support to someone on Cakewalk forums but, I did not bother to report you because of I knew you're already after it (I found it through first few answers Google search returned). Unfortunately the Waves support did not inform the root for this problem.
Yes, that's correct. Cakewalk forum was the source of that fix. I only found it today because of different search keywords than yesterday. The reason being: it all failed systemwide, on Studio One and Reaper VST scans as well. So I was lead in different directions by mostly useless "information" coming from the different error popups.
I even bothered a Waves "support" guy per chat on their webpage ('cause sending an email at "contact us" didn't work either due to their broken page (seems fixed now)) to no avail.
I asked him for some direct email address to tech support 'cause my system was kind of bricked in terms of music production and much was paid for their products, without me ever having asked for support over the years (of course, he would not provide any).
Well, I'll see if I get some email reply from them and hope it'll be good, given the impact that such issue can have.
Last edit: mimo 2021-09-16