Waves Plugin Free
Alysa Guillama
Today I removed both the VST2 Waves shell and the VST3 Waves shell to see if Cubase would still show the Waves plugs. As expected, Cubase did not show any Waves plugs once booted. All Waves plugs are grayed out in the plug-in manager. So I can conclude they are not stored in a cache in Cubase.
Removing the VST2 Waves shell and keeping VST3 Waveshell in place did not make a difference other than the file classification in Wavelab plug-ins. I also tried removing VST3 and keeping VST2 with no luck.
Yes PG, there are 2 Waves entries in the cache list. One for VST2 and the path is C:\Program Files\VSTPlugins\WaveShell1-VST 9.92_x64.dll. Here, in alphabetical order, API through GTR Stomp plug-ins show up in the cache list, and this is exactly what shows up in Wavelab. No Waves plug-ins after the letter G show up. Again, this is EXACTLY a reflection of what is listed in the Wavelab Preferences>plug-ins>waves, and of course I can load these in the master section.
The other for VST3 is at: C:\Program Files\Common Files\VST3\WaveShell1-VST3 9.92_x64.vst3. Here, only API plug-ins show up, nothing else. I would think the Waves VST3 should be an exact reflection of the VST2, but the plugin cache only shows API plugs, and nothing else. (see attachment)
Honestly, the Waves guy was exasperated after the last solid 2 hour team viewer session, however I felt his conclusion was a bit rushed. And since his help, I have read a bit more about what might be causing this.
I see scanning Waveshells 1,3 and 6. Waveshell 6 is now the only one with plugins. But out of 26 there are only 3 detected. I see them while scanning.
Wavelab 9.5 is still unusable for me with this problem. Still working with WL8.
With all the vitriol Waves is currently receiving, regardless of right or wrong, IMO they have excellent support. I must have spent several hours over several days with Waves doing Team Viewer trying to detect my issue.
I have a lot of Logic sessions that use Waves plugins with specific settings to create certain sounds. I built up these sounds over the years and I often need to return to these sessions and use these sounds again. If the settings I used in these sessions were to be lost, I would lose years worth of sound design work.
However, if you are worried, you might want to revise your backup and archival strategy - if you keep a mirror of your system as it is, then you've always got an option to go back to that system in case any software issues cause problems.
Secondly, if you are worried that third-party dependencies might one day not work, you'll need to assess what that will do to important projects, and archive out versions where you render processing to audiofiles so they will still sound as intended with that processing (keeping the raw recordings too, of course). This means you will always be able to go back and remix or rework that work without the loss of third-party plugins changing anything too much.
You don't have to do this for everything of course, but for important work where you want to be sure software issues don't cause the loss of something vital, steps like these may prove to be your saviour at some future time...
Yeah, that kind of info is stored inside Logic's session data. Waves in particular is very big on backwards compatibility, its part of their guarantee, so to speak. So if for some reason it didn't workout you're allowed to hurl insults at them!! ?
The only time you really need to worry is when someone brings out a new plugin that doesn't actually assume the place of the old plugin. You MAY be able to copy and paste the settings in that case, but its unlikely that would work out.
Guest post by Brandon S. Hire of The Noise Floor. Brandon recently went hell with getting his Waves VST3 plugins all into REAPER. He got through it and I asked him to share the experience to help others in the same situation. Any clues to solving problems like this are gold.
As it scanned the VST3 plugins from Waves, it stalled at Greg Wells MixCentric. Then REAPER flat out crashed. When I re-launched REAPER, there was still no sign of the missing VST3 plugins, and MixCentric was one of them.
So I contacted Waves support. After trying a couple of things, we were able to remedy the problem with a clean install. This required that I go through a few steps to uninstall everything Waves related on my system, and then allow only the newest versions of everything to be installed by Waves Central. The whole process took a couple of hours, but by the end of it all I was back up and running. When I loaded REAPER again, I cleared the cache and re-scanned again. This time there was no crash, and at the end of the scan I had all of the missing plugins.
During the scan for the new plugs, I got: The following plug-in caused an error during load: WaveShetll1-VST3 12.7_x64 and WaveShetll1-VST 12.7_x64. Pop up suggested I disable them so the system doesn't become unstable. Did that.
Thank you! I removed Visual C++ version 2005, because I had been reading about issues it caused. Apparently, that screwed up a bunch of things. Right at that time, I started using Bandlab Cakewalk instead of my actual Sonar Platinum, because i wanted to see if there were more features. And that began a whole rabbit hole of problems with plugins working in Sonar but not in BL.
This seems to have fixed it! Thanks so much for posting this. My own fault, but I didn't make the connection until I read this.
i dont believe this, i do not understand why allen and heat doesnt resolve this. Every console out there work with waves.
Bob thanks for the response but i dont like convert my signals 2 times.
@yurcek you are my last chance!
Bob thanks for the response again, i understand what you explain me, but we need and extra converter and dont using the converters of the desk. I dont carry extra things. Im afraid to tell that the qu 16 doesnt work for me. Im triying to still investigate, because we need so much to run the pluggins. But if dont work i really need to buy other desk from other brand.
If you need this function, you have to make a decision: Qu-16 & Workaround oder another mixer. The Qu-16 is a great mixer and it works very good for my in my home studio and on stage. If i had the choice to buy a new digital mixer today, it probably would be the same decision for Allen & Heath. For me it is a question of trust in Alen&Heath and bad experience with other brands.
I have over 50 Waves plugins that work fine in GP. I have been a fan of Waves for a long long time. I reecently bought two plugins from Waves: Bass Slapper and Bass Fingers. Bass Slapper works flawlessly, sounds great and is very playable. Bass fingers on the other hand will not work at all! I tried it in Live and it works fine there. Be advised before you buy.
I using the Waves plugins (by waveshells vst) in Ardour5.8 on Windows platform. And they works perfect, almost.
The graphic interface and proformance on aspect of effect and automation is normal, nothing different than operating them in other DAW.
You are talking about vendor lock in. Every big company will do everything in their power to lock your data into their proprietary format / service. Then it becomes so expensive and painful to change your software vendor that it is easier to just pay up and stay where you are. That is not a new phenomena, every video tape machine manufacturer locked customer data into their cassette format, microsoft did this with office formats, etc.
Just choose only software that has a free license (if you can) and free yourself from all of the above (and copy protection), or be prepared to pay again and again for the privilege of having your tools working.
UI improvements:
- All plugin UIs now have 10% scaling, from 70% to 200%.
- The ACE UI is now clearer and has new modulation sources.
- Diva UI was also improved for increased clarity.
- The Zebra2 "Unempty Dark Horse" skin is now complete.
- And finally, a number of small graphics issues in various plugins are fixed.
Anyway, I have some Izotope plugins that work great. I am trying to add in some Waves plugins (VST) to make them sound even better. However, whenever I play a track with the Waves Plugin's GUI visible, Vegas lags out severely, and after a second or so, the audio will completely cut out. This even happens when all video tracks are muted (only sound playing). The funny thing is, when the GUI is not visible, everything works normally like it should. The VSTs even apply their effects without any distortion or lag. However, it is annoying because if I want to change a setting, I have to pause the video, open the GUI, change the setting, close the GUI, and see how it sounds. I cannot use any of the indicators on the GUI to see what is happening. All my other VSTs work fine. I can even put like 20 of them in a chain and no lag issues. Not that I do that normally, just testing.
My CPU only runs at about 30-50% when previewing even when all this lag happens. My GPU is barely effected. I have Vegas Pro 15.0. I have also tried this on the trial version of Vegas Pro 18. Still has the same issue.
c80f0f1006