Hi Alex,
 
I'm the one causing the bad vibes - so I'll back off with that.

So one plugin is crashing but the others are not.
Some plugins are saving presets but others are not. Some are saving certain preset areas, others are not.
It certainly smells plugin specific to me.

I think what they have in common is that they all *used to* work - and now they don't. (not just new versions - but the older versions of the plugs that used to work - do not work now). Some crash, some don't save settings...
 

Sorry - I'm not trying to withhold information. I have done a "reset" and manual "rescan" dozens of times, and it does not make any difference. I was pretty sure I mentioned this already, but maybe not.

These problems are all happening with X3D. I'm not so sure that they were actually broken with X3C - but I'm trying to avoid having to go back to an image when SONAR X3c was installed. I have already wasted a lot of time testing
ver 1.05, 1.06 and 1.07 (VST2 and VST3) of Equilibrium and
1.09, 1.10 and 1.11 (VST2 and VST3) of Compassion

I *want* to use the latest version of SONAR. These are not some crappy freeware plugins - they're really good ones, and they *used to* work. The problem is - identifying exactly when they *stopped* working, and what changed to make them stop working.

Obviously when it comes to the ver 1.05 Equilibrium and 1.09 Compassion - *nothing* has changed with them. They worked great in X2 and do not work (for various reasons, that are not entirely predicable and reproducible) in X3D.


Hell, I'm not holding back information - just trying to avoid retyping redundant information...

Dan Gonzalez [Cakewalk]
Taking a look into this now to see if I can repro any of the issues I've seen in this thread. 
-DG

Thanks, Dan. You'll know some conditions to set we may not think of. One curiosity I will test is, if the VST2 and VST3 versions are available in the same directory, would Sonar believe the VST2 was enough not to import the VST3, assuming they are both one in the same? Just a stupid guess. 

if the VST2 and VST3 versions are available in the same directory,

 
That shouldn't really happen should it? VST3's have their own directory (C:\Program Files\Common Files\VST3) and you'd never put VST2 plugs in there - would you?

jbraner
Equilibrium 1.07
The VST2 version still causes SONAR to crash when you try to reopen the project after saving. In other words – if you put this plugin in a project, kiss it goodbye – you cannot reopen it.
 
The VST3 version is *almost* fixed. It is quite bizarre. Here is what happens
-          Add Equilibrium to a track and set it up
-          Save the project and close SONAR
-          Reopen, and all the eq settings are flat
-           Set them up again
-          Save the project and close SONAR
-          Reopen it – and now it’s fine. All settings are intact.
 
How can that happen? Something is either caching or not caching when it’s supposed to or not supposed to…
 
Even weirder:
-          Add Equilibrium to 4 tracks and set it up on each track
-          Save the project and close SONAR
-          Reopen, and all the eq settings are flat on the first instance and fine on the others!
-           Set up the first instance again
-          Save the project and close SONAR
-          Reopen it – and now it’s fine. All settings are intact (including tracks 2-4)
 

I haven't been able to reproduce any of these issues within the program using the Equilibrium plugin. However, the 32bit version of the plugin running in x64 SONAR seems to crash the program right away. VST2 seems to open up just fine when coming from a SONAR X2 project and the VST3 version opens up without hassle. I will pass this plugin along to some other guys here to see what kind of results they are getting. I'm also glad that DMGAudio is already aware of some weirdness and are working on it. 
 
-DG

A bit of clarity on my part: I'm now using Windows 8.1 64-Bit. I'm considering moving back to Windows 7 (myriad of issues, not just with Sonar.)
 
UPDATE: Having moved back to Windows 7, all of my previously experienced issues are no longer. I believe Windows 8.1 still needs work as an OS (even some basic Windows functions were seemingly broken). Maybe the install was botched, but this is the fundamental foundation that every piece of software is developed on or for Windows.

Hi Dan,
 
So you can load the VST2 64 bit Equilibrium in 64 bit SONAR X3d - save the project - and it reopens OK?
If you use the VST3 version - save the project, and reopen - all the settings are intact? Including the Q settings?
 
You can load Compassion VST2 or VST3 - save the project - reopen it and all settings are intact? It doesn't load the settings from the first preset in the current bank?
 
If so - then there must be something I can do to make it work here...
 
EDIT - I'm using Windows 8.1 Pro 64 bit also. I'm *not* considering going back to Windows 7 ;-)
 

This problem is only getting worse – well, actually, the more I look at it – the more *doesn’t work*.
 
What I noticed today – is:
 
-          Equilibrium VST3 hangs on the SONAR VST scan more than half the time it scans. The only way around it is to quit the scan, take equilibrium out of the VST3 folder, rescan, (come out of SONAR), put the equilibrium file back in, then it *usually* scans OK – but not always. Sometimes I have to repeat the whole thing again (take out of the folder etc etc) – then eventually it will scan OK.
 
-          Also for my Q settings to screw up, I don’t even have to save the song. I can put equilibrium in a track, make some settings, go do something else, then go back to it – and it is set differently! Usually the Q settings are changed. As a matter of fact, if I set it up, save as a preset, then open the preset – it’s not the same settings!
 
-          Also, I noticed that the “flat” setting that Equilibrium reverts to a lot (after saving a song and re-opening) is a setting in the “recently used” presets. In other words it’s acting just like Compassion – in that when you open up a song that’s been saved – the plugin reverts to a different “preset” at the top of the list (rather than the actual settings that should have been saved with the plugin)
 
 
I only mention these things in the hope that they might trigger some sort of realisation…
 
In my experience (I work in IT) when things start going this wacky – it’s some kind of (usually simple when you find it) weird problem that affects *everything* - but I’ll be damned
if I can find it ;-)

In case anyone is following this thread - I've noticed some more "funnys" with the DMG plugs - with stereo and mono interleave settings. I just realised that the "dots" in the FX bin tell you if a plugin is loaded as stereo or mono.
 
VST3 Compassion - is fine
loads stereo, changes to mono if track interleave changed
changes to stereo if track interleave changed

VST2 Compassion is loading as mono! (on a stereo track)
if track changed to mono interleave - it stays mono - but track cannot be put back to stereo

mono Compassion loads as stereo! (on a stereo track)
loads as mono on a mono track

compassion - no sc
if plugin set to "enable mono processing" - will not load (crashed SONAR)
if not set to "enable mono processing" - loads in stereo



VST3 Equilibrium - is fine
loads stereo, changes to mono if track interleave changed
changes to stereo if track interleave changed

Equilibrium mono loads in stereo on a stereo track
changes to mono if track interleave changed
then if track interleave changed back to stereo - stays mono

VST2 Equilibrium
loads stereo
track cannot be put in to mono interleave with plugin set to "enable mono processing" set to enable or disable
 
I don't know if any of this has anything to do with the inability to save settings - but it certainly has everything to do with causing crashes - and this "mono stereo" issue has been a problem for me since X3 came out (everything was fine in X2). I got around the problem by using the VST3 versions - which was fine until they stopped being able to save their settings...
 
 

I just got back to this thread and see my reference to Linplug RMV mentioned a couple of times.
For the record my problem report with Cakewalk is CWBRN-22050 - Cake shows as "submitted to development".
I purchased RMV after having already installed X3. I only installed the 64 bit version. I have X3D installed and using Windows 8.1 Pro x64. (Have reset/rescanned many times).
When I got the crash with X3, I tried it in X2 which I still have installed, and (true to Linplug's (Peter Linsener) word) RMV runs fine in X2. I have not tried to install the 32 bit version, as I deliberately bought RMV to run the 64 bit version. I have no history with it - but am confident there is a definite difference between how RMV 64 bit runs in X3D (crashes instantly) and X2 (runs fine). Maybe it is a Windows 8.1 thing, but X2 (in Windows 8.1) runs RMV fine.
 

  

For what it's worth - going back to X3c with Equilibrium 1.05 and Compassion 1.09 (both from Jan 2013) - everything works fine - and old projects still have their settings.
 
*something* changed in X3d!