Final Cut Pro 10.4 Crashes
When I connect my SD cards to it, Final Cut Pro 10.4 crashes. When I try to relaunch, it opens and then closes again. What is wrong?
MacBook Pro TouchBar and Touch ID, macOS High Sierra (10.13.2)
Newsroom Update
Final Cut Pro transforms video creation with Live Multicam on iPad and new AI features on Mac. Learn more >
Final Cut Pro transforms video creation with Live Multicam on iPad and new AI features on Mac. Learn more >
When I connect my SD cards to it, Final Cut Pro 10.4 crashes. When I try to relaunch, it opens and then closes again. What is wrong?
MacBook Pro TouchBar and Touch ID, macOS High Sierra (10.13.2)
Much to my surprise, Apple contacted me directly about this problem, and after looking at my crash logs and system config file they determined it was a known problem caused by a bug in CamTwist. Apparently, some extension that CamTwist installs is not compatible with 10.4 and causes the launch crash. I deleted all CamTwist files on my hard drive, rebooted, and now things work fine.
No, I had written a poor review on the App Store. They then reached out to see what they could do.
CamTwist is a video app that is useful for live broadcasting with various bits of hardware and input sources. Things like live Facebook feeds from your Mac, etc. I haven't actually used it in many years, so no loss getting rid of it.
Hi, I have the same problem here too.
New Admin account gives me the same issue, and it's not SD card related because I didn't try importing anything.
I've tried deleting the .fcpbundle library as I no longer need the previous one but the same issue occurred.
It was definitely the 10.4 upgrade because it didn't happen to 10.3.x
Crash log snippet below.
[...]
Crashed Thread: 7 Dispatch queue: NSOperationQueue 0x60800042c900 (QOS: UNSPECIFIED)
[...]
Thread 7 Crashed:: Dispatch queue: NSOperationQueue 0x60800042c900 (QOS: UNSPECIFIED)
0 com.apple.CoreFoundation 0x00007fff2ffbaaea CFStringGetLength + 10
1 com.apple.CoreFoundation 0x00007fff2ffcd208 CFStringCompare + 24
2 com.apple.ozone.framework 0x000000011c1e1cb9 OZGetNewFontID(__CFString const*) + 41
3 com.apple.ozone.framework 0x000000011c1e3250 OZFontManager::enumerateSystemFonts() + 928
4 com.apple.ozone.framework 0x000000011c1e296b OZFontManagerBase::initFonts() + 27
5 libdispatch.dylib 0x00007fff57846d50 _dispatch_client_callout + 8
6 libdispatch.dylib 0x00007fff57846d03 dispatch_once_f + 41
7 com.apple.ozone.framework 0x000000011c1e2219 OZFontManager::getInstance() + 41
8 com.apple.ozone.framework 0x000000011c1e3f7f -[OZFontMenuImageCacheBuilder rebuildImageCache:] + 1279
9 com.apple.Motion.effect 0x000000011b7502f2 +[FFMotionEffect initializeMotionFramework] + 225
10 com.apple.Motion.effect 0x000000011b7500a5 __48+[FFMotionEffect initializeMotionAsynchronously]_block_invoke + 26
11 com.apple.Foundation 0x00007fff3212b22f __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 7
12 com.apple.Foundation 0x00007fff3212b091 -[NSBlockOperation main] + 68
13 com.apple.Foundation 0x00007fff3212953e -[__NSOperationInternal _start:] + 778
14 libdispatch.dylib 0x00007fff57846d50 _dispatch_client_callout + 8
15 libdispatch.dylib 0x00007fff57859333 _dispatch_block_invoke_direct + 317
16 libdispatch.dylib 0x00007fff57846d50 _dispatch_client_callout + 8
17 libdispatch.dylib 0x00007fff57859333 _dispatch_block_invoke_direct + 317
18 libdispatch.dylib 0x00007fff578591d6 dispatch_block_perform + 109
19 com.apple.Foundation 0x00007fff3212554c __NSOQSchedule_f + 342
20 libdispatch.dylib 0x00007fff57846d50 _dispatch_client_callout + 8
21 libdispatch.dylib 0x00007fff57859e76 _dispatch_continuation_pop + 472
22 libdispatch.dylib 0x00007fff578516cb _dispatch_async_redirect_invoke + 703
23 libdispatch.dylib 0x00007fff57848941 _dispatch_root_queue_drain + 515
24 libdispatch.dylib 0x00007fff578486ed _dispatch_worker_thread3 + 101
25 libsystem_pthread.dylib 0x00007fff57b0b1ca _pthread_wqthread + 1387
26 libsystem_pthread.dylib 0x00007fff57b0ac4d start_wqthread + 13
[...]
Model: MacBookPro11,3, BootROM MBP112.0142.B00, 4 processors, Intel Core i7, 2.3 GHz, 16 GB, SMC 2.19f12
Graphics: Intel Iris Pro, Intel Iris Pro, Built-In
Graphics: NVIDIA GeForce GT 750M, NVIDIA GeForce GT 750M, PCIe, 2 GB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x134), Broadcom BCM43xx 1.0 (7.77.37.5.1a3)
Bluetooth: Version 6.0.2f2, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM0512F, 500.28 GB
USB Device: USB 3.0 Bus
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 17.1
I've got a different "report to apple" dialogue earlier and some code crashed because month = 13 (Seems to be what I've highlighted in red above). But I've changed the date of my Mac to January and it still crashed.
Since updating to 10.4 I have experienced ongoing fatal crashes whilst editing(using the new colour correction tools). I have tried all the usual fixes and am now dealing with Apple directly (I understand that my Mac logs are being sent to the FCut software engineers for their analysis of the reasons for the crashes}. Very, very frustrating particularly after purchasing Larry Jordan's latest training. I am awaiting their report on the reason for the crashes and recommendations for a fix.
Same problem here. Try to upload from SD card, crashed. Now FCPX 10.4 won't start up. I have Sierra and never like to update during busy filming time. Now FCPX updated on it's own and I'm stuck until they fix it.
They don't have an easy way of downgrading versions if something doesn't work. You just have to wait for them. Unless you find an older version via torrent. I did this for Compressor since an older version works better than the newest buggy version.
Unfortunately the only way they will reply quickly is through a bad review on their App Store. That's what I'm going to do right now.
Hello
On my mac pro
FCPX 10.4 updated in the background
Now I try to open FCPX 10.4 and it crash after one second 😟
important edit to do for tomorrow, please help ...
mac os : 10.13.2 (17C88)
best regards
Gabriel
Gabilourson wrote:
Hello
On my mac pro
FCPX 10.4 updated in the background
Now I try to open FCPX 10.4 and it crash after one second 😟
important edit to do for tomorrow, please help ...
mac os : 10.13.2 (17C88)
best regards
Gabriel
Try deleting preferences.
For most people, 10.4 works fine on 10.13.2.
If deleting preferences does not solve it, there may be some software conflict.
You may want to run Etrecheck and post its report here.
I can't even get it to launch. After updating to 10.4 it crashes every time I try to launch it 😟
-Brian
When you say try what do you mean? What exactly are you doing, where?
MacBook Pro 15 inch with touchbar and 4K iMac. UsbC hub on Mbp and card slot on iMac
Seems a different problem. Not related to connecting external devices.
I see - my first go at a forum really. Apologies. Should I start a new conversation elsewhere?
I have just done that, but unfortunately the same crash occurs.
I did a fresh boot and installed it and the same thing happened.
Final Cut Pro 10.4 Crashes