Q: The Final Cut Pro X CRASH Thread

Having the exact same thing after upgrading to Lion.  Whenever I edit, delete or even touch a title in my timeline, I get the beachball, and then FCPx quits unexpectely.

Do you have an earlier version of FCP installed? Did you upgrade to Lion after you installed FCPX?

Yes to both!   Ihave lots of older spots that we still use from the older final cut....  Apple told me that I could use both and that lion would not matter...  FCPX will not open older projects...   Many of us still use FCP 7

Unfortunately, we are facing the teething problems of a potentially great product (once it matures). I knew that aopting early means possible hassle. I am a prosumer and can afford having these problems. Pros probably will want to wait until things have settled, what usually can take over a year. I am 'happy' to go through it and 'help' making it a great product through my bug reports to Apple.

Anyway, I will go through it and clean install Lion and then FCPX; I trust that these issues will go away and will not install FCP7.

Since upgrading to lion I am getting issues with any text as well. Titles, Lower Thirds, the lot. If I clock on them or do anything to them FCPX will crash straight away.

I think I figured out a workaround to the titles crashing.  When clicking on titles with the inspector open, FCPx quits every time (with Likn installed and no previous versions installed).  By closing the inspector first, I can click on titles or lower thirds and delete or even edit the text.

Looks like a bug.

Martin Bolsinger wrote:

 

Unfortunately, we are facing the teething problems of a potentially great product (once it matures). I knew that aopting early means possible hassle. I am a prosumer and can afford having these problems. Pros probably will want to wait until things have settled, what usually can take over a year. I am 'happy' to go through it and 'help' making it a great product through my bug reports to Apple.

 

 

No offense Martin but the P in FCXP denotes Pro, does it not?

Why would a company like Apple release a program that is essentially an early Beta release and risk their bright and shiny reputation?

I would think about asking the difficult questions before piling on the accolades.

pancenter-

I've always installed Mac OS X on a completely clean drive.. I dont believe in OS updates over exisiting OS's! For FC this is even more important to remember.

I installed LION from a DVD to a completely newly formatted HDD, after which FCPX and its updates were installed and then MOTION etc.

I still get the rare Unexpected Error.. but they are rare and no more than FCP7. Thus far, Ive created 7 programmes using both FCPX and Motion and its quite stable.

What has helped: (in FCPX) Turning OFF Background Rendering; Turning OFF Skimming in the timeline (which I personally dont like and find annoying!)

Oh and Im running an original MacPro 1.1 (2006) with an 5770 HD graphics card.

This is my point, it is so un-Apple to do this to loyal fans. I think Apple has problems at home and we are seeing the signs of a once great company taking a fall.  As a creative Apple has always been there for me and I am still buying everything they put out. But my love of Apple and protection of the brand is gone...

No offense Martin but the P in FCXP denotes Pro, does it not?

Why would a company like Apple release a program that is essentially an early Beta release and risk their bright and shiny reputation?

I would think about asking the difficult questions before piling on the accolades.

Just hope you are not right! So far, my initial disappointment in an Apple product was turned around by a good customer service. Really hope Apple thinks different and makes FCPX a great product. Agreed that it tastes like a beta product, but then, the root cause of the issues may be very diverse and only a release would tell them! Let's see when the first fix comes and what it addresses ...

ajhmedia wrote:

 

I am still buying everything they put out. But my love of Apple and protection of the brand is gone...

The fact that you would buy something in spite of the quality is what Apple depends on.

It certainly doesn't encourage a company to do better if you buy without question everything they produce.

pancenter-

I think this a concise report on what to do. I did the same, also on old iron, with the added step of moving the new FCPX apps to a subfolder, and then installing FCS3. All is working great. Cheers!

Thanks brianfox!  Your solution worked for me.  Just turned off the inspector and now I can edit text.  Oddly enough, now the whole thing seems to be working once I got it working the first time.  Now that I've done it once, I can go an click on a text transition with the inspector open and it's not crashing anymore.  Strange stuff.

Good to hear Millerrh512.  It was driving me insane as I was just trying to make a final change to a project i was working on.  I've seen the app work much better after closing the inspector...and then even after reopening it.   Not sure what the bug is...but I was certainly able to reproduce it.   Very strange stuff indeed. Here's hoping for an update to fix it.

I can't confirm that a clean install will help.

As I have never succeeded in starting FCPX - also after upgrading to lion - I installed a new ssd drive, installed Snow Leopard, upgraded it to Lion, and then installed Firefox and FCPX. The only programs (besides the built-in standards) on this new drive! And again: it crashed during the start up.

This program is driving me insane.