FCPx will not open, Leaves spinning beach ball of death over the application which is unresponsive after upgrade to 10.8.2.

I may have an overactive imagination, but it sounds to me like you've downloaded a pirated copy; then when it started beach-balling, you decided you'd better download something legit...

After downloading the latest trial version, it still didn't work...

And all this while with an editing assignment only one week away?

How's my crystal ball?

How long does the beach ball show for?

Did you totally delete (or move) the Final Cut Events folder as well?

HI Suisse-Lad, try removing the FCPX state information..

Simply

1. quit or force out FCPX
2. use the Finder or the terminal.app to PURGE | REMOVE | DELETE the following state inforataion from FCPX before you start looking at the FCPX prefs which I'm confident others may suggest.

Step 1: delete this:

~/Library/Save Application State/com.apple.FinalCut.savedState

Step 2: USe Finder or terminal.app rename these two folders that appear on ANY file systems you have where they exist where you may have asked FCPX to put its goodies, rename to something else:

Final Cut Events and Final Cut Projects to zzz.Final Cut Events and zzz.Final Cut Projects

This should cause FCPX NOT to try and reinstate the FCPX UI like it was launched last time and secondly NOT to try and LOAD any events or reinstate an PROJECTS and build proxy thumbnails because it wont find any. If you'r enew to FCPX these two directiries will be likely in your ~/Movies directory...

Step 3: Launch FCPX and see if yourresults differ.

Step 4 (optional) IF not then as others may suggest to delete the 3-4 com.apple.FinalCutxxxx.plist files in the ~/Library/Preferences (your home domain library)

Post your results for other to see.

Warwick

Hi joe, thanks for the replies. Firstly YES definately delete that plist locked file. It's residual .. Do this when you have terminated FCPX. Then try again.

From you first reply it sounds like the procedure didn't work for you.. Strange indeed. Usually it will make FCPX launch like new... So as per a precious poster the code and its framework might be corrupt.

In your second reply it sounds like it did work.. Lol...

If the procedure did work it would be helpful to others if you marked the solution as either "fixed" or "helped" so that these type of threads turn up quickly in these search forums.

I hope it worked for you and if so , like many other glad to have helped. Don't give up on FCPX it's great!

Cheers mate

Warwick

Hong Kong