FCP - Error: Out of Memory at 18 gig ram

[Timm Hogerzeil]

I am using FCP 7 all was fine the last days but now I get this message ... Error: Out of Memory
The box has 18 Gig in ram and is an 8 core powermac - so there should be no problem. i read in a threat it could be because of the red codec.
I am editing red_F quicktimes.

Anybody had this problem before or has a solution?


Thanks

 

[Simon Blackledge]

Your mac isn't out of memory. But FCP is by the sounds of it.

F proxies are Full rez. So what rez did you shoot ? 4k ? 4kHD 3K?

s

 

[Patrick Britton]

I got this error a lot bringing in 2K credit scroll files from photoshop, and my machine was only showing 2.5 gigs usage of ram for FCP on a 12gig Nehalam Mac Pro. It seems that FCP is hard coded to only see that amount of ram.

I guess we'll have to wait for a native 64bit version of FCP to address more memory.

 

[Sidney L. Plaut]

Ive encountered this problem many times over the years... rendering - you can see in the "activity monitor" utility, under system memory, that ram goes from "free" to inactive- when it runs out FCP crashes. It has nothing to do with RED files. and it seems to be periodic - like after some updates.... not sure though. tried it on G4,G5 mac pro - (though not on my Nehalem.. yet)

never found a real fix for it - but once copied a sequence over to a new project to render - as original project had many sequences and clips.... did the trick for a while.

 

[Daniel García]

FCP is a 32 bit app sir.
It needs a full rewrite to migrate to 64bit.

 

[Kaku Ito]

Like many mentioned here, FCP can only use 4GB of RAM at this point until it becomes 64-bit app.. I was surprised that Adobe person mentioned that AE CS4 and PP CS4 use 64-bit memory space even with current version.

Also, I get this out of memory caution when working on the long title like Patrick mentioned and that is more likely to happen when you have the source and the timeline coded or aspect ration that is unmatched (so requires rendering).

 

[John Reynolds]

Ive encountered this problem many times over the years... rendering - you can see in the "activity monitor" utility, under system memory, that ram goes from "free" to inactive- when it runs out FCP crashes. It has nothing to do with RED files. and it seems to be periodic - like after some updates.... not sure though. tried it on G4,G5 mac pro - (though not on my Nehalem.. yet)

never found a real fix for it - but once copied a sequence over to a new project to render - as original project had many sequences and clips.... did the trick for a while.

I tried the cut and paste trick and it seemed to work. Thanks for the tip.

This is an old thread has anyone any new information about this issue?

 

[Gunleik Groven]

Many weird things can lead to this...

If you have tried to conform a multiclip sequence, the trace of only one clip in a long sequence with hundreds of cuts will give you this...

 

[Henk van den Doel]

Encountered the same problems a few times (only on tight deadlines of course), and I think it always had to do with having too many projects running at the same time. Or too many big sequences being open in projects.

 

[Jon Carr]

I found, closing other sequences and some times just saving the project before you render stops it from happening. But then again, FCP.....

 

[Oliver Peters]

One workaround is to close all sequences and close and relaunch FCP. Then highlight the sequence in the FCP browser and use the pulldown Sequence-Render menu.

- Oliver

 

[Johnny Friday]

Also, Digital Rebellion has a very nice FREE APP....to clear your cashe and any junk that may be plugging up FCP. I use this at least ONCE a week to clear cashe and start fresh...but i first save my preferences...clear cashe and then recover my preferences....all simple to do with the free app. Or in my case i just paid for it and utilize it on my dekstop when needed.

 

[Matthew Riggieri]

So many issues can cause this. Corrupt Clips, too many sequences open, too many projects open, or just sometimes it can't be explained. For the unexplainable, reset your PRAM

Cheers
Matt riggieri