Previous 1 2 3 Next 198 Replies Latest reply: Aug 23, 2014 2:05 PM by blairthornton
churchillstudios Level 1 Level 1

Hi folks outside of noticing all the missing features everyone's discussing, my first experience with Final Cut Pro X has also been plagued with slow, unresponsive hang-ups, usually accompanied by the spinning beach ball.  Most of the time the app recovers... takes about 30 seconds or so ... but other times the ball keeps spinning and will freeze the app, crash the app, or in rare circumstances freeze my whole workstation.


This is counter to the "no wait while rendering" I keep hearing about and is certainly not like what I saw from the NAB demo. So I have to wonder if it's something to do with my system, a brand-new Mac Pro - not a month old - with dual 2.93GHz 6-Core Xeons, 32MB RAM, and Nvidea Quadro 4000 graphics card.  All drivers are updated and I'm running on OSX 10.6.7.  Meanwhile all my other apps (CS5.5 Production Premium, Boris CC, Colorista II, Lightwave 10) are extremely stable and practically scream with speed.  None of these were open in the background when testing Final Cut, by the way.


I've researched the spinning ball even more by manually pausing the background renders.  When I do the app seems to free up and I can move around ... That is until I apply another effect that requires a render... then processing kicks back up, and I get more beach balls.


As for crashes, here are two quick observations: The app seems to consistently crash when I try to change the curve style of a clip’s opacity.  The other (more sinister) computer freeze has happened twice as I recall while simply accessing a pull-down menu.


Any thoughts?  I suspect it could be conflicting software or my Quadro graphics card?  Any help is appreciated.


- BC

Final Cut Pro X, Mac OS X (10.6.7), Mac Pro w/ Dual 2.93GHz 6-Core Xeon
  • phonax Level 1 Level 1

    I have had similar things happen. It responses very sluggishly its not the working experience I had with FCP or FCE. This really slows you down and it crashes all over the place.

  • Robert Rogers Level 2 Level 2

    I too have experienced the spinning beach ball  as well as crashes.  I have noticed that with each new release of new software that is supposed to just work, it usually does not until at least the first upgrade. True of Aperture, IPhoto and now FCPX.  Ultimately it gets done but not the way we expect it from Apple. Perhaps that what happens when the price for the previous software is so reasonable.  We the early adapters are the beta testers.  I'm sure it will all work out but a bit disappointed.

  • dosers Level 2 Level 2

    Same here.

    Ugh. I am on a Mac Pro with 32GB, 8 Cores and  ATI HD Radeon 5870 card.

    And literally the whole system freezes up with beach balls. If I have Motion 5 on too, I can walk away for a minute. Horrible.

    I had no issues with previous FC - it seems there must be a bug here. I don't see it using much of my 8 (nee 16) cores either, or memory; It's pretty pathetic 

  • moxytom Level 1 Level 1

    I know this isn't much help but I'm having the same issues as all of you. And now I can let out a big sigh of relief as well. I'm actually running FCX on my 13" Macbook Pro 2.26 Dual Core 5GB RAM.  So knowing even the superest of super macs are having issues makes me feel a bit better.  I have also never had issues before as I've been able to run FCP, Motion, Photoshop and AE all at once and had no problems.  I have decided to forego my FCX training and spend more time in Motion 5, which so far I'm loving! What Apple messed up with FCX they definitely got right with Motion 5. 

  • dosers Level 2 Level 2

    well, it's some help

    I assume, as the outcry isn't uniform, there is something we all have in common - a chipsept, a Graphics Card manufactuer, something - that is making FCPX choke. It's literally slower than molasses, and slows everything else down as well (usually even the most demanding programs - especially on a high end Mac Pro - will not slow down thing overall).

    My hope is that this will be fixed pretty quickly; I have now experiences it on 2 Mac Pros - so while maybe not universal, I assume it's not 'really rare' either.




  • shorafix Level 1 Level 1

    I have downloaded FCP X right after it was available from Appstore. I was testing it and started a new project. I have worked with it for about 24 hours. However, since today I had several issues with spinning beach ball forever. The app simply crashes when importing a clip into an event, applying an effect or for any other reason. It didn't happen right from the beginning when I purchased it yesterday and it did not have anything to do with software updates I installed right after the purchase. I can't tell why and when it happens, but it does crash frequently. Updating to MacOS X 10.6.8 didn't help either. I am absolutely clueless.

  • danwayfilms Level 1 Level 1

    This is a relief to me also. I'm running on a 15in MacBook Pro Dual Core 2.53ghz w/4gb ram (soon to be upgraded to 8). While i'm not expecting things to render with unrelenting speed, i've never had an issue with FCP7.


    It seems that the more complex the timeline gets, the slower things become. If Apple could fix this, I would be very happy... for now anyways

  • pedspew Level 1 Level 1

    I also have the same problem.  I have an hour long iMovie project that I imported to FCPX

    and it is soooooo slow.  The spinning beach ball pops up if I even move the cursor.  It takes probably about 10 minutes just to load the project from the project library.  It has crashed twice in the 4 hours I have had it and I have had to fore quit half a dozen times.  For being advertised as BLAZING SPEED, it is almost non usable cause its so slow.

  • TrevorRawson Level 1 Level 1

    While this probably won't fix your problem I would suggest updateting your operating system to 10.6.8. Of course you posted this 6 days ago so you might have already tried that by now. I'm on a Macbook Pro with 2.53 Intel i5 and 4 gigs of ram and having the same problem. What kills me is even though it's rendering in the background it seems to take a long time to do basic color changes on stills with a few cross dissolves thrown in. It bogs down my whole computer while rendering in the background. Seems that it would be easier for me to just let it render in the foreground ten times faster.

  • Casciari Level 1 Level 1

    Brand new top of the range 17 MacBookPro. Software updated. Final Cut Pro X installed. 3000 fullHD clips imported. Project started. Even writing this few lines becomes a nightmare due to the "background" job.

  • Sebastian Soyka Level 3 Level 3

    If it's your first lauch of FCPX, it may be busy constructing an index of all applicable media on the volume. Somewhere I read an Apple note that - at least for audio files - that may take a couple of hours, depending on your machine. I'd suggest to let it finish its background processing (use Activity Monitor or another suitable app to gauge disk activity), then quit and relaunch. Just my humble 2¢

  • Casciari Level 1 Level 1

    It's been a week now... ;-) I can stand it for now, being out of season. But I hope in october something happens. Better, something... Apple. As for the rest of FCPX, weeks ago I fortunately planned to start from scratch all of my projects. Sixth sense!

  • Sebastian Soyka Level 3 Level 3

    One Week?! You're right, that's an extraordinarily long time

  • montywent Level 1 Level 1

    The biggest problem and the one most bragged about by apple was the speed fcpx was bringing to the program. ooophs, I guess they forgot to include it.


    How can the brains at apple be so stupid?


    Very disappointed and I went back to fcp 7 to get some work done.


    This is what we can expect from apple?


    They won't charge my card for this will they?



Previous 1 2 3 Next