Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro Legacy Sequence Not Found Error Out of Memory

  • Sequence Not Found Error Out of Memory

    Posted by Andrew Roger on July 16, 2008 at 7:48 pm

    First of all we updated this machine (3ghz Quad, 4gig RAM, OS 10.4.11, FCS 2.0) to FC 6.0.4 as well as some other updates like QT 7.5 and Remote Client. I have searched for similar errors on the cow.

    I have a sequences that is made up of other sequences for a longer project. After updating, my project was acting rather slowly and the Canvas was having a hard time keeping up with sequence. Suddenly, all stopped and a little error box popped up and said “Not Found”. I clicked. And it said “Error: Out of Memory”. Then the canvas appeared red and said that I need to refresh the window to get it to work again. I can scrub through the sequence at this stage and can see and hear my footage and edits. When I close the sequence and try to reopen it again, it can’t be opened and brings back the not found and memory error message. If I make a new sequence it handles dumping in the little sequences for about five minutes and then the errors continue and once closed the sequence is locked down with the errors. The catalyst for the onslaught of errors has been focused around transitions such as cross dissolve and dip to color.

    I’ve searched the forums and tried various techniques such as dumping render files, trashing prefs, zapping pram, media managing a whole new project to test on another computer, and changing memory parameters.

    please help and thanks in advance

    John Dinh doan replied 17 years, 1 month ago 4 Members · 3 Replies
  • 3 Replies
  • Andrea Stewart

    July 16, 2008 at 10:14 pm

    Andrew,
    Fret not. There are a few things to try to fix this problem. In my experience it happens when the project has gotten too big. How big is your project file? If it’s over 150MB it’s probably too big. Another reason can be that your drives while still having lots of space left do not have large chunks available for renders. Rule of thumb that I’ve heard around the COW is to leave 10-15% of your drive free.

    Now, to fix the situation at hand. Are you working on a program? If so, create a separate project for each act. Make a new sequence and copy and paste from your other project into the new one. Its important to copy and paste, not drag the other sequence into a new one like a nest. Do this for all of your acts. Once you have them all at their final stage. Make a new project, call it “Compiled” or some such and NOW you can place those sequences into a new one for output.

    In regard to renders. I recommend breaking them down to smaller chunks so they can find a home on your drives. If I attempt to render a whole sequence, it usually results in a crash. Remember to save after each successful render.

    Finally, I recommend cleaning your drives when your done with a project so when you start a new one you have fresh large chunks of space available.

    -Andrea

    Andrea Stewart
    Producer/Editor/Director – Owner
    Germane Creative LLC

  • Jason Lefrense

    November 26, 2008 at 5:37 am

    Hey Andrew, I have the exact same problem right now. I was wondering if you came up with a fix for it.

    Jason

  • John Dinh doan

    April 17, 2009 at 7:22 am

    I ran into this EXACT same problem when I started to nest clips within clips. It seems the tiered nesting is the root cause of all my problems.

    When I went in and deleted a nested clip (that I also through a cross dissolve onto) the problem went away.

    My workaround was to export any “nested” clips as a standalone QT movie and then bring that into the sequence I’m working on. This eliminated the sequences within a sequence tiered nesting that brought on the “Sequence not found” error and “Not Enough Memory” error message.

    Has anyone else tried this or found this to solve the problem?

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