Workaround for Crash Issue?

I have invested many hours in a song.  It is nearly complete.  When I try to edit it, Sonar crashes: I get the faded out screen with the message that the Teleport server is not working.
 
Details:
 
- Project has several MIDI tracks driving external sequencers.
- Project also has some tracks with short sound effects: WAV files I imported.
- Project also has SI Bass, Session Drummer 3, RealGuitar, and six instances of Vienna Symphonic.
- Crash happens when I edit the last instance of Vienna by (a) adding a controller message in Event List, or (b) dragging a MIDI clip from another track into it.
 
This file has always been weird: I used to have to open it by shift clicking and then saying OK to all the plug-ins one-by-one (although I am not sure why that mattered).  It was fine for quite a while until I got to this last Vienna instance.
 
Although I have a number of VIs plus some Lexicon plug-ins, the number does not seem excessive for a 64-bit i7 with 12 GB memory.
 
Thoughts?
 
Thanks.
 
 

Teleport server errors are related to Bit Bridge. I used to get them all the time when using the Korg Legacy series in SONAR 64. I solved this by switching several of my 32 bit vstis to jBridge and all is well. If you're not familiar jBridge is a third party wrapper for using 32 bit plug-ins in a 64 bit host. It's not free, but worth the small price. If you already have it on your system, switch the offending plug-ins over to it and those errors should go away.

So.... workaround. I'd try freezing a bunch of stuff, then saving the project. After that, I'd restart the machine entirely to make sure everything is flushed out and see how it works then.

konradh

Although I have a number of VIs plus some Lexicon plug-ins, the number does not seem excessive for a 64-bit i7 with 12 GB memory.
 
Thoughts?

This is exactly why I don't use X1 64bit anymore and use X1 32 bit ... to avoid Bitbridge. Don't use X1 x64. There's really no need to.

Plus, you should be freezing your tracks when you are done recording them anyway for two reasons.

1. To free up your CPU and RAM.

2. Say a couple of years from now you want to open up this project again, but some of the synth's you used are no longer included with Sonar? You're screwed if you don't have the old version of Sonar installed.

Freeze freeze freeze and unload your CPU and RAM. It's the only way to get around these problems if people keep insisting on running Sonar 64 bit while using 32 bit plugs/synth's.

to avoid Bitbridge. Don't use X1 x64. There's really no need to.

 
 
i know where you are coming from Bub, but its not that simple,  i would imagine that it is not just a simple matter of reverting back to X1 32bit. i have been native 64 a long time now. i maybe have only 2 or 3 go to plugs that are not 64bit yet. i myself go beyond the 3gb RAM limit in 32bit all the time, and i havent had to freeze a track since Sonar 7. alot of us just have to wait it out until we are finally once and for all done with bitbridge/jb.

Thanks for the thoughts and ideas.  My bad for not mentioning that I had already tried freezing most of the VIs.

I will look into JBridge.