Waves presets - not working in X3D - CWBRN-23699

I searched the forum and once again, found zero.

I know I seen this reported and was trying to find out the details. In X3C - Waves presets work as expected. In X3D - Presets are not loaded when projects are brought up.
 
I thought I seen something that this was fixed or reported. Trying to figure out which one. TIA!

Um... X3D changelog here: 
http://www.cakewalk.com/s...reader.aspx/2007013355
 
Otherwise info about how third parties can contact Cakewalk etc (not just vst3 info):
http://forum.cakewalk.com...nternals-m2976078.aspx

a bug where settings were not persisting when you saved and reopened a project

This is exactly what the problem is with the DMG Audio plugins (Equilibrium and Compassion). I think sometimes we mistakenly refer to "presets" when we mean "settings" (I do anyway).
 
The recipe is simple:
- load a blank SONAR song (from the default blank template) in X3d. (no MIDI, no audio)
- Load the newest VST3 versions of Compassion (1.11) and Equilibrium (1.07).
- Set the EQ up to something and pick some settings on Compassion (it's a compressor) Just don't pick the first preset in the bank - pick something else and change the settings a little.
- save the song (project, whatever you want to call it)
- reopen it, and you will find
      Equilibrium is either set completely flat, or else the Q values are completely changed
      Compassion is set to the settings of the first preset in the current bank (in this case we are kind of mixing up presets and settings)
 
 
Now, try this with SONAR X3b or X3c.
The same thing will probably happen with these versions of plugs - but go back to Equilibrium 1.05 and Compassion 1.09 (both from Jan 2013) - and everything works fine. The weird thing is - the latest versions of the plugins had fixes "Fix bug with reload of presets some users have reported." You can even open a file that was saved with the "problem" versions of plugs - and the settings will be correct. So the "settings" are actually there - but not being picked up correctly when the song is opened.
Forget about the VST2 version, as they have different problems (including crashing SONAR) BUT the VST2 versions worked great in SONAR X2!
 
Something has changed in SONAR X3, and then is changing again from X3b & X3c to X3d. (Otherwise why would the VST2 versions work in X2, but crash in X3? Also - why do the older versions work fine in X3b and X3c but break in X3d?) Dave Gamble has got a copy of SONAR and is trying to work this through with me - but I have had no replies from Cakewalk support. I have not phoned them (I'm in the UK) but am trying to open email correspondence via the web page. (with my limited number of characters)
 
I "did" just notice the blog post, and have posted it to Dave. (Thanks Alex - I actually noticed it yesterday in a different thread)
 
For all I know - there is something on my system (win 8.1 pro 64 bit, SONAR X3 64 bit) causing the problems - but these problems are repeatable, and they're using a "bare bone" SONAR project with nothing else in it. It *does* get confusing testing the permutations of X3b, X3c and X3d with Equilibrium 1.05, 1.06 and 1.07 VST2 and VST3 and Compassion 1.09, 1.10 and 1.11 both VST2 and VST3. So forgive me if I get confused ;-)
(not to mention - this is becoming a full time job!)
 
To be honest - I just finished my last song without any DMG Audio plugins - and everything is fine, but these are very good plugs and I have been used to using both Compassion and Equilibrium on almost every track.

Noel, please help me understand how can this work in X3C, not in X3D, and be a **your plugin here** problem if the **your plugin here** code has not changed?

Exactly!
 
We aren't trying to bash Cakewalk - but something has "broken" for a bunch of plugins in X3d. If we can't get to the bottom of it, how can we have any confidence to move to X3e or X4 for that matter?
Even if they (Cakewalk) can let the developers know - we'll have half a chance.
 
And *please* don't tell us to rescan again ;-)

Cue Alex telling us to rescan our plugins
 
And nothing is wrong with SONAR...

IIRC when you use the WAVES menu for presets it's OK but if you use the SONAR drop down list for presets it's wonky.

jbraner
Cue Alex telling us to rescan our plugins
 
And nothing is wrong with SONAR...

Nope please RESET your plugins!!! (How many times do I have to say rescan is not reset )

Guitarmech111
This issue was fixed in X3C and regressed in X3D. If you start with X3a and go forward, X3C is the only one that works so far.

From the X3C patch info:
Fixed a variety of issues where VST3 Waves Plugin parameters would not persist correctly

That is not (entirely) true. See post #12.

MY issue was fixed in X3C. It was broken in X3A, B and D .

I only threw in the save preset because that is what I did. I needed a way to get the parms back so my buddy wouldn't scream - where are my settings!!
 
I believe these settings should be saved with the project regardless if they are a saved preset or not... I am sure someone will correct me if I am wrong.
 
 
A more correct title would be in my original case, "Waves settings not remembered by SONAR". It looks like it may be the same issue with different flavors maybe?

Not really a preset per se, but saved project with the plugin settings as they were when the project was saved.
 
So if you open a project, put in a plug, tweak the plugin settings and save the project, SONAR should remember the plugin settings without loading any saved preset. I ended up creating the presets because I knew SONAR would not remember them when reopened in X3D.

Just opening the project in X3D produces the incorrect results here. I am also on Win7 64 all around and Waves VST3.

Another thought. FX-Chain (on track or bus) in Pro Channel or not. Or, simply FX-Bin?
 
I'm using FX-Bin.
 

FX bin only - you can repro a simple project like I outlined. It does the same thing. It opened funny when I tried to in X3D and he had zero presets for that plug setting. Kust tweak some settings and save the project. My buddy has the original project so I am not able to send it.

But this just happens on waves plugins and some other third party (assuming you all did a VST reset). If it works with other plugins... well work it out for yourself... Has anybody contacted Waves and pointed them to this thread?

Yes that is my opinion and I'm entitled to it, I have stated my logic and you have stated your logic. You may have another opinion and that is fine, but please remember software is built up upon dependencies so just because it works on a patch but not on another patch this is no smoking gun, neither of us have the source code so argueing over this is futile and silly.

Still nobody has stated they have done a VST reset (so we are never allowed to ask this any more as this is the most obvious thing to do right? And to repeat again not a rescan, a reset) and my actual question was ... Has this been reported to waves etc? I can't see anything unreasonable about asking this as well other than this being 'too obvious'.

Thanks..