Hi Folks,
 
This is most likely two different issues (setting loop points and switching screensets). We would like to investigate these issues to discover what specific workflows may be causing this. If anyone has projects where this can occur and are willing to share them and offer description to reproduce, please PM me. 
 
Thanks!

Hi Dan, 
 
This isn't specific to any one project with me, it's just a general thing that happens in all projects. And it doesn't happen all the time, like I said maybe one in five times that I set a loop during playback. 

Sharke,
 
One in five times is pretty repeatable. I'm looking for clues to what workflow scenarios might be causing this. If you have a project you know this has happened in and would like to help us resolve this issue, you can send me the project with some hints on what you did or how you typically use loop points. Most likely we wouldn't require the audio, just the raw .cwp file would do. 

Sharke, can you get it to crash after freezing a majority of your tracks? I'm wondering if this could be an issue when trying to wake up some specific plug-ins too quickly at a specific loop start point. I've seen issue when using lots of tracks (25+), each with 3-4 3rd-party plug-ins live. Sometimes on a loop, an individual track may be muted slightly longer than another until the plug-ins can be "live". If a plug-in is questionable, I could see it potentially crashing the DAW.

Hi Dan,

I can send you another project. I just started a new one, all seemed great and boom all of a sudden I can't change back to screenset 1 again without it taking 10-15 seconds or more, just like in the last one I sent you. No audio dropouts its just the switching taking painfully long. Changing to any other screenset is like lightning. This is project number 3 with this same problem.

I'm stumped. I know in your last correspondence with me me you thought my system was struggling, but, it's only been like this in X2 and really, an i5 running at 3.5 ghz, 8gigs RAM, and 2 gig GT640 graphics card. Surely it man enough for X2????

Just realised it was Dan Gonzalez I was corresponding with, but, I am happy to send to you Dan.

STinGA
Hi Dan,

I can send you another project. I just started a new one, all seemed great and boom all of a sudden I can't change back to screenset 1 again without it taking 10-15 seconds or more, just like in the last one I sent you. No audio dropouts its just the switching taking painfully long. Changing to any other screenset is like lightning. This is project number 3 with this same problem.

I'm stumped. I know in your last correspondence with me me you thought my system was struggling, but, it's only been like this in X2 and really, an i5 running at 3.5 ghz, 8gigs RAM, and 2 gig GT640 graphics card. Surely it man enough for X2????

Have you tried duplicating a know good screenset to screenset 1?
 
I've had SS's go bad on me and this usually clears it up

I haven't, but this is the 3rd consecutive new project this has happened with.... I will try though thanks for the tip it definitely worth trying,

It might be something silly like Screenset 1 in your default template is corrupt - and it's loading up every time you start a new project.

sharke
Anyone else? I select a chunk of the timeline or select clips and then shift-L to set the loop during playback - around 20% of the time, Sonar freezes and makes a stuttering machine gun noise and I have to kill the task

This isn't a new problem.  It was happening for me in Sonar versions 6 and 7 too.