I'm getting an 'out of memory' error on Producer X2 with the '2a' update installed.  Before the update I never saw this error message.  Since the update I'm seeing it pretty much every time I work on a project.  It seems to happen when I'm previewing audio samples, adding audio samples, and occasionally adding effects.  Sometimes the software will start working normally again after a few seconds.  Other times I get the error every time I try to do anything, and have to close the software down and open again - then it will work fine for a while.   I have recently changed to windows 8 pro from windows 7 home premium, but the software worked fine in windows 8 before the update.  

I'm running X2 in a 32 bit system (Dell XPS 430 intel quad core (2.83 ghz), 4Gb RAM (3Gb useable), Edirol FA-66 through firewire, the 'cakewalk content' files are all on a seperate HDD from the program files (I read somewhere the X2 needs plenty of spare drive space).  I'm also using a memory stick for cache but that hasn't helped.  I obviously can't upgrade the RAM any further.
I know shutting programs down will free up RAM, but generally I don't shut any programs down when using X2 and I've never got the out of memory error - and as I said before the system was fine before the update and not afterwards.

Anything I can look at?  Any known problems with the '2a' update that might cause this?  Is it possible to remove the update without having to re-install X2?

The X2a update is NOT supported for XP.

The last update that will ever be supported for XP is X2 - but NOT X2a.

This is due to reliance on Microsoft distributed libraries that are not released for XP, and never will be.

Soooo, you have to go back to X2 and that's the end of the line for XP.

On the bright side - a nice shiny new computer is out there waiting for you, which will include running in 64-bit format with either Windows 7 or Windows 8.

Good luck, I am sorry to bring you the bad news on this, but hopefully whenever you pick up a new computer you will be happy.

Bob Bone

Forgot - this is from the Cakewalk site, on support for XP for the X2a update:
Please note: SONAR X2a is only officially supported on Windows 7 and Windows 8. Installation is not possible on unsupported operating systems, such as Windows 98 & XP. It remains possible to install and use SONAR X2a on Windows Vista though it is not recommended.  


Bob Bone

robert_e_bone


The X2a update is NOT supported for XP.

The last update that will ever be supported for XP is X2 - but NOT X2a.

This is due to reliance on Microsoft distributed libraries that are not released for XP, and never will be.

Soooo, you have to go back to X2 and that's the end of the line for XP.

On the bright side - a nice shiny new computer is out there waiting for you, which will include running in 64-bit format with either Windows 7 or Windows 8.

Good luck, I am sorry to bring you the bad news on this, but hopefully whenever you pick up a new computer you will be happy.

Bob Bone

Did you read the post you are responding to?

Grum.

Thanks for the reponse, but I'm using windows 8.  

jag, that's a tough one. The only time I've ever gotten that "out of memory" message is when I've tried to bring in M4p's from like iTunes or whatever the heck that file extension is called. They are encoded a bit differently or something and Sonar won't read them unless I use this other software I have to turn them into regular mp3's. But that's the only time I've ever experienced the out of memory message.

You should be able to just install X2 (the program only) over top of the X2a update. It's worth a try though I can't promise you it will be a fix. Just go to your X2 install and select "custom" install. This way all you'll install is Sonar without all the plugs and synths etc. From there, make sure you at least get the hotfix patch for the original release of X2. The hotfix really controls crashes and inconsistencies. If the hotfix gives you issues and you had no problems with just stock X2, go to C:\Program Files (x86)\Cakewalk\SONAR X2 Producer (if you installed 32 bit Sonar) or C:\Program Files\Cakewalk\SONAR X2 Producer (if you installed 64 bit Sonar) and you'll see a folder there named "Backup".

In this folder is the original Sonar exe. Copy it and paste it into the directory where the backup folder is in, which is one of the directories I mentioned above. You'll see another SONARPDR.exe and it will ask you if you want to replace it. Say yes.

Keep in mind, the above will only work if you install Sonar X2 from the original release, then apply the hotfix. The hotfix is what creates that "backup" folder and puts the original Sonar exe in there. So when you go to that folder and copy and paste the exe back into the correct directory, you are removing the hotfix and going back to the original release of Sonar X2. Hopefully though, just re-installing Sonar by itself and then putting on the hotfix eliminates your issues. That hotfix really helped me out with Pro Channel crashes, so it's worth a try to put it on after you install Sonar. But if it fails, you can revert back easy enough.

Worst case scenario, totally uninstall Sonar and reinstall. Though it sucks, it may be the only way to go unfortunately. Good luck.

-Danny

Hello Danny.  Thanks for the information.  I have been using some audio files that are not wav or mp3, so I'll try doing something with some more conventional audio files first and see what happens.

The odd thing is, if I look at the total RAM used when sonar says 'out of memory' it's only at about 66% - meaning there should be about 1 Gb of RAM unused.  

I have a feeling I'm going to need to try the Sonar installation tips you gave because of the fact that this only started happening after the update.

I don't recall whether I applied the hotfix.  I'll have to take a look and see if the backup folder is present.

Thanks again for the advice.  I'll update this forum with the outcome.

grumbleweed4162

robert_e_bone


The X2a update is NOT supported for XP.

The last update that will ever be supported for XP is X2 - but NOT X2a.

This is due to reliance on Microsoft distributed libraries that are not released for XP, and never will be.

Soooo, you have to go back to X2 and that's the end of the line for XP.

On the bright side - a nice shiny new computer is out there waiting for you, which will include running in 64-bit format with either Windows 7 or Windows 8.

Good luck, I am sorry to bring you the bad news on this, but hopefully whenever you pick up a new computer you will be happy.

Bob Bone

Did you read the post you are responding to?

Grum.

Wow - I did read the post - just processed it incorrectly - I saw the line about X2 and then 32-bit and my brain saw that as XP 32-bit.


I am sooooo sorry about that.  I don't miss the mark too often, but certainly did here, and will try to avoid that again as best as possible.


Bob Bone

jaggedredux


Hello Danny.  Thanks for the information.  I have been using some audio files that are not wav or mp3, so I'll try doing something with some more conventional audio files first and see what happens.

The odd thing is, if I look at the total RAM used when sonar says 'out of memory' it's only at about 66% - meaning there should be about 1 Gb of RAM unused.  

I have a feeling I'm going to need to try the Sonar installation tips you gave because of the fact that this only started happening after the update.

I don't recall whether I applied the hotfix.  I'll have to take a look and see if the backup folder is present.

Thanks again for the advice.  I'll update this forum with the outcome.

Hi jag,
 
I'd be willing to bet that's what your problem is....the weird files you're using. You may need to convert them to waves or AIFF's or something. That's correct...when this out of mem message comes up, you're never physically out of memory. I don't think you need to reinstall Sonar...honest. Try working with a few wave files and see if you get it. I'd be willing to bet you won't get the warning anymore. Certain files....Sonar (as well as other DAW's) just don't work well even if the file format is something that is accepted by a DAW.
 
For example, when I mentioned those M4p files that come from iTunes, no DAW I own can open them. I get out of memory messages from them too. Wave Lab fails, Reaper fails, Studio One fails, Adobe Audition fails and even Audacity fails. Audacity is the garbage disposal of DAW's...it opens everything. LOL! But not these...same message there. I have to use a product from Daniusoft...which is an audio converter.
 
Once I run the files that give me that message through that and convert, they open right up in Sonar and never give me an ounce of trouble ever. So before you go messing with Sonar and do a reinstall or whatever, try working with some standard files if you can like wav, aiff, 320 mp3, flac, rex, wma etc which are all supported by Sonar and have never given me any trouble. But if you really feel the need to reinstall, definitely try what I mentioned in my other post as that is what I myself would do if I were in your situation. Best of luck...and yeah, please post back and let me know how you made out with it all. :)
 
-Danny 

Hi Danny. You were right. I used nothing but wave files in a project and no memory error. Your reply has saved me a lot of heartache I'm sure! I'll convert any files I use to wav from now on. Thanks for your help, Paul. Hi Bob. No problem. Thanks for reading the posting. These forums are the most helpful, and friendly, that I've ever experienced.