I see there are still threads around with "X3c" and "crashes" in their titles, yet they go over pages and get really hard to keep up with on a limited time budget; these threads don't seem to come to definite conclusions or real solutions ... or maybe I just blanked out reading through the 40th post ...
 
So, anything definite with X3c which could be identified to stay clear off that would get you into crashing territory??? Some hard fact like the 64 bit engine bug causing the hum and all sort of other issues???
 
The reason I ask is that I can work with X3c for hours and be a real happy camper, but then unexpectedly one project just will go nuts on me (i.e. it won't open after save, or crash when freezing tracks, ...) yet these things are hardly ever reproducible (and if they are, Cakewalk support ignores them anyway).
 
One thing I've come to realize is that X3c does not like projects or templates created in X2; using them will eventually bite you ... not straight away, but once the project gets complicated (e.g. goes beyond the 50+ track count, requires advanced routing/SC, etc) - not being able to feed on leftovers from previous work is a real bummer since it makes it either unsafe to pull things in from previous projects or time consuming if you don't and always start over ...
 
The 2nd unsafe bet is the freeze/unfreeze functionality where I managed to crash with quite a few plugs from different vendors (melodyne, fabfilter synths, kontakt 5, ...)
 
 
 
 

FreeFlyBertl
One thing I've come to realize is that X3c does not like projects or templates created in X2

+1

Don't have more than one VSTi at a time sending MIDI events out with the "Enable MIDI Output" turned on.
 
!!Crash!!

Why not bump your thread with your specific issue. Talking about crashes in a general is a total waste of time because there are always different reasons and it's generally down to your environment. I'm running Sonar X3C just fine and actually I'm using quite a few old X2A projects now with it now as well as new projects. I've had a few X3 crashes but I've known exactly why each time and I've reported them to Cake if necessary (all apart from one were third party issues).
 
So please stop talking around your issue get your old thread back.
 
cheers.

SilkTone
Don't have more than one VSTi at a time sending MIDI events out with the "Enable MIDI Output" turned on.
 
!!Crash!!

Has this been reported to Sonar with specific steps to reproduce?
http://www.cakewalk.com/s...act/problemreport.aspx
 
Thanks.

 Dependant, Audio Device issues with other devices or OS  with  undone setup, can cause crashes...with sonar or any other DAW...So issues are not always defined, and can be masked by latency like symptoms .... changing buffers do not solve for the symptom, most techs believe is the solution...So if it does not resolve it, then it is not a latency problem with the audio cards performance...it is a sharing or being interrupted by something else...sharing irqs or service or app causing the latency symptom like problem...which can cause crashing!...mostly clicks pops and drop outs are noted first.
 
 
 

CakeAlexS

SilkTone
Don't have more than one VSTi at a time sending MIDI events out with the "Enable MIDI Output" turned on.
 
!!Crash!!

Has this been reported to Sonar with specific steps to reproduce?
http://www.cakewalk.com/s...act/problemreport.aspx
 
Thanks.

Yes, as CWBRN-2504 on 03/22/2010. We are now at CWBRN-22142, so that means there have been almost 20,000 reports since then. And yet to this day Sonar still can't route its way out of a paper bag.

Jlien X

FreeFlyBertl
One thing I've come to realize is that X3c does not like projects or templates created in X2

+1

 
OK, at least i'm not alone on this one ... yet, I don't expect any improvement here with X3d
 
 

CakeAlexS
Why not bump your thread with your specific issue. Talking about crashes in a general is a total waste of time because there are always different reasons and it's generally down to your environment. I'm running Sonar X3C just fine and actually I'm using quite a few old X2A projects now with it now as well as new projects. I've had a few X3 crashes but I've known exactly why each time and I've reported them to Cake if necessary (all apart from one were third party issues).
 
So please stop talking around your issue get your old thread back.
 
cheers.

 
Well, I don't agree - otherwise I wouldn't have started this. Remember the discussion about the 64 bit engine: No everyone knows, turns it off and lives much happier ...
 
I wish I'd be as lucky as you and know each time exactly why the software decided not to work. Maybe you can explain these two examples:
 
Example A: I import a track template consisting of 4 tracks and 3 busses into project #1 and #2. Everything works fine, no problem for hours. Imported the same template into project #3 and it does no longer open after save. I start from a backup and repeat. Same result. I check project #1 and #2, which open fine. I start from the backup and do some other things (like freezing synths which have nothing to do with the template to be imported, but of course change the structure and size of the saved file) and then try again, it works ... lost 2.5 hrs going back and forth between projects finding some dogdy workaround  ...
 
Example B: Freezing Kontact takes ages. I see in the audio directory that after freezing one Kontakt track, it freezes the FabFilter synth, then one Kontakt track, then again FabFilter. So without being asked it freezes the same FabFilter synth 64 times wasting about half an hour. In this case, I'm as lucky as you are Alex, and know exactly what it is: I have linked MIDI clips in one Kontakt 5 track and the FabFilter track. Doesn't make sense when it comes to causing that freezing issues described, yet that's it. I break the link betwen the clips and and think I'm sorted. I click freeze and BOOM! There you go ... no go figure and, of course, this can only be down to my environment ...
 
 

SilkTone
Don't have more than one VSTi at a time sending MIDI events out with the "Enable MIDI Output" turned on.
 
!!Crash!!

 
Thanks. That's a valuable post  and worth going after to check. I wonder if that option may be active in some of the VST related issues I've encoutered. I know this is an option when insert the synth (and never really cared about it), but where do I check/disable once the VST is in the project?

<< deleted - double post >>

i believe we need what is commonly referred to as a "known issues list"...