I'm a hobbyist. I've never updated my Waves pack.

I'm not very familiar with the releases, but in my Apps folder, it looks like this (picture 1 below)

If I want to update the Waves bundle without losing anything, what exact procedure to I use? In other words, I have Waves 9.6.1 sitting here (dada release), there might be a newer one, but must it be from the same group, etc? Is there an update option built in?

Thanks@!

1.

 

NFO files serve a purpose. If you can't go through them, maybe you shouldn't try to update anything.

 

nonsense, on windows the manual didn't warn me for the fuck ups it started,
updating with every single realease is simply not worth it. even if you read the manual

asking this is actually a smart thing to do

 

...open the nfo file and follow the instructions...

 

@sk8816
the real question would be, Why you want to update.
i've had tons of issues with updating to the latest version. i hadnet updated in 2-3 years. i spend WAY to much time getting things to work, i thought i would at least tell you that part.

 

There is a saying that goes ( there is no stupid question ) if you don't ask questions you don't learn anything

 

Totally true, my bad. I sincerely apologize.

If I'm not mistaken, the NFO says to perform a clean install to avoid issues. If you really clean it up, you should have a smooth ride.

 

I tried, To be honest the mistake is likely to be in between my seat and the screen.
Fl studio didn't resolve the plugin names anymore and named them by number

 

Here I am -- almost a year later -- thinking about this again.

So, ideally, I should be able to uninstall Waves, reinstall a newer Waves bundle, and all projects that use Waves plugins will automatically begin to use teh newer version of the plugin?

This seems like it should definitely work for a purchased copy (I could never afford) -- there is probably an update button. But even with these cracked guys?

Any experience anyone?

BTW: I am interested in trying soe of the new plugins. Not worth it?

 

Yes. This is the idea. I loaded up a project I did in Cakewalk 9 - 18 years ago (~1998-99) when I was using Radium NPP Waves pack - into Sonar Platinum (2017). Using a "recent" R2R WAVES pack. All of the REQs popped up as well as Maxxbass plugins (...all instances popped up no problem). So, I can confirm that the original plugins that WAVES have been offering for 20 years are still recognized. It would be safe to assume that all WAVES plugins should function retroactively with old projects - which ALL companies should take a page from. Just make sure you're not using that weird WAVES plugin selection menu when choosing vsts in your DAW (not sure if that menu exists anymore in the new R2R versions?)

 

Last edited: Jun 17, 2017

On mac it's pretty easy. All your Presets and Plugin Settings (if you saved any inside the Waves menu) are stored in the Users > Shared > Waves and they remain there, even if you uninstall the bundle und update it. But you could back them up for safety.

So like said before:

1. read .nfo
2. follow instructions
3. Done.