The Final Cut Pro X CRASH Thread

Followup. I dragged project folders, one at a time, from the trash back into the FCP project folder and restarted FCPX after each drag. Got almost all the way through before FCPX crashed on startup. So after removing the offending folder tried another relaunch. Crashed. I had to drag several project folders out (folders that one minute earlier had been ok) before FCPX would launch successfully. Then, after dragging all but the last project BACK into the FCPX folder, it runs again. But why did I have to remove "good" projects out and then back in? Doesn't inspire a lot of confidence that the system is stable...

Entering Option-Enter in the Label field for the timecode generator will result in a crash for FCPx (10.0.2) and making that project unsable and unrecoverable. This is reproduceable on both OSX 10.6 (MacPro) and 10.7 (MacBookPro).

When you enter Option-Enter in the Label field in the timecode generator, it will crash FCPx. When you try to restart FCPx, it will crash. To recover, I moved the project folder in the Final Cut Projects directory to another disk, and restarted FCPx. I then shut it down, replaced the project folder back in the Final Cut Projects directory, and restarted FCPx. The project shows up, but if I attempt to open that project, FCPx will again crash.

Not sure how to recover this project, or is there is a way at all.

OK, I give up. Why would you press Option-Enter in the label field of the timecode generator?

It doesn't look like there is a way to recover it. The project content seems to be OK except for the timecode generator, which becomes corrupted, and I can't see any way to get rid of it.

Simple, it looked like the label box allows for multiple lines of text to be written since its a multiple line dialog box. I was trying to add information on the second line, and as with many other apps, you can enter a option key to enter a new line, rather than have it wrap. I didn't remember what it was, and tried Cmd-Enter and Option-Enter. One did nothing, the other crashed it.

Why doesn't matter. It should either be accepted and handled appropriately or discarded, no?.

Currently, Option-Enter is a valid command and mapped to the FCPx crash function! I think this feature should be removed as it isn't very useful for most of us 😉

as with many other apps, you can enter a option key to enter a new line,

Really? Which app does that?

On a Mac you normally just put in a return for a new line.

Tom, this is possible in some apps and it's useful in cases where Enter performs another function such as submitting a dialog box.

Seriously? This is more important than whether or not I can crash FCPx on demand and corrupt projects just by entering common keystrokes in a dialog box?

Fine, whatever... just to name a few that use a common convention of using a modifer key to enter a new line when the enter key is used to complete the dialog box (option, command, or shift); Microsoft word, TweetDeck, SimpleMind, BlinkBid, Evernote, Celtix, Things, iCal, Firefox, Safari, many of the desktop widgets, etc.

You focus on why I pressed the modifier key. I'll focus on what happened and try to get it fixed. 🙂

I have read with great interest everything in this thread because I've experienced tremendous frustrations with FCP X over the last couple of weeks trying to finish a project a little over an hour in length. I have an Imac bought midway through this year with an I7 processor and 12 gig of ram. I partitioned my hard drive and set Lion up on one partition and Snow Leopard the other. Using fcp x in Lion has been a real nightmare with several crashes every editing session. I have since switched to editing on my Snow Leopard partition and FCP X's stability has improved 100%. I've just finished two 2 hour session editing throwing everything I can at the timeline. Layers upon layers with effects added, titles, lots of picture in picture type things etc etc. FCP X handled it all perfectly with lots of speed. My conclusion, and I'm not really a computer wiz is that there is something dodgy happening between Lion and FCPX.

I'm lost in the threads and at a loss of what do do with my lovely edit that will not share so pardon me for just jumping in. FCPX just closes when I try to share, no error report. Also, not holding rendering on all parts. Using Eevent Manager X. Deleted preferences. Went back in Time Machine to retrieve an earlier project file that I know was good, and same thing happens. Do the editing gods have any solutions so I can finally finish this dog and then jump out the window? There are so many features I like about FCPX, I've stayed with it this long. But the past couple weeks have become intolerable. Certainly the Event Manager helped. At this point, unless Apple can proceed with a major overhaul and release an update soon, I'm going to ask for my money back. I've never had experiences like this with any Apple product until June. Is it possible that Steve being out of the picture could have made such a huge difference in quality control? I hope and pray someone has an answer to heal my wounds.

Let's see what we can do. Start with the exact specs of the computer, the media you're working with, and the project properties.

Start out by trashing prefs, repairing permissions, and rebooting before you export. Export to movie with current settings.

Hi Tom --

I've done everything you listed. Several times. Even made 150 gig additional space available on my project drive.

MacBook Pro 2.93 ghz 8 gb ram 320 gb hd. 2 -1 tb OWC external drives, 1-1.5 tb OWC external drive, 1-4 tb OWC raid for Time Machine. Two drives are SATA card connected and 2 are 800 firewire.

I'm using one of the OWC external drives for my project connected vis SATA. Now about 250 gigs free.

Event Manager was acting strange, so I trashed it and reinstalled.

Sharing using current settings to Apple Devices. App closes as soon as I release the mouse from that choice..

Sharing using current settings to Apple Devices

Please try the procedures and export to movie. Do not share to a device or remote site. Please try exporting a movie using current settings.

Please could you give the exact specifictions of your media nd your project properties.

Does seem willing now to Share to DVD and Blu-Ray. The edit is 16 minutes long, 4096 x 2048. Files size for Blu-Ray showed about 3.5 gb.

I tried erlier to copy the file and paste it into a new timeline on a different drive, but didn't want to take it.

OK. Will do. Thanks.

While I'm waiting for rendeer to complete after trashing, handling permissions, rebooting... I'll answer your questions I missed earlier.

Imported interview media is 1080i Sony HDV, various jpeg stills and off-air news recordings, a variety of formats. Interview media and other footage is imported as proxy, jpegs copied to event folder. All that's transcoded, right?

The edit seems to lose rendering in some sections with live action, stills in chroma-key sometimes, and other times where I have credit rolls over stills.