Activity › Forums › Creative Community Conversations › Why does FCPX crash so often?
-
T. Payton
November 29, 2011 at 12:14 amNow that you mention it, my daily crashing has stopped too.
However, I have found a few things that can crash it for sure:
– a corrupt font
– a really large PSD (this only happened on one file but is reproducible)
– Camera Raw files on certain machines (My MacBook Pro for example crashes on a camera raw, the MacPro has no problem with it)
– Low Memory. Well I don’t know if it really crashed or I just became impatient.However, with that said I would call Apple. They should be able to help.
——
T. Payton
OneCreative, Albuquerque -
Bill Davis
November 29, 2011 at 12:50 amJust to add another voice…
I started with no crashes at all. Probably my first 2 weeks. That was with relatively “low stress” projects. DV footage, no complex fonts, and I was keystroking moderately since I was “feeling out” the software.
Then I migrated to more complex projects. At one point, I started getting crashes. For a short period, I had 3-4 a day when I was working on some DSLR projects with more complex timelines including relatively large imported photos.
I haven’t had a program with a large number of big photos lately, but I did notice than after the two subsequent FCP-X updates, my timelines, my footage, and the speed of my use of the program have all increased significantly – and I haven’t had a crash in weeks.
It’s really hard to diagnose other people’s machines, software, and setups. In the past I’ve seen too many posts where someone was having a horrible time – only to find that in a week or so they discovered some “individually specific” cause – perhaps a RAM chip gone bad, a bad font, a behind the scenes program (remember how evil INITS used to screw things up in the old days!) or some other issue specific to that particular editors system that did not effect the general editor.
This is a hassle and I feel for the OP. Because I’ve been there when it was MY machine that wasn’t working right when everyone else’s was.
But I’ve got to report that X and Lion are working fine together on my MacBook Pro. (I just ordered a new Open CL compatible graphics card so I can also start cutting on my MacPro system – but I’m so happy with my laptop performance that I’m not sure I’m going to migrate even when I can.
FWIW.
“Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Connor
-
Rafael Amador
November 29, 2011 at 2:38 amI have perhaps one crash a year with FC7 and I’ve been using FCPX.1.0 for 4 months without any crash.
Does anybody around run something like DiskWarrior or TechTools in a regular basis?
rafael -
Rob Mackintosh
November 29, 2011 at 9:33 pmSince upgrading to 16GB of RAM I’ve had no crashes. Things still get sluggish with multiple layers of titles.
Motion 5, however, crashes repeatedly when editing an effect or title and FCPX is open.
Seems to happen more on Rigs and when you have an instance of the effect applied to a clip in the FCPX timeline. -
Jason Jenkins
November 30, 2011 at 6:29 pm[Walter Soyka] “See, this is what I miss about Mac OS 9. It crashed just the right amount: not so frequently that you couldn’t get anything done, but not so rarely that you missed out on good reboot coffee breaks.”
And with a solid state system drive, a full reboot only takes about 50 seconds… It’s a good thing I don’t drink coffee, because I wouldn’t have the time!
Jason Jenkins
Flowmotion Media
Video production… with style! -
Jeremy Garchow
November 30, 2011 at 6:46 pm[Jason Jenkins] “And with a solid state system drive, a full reboot only takes about 50 seconds… It’s a good thing I don’t drink coffee, because I wouldn’t have the time!”
I helped a colleague setup a brand new 12core MacPro a few weeks back with an SSD boot drive. I thought something was wrong it boot so fast, and this was a cloned copy of a Snow Leopard install from the old system.
Craziness.
Reply to this Discussion! Login or Sign Up