FCPX 10.6.1 Won't Shut Down On M1 Pro Mac

Question

Level 1

8 points

FCPX 10.6.1 Won't Shut Down On M1 Pro Mac

I have a new 16 inch MacBook Pro M1 Pro and have been having the worst time with Final Cut Pro x 10.6.1. Not only is the horrible beach ball appearing more often than my 2015 i7 MacBook bro but I’m also having issues where FCPX won’t shut down properly. I’m forced to force reset every single time!

Ive tried uninstalling and reinstalling. Tired command and option upon loading. Nothing seems to fix this. Any help would be much appreciated because I’m about to send this MacBook Pro back and continue to just use my 2015 MacBook Pro.

MacBook Pro

Posted on Nov 22, 2021 8:48 PM

Reply

Answer 1

Top-ranking reply

Luis Sequeira1

Level 9

73,332 points

Nov 23, 2021 7:44 AM in response to emkwan

Let me guess... you migrated everything from your 2015 mac to your new M1 Pro mac.

It is very likely that some third party software that you migrated does not work correctly in M1 macs and Monterey.

Also: if you have an antivirus in this machine, uninstall it.

Another well known enemy of FCP and other professional applications is Chrome (and its keystone thugs).

In order for us to know about these or other potential causes of trouble:

Please run Etrecheck and post its full report here. Use the "additional text" button and paste the report into the text box.

Reply

Answer 2

emkwan Author

Level 1

8 points

Nov 23, 2021 7:08 PM in response to Tom Wolsky

Genius Bar - reset something to do with MacOS itself. (Wasn’t a reformat thankfully). Uninstalled FCPX, all plugins, motion templates.

Then…Reinstalled FCPX and didn’t install plug-in and templates. Also made sure to turn off background rendering.

I’ve been testing since yesterday and seems to functioning as expected. Will update here in a few days + few projects if resolved.

Reply

Answer 3

emkwan Author

Level 1

8 points

Nov 23, 2021 6:05 PM in response to Luis Sequeira1

For reference this was an absolute fresh install. Didn’t port anything over. A trip to the Genius Bar helped resolve - also turning off background rendering helped immensely.

Reply