fbpx
Welcome, Guest
Username: Password: Remember me
{JFBCLogin}
25 Jan 2021
New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.
Read More...

TOPIC:

macOS Sierra - What works and what doesn't 03 Jan 2017 16:23 #84517

  • joema
  • joema's Avatar
  • Offline
  • Platinum Member
  • Platinum Member
  • Posts: 2213
  • Karma: 27
  • Thank you received: 544

...Untill few days ago I was able to import R3D files from my EPIC W (8k files) in FCPX. I was already on Sierra. Then it was a Sierra update to 10.12.2 and...When I tried to import the R3D again, I just see a pink frame. You can actually scrub on it (so you see the video) but as you stop it become pink. The as soon I try to import FCPX Crashes!
Crashed Thread: 31 Dispatch queue: com.apple.helium.rq.gpu-ru0.vs0.gcd....

I am working with Apple on a similar "crash on import" problem which started recently -- maybe around the time of the recent updates to macOS 10.12.2 and Pro Video Formats 2.0.5.0. On my 2015 iMac 27 it's 100% reproducible and happens immediately on trying to import anything -- it's not related to any format or codec. Obviously I tried trashing prefs, re-installing FCPX, and using a different account -- it still happens. The crashing thread stack always looks like the below.

However I have the same macOS, FCPX and Pro Video Formats on my MBP and it doesn't crash on that machine.

Thread 20 Crashed:: Dispatch queue: NSOperationQueue 0x600001231b00 :: NSOperation 0x60000124cb10 (QOS: USER_INTERACTIVE)
0 libsystem_kernel.dylib 0x00007fffb229bdd6 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fffb2387787 pthread_kill + 90
2 libsystem_c.dylib 0x00007fffb2201420 abort + 129
3 com.apple.Flexo 0x000000010560c594 FFApplicationHandleExceptionThatShouldNotBeIgnored + 452
4 com.apple.CoreFoundation 0x00007fff9cd1dd5a __handleUncaughtException + 746
5 libobjc.A.dylib 0x00007fffb188bf15 _objc_terminate() + 94
6 libc++abi.dylib 0x00007fffb0d7ed69 std::__terminate(void (*)()) + 8
7 libc++abi.dylib 0x00007fffb0d7ede3 std::terminate() + 51
8 libdispatch.dylib 0x00007fffb21370cc _dispatch_client_callout + 28
9 libdispatch.dylib 0x00007fffb214dae5 _dispatch_queue_serial_drain + 896
10 libdispatch.dylib 0x00007fffb213fcd9 _dispatch_queue_invoke + 1046
11 libdispatch.dylib 0x00007fffb2138e70 _dispatch_root_queue_drain + 476
12 libdispatch.dylib 0x00007fffb2138c47 _dispatch_worker_thread3 + 99
13 libsystem_pthread.dylib 0x00007fffb2384712 _pthread_wqthread + 1299
14 libsystem_pthread.dylib 0x00007fffb23841ed start_wqthread + 13

Please Log in to join the conversation.

macOS Sierra - What works and what doesn't 28 Mar 2017 17:31 #86788

  • VidGreg
  • VidGreg's Avatar
  • Offline
  • Platinum Member
  • Platinum Member
  • Posts: 1007
  • Karma: 28
  • Thank you received: 208
Well this topic has been quiet for awhile now, but wondering with the new macOS update and latest FCPX version, how Sierra is doing now? Issues still remaining?
Think it may be time for me to update from El Cap with a clean install. Reason is I like to upgrade before another macOS is introduced. Think the next version may be really problematic? Apple is updating the underlying file system to APFS. I am looking forward to a new file system but there may be initial pains/bugs. Latest iOS just released does make the switch to APFS when you update.
So my question is… Is now good time to go with Sierra or do problems remain?
Thanks, Greg

Please Log in to join the conversation.

macOS Sierra - What works and what doesn't 28 Mar 2017 19:36 #86790

  • JoeEditor
  • JoeEditor's Avatar
  • Offline
  • Platinum Member
  • Platinum Member
  • bbalser.com
  • Posts: 4923
  • Karma: 34
  • Thank you received: 702
Pretty stable. Only bugs I know of are FCPX itself, not OS based. Third party plugins have all been updated for quite awhile now, except Color Finale with the latest macOS update.

Color Finale including Pro doesn't work on MacBooks with integrated GPU graphics card after updating to 10.12.4. Denver says they're working on a fix ASAP. All other models work just fine.

I've been using FCPX with Sierra for months in a fast turnaround broadcast environment and don't get slowed down.

Please Log in to join the conversation.

macOS Sierra - What works and what doesn't 23 Apr 2017 12:24 #87464

  • JoeEditor
  • JoeEditor's Avatar
  • Offline
  • Platinum Member
  • Platinum Member
  • bbalser.com
  • Posts: 4923
  • Karma: 34
  • Thank you received: 702
Is this thread at all relevant any longer?

Please Log in to join the conversation.

macOS Sierra - What works and what doesn't 23 Apr 2017 15:29 #87471

  • MsJustine
  • MsJustine's Avatar
  • Offline
  • Banned
  • Banned
  • I am in Durban, safe and warm...
  • Posts: 971
  • Karma: -76
  • Thank you received: 46
Once it reaches 12 pages it becomes relevant again...

Please Log in to join the conversation.

macOS Sierra - What works and what doesn't 05 Jul 2017 10:06 #89227

Hello, I've just upgraded to Sierra, updated to 10.12.5, and I am working on FCP 10.3.4. Since this, my FCP is slower, with frequent appearance of the BeachBall for a few seconds when I try to play my 10mn timeline.
I have a 2013 Imac 3,5 GHz Intel Core i7, with 32 Go of RAM memory, and until now, it always worked perfectly with FCP, even when I edited a 52mn film... Any ideas ? Thank you.
PS : I've installed the free HITFILM plugin recently.

Please Log in to join the conversation.

macOS Sierra - What works and what doesn't 20 Aug 2017 14:01 #90018

Check your activity monitor and try uninstalling the plugin...

Please Log in to join the conversation.

macOS Sierra - What works and what doesn't 20 Aug 2017 19:26 #90020

  • JoeEditor
  • JoeEditor's Avatar
  • Offline
  • Platinum Member
  • Platinum Member
  • bbalser.com
  • Posts: 4923
  • Karma: 34
  • Thank you received: 702
Delete ALL render files for the Library (File > Delete Generated Files...).
Lunch FCPX while holding Option and Command together to delete preference files.
Launch Disk Utility, run First Aid.

BTW, what "free" plugin does HITFILM give away?

Please Log in to join the conversation.