Two VST plugins vanished from older projects

[Marketblandings]

This is odd.
I have two old Waves (trouble right there) plugins that don't pull back into old projects.
Everything else does.
Also, the two plugins CAN be drag and dropped back in - but, of course, I lose my settings. All other Waves plugins are fine.
This problem happened spontaneously with no changes to anything.

Why is Reason hating on these two plugins?

Damon R. Mathews
https://on.soundcloud.com/JwYiwtGoWv4amiVZ7

[bitley]

Reason 13 prioritizes VST 3 I think, so it might have something to do with that?

[Enlightenspeed]

If the projects used VST2 versions of the plugin, but you now have the VST3 only installed, then the plugin is now gone because it isn’t the same plugin, despite the same looks and functionality being the same. Sadly there is no easy fix to this and you need to keep your VST2s and swap them out with a VST3 that has the same settings.

[nebraskafire]

Maybe is has something to do with the waves version. I have 2 plugins (CLA76 blue and black) on Waves version 10 and they both stopped working. I have some plugins on version 15, 14 and 12 they all work fine. Just the older ones dont work anymore.

[joeyluck]

If the projects used VST2 versions of the plugin, but you now have the VST3 only installed, then the plugin is now gone because it isn’t the same plugin, despite the same looks and functionality being the same. Sadly there is no easy fix to this and you need to keep your VST2s and swap them out with a VST3 that has the same settings.

Would be great if Reason could implement IPluginCompatibility: https://steinbergmedia.github.io/vst3_d ... eInfo.html

[Marketblandings]

Maybe is has something to do with the waves version. I have 2 plugins (CLA76 blue and black) on Waves version 10 and they both stopped working. I have some plugins on version 15, 14 and 12 they all work fine. Just the older ones dont work anymore.

My 2 dead ones are 9.92 plug-ins.
They worked until a few weeks ago and no amount of re-loading or re-licensing fixes it.
Maybe our old stuff has been killed by Waves, nebraska!

[ekss]

I know this isn't help in anyway, but I feel like it should be mentioned as often as possible that this is one reason why Rack Extensions are so great; they'll never fail in a reason project, even if the dev stopped updating their REs they'll will continue to work, and stay in your account forever.
I just think the RE format deserve every praise it could get, sure it still has some limitations – my hope is that the format continues to evolve to be able to do anything vsts can eventually.

[Marketblandings]

I know this isn't help in anyway, but I feel like it should be mentioned as often as possible that this is one reason why Rack Extensions are so great; they'll never fail in a reason project, even if the dev stopped updating their REs they'll will continue to work, and stay in your account forever.
I just think the RE format deserve every praise it could get, sure it still has some limitations – my hope is that the format continues to evolve to be able to do anything vsts can eventually.

Agreed. My RE's are always there and always ready!

[Whoopdee]

This is why I never use vsts in my project.

[Marketblandings]

I found the problem. And it was not on the Waves end of things.
I found, in the Plug-ins Manager window in Reason that I had four instances of the Waves 9.92 installer showing.
I deleted 3. Now things work again.
Do I know why this worked?
Nope.