Hello, for the first time I have tried to use my Final Cut 10.3 with the new configuration Akitio Node + XFX RX480. Final Cut opens but when I try to do something (new project, import, etc..) it crashes immediately.
So I tried to update to the new version 10.3.4 but the problem still remain!
Anyone has the same problem?
Process: Final Cut Pro [760]
Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Identifier: com.apple.FinalCut
Version: 10.3.4 (303235)
Build Info: ProEditor-30323005007000000~1
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Final Cut Pro [760]
User ID: 501
Date/Time: 2017-06-04 09:30:44.096 +0200
OS Version: Mac OS X 10.12.4 (16E195)
Report Version: 12
Anonymous UUID: 3C720171-6028-9545-188A-B7830EEB9CB0
Time Awake Since Boot: 3600 seconds
System Integrity Protection: disabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
[FFHGRendererInfo initWithLocation:] CGLSetVirtualScreen failed - didn't expect to get here. Investigate why this code ran: [FFHGRendererInfo initWithLocation:] CGLSetVirtualScreen failed: loc=1, ctxt=0x7fe6c936ac00, err=10008-[FFRendererInfo initWithLocation:], /Library/Caches/com.apple.xbs/Sources/Flexo/Flexo-30323.5.7/framework/image/FFHGRendererManager.mm:341
abort() called
You will need to delete kext files associated with integrated graphics and only use the eGPU on FCP. FCP w/ eGPU on integrated-only macs is problematic.
purge-wrangler ✧ tbt-flash ✧ purge-nvda ✧ set-eGPU
Insights Into macOS Video Editing Performance
Master Threads:
2014 15-inch MacBook Pro 750M
2018 15-inch MacBook Pro
2019 13" MacBook Pro [8th,4C,U] + RX Vega 64 @ 32Gbps-TB3 (Mantiz Venus) + macOS 10.14.6 & Win10 [build link]
Maybe you should look at this thread: https://egpu.io/forums/mac-setup/help-final-cut-pro-x-crashing-with-1070-pascal-gpu/
To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.
.Maybe you should look at this thread: https://egpu.io/forums/mac-setup/help-final-cut-pro-x-crashing-with-1070-pascal-gpu/
To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.
.You will need to delete kext files associated with integrated graphics and only use the eGPU on FCP. FCP w/ eGPU on integrated-only macs is problematic.
Thank you for your answer! Wich kext files I need to delete? In the Extensions folder I see many...
Thank you!
Maybe you should look at this thread: https://egpu.io/forums/mac-setup/help-final-cut-pro-x-crashing-with-1070-pascal-gpu/
The error doesn't seems the same....uhm..however I don't find the solution in this thread.. I see only the message of jonwatso but I don't see the "Automatic Graphics switching" in my power saving options even if I have two graphic cards on my system.
Download this app http://resxtreme.com
and set external monitor to 8 bits/sample in Menu/ File/ Apply Selected Mode
after that open FCP that it will work
Upgraded AKITiO Node with + +
Download this app http://resxtreme.com
and set external monitor to 8 bits/sample in Menu/ File/ Apply Selected Mode
after that open FCP that it will work
Genius!! It works!! Thank you very much!
Cheers
Nice! And dont forget to keep us updated what works and what does not in fcpx...
Things like brucex, effects, exporting to prores, h.264,random crashing...
We want to know everything...
To do: Create my signature with system and expected eGPU configuration information to give context to my posts. I have no builds.
.
You will need to delete kext files associated with integrated graphics and only use the eGPU on FCP. FCP w/ eGPU on integrated-only macs is problematic.
Thank you for your answer! Wich kext files I need to delete? In the Extensions folder I see many...
Thank you!
Hey jefniro Here is my post on moving kext files. can confirm removing the driver bundles for the iGPU works in 10.13. I would imagine this will be resolved in a future final cut update as it seems eGPU support will be added to apps as per this WWDC video