I don't use double monitors but I appreciate the heads up on this. It's also making my decision to use a pre master bus for effects/level/etc tweaks seem like an even better idea. Wonder why it's just the Master doing this. Something to do with the Master being linked directly to the hardware outs?

I just contacted Tech Support and after having a nice conversation with them neither I nor the Tech Support could reproduced this problem.

I know it is still a problem I just can't nail it down. I can not come up with a fool proof recipe. We all need to compare notes and find a common cause. 


 

Right I got the same reply. Thats why I called them as instructed. 

After a Windows Update, I can no longer replicate the problem. I'm thinking it was a temporary Windows bug.

John


I just contacted Tech Support and after having a nice conversation with them neither I nor the Tech Support could reproduced this problem.

I know it is still a problem I just can't nail it down. I can not come up with a fool proof recipe. We all need to compare notes and find a common cause. 

+1


Yeah. so.. How about we list our specs and end the post if we can replicate the bug or not? maybe we can find a common thread. I really appreciate all you people that participate in this discussion even though you don't get the crash. Thanks for that :)
So this is me:

• Motherboard: Asus P8Z68-V PRO/GEN3 Z68 S-1155 ATX
• CPU: Intel Core i7-2600 @ 3.40GHz   3.4GHz 
• RAM: 16Gb
• Audio interface: RME DSPe RayDAT
• Video Card: Asus Geforce GTX 560 TI DCII
• Sonar X2a 64bit
• I get the crah

I get this ALL THE TIME! So much in fact I've started looking at how much of a pain it would be to move to Reaper or PT... Two monitors, one with track view, one with console view. Click on something in the console view, crash. This problem has basically led to two very large projects becoming corrupted and me have to piece things back together manually (basically rebuilding all the track by adding back in the wave files by hand) cursing and screaming the whole time. I've have a few comments: 1. it doesn't have to be the master bus: I had an acoustic guitar bus with a HPF in the Pro Channel EQ that I wanted to A/B while playing -> crash. You hit play in the track view, so that window has the focus, while playing, click a button in the console... see below. 2. I find if you stop playback, click on the title bar of the console view to give it "focus" (in stock Win 7 classic view the title bar goes from grey to blue), then you can click away. 3. Someone mentioned VCC seeming to help this problem show up, and that seems to be the case for me as well. I don't believe VCC to be the cause as it has worked rock solid in the past (same version), but it could have some interplay with vst or graphics handling. I've sent in crash reports and have yet to hear back from CW that any progress has been made (this is over the past few months). If I have to pay for this fix with X3, Reaper may be in my future and I will have wasted a lot of money on Pro Channel add-ons... (luckily all purchased on sale). Having to rebuild projects from scratch is a HORRIBLE thing that I wouldn't want to inflict on my worst enemy...

I'm not sure where anyone has questioned us on this thread about user error.

In many threads from my own experience of helping people it is a common determination and occurrence.  

Clearly it has been confirmed here by me and many others that there is a problem. It is just not showing on all systems. 

hey manny.

this is my theory.. it must be your computer...haaa.
just kidding man.

good job on the viddy-o bro.
I watched it many times before coming to a conclusion.
im wondering first, is it only the master bus your getting the crash with?
does it happen if you touch anything else, like a bus ?...metronome track ?

see when I use sonar with 3 screens, every once in awhile if I click outside the box into something like windows explorer to grab a file to drop I get a freeze, but it soon comes back within a few seconds.

is it possible your focus is on the main screen and by touching a monitor that hasn't been active yet it may freeze like mine only yours is going right to crash.
dare I say it has something to do with the vs 700, you have a great machine there man. its very nice.
but that may be the problem why some others are not getting this and you are, because we don't have the vs 700.

I cant reproduce this either but I can very well see you can and that flys with me.
x1 and x2 do seem like 2 different animals and though ive been having great success here that doesn't help you any.
sorry to hear about this man and if im too far off base with my theorys im sorry.

im hoping maybe something I say can lead you to a new road and solutions.

my best.

Dan Cate [Cakewalk
]

Hi Folks,

Those of you experiencing this crash with the master bus, do you have the Concrete Limiter ProChannel Module installed and on either the track or bus you are clicking?

Thanks

For me, it does appear to only happen if Concrete Limiter is on the Master Bus.  As soon as I removed it, it stopped crashing.
 
This was only after a quick try, I'll experiment further when I have time.
 
Thanks for popping in, Dan.

I notice both John T and cuitlahac both seem to be saying that they don't have concrete limiter on master when it happens.
 
As I've stated before, I use both monitors as one extended screen, with Sonar stretched over both, so I had not seen it until trying to help in this thread.
 
In the project I tested after Dan's post, removing the CL stopped it crashing, re-inserting it caused the crash if I touched the master.
 
I've just been experimenting more.  On another project I had no crash, even on re-inserting the CL several times, so I tried to find a series of events that might.  Eventually the Master prochannel was visible in the inspector, and the graphics became distorted (EQ all over the place), and the CL only showed the words "Load failure".  Next time i touched the Master in the floating CV Sonar crashed.  It sent a dump toCakewalk.

I have tried and tried to reproduce this. For a day or two I had the problem and since I have not been able to get it to happen once, CL or no CL. I have just meticulously gone through the steps again. I'm puzzled.
 
Loptec, I know it isn't just you because I personally experienced the issue temporarily. My only guess is that it went away after a Windows patch? only thing that would have changed on my system between the time I had the problem and didn't have the problem.
 
Sorry I can't be of more help.

Meant to pop back earlier to say that my problem report status is now "Submitted to Development".

It happens to me even when I am not using CL, also it happens if I click anywhere in the console, so - master bus, channels, metronome etc etc.
 
trying to receate it is nigh on impossible tho, it just seems to randomly happen mid project. As I said before the work arounds I have are to open the project, save it (without making any adjustments within the project) and then restart Sonar.
 
Another one is to change the Console view to my third monitor and have the window floating then restart Sonar.