First of all: This only happens when I have the Console View placed on my my second monitor (within the multidock)

It's not happening with all projects, but with most. When I open a project and then go into the CV and try to adjust anything on the Master Bus, Sonar instantly crashes. Most often this applies to any bus, but it ALWAYS applies to the master bus.

If I first make the Master Fader visable in the inspector (while also having the CV in view) and then adjust the volume of the fader in the Inspector, I can then safely jump into the CV and change the volume of the master in there.

It's like Sonar can't predict that I'd ever want to do something like this and get a chock because of it..

I never had this problem with any version of X1.
You don't really need to tell me to send in problem reports and stuff. Of course I've already done this. (I've lost count how many I've sent in about it, actually)

I just wanted to check if there are more people out there with this problem or if it's just me. ... Cuz if it's just me, I guess it'll never be fixed... :/

Here's a video example of what I'm talking about. It showes the same behaviour in two different projects and I also show how it doesn't crash if you first adjust the volume in the inspector first. Since I had to record both monitors it's quite small and the quality isn't the best. But it's enough to see the problem. Just go 720p and full screen to get the most out of it. - http://www.youtube.com/watch?v=nnjZofofhS8


Thanks

Same here!  I've given up trying to figure it out and have resolved to work around it by only adjusting anything in the Master Bus in the Inspector View.  I haven't had too much problem with any other busses in CV, just the Master.  I'm glad to hear that I'm not the only one!  Seems like others have had similar posts previously and most have suggested just to work around it.  If there's a fix I'd like to know about though!!  Thanks for sharing!

  That has happened to me as well I am glad you are able to articulate the problem.  

We all need to send a problem report. 

I replicated on my PC and submitted a problem report.

Replicated here, too, instantly.
 
I have two monitors, but just have Sonar spread accross both, so have not tried this before.
 
I've not seen this posted before.  Why not?  As far as I can tell a lot of Sonar users use two monitors this way.
 
Thanks for posting, Loptec.

Well this is very interesting - I stopped using X2 and went back to X1 because of what I thought were random graphical bugs - when the X2A patch came out, I installed this but it didn't seem to make much difference, so I reverted to X1 and decided to wait for X2b ... and I waited .....and waited.....

I also use two monitors but have Sonar spread across them.
The Master Bus issue (and some other Cv flaky behaviour) were some of the main reasons why I went back to X1.
To be honest I did wonder if I had some kind of graphical interface clash on my system - I think now this is not the case (problem my system) and  that this is a Bug and quite a Big Bug in the X2 programme.

If anyone from Cakewalk is reading this, on another thread someone said Cakewalk needs to give us an update on the current progress with X2B - I  think they are correct - this is a pretty serious flaw and has stopped me using X2.

Come on guys, what's going on!!
Thanks

Nigel

I have the whole of Sonar spread over both monitors, so I can see the Track View over both monitors, or the Console View over both.  I have not had any problems.
 
After reading the OP, I followed his workflow, and it crashed immediately.  I guess this goes to show why some users have terrible troubles, and others don't.

This happens to me but if I pull CV from my second monitor back to Monitor 1 then save, then exit then go back into the project it resolves itself.

Also, if you open the project, hit save, exit Sonar and restart this sometimes resolves it too.

I have been bashing out error report after error report on this one, it can be very frustrating.

Get this all the time on X2a. I'm also using dual monitors with the console in the multidock on the second monitor.

Happens to me all the time. It seems to be worse with Slate VCC inserted. Dual monitors, Console on second monitor. I have reported this many times, though not as detailed, "glad" to see someone else has noticed it at long last.