Very weird Waves plugin bug

hey guys.

So i have several waves plugins, bought, installed and authorized via the Waves Central and i got a weird issue.

I replaced my PC with a new one last week. I have promptly re-installed and re-authorized all my Waves plugins. They work well in Renoise, like they should If i add them newly.

But if i load up an old renoise file (ie. made on the old PC), it says that the plugins are missing. I see them in the DSP chain deactivated. But i still have the very same plugin in the plugins list. I can obviously click on them and re-add them but 1., it’s a major pain in the a$$ and 2., i lose all the settings that were set in said tunes.

I emailed Waves support about it. all they said was Renoise is not on the supported DAWs list and they shrugged.

Why doesn’t renoise see and load in the exact same plugins that i have installed? Does anyone have the same issue? Do you have the solution?

Thanks in advance!

Maybe you’ve used VST2 but installed VST3 version?

I can’t even use/open Waves Central anymore on my machine and many other people have trouble getting their crap to work properly, you can search this forum for Waves installation and I’m sure stuff will pop up…

1 Like

My waves plugins wouldn’t show up in the latest Renoise update when i tried, so i’m at 3.3 now…

Once I finally got my Waves plugins working was when I was constantly deleting the failed cache files in Renoise between experimenting the installation because once they are sort of blacklisted in Renoise you were screwed, you had to delete the failed files cache or else you can do whatever and Renoise won’t care, now I notice Renoise 3.4 has a RESCAN button in the plugin area of preferences but I have never used it, maybe that does the trick instead of manually removing the files, so try click RESCAN and see if that miraculously works.

1 Like

All the previous versions had this rescan button, too. It’s not a new feature. :wink:
I don’t think it’ll work when it comes to Waves, but there’s no harm in trying it out.

I once had the same issue with some VSTs (I don’t want to use Waves, it was something else).
Make sure that you really use the EXACT same versions of your plugins than before.

nope, i use only vst3 of those plugins.
checked their support center and forums but didn’t find anything relating to this specific error.

rescan didn’t help, neither did using the exact same versions (which are the most updated).

Stay away from Waves is my advice

meh

miraculously it got fixed, not sure how.