Waveshell1-vst3 11.0_x64
Smacka Shock
When adding a plug-in to an insert of any mixer channel, the following error is displayed:
There was a problem opening the plugin WaveShell1-VST3 12.7_x64 for an unknown reason. Please make sure it was installed correctly.
What I tried to do:
I got the same error since today.
What changed?
1.) I had bought a new Waves Plugin (CLA)
2.) Then I had updated the Waves Central (not with the v13 features. Clicked that away)
3.) Then I had selected update and install all.
Since that I got that error. DAW: FL Studio.
Have already tried what was described here.
Nothing helped.
In case the steps suggested above did not solve the issue, it can also be caused by non-English username of the operating system account, having a non-English letter in the username or having your Windows set to a language other than English.
I am asking this question here as I had to faff a bit with similar problem with some older VST plug-ins upon installing Sound Forge for the first time, but then it somehow started to load & work once I tinkled with Registry a bit.
However I established by faffing here and there that both WaveShell1-VST3 12.4 (working) and WaveShell1-VST3 12.6 files (problematic) are non-essential and seems to be WaveShells installed for some freebie Waves plug-ins: StudioRack etc. that I may inadvertently have installed at the same time I was obtaining Waves Diamond v12.
Once they have been nuked - and it's interesting that in order to achieve it one must remove the whole set and get it reinstalled, doh! - both files are gone and what remains is WaveShell2-VST3 12.0_x64 set of files which are all that's needed for Diamond bundle to work. And it does seem to work correctly with SF 14 Pro, so am not sure why Waves Support Team is so much hesitant about it?
Further to re-installation advice given so kindly in my other fred, I've so nearly got SPlat back how I like it. CbB has been uninstalled and I'll reinstall as per said advice once SPlat is 'perfect'.
However, each time I start SPlat, the VST scan starts running but always hangs on WaveShell-VST3 9.7_x64.vst3. When it stops, it opens an Explorer window [Documents] whose header is Select Waves 9.7 SG Studio Modules folder:
I select the folder so named and click on Select but nothing happens (the VST scan remains stopped). Once I click Cancel, the VST scan then starts running again and SPlat opens.
1) What happens if you disable scan on start up? (Thinks to self: why does anyone have that enabled anyway?) Are all the plug-ins you would expect to see in the vst3 menu and available to your project?
Ok, again this is guess work at best so treat accordingly to your viewpoint........I had a similar issue a while back with some NI plugs that CW vst scan refused to pick up on even though they were in the same folder as others that it did, so I tried moving the offending items to a new folder and adding that to the vst scan path and then it worked. No idea how or why.
My knowledge of Waves is very limited. Years ago they had problems with X-Ray. mixing Waves VST2 and VST3 plug-ins was a problem (still may be IDK) and CbB needs Waves VST3 plug-in to access their external sidechain inputs. That's about it.
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.
Certainly (attached).
Now, with this config file, the EqualizerAPO will load but crash instantly ( 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) )?
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).
Studio One uses a 3rd party software called Gear Software for burning CD's on the Windows platform. Gear Software provides a universal device driver that communicates with the burner and Studio One. In rare instances, there will be some burners that will not be recognized by the Gear Software driver.
Studio One 2 and 3 have older versions of the Gear Software Driver installed. If your burner is not being recognized, then the first step to resolving this will be to update the device drivers for the GEAR software in the computer that is used for burning CDs.
Click this link to download: =updates/windows/drivers/&file=Driver_Installer_x86_x64.exe
This release of the x86 & x64 GEAR driver installer installs a Windows 8.1 compatible GEARAspi driver set.
We asked Gear Software what they recommend when this happens if installing the driver update does not work. Gear informed us you'll need to install a demo version of their software and see if your burner shows up in their software. If it does then the issue is in Studio One, however if it is not, you'll need to get a new disc burner.
To get a demo of Gear Software, go to the Gear Software product page and download one of the 30-day Professional or Mastering demo packages (not the free burner software). If then in their software if your burner is still not recognized, then your burner is not compatible with Gear Software drivers (or Studio One).
PreSonus recommends using Plextor brand drives which are standard drives in duplication houses worldwide, These are available in both external and internal models. You can find out more information on their website.
e59dfda104