OUT OF MEMORY ERROR

RottenDot, Tom, Steve,

What was the outcome of your issue? I am in the middle of a big job for corporate and sitting here dealing with the exact same issue. It's 11:40pm Friday night - New Year's weekend. This project has been giving me problems that I've not seen before.

I'm on a 3GHz Dual Quad core with 4GB of 667MHz DDR2 and all my Apple ProRes (LT) files are on a 16TB SAS RAID (hardware controller card) built by DAT Optics. I realize many of you may laugh at 4GB of RAM, but in Activity Monitor I normally don't tap half of it - little decompressing going on and the speed of my RAID is... well it's rippin' fast. Only when I create lower thirds in Motion do I ever see a bit more of the RAM tapped.

On this project I have gotten the "Out of Memory" multiple times. A rend seems to be that the more I try to render, the less RAM I have to work with until I re-boot and then I'm back to nromal for a while. Also I went to repair permissions in Disk Utility on my OSX drive and there are always a long list of repairs needed, and after the repair is complete, everything seems normal for a period and it begins all over.

I am editing in a 1080p30 (29.97) Apple ProRes (LT) sequence and all my files are the same. What is going on? Please let me know what you found out! -Stephen

It's a total pain, I have the same problem. Sometimes I can turn off external monitoring, I have a matrix mini. And that will solve it. A new time line worked once. Re-booting use to work that seems to have stopped too. Another solution that has seems to have ceased working is jus t rendering smaller portions of the timeline.

I sometimes will export footage that his being blown up or color corrected, then add the text. And I stack these things i the timeline so when it's time for sending to the real CC suite, I can just blow away those upper tracks. Imean thee are deadlines to be met, this stuff needs to be viewable to edit. I call the pre-renders.

So more and more I having to do these round trips with fcp, so sometime I just send the footage to motion and do part of it there. You then need to bring in the QuickTime, because this problem will happen with th motion files I the timeline A Lot.

I cut feature films, and my projects are big and complex I cant start going through them and taking out stuff. Kinda defeats everything I do.

As near as I can tell it does seem to happen on bigger more complex projects. I keep them below 65 Meg's my projects. Old timelines have to go into a timeline archive project.

This is obviously not a problem with ram or hd memory, it's video card memory. My Mac pro has the smaller video card. And I think one of the updates just has a flaw in its driver for the card, and it isn't flushing video memory or something or it has a memory leak, or it has some memory reserve for iTunes. This is just another reason why I'm transitioning to Avid. Where this problem does not exist.

This was a really helpful post! AnyMountain - I remember when we upgraded to the Radeon 5770 I thought I was having longer renders. I mentioned it to my manager, but it didn't make sense. The card is the same one my own 2.8GHz Mac Pro shipped with - 2010 and even though it's a single Quad Core - it really seems to run faster - but I have 8GB of RAM vs 4GB at work. Regardless, I feel like the Dual Quad at work ran faster before we installed the 5770. If you're right about the possibility that the video card isn't flushing memory - it would really explain what I'm experiencing.

I had nested sequence each containing segments of these interviews. They are sometimes revised or swapped out in order so it made sense to make each section it's own sequence. Those are nested into the main sequence and in that sequence there are some graphics that include a title depicting the next segment and at the end of the main sequence there are credits and a blooper or two. It's fairly straight forward - not as complex as your work. Inside my nested sequences there are very simple lower thirds I made in Motion, as well as a short png "bug" that represents which mountain they are from. I realize a png can be tricky, but I created them in ai and they're made within the HD size with acceptable shrienking in the motion tab - nothing extensive. Further, it was decided that the resort "bug" leaves with the persons lower third, so basically the png file is a single file per person that is up and out within a few seconds.

What did you do to resolve your issue? Are you just dealing with it like I am? I basically worked through carefully getting each sequence rendered one at a time (with multiple re-boots and permission repairs) and was eventually able to render the main sequence, and then export it.

https://discussions.apple.com/thread/2802272?answerId=13329973022#13329973022

The above thread is also about this subject, and thre is a conclusion that is the result of corrupt renders. And that a tool from digital rebellion can help with it.

I'm not sure I buy it, but the rebellion software has a demo period so it is worth a try. Similarly a user on that thread describes the same work-around of turning off external monitoring, and also the use of some particular filters. My problems certainly involve the use of filters, but if not for filters we wouldn't be rendering.

I'm so sick of dealing with it that right now I just re-do each bit in motion, as they become a problem. And I spend my spare time training on AVID.