Using The Extended Desktop- Floating vs Multidock

Hi All!
 
I read a post a few days back that was discussing the use of multiple monitors.  I have had problems since X1 with crashes occurring while using the Console View floated to a secondary monitor (by itself).  There seem to have been a lot of similar reports in previous threads.  I have always floated the CV and never thought to move the entire Multidock to the second monitor.  Can anyone offer observations as to whether using the CV (inside the Multidock) floated to a second monitor has reduced any of the crashing that usually occurs when making adjustments to the CV itself floated to the second monitor?  It seems like a relatively minor distinction but I love having the CV on the second screen and hate all of the crashes that I encounter when using the CV floated by itself.  Anyone know if leaving it in a floated Multidock reduces the incidents of crashes when making adjustments to the CV?  Hope that I'm asking this question clearly.....  any observations or insight would be appreciated!
 
Dave

Thanks for this reply LunaTech!  Yes.  When I float the whole multidock over I do see the Multidock & Project name at the top bar.  When using the CV tab in this manner I refer to that as using the CV "inside" the Multidock.  My approach until now has been to leave the multidock where it defaults (underneath the track view on the primary display) and to float the CV (by itself) to the second monitor.  I do this by right clicking the Console tab while still in the multidock and choosing to undock just that tab.  I then float that over to the second monitor.  This leaves the rest of my "views" and plugs to remain in the multidock on the primary screen. Using this approach I get a crash almost everytime I use a control on a bus.  I leave the browser in its default location to the right of the track pane on the primary screen so no trouble here with changing screensets as you had mentioned.  I was hoping that the crashes might be reduced (or better yet eliminated) by floating over the whole multidock?  Might just be wishful thinking!  I have set up a CV screen set for the primary monitor and that seems to be OK as a workaround but I still would prefer to eliminate that toggling and leave it on the second screen where I can easily observe what's going on in the mix with the track view open (and large!) on the primary screen.

Hey Bob.....thanks for your input.  Just curious......do you drag just the CV or do you move the whole multidock over?

I did float the multidock over to second monitor and never got a problem.

Today however, I just use d to toggle multidock open or closed. And now my TV is stretched across both monitors.

This is a new workflow for me and I'm loving it. Never thought I'd want to go back to a single monitor, but a nice 27" just may get the gig.

cuitlahac
Thanks for this reply LunaTech!  Yes.  When I float the whole multidock over I do see the Multidock & Project name at the top bar.  When using the CV tab in this manner I refer to that as using the CV "inside" the Multidock.  My approach until now has been to leave the multidock where it defaults (underneath the track view on the primary display) and to float the CV (by itself) to the second monitor.  I do this by right clicking the Console tab while still in the multidock and choosing to undock just that tab.  I then float that over to the second monitor.  This leaves the rest of my "views" and plugs to remain in the multidock on the primary screen. Using this approach I get a crash almost everytime I use a control on a bus.  I leave the browser in its default location to the right of the track pane on the primary screen so no trouble here with changing screensets as you had mentioned.  I was hoping that the crashes might be reduced (or better yet eliminated) by floating over the whole multidock?  Might just be wishful thinking!  I have set up a CV screen set for the primary monitor and that seems to be OK as a workaround but I still would prefer to eliminate that toggling and leave it on the second screen where I can easily observe what's going on in the mix with the track view open (and large!) on the primary screen.

Hi Dave,
I know what you mean.  As a test I tried to use CV the way that you do and got my crash. Question, Do you have the Concrete Limiter on any of the Busses?.  This seems to be the last of the big issues I am having.  Not including the nagging issue of my M-Audio Keystation 88 Pro mysteriously stops responding in the DAW if left inactive after a period of time and this is intermittent.  With that said I hope that the fix comes soon. Having to not do the toggling as you stated would be a huge time saver in my workflow.
 
Let's hope that the impressive pace at which fixes have been coming continues... X3 is really good and is moving toward "Awesome" for me.  While I am sure that completely bug free is a bit naïve, I feel that the bakers in particularly with X3 are doing making a commendable effort.
 
Bob,
 
Actually duplicated this and got the Bakers to replicate the issue themselves. With that said, I use "other" tools and Sonar is far from being the only tool with some challenges.  I just think that it is becoming a more capable DAW in it's functionality and that's what I like about it. Some will say that simplicity is better and other's will be giddy over the Swiss Army Knife approach, I just want to continue to enjoy creating, making and engaging the music.  Sonar allows me to do that in a way that works for me.
 
 

robert_e_bone
@Lunatech - is it possible you have not disabled Windows default behavior for selectively turning off idle USB devices?
 
You can check this in either the USB Hub Properties in Device Manager - you would need to set it for each USB hub, under Power Management in properties, OR you can check/set this under power options:
 
Control Panel>Hardware and Sound>Power Options> then choose the High Performance plan, then Change Plan Settings, then Change Advanced Power Settings, then expand USB Settings, then expand USB Selective Suspend and change to Disabled.
 
I am wondering if Windows is just severing the connection due to detected idleness.
 
Bob Bone
 

Hi Bob,
Yes, I have checked all of the settings.  Stopped using a powered hub, etc.. etc.. .. The only thing that has seemed to work consistently is when I had only one controller and it was connected with a midi cable. It does not happen very often, I just don't know when. I have seen some others have similar issues here and on other forums. I have tried updating the drivers, using the Windows driver took all the suggestions that I have seen. What's interesting is that windows device manager still thinks that it is functioning... go figure.  This is not at all a deal stopper for me.  If I am working continuously, it does not happen.  Thanks for the suggestion though....

cuitlahac
Thanks for the feedback LunaTech!  I probably do have the Concrete Limiter on some of the busses as it is my go-to limiter.  I'm sure that it varies from project to project and bus to bus.  Are you suggesting that there might be a connection to the CL being there in the circumstances where I'm getting the crashes?  I'll have to be observant about that!.....
 
Couldn't agree with you more regarding the bakers.....X3c is a great product and I get a great deal of musical satisfaction using it.  I am also fortunate to have a high degree of patience when it comes to these little things that are "inconvenient".  They'll get it fixed in due time and I'll be thrilled about it!  In the meantime we work around this stuff and make our music.....it's all good!

Hi Dave,
That is exactly what I am suggesting.  I corrected my earliest post where as I wrote CC when I meant to write CL (Concrete Limiter).  If CL is on a bus while the CV is undocked and on the 2nd monitor, working in the CV will lead to a crash.  So if I go from track to track and then back to the bus that contains CL, Sonar will white screen fairly consistently.  If you can make a correlation, I hope it helps you to know that the bakers are well aware of the issue.  Keep creating!!!