Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Apple Final Cut Pro A demo of increasing FCPX sluggishness – thoughts?

  • A demo of increasing FCPX sluggishness – thoughts?

    Posted by Doug Suiter on February 17, 2014 at 6:09 am

    *I posted this earlier to an incorrect part of COW – fixing it by posting here*

    Hi all – FCPX user here. I made the following video to demonstrate the sluggishness of the FCPX UI that I am experiencing and that i have read about others reporting.

    “Sluggishness” is a little hart to quantify so I figured a way to measure it (details in the video)

    The reason I am posting this video is because I’d like to know if this is what others are experiencing, before I continue troubleshooting my particular setup. (I have done a lot of troubleshooting in the last few weeks)

    So at first, I’d just like to know if others see similar performance hits as libraries increase in complexity.

    Thanks!

    https://vimeo.com/86859858

    Doug Suiter replied 12 years, 5 months ago 5 Members · 14 Replies
  • 14 Replies
  • Charlie Austin

    February 17, 2014 at 7:24 am

    I’ll have to try the title thing, It seems to slow down for me after the app has been open for a while. A quick restart clears it up though, so not a big deal.

    Also, keeping the inspector open brings things to a screeching halt on my work system in complex projects. Don’t know if that applies to you, but closing that window makes a difference. This is a fun new thing in 10.1 for me…

    ————————————————————-

    ~ My FCPX Babbling blog ~
    ~”It is a poor craftsman who blames his tools.”~
    ~”The function you just attempted is not yet implemented”~

  • Doug Suiter

    February 17, 2014 at 9:09 am

    Thanks Charlie – my issues aren’t cleared up with a restart but i will try the closed inspector method you suggest

  • Dave Brandt

    February 18, 2014 at 12:38 am

    Hi Doug.
    Definitely seeing this aswell.
    Restart helps but only a little and as the project gets more complex it helps less and less.
    Inspector closed makes little difference, and I need it open most of the time to adjust things.
    Anyway, the opening and closing of it is also slow.
    Opening fx panel is painfully slow, as is any editing operation.
    Makes working in fcpx difficult.

    I have found that the more titles or motion templates are used has a big effect on stickiness, even if they are rendered in the timeline.

    Hope this gets addressed soon.

    Dave

    http://www.BrandtStudios.ie

    Macbook Pro Retina 15″ i7 2.7 16GB Early 2013
    PC i7 32GB Self Build
    FCPX LogicX Adobe CC Vegas 12 Nuendo 4

  • Doug Suiter

    February 18, 2014 at 5:14 am

    Thank you Dave – that sounds like my experience exactly

  • Steve Connor

    February 18, 2014 at 3:03 pm

    Is the slowdown you are experiencing from Events created BEFORE 10.1 and upgraded to libraries?

    Steve Connor

    There’s nothing we can’t argue about on the FCPX COW Forum

  • Doug Suiter

    February 18, 2014 at 11:04 pm

    The most severe slowdown is in a library that was created before 10.1, but that also happens to be the most complex project

  • Steve Connor

    February 19, 2014 at 2:12 am

    I have a similar problem with a complex event that was upgraded after 10.1.

    Steve Connor

    There’s nothing we can’t argue about on the FCPX COW Forum

  • Doug Suiter

    February 19, 2014 at 2:15 am

    The thing is though that the other projects demoed in that video are carted in 10.1 and later. Yet they also show increasing sluggishness pattern.

  • Charlie Austin

    February 19, 2014 at 2:19 am

    [Doug Suiter] “The thing is though that the other projects demoed in that video are carted in 10.1 and later. Yet they also show increasing sluggishness pattern.”

    Can you try an experiment? Duplicate or snapshot the project, and delete a few audio layers at a time… does it get less sluggish the less audio it has?

    ————————————————————-

    ~ My FCPX Babbling blog ~
    ~”It is a poor craftsman who blames his tools.”~
    ~”The function you just attempted is not yet implemented”~

  • Doug Suiter

    February 19, 2014 at 2:36 am

    No…deleting audio seems to make a minor difference if any.

Page 1 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy