Vienna Symphonic Library Forum
Forum Statistics

181,904 users have contributed to 42,191 threads and 254,627 posts.

In the past 24 hours, we have 2 new thread(s), 16 new post(s) and 50 new user(s).

  1. Home
  2. Software
  3. Vienna Instruments Pro
  4. Some Waves Plugins not showing up in VSL Server (64 Bit)

  • Some Waves Plugins not showing up in VSL Server (64 Bit)

    X
    X

    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::updateMessage@62] VESplashScreen: Testing VST plugin: Waves Abbey Road Chambers Stereo

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

    2018-08-05 10:26:54.767 INFO  [9348] [VstPlugin::~VstPlugin@979] 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.
  • PaulP
    VSL Team
    PaulP
    last edited
    last edited

    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

    Paul Kopf Product Manager VSL
  • X
    X
    last edited
    last edited

    @Paul said:

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

    😊
  • X
    X

    Hi again,

    Ok so I ran the procedure using command line as drag and drop didn't seem to work.

    Put all files (64 bit) into a new folder: C:\Program Files\VSTWaves

    Added that path to VEP and removed the original folder withe the Waveshells. VEP seemed to scan them but they don't show up in VEP at all. even after restarting and rescanning a couple of times.

    I'll keep trying...

    Thanks again,

    Phil.
  • X
    X

    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.
  • X
    X

    OK more, more info:

    I installed Studio Rack. Which is WaveShell-VST 9.7_x64.dll. I was reluctant to do this as I did not want any V9 shells.

    Anyway, now:

    Non of the V10 plugins show up in VEP but they all appear in Studio Rack. So it seems that VEP will only read 1 Waveshell and that is all.

    In Cubase etc. everything is fine, all V10 plugins show and studiorack.
  • PaulP
    VSL Team
    PaulP

    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

    Paul Kopf Product Manager VSL
  • X
    X
    last edited
    last edited

    @Paul said:

    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

    Thanks Paul at least you are aware. I will PM you some other info that may be useful. If you need any logs etc. let me know.
  • M
    M

    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.
  • B
    B

    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?
  • T
    T

    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.
  • B
    B

    Yes, this is the same with me, VEP can only see waveshell 1 OR 2 but not both. I spoke to Waves and they claim VEP is not supported and it's up to them to figure it out.
  • B
    B

    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...
  • S
    S

    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.
  • T
    T

    "shell2vst64.exe" does not support "V10".
    At least, I get an error "V10" on my PC. ("V9" is output "dll file".)
    I am giving up waiting for VEP's response.

    T.K
    * This sentence uses Google Translate.
  • pkreter_30363P
    pkreter_30363P

    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.
  • B
    B

    Try running "shell2vst64.exe" in Windows 7 compatability mode and run as adiministrator. It works for version 9 and 10 for me. If there are plugins you don't need you can always remove them to a different folder.
  • D
    D

    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.

    Image
  • A
    A
    last edited
    last edited

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

     

    @pkreter_30363 said:

    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.