Sonar X2 - problem with soft synths

Hello, new to the forum here. I was wondering if anyone was having issues with opening and closing synths in the synth rack of X2 or X2a?
 
I have all working well in Sonar X1d and installed X2 recently. I can add synths in X2 no problem but when I turn the synth off and try to reconnect it, the RAM indicator in Sonar goes wild and crashes Sonar. This is not with any particular synth, they all seem to do it. If I leave them all running, it works fine. I like to turn synths off that I'm not using though.
 
I am using 32 bit and 64 bit synths in Sonar 64bit on a 64 bit PC. I have Sonar X1d also installed as 32 bit for opening older sessions. I'm only having this problem in X2, also after update to X2a
 
System: Intel Core i7-3930K CPU @ 3.20, 32 GB DDR3, Intel SSD 420 GB sys drive, 2 WD 2 TB SATA DRIVES. 3X MOTU 2408 Mk3
 
Thanks and please let me know if more info is required!
FD
--------
PS> Also noticing this behavior is the same with only one synth. Even the native Sl strings that comes with Sonar. I tested 32 bit synths alone and 64 bit ones. Same result. Crash if I turn off the synth and then turn it back on.
 
I'm wondering if it's related to having X1 installed first and then the automatic migration of settings causing X2 to act strange with VST synths. Not having this issue with plugs either. I tried the note about resetting the vst folder and rescanning.
Thanks

First I have ever heard of that particular issue.Certainly isn't your system specs. But you list 3 Audio interfaces-do you mean they are synced and you use all three at once?
 
I think most here so not uninstall X1 when they go to X2-I didn't.
As Tom mentioned why would you turn them off?
 
32 GB ram and a zillion i\o- I don't see the need.
 
Anyway, I tried very hard to reproduce the issue but couldn't. Not much help, sorry.

If you're trying to turn off synths to save CPU, archiving the tracks will take them completely off the CPU load, then you can hide the archived track.

I've never seen the issue you're describing, but I don't turn on and off synths the same way you do, using the synth rack,
and I never use any 32 bit synths.

After I've inserted a synth, I bring it up by double-clicking the track icon. To take a synth offline, I archive the track.
Occasionally, if I want to purge a synth from the project, then I will go to the synth rack and delete it.

Have you tried turning on and off these synths in the synth rack with the audio engine turned off ? (the blue light in the controller bar)
This might indicate if it's something to do with your soundcard settings, possibly.

noynekker, thanks! I'll try to use archive to freeze the synth track and see if I have the problem. Great idea!
FD

Give this a try - rescan all of your plugins.  

Bob Bone

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  
 
 
 

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

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

 
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
 
 
 
 

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

 
So, at this point I believe the problem does relate to the Asio driver.... is everyone that hasn't had this problem using asio drivers?