Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy FCP (7.0.4) Message “Out of Memory”—Far From it & Project Takes 23 minutes to Open–CRAZY!

  • FCP (7.0.4) Message “Out of Memory”—Far From it & Project Takes 23 minutes to Open–CRAZY!

    Posted by Daniel Monskey on December 5, 2013 at 2:35 am

    FCP is being difficult. I have been getting messages late in edit sessions that say I am out of memory. I am working with a Wiebetech RTX 200 raid system with 2.0 TB internal drives with 1.1 TB available. My Mac:
    Model Name: Mac Pro
    Model Identifier: MacPro3,1
    Processor Name: Quad-Core Intel Xeon
    Processor Speed: 2.8 GHz
    Number Of Processors: 2
    Total Number Of Cores: 8
    L2 Cache (per processor): 12 MB
    Memory: 8 GB
    Bus Speed: 1.6 GHz

    I have trashed my preferences a few times which helped for a few hours. The program and project has been taking 24 minutes to start up too—–this is ridiculous! And very time consuming. The project just crashed now.
    What could be going on that is causing this condition?
    Dan

    Daniel Monskey

    Daniel Monskey replied 12 years, 4 months ago 10 Members · 28 Replies
  • 28 Replies
  • Gary Milligan

    December 5, 2013 at 2:54 am

    8 GB RAM is a bit on the low side. That and your machine being somewhat ‘old’. It would also be helpful for us to know what kind of files you are working with – HD?… SD?… codec? What are your settings in FCP? How much footage are you dealing with and how long is your timeline? Do you have a lot of effects to process?

    HTH

    Gary

  • Nick Meyers

    December 5, 2013 at 8:38 am

    “What could be going on that is causing this condition?”

    my gues is the project size is too big
    how big is the project file?

    nick

  • Daniel Monskey

    December 5, 2013 at 8:53 am

    I am working in HD. I think what you are asking about when you refer to the codec is Apple Pro Rez 422 (HQ). I am working with about 850 GB of video data (various formats: Panasonic P2’s and GoPro and some other HD video shot with German equipment and compressed and sent via Dropbox to me).
    The timeline is 1:00:00 loaded with clips to be chopped and edited down to 15 minutes.
    The GoPro and German camera video all need rendering, but I have few effects other than a tweak here and there of the coloring and a transition here or there (very few of those too).

    Thanks for your response—-INCREDIBLY thorough and detailed to completely understand how to diagnose. You are very knowledgable!
    Dan

    Daniel Monskey

  • Daniel Monskey

    December 5, 2013 at 8:56 am

    The saved file is 26.6 Mb (but the project files are about 850 GB). I have worked with projects this large before and had no problems.
    I was thinking it was all the crazy render-needed GOPro and German HD video (formatting could be an issue with this).
    Dan

    Daniel Monskey

  • Nick Meyers

    December 5, 2013 at 9:03 am

    yes 28MB is definitely not a problem,

    so the GoPro and compressed german footage are the number one culprit.

    transcode and replace.

    nick

  • Xdominguez Pukkas

    December 5, 2013 at 11:03 am

    Hello,

    I would recommend you to stop using Final Cut Pro and go to Premiere. You can easily do that using xml, and you will also spare yourself a lot of future headaches.

    Just my opinion…

  • Daryl K davis

    December 5, 2013 at 5:39 pm

    Whenever I’ve run across this message it’s sometimes a corrupt video file, but more than likely a still image that’s either too big or it’s in CMYK format instead of RGB.

    ————————-
    DK Davis / Editor/ Post Super
    ————————-

  • Steve Modica

    December 5, 2013 at 5:51 pm

    FCP 7 is a 32 bit app. It can only address 2GB of memory (using signed pointers). So once it has filled up 2GB, it’s out of memory.

    Steve Modica
    CTO, Small Tree Communications

  • Steve Modica

    December 5, 2013 at 8:49 pm

    In the olden days, some apps and OS’s used signed pointers and some didn’t. If you have a signed pointer, you only get 2^31 bits (2GB). I thought FCP 7 was using signed pointers (like SGI used to). Clearly they aren’t (like Solaris).

    I think that’s what OP is hitting tho. The 4GB limit.

    Steve Modica
    CTO, Small Tree Communications

  • Andrew Kimery

    December 5, 2013 at 9:07 pm

    [Daryl K Davis] “Whenever I’ve run across this message it’s sometimes a corrupt video file, but more than likely a still image that’s either too big or it’s in CMYK format instead of RGB.”

    Agreed, I would definitely look at all your stills Daniel and make sure they aren’t too large and are formatted properly.

Page 1 of 3

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