No probs Sander, just look how similar to what I wrote in #29 and what John wrote in his last post (#57), and the sh*t sandwich between now and then about how he thinks I should be approaching this. That is all.
 
(UPDATE - And he's still telling me what I should be doing  - anyways).

Fair enough John, however please note that people what aren't experiencing the issue you are explaining may actually be more than qualified to express opinions as they are experienced, and they are involved in software development and knows how these things get developed. Most people in support desks DO NOT OWN the product you are wishing support for BTW.
 
UPDATE - And please note I will post whenever I feel it is useful, not when you think it is useful. Thankyou.

I've just skimmed the thread again but couldn't see if any specific Waves plug was used. I have Horizon so about half of them. I just inserted a PuigChild 670, picked a random preset from the Waves menu, moved one dial all the way left and another all the way right, saved the project, closed Sonar, reopened, loaded the project, everything is right where I left it.
X3D build 278 x64
Win7 x64

I forget where I can see my Waves version but it's the next to last installer I think, at least I got one upgrade notice about the Loudness Meter which I ignored because it seemed irrelevant to my purposes.

From what I understand Sander, it seems the issue is not in the Waves menu itself, it is the Sonar menu above it (in the same window) where you can select presets, in the grey title bar area.
 
Quite a common issue it seems, I have a number of plugins that will and will not work in this area of the UI (NI for instance). Some plugins will show the presets but don't get the titles of the presets correctly, or some plugins just won't show the presets at all.
 
I am assuming then these particular plugins are not exposing their parameters to cakewalks plugin engine correctly to be consumed, or there is a bug whereby Sonar is not parsing the information consumed correctly into the menu. The only people who will know what the issue is for sure is the developers as they have access to the source code (although it should be noted many plugins work fine in this area), as Cake does not have access to third party plugin code the third parties are basically the guys who need to check exactly what is going on here (and contact Cake if necessary, if they find no bug in what they are exposing to Sonar).
 
Either way there is a workaround.
There also seems to be an issue with presets persisting.
I'm not sure Waves plugins had updates or not since X3C.
 
We also had a confirmation from Cake that:


"BTW with Waves there is a bug in their VST3 preset implementation currently where changing a preset in their UI doesn't update SONAR. I will be reporting that to them."

I thought the OP indicated any edits to the on screen parameters wouldn't save either. For me that is indeed only the case when I use the Sonar menu first. Using the Waves menu, everything, including parameter editing, saves and loads fine.

Suggestion - Maybe if you could state the name and version number of PuigChild 670 DLL and the OP could check he has exactly the same version and issue? I did read his posts again and understand where you are coming from...
 
Thanks...

There is no PuigChild DLL because Waves works with a shell. However, PuigChild's "about" screen shows me Waves version 9.1.0.9 Build 1363. Which is weird because I have WaveShell version 9.2.
But their versioning is just odd like that I think.
 
EDIT: Waves has had an update specifically to deal with Sonar compatibility which came out just after X3C, and they worked with Cakewalk to get that out. They only started supporting X3 from update C which is stated on this website. They have had a minor update out since, which (AFAIK) only updates their Waves Loudness Meter to a "better" version, which I didn't do. They also brought out one or two entirely new plugins which requires them to update their installer, but I don't think any other plugins were altered.

It is NOT the SONAR preset I am having issues with. I did mention the waves plugin in #6. It is the Maserati VX1 stereo plugin.
 
The originating issue I had was the saved settings and not specifically the preset. Presets are another aspect of the issue it looks like though.

jbraner
In an effort to keep this thread on track:
 
Conley - you may have to contact Waves after all. I'm making some progress with DMG (well, he's making progress). We have a few problems besides the "saving settings" one - and it's not fully solved yet - but it looks like there are some things that the plugin is expecting to see from the host, and it isn't.
 

I am on the latest version of Waves - 9..15. I know Waves and Cakewalk worked on this issue and the fix was in X3C. The latest version of Waves works as expected in X3C for which Cakewalk had a fix. In X3D, it is not working. Since Waves did not change their code and the bakers did, I think the issue is with the bakers unless otherwise proven to be otherwise.

My settings are retained, UNLESS I have selected a preset from the Sonar menu and then alter it (or not). If I never touch the Sonar menu at all, and only tweak manually or use the Waves menu, my settings are saved and loaded fine. I don't have the Maserati VX1 unfortunately, I do have the Maserati DRM and that works exactly as I just described.
Can you get any other Waves plug to act like this? Preferably one that I have too?