Beepster
These things happen. They used to happen far more in X1... at least for me. Now I just get weird graphics and editing glitches. Usually when I get whitescreens in X2 I just wait for a few seconds and things go back to normal.

 
Beep, that's interesting. I have never ever had a whitescreen resolve itself. And without fail, it also always takes out the 'link' to my audio drivers when it happens. When I re-open the project, I always get the message about there being 'no audio devices', and I've never been able to reassign the drivers, either in the Driver Settings menu (they don't appear in the dropdown list for either Playback or Recording), or even by unplugging/reattaching my soundcard. Before now, I've even tried switching from ASIO to WDM and running the Wave Profiler to no avail.
 
The only way I can get SONAR running with audio again is to reboot my computer.
 
I'm guessing it must be SONAR-related, because even when this happens, all my other audio programs run perfectly.
 
I'd love to know what to do to prevent the hassle of rebooting.
 
 
 

wizard71
How dare you even attempt to do anything whilst the project is playing. Apart from moving faders. That works well.

Now *that's* sarcasm
 

Hiya, Straummy. Yeah that's sounds pretty annoying. I don't what to tell you aside from that it sounds like Sonar isn't playing nice with your interface (by no means an expert opinion). X1 was pretty much unusable for me until I did some optimization and swapped out my Layla for my Focusrite Scarlett. I was getting constant audio engine stops, dropouts, crackles, whitescreens, crashes, etc if I did anything more than just hit play... and even then it was dicey. My system is a powerhouse and I designed it based on an ADK build so I was pretty surprised. Turned out that the legacy PCI slot was bridged not native so it was choking. The optimization made the Layla usable but I had already bought the Scarlett and I like it better anyway.
 
The whitescreens I get in X2 are usually when I start up Sonar but they are very brief. I think it might have something to do with how it's retrieving stuff from the HDDs but who knows. Other times it'll whitescreen for a bit when I insert a synth or start a big task like an import, export or bounce but again it's pretty minor and never fully crashes. The few crashes I've gotten in X2 have mostly been related to browser synth patches but it doesn't cause a whitescreen. It's usually silence and/or a really terrible noise then it crashes. I don't have to reboot or even wait that long for Sonar to close. I just open it back up again and I'm good to go. Then there is when the project starts acting weird with graphical glitches or unresponsive parameters or various other bizarre stuff. Once that starts happening consistently I can be pretty sure Sonar is about to crap the bed. Sometimes the project is still usable... other times it's not. That last type of crash and the preceding behavior are the ones that really bother me. Those types of glitches however happen all the time to lesser extent without crashing and are the main reason I've been begging for X2b. They are far too common and it makes working extremely difficult even for basic stuff.
 
Sadly... I'm starting to lose hope for a B patch.
 
For your problems though, and I'm sure you've already done this but if not, I'd say give Cake a call and ask them to help you troubleshoot and optimize your system. If you are using a legacy PCI card or a firewire unit there could be a problem with the slots or chipset or Sonar just plain doesn't like it so ask them about it or ask the interface manufacturer about Sonar. Sometimes too the latest drivers aren't always the best drivers. Google around and see if there are any complaints about your current driver. It's all a crapshoot though considering all the variables involved. I just had a case of beginner's luck with my system I guess. Hope you get it sorted. Cheers.

SteveStrummerUK

wizard71
How dare you even attempt to do anything whilst the project is playing. Apart from moving faders. That works well.

Now *that's* sarcasm

Yep! But how about saving a project?!? Sonar crashed my project last night while pressing CTRL+S! Now THAT'S plain ridiculous!

I have white screen recoveries also. And when sonar does crash, it never " breaks my link" to my audio card. And I have an old mAudio 24/96.

But when I do get an "Sonar. Has stopped working" error, I always restart just to have a clean slate again. And this doesn't happen often.

Beepster
Sadly... I'm starting to lose hope for a B patch.

I have not lost hope. Yes, it is taking quite some time since X2a, but think about how many errors they must consider fixing, and how long it must take to troubleshoot countless lines of code, modules, dll's, exe's, etc. I don't work for Cakewalk, but I can understand that it may take time if they want it right. (And I am hoping they share the same belief as me!)
 
X2b hopefully will come soon, but who knows if it will cure all of our problems; there are so many out there, all with different aspects.

Well unless it comes out this month or they're putting X3 on a 2 year cycle I don't know, man. September is coming pretty fast.

Beepster
Well unless it comes out this month or they're putting X3 on a 2 year cycle I don't know, man. September is coming pretty fast.

 
I hear ya. Well, I've certainly tried to keep them busy with all of my submitted Feature Requests and Error Reports! [fingers crossed...]

2:43AM

SteveStrummerUK

wizard71
How dare you even attempt to do anything whilst the project is playing. Apart from moving faders. That works well.

Now *that's* sarcasm

Yep! But how about saving a project?!? Sonar crashed my project last night while pressing CTRL+S! Now THAT'S plain ridiculous!

How do you know Sonar crashed your project? It could have been a Windows problem. Good thing you had autosave on so you didn't lose much, if anything. 

I think I've seen others complain about Ctrl + S causing problems. IIRC a few people mentioned they just started using the global File menu to save. That's what I've always done and I've never had a problem. Is it right? Certainly not but it's better than crashing... especially when you are at a point in your project where you would manually save.
 
And I've never used auto save. I save constantly and create new versions every time I finish a task. My project folders get huge but if something goes wrong I lose very little work. Maybe an hour or so tops. I just get the feeling autosave is the type of thing that ends up saving the corrupted parts as well and I don't get a lot of crashes anyway. Just projects that slowly become unusable. If I see that starting to happening I just go back to an earlier version and delete the one that was going wonky.