Waves 9.2 VST3 plugins resetting to default settings after saving??

Hi,
 
I just installed Sonar X3, its great! But when using Waves plugins like C1, Desser..L1, L2  as VST3, once I save the project and reopen it, all my plugin settings are reset to default. Even if I start a new project directly in X3, it fails.
 
Sometimes it remembers some plugs settings, but C1 always gets reset, I was happy to use it for sidechaining...but right now its not working for me!
 
I reinstalled waves and still the same, also projects from X2 they open waves plugins as default settings.
 
Can anyone confirm if this is a bug? anyone with waves 9.2 can use them as VST3 and can reopen with all the settings correct after saving?
 
Just try it on a new empty Project with the C1 compresor as VST3..
 
Thanks
 
Daniel

Thanks for your answer Noel, I hope it gets solved soon :)
 
I just tried using the waves plugs in "vst2 mode" and the GUI is totally messed up,  its unuseable :(
 
Right now, waves plugins also dont work in vst2. They work in X2 but without the vst3 enhacements.
 
Perhaps would be interesting to advice this problem...people can loose a lot of time mixing and later opening the project not knowing that all their waves settings are reset to default and all their time work is lost.
 
 
Daniel

Same here. I just realized it. I also had two chrashes when inserting  Waves plugs into the FX bin. (i'll stay away from waves for know...)
Other than that, no issues. Only positve surprises with X3 so far.
BTW, the VST3 folder doesn't show in the browser but the plugins are available right-clicking the in the FX bin.
 
 

I'm on X3 Producer 64 bit, and my Waves Renaissance Comp (VST3) also resets.

Ok, after doing more tests I found that to work with waves as vst 2, I must uncheck the option "replace vst2 plugins whrn opening projects" (on the VST 3 migration options).
 
Then the GUI is working perfectly in vst 2
 
Also, "vengeance VPS multiband sidechain VST3" plug in, resets to default settings after saving and reopening the Project!
 
I dont have more vs3 plugins, its posible that all vst3 plugins reset their settings after saving...
 
Daniel
 
 

ooops, Lancey, we wrote it at the same time ;)
 
 
 
 

Thanks Noel
 
Once we got VST3 fixed,  there will be no need to use VST2 anymore :)
 
Sonar X3 activated by default the VST3 migration options....perhaps would be interesting to advice that vst3 waves plugs are not working at the moment
 
If someone opens a project in X3 and saves it...they will loose all the waves plugin settings from their project...
 
 
Best
 
Daniel
 
 
 
 

That sounds good Noel!
 
Thanks

I would say, dont use any vst3 until the new patch, if you use the vst2 versión from waves it shouldn´t be any problem.
 
 
 
 

Well...anyway you cant use waves vst3 because they just loose their settings once you save and reopen the Project.
 
I dont know if happens with all vst3 plugs...I would suggest to stay away from vst3 until the patch.

 worked on a mix all night yesterday to find all my settings gone.  Now I find out about x3b addressing this issue!  I just bought x3 and the download was for x3a.  I hope when I install the patch it remembers my settings!!!!

It also seems to be resetting the Drum Replacer settings as well

djtrailmixxx
Bump, this is still an issue

I'm glad someone is bumping this. I am having huge problems with Waves plugins having their controls reset. It's mainly the SSL-Channel and Q10. I'm really frustrated about it because it's completely destroyed hours of work getting EQ sounding just right. I load the project later and things sound awful. Open the Waves plugins to find many of my EQ settings have been hosed. 
 
This plugin resetting business is quite possibly one of the most frustrating things I have found in Sonar. It's been happening to me for as long as I've used the program. It used to be Native Instruments plugins as well, but they seemed to have fixed that issue. And at one time I was even opening projects to find all instances of the Quadcurve EQ in the ProChannel messed up with crazy EQ boosts or cuts of 16dB in the same frequencies. If you can't rely on your mix settings being saved with the project then the DAW is functionally useless. We really need to get to the bottom of this. I would even advise Waves users who are thinking of buying Sonar to hold off until it's fixed. Let's start reporting this issue again.