alexgrainger

Q: FCPX 10.1 Very slow on iMac and lots of spinning beach balls

I have noticed since I have started to use FCPX 10.1 on my Late 2012 iMac (32GB RAM, 680MX Graphics, i7 quad core, thunderbold Arecca Raid) I am getting lots of spinning beach balls and things are generally slower.

 

I am really hoping Apple thought about people who cannot affored a Mac Pro, and ensure the performance is also good on iMacs, but unfortunately I am seeing a drop in performance compared to 10.0.9.

 

Has anyone else with an iMac noticed this?

Posted on Dec 22, 2013 5:37 AM

Close

Q: FCPX 10.1 Very slow on iMac and lots of spinning beach balls

  • All replies
  • Helpful answers

first Previous Page 14 of 14
  • by Lemolai,

    Lemolai Lemolai Jan 26, 2015 7:13 AM in response to Luis Sequeira1
    Level 1 (4 points)
    Jan 26, 2015 7:13 AM in response to Luis Sequeira1

    Yes, good to know, but still. What happened with FCP 10.1.4

    Previous versions worked with mts formats like knife through butter.

    Within last 24 hours FCP X has crashed 10 times. Previously maybe once in two days, which was bearable. And after starting again it starts to render something and this takes timeeeeeeeee. Every simple move (selecting track) causes 10 seconds beachball. Sometimes 15 seconds.

    And I'm working with audio which shouldn't take too much resource of the machine.  

    MTS might be crappy format, but still millions are using Sony cameras and mts formats. Optimising is not an option. It is pointless waste of discspace.


    Finally if it ever would be possible I'd go immediately back to previous version. I'd rather manage green dropped frames than watching spinning ball, restarting the programme and listening clicks and pops in audio.


    So does anybody have information or heard from somewhere - is there any movement at Apple to fix those issues?


    thanks, I go back now to see my favourite movie "Spinning Beachball revenge pt.XXXVI",


    Lemo

  • by Tom Wolsky,

    Tom Wolsky Tom Wolsky Jan 26, 2015 7:42 AM in response to Lemolai
    Level 10 (118,348 points)
    Apple TV
    Jan 26, 2015 7:42 AM in response to Lemolai

    You don't have to optimize, but if you import properly you won't be using .mts files but QuickTime, which is incredibly more efficient for production.

     

    I haven't seen this problem in 10.1.4 using long .mts files. It hasn't crashed, since I can't remember when, certainly not this year, and I use it every day. There was almost no change in the FCP application in 10.1.4 with the exception of new codec integration which was added with the Pro Video update, not the application update. The update was so small that 10.1.3 can open libraries created in 10.1.4.

     

    I'm thinking something else has changed on your system that's causing this problem with FCP, maybe some plugin or some other software that interacts with FCP.

  • by Lemolai,

    Lemolai Lemolai Jan 26, 2015 8:02 AM in response to Tom Wolsky
    Level 1 (4 points)
    Jan 26, 2015 8:02 AM in response to Tom Wolsky

    Thanks,

     

    Any suggestions what plugins should i look after on which soft might interact with FCP?

     

    Lemo

  • by Tom Wolsky,

    Tom Wolsky Tom Wolsky Jan 26, 2015 8:08 AM in response to Lemolai
    Level 10 (118,348 points)
    Apple TV
    Jan 26, 2015 8:08 AM in response to Lemolai

    AAny plugins might do it. Audio plugins seem more prone to problems, but that's just that they're reported more often. Do you have any plugins? Try removing them all to start.

  • by menick,

    menick menick Jul 5, 2016 4:39 AM in response to alexgrainger
    Level 1 (8 points)
    iWork
    Jul 5, 2016 4:39 AM in response to alexgrainger

    This issue persists on the latest OS X 10.11.5 and 10.2.3 FCP X. In an attempt to narrow down this issue, would it so happen that everyone experiencing this is running a secondary display? Also do all of you have fxFactory plugins?

  • by Luis Sequeira1,

    Luis Sequeira1 Luis Sequeira1 Jul 5, 2016 5:50 AM in response to menick
    Level 6 (12,500 points)
    Mac OS X
    Jul 5, 2016 5:50 AM in response to menick

    At this point in time I believe you should start a new thread and give specific information about your issues, including your hardware setup.

     

    This thread is very old, and FCP X works just fine for most people today, as it did back then. If you have been suffering from performance issues all this time, there is likely something else, specific to your setup, that is involved, and not a yet-to-be-fixed bug. If you keep waiting for a new release to solve those issues, you are likely to be perpetually disappointed.

first Previous Page 14 of 14