robert_e_bone
Hang on - the VST 2 versions work just fine in X3e.  You just have to get rid of the VTS 3 versions - until the issues get fixed.
 
There is NO reason to drop the whole bunch of them, and VST 2 modules sound the same as their VST 3 versions, so you aren't losing a thing, other than whatever functions a VST 3 version brings to the table.
 
Bob Bone
 

Exactly.  I do not think any of these plugins use "per note expression" or any of the extra features added in VST3. If I  understand it correctly the CPU savings are possible but do depend on the plugin being written to take advantage of that feature.
I found I had to completly uninstall and than reinstall to get rid of the the VST3 versions.
 

That is what I did too -
 
There might have been a more elegant way, but I am not an elegant guy.
 
Anyways, all the VST 2 versions work great.
 
Bob Bone
 

robert_e_bone
Hang on - the VST 2 versions work just fine in X3e.  You just have to get rid of the VTS 3 versions - until the issues get fixed.
 
There is NO reason to drop the whole bunch of them, and VST 2 modules sound the same as their VST 3 versions, so you aren't losing a thing, other than whatever functions a VST 3 version brings to the table.
 
Bob Bone
 

 
Oh - derr... thanks. I didn't realize that there were VST2 versions. I get what you mean now. Thanks for the clarification.

I did not mean to 'sound' like I was chastising you with my caps from the above post - those were only for emphasis.  :)
 
Glad you circled back and got what I had been trying to explain.
 
Please give that a shot and post back.
 
Bob Bone
 

I just got the 15th Anniversary group as well, what a great deal!
 
Thanks for the info - I had just gotten through workarounds with the standalone versions of each vsynth, seems they didn't care for my ASIO so had to install ASIO4ALL. Hopefully not a problem to leave it installed - so far so good!
 
Once I got that sorted out I had the VST3 issue going with Sonar, found the temporary VST2 fix in this forum. I actually don't know what the differences are between VST2/3 yet, but it's one higher so it must be better!
 
 

If I could not get a synth standalone running. I would rather run the synths inside VSTHost or SAVIHost before installing ASIO4ALL.

Congrats on picking that up - I got the same collection for a sale back around Xmas-time and am also loving the sounds.
 
I am a bit confused as to what sort of ASIO issues you were having with the stand-alone versions of the plugins.  Can you please elaborate?  
 
By the way, those stand-alone versions appear to be 32-bit = don't think it is an issue, just odd, since they have both 32 and 64-bit dll's.
 
It just seems quite odd you would have ASIO problems, and then have those go away with ASIO4ALL.  (I don't think ASIO4ALL is generally a good choice when there is an actual audio interface present).
 
Bob Bone
 

Yes, the standalone synth would load, but attempting to change from Windows Direct driver to ASIO the app would immediately crash. 
 
I found the ASIO4ALL workaround  at  but what's different for me is when I  remove ASIO4ALL the crashes resume. 
 
Maybe it is a 32bit app vs 64bit driver issue, thanks for the clue :) I'll look at that some more later today.
 
 

Some 32-bit plugins definitely do not play well in 64-bit Sonar.
 
But if those are the issue, then you should be able to open Sonar in a new project, or in no project, and change over to ASIO of your audio interface, and it should not then crash.  What happens when you do this?
 
It would really help me to help you if you posted more detail as to what is in place and what is loaded, and that sort of thing, because this does not seem to happen to lots of folks - meaning it is likely something unique to your system or your steps.  Thanks, 
 
Bob Bone
 

For instance, I was having all sorts of horrific noises coming from my audio interface, for roughly the past 2 weeks, and I was going nuts trying to figure it out.
 
Turned out to be something goofy in the driver that just started acting up, and it happened that the vendor of my audio interface, Presonus, released a new driver version last Monday, and changing over to that completely fixed everything.
 
So, let's get a clear picture of your system, your settings, and the steps you are performing when these crashes occur - I think this is likely solvable.
 
Bob Bone