Vienna Symphonic Library Forum
Forum Statistics

174,506 users have contributed to 41,836 threads and 253,012 posts.

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

  • [SOLVED] Waves Plugins not Loading in VE PRO (Win 10)

    Seems like my Waves plugins are not loading in VE PRO. See message below that I get on every one of them. This is under Win 10. Any idea on how to fix this?

    https://www.dropbox.com/s/pq6n3tv8qxwualu/Screenshot%202015-08-28%2000.33.24.png?dl=0

    Thanks,

    Nektarios


  • Hello Nektarios, 

    Waves plug-ins can´t be loaded from the WaveShell (or WavesHell, as some put it). Please extract the plug-ins from the shell and load them this way. 

    Best, 
    Paul


    Paul Kopf Product Manager VSL
  • last edited
    last edited

    Thanks Paul! Will do...

    I know what you mean... 😢  I am tired of this waves"hell" crap...


  • Hi there, I have successfully opened Waves, in VEP, through the free StudioRackV9r10(Waveshell 9.7), which loads up to 6 plugins at once and/or BlueCatAudio PatchWorkv1.7.1 and the shell2vst way works okay, also. Since my recent purchase of VEP, I have had to reinstall a lot of plugins, as so many of them were only installed as .vst3, so extra work anyways. pacman


  • last edited
    last edited

    Thank you! So if I understand you correctly, by installing StudioRack by waves I should be able to load Waves plugins in VE Pro? This is awesome, thanks for letting us know!

    @pacman said:

    Hi there, I have successfully opened Waves, in VEP, through the free StudioRackV9r10(Waveshell 9.7), which loads up to 6 plugins at once and/or BlueCatAudio PatchWorkv1.7.1 and the shell2vst way works okay, also. Since my recent purchase of VEP, I have had to reinstall a lot of plugins, as so many of them were only installed as .vst3, so extra work anyways. pacman


  • Absolutely, as many times as you like, so far, anyways and StudioRack ('save as' is the same way/s) doesn't seem to use any extra resources.


  • last edited
    last edited

    Awesome! Thank you!

    @pacman said:

    Absolutely, as many times as you like, so far, anyways and StudioRack ('save as' is the same way/s) doesn't seem to use any extra resources.


  • last edited
    last edited

    @pacman said:

    Hi there, I have successfully opened Waves, in VEP, through the free StudioRackV9r10(Waveshell 9.7), which loads up to 6 plugins at once and/or BlueCatAudio PatchWorkv1.7.1 and the shell2vst way works okay, also. Since my recent purchase of VEP, I have had to reinstall a lot of plugins, as so many of them were only installed as .vst3, so extra work anyways. pacman

    Ah! Another soul who wouldn't mind if Vienna would implement VST3 support in their slave software 😕

    Almost thought I was alone in this quest....


  • last edited
    last edited

    nar, you are not alone and, although I was upbeat to start, it has recently become a bl..dy nuisance! Please give us access to our *.vst3 plugins 😢


  • last edited
    last edited

    @Paul said:

    Hello Nektarios, 

    Waves plug-ins can´t be loaded from the WaveShell (or WavesHell, as some put it). Please extract the plug-ins from the shell and load them this way. 

    Best, 
    Paul

    Can Waves plugins be extracted from WaveShell?


  • yes, just 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 at  http://www.xlutop.com/buzz/zip/shell2vst.zip 


  • Kudos Pacman,

    I would have really been po'd if not for your suggestion. I myself would have never thought of this.

    A couple of screens popped up asking for certain folders, (and you must be exact or the install will not work) but this is probably due to the fact that not all installs are exactly the same. So with a little trail and error I'm up and running.

    For me, EP is at the center of my midi operation, (and I don't think I'm alone) so when it comes up short, it kills the creative process. Mozart didn't have this problem but I do. So I really hope VSL recognizes this. I know they can't solve all problems but I don't think they really looked into this one because their EP/Waves customers are just too few. And you've got masterpieces to create so you can't monitor your mailbox everyday!

    So again, much thanks,

    mike


  • Pacman,

    I did as you described, using the shell2vst64.exe, and indeed a Waves folder gets created with all my Waves plugins inside. Unfortunately, when I start VE Pro, the plugins do get scanned, but they do not appear in the list of VSTs. Any idea why?

    Thanks!

    Nektarios 


  • last edited
    last edited

    Sorry, for some reason it works now. 😕 All good now! Thanks!


  • last edited
    last edited

    @nektarios said:

    Sorry, for some reason it works now. 😕 All good now! Thanks!

    Glad to hear this, as I was just about to try and emulate your question, P


  • The issue was that I was launching the 32-bit version of VE Pro, and all my plugins were 64-bit.


  • Also if on Windows 10 v1607, remember to go into the properties of 'shell2vst' and switch to run in Windows 7 compatibility mode if you experience a failure to create issue.