Your experience is very much on the same lines as mine Steven

My only problems were a few issue from Sonar to Producer - some problems with the EQ, but I was able to solve it.

I can't say if x2a or x3c is to fault for the corruption of CWAs here..I only have a few saves in x3c, one of which went hairy...and will not open, which was the first one made in the new build...But it seems x3c will not open a lot of my x2a projects if any.. X3c gives me a error and option to send a file report, and or ticket...my option is forced to closing out with out sending.. (I turn off my internet on this system in bios, so sometimes I cannot send reports when it happens)..and then Sonar X3c shuts down.
 
So I turned my Nic on, and sent a few reports....wink....but as my nic is said to interfere with my Allen and Heath audio solution...It may now be tainting the results in the error report or now partly to cause them.
 
Sir Les

I had a project file truncated to 51K the other day. It was normally around 4500K. When I opened it I was presented with an empty project - weeks worth of MIDI data just gone. I was able to recover a previous version in Gobbler, but it make me worry what was up.

The project has stability issues anyway, possibly related to third party stuff, but it's crashed a few times and especially on exit. I've been racking my brains to work out exactly what I did the last time I saved it. One theory I'm toying with is that I had a crash just before I was done for the night, and it gave me the "would you like Sonar to try and save a recovery of your work" type message, and instead of clicking no (I'd probably just saved it a few minutes before) I accidentally clicked yes, and that's when it saved a truncated file.

This same project sometimes crashes Sonar when I launch it. I think I'm going to have to try and get to the bottom of why it's so unstable tonight, because it worries me Gobbler or no Gobbler.

I am wondering if a bunch of the corruption occurs in projects where there are 32-bit plugins running in a 64-bit Sonar.
 
Can some of the folks who have had many instances of corruption please respond on this aspect?
 
And, if there are indeed 32-bit plugs in these corrupted projects, can you please list which ones are present?  Perhaps some kind of pattern can be observed.
 
I am just trying to see if there are 'environmental patterns' to some of this, where maybe we can collectively get better at avoiding corrupting projects moving forward.
 
Thanks, 
 
Bob Bone
 

I now have SONAR X2 and it will no longer properly open .CWB files. The track clips continually show as "busy".
I have Music Creator which will not recognize the SONAR .CWB files. SONAR X2 will not open the Music Creator .cwb files - same "busy" error on the clips. However, Music Creator opens these files just fine. So it appears the problem lies somewhere inside SONAR.
 
This is across two different machines with two different operating systems. Desktop with Win 7 PRO and a laptop with Vista Ultimate 32 bit.

I suggest you start a new thread about this particular problem. Vista isn't directly supported any longer.

I've had it happen. That's why it's a really good idea to have Sonar auto back up your project. I had it happen the other night when Sonar froze up. When I tried to open it back up it said the file was truncated (half of it missing). I opened the backup and everything was fine. I have Sonar set to back up at every 5 changes. So I never lose much of anything.

ampfixer
I suggest you start a new thread about this particular problem. Vista isn't directly supported any longer.

 In case you didn't noticed,  I said the problem occurs across multiple OSs....therefore it ISN'T the OS.
 

Unless you are the OP it's best to start a new thread rather than resurrect/piggy back on something from 4 years ago. Likely to cause confusion as it has done already. ta.