Error: out of memory (after trying everything i found on the forum)

hi guys,
I'm editing a short film shot in HDVCPro 1080i50i
I'm on FCP5 on a MacBook 2Ghz Intel Core2Duo with 1,7Go Ram & Mac 10.4.9. Stockage is 120go with 40go free.
The rushes & project is on an extern LaCie disk (it takes 200go of the total 250go).
When I add rushes on the timeline, the error message "out of memory" keep coming up.
I tried everything i found on the forum (trashing preferences, lowering the application rate in memory & cache, making several "mini projects"...).
Im runnin out of ideas & my only option is to use a Power PC G4 with 1.2go RAM (I doubt it will change anything)
If any of you can suggest something, or at least confirm me that i've to invest in a MacPro ...
Thx
g4 & macbook Mac OS X (10.4.9)
g4 Mac OS X (10.4)

easy setup is "DVCPro HD 1080i50" & sequence settings are the same...
i don't understand why it worked fine during my first days on the project & began to mess only now...
thanx

Similar Messages

"Error: Out of Memory" when trying to Render

Hello all,
I'm editing a project in FCP 5 that is using, in part, .mpeg-4 videos downloaded from the internet. After several weeks on the project with things going fine, the downloaded videos can no longer render. I can see them in the source window, but when laid into the sequence these downloaded videos produce an "Error: Out of Memory" message. Other videos of this type that are already rendered and playing in the existing sequence cannot be re-rendered or adjusted without producing the same Error message.
A few things to remember...
1. Other types of rendering, such as filters and fit to fill effects, render just fine.
2. There is over 30 GBs on the external drive this project is running on.
3. I've tried resetting scratch disks, transferring the project to another drive, and opening it on a new, super-fast computer, and nothing is different.
Please help, I'm really stuck in the mud here and am dying to get past this issue,
Peace,
Sam

Did either of you find an answer? I'm running into the S A M E issues. I feel strongly that it has to do with the quicktime update, as editing mp4's worked FINE in January.
There is a lengthy protocol for trying to circumvent this issue:
http://discussions.apple.com/thread.jspa?threadID=1413028&tstart=0
Didn't work for me, but I think it worked for the query. And VLC (http://www.videolan.org/) ended up being the only program I can even VIEW mp4 in now properly.
So if you can use a viewer, that works.

Multiclip Nightmare: General Error/Out of Memory when trying to match frame

I'm an assistant editor on a reality show and am fairly experienced with Final Cut Pro. But I've never seen something like this.
At our post house, we have over 30 Macs running FCP7, streaming media off a Xserve/Promise RAID SAN via Fiber channel. We create multiclips for everything (it's a reality show) and have run into some weird bugs.
What's happening is that mutliclips will all-of-a-sudden be unable to match back to the original multiclip. It gives a General Error then an Out of Memory error. Sometimes, after those errors, FCP immediately quits. When I double click the clip in the timeline, I get the same general error. I can, however, match back to the original media clip. But matching back to the multiclip causes the error.
I can't pinpoint a cause or common element. It's happening to different episodes with different editors and different project files.
Also, randomly, things will go offline for no reason. And not everything in a timeline, just some things (which makes no since). We can reconnect them quickly since the media drive never went offline in the first place. I mention this because but I'm wondering if both of these problems are common symptoms of corrupt multiclips and if there's a way to fix them. The only element that I can find linking media randomly going offline is that these multiclips had subclips embedded in them. But even that doesn't seem to be a common thread.
These timelines have been passed around from story editors to editors to AEs then back to editors, so we're thinking these multiclips might be getting corrupted through that process. I don't understand why because everything's looking at the server and all the Macs are pretty much identical.
What I began to do was recut in each clip on the editor's timeline with the original multiclip. It fixes the problem but it's beyond time consuming to say the least. Now that these errors have come up three times in different places, I'm worried we have a widespread problem and if there's a better way to fix it.
Details:
We transcoded all the DVCPRO tapes with AJA Kona Cards to NTSC ProRes (LT) with plans to online the show once we lock
Everyone's running the latest FCP7 and Snow Leopard release

Nate Orloff wrote:
It seems that FCP is making HUGE multiclips. I'm guessing that's the source of the memory error. Some multiclips (the ones it'll let me open) are 9 hours long.
Interesting... Could be the source of your problem indeed
And for no reason.
Are you sure there's no reason? When making multilips there's not one clip's timecode passing 00:00:00:00 for exemple? Or a small clip is also selected with a complete different Timecode? Is it black all 9 hours long? etc.
There must be something that is causing these long multiclips.
I agree with Tom (down in this thread) that sending apple feedback with as much detail as possible might be helpfull.
[FCP feedback|http://www.apple.com/feedback/finalcutpro.html]
I would also be interested in an XML of one of the culprit clips. Not that I know answers, but looking at it might give some clue.
Please select one of the wrong multiclips (in the browser). Select File > Export > XML. (version 5, include metadata; Please also make a version 4 XML).
Send both XML to my email address (in my profile; click on my name in the left column of this post). No promises But you never know...
Rienk

Why do I get a "Fatal Run Time Error: Out of Memory" after an hour while using RT on a PXI 8186?

When I run this code with high speed DAQ+proccessing+control for over an hour in RT on an 8186, I get the above error. There were some arrays being built really quickly, etc. So I replaced these array initializations followed with "replace arrays subset" blocks. Still ,No luck.
I'd really appreciate it if anyone could help me. the code can be posted here as well if reqd.
I'm Running LV RT 7.1, and the target is a PXI-8186.
Also, is there any way of allocating extra virtual memory in RT?

Let me second everything that Aaron mentioned.
Please post some code that demostrates your trouble and we will take a look.
Gnerally I have to say that RT applications are rather demanding in the area of memory.
I find myself avoiding data types that can vary in size, like strings. These can demand increases in buffer allocations such that the buffer previously allocated are insufficient, are tossed on the heap and another larger block is allocated. Too much of this happening can kill you in RT. Building strings is bad.
Building arrays is just not allowed.
LV2 globals (when properly coded) are useful in keeping memory useage static or diminishing. This dovetails with Aarons circular buffer.
Review all code that is executed repeatedly using
Tools >>> Advanced >>> Show Buffer Allocations
In a nutshell, one or more of thes is killing you.
Post your code so we can make specific suggestions.
Trying to help,
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

IMac monitor (my parents), the greys are so light and faint, they are almost impossible to see. especially in icalendar. i've gone into system preferences and i think i've tried everything there and checked the forums. no luck. any other suggestions?

monitor too faint to read. the greays on my monitor are so faint, they're almost impossible to see. especially the numbers of the dates in ical.
i've gone to system preferences and contrast controls. but no luck. any other suggestions? thank you

Thank you. I didn't know about the universal access adjustment. All the way left is a little better, but still much fainter than on my own imac. I'm not sure why apple uses grey typeface, but it's so faint on this imac monitor that it was difficult to find the "reply" option on this post. Are there any other suggestions? thank you

Receiving "Not Found" - then "Error:Out of Memory" trying to open Sequence

I have received a FCP Project edited in 2009 from the UK and have pulled the project file onto my workstation and all of the media onto an ext HD. I have also reconnected all of the media. However, when I try and open one of the Sequences in the project - I receive the following error "Not Found" then once I click off of that a second error "Error:Out of Memory". All of the other sequence in the project open fine.
Initially, I was able to open the original project file and open the sequence - but when I tried to copy the sequence & paste into a new project-I would receive the errors. Now I am receiving the same errors in the original project.
At first I thought it might be an problem with the computer but I have tried this on two different work stations /computers so I don't think it would be a prefs ( trash preferences) issue. Also footage was first on an XRAID and then I brought it to an external HD, so I don't think it had anything to do with permission issues.
This sequence is critical that I am able to get to it as it is part of a TV episode, so I would very much appreciate any help / advice on fixing this problem ASAP!
Thanks!

p.s. having looked at other posts, perhaps I am missing some (or all) of the relevant codecs?
In the folder Macintosh HD > Library > Quicktime
there is basically nothing. Do you think this is the problem?
If so, where do I download FCP codecs from?
Many thanks..

Computer error - 'Out of Memory'

Hi all,
Company I edit for bought a new tower. Here are the specs
Processor Two 2.66GHz 6-Core Intel Xeon
RAM 12GB
Graphics Card ATI Radeon HD 5870 1GB
Yesterday was my first day on it, and all went fine until I started bringing render-heavy motion files into Final Cut. It would start rendering them, and then stop and say 'error -- out of memory'.
The internal drive has 800G of free space, but Just to be safe, I switched the scratch disc to an external with 400G of free space. Got the same error and message.
I also tried trashing preferences, repairing disc permissions and restarting. No luck.
I switched to my laptop (2.8 GHz Intel Core 2 Duo/4G Ram) and the sequence rendered just fine (if a little slow).
Any idea what's wrong? We bought the machine specifically for rendering and compressing, so this is pretty frustrating...

I've only run into this problem in a ProRes project, with clips transcoded from a Canon 7D. Other projects, using DVCPRO HD 1080, with lots of effects, haven't done this. What seems to help is 1. If you're using still files, make sure they're RGB and 72ppi; when I can I use jpgs rather than tiffs, and I think it helps to make them no larger than you need; 2. Close the sequence tabs you're not using, especially if they're psd still files; 3. Selectively render only the tracks at the top; 4. Save after every render.
If anyone has other ideas, please let us know. This really can be a pain.

Ora-04030 process out of memory when trying to allocate nn bytes..

Hi,
Again we are facing the same error after increasing pga_aggregate_target from 2G to 3G, the journal import program request finally results in ora-04030 process out of memory when trying to allocate nn bytes.
wiil there be any bugs issue?
DBMS:9.2.0.3
OS :sun sparc 5.10

IF possible try to apply last patchset to take your DB to the latest version which should be more reliable and many bugs should be solved.
Do you have free physical memory to use the 3gb?
Hope this helps.
Regards.
FR.

Getting Error Out Of Memory while importing the work repository in ODI 10g

I exported the work repository from topology of ODI 10g of one DB and tried importing it in the another ODI 10g topology of another DB.While importing i got the error 'Out of Memory' .
Can somebody suggest me ,how to solve the heap size out of memory issue while importing in ODI 10g.
Thanks in Advance.

Hi,
you have to post your question in ODI forum
Data Integrator
Suresh

TS1587 I tried everything, except for reinstalling the SO-DIMM memory modules. Still, my iMac will not wake up. Turning it on you can hear the fan run, but the display stays dark. Any ideas what to do? Thanks Maja

My iMac won't start up, or wake from sleep. I've tried everything, except for reinstalling the SO-DIMM memory modules. Still, my iMac will not wake up. Turning it on, you can hear the fan run, but the display stays dark. Any ideas what to do? Thanks!

Mac doesn't boot
Can you hear the fans and hard drive and see the white boot screen? Flashing question mark? The circle just runs and nothing happens? Only black screen and nothing else? These can be very helpful to diagnose the source of the problem. [1]
Flashing question mark [2]: This is usually a sign of a failed hard drive. This indicates that boot up volume can not be found.
Black screen: This is usually a sign of a failed logic board. There is no single reason for this and this may be caused by failed GPU, screen, CPU or RAM.
Circle of death/no circle/blue screen: This is usually a sign of a hard drive failure. This may NOT be a dead hard drive, just broken permissions or something
Gray screen/Apple logo/spinning gear or globe/prohibitory sign/folder with flashing question mark [3]: This could be a sign of faulty hardware but more likely a software issue, i.e. broken permissions, failed software update, etc.
[edit]
What to do
First, hold down the option key (also known as the alt key) just after you've pressed the power button. This should show all the available options to boot from, so if you have Windows installed through Bootcamp or a disk in your SuperDrive, you should be able to see them along with your OS X drive/partition. Select the OS X partition with arrow keys and press enter. Startup key combinations
If that doesn't help continue doing the steps from below:
1. SMC reset [4]. Shut down and unplug all cables including power cord for at least 30 seconds and then plug in power cord and keyboard/mouse.
2. PRAM reset [5]. Hold down option, command, P and R while booting. Start it when you hear the sound and don't let go before it reboots.
3. Safe boot [6]. Hold down shift while booting to boot into safe mode. If this works, open Disk Utility from Utilities and repair your permissions and verify the disk
4. Hardware test [7]. Insert the install disk (disk 1 in Mac which shipped with OS X 10.5.4 or earlier, disk 2 if shipped with OS X 10.5.5 or newer) and hold down "D" before the grey boot screen opens. Follow on screen instructions
5. Boot from install disk. Boot from the disk that came with your Mac. Hold C while booting. Select Disk Utility from top bar and repair permissions and verify the disk. Reboot normally and see if it works now.
6. Boot from another Mac (Firewire target disk mode). Connect the machines with a Firewire cable. Power on your Mac and press T. Select the other Mac's hard drive. Download the current OS X combo update. Run the combo update installer and select the drive that won't boot as the destination.
7. "Repair" OS X. Boot from the install disk as in point 5. and reinstall OS X. This should NOT erase any data, just replaces the system files which may have caused your booting problem. Now install the latest combo update for OS X and repair permissions on your drive with Disk Utility.
7.1. Install OS X into an external hard drive and then boot from it [8] and try to copy your data from the hard drive before proceeding. If you have done a backup recently, you don't have to do this.
8. Restore OS X from Time Machine backup. Boot from the disk that came with your Mac and choose the Time Machine restore option. This step will lose any changes made since your last backup but the system and your data will be put back to exactly as it was on that date.
8.1 Reinstall OS X. Boot from the install disk as in point 5. and select Disk Utility again. Now erase the whole hard drive and install OS X again. If you had a Time Machine backup and step 7 worked you don't have to do this.

Error message-----General error (34) Error : out of memory

Im trying to open a sequence & im getting an error message general error (34) Error out of memory
wont open sequence
any ideas

How much free space do you have on your scratch disk
What amount of RAM?
Read this thread:
http://discussions.apple.com/thread.jspa?messageID=1162802&#1162802

My ipod touch 4 gen is in recovery mode and i dont know how to get out of it,i tried everything like hold the home and top button at the same time. All it did what g to the apple logo and went back to recovery mode any help?

My ipod touch 4 gen is in recovery mode and i dont know how to get out of it,i tried everything like hold the home and top button at the same time. All it did what g to the apple logo and went back to recovery mode any help?

Once the Device is asking to be Restored with iTunes... it is too late to save anything... and you must continue with the Recovery...
kevinpowell1 wrote:
how can i get it out of recovery mode?
Make sure you have the Current Version of iTunes Installed on your computer
iTunes free download from www.itunes.com/download
Then See Here > http://support.apple.com/kb/HT1808
You may need to try this More than Once... Be sure to Follow ALL the Steps...
Take your time... Pay particular attention to Steps 3 and 4.
Some users have reported as many as 8 or 9 attempts were necessary before success.
After you have Recovered your Device...
Re-Sync your Content or Restore from the most recent Backup...
Restore from Backup > http://support.apple.com/kb/ht1766
If the issue persists...
Then a Visit to an Apple Store or AASP (Authorized Apple Service Provider) is the Next Step...
Be sure to make an appointment first...

Error: out of memory during render

Hi,
I am attempting to write a non-self contained quicktime movie from a sequence in FCP 6.03. The sequence was originally edited in AIC 720p, then onlined to 8 bit uncompressed via the .m2v files.
When rendering I receive an "error: out of memory" message.
I am wondering what might have caused this, as I have not experienced it before. I have done a search within mac forums, but none of the threads I found seemed to address my specific issue.
Any thoughts??
Thanks,
-Tom

Onlined to 8 bit uncompressed SD? or HD?
You likely have a corrupted media file involved. It's usually the same percentage in from the head of the sequence, as the failure is reported... i.e, the failure is reported after 50% complete? then look half way into your sequence, and re create or re capture that area of the sequence.
Jerry

Error Out Of Memory Due to Digi Effects

Hello everyone, got a bit of a tricky situation to troubleshoot :/
Before you ask here's my iMac info http://gyazo.com/0648a1d03fb15935117894dd6716ffbc
Ok so the problem is, I'm making this video and its having a lot of distortion effects added to it within FCP 7 using the plugin Digi Effects Damage "Blockade". Now I had a sequence which had just enough memory to use it on all the clips I needed. However, I sent that sequence to Color and sent it back to FCP and in my new 'color sequence' I can watch the whole thing through in real time with safe RT and unlimited RT, however there is this colour http://gyazo.com/d022bf802fb82d76d191a004ddcbc387 above all the clips that have the plugin on.
Although I can watch it through in playback mode, when I render, after a few seconds it says Error: Out of memory.
Here are my general sequence settings http://gyazo.com/a270414e2c2d38cb1274f8f84f507383
I am using clips in the pro res 422 format. Any ideas? :/
-Bob

Hi
Out of memory use to refere to amount of
• RAM
• free Space on Start-Up (Mac OS) Hard Disk - VERY IMPORTANT
• Space availably on Hard Disk/s That holde the Movie Material
RAM
Never been a problem to me - 2 resp 5Gb dep on Mac used
Free Space on Boot HD
I never go under 25Gb free space - when working on SD-Video project's - I guess that 4 - 5 times more will be a safe level when doing HD. This space HAS TO be just here as Mac OS works like UNIX (it is in fact) and then produces lot's of temp. files that can not be stored elsewhere and so does FinalCut (or whatever application running)
Space to keep Movie Project
• Should be on other hard disks than the Boot HD.
• Should be as fast as possibly - RAIDed, FireWire or Thunderbolt - USB/USB2 performs badly to me and especially when filling up and when holding HD-material
• MUST BE - Mac OS Extended (hfs) formatted - this goes for all Video editing - iMovie, FinalCut or Adobe etc.
• This too can fill up - So this space is also important
What memory that are not sufficiant - is hard to guess - when You don't tell the above figure.
Good Luck in finding it
Yours Bengt W

Render - Error: Out of Memory

I have been getting the following error message while trying to render - Error: Out of Memory.
The system I am working on has 10 gigs of RAM and is connected to a SAN with a whole lots of storage. The error message doesn't appear until almost the end of a render, which is of itself very annoying. Anyone know why this is happening? If I restart the application I am OK for a while then it happens again.

If you really want me to hold your hand I will. Here's some links that came up when I typed "Out of Memory"
http://discussions.apple.com/thread.jspa?messageID=7490395&#7490395
http://discussions.apple.com/thread.jspa?messageID=7376550&#7376550
http://discussions.apple.com/thread.jspa?messageID=7480220&#7480220
http://discussions.apple.com/thread.jspa?messageID=7756170&#7756170
If you still don't find what you need post back and there's a few other things you can try.
FYI- No need to be a smart a$$ to someone trying to help you.

Error: out of memory (after trying everything i found on the forum)

Similar Messages

Maybe you are looking for