Welcome, Guest
Username: Password: Remember me

TOPIC: Final Cut Pro crashing and unusable on new MacBook even after uninstall/reinstalls

Final Cut Pro crashing and unusable on new MacBook even after uninstall/reinstalls 18 Oct 2017 17:15 #91180

I have a new 2017 15" MacBook Pro running High Sierra. Created a new, clean user account, no migration from my old MacBook.

Installed Final Cut Pro X from the Mac App Store. Click on Import Media. As soon as I select a media file, FCPX crashes. Doesn't matter what format the file is (.mov, .mp4, etc.).

So I opened some FCPX projects from my old MacBook. I can open them, but as soon as I click on anything within the project, FCPX crashes. I've tried 7 different projects.

I've trashed the preferences on launch. Doesn't help.

I've uninstalled FCPX and used this article to delete all the preferences and caches, and then reinstalled FCPX from scratch. Didn't help. support.apple.com/en-us/HT202412

So....I have a NEW MacBook with a NEW user account and a NEW install of FCPX, and I can't use it. Can't create new projects and can't open existing projects. Everything else on my MacBook is working fine. Any idea what could be going on?
The administrator has disabled public write access.

Final Cut Pro crashing and unusable on new MacBook even after uninstall/reinstalls 19 Oct 2017 09:31 #91196

  • joema
  • joema's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 1125
  • Thank you received: 236
  • Karma: 20
CincyTriGuy wrote:
...Click on Import Media. As soon as I select a media file, FCPX crashes. Doesn't matter what format the file is (.mov, .mp4, etc.)....

There was (or is) a bug in 10.3.x whereby FCPX would immediately crash upon raising the file import dialog box if a certain file was in the import folder. In my case it was an .M4A audio file from iTunes. This was difficult to perceive because there was a small but variable delay in the crash. You could sometimes click on a video file, then it would crash, which gave the impression it was that file. In actuality was was the .M4A file in the import folder. The file was not apparently corrupt or damaged.

Since the import dialog remembers the last folder location, every subsequent import attempt would crash upon launching the dialog or almost immediately thereafter. In my case the solution was to identify and remove that file.

You can rule this bug in or out by temporarily removing all files from your import folder at the Finder level, then launching the FCPX import dialog.

Here is a long thread on this particular problem, including stack traces: www.fcp.co/forum/4-final-cut-pro-x-fcpx/...t-error?limitstart=0
The administrator has disabled public write access.