John Kernan
Level 1 (71 points)
Desktops

Q: fcp7 out-of-memory message

     This is suddenly popping up rather often. Only restarting the program get's me going again.Is there a better fix for this?

iPhone 6, iOS 9.0.2

Posted on Dec 23, 2015 5:01 PM

Close
John Kernan

Q: fcp7 out-of-memory message

  • All replies
  • Helpful answers

  • by Meg The Dog,

    Meg The Dog Meg The Dog Dec 23, 2015 5:09 PM in response to John Kernan
    Level 6 (11,168 points)
    Video
    Dec 23, 2015 5:09 PM in response to John Kernan

    Do you have still images in your sequence?

    If so, they need to be less than 4000 px in the widest dimension, RGB Color Mode, 8 bits/channel.

     

     

    MtD

  • by John Kernan,

    John Kernan John Kernan Dec 25, 2015 11:16 AM in response to Meg The Dog
    Level 1 (71 points)
    Desktops
    Dec 25, 2015 11:16 AM in response to Meg The Dog

    I'll check, but I'm almost positive that there's nothing that wide.

  • by Meg The Dog,

    Meg The Dog Meg The Dog Dec 25, 2015 12:10 PM in response to John Kernan
    Level 6 (11,168 points)
    Video
    Dec 25, 2015 12:10 PM in response to John Kernan

    Check the color mode and bit depth as well. CMYK causes problems.

     

     

    MtD

  • by John Kernan,

    John Kernan John Kernan Dec 30, 2015 6:47 PM in response to Meg The Dog
    Level 1 (71 points)
    Desktops
    Dec 30, 2015 6:47 PM in response to Meg The Dog

    Just getting back to this.

    There are no CMYK files.

    What's worse is that I placed an entire nested sequence into the timeline. The elements of the sequence were all rendered, but the sequence itself would not render. Finally, when I more or less just jiggled the words, it went through.

    This is a long term legacy project with a ton of material, maybe too much. Maybe I should jump to newer software, but it seems pretty daunting at this point, and anyway I'm trying to get it wrapped up and don't want to open a whole can of worms.

  • by mdesignffm,

    mdesignffm mdesignffm Jan 5, 2016 2:54 PM in response to John Kernan
    Level 2 (306 points)
    Notebooks
    Jan 5, 2016 2:54 PM in response to John Kernan

    this is a common error. i do not know a real cure either.

     

    reasons i experienced:

     

    jpegs much bigger than sequence resolution. some codecs (gopro, some mp4s,...). large 4:3 files in a 16:9 sequence.

     

    workaround:

     

    use only pro res files in 16:9 for video. convert everything else, eg with mpeg streamclip. in case of complicated things (eg nested sequnces), export and reimport as simple video. crop and resize jpegs to minimal size required.