FCPX 10.2.1 crashes

Hi all,

I've a new iMac 27" connected to a Promise Pegasus2 R8 (24 TB) with thunderbolt 2. I'm running FCPX 10.2.1
I ingested material of a new project - the first on the iMac and this copy of FCPX - and began to key word it and too often FCPX would just "unexpectedly quit". No loose of work or any other damage - just annoyance.

I wonder if other people here have similar experiences with FCPX 10.2.1

Thanks,
Benny Brunnner

1- Trash pref files.
2- Run Disk Utility to "repair" all drives.
3- Move FCPX from Applications to the Trash, go to App Store, Purchased section, install again.

I am having a similar problem with crashing. My crashing seems to be from using two screens and when I double click somewhere on a screen I get the error that something was not able to be written so FCPX is going to crash. It does crash once I click on the OK button. There is nothing special about my setup MacPro(late 2013), 32 G, OS 10.10.3, FCPX 10.2.1, two older 27" Apple Monitors, Pegasus R1 RAID. I am not able to reproduce the crash each time when I click on the other screen but at some point it will happen again. I have done all of the steps Ben suggests but I still get the same crash. For me maybe it is time to re-image the computer.

I've been getting crashes as well. Once every 1-2 days usually. It can't seem to find a consistent cause either. Other then it happens when I'm working in the timeline.

Much more crashes with this version, also I am getting system crashes with it.
FCP will freeze, then the whole system reboots.
Usually during render out or timeline scrub.

Diskworrior/pref delete, helps until the next crash a few hours later.

Yes I have also been getting these freeze ups where I have to do a hard shutdown. I think I started getting those on FCPX 10.2.

DI am having many more crashes than usual, since installing the last upgrade. The mention of running two monitors is interesting. I also run my system with two monitors. I am curious if that might have something to it.

It looks like we all here are running the latest MacOS and FCPX versions. I hope Apple is listening.

I'm absolutely hating FCPX right now - crashes so random. I thought the idea with updates was to improve function and reliability?

I am also on 2 monitors via a GTX 680

Besides a pathetic amount of FCP and system crashes caused by FCP, I have seen garbage in exported video clips where the garbage is not in fcp itself. Render or not, playback in fcp looks fine, upon rendering out to 422 or h264 garbage gets introduced into the video.
In one project I removed and exchanged many transitions to fcp transitions (because I was in a rush to get the job out), and the garbage went away. So its possible 3rd party filters/trans that were compatible with the last version, are not now. I haven't really done enough testing to say that for sure, but it is leading in that direction..

The 'adding keyframes' bug seems worse as well. Add a keyframe to a clip, somewhere in the middle of the timeline, and the keyframe gets added way down the start of the timeline.. as the whole timeline shifts and you loos the place you were working on. Really bad.
What I think is happening is if a clip is trimmed (or in an out points set), then it adds a keyframe somewhere else in a trimmed area that aint even on the timeline... that in turn causes the whole timeline to shift positions to the invisible trimmed area of that clip.

Also I am noticing much more loss of the skimmer. This happened in the last version but worse now. All of a sudden the skimmer no longer works.. you need to click on to the desktop some where, back onto fcp somewhere a couple of times to get the skimmer back. Also the skimmer will not work at all if you have the 'keyframe editor' on in the viewer. If you dont click the 'done' box you will never get the skimmer back. Not sure if this is by design or not.. I seldom use the monitors keyframe area. Only to set every single keyframe I make to linear. Why it is not set this way by default is beyond me, the way it is now is all erratic in its movements from keyframe to keyframe. Any video online you can tell in a heart beat.."that was made in FCP" simply by the drunken looking keyframes.

I'm beginning to think that Apple spent too much time on a 3D text tool that no one really was in desperate need of, and not enough time fixing existing bugs, nor working on long-time desperately needed tools. Thus, opened up a whole can ow worms (bugs) that put them further behind on bug fixes than anyone at Apple cares to admit. Just my persona opinion. They're working on fixes, they're listening to us, they just don't have the time and man power needed assigned to FCPX to catch up that quickly.

Ben, there is absolutely not one single word of what you write that I can disagree with!

At least reading everyone else's problems here, makes me realise I'm not alone!

I'm confident there will be major bug fix updates very soon. But I fear this will put off the adding of long time desperately needed tools even further. But we'll see bug fixes pretty quickly.

I'm testing the auto-backup system in response to another post here. Since the 10.2 update it is basically non-functional. Filling out feedback form, hoping for the best.

But yes, we have some very serious bugs that need to be dealt with, and I've got confidence in Apple to fix them properly.

I wonder where from you draw your confidence in Apple or do you know something that we mortals don't

From Apple's track record, from spending time with Apple folks over the past many years at NAB and other events and jobs I've done. Where do you draw your lack of confidence?

Besides the crashes now when I go to drag a text box around, the typed words do not follow the box. Even after dropping the box the text sometimes does not move. Clicking once again on the box sometimes brings the text to the moved text box. This must be a bug as I deleted FCPX and all of the preferences, restart computer, re-installed FCPX, same problem with the text not moving. I have not reported these problems since I can not always duplicate the problem each time.

It seems you're on solid-confidence-ground and I don't dispute it.

I wouldn't describe my attitude as "lack of confidence" but more as "the burden of proof is on Apple's shoulders". I don't have to tell you how annoying and a waste of time it's to deal with the problems discussed here when you're editing a project.

I don't know if the bugs are in FCPX exclusively, maybe some of them are in MacOS itself. Since Apple adopted a yearly OS update cycle, we're experiencing a growing number of bugs that are carried on to the next OS update.

At the end of the day, I want to edit my film, not to get distracted and annoyed by a buggy FCPX.

"Clicking once again on the box sometimes brings the text to the moved text box"

I have seen this as well. You need to move it at least twice (from what I can see) to get the text box to actually move. Also finding the area by hovering the pointer over where you think the box is.. seems to work when it wants too..

"At the end of the day, I want to edit my film, not to get distracted and annoyed by a buggy FCPX."

Yep, true, and MC and PPro are pretty buggy, also. Sad state of today's IT industry.

Not much of a comfort that MC and PPro are buggy too. And yes, the IT industry is indeed in a very sad state; they treat us as captured customers without real options to make another choice. Sad.