Windows 10 (latest)

Some of my Waves plugins are not showing up in VEP

• These plugins all show and work perfectly within Cubase, Nuendo, Wavelab, Vegas Pro
• They are all Waves V10 - (I do use V9) and all have vaild licenses
• I Double checked that the correct paths are in VEP
• I tried removing Waves Cache
• Also tried removing the VSL Cache: C:\Users\USERNAME\AppData\Roaming\VSL\Vienna Ensemble Pro
• This forced a rescan (again) - Still no sign of the missing plugins. Very odd.
• Have removed the VST folders (in VEP) and added again etc. many times
• Reinstalled the missing Waves plugins
• Rescanned many times under various scenarios

The plugins appear to have been scanned as I see them in the VSL Log C:\Users\USERNAME\AppData\Roaming\VSL\Vienna Ensemble Pro\logs\app

Example:

2018-08-05 10:26:54.763 INFO  [9348] [VESplashScreen::] VESplashScreen: Testing VST plugin: Waves Abbey Road Chambers Stereo

2018-08-05 10:26:54.764 INFO  [9348] [VstPlugin::] Creating VST Plugin: C:/Program Files/VSTPlugIns/WaveShell2-VST 10.0_x64.dll

2018-08-05 10:26:54.767 INFO  [9348] [VstPlugin::] Destroying VST Plugin: C:/Program Files/VSTPlugIns/WaveShell2-VST 10.0_x64.dll

But those certain few plugins just do not appear in VEP at all (above Waves "Abbey Road Chambers Stereo" is an example).

Where does VEP store its list of plugins, maybe I can edit that list manually?

Any other ideas appreciated.

Thanks in advance.

P.

Originally Posted by: Paul

Hello P., 

Here is a possible solution:

Place WaveShell-VST 9.6_x64.dll & WaveShell-VST 9.7_x64.dll onto shell2vst64.exe and a folder called 'Waves' will be produced: inside will be the plugins you have purchased and you may move these to where ever is most convenient. Hope this clarifies. Shell2, 32bit and 64bit is available here

Best, 
Paul

Thanks Paul. I did see that thread when seraching but I thought that was for older versions. I'll give it a go anyway.

Ahh, unofortunately the zip link is 404 :-/

Ok found it here: http://www.xlutop.com/buzz/zip/shell2vst.zip (non https link).

:-)

More info:

There are two Waveshells:

WaveShell1-VST 10.0_x64 / WaveShell2-VST 10.0_x64

The missing plugins are all contained in WaveShell2-VST 10.0_x64

If I remove WaveShell1-VST 10.0_x64 frome the VSTPuginst folder then the plugins from WaveShell2-VST 10.0_x64 show up.

As soon as I put WaveShell1-VST 10.0_x64 back, only the WaveShell1-VST 10.0_x64 plugins show up.

I will contact Waves again with this info.

Hi, 

Could be that a WaveShell always gets the same Plug-in ID, which would explain this behaviour. 

We will investigate this, but unfortunately I cannot give you an estimate at this point. 

Best, 
Paul

Yeah, I wish I saw this post before I "repaired" my Waves v10 plugins. Oddly, they show up and all work on a Mac running High Sierra. Not so (except for Codex) on a Windows 10 PC.

I previously posted the same topic, but the same symptoms seem to be increasing.

If "WaveShell1-VST 10.0_x64"  and "WaveShell2-VST 10.0_x64" are at the same time, 1 will be ignored and only 2 will work.
If 2 is deleted, 1 is recognized normally.
In my DAW, I recognize all the WAVES plugins. Is this a bug in the Waves plugin?

In addition, in my environment, it seems that "Abbey Road Chambers" is not recognized only when comparing VEP and DAW.

T.K

* This sentence uses Google Translate.

I believe I just found a workaround. The file "shell2vst64.exe" worked in Windows 7 so I ran it in Windows 10 with "Windows 7 comatability" and "Run as Administrator" and it worked! Just drag both waveshells on to the "shell2vst64.exe" and it creates a "Waves" folder with all the .dll files (just as in Windows 7).

Hope this helps...