The chat guy couldn't help and I'll contact tech support, but wondered if maybe someone knew how to fix this quicker. After The Waves Central update, I downloaded a Puigtech Eq demo and I went and scanned (in sandbox) to pick it up and instead of scanning just that one new plug (I don't have the re-scan everything box checked) Cakewalk scanned a whole bunch of Waves plugs, like 162 or something and then said it found something like 156 new plugs or whatever it was, so here goes Waves breaking s#** just by virtue of updating the Waves Central lol. Waves Audio dedicates significant effort and software development resources, in order to ensure that the plugins that users have invested in, whether recently or years ago, will remain compatible with all the.
#UPDATE WAVES PLUGINS UPDATE#
Has this happened to anyone else? It's weird because only some of the Waves vst3 plugs went missing after the Waves Central v.11 update. In this article, you will learn about the top Rhodes VST plugins that let you play classic Rhodes electric pianos right from your computer But before we check them out, let’s find out more about these VSTs. The Waves Update Plan comes free for one year with every new Waves plugin or bundle purchase and is renewable at any time afterwards.
Oddly enough a couple of non-Waves vst3 plugs by Nembrini went missing too. Actually, most of them are not missing, but vst3 versions of SSL bundle, API Collection, CLA Vocals, and the King's Microphones have gone missing, though the vst2 versions scanned fine. So I just updated Waves Central to v.11 (not my products, but just the Waves Central software) and now some of the vst3 versions of my Waves plugins are missing. By updating to V11, users benefit from future-proofing their sessions, ensure continued compatibility with the latest DAWs and operating systems (including macOS 10. The update comes with updated Renaissance plugins, additional plugins for premium bundles, and lots more. So if this happens to you then take note of the versions of what went missing (and what didn't), and a reinstallation of those legacy products is likely in order. Waves Audio has announced Waves V11, a new version of Waves plugins. That's right, merely updating the Waves Central software-not the products themselves-to the latest version 11 caused this. He said the solution is to reinstall the legacy 9.2 versions to restore those products whose vst3 plugs went missing. Some of my Waves stuff are v.10 and some are v.9 and after the Waves Central update nothing happened to the v.10 stuff only my SSL Bundle, API Collection and a couple others that were v9 were affected. Just called Waves tech support and they found that, as a result of updating Waves Central to v.11 some of my legacy Waves v.9.2 vst3 products became no longer supported w/ the v.9.6 vst3 Waveshell (the vst2 plugs of those same products were scanned ok).