Thanks for the work-around ideas. I have scanned the VST directory several times, it finds everything as it normally does. 
 
Freezing synth doesn't cause the problem which is good. But you can only freeze a synth that has midi data recorded.
I just want to open a fresh Sonar file that loads up with all my various synths but not connected. I have this working beutifly in X1d. I've also never had a synth crash or cause problems from being enabled or disabled in any version of Sonar, so this is strange.
 
At the very least, I would consider this a bug that others may encounter. I mentioned I had tested this on my sons win 8 computer and the problem wasn't there. He has no other audio programs though. This problem happens when installing X2 on a system that already has an earlier Sonar version installed and configured. When you migrate your preferences, something goes wrong. I've tried various ways to install, where I don't allow it to migrate etc. but the problem still happens.
 
The X2a update also suggests "resetting" your VST directory and then rescanning it which causes some synths to not even open or act like they weren't installed.  
 
This is all being set up on a brand new machine, fresh win 8 etc. So the registry is in good shape.
I'm going to try a few other things but at this point it looks like I might have to wipe my machine clean of audio apps and start fresh with X2 to have this problem go away. It's unfortunate though as a lot of time was spent loading libraries etc.
 
I would just leave X1d on there as it's working perfectly but I want the new X2 features SO BAD!!! Some really great features in this version!
thanks  
 
 
 

Quick update:
I created a system restore point, uninstalled all my versions of sonar - X1 32bit X1 64bit and X2a 64bit.
Then I killed all folders relating to sonar on C drive. I didn't go through the registry and delete anything however.
I reinstalled only X2a 64 bit. Of course it automatically found everything and was already set up, despite the fact that I killed all the folders.
Problem with the synth rack still there.
I sys restored back to where I was with all versions back again. Working as it was.
 
I guess if I try it again I'd need to dig deeper looking for Sonar files to remove so it's a clean install.
FD 
 

Hey FluffyDog,  Just what do you mean by turning off the synth from the synth rack?  Are you deleting it?  this is a new concept for me.  There were some changes made to the delete synth process from the synth rack in X1 from earlier behavior but I think that X2 is the same as X1.
 
Glen

Hey Glen, not deleting the synth, turning it on or off. You can turn a synth on or off by right clicking on the synth dropdown and selecting "connect synth" or "disconnect synth". In version 8 and earlier the icon itself was the power button. (They should bring that one back! Less clicking!)
 
FD

I have tested several synths out, disconnecting and reconnecting them, and have no issues whatsoever when I do that.

Perhaps there is something else causing this to happen when you are doing this?

Bob Bone

Thanks FD.  Always learning new things here.  Something new for me to play with.  This might be handy in my templates.
 
Glen

 
The problem is resolved and is what I suspected (something odd in the way x2 migrates the older settings and vsts):
 
I first copied all my Vstplugins folders from the various cakewalk locations.
i did a screen shot of my vst scan paths as they would be removed after a clean install.
I then completely uninstalled all versions of Sonar. I used this method to remove important files left in the registry-in message #4 here:
http://forum.cakewalk.com/fb.ashx?m=2437977 
 
I rebooted and installed X2 with updates to X2a.
This time it didn't ask to migrate settings and also wanted to run the wave profiler test. I new this was a good sign as it would not be using the old settings that might have a problem.
 
After booting up Sonar I checked the synths that come with X2 and the problem I was having was gone! Now I would have to put back the old vst scan paths and rescan my vsts.
Everything showed up and loaded fine; plus, the problem was indeed gone. I could open and close synths in a flash without any RAM spikes etc.
 
I had one synth (Superior drummer) that loaded but can't find it's sounds which I'll deal with now. (Perhaps SD caused the problem? Probably not but worth jotting down)
 
In conclusion I can only assume the problem was related to X2 not migrating the settings properly from the earlier X1 install. If anyone else has this problem I hope something here might help.
 
Thank you everyone who chimed in!
FD
 
 
 
 

 
PS. There are many good reasons to turn synths on or off:
 
- In my case, I am creating the default sonar template, when it loads, it has every synth I own inserted and ready to enable should I want to. The file loads in the same time it takes to open the regular default template. (a little less than one second..) When I need a synth, I simply enable it and off I go. Some synths like Kontakt may be running several different sounds which I don't want to be bounced together like they would be if I "froze" the synth. I simply bounce the sperate midi tracks down to audio as I want them laid out and turn off the synth until I need it again.  
 
*I could have my default template open sonar with all these synths connected, but it's a 14 second wait to open the program. Plus I might only wish to use one of the synths so it's not worth waiting for.
 
Also. when you have 100 + audio tracks, a video file playing, a zillion plugins and synths, it makes sense to turn things off that you aren't using. Even if you have a ton of ram... musicians usually tend to try to max out whatever they have right? lol
 
FD
 
 
 
 
 
 

Hey Robert, did you migrate from X1 to X2? Just wondering if that's part of the issue.
FD

Okay... more to the story...
As I configure my new install I realize I get the problem back when I change the default wdm drivers to Asio drivers.
So I system restore back to when I had all versions installed and switch the driver to Wdm/ks in X2 and the problem goes away!
 
But, obviously I want to use Asio... hmmm
 
Is it possible I need to install the Motu soundcard's 32 bit driver? I only installed the 64 bit windows driver. Is it possible I need both because I'm using some 32 bit synths?
 
Still, don't have the problem in X1 so probably not the reason...
Asio?
Tricky one...