Just lost most of the project I have been working on for several hours. Vocals, keys, harmony guitars all gone in a white screen of failure and  buggy sonar.  Don't tell me it's my fault for not saving every five minutes or whatever. That is a lame exuse for poorly coded and buggy as hell software. I have used sonar since version 2. This version has crashed more in the last several months than all the others combined.  Each time my computer faithfully sends a report into some  black hole of data that I have not seen make any difference.  Win 7 64 bit and  Sonar X2a 64.   Not happy camper.... arrgh!!

That sucks. However it has to be said that frequent saving is a must no matter what program you're working with. If I'm working in Photoshop I save every few minutes, even though the thing has never once crashed on me. I even do the same when I'm working in Excel, and I've never heard of that crashing on anyone. Even with a 100% stable program, who's to say the power isn't going to go out at any minute? 

DAW's crash. Pro Tools used to crash on me regularly and it's the "industry standard." Another way to look at it is, it gave you several hours without a crash. And who knows what caused it? Could have been a poorly coded plug or a driver bug that only shows itself once in a blue moon. 

For the record I've had very very few crashes since the quickfix, and the only crash I've had in X2a was when I tried to put Cakewalk's tape sim on the master bus....that pretty much crashes the program for me 50% of the time, so I always make sure to save before doing it. 

Hi Steve,

That happened to me last night. Lost 2 hours of recordings.

I normally have Auto-Save set up to save every 60 seconds. That doesn't mean it saves that often, it doesn't do anything while you are actually recording, but it does ensure that when I am recording and hit 'Stop', the project is saved. This does not effect your original project. You'll still have to save that, or hit Ctrl-S when you want to save that main project. Auto-Save saves your project with the extra word 'Auto' in the title.

I normally do this, but have only used X2 to remix old tracks since it came out. Just this week is when I started recording with it, and it's not working so well and I forgot to set up Auto-Save. I did a fresh install of everything when I got X2 and forgot to set it up because I wasn't doing any recording at that time.

Your wav's are probably all still there in your audio folder, but you'll have to line them up manually ... a huge pain in the ass, but it can be done if they are there. They are usually there, what gets lost is your cwp file with all the track info as to where the wav's should be.

Set up Auto-Save ... you'll still have crashes, but you won't lose hours of work.

Honestly, Cakewalk would do themselves a big favor by making Auto-Save on by default ... there would be no threads like this unless someone turned it off ... then they only have themselves to blame.

The X's are buggy, no doubt. They are the most picky version of Sonar I've ever used when it comes to what system they will run on. I've been using Cakewalk/Sonar since CPA9.

Auto-Save!

I can't say it enough.

Cake should make it on by default.

Been working for the last two days on a project in x2a...very screwy and crash prone as regards VST plugs...especially UAD and Softube for me.  Other anomalies as well.  So far, even with the latest version, not ready for prime time.  Dern!!!

Right off,the OP's description sounds exactly like day one on X2[sending reports] BEFORE the "Quick Fix"??,and X2a includes this,so..

Yeah Iv'e had weirdness,but I set it to save every 3 changes or whatever,but some days,absolutely nothing goes wrong..nada,so I don't even consider going back to X1d expanded.

To be honest ever since using a great performing,for the price here[32 samples 8ms Round Trip Latency Measured Properly with this:http://www.oblique-audio.com/free/rtlutility]Native Instruments KA 6 USB 2.0 interface,I have had odd things happen-blue screens,ONLY whilst leaving the room,while on the net?,weird long shutdowns,where I have to force shut off,but will fire back up like nothing odd has happenned?


So on I go,and 90% of Sonar time no badness[as long as Ctrl+S,or "save every 3] ,+ this laptop is in a dusty,cigarrette smoke filled enviroment,so I'm just amazed it's all working as well as it is.


I haven't really fired up my faultless desktop due to summers heat[12 days of 40c +!!]and the room it's in is not insulated,but will see,when we experience autumn,and maybe be[?] surprised,as nothing EVER went wrong under X1c,d on THAT machine,and I always only have 64 bit installed.and 32 bit plugs[the few that I actually use]run fine wit the "standard" bit bridge[teleport server] 
Bob

yorolpal


Been working for the last two days on a project in x2a...very screwy and crash prone as regards VST plugs...especially UAD and Softube for me.  Other anomalies as well.  So far, even with the latest version, not ready for prime time.  Dern!!!

Melodyne act weird sometimes in SONAR X2a x64 too?
Bad audio after rendering back track in SONAR X2a also?
Also Open a saved project and continue editing in Melodyne on a specific Melodyne track give you bad audio, robotic sounding and sometimes. It even sometimes  "cut off the audio stream" completely?

 
 
http://www.celemony.com/userforum/viewtopic.php?f=13&t=14325
Best Regards
Freddie

Cakewalk Problem Report Form

Thank you Freddie !

We have received your report. Your report number is as follows: CWBRN-14580

I had Sonar crash on me last night. I was using Dimension Pro and tried to load a patch and that was it. Project all gone. Fortunately for me I just started the project and I have not recorded anything yet.

Sonar has not done that since the initial version of X2 was released. I am probably going to get flamed for this but.....I switched to the 32 bit version. The reason why I did is because for me it has been more stable. I still read through the forum and see people complain about crashes and then I look to see what version they are running in their system specs.

To be honest I can't say that the 32 bit is more stable then the 64 bit version, but I can say it has given me less problems. Last nights crash was the first one in a long time. I am not saying this is a fix! everyone's computer is different.

If I had to do it over again I would buy a different Computer, for now 32 bit works fine and I am waiting for X2b or X2c before I start using 64 bit again.

Running 64 bit X2a with Steven Slate SSD4, 11 Slate VCC, 11 Slate Tape Machines, 1 Slate FG-X, 2 UAD Massive Passive, UAD Buss Compressor, 4 UAD Neve 88RS. No crashes, no issues. So far, so good.

Hi
I had X2 crashes too the last days.
Than I remembered an Nvidia graphic card Driver update to version 310.99 the other day . 
The graphic driver has been the reason for crashes here a while ago. 
And guess what:
Since I´m using the older driver( version 275.33, everything is running well.
Hope this helps anyone.
Pragi