Community Forums Archive

Go Back

Subject:Out of Memory Errors when Normalizing
Posted by: ErnieSprance
Date:8/9/2013 12:04:33 PM

Just installed SF Pro 11 in conjunction with a brand-new install of Win7 SP1. When I try to normalize a file longer than 3.5 minutes, I get an "out of memory" error message with the advice to shut down other applications. SF is the ONLY app running. Sony support suggested an uninstall, settting up a new admin user, and reinstall. I didn't think that would do anything but I followed their instructions to the letter. No change. Still waiting to hear back from tech, but I'm not holding my breath. Any suggestions? BTW ... running 32-bit with 4GIG RAM.

Subject:RE: Out of Memory Errors when Normalizing
Reply by: rraud
Date:8/9/2013 1:10:33 PM

Increasing the size of virtual memory helped on my Vista machine which exhibited the same message.
Don't know about Win 7 but typically the (manual) setting recommendation was double + half of your ram whatever, put 4GB+4GB+2GB = 10GB (10240 MB)
Its vitual, and only be used if there are some heavy.

Subject:RE: Out of Memory Errors when Normalizing
Reply by: J.
Date:8/9/2013 1:46:14 PM

Even at very high sample rate and bit-depth, a 3.5 minute file will only be a couple hundred MB. Viewing Task Manager while running Forge will probably confirm that there's no shortage of RAM.

More likely it is a generic message but the cause is a disk memory issue. Check the accessibility/content/space of your temp folder. What does the Free Storage field on the lower right of the status bar report?

If that all seems fine, try setting Options->Preferences->Editing->Global media cache to zero, but, again, Task Manager likely already confirms this isn't the issue.


Message last edited on8/9/2013 2:05:19 PM byJ..
Subject:RE: Out of Memory Errors when Normalizing
Reply by: happyguy
Date:8/13/2013 12:22:35 AM

I am having the same exact problem, I upgraded from version 10 and never had this problem until upgrading to version 11. The drive with the temp file has 568 GB free so space isn't a problem. Going into task manager shows almost 1.4 gigs of memory free so it doesn't look like a memory issue. I'm running windows7 32bit with 4 gigs of memory.

Subject:RE: Out of Memory Errors when Normalizing
Reply by: Sinkronizer
Date:8/14/2013 5:53:25 AM

Seems I'm having the same memory error problem, unable to process anything after recording in 32bit 96Hz, 24bit 48Hz was workable, however I've never had a problem with recordings in the higher quality in SF10 Pro.

Subject:RE: Out of Memory Errors when Normalizing
Reply by: Bone Studio
Date:8/16/2013 1:53:01 AM

I was getting the same error when ripping CD's did the below suggestion (thanks "J") and havent had the problem since

" try setting Options->Preferences->Editing->Global media cache to zero, but, again, Task Manager likely already confirms this isn't the issue "

Subject:RE: Out of Memory Errors when Normalizing
Reply by: ErnieSprance
Date:8/20/2013 9:30:12 AM

Your first suggestion about the temp folder produced no change. BUT, your suggestion about zeroing out the cache did the trick!

Message last edited on8/20/2013 10:10:29 AM byErnieSprance.
Subject:RE: Out of Memory Errors when Normalizing
Reply by: ErnieSprance
Date:8/20/2013 9:33:14 AM

Check that. It worked ONCE. Now, it's back to the same old error message about memory. Will keep you posted.

Subject:RE: Out of Memory Errors when Normalizing
Reply by: ErnieSprance
Date:8/20/2013 9:34:43 AM

Closed out SF, reopened, and tried again. WORKED! Seems the fail-to-release-memory-hog is SF itself! More experimentation to come.

Subject:RE: Out of Memory Errors when Normalizing
Reply by: ErnieSprance
Date:8/20/2013 10:09:58 AM

NO LUCK. Back to receiving the out-of-memory messages, not matter what I try.

Subject:RE: Out of Memory Errors when Normalizing
Reply by: Cielspacing
Date:8/21/2013 4:17:27 AM

Well, I guess if it is replicable, then there is a bug somewhere.
If that is the case, then SCS should take care of it... which -following this forum- you may see SCS actually does, though it might take some time.

If you are in need of this function, you may try to normalize via a plugin, and if SF shows you Our of Memory Error signs again, you might try to solve it utilizing jBridge (unexpensive) software.
Their own manifesto states that "it aims to make it possible to run 32bit plugins in 64bit hosts, 64bit plugins in 32bit hosts, or" here is the part that might help you with this issue: "even bridging 32bit plugins to 32bit hosts, allowing to overcome the memory limitations of a single 32bit process".. Precisely what your system is signaling you into.

//On 2nd thought... you did a clean WIn7 SP1 install... Have you updated everything up to date? Including frameworks, directx and everything really? It does involve various restarts. Check this.

Message last edited on8/21/2013 11:38:43 AM byCielspacing.
Subject:RE: Out of Memory Errors when Normalizing
Reply by: Cielspacing
Date:8/21/2013 12:54:28 PM

You might try an additional step.

When working with 32 bit versions of Windows, the OS is commonly configured for software to use only up to 2 GB, despite your software or app that is able to use up to 3 GB (large address aware), because the instruction has to be configured as such at the OS boot process.
Something that might not be, depending on your Windows version.


Hence you might try to apply the following to enable /3G if working on (VIsta or W7) 32 bit Operation Systems (XP is a bit more complex):

• In W7 type cmd in the search box from the Start button and right click on cmd.exe to run it as an administrator
• In Vista look for Command Prompt in the Accessories program group of the Start menu. Right click it to run as Administrator.
//Continue with the next same steps for W7 & Vista
• At the command prompt, enter "bcdedit /set IncreaseUserVa 3072"
(without the "s)
• Press Enter
• Type exit
• Press Enter
• Restart the computer.

Hope it helps

Message last edited on8/21/2013 1:07:20 PM byCielspacing.
Subject:RE: Out of Memory Errors when Normalizing
Reply by: Bone Studio
Date:9/4/2013 12:21:11 AM

I've been still getting 'out of memory' cut off's during the 'extract audio cd' I've tried the 'Global Media Cache' to zero and it worked once after that then tryed 'Cielspacing's' suggestion and no change...any other suggestions...
I Should add that when trying this with no other programs open there is still 92% off my proceccer unused and 60% of Ram unused...
Seems like a Bug to me (played with all the settings i can find ) WMP has no trouble extracting audio from a CD (neither did SF V10)

Message last edited on9/4/2013 4:19:23 AM byBone Studio.
Subject:RE: Out of Memory Errors when Normalizing
Reply by: happyguy
Date:9/8/2013 2:07:04 PM

First I would like to say thanks for all the suggestions, unfortunately none of them worked in my case. I am having the same problem as Bone Studio, changed global media cask to zero worked one time then never worked again. I have been using Sound Forge since version 6 and upgraded to the new versions when they came out and even thought I use Sound Forge 3-4 times a week I never had any problems at all until version 11. The more I try to use version 11 the more Out of Memory error messages I am getting. I have recently gone back to using version 10, can't get any project completed with version 11. BTW I installed version 11 on another windows 7 32bit computer here and get the same error messages then tried it on my 3rd computer running windows 7 64bit and it works without errors. Unfortunately the system with all the sound equipment is setup on a computer with a 32bit OS so it looks like I will be using version 10.

Subject:RE: Out of Memory Errors when Normalizing
Reply by: Bone Studio
Date:9/8/2013 11:06:27 PM

Looks like i'll be doing the same (re-installing Version 10).I'll check back here to see if any updated of fixes are released ,in the meantime the new features aren't worth loosing the others for.I only have a 32 bit computer.

Subject:RE: Out of Memory Errors when Normalizing
Reply by: Cielspacing
Date:9/10/2013 2:25:34 AM

The main difference between 32 Operating Systems and 64 OSes (other than the less allowed RAM capacity) is that the former OS processes data in chunks of 32 bits long size, whereas the latter does fairly the same processing, but in bigger 64 bits sized packs which is more efficient.
Therefore, in order to complete the same task, a 32bit OS needs to double the processing power to do it in the same lapse, or take complete it.

This commonly means that computers runing 32 bit OSes for complex Audio work, require to be optimized, specialy so if the software to be utilized was recently developed, and thus, takes advantage of improved instructions and protocols that are integral part of the newer OS.

>That was behind my question in a previous post about having everything updated.

I would recommend checking the following 3 possible Windows updates:

1- DirectX End-User Runtime, which provides updates to DirectX 9.0c and previous versions.

Since SF11 was released this 2013, it is probably built with DirectX 11 on mind, so
you may want to run the DirectX diagnostic tool built in your Windows to find out which DirectX your OS has.
In order to do this:
*Type dxdiag in the search box found at the startup button.
*Click over the dxdiag.exe found, and locate which DirectX version your Windows OS has.
*Additionally click Next to cycle the tool in order to show you if there are any problems in the Audio and Video sections.

2- Visual C++ Redistributable Packages main job is to install runtime components required to run C++ applications. There is already a FAQ in this SCS site that explains some needs for this package update.

3- NET Framework 4 web installer package, that downloads and installs .NET Framework components.
In some cases installing version 4 does not override the need to install previous versions updates (up to 3.5), so you would need to track those, download and install them separately.

Note that some of the links above take you to the donwloader, so in these cases you will need to download that one first and upon activating it, the real second and bigger download will start. Going thru these two stages will complete each update.

//I will appreciate if someone who perceives improvements with any of the optimizations described in this thread, reports it here.

Message last edited on9/10/2013 2:44:17 AM byCielspacing.
Subject:RE: Out of Memory Errors when Normalizing
Reply by: Bone Studio
Date:9/10/2013 4:29:30 PM

Thanks Cielspacing,I'll give your suggestions a go and report back ...

Subject:RE: Out of Memory Errors when Normalizing
Reply by: Bone Studio
Date:9/10/2013 10:15:34 PM

As well as the previous tips I've now tried your new suggestions Cielspacing and listed below my spec's
The program still gives a out of memory error message when I (1) try to rip a cd to the hard drive (it will work on some tracks then skip others) (2) when i normalise a file (a small selection will sometimes normalise) and (3) it's happened using 'wavehammer' on occasion too
When the message has happened the processer and ram are hardly being used (as i said in a previous post)
Anything in the settings below that could be the issue.?
Microsoft .NET Framework 4 Client profile v4.0.30319
Microsoft Visual C++ 2012 Redistributable(x86) - 11.0.60610
Direct x v 11
My Computer _
Operating System
Platform: Windows 7 (32-bit)
Version: 6.01.7601 (Service Pack 1)
Language: English
System locale: English
User locale: English

Class: AMD Phenom(tm) II X4 955 Processor
Identifier: AuthenticAMD
Number of processors: 4
MMX available: Yes
SSE available: Yes
SSE2 available: Yes
SSE3 available: Yes
SSSE3 available: No
SSE4.1 available: No
SSE4.2 available: No

Primary: 1920x1080x32

Physical memory: 3,326.1 MB
Paging memory available: 6,650.6 MB
Virtual memory possible: 2,047.8 MB

CD Drives:

Detailed information about "HL-DT-ST BD-RE BH10LS30 1.00."
Vendor: HL-DT-ST
Product: BD-RE BH10LS30
Firmware version: 1.00
Driver interface: SFMMCX (17)
Location: adapter(01), device(00)
Drive letter: E
Buffer Size: 4096 KB
Max read speed with current disc: 40.0X (7056 KB/Sec)
Max write speed with current disc: 40.0X (7056 KB/Sec)
ISRC Read/Write: Yes/Yes
UPC Read/Write: Yes/Yes
BurnProof technology: Supported
CD-R Read/Write: Yes/Yes
CD-R Read/Write: Yes/Yes
DVD-ROM Read: Supported
DVD-R Read/Write: Yes/Yes
DVD-RW Read/Write: Yes/Yes
DVD+R Read/Write: Yes/Yes
DVD+RW Read/Write: Yes/Yes
DVD-RAM Read/Write: Yes/Yes
Eject tray: Supported
Erase: Supported
Audio play: Yes
Lock/Unlock media in the drive: Supported
Streaming play: Supported
CD-DA Stream is accurate: Yes
CD-DA Seek is accurate: Yes
C2 pointers: Supported

Subject:RE: Out of Memory Errors when Normalizing
Reply by: Cielspacing
Date:9/12/2013 1:41:54 AM

Ok, it all looks correct and up to date according to your log, Bone Studio. If we add the recurrence observed in various 32 bit installations, one could say it does present as a bug somewhere and SCS probably has it under scrutiny already.

Besides, the remaining alternative that the issue might be caused by problematic installation/configuration appears as remote,

Meanwhile and if you or someone with the issue are keen to go an extra step, you might try some Memory Configurations plus at the second part of this post, I include several System Optimizations, which by themselves might improve SF11 usage as it is.

Go to "Advance System Settings" simply by opening any explorer window and right-clicking on "My Computer"and a menu appears, then clicking on Properties will open a new window with the Advance System settings option located at the left column. Click this and then the System Properties window will finally open.
Other way is going to Control Panel, and clicking on "System", this will take you to the System Properties window

Once the "System Properties" is opened, go to advanced tab and click on "settings" from the Performance section. Once opened, choose the Advanced Tab and choose the adjust performance for: OTHER SERVICES.
This would be the first reconfiguration to test if the Memory error with SF11 32 bit has been affected Note this selection is recommended for Audio PCs. so you might want to keep it.

Additionally go to the "Virtual Memory" section just below, and click over the "Change" button.
A new window will appear that shows Windows' default selection on "Automatically manage paging file for all drives". In this window, I would try several alternatives and check one by one if the Memory issue persist.
*Firstly choose NO PAGING FILE. Since you (Bone Studio) said memory usage in your PC was low all the time, this choice forces Windows to use only real RAM and no the slow hardisk-based virtual one (also called Paging File) that supports the real. I have seen Windows 7 systems running better with this configuration. This is the ideal setup for 64 bit systems with ample RAM installed.
*Secondly if the above fails to improve things, choose "Custom SIze" and write the recommended number of MBs show in the same window just a section below. Make sure the same number is written on the "Initial" and "Maximum" spaces, you don't want your virtual Ram fragmented (Read below about Defraggler).
Every time you finish a configuration in this dialog you need not to forget to press "set" and "Ok", also you have to restart the PC each time you change anything in order for the system to change to the new settings.
*If everything still fails, you may want to keep the last settings and finally to try moving the paging file or virtual memory onto another drive (and thus choose NO paging File on C:) to rule out all alternatives at hand. OSs tend to show unpredictable behavior to non experts, after all.

Furthermore I list a few of my favorite general optimizations. One of them does affect virtual memory and the others are of general usage. The good side of these additional efforts is that you might adopt and apply them periodically for improved PC operation.

1. Registry cleaner
"Free Windows Registry Repair"
This one is real freeware, very light (less than 1 MB) respectful and efficient. I have tested in dozens of systems with zero issues.

2. Once you have leaned the Registry you might need to defragment it, something that de-fragmentation software does not do.use this specialized registry defragmenter.

3. Defraggler. Defragments the hardisk, Even after a first clean Windows install, the files appear fragmented.

Make sure you check the color codes and see the beige colored bricks as one single block, otherwise you will need to re-create the paging file using the procedure described above. Just cycle with the following three stages until one single block is created.
-1st set No paging file,
'-2nd restart and defragment,
-3rd set Custom Paging choice again equaling MIn and Max MB numbers, restart and analyze with defraggler.
Be careful that the last stage of the installer you need to untick the option that offers you (enabled by default) to add the Google toolbar.

4. CCleaner. Cleans temporal files and deselect software that forces its start when Windows starts.

//Lastly, there are additional tests that could possibly provide more info into which area the problem might be related to. For instance testing DPC (Deferred Procedure Calls) is rather simple and will show if some service or hidden process gets activated at the same time or before the Memory problem arises.
If a correlation is found, deactivating the signaled service or lowering the priority of the other process in question might help

Again, hope it helps.

Subject:RE: Out of Memory Errors when Normalizing
Reply by: Bone Studio
Date:9/12/2013 3:14:09 AM

Thanks Cielspacing,I'll be out tonight so i'll try out the new tweaks you've suggested and report back.But just quickly, I regularly perform cleanup's of the registry and the hard drives defragged.I use CC Cleaner and Norton Utility's.I really appreciate your effort to respond,There does seem to be a few others complaining so there could be a update patch available soon.

Subject:RE: Out of Memory Errors when Normalizing
Reply by: Bone Studio
Date:9/14/2013 1:16:17 AM

I'll just explain some of the faults i'm experiencing.
Freshly restarted with no other programs running and after defragging and cleaning the registry with showing only 4% processor and 30% Ram in use.
CD Ripping ...I ripped a cd containing 20 tracks it got through the first 16 tracks no prob's before the "not enough memory" error, I chose to continue with the rest of the tracks and it (seemingly ) randomly allowed a few more of the tracks to rip. I then restarted the program and tried to just rip the tracks that were missed (to no avail)..
Ripping an entire CD at once some times works (but not all the time)
Normalizing..(not that i use this much) ... but for an exercise i opened a 6 min track and tried to normalize to no avail .I stepped down the amount of the track selected till it would perform the task which was around a 1 minute selection from the 6 min track.
I'm sure it's not my computer.

Edit.. I have no problems ripping a CD with sf V 10 (did it easilly while playing a track on sf v 11 and playing music with wmp all at the same time.The processer was still only using 35% and ram got upto 60%)

Message last edited on9/14/2013 5:14:23 PM byBone Studio.
Subject:RE: Out of Memory Errors when Normalizing
Reply by: Bone Studio
Date:9/18/2013 7:31:44 PM

Just to add to the list of things that cause the Out of Memory Error (and to keep this at the top of the forum thread)
Click and Crackle Removal and Noise Reduction.
Do I need to have Both Sound Forge Versions 10 and 11 installed.
Both pluggins work fine in V10 but 'Error out' in V11 working on a 2 min Song .
I really only updated because I like the abillity to send to Spectralayers Pro, but if i have to save and open a file in version 10 just to use any of the sony pluggins then it's not worth the upgrade.
Edit.... add Sony's Volume and EQ pluggins to the list of 'out of memory' error problems in V10.

Message last edited on9/20/2013 7:32:16 PM byBone Studio.
Subject:RE: Out of Memory Errors when Normalizing
Reply by: Cielspacing
Date:10/4/2013 4:27:28 PM

Windows automatic fixing online service -fixit- has a solution for a special case of " "Out of Memory" error message appears when you have a large number of programs running".

Go to
Click on the blue text that says Fix this problem, and follow the suggested process.

Message last edited on10/4/2013 5:12:46 PM byCielspacing.
Subject:RE: Out of Memory Errors when Normalizing
Reply by: Bone Studio
Date:10/5/2013 12:54:23 AM

Thanks Again Cielspacing..
I'm still getting the problem (volume,Normalize even copy from other channel in fact many of the standard pluggins. Of a 11 min song any selection over 1 min would cause the error message - Sometimes)
Before I saw your reply, I'd just re-Downloaded the program from Sony and re-Installed it (the file size were different from what I downloaded originaly (163 MB (171,835,952 bytes)) to what I downloaded today (163 MB (171,848,160 bytes))
So I tried your fix (Both the automatic and the manual) and still the same problem...
I have re-installed sfv10 and that works fine no probs all the pluggins work and they work while other programs are running while sfv11 Dummy Spits even after a restart with no other programs running.
Just to note--- It seems to only happen when using Sony's own pluggins "Normalise,Fade in/out (on a large selection) ,Channel converter,the Graphic,Parametric and paragraphic seem to decide on the day if they are going to work or not.CD extraction - no change- it sometimes works then will be 90% the way through and stop or will randomly take some tracks and not others.
Izotope's pluggins all work fine and the rest of the program all works fine too..Recording works , sending selections to Spectralayers Pro 2 works, CD Burning works.
Anyone else had such problems or am I The only one???

Subject:RE: Out of Memory Errors when Normalizing
Reply by: soundsmith
Date:10/9/2013 1:52:24 PM

Actually, is isn't just Normalizing that can cause the "low memory" error. I never had a problem with SF10 using Processes, e.g. Click and Crackle Remover, Noise Reduction or Normalizing. After upgrading to SF11, with the new iZotope plugins, I started getting the "low memory" errors initially with the iZotope processes. Followed support instructions with the same bs as other users have gone through, i.e. installing under a new account, etc., none of which fixed the problem. I also tried the similar native SF processes and had a similar problem, specifically with Normalizing. After the initial Tech Support response thread (which expired because I can't devote full time to trying to fix defective software) Tech Support would no longer respond to my requests for assistance. I finally contacted SF Chat, which doesn't offer Tech assistance, to find out why I was being stonewalled. I was told that, indeed, a bug with the 32 bit versions handling of memory had been identified and that users would be notified when a fix was available. I reverted to SF 10 and continue to use it without incident. Wasting hours of time on this issue has left a sour taste. I'm not sure I will use SF11 even if a fix, supposedly, is offered or ever upgrade again. I'm also unclear as to why Sony bundled iZotope plugins that do the same thing as the native Noise Reduction bundle. Is this an admission that the native plugins are sub-standard?

Subject:RE: Out of Memory Errors when Normalizing
Reply by: cyberbeat
Date:10/20/2013 5:19:38 PM

Same here. I actually had so many problems (just like others on this forum) and I couldn't take the time to keep going back and forth with Sony to help figure them out. Besides, it's their job to work out the bugs, not mine. That's why I went back to V10 and had no trouble. Thing is -- now I can't even use V10 on Win8 Pro for some reason after doing a complete re-install of the OS and I also get the frustration of things sometimes working fine and then you reboot or something and it goes back to not working again. For now I struggle along with V11 but I hate it!

Message last edited on10/20/2013 5:30:02 PM bycyberbeat.
Subject:RE: Out of Memory Errors when Normalizing
Reply by: happyguy
Date:10/31/2013 3:50:44 AM

The new update that Sony just put out for version 11 seems to have fixed all the memory errors.

Subject:RE: Out of Memory Errors when Normalizing
Reply by: Bone Studio
Date:10/31/2013 4:09:22 PM

Well well.....Thanks Sony.
I can reduce the volume of a file by 3db I can now rip a CD......I might just change my name to Happyguy too.....hehehe

Subject:RE: Out of Memory Errors when Normalizing
Reply by: Cielspacing
Date:11/3/2013 11:25:30 AM

Plus Bone Studio, with the information in this thread, you may now fix most (configuration related) Out of Memory problems in Windows 32 bit systems.

PD:I do optimize and fix systems.

Subject:RE: Out of Memory Errors when Normalizing
Reply by: Bone Studio
Date:11/3/2013 11:28:34 PM

Thanks Cielspacing for the help you gave ...

Go Back