Out of Memory Error… FCP 7… project too large?

[Ville Tanttu]

hello

Try This: to change 64 bit to 32 bit.
FCP is 32 app, so all these kind of super random bugs seem to appear with new systems…
This really improved performance in my system – and the same kind of problem as u have disappeared- with similar Mac setup.

I hope this cures it:

all the best

Ville

To temporarily switch the kernel:
On bootup, hold down the “3” and “2” keys to switch to the 32-bit kernel. The system will continue run in this mode until the system is rebooted, reverting back to 64-bit kernel. Inversely, holding down the “6” and “4” keys upon bootup will force the 64-bit kernel to load.

“To persistently toggle your Mac Pro to the 32-bit kernel follow the steps below.
NOTE: These scripts toggle the nvram, and the changes require authentication. You must have a password on your system, blank passwords will not be accepted.

To switch to the 32 bit kernel, download and unzip the attached file and run the switchto32bit.command file.
To switch back to the 64 bit kernel, run the switchto64bit.command file, also included in the attached zip file.”

https://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=375771

[Joe Hackett]

Jerry,
I just deleted my Sequences folder on a feature I am outputting and I can not believe how much smaller it made the project file!
Thanks. I too was getting the out of memory message. I hope this helps

Joe Hackett

Joe Hackett

[Glenn Camhi]

[Jerry Hofmann] “Having open sequences that contain a lot of edits can bring your computer to it’s knees. The more sequences you keep the worse this gets too.

[…]

One thing you shouldn’t do is keep copy upon copy of your sequences. Backup your project files instead. Having a lot of clips usually isn’t what makes the project file so large, it’s piles of sequences, […]”

Thank you for this, Jerry. You just solved a vexing problem. Closed all the open sequences, and finally rendering a complex project without a hitch.

[Carol Phiniotis]

I just wanted to share that this thread helped me solve a major headache. I was getting the same Out of Memory error from FCP 7 and couldn’t render. I tried flattening my photoshop images, but that didn’t work. I tried removing my photoshop images, that didn’t work. But when I removed the right .jpg, my problem was solved. It was all due to one image that FCP really didn’t like. I checked the image and it was RGB, but it was also huge at 7200×7200. I resized it to 1800×1800, dropped it back in FCP and it rendered. Thanks.

[David Roth weiss]

[Carol Phiniotis] ” It was all due to one image that FCP really didn’t like. I checked the image and it was RGB, but it was also huge at 7200×7200. I resized it to 1800×1800, dropped it back in FCP and it rendered. “

FCP currently has a maximum pixel dimension that cannot exceed 4000 pixels wide, which is essentially a 4K image. So, that’s why that issue arose. Now you know, whenever importing images or video part of your job as the editor is to check every file before you import it.

Here in Los Angeles, a simple miscue like that could conceivably ruin a career, because it could throw off an entire post-production schedule and thus cause a missed release date.

David Roth Weiss
Director/Editor/Colorist
David Weiss Productions, Inc.
Los Angeles
https://www.drwfilms.com

POST-PRODUCTION WITHOUT THE USUAL INSANITY ™

Creative COW contributing editor and a forum host of the Business & Marketing and Apple Final Cut Pro forums.

[John Hadwin]

Well, you heard it here first. The inadequacies of Final Cut Pro can easily get you fired in L.A.

Why we haven’t fired Final Cut for their software’s amazing ability to replace productivity with completely useless error messages (with no solution but to hit okay and pray for different results) is beyond me. The software is supposed to bend around my project; I shouldn’t have to bend my art-form around their software. It’s plain and simple! My computer is a beast and memory WILL NEVER be an issue. But I get this Out of Memory Error instead of an error that tells me all the speculative things I have to come here and find out. All of the people here simply want to know what final cut has a problem with now! Why is FCP holding my project hostage this time!?

The answer to the customers’ problem is never, “We’re working on a solution to that.” It’s, “Well, good luck with that. Maybe you can figure out an annoying work-around that still doesn’t actually accomplish what you’re envisioning. I’m sure there’s some way you can change your proven workflow to accommodate our software engineering problems.” Apple is taking advantage of my loyalty as a customer and has no loyalty to customers who encounter problems with their products. Their solution is to get more desirable customers, with more conventional non-complicated edits. Fine! The first chance I get, I’m taking my business where my productivity won’t be a daily crap shoot and my education always insufficient.

I simply cannot afford to continue begging Apple to do common sense things! Like (1) taking everyday SLR images of any size and working with them in an HD project without freaking out, (2) using audio that isn’t originally 48 freakin’ kHz and not screwing it up, (3) supporting me on something other than iTunes Sales until my expensive post production problem has been solved, (4) actually responding to the MANY complaints of thousands of potential Avid Media Composer customers (5) giving me assurances that when I upgrade to FCPX these problems will actually be solved (6) producing accurate error messages that mean something when I screw something up.

Or start by fixing 3-4 version old problems like jittery, embarrassing movement with keyframing FCP’s motion tab’s position property if using anything but even integers (odd and floating point numbers cause the problem). Fix it! How about checking my activity monitor to see that CompressorJobController and CompressorTranscoder aren’t responding and I can’t even type this stinking post in real time because of them. Go ahead and reformat your machine with a fresh install and you’ll find the problem repeats itself with no word or fix from Apple. But guess what! 2 years later, “You can now buy Final Cut 10! This time, if you buy it, we promise we’ll support the problems you’re having until they’re fixed!”

I can’t imagine staking my career on a complete new build with all the unforeseen problems on top of all the problems Apple doesn’t care I’m having on any previous version, RIGHT NOW! No pro will switch any time soon for that reason. So while all the amateurs are screaming “it’s awesome, there’s no problem here”, with their simple little iMovie type projects for the car dealer in town, when we switch we would still be the first to test it with our “weird” and complex projects and find out our needs still aren’t met. Perhaps the new price is achieved by all the money saved from not supporting previous versions. If I’m going to have to learn a new build, why not learn the competitor’s build, whoever has real customer service!

If I gave such poor responses to my customers, they would certainly fire me; especially with my competitor right down the road! But to do business with Apple, by continuing with FCP, I will have to make up for their lack of response to their customer (me) and my customers too.

Screw this! I’ll buy my iTunes from Apple, but I’m done buying problems for my post workflow. I want solutions that allow me to be artistic, not a technical Unix wizard. I want something that allows me to take control of my vision and my art comes out the other end; not some goofy hybrid squeezed through the FCP play-doh art factory.

Very sincerely,

John Hadwin

[Diana Cadavid]

Can’t agree more.

[Nacho Barros]

Hi all.
I have read this forum and still the problems remain.
I’m working on a Mac Pro Quad-Core Intel Xeon 2.8 GHz and 12 GB of Ram
Although it is well that the machine is not top of the line I think is not a bad computer.
I’m working on a project that meets a variety of formats, the main material recorded with Cannon D7, my sequence is set will the Apple Pro Ress ….. 23.98 fps 1920×1080 HQ
The sequence is 70 min, I have divided the sequence into smaller sequences of 7 min or so to avoid having too many cuts, however, and once I unified the formats that are not Apple Pro Res to this … that is the h-264, DV, MP4 etc. and also decrease the size of the photos ….. 1800P is sending me the damn error.
I lost too much time trying to find a logical way that allows me to work and give my client work and also agreed time I run out of solutions.
I read that duplicate sequences is not good, you do not know, but each sequence is a sequence dieferente finally to rest and do it that way to optimize my work … but I still have the error.
By now I can not know what else to do to fix the problem ….
I hope I can make a contribution because they do not know what else to do.
I think I have done t
If there are problems with writing is because I am from Chile and management to improve your English.

[Arbel Vaknin]

Hi, after remaining with only one sequence in the file, and now it weights less then 9 MB I finally realized that text even though created in final cut, was the only reason I couldn’t render my sequence made of RED materials.
and I have a very nice machine, but also not the state of the art.

[Aashish (ash) Shah]

Hi Chris Pelser,

I am having exact same problem as you mentioned in your post, and I’m following your advice and doing how you suggested, but I didn’t understand the photograph part, I’m working on a Documentary so I have a lot of jpeg photos and lot of texts, Do I need to convert my jpegs?

Thanks,
– Ash