out of memory rending problem

[David Roth weiss]

Try deleting all render files for that project using Render Manager, then try re-rendering.

David Roth Weiss
Director/Editor/Colorist
David Weiss Productions

David is a Creative COW contributing editor and a forum host of the Apple Final Cut Pro forum.

[Chris Gorman]

Thank you. I deleted all the render files. Now, as a test, I’m trying to render just one 45 sec. clip – part of the clip that has the logo bug. The progress bar is telling me it will take 2 hours.

I have a couple photoshiip files I recently imported. They are probably way too big, so I’ll decrease the psd dpi to 150 instead of 300 dpi and re-import, in case that has anything to do with this. However, I’m not even trying to render those clips now, I’m simply trying to render the logo bug. Should I take the big psd files off the TL? Any other suggestions?

Should I have re-booted. Prior to my first post on this, I had done a DiskWarrior directory defray.

PowerPC G5 DP2.3, 4GB DDR SDRAM, ATI X800XT, OSX.4.11, QT 7.5.5, FCStudio2, FCP 6.0.5 Sonnet 5 Bay SATA (RAID or JBOD as needed), ACD 23″ & Sony NTSC Monitor via Matrox v.1
Sony ZIU hdv, edit w.ProRes

[Shane Ross]

It might very well be those stills. That’s the main culprit for that error…large stills. And not DPI wise…that’s meaningless in video. it’s the dimensions that are important. Anything over 4000 pixels will cause this error. Drop the longest side to 3800, save it, and then see what happens.

Shane
Little Frog Post
Read my blog, Little Frog in High Def

[Chris Gorman]

I changed the dimensions on those clips now. I’m tried another test render of a clip that does not even involve those bigger psd files in the render request. Again, after about 20 minutes of render progress, it ended with the message “error – out of memory”.

Now, when I click on the jpg or psd files to open them in the viewer, I get a blank green screen instead of the image. This is only happening on the files where I changed the dimensions in photoshop and roundtripped back to the TL.

PowerPC G5 DP2.3, 4GB DDR SDRAM, ATI X800XT, OSX.4.11, QT 7.5.5, FCStudio2, FCP 6.0.5 Sonnet 5 Bay SATA (RAID or JBOD as needed), ACD 23″ & Sony NTSC Monitor via Matrox v.1
Sony ZIU hdv, edit w.ProRes

[Karel Voners]

Whenever I encountered that problem I would restart FCP and that would solve the issue.

You can also set in an out points on the sequence and render things out in smaller pieces on the sequence first before your export.
If you export a rendered timeline you basically stitch together all pre-rendered files so no additional rendering is needed.

It can also be corrupted media. Rendering small pieces on the sequence can help you isolate the bad clip.

The green screen you describe happens on every FCP system I have ever worked on…

K.

ps: make sure to change the render settings in the sequence settings to match the settings you need for output.

[Chris Gorman]

Thank you. This is first time I’ve encountered the green thing with fcp. I booted onto my other hard drive which is a duplicate of all the apps I have on the first one.

Now I have no green screens when working on this hard drive. (But from fcp it won’t see my external apps for some reason) Rendering time is more reasonable now – kinda like the usual slow I’d expect.

For safety, I decided to move off some of the media and old projects not related to my current project, so that I have more free space on the RAID. Early this morning I started copying over an approx. 295 GB folder. The progress bar estimated 8 hours I think. About 4 hours ago the progress indicated 124 GB to go.

But now it’s 7 hrs. and still it say 4 hours, 124 GB to go. I hope I don’t get stuck with not being able to move any unneeded media off this drive. Or…….I hope I don’t later get a message that it was not able to complete the operation because not enough memory. I’m on my way out for awhile. If I get back in 4 hours and have the same progress message, maybe I’ll have to abandon the attempt and reboot, ugh.

PowerPC G5 DP2.3, 4GB DDR SDRAM, ATI X800XT, OSX.4.11, QT 7.5.5, FCStudio2, FCP 6.0.5 Sonnet 5 Bay SATA (RAID or JBOD as needed), ACD 23″ & Sony NTSC Monitor via Matrox v.1
Sony ZIU hdv, edit w.ProRes

[John Kaley]

Make sure your FCP project isn’t larger than 100MB. If it is, delete some unused sequences and media from your project.

Other causes: mp4 or h.264 footage anywhere in you timeline. Stills in CMYK color space instead of RGB.

[Tahoe Todd]

Try deleting all unused plug-ins. I had this same issue and discovered that because I had so many plug-ins that were not being used, the entire system was slowed down substantially and I was getting the error. Deleted all the “trial” plug-ins I had installed and everything was back to normal.

[Chris Gorman]

Thank you. Things are going along ok after I decreased the psd dimensions, and later rebooted. But to avoid future problems, I checked and see that the project size is only 1.1 MB. The psds are rgb, except for the logo bug. When I read your post I discovered that the psd for the logo bug was cymk. The logo bug file size is less than 1MB, so I don’t know if the cymk would make a difference with such a small file size. I changed it to rgb to be safe.

[Erik Hatch]

I have the same problem. The photos are Jpeg and are smaller than 4000 pixels on any side. It prompts the “out of memory” when i try and render with the photos in the seq. If I remove them, it renders fine.