Final Cut Pro and Spinning Beach Balls

I have shown apple all the evidence of it chasing and beachballing and timeline scrubbing issues too, videos of times it has happened, they still deny it's an issue, they blamed that the 2020 macbook pro 10th gen wasnt powerful enough, they are wrong. It's a final cut problem and apple must fix it soon

Probably best to tell engineering exactly what's happening on your system and what you're doing when it happens, step by step. The more information they can get about specifics of systems, drives, and media the more useful it is. Thinking they don't need lectures.

I would also return the laptop but contact Apple support and see what they say first about the issue, I have held on to mine in the hopes of Apple fixing the issue and to update this forum about the issue, but there could be an update coming as soon as next week so I will hold out on that

Understandable, however like mentioned earlier, this type of throttling is unique to this issue in my experience. I'm coming from a 2012 MBP 15 inch with a slower GPU than Intel Iris and have encountered nothing like this. This isn't the computer getting "slow". This is a different issue. For example, after experiencing this behaviour, I closed Final Cut and opened YouTube. While watching a video, the play button and full screen button would not stop flickering. It was only until I restarted the computer was the issue fixed. Like I said, there is no reason a maxed out 2020 machine shouldn't be able to handle my "on the go" workload.

Bought the MBP 13 inch 2020 1tb 16gb 10th gen intel and same issue. Last night I was trying to edit a moderately complex project (7 tracks 1080, some more) on the machine in premiere. It was extremely laggy and kept glitching and freezing so I thought I'll give the machine the benefit of the doubt. I thought that it was time to bite the bullet and move over to FCPX as I have heard about how powerful it is and particularly that it is optimised for macOS.

It plays and works fluently for 10 or so minutes before saying 'I've had enough' and from then it goes downhill, freezes and I have to force quit the app. This happens a lot.

Called Apple support and they just told me to install prores, maybe try a test account but to be honest from seeing all of this it must be a software thing. What I don't get is how this has not gained more traction? Why isn't there anyone on twitter shouting and screaming about this? It's an 1800£ machine!

Maybe it only affects some units

I called Apple today to complain about the problem and got through to a rep from the engineering team. She screen-shared on my MacBook to see the issue but I wasn't editing at the time so she wasn't able to witness the beachball. She gave me some tips like using an external SSD to hold my files since my MacBook was half full (I have 500gb of storage total), but I'm not confident that will fix the problem since I was already editing from a portable 1TB SSD. I showed her this thread and she confirmed that they are aware of the complaints, but they need more people calling in when the problem occurs so that they can screen-share and witness the problem live. Seems kind of hopeless at this point until FCP releases an update.

Yes, we did a support call, but they started going for the "reinstall" and all that stuff, so we basically ended the call. I've got both of the FCPX and macOS feedback tabs open, but I haven't reported it yet. Not very forthcoming of me, I know.

However, if anyone else is feeling lazy like me, you can do what I've started doing: Whenever FCPX gets into a beachball frenzy, you can force quit it, and as you do that, the error reporter pops up and asks why you quit it and asks you to reopen the application. I've done this quite a few times now. This could be a convenient way to bombard Apple with crash reports and messages describing why the app became unresponsive.

Let's hope there's a fix soon!

PS, another interesting thing I've seen on my 32GB machine is that the RAM doesn't seem to be used up more than about 55%. Throughout the issues iStatMenus has never plotted over 60% memory usage. Seems a bit odd. Anyway, sorry for the side track.

PS, another interesting thing I've seen on my 32GB machine is that the RAM doesn't seem to be used up more than about 55%. Throughout the issues iStatMenus has never plotted over 60% memory usage. Seems a bit odd. Anyway, sorry for the side track.

That's normal. Programs only need so much memory. If your machine at the time needs only 60%, that's what it gets. By adding memory it's like having given it a bigger blackboard on which to do calculations. You only need so much board. It is, and of itself, a good sign. The programs running on your machine are getting the memory they need. You have plenty of memory. Something else is the problem. The leftover memory is used as a file or I/O cache to speed up disk access, but I don't know if that's included in the memory usage reported by the iStat Menus app.

I have noticed this issue only on FCP. Also yes, maybe it’s a general problem (OS wide) about hardware but I don’t think it’s a hardware issue. I think it’s a software issue about how the software handles that particular hardware, like the drivers are not fully optimized for those Intel chips. So I think an update on FCP or macOS in general will fix the issue, I’m sure they will bot leave those models with such a major issue forever!

I got 2 version 8th and 10th generation. I used FCX on the 8th gen without any problem like freezing in 5 hours contrast with the 10th gen freezing all the time whenever I dragged the timeline. But I already returned both of them because both of them laggy when I use video call like facebook and the 8th gen has only 1 fan.

Begin this week I received my new Macbook 16 after returning the Macbook 13 inch. After using FCPX for more than an hour, i do not have any problems with it. I'm very happy I upgraded to the 16 inch version. The bigger screen is more pleasing to work on.

I hope apple will fix the problem for the 13 inch version soon, guys!

My late 2017 MacBook Pro screen died last month so I took the opportunity to "upgrade" and grabbed the 2020 MacBook Pro (2ghz quad core and 16GB memory). Was looking forward to faster, more reliable video editing (as my 2017 model was handling everything well) but I've been having this issue too.

Final Cut constantly freezes, beachballs and crashes - full fresh install of everything (didn't move anything to the new machine, just started with fresh app installs) and its getting a bit ridiculous, poorer performance than my older MacBook!

If anyone finds a fix please let me know!

3 weeks after returning the 13 inch, I bought a refurbished 16 inch i9. At first I didn’t want a 16 because I find it to big for tight spaces like in my sailboat. Having no issues editing with FCPX and I realize that the bigger screen is golden.

S/V Lusca

https://youtu.be/Td-DBMywcqs

She has put a pinned comment explaining that she is having major issues with final cut pro