The Final Cut Pro X CRASH Thread

My FCP X is working good except if I use foreigner caracters. If I just type any letter like "á", it's crashes immediately. It's always came back ok without any losses, but it's very annoying. The only way I figured out to avoid this crashes is copy/paste the foreigner letter.

Any suggestions? This situation is slowing down my work badly.

JR Gandara

We run a small edit suite with 10 macs, 5MBP's and 5 imacs, all brand new running lion and fcpx. We moved the entire buss to mac in one week. We had never used fcp before. We use both mini dv cams to shoot (Sony) and new sony sd card cams, AVCHD. We all use WD external drives using fw800 connections. Our edits are simple but the source footage is huge, huge, huge. A project is typically 200 gig of source media if captured in proxy.

3 weeks of 10 hour days on all 10 machines the following is our conclusion.

• The footage/media captured into events via fcpx somehow gets corrupted and invariably is the source of many a crash.
• Often the name somehow goes missing on certain clips and will cause problems.
• Overlays cause crashes and is always audio related, again our theory is the footage gets corrupted.
• We have tied capturing using imovie. Still crashes with this footage
• SD avchd, based footage seems more stable (we shoot hd standard around 4gig per hour footage)
• Proxy vs optimised makes no difference in percentage crashes.
• Background rendering causes trouble, Kuk as we say in SA.
• Often once you capture to fcpx the machine is buggy until it has completed its massibve rendering process. if you allow it to finish things smooth out.
• In the power manager setting on the MBP's turning off the setting that effects the graphics card usage makes a huge difference, less buggy, less crashes
• We have not tried to re render using a secondary app, with around 100gigs of original footage per project it would slow us down massively. Might give it a go but as a workflow i want to avoid it. Would be more cost effective to purchase new sd cameras.

Conclusion. FCPX is massively buggy, crashes lots but invariably for us (we use no real effects worth writing home about) its unhappy with the footage/media it has created itself. Apart from the crashes (very recoverable) the programme works a dream and we hare holding our breath they will resolve the fact that FCPX seems to create media it cannot itself work with.

On we plod getting projects out working around every possible FCPX trap. Nice programme with plenty KUK/trouble in its code.

Hey nfoo,

Thanks for your response. Well, I personally have a 50-50 success rate with following Apple's support documents. I do however, always have a solid Final Cut workstation 🙂.

I think your note will help a lot of people out. But man, if you're right about having to use Parallels with Lion, just to use Final Cut Studio, yikes that's a bummer!

It's just anecdotal, but most of the editors I know are keeping FCP7 around as they test out FCPX. I guess they won't be able to do that with Lion.

Maybe Snow Leopard is an answer? I had no crashes in either FCPX or FCP7 with SL.

Thanks again,

Andrew

My procedure for opening SEP X for the past week has been to delete the 2-4 plist files then open FC. Now when I open FC it only allows me to load projects that are on my internal drive whether they contain only audio or video. It will not allow me to load into the timeline any project that has either audio or video from my external drive. This condition happened after I was working on a project, during which FC crashed. The procedure I was working on before it crashed, was choosing a range in the video.

I have trashed my original FCP X product. And downloaded another from the App Store. With the same result: crash.

Any suggestions?

Wow, apple you used to be cool.

Spent 3 days editing (through crashes) only too have FCP X crash permanently and be unable to open at all!

I want a refund, this app bites!

OSX 10.7 latest

Mac mini scratch and app drive.

You're not going to get a refund here. Try contacting Apple.

Did you trash your prefs? Sounds like your system is underpowered.

Not Saving / Command Undo not working question:

I've tried to follow this thread some and I remember seeing someone say that if you notice your ability to undo goes away that FXPX is not auto saving - OK - well I went to Command Z - nothing. So I quit and restarted software. Yup - it hadn't saved any work for the past 45 minutes.

Can anyone explain why or how this happens? Or what to watch out for - to catch it earlier?

Besides this and crashing on tweaking some transitions I've had almost no problems.

I just Trashed mY Pref - using the Preference Manager App and started work again - but I would like to learn from this experience.

Thanks Everyone.

The update 10.0.2 is now available from the App Store.

Whether or not that will help, you should nevertheless update.

It makes it possible to save the fonts and text in Titles along with some other stability issues.

Good luck

I'm assuming that 10.0.2 is more stable? And is an imporvement?

I've been working with 10.0.1 on OS X 10.7.2 Mac Pro 8 core with 10 gigs RAM and Radeon 5770.

I've been editing with DSLR h.264 footage from a Nikon camera and 16/48 audio WAV files from a Zoom recorder.

FCP X crashed on me twice while I was synchronizing clips. After I sync (the correct clips) and then disable the audio track of the video clip in the resulting synced clip, then if I skim the clip in the Events window - crash - every time.

It also crashed on me twice just editing in the timeline, working with the audio and the equalizer.

Very buggy and unstable.

I am now waiting for the 10.0.2 update to insall. I'll report back after I edit with it on the same project that has crashed on my 4 times in the last hour.

Thanks

Synced clips. Every time I put one on the timeline that is a super over the storyline, and then I disable its audio, crash.

you know boys and girls this thread is probably the most important one. Bottom line:

FCPX is a phenomenal, ahead of its era program.

FCPX is buggy and frustrating

All FCPX users are holding their breathe for some quick fixes of these basic operational issues.

...I'm just glad I'm not the only one. Luckily it is a "loveably" program son I still have some more patience....lets hope, pray and see....

This really reminds me of Motion. I've loved Motion since version 1.0. It has some really amazing things it does that no other app does, and these things save a huge amount of time. Unfortunately, Motion was very buggy and unstable for years. I think it still is. So if Motion is any indicator, I see people who love the great features learning workarounds versus it becoming a solid app.

Let's face it, Apple makes billions off of iPads and iPhones, not a silly software program. I guess I'm jaded. 🙂

Looks like the FCP X Crash Thread is OCCUPYING Apple's communities. Next up: the FCP X engineering room.

apple needs to make the workarounds.