What is the solution to "not enough memory to create sound buffer"?

My old computer system crashed and I replaced it with a much faster one with a lot more memory however when I open my older projects into AE CS3 on my new system I can no longer hear the audio when I render my projects via ram?
I don't recall what the settings were on the old system but I didn't have this problem before and the old system was very slow compared to the new one. My old system only had 2Gs of ram and again did not have this problem. New new system has 12Gs ram. Even if I select a 30 second piece of video on stage it doesn't play back with audio however I see the audio levels moving.
Anyone have any ideas?
Thank you.

I checked the audio preview duration and it is: 0:00 08:00. What would you suggest it be?
If you have sufficient RAM, you can ramp it up to 30 seconds without risk. It is in any case only relevant whzen multiple audio sources need to be "mixed", i.e. you have overlapping fades and such. With only a single source, AE will attempt audio passthrough, so disabling the sync might have freed up that part. Presumably your audio outputs are tied to another component (e.g. HDMI audio) or the audio hardware itself is set up so as to spit out surround sound or something like that, so the individual ports are synchronized by default. Turning it of simply should decouple the channels and give you a normal stereo behavior. Probably not the "clean" solution as intended by the audio hardware vendor (I'm sure you are supposed to flip some switch in their multimedia center software panel), but if it works, noone can argue success.
Mylenium

Similar Messages

Not Enough Memory To Create U_memTrackedObject, after effects error

Im doing basic keying of 10 minute hdv 1080i footage, with keylight. The background image is a 1080x1920 png still image. My macbook handles this same project just fine everyweek. Now my new mac pro can't do it. 20% percent into the export I receive the following errors.
"Not Enough Memory To Create U_memTrackedObject, (3k requested, 0 available)" then "not enough memory to create sound buffer," and sometimes "unable to allocate space for a 712x 402 image buffer." And after the errors appear, they will not go away unless i force quit the program.
I've adjusted the secret setting and some other settings to trouble shoot but just can't figure it out.
Please Help! Thanks guys!
Brand New Mac Pro osx 10.6.7
Processor 2 x 2.66 ghz 6-core Intel Xeon
Memory 6gb 1333 mhz ddr3
After Effects cs4 9.0.0.346
Multiprocessing is off
total ae memory usage 1.796
Ram to leave for other apps 2gb
secret setting: disable layer cache, purge every 5 frames

Thanks! the update worked and my render completed in record time! I'll do some more tests to verify. I dont know why the "adobe updater" didn't fetch this update tho on either of my machines. Or maybe i just clicked cancel everytime

Could not render the database. Not enough memory.

This seems to be a big bug in Fireworks CS4. I am building a 10 page website. I only had the opportunity to insert about 10 high quality images into the project, and then tried saving the project as a Fireworks PNG. It appeared to Save successfully, however from that point on, any object I would click on, any layer I would select a message would appear.
"Could not render the database. Not enough memory."
Has anyone seen this before? How can I fix this?
I tried doing a workaround. I tried opening the saved file from Fireworks CS3. Before opening, it displays a message about insufficient permission in the registry. I click OK, and it opens in CS3. I can finally edit the project and make changes, and save it without problems. However, even after saving in CS3, I cannot open it in CS4 without getting the error message. It is not only on my machine. I send my project to others to see if they can open it via CS4, and they can't either. They get the same message.
I attached the PNG file, this is for a school project.
Any help is most appreciated.

I'm relieved to hear that. So I trust that your images are all nice and small, file-size-wise.
Okay! I trust you have already defragged your hard drive and turned off all those nasty TSRs that eat up your RAM. Fileswapping is usually what slows my computer down.
Check for scripts that might be running wild in the background. Can't think what they might be, but if something is looping and shouldn't be, you'll end up with less free RAM to move around in.
I haven't noticed the problem with lots of layers, but I haven't been watching, either. Have you experimented with turning off the layers that you are not actually exporting? I understand the convenience in keeping all those layers in there...it's a big timesaver in editing throughout a project. If all the layers are not needed in the image export, however, turn them off temporarily. That might save some elbow room.
It sounds as if your system fits the basics, but you might check:
Windows
1GHz or faster processor
Microsoft® Windows® XP with Service Pack 2 (Service Pack 3 recommended) or Windows Vista® Home Premium, Business, Ultimate, or Enterprise with Service Pack 1 (certified for 32-bit Windows XP and Windows Vista)
512MB of RAM (1GB recommended)
1GB of available hard-disk space for installation; additional free space required during installation (cannot install on flash-based storage devices)
1,024x768 display (1,280x800 recommended) with 16-bit video card
DVD-ROM drive
Broadband Internet connection required for online services*
Mac OS
PowerPC® G5 or multicore Intel® processor
Mac OS X v10.4.11–10.5.4
512MB of RAM (1GB recommended)
1GB of available hard-disk space for installation; additional free space required during installation (cannot install on a volume that uses a case-sensitive file system or on flash-based storage devices)
1,024x768 display (1,280x800 recommended) with 16-bit video card
DVD-ROM drive
Broadband Internet connection required for online services*
Rather than jumping to think it's a bug, try a test with 9 layers, or 8 layers. If only 10 layers and up provide problems, file a bug/feature report or contact someone in support.
As this is a user forum, we (other users) neither speak for Adobe nor know everything about the applications from a support viewpoint, so while we're always willing to offer opinions and frequently solutions, real bugs are not in our bailiwick.
Perhaps someone with a multi-layer difficulty can chime in here.
Beth

Does the "Warning! Not Enough Memory" bug still exist in Logic 8?

Hello everyone,
I'm wondering if the dreaded "warning, not enough memory" bug still exists in Logic 8. Here is a detailed account of the bug from Logic 7: http://discussions.apple.com/thread.jspa?messageID=767597&#767597
If this is fixed, I'm seriously considering upgrading mid-project! The film score I'm working on has many doubling parts that I'd like to edit at the same time in the matrix editor. However, editing multiple parts in the matrix editor seems provoke the little bugger, and I've already been bitten a few times in this project already. The only solution I've found is to stay clear of editing multiple parts at once (i.e. edit each parts individually, which obviously takes more time) or save before editing and hope I dont get bit.
I would LOVE to hear a report that this bug has been exterminated, and perhaps may upgrade mid project if thats the case.
Thanks in advance for your reply!

Heya,
I'm not familiar with the bug you're talking about. But would, as a fellow film composer, strongly urge you against the mid project switch.
I loaded in LP8 and ofcourse had a look at what it was all about, and it's really really fantastic. It also seems very stable. I fortunately have a side project that I am working on so switched to LP8 for that. Whilst I'm thankful to get my head around a very new approach for logic, I'm also thankful that I have this side project as it has illuminated a multitude of problems that exist with LP8 that would make any scoring process a bit of a headache to say the least. The main one being that if you don't have a very very powerful mac (I'm prepping a really fully loaded 8 core) you are not going to get anywhere near the performance out of Logic as you do with 7. This is a bottom up overhaul and it needs hardware to match. Heck even my 30" cinema display seems cramped and insubstantial on this new version. I would be so bold to say hold off until you have a hearty new mac and at least 8.2 is released IMHO but maybe try and get on it onto a smaller project to familiarize yourself before hand.

Could not open the file. Not enough memory

I have always used fireworks cs4 normally, but today, i experienced a bit of trouble. there is one png file that when i click to open it the fireworks loads but then a message pops up (could not open the file. Not enough memory) after a bit of researching, i found out that this error happens when i bring to stage one of the common libraries menu bars. (menu bar 4). Does anyone know how to fix this?
ps: I am able to open this file via file-open-*png. Please i really need help. Is the library corrupted maybe?

Hi,
It opened on mine (1.2Gb). I don't think it's a memory issue. I've used FWCS4 with 512mb RAM, never had such a problem. (of course it was very slow at the start, and i used to leave for a cup of coffee first and then come back when it was ready for work. That's why i upgraded to 1.2G .)
Import this menu bar from the common library, save it again as a png and then open it with fireworks the way you did, to see if the same error occurs.
Has this happened with other files as well?

I see message "Cannot open the file. Not enough memory to open the file"

When I'm trying to open file from adobe.com on my tablet, I see massage " Cannot open the file. Not enough memory to open the file" . I've got 10 gb free memory , so I dont know, why...

Which system are you running (is this information correct in your profile)?
Are there complicating issues to this question such as you transferring libraries between computers?
Have you upgraded iTunes recently?
Troubleshooting iTunes installation on Mac OS X - http://support.apple.com/kb/HT2311 - read section on Opening iTunes for information about running multiple copies of iTunes.

CRASH "Not enough memory to create clipboard. This should never happen."

CRASH Error message: "Not enough memory to create clipboard. This should never happen."
What the F???
SvK

i was talking to someone at frankfurt about this (possibly logic had crashed on something we were looking at - i don't remember) and they said error messages like that were for the developers. the fact you saw the error message yourself was in itself a bug.
i don't know for sure, but i think you are seeing some kind of bug relating to memory management. try deleting history and reorganizing memory if you get this error a lot.

"not enough memory to create CORp_PSLMalloc" error msg

Hello everybody,
I've been getting this error msg every time I try to render a 1920x1080 composition. It has particles and high-res photos, but that's about it, (no video).
I'm on a 2.4 GHz Intel Core 2 Duo with 2.5 GB 667 MHz DDR2 SDRAM... and error msg actually reads "not enough memory to create CORp_PSLMalloc" / (132 K requested, 51K available)
Can anybody please tell me if I'm not setting this render right? I'm using H.264 compression, with highest quality and frame frequency set to automatic. it's 1920x1080 16:9 with no sound...
Thank you very much for your help!

Mylenium,
Applied all masks in the photoshop files, but had the same problem, same error msg... it's strange indeed, i've been having problems with the user and the session (that i also don't quite figure out, this user has administrator rights but when I try to save files into a folder i get an error msg saying that the file is locked and i can't). Do you think it might have something to do with that? Like, AE trying to access the files but somehow having problems with that?
I'm on a Imac by the way...
Thanks a lot for your help!!
Paola

After Effects: not enough memory to create COR_BibAlloc

After Effects: not enough memory to create COR_BibAlloc
(64k requested, 388412K available)
My comp is a 1280x720 30 second spot. Not too complex
of an animation with not that many layers (I know that
sounds vague). I've purged the comp and even tried the
"Secret" option in preferences to purge every 3 frames.
Keep getting this error message when I render. I am
running an Intel Xeon CPU 2.8ghz dual with 2.75 gb of
RAM with AE 7
Thanks

Mmh, yes, indeed that very likely would be to blame on Quicktime. You probably had better luck with CS3 which handles H.264 natively via MediaCore. My guess that it is simply some odd allocation of the compression which could be fixed, probably even a simple export from QT Pro to the same format. Do the files correctly play in QT player? As an alternative to QT Pro I recommend attempting to run it thru SUPER©, which is free. Perhaps this will repair the streams and prevent the errors. If not, you will have to shelve out some money or find otehr ways of converting your footage, I'm afraid.
Mylenium

What does "After Effects error: Not enough memory to initialize PSL. ( 83 :: 8 )" mean?

So, about a week ago I did a fresh install of 64-bit Windows 7 Ultimate on a new PC, and subscribed to the Adobe Creative Cloud, installing After Effects CS6 and Photoshop CS6 from the Adobe Application Manager, then doing all updates (and I just checked right now at 10:35PM on July 26th, I have the latest versions of everything).
After Effects was working completely normal, then just now, I tried to import a Photoshop .psd and I got the error message:
After Effects error: Not enough memory to initialize PSL.
( 83 :: 8 )
Then After Effects crashed. So now it opens up normally, but when I try to import a .psd or open an After Effects project saved from an earlier version of After Effects (CS3 to CS5) I get the same error and a crash, every single time.
Searching the forums, I see people talking about this error when importing .psds into CS5, and they say that getting the latest updates solved the issue for them (which obviously can't help me). I'm running all legit software on a brand new computer with 32 GB of RAM which has passed all my physical stress tests so I know it's not hardware related.
The one thing I saw people suggest is to hold down Ctrl-Alt-Shift when starting the program. When I do this, Windows asks if I want to allow After Effects to make changes to the system, and when I say yes, I can import .psds and open the older AE files. When I close After Effects and reopen it without holding down the Ctrl-Alt-Shift keys, it goes right back to crashing.
Obviously the smart-*** answer is "then hold down Ctrl-Alt-Shift, dummy", and I'll do that for now, but is there any clue what the problem is?
I feel like kind of a chump because I decided to stop using my student versions of Adobe software (I haven't been a student for about four years) and pay the full price for the cloud membership and the latest creative suite, and it's full of bugs.

Now, I get the same ( 83 :: 8 ) error listed above, followed by a new dialog window that reads:
After Effects error: Crash in progress. Last logged message was: <4488> <DynamicLink> <5> C:\Program Files\Adobe\Adobe Premiere Pro CS6\Adobe Premiere Pro.exe
Then, when I click OK, I get:
After Effects can't continue: sorry, After Effects has crashed. For After Effects Help and Support, go to http://www.adobe.com/go/learn_ae_support. If you still can't resolve the issue, please contact Adobe Technical Support (2).
( 0 :: 42 )
Clicking OK to that gives me a chance to save the latest project, then the standard Windows 7 crash dialog window opens, the one that gives me the choice of "Check online for a solution and close the program" or just "Close the program" and lets me View problem details, which are:
Problem signature:
Problem Event Name:          APPCRASH
Application Name:          AfterFX.exe
Application Version:          11.0.0.378
Application Timestamp:          4f6d63ab
Fault Module Name:          StackHash_a85b
Fault Module Version:          6.1.7601.17725
Fault Module Timestamp:          4ec4aa8e
Exception Code:          c0000374
Exception Offset:          00000000000c40f2
OS Version:          6.1.7601.2.1.0.256.1
Locale ID:          1033
Additional Information 1:          a85b
Additional Information 2:          a85ba096cc6b6acabe6eaf35bf34dc60
Additional Information 3:          f862
Additional Information 4:          f86227a9dfa15a47cdb6c94bb0d08360

What if the cache is not enough to hold one transaction's information

Hi, all,
I have the following concern:
If I make the cache to 100 mb, and in a single transaction, I inserted about several million records, I am wondering if this kind of process will cause problem? Before transaction.commit() gets called, I think all inserts will remains in the memory to be committed. So, if the cache has only 100mb, which is not enough to hold several million records, what will happen?
michael.

To add to what Charles said, if you have a single transaction that writes millions of records you will almost certainly run out of memory. The data is on disk and does not need to be in memory, but there is a lock for every record written that is stored in memory. The locks will fill up the cache and then the heap and you'll very likely get OutOfMemoryError. The rule with most database, and JE is no exception, is that transactions should be kept as small as possible. As Charles said, DeferredWrite is more appropriate for an initial load.
--mark

The Visual Elements - not enough memory

I have a 3rd generation iPad running iOS 6.01 with 3.7GB of free memory, but when I try to "update" "The Visual Elements" app I get a message that says "There is not enough available local storage to download..". I don't see how this is possible. Does anyone else see this error? I didn't see it listed in a search of the iPad community. I don't have this problem with ANY other update - and I have updated dozens since upgrading to iOS 6.0.
Does anyone have any suggestions on how I might resolve this? I have tried deleting other apps and freeing up space, but it seems insatiable.

I have a 64GB iPad, so I guess I'll delete more apps. Apple really needs to increase the memory options - hopefully the next generation will offer double the memory at the various price points. Solid State memory prices are dropping and you'd think they'd start upping memory. It is starting to feel like the days of 64KB memory in the early days of PCs......but then I may be dating myself.

Warning: "not enough memory to create shadow map vertice"

Hi,
First of all I am not too technically minded and not a great expert at after effects so keep this in mind when answering
I will post as much info to give a comprehensive idea of my setup and issue.
What I am basically asking is if I have after effects setup correctly for the spec I am running to achieve maximum benefit and performance?
And Is this perhaps a project composition error?
I have an after effects project that fails about 2.5 hours into rendering with this warning:
Now just a bit of background. I had 4gb and have upgraded to 8gb. The reason I upgraded was due to this error however I still have same issue (to be honest I dont see any improvement with ram previews etc).
This is my current PC spec:
I have changed virtual memory to double the RAM which I believe is what is recommended?
Now this is what after effects looks like on start up: Should it not utalise the 8gb?
When rendering it also just says using 4gb also:
Here are my multi processing and memory settings:
I hope this is detailed enough for someone to troubleshoot and help me out.
Kind Regards,
jmcall10

CS4 is 32bit. It will never use more than 4GB. Basic computer math. Simply consider turning off MP rendering to free up more RAM for the primary render instance. Shadow map size defaults to "comp size", but of course you may be able to reduce it. Check the advanced comp settings. Beyond that simply render to an image sequence so you can resume from the point of the crash/ hang without losing all your rendered stuff, then assemble the iamges to a clip file in a second pass.
Mylenium

Not enough memory to create DVD

What do I do if I don't have 20 GB to create my iMovie in iDvd? iPhoto and iTunes take up 50 GB together and I don't see anything else to delete.

I suppose you could buy another hard drive? And, if you keep all your media on a 2nd drive and your OS and apps on another, you will see a performance increase!
Mike

"not enough memory to place the file" error message

hello all,
running windows 7, illustrator cs3 on a pc.
trying to open or place psd files in illustrator and get the following message "not enough memory to place the file".
I've reset illustrator prefs, disabled "enable desktop connection", check scratch discs, etc.
Nothing seems to be addressing the problem, has anyone else run into this?

There's no such thing as an "Illustrator CS3 portable" version. What you have is an illegal torrent download. Any issues you experience may be due to the illegal copying of the software.

What is the solution to "not enough memory to create sound buffer"?

Similar Messages

Maybe you are looking for