Project Too Large?

[Shane Ross]

How does FCP crash? Any sort of error?

Try trashing prefs, then launching.

Shane

GETTING ORGANIZED WITH FINAL CUT PRO DVD…don’t miss it.
Read my blog, Little Frog in High Def

[Martin Nelson]

“How does FCP crash? Any sort of error?”

If media is online then at the end of reading the project it just crashes out without a message. Crash Analyzer from FCS Maintenance Pack first said:

“This crash appears to have been caused by an issue with your graphics card or graphics drivers. A common cause of issues is running Final Cut Studio on an underpowered graphics card.”

I’ve just installed the ATI Radeon HD 4870 and ran software updater. And I can run much earlier versions of this project from Autosave.

The next crash gave me this message from Crash Analyzer:

“This crash was caused when trying to draw or interact with a user interface element. A common cause for this crash is a corrupt or outdated version of the ProKit or BrowserKit frameworks, but in some cases it may be a Final Cut Pro bug that should be reported to Apple. Users sometimes get this error if they upgrade their OS without reinstalling Final Cut Studio or if their HIToolbox preferences are corrupt.”

This is a fresh install of OS 10.5.8 with updates run and then a fresh install of FCP with updates run.

“Try trashing prefs, then launching.”

I did, Shane. In fact, immediately before launching I went to the Privacy tab under Spotlight in the System settings and blocked out all the media drives, I then ran Disk Warrior (all in pretty good shape, but rebuilt any directory 7% or worse out), Disk Utility (no problems found, permissions repaired), Compressor Repair, FCS Housekeeper and Preference Manager. These last two pretty much trash all the preferences. I then restarted computer, took all media drives offline and only then launched the app. That’s when I got the “unreadable or may be too new…” message.

Martin

2 x 2.26 Ghz Quad-Core Intel Xeon
12 GB RAM
OS 10.5.8
ATI Radeon HD 4870
FCP 7.0.2
Quicktime 7.6.6
Avid Media Composer 4.0.2.20

[Jon Chappell]

Have you tried Project Repair?

My software:
FCS Maintenance Pack – Tools to keep Final Cut Studio running smoothly and fix problems when they arise
FCP Versioner – Backs up Final Cut Pro projects to XML and creates changelists for each revision
More tools…

[Martin Nelson]

Absolutely, Jon. You know I turn to your stuff first. It quickly said the project was repaired, but that didn’t end up changing any results.

Martin

2 x 2.26 Ghz Quad-Core Intel Xeon
12 GB RAM
OS 10.5.8
ATI Radeon HD 4870
FCP 7.0.2
Quicktime 7.6.6
Avid Media Composer 4.0.2.20

[Jon Chappell]

If you get the “Project is unreadable or too new” message, it’s for one of three reasons:

1. It is too new for the current version of FCP.
2. It is corrupt.
3. The metadata is invalid (which Project Repair fixes).

I’m guessing it’s corrupt then.

My software:
FCS Maintenance Pack – Tools to keep Final Cut Studio running smoothly and fix problems when they arise
FCP Versioner – Backs up Final Cut Pro projects to XML and creates changelists for each revision
More tools…

[Martin Nelson]

“I’m guessing it’s corrupt then.”

Well, that was my guess too, Jon. So I went looking through my Autosave folder, I found all of them refused to open as well. I do happen to have an old Autosave folder on a different startup disk and I can get those considerably older and considerably smaller projects to open just fine (by “just fine” I mean I can get them to open with the media offline; I haven’t taken them to the next step yet).

BTW, I just tried to open the project on a different earlier startup disk. It crashed and Crash Analyzer gave me the following. I haven’t seen this message on the new startup disk, but did get it occasionally when I was still running off of this earlier one:

Suspected Cause:
This crash appears to have been caused by Quartz Composer. Such crashes are most often caused by corrupt media or graphics card issues.

Martin

2 x 2.26 Ghz Quad-Core Intel Xeon
12 GB RAM
OS 10.5.8
ATI Radeon HD 4870
FCP 7.0.2
Quicktime 7.6.6
Avid Media Composer 4.0.2.20

[Jon Chappell]

If you get vastly different causes for each crash, that is generally an indicator of much greater problems on your system. It’s difficult to say what those might be though. Have you tried opening them on a different computer?

My software:
FCS Maintenance Pack – Tools to keep Final Cut Studio running smoothly and fix problems when they arise
FCP Versioner – Backs up Final Cut Pro projects to XML and creates changelists for each revision
More tools…

[Martin Nelson]

“If you get vastly different causes for each crash, that is generally an indicator of much greater problems on your system.”

My thinking too and I’ve been trying to isolate that problem. I believe you’ve read my novel: https://forums.creativecow.net/thread/8/1087193
Crash Analyzer typically calls for “Graphics Card / Driver Issue” or “Corrupt / Unsupported Media.” I recently installed the ATI Radeon HD 4870 card and ran software updates hoping that would fix something in response to the first message. In response to the second, I did have a lot of unsupported files when I inherited this project. I attempted to eliminate them all several months ago, but I may have missed a few.

But why does it bail on me now? If I could just get it to launch I could migrate over a small part of the project to a new project and perhaps carry on.

Martin

2 x 2.26 Ghz Quad-Core Intel Xeon
12 GB RAM
OS 10.5.8
ATI Radeon HD 4870
FCP 7.0.2
Quicktime 7.6.6
Avid Media Composer 4.0.2.20

[Bj Ahlen]

A graphics card problem can definitely cause these symptoms.

Do you still have your old card?

Can you borrow someone else’s card?