macOS Sonoma caused Final Cut Pro 10.7.1 to struggle with 4K playback?

Hi everyone, it’s my first time posting here! I usually don’t ever write in forums; which I think just shows how desperate I am right now.


A few weeks ago, I finally decided to upgrade to macOS Sonoma on my 2022 M1 Ultra (20-Core CPU, 64-Core GPU, 64GB RAM) Mac Studio after staying on Ventura for a while. After updating, I noticed that Final Cut Pro X has started to struggle with playing back & editing 4K footage. I’ve been using Final Cut Pro X for 7 years now, and have been able to easily edit 4K multicam footage on my Mac Studio. Now, even if I just have a single 4K clip, I get anywhere from 1-5 seconds from hitting spacebar to the clip actually playing.


Things I’ve tried:

• Switching Hard Drives - I’ve tried both Samsung T9 and T7 plugged into the front Thunderbolt ports. Even tried moving all files locally onto the Mac’s own hard drive.

• Uninstalling Google Chrome + Keystone files - Heard that this is a common issue, but it didn’t seem to help me

• Clean / Fresh Install - I’ve completely erased the Mac’s data drive and did a fresh re-install of Sonoma. After only having Final Cut as the single app installed, it still struggled with 4K playback.

• Deleting custom preferences

• Creating a new library & project

• Using proxies instead of original media (I’ve had no problems using original media all this time, so it seemed suspicious to me if I only had to start using proxies now)


I was really hoping that it was just coincidence, and maybe I could troubleshoot it myself. But I’m starting to think that I might just be cursed with combination of macOS Sonoma + Final Cut Pro 10.7.1. I’ve also included my EtreCheck report.


Thank you to anyone who takes the time to reads this!

Mac Studio, macOS 14.4

Posted on Mar 12, 2024 9:44 PM

Reply
Question marked as Top-ranking reply

Posted on Mar 13, 2024 8:11 AM

After trying what Tom suggested, if the beachball hang still happens, while it is hung, do these commands. It doesn't have to be the same hang event, but make sure FCP is hung in the beachball state while each of these run, which takes about 3 sec each.


These are built-in MacOS commands to sample data from the hung app and produce TXT files you can submit or post somewhere we can get them.


The first command (spindump) samples the hung process every 10 milliseconds for three seconds, creating a list of each thread's call stack, ordered by the number of times the function appears over the sample period.


The second command (sample) also samples the hung process every 10 milliseconds for three seconds, but it writes each sample to the output file. This enables post-processing of that file to examine the execution frequency of each function in each thread's call stack over the sample period.


The spindump file will be about 10MB and the sample file about 2MB. They are TXT format, but too large to post.


I can analyze these and hopefully get an idea of what FCP is doing during the beachball interval. You will need to upload them somewhere we can get to them.


sudo sample 'Final Cut' 3 -file ~/Documents/FCPSample3s.txt


sudo spindump 'Final Cut' 3 -file ~/Documents/FCPSpinDump3s.txt



Similar questions

16 replies

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

macOS Sonoma caused Final Cut Pro 10.7.1 to struggle with 4K playback?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.