Final Cut Pro Memory Error/ Fix RAM?

[Daniel Ludwig]

hi Alley,
there could be several reasons why this error-message will appear.

mainly it is an issue of the OLD FCP-sourc-code that now is about 10-15 jears old.

one reason could be, that you have to much sequenzes open at the same time, so close the sequenzes you wont use.

othere reason could be that you used CMYK-graphics within your sequenzes. graphics needs to be RGB not CMYK. uncompressed 8 or 10bit should not have a problem with it, but I know that othere codecs will!

there are also other reasons why this could happen, these are just some samples, mainly this is an issue with FCP7. we all need a new version of FCP with 64bit-support (it´s still 32bit) and new source-code.

cheers

danny

[Bret Williams]

It’s usually a jpeg in your sequence that’s too big to handle. With people passing around huge 8+ megapixel jpegs from digital cams these days, it’s becoming increasingly common. Gotta keep those jpegs to sizes under 4000×4000 generally. You can use Photoshop or Preview to resize.

[Tad Newberry]

ya, i’ve been running into this a lot, too, since moving to FCS3 (with FCP7). like the guys are saying, it’s probably a large still image. i have trouble tracking mine down, but then i also think that is not ALWAYS the problem. case in point: i left my machine to render a show for me overnight – 4 segments, about 30 minutes total. in the morning, it didn’t finish because of “out of memory” error. ARRRGGH.

so, i did a test and rendered just the first half of the sequence (which included the first 2 segments – of 4 total – of the entire show). no problems. so, rendered the second half of the show (second half of the sequence, which included segments 3 and 4), and it gave me the error fairly soon after starting, so i figured the problem file must be in segment 3. so, rendered segment 4 first, it finished fine no problem. so now, in my little mind, i have narrowed the problem down to only the third segment. i set in and out points on it for the first half of segment 3. it rendered no problem. then the second half of segment 3…no problem…so, in conclusion, by the time i broke the rendering down into smaller chunks (all WITHOUT finding nor deleting any “corrupt” files), it all ended up rendering fine…and i’m still stuck with the mystery.

oh well…but maybe all this will change with FCP 8? i don’t recall it happening in FCP 6 when i had half the RAM.

thanks for helping out a bonehead!
__________________________

FCS3
2.66 GHz Quad-Core Mac Pro
6GB RAM
NVIDIA GeForce GT 120
…and a few TeraBytes o’ storage
(then it’s on to PetaBytes, ExaBytes and MosquitoBytes!)

[Alethea Gogeri]

Thank you all so much for the advice- I relocated my media and the project opened. I reconnected the media one by one and found a video file that was causing the trouble. Thank you for your help so much! I truly appreciate it ya’ll have saved my butt! 😀

[Tony Brittan]

Another thing that helps is to make the dpi on images 72dpi. I use Photoshop to batch re-size to .png and 72dpi.

Tony Brittan
Apple Certified Pro – FCP
Owner – Island Shore Productions

[Dean Neal]

Other than the obvious comments about still images, one thing we have learnt with these issues is when you are close to finalizing your edit to print is to delete excess junk in your FCP Project – bins, sequences etc.

We edit in full ProRes HD for 90min shows and by doing this have seen our FCP Project file sizing drop from 60-70MB down to less than 10MB!

Dean Neal…

[Tad Newberry]

Seems like a pretty good idea…i suppose the best way to do this is via Media Manager, and just do a copy (or move?) of the final timeline/sequence?

thanks for helping out a bonehead!
__________________________

FCS3
2.66 GHz Quad-Core Mac Pro
6GB RAM
NVIDIA GeForce GT 120
…and a few TeraBytes o’ storage
(then it’s on to PetaBytes, ExaBytes and MosquitoBytes!)