I think you guys should be looking for a common solution to your problem here rather than just saying its x2.
everyones computer is different as is every version of sonar.
but I haven't experienced any of these graphical glitches myself and not a few of these other problems either.
but it could very well be maybe a windows update that made things different, possibly a graphic card/os issue.
possibly soundcard issues, it could be anything.

trust me im the first person to say sonar would suk.
I paid good money for it and if theres something not right im very vocal.
but ive been using sonar in a professional studio almost 8 hours a day and then bringing this work home at night sometimes for another 3-4 hours and its been very solid.
I haven't had a crash in almost 2 months.
I narrowed that down to a third party plug in (32 it) in a 64 bit system.

please, before you give up, don't get discouraged.
I know that's easier said than done but don't, work together and solve some of the issues that are in your control.
how do I know these issues are in your control ?
because im not having them.
not all of them anyway, some I haven't yet got a chance to verify as ive been swamped with work here.

my best to you all.
you paid good money, cake can fix some things but other things are up to us. :)

Bob thanks. I've replied to your post on the X2a stability thread. I'll report results back later... thank you for your help. similarly Charlie. appreciate your attention on this mate. I'm all over the self diagnosis thing. I have a roll back point on w7 which I will go back to tonight. basically it's a fresh W7 install, with Sonar installed. let's see if it makes a difference. I'm not holding my breath mind you. I have been around Sonar for many years and I know how to optimise a DAW. I am convinced what I and others are experiencing are bugs but given the lack of recognition this issue is getting from support I will pursue my own path as you suggest.

Bob
Thanks for the input - I'm away from my machine for the next couple of days - I'll get back to you soon as I can
Nigel

I have been around Sonar for many years and I know how to optimise a DAW.

Really? What did you do to optimize your DAW? Did you overclock the CPU or the chipset? IMHO, Windows 7 or 8 don't really need any optimizing.

Dave, agreed. With W7 out the box with enough memory you shouldn't need to. especially on a Cakewalk approved pc such as I have which is a HPZ420 and a decent soundcard. Pre windows 7 different story! cheers Michael

So, my crashes appear to be happening when I click on a bus. Happened twice tonight. Both times when I clicked on a bus to make some adjustments. 1st time the Master bus, 2nd time the drum bus.
?
Intel i5. Windows 7 64 bit. 8 gigs RAM. 2 hard drives (1 for programs, 1 for audio), X2a

rodreb


So, my crashes appear to be happening when I click on a bus. Happened twice tonight. Both times when I clicked on a bus to make some adjustments. 1st time the Master bus, 2nd time the drum bus.
?
Intel i5. Windows 7 64 bit. 8 gigs RAM. 2 hard drives (1 for programs, 1 for audio), X2a

Can you detail what, if anything is on each bus?  Also, what adjustments were you trying to make when it crashed?

Thanks, 

Bob Bone

Do you have the Pro Channel (PC) open in the inspector view?  If you do, try collapsing the inspector to see if it still does this.  Alternatively, try setting the inspector to the clip or bus view instead of PC to see if that helps.
 
GLen

Sounds to me like you have some bad memory. I'd run a full memory test in Windows or using memtest. Or a bad plug-in... What plug-ins are you using?

there are others posting about crashes when touching the master bus when the console view is floated. I float the multi-doc and have the CV docked. I am not having any crashes. I also ran the same setup on my older quad core and did not have any crashes related the the bus. Hope you get it sorted.