General Discussions
FCPX eGPU new Mac Pro crash - CGLSetVirtualScreen failed
 

FCPX eGPU new Mac Pro crash - CGLSetVirtualScreen failed  

  RSS

nickmilitello
(@nickmilitello)
Eminent Member
Joined: 3 years ago
 

I have an eGPU (akitio with Titan Z) on a nMP 2013 running Sierra.  When I launch FCPX 10.3, it crashes every time.  If I move this set up to my MacBook Pro, with all the same software, FCPX works fine.  Anyone else have a nMP with an eGPU and FCPX that could test or have any issues.   I get this error every time and Apple hasn't been helpful at all.  

[FFHGRendererInfo initWithLocation:] CGLSetVirtualScreen failed - didn't expect to get here. Investigate why this code ran: [FFHGRendererInfo initWithLocation:] CGLSetVirtualScreen failed: loc=2, ctxt=0x7f7f97d0b800, err=10008

 

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
devild
(@devild)
Trusted Member
Joined: 3 years ago
 

Hey, I've been able to test nMP 2013 with eGPU last Friday with FCPX 10.3.1 Trial but only on El Capitan - and there were no problems with start.

So I assume that there is some problem with the Metal option on Sierra. But I know that FCPX 10.2.3 is working on Sierra with eGPU.

That is not dead which can eternal lie, And with strange aeons even death may die.


ReplyQuote
Barni
(@barni)
Eminent Member
Joined: 3 years ago
 

Get the same error. I just setup my first eGPU (Sapphire Radeon RX 470 Nitro+ 8GB) in Akitio Thunder2 with my Mac mini 2012 i7 16GB Sierra 10.12.3?
It also crashes in iMovie. Lightroom CC and DaVinci Resolve works fine (at my first looks)

Application Specific Information:

Crashing on exception: [FFHGRendererInfo initWithLocation:] CGLSetVirtualScreen failed - didn't expect to get here. Investigate why this code ran: [FFHGRendererInfo initWithLocation:] CGLSetVirtualScreen failed: loc=1, ctxt=0x7f89872d8600, err=10008

-[FFRendererInfo initWithLocation:], /Library/Caches/com.apple.xbs/Sources/Flexo/Flexo-29713.7.52/framework/image/FFHGRendererManager.mm:341

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
Barni
(@barni)
Eminent Member
Joined: 3 years ago
 

Well, found the solution 2 threads later on my FCPX crashes search here in the forum 🙂

I unplugged my HDMI Monitor (which was still attached because of the setup of the eGPU system)

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
Barni
(@barni)
Eminent Member
Joined: 3 years ago
 

Sadly it worked only for a short time? Now i have the crash again and no hdmi is connected?

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
Barni
(@barni)
Eminent Member
Joined: 3 years ago
 

After some researches i found out that FCPX (and iMovie) does not work together with 

1) INTEL HD 4000 and  
2) AMD RX 470 (in my case)

because this combination does not exist in Macs.

The solution is to delete the corresponding files of the INTEL HD 4000 card in /System/Library/Extensions

In my case i backuped /System/Library/Extensions/AppleIntelHD4000Graphics*.* to a save place

opened terminal and entered:

MacMini$ cd /System/Library/Extensions
MacMini$ sudo rm -rf AppleIntelHD4000Graphics*.*

After a reboot FCPX runs like a charm (so far after some minor tests)

Maybe because i pulled out the HDMI cable out of my monitor (i mentioned earlier) the internal INTEL HD 4000 was kind of switched off and thats why FCPX works for a limited time?

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
kukkis
(@kukkis)
Trusted Member
Joined: 3 years ago
 

@Barni: that is really good news that FCPX works with that hack in Mac Mini. With laptop that hack would make it a desktop unless one is willing to delete and add corresponding iGPU kext back every time.

How did RX470 behave on exporting project from FCPX? I noticed that Intel Iris 540 is much more efficient with quick sync than gtx970 in exporting.

late-2016 13" MBP + [email protected] (AKiTiO Thunder3) + macOS 10.12.3


ReplyQuote
Anchoricex
(@anchoricex)
Trusted Member
Joined: 3 years ago
 
Posted by: Barni

 

After some researches i found out that FCPX (and iMovie) does not work together with 

1) INTEL HD 4000 and  
2) AMD RX 470 (in my case)

because this combination does not exist in Macs.

The solution is to delete the corresponding files of the INTEL HD 4000 card in /System/Library/Extensions

In my case i backuped /System/Library/Extensions/AppleIntelHD4000Graphics*.* to a save place

opened terminal and entered:

MacMini$ cd /System/Library/Extensions
MacMini$ sudo rm -rf AppleIntelHD4000Graphics*.*

After a reboot FCPX runs like a charm (so far after some minor tests)

Maybe because i pulled out the HDMI cable out of my monitor (i mentioned earlier) the internal INTEL HD 4000 was kind of switched off and thats why FCPX works for a limited time?

   

 

This is a really big find! Can anyone verify this process works for laptops and other internal Intel HD ___ variants? My 2016 Macbook Pro 15" runs a Intel HD 530 alongside the dGPU (AMD Radeon 460) and I've been hesitant to test with an RX480 because of the FCPX issues. This has been a huge turn off that I've seen prevalent throughout the forums, and if this can be solved this may really further increase the appeal of eGPU's alongside Macbooks. 

 

 

In this screenshot, there is no "530" file, do the 5000 files correspond ? Someone with an RX480 please test this!

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
Barni
(@barni)
Eminent Member
Joined: 3 years ago
 
Posted by: kukkis

 

@Barni: that is really good news that FCPX works with that hack in Mac Mini. With laptop that hack would make it a desktop unless one is willing to delete and add corresponding iGPU kext back every time.

How did RX470 behave on exporting project from FCPX? I noticed that Intel Iris 540 is much more efficient with quick sync than gtx970 in exporting.

   

Hi kukkis,

because this is the first time ever i work with my new eGPU and FCPX i will need some time to figure that out.
My intention to use a eGPU was to edit my DJI Mavic Pro videos in 4K without converting them to proxy videos first. And this works like a charm (so far).

I am just right now render a Trailer in iMovie and the RX 470 does nothing at all (CPU is at 600%). So i would say rendering (exporting) do not uses the RX 470.

But i just started this eGPU project and have to dig deeper in this.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
Barni
(@barni)
Eminent Member
Joined: 3 years ago
 

I want to link here to the original post i got the final hint from: 

https://www.tapatalk.com/topic/1071455-hackintosh-forum-de/29369-imovie-crasht-mit-radeon-rx-460

"Der Fehler tritt auf, wenn man gleichzeitig eine Intel und eine AMD Grafikkarte verwendet. Eine solche Kombination gibt es in echten Macs nicht, da hier Apples Grafikumschaltung genutzt wird. Da die Intel Grafik bei den RX-Karten nur für den Boot gebraucht wird hilft es die entsprechenden Intel-Kexte für die jeweilige Karte erst zu sichern, dann aus /System/Library/Extensions zu löschen. Dann hat die Intel-Karte zwar keine Beschleunigung mehr, aber sie ist ja sowieso nur Starthilfe."

Translated:

"The error occurs if you use a Intel and a AMD graphics card at the same time. Such a combination does not exists in real Macs because they use Apples "graphics switching". Because the Intel graphic is only used for booting the RX cards
 it helps to backup the Intel.KEXT of the desired card and than delete them from /System/Library/Extensions. Then the Intel card does not have a acceleration at all, but it is only used as a jump start.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
Barni
(@barni)
Eminent Member
Joined: 3 years ago
 

I will write e new post later about the detailed setup of my Mac mini 2012 i7 16GB, Akitio Thunder2 PCIe Box, Sapphire Radeon RX 470 Nitro+ 8GB and Dell DA-2.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
kukkis
(@kukkis)
Trusted Member
Joined: 3 years ago
 

@Barni: I have exactly the same part for eGPU but tried to get them to work on 2016 MBP which did not go that well. Now I am thinking should I get a 2012 Mac Mini or build a skylake hackintosh to hopefully get the benefits of quick sync as well.

My main purpose for the eGPU is also to be able to edit GH4 files in 4k and with GTX970 it went pretty smoothly when I made 3840x1600 2.40:1 project, imported 4k GH4 files as Prores422, used couple of quite heavy LUT's, graded a little and exported the project. The GTX970 was quicker on transcoding while editing but on exporting the project it was really slow compared to intel quick sync. Will definitely have to test more and find out how much and where eGPU helps on FCPX.

late-2016 13" MBP + [email protected] (AKiTiO Thunder3) + macOS 10.12.3


ReplyQuote
nickmilitello
(@nickmilitello)
Eminent Member
Joined: 3 years ago
 

@Barni

Any thoughts on what to change with the Mac Pro 2013 with dual D700's.  It would be amazing if I could get this fixed!  I have good luck with a MacBook Pro with Thunderbolt 3 and FCPX.  But my Mac Pro crashes FCPX every time with eGPU.  I don't have any HDMI plugged into the Titan Z.  I have tried to use the HDMI and I have also tried a 980ti (instead of the Titan Z).  Also completely deleted the OS and started from scratch with no luck. 

I assume there must be something that I can change in terminal just have no idea what to change.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
Barni
(@barni)
Eminent Member
Joined: 3 years ago
 
Posted by: nickmilitello

@Barni

Any thoughts on what to change with the Mac Pro 2013 with dual D700's.  It would be amazing if I could get this fixed!  I have good luck with a MacBook Pro with Thunderbolt 3 and FCPX.  But my Mac Pro crashes FCPX every time with eGPU.  I don't have any HDMI plugged into the Titan Z.  I have tried to use the HDMI and I have also tried a 980ti (instead of the Titan Z).  Also completely deleted the OS and started from scratch with no luck. 

I assume there must be something that I can change in terminal just have no idea what to change.

Sorry nickmilitello... I only own a Mac mini 2012 and heard about the incompatibility between Intel HD and ADM Graphics and removing the HD driver files did the job for me... 

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago

ReplyQuote
nickmilitello
(@nickmilitello)
Eminent Member
Joined: 3 years ago
 

@goalque Thanks for the links.  I tried to plug in an HDMI into the Titan Z and launch FCPX with no luck.    I will try to do a 980ti with HDMI plugged into a monitor to see if that works.  Though I do remember trying the 980ti and FCPX 10.3.2 and it still crashed though I didn't have a monitor plugged into the 980ti.  Wasn't sure how to proceed with the first link you sent though.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
nickmilitello
(@nickmilitello)
Eminent Member
Joined: 3 years ago
 

Using a DisplayPort to HDMI adapter to my 40" 4k monitor coming straight out of the Titan Z allowed FCPX to actually work.  For some reason it seems when a monitor is plugged directly into the Mac Pro and there is an eGPU attached, FCPX crashed constantly.  Having the monitor plugged into the eGPU  seemed to have corrected the problem.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
kotlos
(@kotlos)
Trusted Member
Joined: 3 years ago
 

I have this problem with and RX 460 on the MBP 13" 2016 TB and Sierra. FCPX always crushes. I did not have this problem with the Titan X. Has anyone tested the high sierra with FCPX ? 

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
imcalledandy
(@imcalledandy)
Estimable Member
Joined: 3 years ago
 

I've been getting some issues with FCPX too (on Sierra using 980Ti). Everything worked fine a week ago, but I have been trying to get a 3 x eGPU setup working with the nMP, so I must have broken something and need to revert back to a backup. I'll come back if I have anything further to add.

2013 MacPro 2xD700 [email protected] (AKiTiO Thunder2) + macOS 10.13.3
2017 TB MBP 2xGTX1080Ti-TB3 (Akitio Node) + macOS 10.13.4


ReplyQuote
ualwayaslose
(@ualwayaslose)
Active Member
Joined: 3 years ago
 

Same issue happening for me with High Sierra PB6 and AMD RX 570 with Razer Core.

 

Unsure what methods to fix.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote