The Final Cut Pro X CRASH Thread

I've never done it before, but I know it is possible to have dual boot available. It's how developers usually test out new OS's while they are still running the current version. Just do a little digging online and I bet you figure out how to do it.

Please tell me they're fixing this. I "upgraded" to FCP X, was a good soldier, cut a documentary with it, lived through it, and then "upgraded" to Lion, thinking it might work really well with FCP X and give me all the speed enhancement promised. Now it crashes if I touch anything. I've started a critical project and can't get past 2 minutes of editing, or even moving a clip on the timeline without it crashing. Really Apple? Really???

Thanks Brian!

It works for me as well, I have my titles back!

Good Job, It is too bad Apple doesn't have a fix for this problem...and here you are at least you found a temporary solution...

Patrick

I went through the trouble of installing a clean version of Lion this last weekend and just now have gotten a chance to test out FCPX on my "new system."

Opened up a project with a title. Opened the inspector. Clicked on title.....CRASH!!!!

Guess that didn't fix it after all....sigh.

At least we know to keep the inspector closed. That seems to at least make it less tempermental. I sure hope Apple releases an update soon.

When I open fcpx, the first I do is to go the window menu and click on reset original window layout. Once I do that, my titles don't induce a crash when I click on it.

Before I close the program, I go back to the window menu and click again on the reset original window layout.

Hope that helps

B

I feel your pain. I just went through a similar exercise of backing up my MBPro, erasing the HD, and installing a fresh copy of Lion from a USB stick (which all worked remarkably well I must say).

I copied my iMovie files back to the hard drive, along with FCP X. Launched iMovie to make sure the projects were still ok (which they were), then launched FCP X and tried to import a project...CRASH! Same old, same old.

Not only that, but I'm not seeing any improvements in performance now that I have a 'clean' install, so it was really was a waste of several hours.

Waiting on Lion patches, FCP X patches...

This is why I refuse to do a fresh install. It's taken me nearly two years to get my current system where it is. I'm also enjoying lion with no applications giving me any problems. I use time machine but also clone my main drive.

I'm not prepared to start from scratch only to find the same crash problems.

I gues a dual boot system may be worth trying.

I have purchased the ripple training videos (excellent) as I really want to give fcpx a chance, but unfortunately the program will not run for more than two minutes at a time. :-(

Thx Brianfox!! It helpt, i don't know why but it helpt 😀

FCPX crashed every time I clicked on a title sequence. I reset to the defalt windows and could delt the unwanted titles. Thanks DVCapture. I am finaly able to get back to work.

Bite the bullet - DO A FRESH INSTALL -

For what it's worth, here is my recipe for perfectly running Lion / FCPX / FCS3 machines:

1) Clean install of SL, with updates up until 10.6.7

2) Install of FCPX/Motion/Compressor (then moving those apps into a subfolder in /Applications)

3) Install of FCS3, then all other apps

4) Update to 10.6.8 + supplemental 10.6.8

5) Install of Lion 10.7

This is what I did to create a decent image that performs well and has none of the major problems seen here:

https://discussions.apple.com/community/mac_os/mac_os_x_v10.7_lion, or in this thread.

This image has been to both MBP3,1 and iMAC8,1 machines, breathing new life into old iron.

Cheers!

Here's how I did my fresh install.

1) Back up everything in Time Machine

2) Erase hard drive

3) Install Lion from the boot disc I created (no Snow Leopard)

4) Use Migration assistant to copy over personal files NO SOFTWARE

5) Install FCPX, Motion, and all my other software (CS5, etc.)

This did not work for me. FCPX still crashes when trying to edit titles and motion was still very slow when doing more complex animations.

At least I know the workaround for the titles is to put it back in the default window display. Still though...kind of surprised they let this out the door like this.

Sorry if I upset someone, but I'm at the end of my rope with three weeks of product waiting for me to edit.

AND THE **** FCPX KEEPS CRASHING! How can this have the name PRO?

I have had an apple computer for 20 years... Always the best always doing what Apple tells me in order to "best" use the product. Where are they now!

I have had every version of FCP and every operating system apple has created from that 20 years. I was a devoted fan... I "Bit the Bullet" and did everything that was suggested by apple and this group. I still have crashes and I am here to say that this is apple's problem and they don't know how to fix it... I have been on the phone with them and it's like they know nothing about what is going on. They say nothing in public about this mess and you must wonder if Rome/Apple is falling...

I love the style of the new final cut and motion but never had a crash with the old final cut. In fact I checked and I have not had anything crash in almost a year. The last one was me having two many programs running at once.

I have been fighting my system (Lion) from the first day I installed the new OS. Nothing works right anymore and I really hate the crashing... The problem with great fans of a product line is that when you let them down (like apple has) it turns them into super anti-fans. 100 times the energy of a normal person who may not like a product.

APPLE! SHOW SOME BALLS! STAND UP! FIX THIS CRAP, NOW!

Brian's advise is working for me until Apple fix the problem: turn the inspector off then you will be able to edit your text...as a matter of fact my FCPX seems to be working better now... THE PROBLEM IS WITH THE NEW LION

do not reinstall or anything like that I talk to Apple and that WONT WORK! they are working on the problem...

I hope they fix it soon...

Cheers

Brian's advise is working for me too.