DMGAudio - Compassion and Equilibrium problems (VST2 and VST3)

Hi,
 
Is anyone here successfully using these plugins? I'm using 64 bit versions with SONAR X3 Producer 64 bit on Win 8.1 64 bit.
 
I had a night mare when I upgraded from X2 to X3. Everything worked great (VST2 versions) on X2 - but when I tried opening my X2 projects in X3 (some were in progress) - they caused X3 to crash!
 
The short story is that the VST3 versions of these plugins work fine BUT - I just realised that neither Equilibrium nor Compassion are saving their settings correctly! Both plugins were updated in December so between the different versions I can only get Compassion 1.05 VST2 to load OK and save settings OK.
 
No version of Equilibrium (1.05 or 1.06 VST2 or VST3) works. Both VST2 version cause SONAR to crash when you try to open a project that they're in and neither VST3 version saves it's settings. 1.05 opens up "flat" and 1.06 has the Q settings wrong for every node!
 
Does anyone use these plugins? Are they working for you?
 
Thanks

I had the same problems with Equilibrium after going to X-3. Open a project with Equilibrium in it, push play and Bam!! Crash city! The only way I could make it work was to delete every instance of Equilibrium, save the project and then add Equilibrium back in. Its a pain but I did it. Ive never had a problem adding a new instance of Equilibrium. The only problem I had were the projects that already had Equilibrium in them from before X-3.

I've been using them with success, but I will say that DMG has informed me that the latest versions have some bug-fixes regarding Sonar, even though they don't specifically state them. I've had issues with them crashing the VST Scanner, but they still work.
 
Be sure not to mix VST2 and VST3 on the same FX Chain. Also, Equillibrium is still warm from the oven, so there's possible undiscovered bugs. If you can recreate the issue, go ahead and send them an email with that info. They'll look into it.

I tried the new Equilibrium 1.07 and Compassion 1.11
Here are my results. (this is copied from the email I sent to Dave)
 
This is pretty bizarre. Equilibrium is definitely not fixed.
 
First the good news. Compassion 1.11 VST3 works fine in SONAR now.
The VST2 is just like before – whatever settings you use, when you reopen the project, it changes to the settings of the first preset in the bank!
 
 
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)
 
This isn’t usable, as you never know when it’s going to save your settings or not. You literally have to add Equilibrium to your tracks, save your project and close SONAR, then reopen it and set up the eqs. Then close SONAR and reopen it and see if all your settings are intact – this isn’t good. When it’s screwing up – you can’t even save your settings as a preset, because it will reopen your preset with the wrong Q settings!
 
As I stand right now – I can use Compassion, but I can’t really use Equilibrium (I like to put it on every track) unless I feel like farting around all day saving and reopening and checking.

Well, Dave has been in touch - and he's on the case now, so I'm sure it will be fixed soon. I'll report back.
 
The thing is - no one else has reported this, so there's always a possibility it's something weird at my end.

I don't want to steal your thread but there is definitely a difference in X3's plug handling compared with X2 (likely due to VST3 compatibility(?)). I bought Linplug's RMV (posted about this elsewhere and reported to Cake) which runs fine in X2 but crashes X3 instantly upon loading a new instance. I get the impression Linplug is not going to fix this, seeing it as a Cakewalk issue (since it is clearly something X3 "broke").
Hoping X3E fixes these incompatibilities.

If third party developers want to contact Cakewalk they can I'm sure.... Cheers..

jbraner
Thanks for the replies - It's good to know it's not just me!
 
The VST3 versions load fine in X3 but
Dude and brconflict - are you having problems saving settings? Do check because I just got an email from Dave Gamble @ dmgaudio saying that there was a problem with this. He says there is a version 1.07 (Equilibrium) and 1.11 (Compassion) on the server, so I will check this.

I just upgraded to Windows 8.1, and Sonar isn't recognizing the .vst3 DMG versions. So, this is new for me. I haven't been able to test the rest.

Alex,
 
I was being sarcastic - thanks for not taking it personally
 
Anyway - my problem is *not* fixed. I thought it was, but it's not

VST2 Equilibrium crashes SONAR
VST3 Equilibrium - just like the last version, if you save a project and reopen SONAR - the Q values are not saved!

VST2 compassion does not save settings when you close the project and reopen. It changes to whatever is the first preset in the bank that's loaded. AND it turns a stereo interleave track to mono - and you can't change back.
VST3 Compassion does the same "not saving settings" and loads the first preset in the current bank.

 
Other plugins:
Linplug's RMV - see Brando's reply above. This crashes just like the VST2 version of Equilibrium
 
Waves CLA plugins (VST3) and Plugin Alliance's Dynamic Spectrum Mapper
http://forum.cakewalk.com...settings-m2963965.aspx
 
Voxengo Soniformer VST3
http://forum.cakewalk.com/X3-Voxengo-Soniformer-VST3-Settings-Not-Retained-m2964341.aspx
 
 
Please don't tell us to do a reset and a rescan OK?
 
EDIT: Oh yeah, also - these are not just "corrupted" presets not being saved, they are new ones. Technically, we're not talking about saving presets anyway. You should be able to change a plugin settings, and that should be retained when you save the SONAR project. I'm still wondering if something is being cached that shouldn't be, or vice versa - something not being cached that should be...
 
Without wanting to be a wiseguy - I just think it would be easier if Cakewalk told us what they changed - they *have* changed something or all these plugins would work like they did in X2 and even (although I can't prove it) possibly X3c.

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.
 
> Please don't tell us to do a reset and a rescan OK?
 
Sorry but I didn't tell you to do anything... I politely gave my advice and I asked you if had performed a VST reset and you don't seem to want to answer, ok then, again I am still politely enquiring:
 
Are you running X3D?
You may have issues with previous presets but what about new presets? (In new X3D projects after you reset and rescans VSTs). (As you edited your thread I crossed this out).
 
And please no need to respond anymore if you don't feel like giving out this information, I'm feeling some bad vibes, I shall happily move onto another thread if there's some sort of issue.
 
UPDATE - Nevermind Cakewalk are onto it I shall politely exit this thread.

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...

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?

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.

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

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.