Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Render: Out of Memory Error

  • Render: Out of Memory Error

    Posted by Mike Kahn on February 25, 2007 at 5:20 pm

    I am onlining a show for a new company and I try to render the next days episode overnight. I continue to get an error message after about 8 minutes of the sequence being rendered. The message comes up and says “Out of Memory” I am rendering to a drive with 300gigs of available memory.

    I am using a Mac G5 with 4 2.5 GHz; 5 G DDR2 SDRAM. I have tried restarting the computer to free up RAM and have closed all other programs to save RAM. This really makes no sense to me and I have done some searches in this forum but with no real answers found.

    Any ideas on settings or anything that need to be changed to get a full 30 minute sequence to render overnight with no problems?

    Thanks,

    Mike

    Mike Kahn replied 19 years, 6 months ago 3 Members · 5 Replies
  • 5 Replies
  • Chris Tompkins

    February 25, 2007 at 7:42 pm

    I’ve had this b/4 on a troubled proj. I ended up rendering it a little bit at a time, peice by peice, like a giant elephant

  • Mike Kahn

    February 25, 2007 at 7:49 pm

    Yeah this is how I’m getting around it also, but I want to render overnight to save time during the day.

  • Chris Tompkins

    February 25, 2007 at 9:30 pm

    I hear ya, who wouldn’t. Have u tried trashin prefs?
    Creating a brand new proj. opening the old one and drag over the timeline into the new proj.?
    Sometimes helps.

  • Ben Holmes

    February 26, 2007 at 1:51 pm

    [twentydeuce] “I have done some searches in this forum but with no real answers found.”

    Really? This question is asked frequently. Previous posts have made the point that the error has NOTHING to do with RAM OR disk size.

    Admittedly, no one is certain what causes the problem, although the consensus is that it’s due to a bad render file (if it occurs once during rendering) or a bad media file – which you should be able to deal with using the bit by bit method.

    Other causes include nested sequences (which sometimes seem to confuse FCP in a sort of “divide by zero” logic error sort of way – ie. some kind of illogical calculation has been performed by the system as a result of the nest etc.) This is not to say that the nesting or sequence is incorrect on your part, it’s just a bug in FCP, which MAY have been fixed in 5.1.4 (maybe…)

    Solutions? If it occurs when you OPEN a project, restore to a previous autosave. If it occurs during a render, clear all of the render files for that project off the system and start again. If it still happens, you may have to replace a media file.

    If it happens all the time, I would recommend a complete system re-install from OsX up. You’d be suprised how much more stable a clean system can be using fcp.

    Hope this help!

    Ben

    Editec Broadcast Editing Ltd

    EVS & FCP specialists for live OB operations.

    New HD edit/slomo truck on the road this month. Dual FCP systems/6 slomo positions.

  • Mike Kahn

    February 26, 2007 at 3:37 pm

    Thanks for the suggestions, I will pass them along to the company who owns the machines.

    What confuses me is that I can render if I do it act by act but can not render an entire sequence at one time. If it always failed at a certain point I could figure out what is wrong with a certain media file but it seems to be random and without cause.

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