Another plugin losing its settings - Ozone Imager

I too have had have had this occasional issue for years James, with various plugins, mostly vsti's. Damned if I can find any rhyme or reason to it's occurunce! I remember it started with a release that caused it to happen with all VSTi's that Cakewalk released a fix for almost immediately, but it has lingered on a semingly random basis. It seems to hide long enough for me to forget about it until I am working on a project that I have spent hours tweaking sounds in:)

I hear you. It is extraordinarily frustrating. I can't believe more people haven't run into it. I used to think it was mainly Kontakt and waves plugins that it happened in, but it has pretty much popped up in everything I use over the years. Nothing worse than opening an archived project to find all of your sounds gone!
There are many things I will miss from Sonar. This certainly isn't one of them.

I recently ran into this with a couple of no-longer-supported 32 bit MHC VSTi's.  And then discovered that, although they used to work (as I'd used them reliably under 8.5.x, if I remember rightly), they no longer saved state in *any* VST host I tried them in - since they've had no updates for years, I assume that a Windows update (I'm on 7 still...thankfully!) broke their persistence in some way.  Not expected at all, but maybe worth checking these on another system (ie. different set of Windows updates) or in a different host on your machine.

Interesting to hear other people report this now, I did feel like I was somehow doing something wrong or was cursed, judging by how few people mentioned in on the forums before. Maybe we should have kicked up a bigger stink about it, lol! 
 
As a beta tester it was a constant source of frustration that I couldn't come up with a recipe to recreate the problem. And it seemed so random - sometimes these synths and plugins would load fine, other times they would load flatlined. Someone else on the beta team with the Quadcurve problem said they think they saw it happen after moving the playhead in a project, so that might have been a clue. 
 
As for the Waves issue, I did find a promising clue not long before Cakewalk went kaput. I was able to capture on video a band of the Q10 moving without touching it, along with a recipe of how to recreate it. Check this out: 
 

 
I discovered it quite by accident. I'd opened the Q10 to make an adjustment, and after wondering why I couldn't hear any change in the audio, I saw that the ProChannel that the Q10 was hosted in was turned off. When I turned it back on, the band I'd adjusted moved on its own. I think the same thing happens with FX bins as well. So there you have it - an illustration of how turning on a ProChannel (after having made an adjustment to the plugin with the PC turned off) can send a signal to a plugin and change its settings. 
 
So that got me to thinking about how these plugins were being changed. I don't think it's that Sonar is not saving the settings in the project file - I think it's more likely to be that something is happening as the project loads. Could it be that as Sonar initializes your ProChannels or FX bins, these stray messages (whatever they are) kill or vandalize plugin settings? And maybe something along those lines is happening when synths are initialized in the synth rack as well? Or maybe that's not the case at all, and the problem in the video is totally separate!
 
I submitted the above as a bug, and the Bakers were able to reproduce it. And then Cakewalk was no more. Daaaaamn......

Rasure
I get this often too, seems to be pro channel related. I find the concrete limiter can often mess things up for me. I might have to try just using the FX bin and not use the PC anymore, pitty cus I love the PC EQ. 

The problem illustrated in the video above happens with the FX bin as well, so I think both are problematic. I bet the FX bins and ProChannels share a certain amount of code. 

Yup.  Had this on and off for years.  I just have accepted it by now!   Most recently I had it happen (twice) with Bias FX.

I also found it happened far more freqently when re-enabling a synth track after it had been disconnected and archived. Still, nowhere near 'all the time', and never reproducable. Grrrrr!
 
Pleased to say I haven't come accross it in S1 as yet. Still early days though:)

Sorry to hear you are having problems James. You mentioned Ozone Imager. I am assuming it's Izotope's Ozone Imager?  
 
Anyway, I thought I would mention that they give that plugin away for free now, you can use an installer directly from them to install it and activate and use it rather than using waves, that's what I did although I haven't worked with it much yet, so I don't know if it has the same problem with the presets saving and such things. 
 
Here's the link to the information and download page from Izotope.
 
https://www.izotope.com/en/products/master-and-deliver/ozone/ozone-imager.html
 
I'm thinking it's the same plugin, so perhaps if it is then you can install it this way and bypass the issue with Waves. 
 
I have a couple of plugins from Waves that were giveaways, the One Knob Louder and VU Meter, but that's the only reason I have waves on my PC right now, but I do plan on buying a few plugins from them in the future also, they have had a 29 dollar sale on several plugins I got an email from, so who knows, I may purchase some soon. 
 
Anyway, I hope this helps you out, you've always had some really good input and advice on things for others, including me that I have read here from time to time. Good luck!
 
Happy Holidays! 
 
Bobby