-
“Out of Memory” message when rendering.
Hello!
It’s my first time working with 4k footage (shot on a Red One) and I’m having some trouble rendering.
I only have 3 stills, one quicktime proxy clip and some transitions on my timeline yet I can’t render without “Out of memory” coming up. However, I have 10GB of memory and the stills are all in RGB color space.
One of the stills was created from a proxy clip. Does that still need special formatting perhaps?
I’ve edited many projects before without ever having this problem, but none of them used Red One footage…
I work on FCP 6.0.5 on a Mac Pro using OS X 10.5.6.
I know little about troubleshooting computer hardware or how it relates to FCP so I’d really appreciate any ideas or help you can give me! Thanks!
-
10 Replies
-
Hi
here is an article published by apple in regards to Ram and Final cut I hope it is of some use to you
https://support.apple.com/kb/TS1957Life Begins at 155mph
Catch it edit it View it
3am Studios llc.
3amstudios.org
Sharedsummitsfever.com -
I recently worked on a 1080 video that had multiple 4K and larger stills. I’d get the memory error too. Try rebooting and closing every sequence except the one you’re rending.
FYI, FCP can’t use more than 2.5GB of RAM. It’s limited by old code.
-
Unbelievable, and after many hours on the phone with fcp support, it turns out that ProRes 422 (HQ) has problems with jpeg files. I transfered all the stills to tiff and now everything works perfectly. How bizarre!
-
Sorry to say, the problem ended up being only delayed. The tiff files are smaller so the “out of memory” message has come up again as the filters or transitions added up on my project. Any ideas?
-
Hi – did you ever figure this out? I have been having the same problems – getting the “out of memory” message when trying to render even simple sequences (3 layers) no stills. I have the same set up as you 10G ram in a MacPro and working in ProRes HD.
Thanks. -
FCP support???????????????? who is that? I thought Creative cow WAS FCP support, lol.
Broadway Video, NYC
AVID/FCP editor/engineer -
Hello!
Nope, sadly I never did fix it… I may have understood it though.
I removed the stills and since then it has rendered normally. At first, I simply downres-ed the stills but that just delayed the message popping up. I guess that smae as the stills, the 3 layers may be too much for fcp to handle as it can only use 2.5 GB max. They’d better hurry up and improve on that cos it’s damn unpractical!!
Good luck… Please let me know if you do fix it…
-
Same problem here… Makes me feel like Im working on a PowerMac 9600 AVID, not a 8-core mega giga flippity flop computer..
UGHHHH Its things like this that really go “Really??” I guess Im wondering outloud, again, like so many other people, what the long term plans if any for the “PRO” apps..
-
Not sure if this will help anybody now, but I had the same problem with rendering stills which lead me to this post. Try working in DVCPRO HD instead of Apple Pro Res. I noticed that everyone having the problem seemed to be using pro res (as I was), so I copied my work into a DVCPRO HD sequence and rendered all of my stills with no problem. I’ve worked on a few shows that started out using Apple Pro Res and changed to DVCPRO HD mid-stream. I think the show I’m working on now is going to do the same beginning with the next episode.
-
Not sure if this will help anybody now, but I had the same problem with rendering stills which lead me to this post. Try working in DVCPRO HD instead of Apple Pro Res. I noticed that everyone having the problem seemed to be using pro res (as I was), so I copied my work into a DVCPRO HD sequence and rendered all of my stills with no problem. I’ve worked on a few shows that started out using Apple Pro Res and changed to DVCPRO HD mid-stream. I think the show I’m working on now is going to do the same beginning with the next episode.
Reply to this Discussion! Login or Sign Up