-
FCP project size and system crashes
At 9.9MB in size, I just had a huge FCP project crash. No matter what I try, I can’t get the project to boot up again. It get’s most of the way there and then crashes again. Even the backup files are corrupt and useless. Has anyone else reached a limit on project size, or is it even the project size that’s the problem? My system consists of a G5 with 2.5Ghz dual processor, 4G of RAM along with a full compliment of RAID/XServe drives totaling 2.7TBs of space. Why this amount of computing power can’t deal with a comparatively tiny 9.9MB project file is frustrating to say the least. In fact, my system has been nothing but trouble since I bought it. It not only crashes at will rather often, but digitized media files not even presently in use will randomly disappear from the hard drives without a trace. I’ve had qualified pros take a look, but they keep telling me that everything’s operating normally! That said, my obvious question is has anyone else experienced similar problems with a similar FCP setup?
Mark LoPresti, Buffalo New York
-
7 Replies
-
Post which versions of FCP, QT, and OS you are running. If you upgraded to Tiger, post how you did it… if you just ran “upgrade” you are in for a lot of problems… I’ve worked with 30MB files… no problem, just sort of long to save… lol…
Jerry
Apple Certified Trainer
Author: “Jerry Hofmann on Final Cut Pro 4” Click here
Dual 2 gig G5, AJA Kona SD, AJA Kona 2, Huge Systems Array UL3D
-
Try reading the manual (Chapter 7 – Overview of the Media Manager). It’s a good place to start.
-
Why do you keep saying that on completely unrelated topics? And what does that have to do with pilot error?
-
Check out the following article for some tips on how to resurrect the project (assuming you’ve already tried the most recent autosaved file).
https://www.kenstone.net/fcp_homepage/restore_corrupted_project.html
Your project file size is not too large, but it’s wise to keep an eye on it and if necessary, break the project down accordingly. A piece of advice from the late, much-lamented Ralph Fairweather which has kept me free from such problems since FCP 1.2
-
[Bob Roberts] ”
Try reading the manual (Chapter 7 – Overview of the Media Manager). It’s a good place to start.”The Media Manager has nothing to do with this issue. It’s more of a corruption issue with the project.
Walter Biscardi, Jr.
Creative Genius, Biscardi Creative Media
https://www.biscardicreative.comNow in Production, “The Rough Cut,” https://www.theroughcutmovie.com
Now editing “Good Eats” in HD for the Food Network
“I reject your reality and substitute my own!” – Adam Savage, Mythbusters
-
mark,
It’s not the project size that causing you problems. On a daily basis we’re dealing with projects in the 100- 170MB range. At that size you have very slow opening (10 minutes), and if you try to keep open several projects of that size you’re flirting with a crash. However, at your size (below 10mb) there must be something else going on. A corrupt sequence? Bad media? It’s something else.
You say the back up files are also corrupt. How far back? Auto save or “Save as” back ups? What did you add to the project before you experience these crashes? Have you tried opening the project “off-line”? Not connected to your drives? Trouble shooting isn’t fun, but I think your problem is in your media or sequence.
Good luck.
Mark
-
[Jerry Hofmann] “Post which versions of FCP, QT, and OS you are running. If you upgraded to Tiger, post how you did it… if you just ran “upgrade” you are in for a lot of problems… I’ve worked with 30MB files… no problem, just sort of long to save… lol…”
I’m presently running OSX version 10.3.9 along with FCP HD 4.5 and QT version 7.0.1. This is actually the second crash I’ve had after reaching the 10MB level. It’s been suggested that the project size isn’t the problem. With the other problem I’ve been having (digitized footage randomly disappearing from the drives without a trace) I have to agree.
Mark LoPresti, Buffalo New York
Reply to this Discussion! Login or Sign Up