Error: Out of Memory…. HELP!

[John Dinh doan]

Not convinced this is the root cause, but after trashing all the preferences, restarting, etc., etc. I went back to what I was doing last before all these errors came up.

I realized that I ran into this problem when I started to nest clips within clips. It seems the tiered nesting is what caused my pains to start. When I deleted the nested clip the problem immediately went away. Coincidence? Maybe. I’m just hoping this might help someone else.

[Jesus Ali]

John Dinh Doan has hit upon something here.

I am having the exact same problem and came to this Thread after Googling my error messages.

10-Bit Footage placed in a DV NTSC Sequence, Then Nested into ANOTHER DV NTSC Sequence is causing my FCP 6.0.5 to FREAK.OUT.

I have a Sequence (Easy Setup “DV NTSC 48khz Anamorphic”), with matching DV footage inside of it.

I used Apple’s Podcast Producer program to record a screen movie of me using a website. The entire clip is 10 minutes long.
This was the solution to this hilarious thread: https://forums.creativecow.net/readpost/150/859889

Podcast Producer saved the clip as MPEG-4, with only 10 frames per second, but it looked great.

I put the clip into Compressor and converted it to Apple ProRes 422 (HQ), because I thought (probably wrongly) that the Animation codec would give me problems in FCP.

I wanted to resize and crop only a window of my screen capture, so I put the footage into a new Sequence, resized and cropped it, and then put a Color Matte behind the footage which matched the grey I used as my desktop color during the capture.

That way, the cropped and resized (and off center) grey desktop and browser window weren’t just plopped on a black FCP background.

So then, I took the Sequence (consisting of 10-bit pro res screen cap and color matte slug behind) and Nested it into my main Edit Sequence.

Then I started chopping up the Nested screen cap sequence.

Things were fine for a day, then today, I double-clicked the Nested Sequence, double checked some Motion Numbers, then tried to jump back to my main Edit Sequence.

But NO DICE.

FCP hung and waited, and eventually said “Error: Not Found”.

Then I double clicked the Edit Sequence again, and FCP said: “Error: Out of Memory”

So I think the problem is as I stated, the allignment of:

10-bit footage
placed into a DV (or 8-bit?) Sequence, which
is Nested into another DV (or 8-bit?) Sequence.

an additional element MAY be,
DISPLAY AUDIO WAVEFORMS
is turned ON.

Perhaps when FCP tries to display waveforms for the main sequence, but then sees the ones pulled in from the Nested Sequence, it can’t handle it?

Hmmm… I think instead, there is probably some Memory Leak occurring caused by Nesting 10-bit footage.

Right now I am using Compressor to Convert the original Pro Res HQ to standard ProRes, Animation and Uncompressed 8-bit. On Monday we’ll see how those do.

btw, I AM periodically able to open the main timeline again. About 1/10 times I double click it. Usually, after I do something with Rendering in the 10-bit timeline, then double click back the parent timeline, it finally opened.

I quickly selected All, copied all the clips and edits, and made a new FCP Project and pasted them into a new DV Sequence. Saved that Sequence and CLOSED IT.

Then I came back, deleted the 10-bit nested clips from the parent Sequence, then also copied all those Clips and Edits out to a new FCP project.

Copying just the parent Sequence to a new project DID NOT work. It would generate the same errors.

Phew! Sorry this is so long, but maybe it will help somebody in the future! It should have all the Keywords I searched for!

Thanks, Jesus

[Frank Axelsen]

It´s probably a few years to late to make a surgestion, to this problem. (and I have´nt read the whole thread, so the this might be a repertition) But if your working with stills, make sure, they are about the same size as your project. I´m working with a 1920×1080, so I made the image width 1920pixels in photoshop. Before I did that, I could´nt render it, and got the same out of memory message. But now it´s running fine. (sorry for any misspells, I´m Danish:)

[Philip Courter]

I am running FCP studio 6 on an 8 core Mac Pro with 6 Gigs of memory. Only one of several sequences refuses to render any video whether “preview” or “needs Render.” This sequence also cannot be exported with current settings. Other sequences continue to render as necessary. All sequences are Apple Pro Res 4:2:2 HD 1080i. WTF?

[Walter Biscardi]

Could very well be a corruption in that timeline somewhere.

First thing I would do is create a New Timeline

Now Copy everything from that problem Timeline and Paste it into the New Timeline.

Can you render now in the New Timeline?

If not, remove any graphics from that timeline. Can you Render now?

If not, now create a New Project.

Create a New Timeline in that Project.

Again, Copy and Paste from the original timeline to the new timeline in that New Project.

Can you Render now?

If not, I would go back to that original timeline and figure out what might be corrupted in it.

Walter Biscardi, Jr.
Editor, Colorist, Director, Writer, Consultant, Author.
Credits include multiple Emmy, Telly, Aurora and Peabody Awards.
Owner, Biscardi Creative Media featuring HD Post
Biscardi Creative Media

Creative Cow Forum Host:
Apple Final Cut Pro, Apple Motion, Apple Color, AJA Kona, Business & Marketing, Maxx Digital.

Read my Blog!

Twitter!

[Philip Courter]

This sounds like good advice. The specific scenes that refuse to render are stills (probably JPEG). Will do as you advise tomorrow. Many thanks, Phil

[Philip Courter]

Based on reading several posts, I opened the non-rendering original files (photos) in Photoshop, re-sized them (one was particularly huge) re-saved them with new names, re-imported them into FC and replaced the clips in the timeline. They rendered normally, but when I tried to output the file (to make a master for the DVD) FCP “quit unexpectedly.” So I did a system re-boot, opened FCP, created a new timeline, and copied and pasted the contents from the old to the new. It worked.

[Josh Smith]

I just upgraded to FCP 7 on a new system and got this same message. It turns out my problem was that one of my pictures was 8000 x 4000 at 600dpi. I reduced the image to 72 dpi and reduced the size to 4000 x 2000 (for motion effects) and it rendered fine.

In order to troubleshoot it, it had to render each picture one at a time to find out which one was causing the problem. Then I just revealed it in finder and changed it in photoshop.

In case this helps anyone.

Josh Smith
Bryan, TX

[Sam Griffiths]

If you have not already, please check to see if you are using any nested sequences. If you are, make sure each of those nested sequences have been prerendered in their own timeline and then go to your main sequence and try rendering.

I ran into the issue that final cut would stall and prompt me with “Error: Out of Memory” whenever a nested sequence had not been rendered before the main sequence attempted to render the nested sequence in the timeline.

[Vince Vilan]

“I just upgraded to FCP 7 on a new system and got this same message. It turns out my problem was that one of my pictures was 8000 x 4000 at 600dpi. I reduced the image to 72 dpi and reduced the size to 4000 x 2000 (for motion effects) and it rendered fine.”

Almost the same thing here but not quite the same thing my friend and I did. What happened was that the picture which was a jpeg became corrupted after a while for some unknown reason. We tried to render the whole sequence but it would always stop at the same percentage. So, my friend rendered it in pieces and finally found the culprit which was the picture. We merely had to delete it and redo the adjustments we did and it rendered magnificently. No more problems.

We found our leads through Google and found our way to Creative Cow. We are grateful and want to save major heartaches due to this Error Message and are posting this. Thanks you guys. This is my first post.