The Final Cut Pro X CRASH Thread

I really think 8 was the best version. 9 was a dog.

The thread has been very useful. I read it avidly. If only I could apply a hum filter to reduce that whine.

You should pop around the corner Susan and give them a bit of stick.

Actually I need a notch filter.

Oh and FCP10 is much better than iMovie9.

Message was edited by: Tom Wolsky

Here's a thought. Next time I post I'll add:

**Disclaimer: Warning, this post contains whining because I'm still not over "it."**

My FCPX is SO UNSTABLE.

PLEASE PLEASE Apple put out an update.

I'm running on a brand new 27" iMac quad-core with 2GB of Vram and 8 gigs of the plain ol' ram. THESE FREEZES AND CRASHES ARE KILLING ME.

Unexeptable.

I'm glad this thread is out there. I hope it gets the attention it deserves.

Thanks,

JS

Unacceptable...

Oh yes. Naturally.

Final Cut Pro X was running great, but now it seems to be crashing on me for just going into the timeline.

I'm running a 3.6 GHz Core i5 iMac with 4 gigs of RAM, with Lion. And despite editing SD footage, it's now crashing on me every time I try to edit in the timeline for my project. It doesn't matter if I restart my computer, or leave it open untouched to load in. Once I turn on Final Cut Pro X, and go to the end of the timeline, it crashes. One of the only ways I could fix it was to delete the latest clips. But now, that doesn't seem to fix anything.

Not sure if this will help most out there or not, but here is my own crash story.

I first installed FPCX onto my laptop, a fairly new thunderbolt MacBook with no problems at all. You see, I was working on project in FCP7 on my main Mac Pro and didn't want anything to happen while in the middle of that project. However, when I was finished and backed up with that project, I decided to install it on the Mac pro as well.

In both cases I installed it alongside FCP7 on the same partition. I understand it's not recommended but I followed the "best practices" FAQ from Apple. But where I had a stable installation on my laptop, my desktop installation was very buggy. Specifically, adding the placeholder generator or the artifact effect to a timeline would result in a blue screen and eventual crash.

After many reinstalls, and deletions of preferences, I deduced that there was something on my desktop that wasn't on my laptop and whatever that was (program or library file or something else entirely) causing the instability.

Thus began my three day project of completely wiping my main hd and reinstalling all my programs and preferences. It wasnt an easy task, and required a lot of planning, but it was the only way I could see if there was a particular culprit behind the FCP X instability.

Now, before I had installed FCP X on my desktop, I had backed up my main drive to another drive, so I knew if this didnt work, I'd still have my old system available to go back to.

One thing I did different, was I installed Snow Leopard from the start even though the original OS for my desktop was Leopard. My laptop had always been a SL machine, so I figured I'd make my desktop one as well. As I reinstalled each program, I opened and tested FCP X and FCP 7, to make sure they still worked without crashing.

The good news was that FCP X became stable on my desktop machine. I reinstalled all of my programs and it remained stable, so it wasn't a particular program that was causing it to crash. Probably some junk files that accumulate on a machine that's been running for a while. Or it could have been an issue with a computer that was upgraded to snow leopard from regular leopard.

I've also not completely reinstalled all my FCP 7 plugins as I was more worried about them causing an issue than I was worried about iWork. But I've been reinstalling them a few at a time, making sure I gave a restore point to go back to, just in case. I also don't really have that many plugins, so I no longer expect any problems there.

I tenatively recommend this technique to anyone having serious crash issues. Obviously you should have a pre-FCP X backup of your drive before you attempt it. If nothing else, you'll need it to reference all the little things you need to re-set up (like smart mailboxes in Mail, FCP 7 preferences, browser bookmarks, addresses in your address book). I also recommend that if you DO try this, that you install FCP 7 BEFORE reinstalling FCP X.

Andy

my Crashes:

- BlueScreen by some Effect Presets. Can`t use them.

- The Same by some Generators

- The Placeholder Generator causes a crash every time i try to use it.

- The Bigger the Project, the slower Pro X

I have Lion OS and i also have FCPX, it seems to crash EVERYTIME i try to add a title, it adds the title to the timeline but when going into the title to change the writing/font it just crashes EVERYTIME garentee'd. ive tried many methods such as copying the timeline to another project, starting a new project, using different titles but it still crashes EVERYTIME. does anyone know how to fix this?

I have a 3.06 GHz Dual core with 4 Gig ram which is a year old and should be able to easily handle FCPX

@iBrianMedia - I have the same problem. Someone suggested closing the panel that has the transitions,titles, etc, and it would work. I did this and it works fine.

Add your text, close that panel and it should be fine. HOpe this helps you.

It seems FCPX has issues with this panel open.

@Apple - please release an update to all of these major crashing issues....sigh

You can also try removing all but your system fonts from your system. When problems arise involving fonts, I almost always suspect the font.

Andy

Great and necessary thread. Yes mine crashed 5 times in two days, including after re-installation. Often the playhead stops working and then it's not long before it's bye-bye FCPX. The worst part was on the second crash, I lost all of the progress that had supposedly been auto-saving. Anyone else lose work progress? FINAL CUT PRO, PLEASE FIX THIS!

Here's the thing. It only crashes on me if I try anything after the 5 minute mark. Watch a clip, add a clip. Doesn't matter what clip. After the 5 minute mark, if I try anything somewhere past that, it crashes.

However, if I do something at the beginning of the project, nothing happens. It works fine. And I haven't even added titles yet. I've tried deleted the exact clip that I was over that caused the crash, but no dice.

FCPX update... (Alert! I plan to say bad things and I’m not sorry for them))

OK, I dumped everything that came before lion, did the clean install (no snow) installed FCPX and Motion.... And they work better, but still crash... Just a very buggy program...

I know it's early and the fixes will come, but this is just sad. Oh and those jerks that keep telling everyone to shut up and move on. This is our job! Not a joke, not a place to play with our software, we already depend on. We make a living cutting every day. It’s hard enough coming up with 30 new spots a week, but you don’t want to fight the tools at the same time.

I will keep watching for answers and upgrades, but for now I think FCPX is just for fun and not very dependable.

It must be fun at Apple these days, lots of cash for corporate. Nothing but crashes for us!

Kinda like getting coal in your stocking, we must have been bad customers buying all that stuff.

FCPX is our reward!

My current crashing seems to happen when I move a cover layer clip on the timeline. The timeline move is fine if you have not added a filter. If one of the two clips have a filter it will crash. Also, if I add a transition to a clip that has been pulled down in size, it will only run the transition full screen, not just transition my small clip, then it crashes.

Motion will not always export, it gets to 76% and stops... I try to close it after about an hour and it crashes. It will not playback in real time only jerky motion...

I look forward to each and every post. This community is a wonderful tool during hard times. Sometimes you feel so alone with these problems and apple is no longer the problem solvers of the past. I talked to seven different people in five area’s of apple. Each finding a reason to pass me on and never giving me much hope. It felt more like an investigation than someone who had answers. We are all Beta testers and have been for years. One nice apple guy said he was “sorry for the problems but people are working on them and we hear you” He has had me send him several post from this site.

Most important, they are reading this site and we should be sharing every detail of our problems and our passion.

FCP X also unstable when "browsing" effects. This results in blue screens. Looks like random crash, not repeatable / reproducable when clicking the same effect again. It just crashes on another one. My old FCP Studio was stable as a rock. Also some other bugs:

-send to compressor does not work although it is installed.

-main project window uses other audio channel than "scrubbing" raw footage in "event library" screen

-dragging footage from finder to fcp x sometimes hangs. Quit & restarts resolves issue

hardware:

cpu Intel Quad Core, SSD drive & black caviar disks

RME fireface 800 for audio

27 inch screen

osx 10.6.8

(use mbpro to test Lion, but don't trust it yet)

Hope they will release an update soon.... or should I switch back to FCP studio again? So now the question is: unstable FCP X with better GUI vs FCP S fast & stable, but more "old style" GUI....

(At least my cubase 6 & Play 3 upgrade remained stable.... but that is not apple)