I used x1 right up until x2 was available, had ZERO issues with it. Now I am experiencing just random crashed and weird behaviors. I love Sonar, mostly cuz I know how to use it, however I am starting to think about changing daws. I get crashed and just random things that happen that side track me for 10 mins here, 20 mins there, have to reboot at least once per session cuz sonar drops out. never had any issues with x1. Is there actually a list somehwere of known issues and fixes? So at least I can see if the things that are happening to me are bugs or if I have other issues happening. After all I have invested in this software, both in time and money, I would really like to get this figured out! Cakewalk are you listening. I have seen many post that are showing the same frustrations as I am having and tried to stay out of them, but my session tonight was just riddled with issues.
 
the wave forms disappeared randomly, the audio still played, took me a few minutes to figure that out.
 
a blank lane exists where a take lane used to be. I deleted the take lane and there is an empty space (not a lane). the lanes did not shrink back together once it was deleted. even after a reboot, its still there taking up screen space.
 
While recording, monitoring was perfectly fine, I hit stop, and the wave file was moved 1 measure past where it should have been. Thought I did something wrong, tried again and same thing. rebooted and then it worked correctly again.
 
when I clone a track with multiple takes, any muted takes are unmuted. took me 30 min to figure this out and remute the takes.
 
sometimes when I add an effect to the fx bin, the audio stops working in sonar, I open media player and it works fine. sometimes I can toggle the audio engine button and it comes back, most times I have to reboot.
 
I had the snap to grid on whole note, inserted midi clips and they were about 1/16 off. why does snap to grid on not actually snap to the whole note as selected?
 
CAkewalk, please let us know you are actually addressing this! I understand it may take some time, would be great to know you are working on it. 

If you've all of a sudden got stability issues with X2 its gonna be your system or a corrupted project. Workflow issues are probably Sonar issues. Existing project or new project? Have you updated all your firmware and drivers everywhere? Have you updated your BIOS and chip set drivers. Have you run windows update? Have you defragged and run scan disk? Have you updated your plugins? Have you installed any new plugins recently? Are you running X2A? Sadly you are going to need to spend some time on this.
I can answer on cakewalks behalf that they are working on X2B.

TraceyStudios


I love Sonar, mostly cuz I know how to use it, however I am starting to think about changing daws. 

When Sonar was X1b (or was it X1c?) and was quite unstable, I went on to purchase another daw. Having two daws is actually nice. When one gets stuck I can keep working using the other. Fortunately, X2a and the other daw both work without major problems.

Having said that, I would do a clean re-install of X2 and X2a before thinking about another daw.

TraceyStudios


I used x1 right up until x2 was available, had ZERO issues with it. Now I am experiencing just random crashed and weird behaviors. I love Sonar, mostly cuz I know how to use it, however I am starting to think about changing daws. I get crashed and just random things that happen that side track me for 10 mins here, 20 mins there, have to reboot at least once per session cuz sonar drops out. never had any issues with x1. Is there actually a list somehwere of known issues and fixes? So at least I can see if the things that are happening to me are bugs or if I have other issues happening. After all I have invested in this software, both in time and money, I would really like to get this figured out! Cakewalk are you listening. I have seen many post that are showing the same frustrations as I am having and tried to stay out of them, but my session tonight was just riddled with issues.
 
the wave forms disappeared randomly, the audio still played, took me a few minutes to figure that out.
 
a blank lane exists where a take lane used to be. I deleted the take lane and there is an empty space (not a lane). the lanes did not shrink back together once it was deleted. even after a reboot, its still there taking up screen space.
 
While recording, monitoring was perfectly fine, I hit stop, and the wave file was moved 1 measure past where it should have been. Thought I did something wrong, tried again and same thing. rebooted and then it worked correctly again.
 
when I clone a track with multiple takes, any muted takes are unmuted. took me 30 min to figure this out and remute the takes.
 
sometimes when I add an effect to the fx bin, the audio stops working in sonar, I open media player and it works fine. sometimes I can toggle the audio engine button and it comes back, most times I have to reboot.
 
I had the snap to grid on whole note, inserted midi clips and they were about 1/16 off. why does snap to grid on not actually snap to the whole note as selected?
 
CAkewalk, please let us know you are actually addressing this! I understand it may take some time, would be great to know you are working on it. 

Hi there!
 
I think I know what causing stability issues that you experience!
Blue death crash,  restart windows?
 
Have you check windows event log file?  "error id 46 volmgr"
 
 
Let's try these steps to change the settings of virtual memory only for 'C' drive and remove the settings to automatically manager paging file size for other drives.

a. Open System by clicking the Start button, clicking Control Panel, clicking System and Maintenance, and then clicking System.
b. In the left pane, click Advanced system settings. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
c. On the Advanced tab, under Performance, click Settings.
d. Click the Advanced tab, and then, under Virtual memory, click Change.
e. Clear the Automatically manage paging file size for all drives check box.
f. Under Drive [volume label], click the drive that contains the paging file you want to change.
g. Select the drive and select no paging file and click set for all the drives except for C drive:
 
Set page file size as same as your installed RAM size, example: If you have 8126mb RAM set MAX pagefile to 8126 and minimum to same value 8126.
Windows will need to rebot your system..
 
http://windows.microsoft.com/en-US/windows7/Change-the-size-of-virtual-memory

I wouldn't do Freddie's tip unless you exactly have what he thinks he's diagnosed. If he's right he's a genuine mind reader (didn't see any mention about BSODs)

CakeAlexS


I wouldn't do Freddie's tip unless you exactly have what he thinks he's diagnosed. If he's right he's a genuine mind reader (didn't see any mention about BSODs)

It doesn't alter the system in any bad way even if you try it!  
You can always go back to "windows default" anytime.
 
 
Often you get this error message if you have 16GB RAM or more installed, but sometimes on 8 or 4GB too.
But yes, of course try to check if you find  "error id 46 volmgr" is a good thing.

I find it completely idiotic that windows allocates the amount of space to the page file = to the amount of ram. For instance 15 GB seems rediculous for a page file. But what do I know. And on top of that if you have hybernation turned on windows sucks another 15 GB. That's 30 GB reserved for windows which will more then likely never be used. 

Again I'm not seeing anything about a paging issue or BSODs on the original post, however I've also just noticed the Windows version hasn't been stated at all either, anyway just for kicks here are MS recommendations for paging size (64 bit Windows):
http://support.microsoft.com/kb/889654/en-us

Alex: Its not that all of sudden I am having issues, been having them from day one with x2. I do realize that I have been getting more "complex" projects, more midi instruments, more automation etc. I'm sure the projects are requiring more resourses. I'm learning more and doin more, Perhaps that is why I didn't notice anything with x1. 

I rarely get a blue screen crash. Don't think have ever got one related to sonar. Sometimes on shut down I get it.

Yes, I have added a few plugins, amplitube, arc2, ampeg svx & ozone 5. that's it.

no i have not updated windows, my computer is a dedicated recording machine. rarely connect to the internet.

I have defraged a couple of time, I have a dedicated drive for the cakewalk projects, another dedicated drive for BFD, and another backup drive. I will try to defrag the project drive.

I have shut off services which are not required, as per the sweetwater windows 7 optimization guide, I was have all the issues prior to this, was hoping this would help.
http://www.sweetwater.com/sweetcare/downloads/Windows_7_Optimization_Guide.pdf

Have you updated your BIOS and chip set drivers. dont' know how to do this, any documentation on this?

these issues happen on both existing and new projects.

I'm sorry if it sound like I was just complaining, i guess I am just frustrated. Good to know they are working on an update. Is there a list of known issues? If so this would help me determine if my issues are sonar related or system related.

I am using windows 7 64 bit, see my signature for additional info about my system.

I have not had any errors indicating paging issues. I will look at the doc you linked.

Thanks Alex.

So I don't think it's a paging issue Tracey although I see no harm in optimizing your performance (but I would do this last). 8Gb of memory should be fine although there's never any harm in purchasing extra memory (I'd hold off though). I'm pretty certain memory isn't your problem.

I totally understand the "if it ain't broke don't fix it" mentality, however it is broken, I strongly suggest you connect to the internet and run Windows update two or three times. I also strongly suggest you go on the internet as well and update all your firmware and drivers/ BIOS and chip set drivers/plugs to the latest versions, it may have worked well with X1 before but doesn't rule out any of what I'm pointing out. Also rescan your plugins.

I'm running X2B with total reliability and I see no reason why you shouldn't. I'm specifically talking about the crashes here.

Cheers... I hope you get this resolved.
PS At no stage did I think you were moaning, it was a good post, you just need to rule everything else out first.