Can't Work on Project - CRASH

Hello-

Right now I cannot open FCPX. I've been working on a 15 minute project with a moderate amount of effects.

Tried to edit today, and after opening, quits after trying to render.

Ran Pro Maintinance Tools which generated this crash report:

Effects Rendering

This crash appears to have occurred while trying to render effects on a clip. Possible causes for this include corrupt or unsupported media, a bad filter, a graphics card issue or too many filters applied to a single clip.

Suggested Actions

Use Corrupt Clip Finder to check for corrupt media.
If you are editing with long GOP media (H.264, HDV, MPEG-2, XDCAM, WMV, etc), consider letting Final Cut Pro X transcode them to ProRes for better performance.
Consolidate filters where possible. For instance, if you have multiple color corrections on a single clip, try to achieve the same colors with just one filter.
Remove third party filters from clips, or use Plugin Manager to disable them completely.
Make sure you are running the latest version of OS X.

--------------
Relevant Line
0 com.apple.Flexo 0x0000000100cbe2ce -[FFEffectStack(Retiming) retimed] + 30
--------------

I've deleted every render file.
I've deleted every thumbnail file.
I've trashed all preference files and caches.
Deactivated all filters within FX Factory.
No corrupt files found in Events or Projects folders.
I've uninstalled, and reinstalled FCPX 10.0.4
I've updated the OS to 10.7.4
My external LaCie Rugged has only two folders on it, Events and Projects. The entire drive is for one project.

Nothing. Crashes on open.

I'm completely out of ideas. Anyone who can help me solve this will have a slave for life...or certainly my deep gratitude.

Thank you.

Final Cut Pro X, Mac OS X (10.7.4), FCPX 10.0.4 / 2.93 GHz / 8GB Ram

Also, can you export (or Share) instead of rendering?

FCPX works a little differently than FCP7 and rendering your timeline isn't as necessary if you don't want to.

Jeremy

[Fred Roberts] "It crashes before I have a chance to select anything. It stays open the same amount of time each time I open the program. Crash report is always saying the same thing."

Turn off background rendering in prefs.

Are you saying you can't get to the prefs before it crashes?

Did you move all of the Events and Projects out of the folders and relaunch FCPX?

Easiest way to do this is make a folder called Final Cut Projects Disabled and Final Cut Events Disabled.

Drag all the folders in your Final Cut Events and Projects folders in to the corresponding Disabled folders.

[Fred Roberts] "I don't have any THIRD PARTY retiming effects applied, but I have several clips retimed using FCPX native effect. How in the world would I be able to find the clip that has a native effect applied, and presumably try to disable it?"

Select all, command-r, anything that doesn't have a green 100% marker is retimed. Find those clips, shift-n to reset the timing.

Mine crashed on me yesterday.

When I opened it back up it was like a brand new app.

All events and projects gone.

I restarted the computer and then everything was back to normal.

I don't know if you have tried a restart.

Very scary.

Make sure your computer is booted in 64 bit. If you have multiple projects, move them out of the folder they are stored in one at a time until FCP will open. Just went through this a few weeks ago. The editor was booting into 32 bit and creating multiple compound clips.

[Fred Roberts] "FCPX opens fine if there are no projects and events. Once I put the ONE project I am working on back in the Projects folder, crash happens. No corrupt files found. I'm using a LaCie Rugged 500GB external with nothing else on it except the Events and Projects folders. No system file on that drive, nothing."

Ok. Is it still crashing when rendering?

[Fred Roberts] "I'm able to uncheck background render, then of course it's ok. But no ability to edit."

Fred-

Please try and be specific as possible.

So, you can uncheck background render and no crash, but when you start to edit, it crashes?

Or are you saying without background editing, you can't edit?

Ok.

One thing at a time, I know it's tense at the moment.

Do you know which clips are retimed? Have you tried taking the retime off?

What format is your media?

Good advice. I am loosing my mind a bit.

If I load the project to try and remove any effects or titles that might be causing the problem, it crashes. Turning background render off seems to not prevent the project from rendering once I load it into the timeline. This short period, from when I load it to when I try to make changes, is enough time for it to crash.

All the footage is there of course. I just can't access it to try and troubleshoot.

UPDATE: Now it appear even while opening FCP with NO projects in the Projects folder, it crashes. I opened the program with no Projects, but with Events for that project. I'll try with no events.

Thanks.
Steven

With no events, and just the project, it crashes. Same error message in crash report.

I did something close to that on another machine, new account, no external hardware, etc.

Based on getting the same error message after the crash, I'm convinced it's crashing when it tries to render, either a retimed clip or something else.

I'm just trying to figure out how to salvage a week's work and not start over. I just can't find a way to remove the effects before they begin to render. I just need FCP stable long enough to remove the effect causing the crash.

There are both types in the project.

Fred,

- Have you exported out any versions of your edit? If you're running out of time, it might be quicker to piece together any segment exports that you may already have.

- Have you tried opening your XML file on another FCPX system?

- Do you have XML Versions? If so, have you tried loading an earlier version?

Sandeep.

Fred,

Understand your frustration.

Also, do you have access to iChat or FaceTime via an iPhone or iPad separate from the machine you're having the problems on?

If you do, I'd be happy to try to connect with you in real time that way and talk you through some problem solving steps.

Good luck, and keep us up to date.

"Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions."-Justice O'Connor

Have had a good back and forth about this particular corruption of the project file with Jon Chappell at Digital Rebellion. I provided him crash reports from the only piece of software that offers some hope in these situations, Pro Maintenance Tools. His semi-conclusion:

"Something strange is happening here. It looks like FCPX is trying to render or process a clip and is ending up in recursion hell and probably running out of memory. This may be because a compound clip or secondary storyline is involved or because the database links between some of the clips have been corrupted.
The difficult part isn't identifying the problem though, it's trying to work out what you as an end-user can do to fix it. And I don't really know the answer to that. FCPX unfortunately has a lot of bugs that fall into this category."

Terrible to know that all the footage, edits, etc. are there, but FCPX project file can't read them.

Thanks to all who offered suggestions and help.
Steven