Hey guys.

I've got the new Waves V9r29. and while all the plug ins work, I'd love to be able to organise them a little better, so I've tried using the shell2vst64, over the last few years but I've NEVER managed to get it to behave in Ableton. It starts scanning the individual vsts and it always fails on one or two (see attached screen shot)

The individual dlls that fail work fine when running them from the (cumbersome) waveshell via ableton plug in loader. Can anyone help, or has anyone had this issue, or am I just lucky?

Thanks for your help in advance guys

Pete

 

Last edited: Aug 26, 2015

https://audiosex.pro/threads/separating-waves-plug-ins-for-better-organization.10502/#post-69377 ..... This might be of help.

 

Try vstwrapperbuilder much better i.m.o but v2.1 did not do it for me for some reason so i use 1.0 for x86 and 2.0 for x64 read the manual you must have the shell on another folder then the vst one in order to get it to work

http://hypercube-softwares.duckdns.org/softwares/vstwrapper/

 

Maybe I misunderstood but - you do know the waveshell scanned by shell2vst is supposed to be somewhere else? For instance, the waveshell in Program Files\Waves\Waveshells. And no waveshell can be in your vst folder.

To @Pete I had a few problem plugs that were causing crashes on scan too. Ask yourself if that plug is worth more than freedom from the waveshell. If not, delete the last plug scanned before the crash.

edited for clarification and typos. I tried writing this on my phone

 

Last edited: Aug 26, 2015

I dont know what OS your using but I had the same Issue in Windows 10. Setting Ableton to always open as Administrator sorted the problem out for me.

 

Thanks so much as always guys, always appreciate your help

Thanks man, I had followed that through, sadly it didn't change anything

Cheers dude, it still has the same problem with the L316, but it is nice that that program sorts them into Mono/Stereo/Surround. That's pretty useful

Mate I know what you mean it's SUCH a nightmare, this is why I want them seperated so I can go through and pick out the ones I like (H-Delay) and such.. it really is a faff though, this install of 9r29 is the nearest I've got, before I couldn't get ableton to do ANYTHING with the extracted dlls

I guess it's just one of those things that isn't going to work properly, it's such a shame as you do get completely lost in the waveshell.

Thanks again for your help guys, lovely people you are

 

I felt that way originally, but you tube has tons of help videos. I would say I use about 10% of them now.



Pete.

I wouldn't suggest you do it that way around anyway. It takes ages for Ableton to load them that way, plus every time you install a new vst, it has to run through the whole lot again. It's an absolute nightmare.
If you get them working the (easy and quick) way, take my word for it and leave well alone.

 

Whilst I think of it. If anyone is having trouble (64 bit only) with ableton crashing as soon as they try and open (any) waves plug.

1) Delete your prefetch files AND Folder. from C:\Windows
2) Reboot (it will take longer to boot up first time and possibly 2nd time too) as it replaces the prefetch folder and files with updated versions.
3) Make sure when running things like CCleaner you do NOT delete this registry key:-

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls ( I added this key to the exclusion list for safety)

4) You should now find they open nicely without ever crashing again.

 

Thanks Artic, I never knew that. However, whilst everything is working exactly how I want, I will leave well alone.

 

I have sorted my vst folders in a folder hierarchy so i put all dynamics in a dfolder i call Dynamics all delay in a folder i call Delay all Reverb in the Reverb folder you get the idea so much easyer to find what i looking for instead of folders sorted by manufactors.
So i when i extract from vstwrapper i extract all in a temp folder and then i put all in their respective folders and since they are not real vst dll:s once you have done it the first time if you install the next update and their is a new plugin you only need to move the new plugin and delete all other that vstwrapper have extracted.
And since i only have 2 monitors i dont need surround plugins so i delete those and also some others i dont use to bad i cant do the same with the vst3 version

 

Last edited: Aug 26, 2015