Final Cut pro running really slowly - M1 Pro

Hi,


I have a M1 Pro MacBook pro 16" 16GB RAM 1TB SSD. When editing in final cut pro I am working off projects stored on the local machine with around 300GB available space and its running really slow to the point where I cannot edit. Please find my ram usage below



I thought it could be maybe some of my extensions aren't M1 Pro compatible so I went back to the barebones of FCPX and still facing the same issue. Any suggestions would be much appreciated

MacBook Pro 16″, macOS 11.4

Posted on Sep 26, 2022 03:37 AM

Reply
Question marked as Top-ranking reply

Posted on Sep 26, 2022 04:01 AM

RAM usage per se does NOT seem to be the problem.


However, we can see that you have Chrome, and that is well known enemy of video applications.

You should completely uninstall Chrome, and its evil keystone daemons, which run in the background and completely hog the system videotoolbox.


See https://chromeisbad.com for an explanation of the problem and instructions for removal.


Note that it is NOT enough just to quit Chrome, or even to remove it; you need to delete the keystone daemons and agents.


After you've done that, you will also need to delete and reinstall FCP. This does not affect your libraries or media. Just drag the application to the trash and download a new copy from the App Store.


If there are still problems, there could be other issues that we can't see just from the screenshot.

Please run Etrecheck and post its full report here.

Use the "additional text" button and paste the report into the text box.


5 replies
Question marked as Top-ranking reply

Sep 26, 2022 04:01 AM in response to aaronf15

RAM usage per se does NOT seem to be the problem.


However, we can see that you have Chrome, and that is well known enemy of video applications.

You should completely uninstall Chrome, and its evil keystone daemons, which run in the background and completely hog the system videotoolbox.


See https://chromeisbad.com for an explanation of the problem and instructions for removal.


Note that it is NOT enough just to quit Chrome, or even to remove it; you need to delete the keystone daemons and agents.


After you've done that, you will also need to delete and reinstall FCP. This does not affect your libraries or media. Just drag the application to the trash and download a new copy from the App Store.


If there are still problems, there could be other issues that we can't see just from the screenshot.

Please run Etrecheck and post its full report here.

Use the "additional text" button and paste the report into the text box.


Oct 6, 2022 02:11 AM in response to aaronf15

The program is now crashing. Here is the crash report:


-------------------------------------

Translated Report (Full Report Below)

-------------------------------------


Process: Final Cut Pro [52702]

Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro

Identifier: com.apple.FinalCut

Version: 10.6.4 (405402)

Build Info: ProEditor-40540002015000000~15 (18G6c)

App Item ID: 424389933

App External ID: 851212100

Code Type: ARM-64 (Native)

Parent Process: launchd [1]

User ID: 501


Date/Time: 2022-10-06 10:08:00.1488 +0100

OS Version: macOS 12.4 (21F79)

Report Version: 12

Anonymous UUID: 8A7D1EA9-D606-207F-B7E1-315A734D03F5


Sleep/Wake UUID: 47093938-99FA-4ACB-964A-E5796F3C8CB0


Time Awake Since Boot: 360000 seconds

Time Since Wake: 3748 seconds


System Integrity Protection: enabled


Crashed Thread: 66 Dispatch queue: com.apple.root.default-qos.overcommit


Exception Type: EXC_BREAKPOINT (SIGTRAP)

Exception Codes: 0x0000000000000001, 0x00000001ac5e4264

Exception Note: EXC_CORPSE_NOTIFY


Termination Reason: Namespace SIGNAL, Code 5 Trace/BPT trap: 5

Terminating Process: exc handler [52702]


Application Specific Information:

API MISUSE: Over-release of an object



Thread 0:: Dispatch queue: com.apple.main-thread

0 libsystem_kernel.dylib 0x1ac75d738 __psynch_mutexwait + 8

1 libsystem_pthread.dylib 0x1ac795384 _pthread_mutex_firstfit_lock_wait + 84

2 libsystem_pthread.dylib 0x1ac792cf8 _pthread_mutex_firstfit_lock_slow + 248

3 OpenGL 0x20de78704 CGLCreateContext + 144

4 ProGL 0x100e45d30 PGLCreateSharedCGLContextObj + 96

5 Flexo 0x1075d2608 -[FFMetalVideoPainter initWithMTLDevice:drawStyle:rawColorSpace:destOSCsDisabled:] + 1396

6 Flexo 0x1078254cc -[FFPlayerVideoModule updatePlayerAndDest:] + 496

7 CoreFoundation 0x1ac85950c __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 28

8 CoreFoundation 0x1ac8fdc08 ___CFXRegistrationPost_block_invoke + 52

9 CoreFoundation 0x1ac8fdb74 _CFXRegistrationPost + 456

10 CoreFoundation 0x1ac8281b0 _CFXNotificationPost + 732

11 Foundation 0x1ad6eccc8 -[NSNotificationCenter postNotificationName:object:userInfo:] + 96

12 AppKit 0x1af5f427c __67-[NSWindow _updateSettingsSendingScreenChangeNotificationToScreen:]_block_invoke + 620


Oct 6, 2022 02:15 AM in response to aaronf15

Whenever the application crashes you must delete its preferences, because they get corrupted and will cause more crashes.


To delete preferences, hold down command and option while starting FCP X and click Delete Preferences.

The application will start in a default state, and open an “Untitled” library.

Reopen the library you were working on, set the preferences the way you like them, and try again.


Did you remove Chrome and all its evil keystone daemons?

Did you then get a fresh copy of FCP?


Please run Etrecheck and post its full report here.

Use the “additional text” button and paste the report into the text box.

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.

Final Cut pro running really slowly - M1 Pro

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