FCP Quits Cannot Figure it out Need Help . . . Please

[Shane Ross]

Let’s do this the old fashioned way. The way we used to test OS9 and earlier when the computer would freeze on startup.

Take all the plugins out of the plugins folder. Now launch FCP. If it loads, quit, add 5 plugins, open again (do this aplhabetically so you know where you left off). And again and again until it quits. When it quits, you know it was one of the last 5 plugins you loaded, so take them out and load them one at a time until the program fails to load, then you know your culprit.

This happened to me not too long ago…

Shane Ross
Alokut Productions
http://www.lfhd.net

[Cowcowboogie]

Exactly the same thing happened to me today. I was able to restore with FCP rescue, though. Could Apple have sent some sort of update in the last 24 hours that’s causing problems?

[David]

Shane,

Thank you for the quick reply. Unfortunately, even removing all the video plugins does not seem to fix the problem. In fact, when I put them back, it seems to get past the video plugins and falters at the audio plugins. Not sure if that’s right but the last thing I see begore it quits is audio something or other. Strange thing is is that it gets to the very end of the initialization and just when you’d expect it to give you the empty project, it quits. I wonder what the very last step of the initialization is?

Again. I reloaded the software back to 5.0 off the discs. . . . . ahhh I have an idea. This fcp install was originally upgraded identically in two suites. Obviously this gave us problems which we resolved by purchasing another copy of FCP. So what I did was toss the registration plist (or some such) and put in the new registration number. I wonder if it could be shutting itself down because it thinks the serial number is not valid. Although mybe not since its been working fine on this number for months.

Rats.

David

[Steve Eisen]

Try opening a different project. Most likely it is a corrupt media file in the project you are opening.

Steve Eisen
Eisen Video Productions
Director-At-Large
Chicago Final Cut Pro Users Group

[Boco007]

Hi Steve, I am having the same problem when I try and mixdown. The application quits over and over each time I try. How would I go about finding and fixing this? I am rather a novice so if you could step by step me I would REALLY appreciate this. I have spent days trying to geta disk burned.

[Rogelio Cordovez]

I had the same problem, all last week…exactly the same…for some reason the RAM that had be working perfectly up to know, when doing the Harware Test (disc that came with my G5 pkg) the ram was defective. I had to take out the RAM, re-install FCP, now I’m running FCP 5.0.4 with no problems (knock on wood).

I have a G5 dual 2.0 (had 5 gigs of RAM) now 3 gigs of RAM. The good news Kingston has a lifetime warranty on that RAM.

Hope this helps,

Rogelio

[Boco007]

I will do. Did you replace the old RAM with new RAM or just uninstall and reinstall? Thanks for the help, this has been driving me crazy!

[Miska Draskoczy]

Did you ever figure out what the problem was? I’m having the exact same issue with final cut pro. In my case it was because I upgraded from quicktime 7.0.4 to 7.1.1 and now final cut quits as its loading its plugins, also seems to be on the audio plugs.

There is apparently no way to downgrade quicktime, at least not 7.1.1 to 7.0.4. I’d like to avoid reinstalling the whole machine from scratch if possible. I tried upgrading to FCP 5.1.1 but that didn’t help either.

thanks
-z