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!

I'm having the same problem with DMGAudio plugins. I wish they'd tell us what changed in X3d! :-\

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

Can you explain exactly what you both are doing with a recipe starting with an empty project (also create a bug for it and list the number) When you say presets what are you referring to? The native VST presets or the SONAR presets in the preset picker?
 
What was fixed much earlier was a bug where settings were not persisting when you saved and reopened a project which had nothing to do with presets. 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.
 
Regarding Audio Damage please submit a detailed recipe and I will follow up with Dave since I am in touch with him.

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.

My recipe - (X3C works without issue)
1. Load project with the Waves Maserati VX1 Stereo on a track
2. Tweak Maserati settings to something other than default
3. Save preset to file in Waves dialog
4. Put into preset menu as - 'Your Preset Filename'
5. Save project and close SONAR - Project saved originally in X3C
5. Reopen project
6. Pull up Maserati plugin
 
In X3C the tweaks remain as saved when SONAR was closed and project reopened.. I was working with my friend when I originally encountered this. He wanted to update to X3D and did so while we were working together. In X3D, the presets are not showing up as saved in the preset. None of the tweaks set prior were present when the projects was reopened. We reverted back to X3C.
 
Waves is the latest at 9.15
 
Noel, please help me understand how can this work in X3C, not in X3D, and be a Waves problem if the Waves code has not changed?

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 ;-)

Queue Alex  with problem record tracking  :)

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

You know, rescanning is always the first thing I do when I have plugin problems. It is always 40% better after that...   ;)