Me too, because there are 2 versions of the waveshell 10, VEP can only see 1 and "shell2vst" doesn't work with waveshell 1. Anyone actually go this working on Windows?
-
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...
-
A fix for this would be very much appreciated. Right now, using shell2vst64.exe results in a ridiculously long list of waves plugins that is too big to display fully in the popup that VEP presents. Waves are a major player in the plugin market and they need to be supported. Why they cant just release separate plugins I dont know.
-
My Waves V10 plugins are not showing up in VEP, but I have found a simple workaround.
Waves Studiorack is a free V9 plugin that can host a chain of othes Waves plugins including V10 plugins. https://www.waves.com/plugins/studiorack Studiorack does show up in VEP on my system.
So I first instantiate Studiorack in a VEP FX slot and then I can load any of my other Waves plugin from within Studiorack.
-
Waves always changes the number of waveshells they using. Now it's 3 of them. And only one of installed Waveshells will be visible in VEP - last scanned.
Sadly, VEP is the only VST host which can't handle multiple Waveshells. That's not normal.
All 3 current Waveshells are VST Plug-in Containers (not a plug-ins) with same VST ID - 'ksVW'. Waves often transfers their plugins between shells (for local fixes and updates). So common VST ID for Waveshells - needed for compatibility.
VSL should work with VST containers more smart way.
-
I thinked about this solution in the meantime but studiorack is really slow to load on VEP! ..don't know why..
I hope they will fix at least the TAB issue to see all the waves plugins in the view (or at least possibility to split them in different folders ex waves1 waves2 waves3..)
My Waves V10 plugins are not showing up in VEP, but I have found a simple workaround.
Waves Studiorack is a free V9 plugin that can host a chain of othes Waves plugins including V10 plugins. https://www.waves.com/plugins/studiorack Studiorack does show up in VEP on my system.
So I first instantiate Studiorack in a VEP FX slot and then I can load any of my other Waves plugin from within Studiorack.