Quote:
Originally Posted by schwa
The VST3 API provides a way for VST2 developers to update their VST2 plugins so that the saved settings are compatible with a VST3 version of the same plugin. If this scenario occurs -- the developer updates the VST2, you have a project saved with that VST2, then load the project on a machine that does not have the VST2 but does have the compatible VST3 -- REAPER will give you this warning:
WARNING - The following VST2 plug-ins were not available, but matching VST3 versions were found. This is a one-way migration, if you save this project it will require the VST3 versions going forward: {plugin name}
|
Just installed latest version and ABSOLUTELY LOVE this feature. Just one of the mistakes a newbie like me makes is not realising that Reaper is designed to work with (my Waves) VST3 not VST plugin versions. Consequence - lots of legacy uses of VSTs. Now, each time I load a legacy project, Reaper will implement VST3 where it finds VST, if I so wish. And that's great!!! Just love Reaper - it always delivers for me.
I wish I could say the same about Waves. Their move from v10 to v11 (Waves Central, and plugins) is causing me days of wasted effort, confusion, and plummeting confidence. I work on one Win8.1 machine and one Win10 machine. I keep Reaper on a USB stick (so my custom settings etc can move between machines) and my projects on OneDrive. Waves (in their wisdom) all but duped/forced me into moving from Waves Central v10 to v11. But v11 isn't supported on Win8.1. Also, the Settings/Tools stuff in Waves Central will remove all v10 or all v11 versions if you do an Update. It doesn't seem possible/easy to have both v10 and v11 on a machine. That means if I use v10 plugins on the Win8.1 machine, the Win10 machine will not recognise them as it only has v11 plugins on it. Or something like that. To be honest I'm completely confused by it all. And its not as if the plugins tell you (in your Reaper listing) whether they are v10 or v11 (why?) which might help a bit. So you end up in complete muddle. And even though I've bought all my Waves plugins within the last 12 months and so am covered for technical support, I've not found the Tech Support much use - they keep galloping to the rescue after I've sort of managed to fix a problem myself. So its hard to see how the extortionate Waves Update Plan fees are worth paying (and I won't be!).
So whilst I can't see me leaving Reaper behind, I might just wave Waves goodbye at some point. Which would be a shame, as I've had some good results with their plugins.
Hey ho, back to making music........if Waves Behaves (please Lord, let them!)