Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Out of Memory error while rendering

  • Out of Memory error while rendering

    Posted by Eddie Brega on March 2, 2006 at 6:26 pm

    We are doing a 96 minute documentary that has a lot of high resolution images and about 115 hours of footage. While we are rendering our sequence we often (but not always) get an out of memory error. I’ve tried a ton of different things but nothing has helped.

    Some info about our system/project:
    1. Project file has been trimmed to just the one sequence and some bins with clips. Its 29 MB. We are working entirely in DV right now but will be onlining back to HD.
    2. OS 10.4.2, QT 7.0.3, FCP 5.0.4, 4.5 GB RAM, Dual 2.7 G5, 350MB free on our 2TB sata raid drives,
    3. Since we are going to hd, some of our images are very very big (one is a poster that we zoom in closely on). I’m thinking that is has to do with these images. In the System Memory settings, should I bump up the still cache or is that just for real time viewing and not rendering?
    4. I’ve trashed prefs, cleaned caches with Onyx, tested system memory with TechtoolPro.

    Any ideas? Thanks.

    Randyp replied 20 years, 2 months ago 3 Members · 2 Replies
  • 2 Replies
  • Jay Dobek

    March 2, 2006 at 6:51 pm

    One thing that may be the cause here is the lack of space on the 2TB drive. It is recommended by most that you do not exceed 80% (some say 90%) of available drive space. So if you have a 100GB drive you wouldn’t fill it past 80GBs.

    The disk might be fragemented as well. You can run a program like Disk Warrior to help with that. Warning – it will take awhile on a 2TB drive.

    Make sure you back up all your files for this project. Worse case senario you may have to wipe the drive clean and re-batch everything.

    Good Luck.

  • Randyp

    March 2, 2006 at 6:54 pm

    What drive are you rendering to? For me, when I got this same error message, the solution was simple. It turned out that I had tons of space on my RAID, but I was actually rendering to a file on my Mac hard drive, which, as I discovered, was practically full with other files.

    Randy

    “You are:
    1. Untalented but excessively persistent
    2. Unbelieveably stupid
    3. An artist
    4. All of the above”

    –Norman Rockwell

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