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 filled out a problem report today.

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. 


 

I just got this back related to my crash...

<Email from Cakewalk>
The problem you are experiencing is most likely a system specific problem or a configuration issue that we believe can be resolved with assistance from Cakewalk Technical Support. Unfortunately, as explained in the Problem Report Form, this form does not put you in direct contact with our support staff.

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

As I mentioned before, I spread X2 over two monitors, so use them as one big monitor, and have not had any problems.
 
To help the OP out, I tried to follow his workflow, and discovered that my Sonar crashed every time.
 
I'm busy working away in another studio for the next fortnight, away from home, but will pop back when I return.
 
Again, Maybe this is why one person finds a program buggy, and another finds bug free.
 
For the way I normally work,  Sonar X2a is as solid as a rock.

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

On the phone with tech support I couldn't get it to happen either. 

But that is always the case. LOL

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

First, without a lot of playing around with this I was unable to produce the problem, but I think I might have a recipe figured out.  We are all looking at the console being detatched and on separate monitors as the culprit, but I think this might actually be a problem with the Inspector view and the Pro Channel.

With the console view not displayed, expand the Inspector view and select the Pro Channel to be in the active field.  Then open the console view and float it.  With the PC showing in the Inspector try to adjust the bus volume.  I think this will dependably crash Sonar.

A suggested work-around would be to display the PC in the console view instead of the Inspector.

Bug report created.

Glen