Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy DESPERATE: Out of memory error with IMPENDING DEADLINE!!

  • DESPERATE: Out of memory error with IMPENDING DEADLINE!!

    Posted by Josh Evans on January 10, 2006 at 3:59 am

    Hi,

    I’ve been having “error: out of memory” messages recently on a big project (the project file itself is around 140MB). They were annoying but not too much of a problem, it happened every 15 mins or so, the message came up, the canvas went red, but then it went away again.

    BUT NOW:

    I opened the project after an all-night rendering session, and none of the sequences will open. Whenever I click on a sequence, i get the “error: out of memory” message.

    Please help.

    The drive i have as scratch disk scratch has around 8 Gig free.

    Running FCP 5 on a Dual 2 Ghz Powermac,

    1 Gig RAM

    Mac OS X Panther

    Ben Holmes replied 20 years, 4 months ago 8 Members · 7 Replies
  • 7 Replies
  • John Grilli

    January 10, 2006 at 4:09 am

    Try Trashing your Prefs,,,,,,if you haven’t already, do a search in the forum on “trashing your prefs” it’s a common thread.

  • Mark Raudonis

    January 10, 2006 at 4:18 am

    1 gig of ram is very low. If you’re working with large projects, more RAM will absolutely make your day go smoother.

    Go buy yourself some more ram. 2 gigs good. 4 gigs better!!!

    Mark

  • Shane Ross

    January 10, 2006 at 6:11 am

    Oh yeah…WAY too little memory…you need at least one more GB, like Mark said.

    Shane Ross
    Alokut Productions
    http://www.lfhd.net

  • Boyd Mccollum

    January 10, 2006 at 3:30 pm

    Along with what everyone else said, 8 gigs free on your scratch disk seems really low. Do you have it on your system drive? You should get an external drive with more memory for your scratch disk/media. Check your system settings for minimum allowable free space on your scratch disk. Recommended is 10% of the size of your the disk drive you have it on.

    You may also have a bad render file. Close FCP, trash all your render files (you can always rerender) and see if you can reopen your sequence.

    Boyd
    “Go slow to go fast”

  • David Bogie

    January 10, 2006 at 6:36 pm

    [mushyosh] “I’ve been having “error: out of memory” messages recently on a big project (the project file itself is around 140MB). They were annoying but not too much of a problem, it happened every 15 mins or so, the message came up, the canvas went red, but then it went away again.”

    Good god, you had all that warning and you just kept working?
    Your karma, baby, but you SHOULD have made a backup copy of your project file immediately and considered your worst case scenario and then made some intelligent plans to prevent it from happening.
    There’s a long list of prophylactic measures including incrementing your project to a new version, Media Manager-ing a new copy containing only used media, and backing up everything perceived as critical to a cheap FW drive just because it would feel good to have a backup.

    While we wish the best of luck–no on wants to see anything bad happen to you or your media–but you’re on the edge, you got there yourself and next time we hope you’ll know better.

    bogiesan

    This is my standard sigfile so do not take it personally: “For crying out loud, read the freakin’ manual.”

  • Phil

    January 10, 2006 at 8:35 pm

    This has happened to me once before. Try making a complete copy of your project. Copy everything in your browser and paste it into a new project.

    Close both projects and reopen the new project. The sequences should open.

    Phil

    Dual 867, 2G RAM /
    OS 10.3.7 / QT 6.5.2 / FCP 4.1.1

  • Ben Holmes

    January 11, 2006 at 1:32 pm

    Reverting to a previous saved version will cure this problem – then save a copy and use media manager to back up.

    I don’t believe this problem has ANYTHING to do with a lack of physical ram on the computer. I have two systems with 6 gig of ram, and still get this occasionally. It has been extensively discussed before on this forum – a search under ‘out of memory’ will, no doubt, add numerous advise on this. I have been led to believe it can be caused by a computational ‘divide by zero’ or recurring number error.

    If you didn’t have autosave on, and you have no other versions, you may have a big problem – although the previous post sounds interesting, so let us know. This is an ongoing problem in final cut.

    Ben

    Editec Broadcast Editing Ltd
    EVS and FCP specialists
    Current Mac systems All Dual 2.7Ghz with Kona 2 and Digital Voodoo cards, 6Gb Ram, Sapphire, SCSI320 Medea and Huge Arrays.

    FCP projects include Sky TV coverage of the Ryder Cup and US Open Golf – Live OB specialists. Edit/slomo vehicle.
    http://www.editec.co.uk

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy