Final Cut Pro X (10.3.2) Crashes

[ben1000]

Howdy... I had the same issue with FCP Crashing... I read that disabling the internal graphics card would fix this, and indeed it has done so for me. Now I am using FCP with no issues on my Hackintosh.... The only problem is that to use Intel QuickSync acceleration, you have to have the integrated graphics switched on... But when I do that, FCP crashes... So I'm still looking for a solution that will fix this issue...

Best,

Ben

 

[ben1000]

I had read on the forum that there was a custom Multibeast file that would let you change the name/order of the graphics cards when they loaded, and that this would solve the issue... I'm a newbie and don't really understand all that, but I'd love it if an expert could put it neophyte terms for me...

Best,

Ben

 

[alexjibcam]

For me the perfect fix was to disable integrated graphics in BIOS settings. Now FCP works like a charm.

I second this. Worked for me. Was then about to format my machine for the second time which seemed to fix it the last time around but a real pain. Thankyou th3us3r for this quick fix.

 

[funkyfrank]

If you want to keep sleep mode for AMD gfx, but use FCPX, you can do this:

1. Enable internal intel gfx in bios as primary again

2. Remove / move away all AppleIntelHD* kexts from /Sys/Lib/Ext:

sudo -s
cd /System/Library/
mkdir ExtensionsBackup
mv Extensions/AppleIntelHD* ExtensionsBackup/

Run kext utility.

3. For my Intel HD4600 the Intel Framebuffer "Azul" is loaded (AppleIntelFramebufferAzul, could be Capri for your cpu). This framebuffer kext seems to be responsible for a working sleep mode. Though LuxMark only shows the AMD as available gfx card, and Final Cut Pro X 10.3.4 will work.



Sidenote:
Using a nVidia card + internal iGPU works fine in FCPX, no crashes.

 

[vinste]

I got FCPX 10.3.4 to run perfectly together with iGPU acceleration (h264 encoding and decoding), sleep and boot screen.
Basically, the good ig-platform-id needs to be found, together with some other consistent parameters.
In my case, it is 0x59120003, together with intelGFX at 0x59128086, boot args at -disablegfxfirmware,-shikibeta, inject intel and inject ATI, with SMBIOS at 18,3, Lilu and Shiki, in High Sierra DP6.

 

[Torrijos]

I got FCPX 10.3.4 to run perfectly together with iGPU acceleration (h264 encoding and decoding), sleep and boot screen.
Basically, the good ig-platform-id needs to be found, together with some other consistent parameters.
In my case, it is 0x59120003, together with intelGFX at 0x59128086, boot args at -disablegfxfirmware,-shikibeta, inject intel and inject ATI, with SMBIOS at 18,3, Lilu and Shiki, in High Sierra DP6.

Where / How do I find the proper information for my system, and
How do I inject those values in Clover?

 

[vinste]

Where / How do I find the proper information for my system, and
How do I inject those values in Clover?

You need to try different Ig-platform-id in clover/Graphics. You can first try with 0x59120003 and check if FCPX launches. (set your 7950 as primary gpu in Bios before)

 

[Torrijos]

I've been trying to set this all up with no success...

I my old Chameleon config I had good graphics with
IGPlatformID : 01620005
But I have no idea about the IntelGFX value.

Are there table with those?

 

[zipb]

I got FCPX 10.3.4 to run perfectly together with iGPU acceleration (h264 encoding and decoding), sleep and boot screen.
Basically, the good ig-platform-id needs to be found, together with some other consistent parameters.
In my case, it is 0x59120003, together with intelGFX at 0x59128086, boot args at -disablegfxfirmware,-shikibeta, inject intel and inject ATI, with SMBIOS at 18,3, Lilu and Shiki, in High Sierra DP6.

Have you upgraded to OSX.13.1 and does FCPX 10.3.4 still work for you? For me, FCP worked OK on 10.13, but crashes all the time on 10.13.1
Looking for a solution.

 

[vinste]

Have you upgraded to OSX.13.1 and does FCPX 10.3.4 still work for you? For me, FCP worked OK on 10.13, but crashes all the time on 10.13.1
Looking for a solution.

Yes, FCPX still works in 10.13.1
If you use clover, you can post your EFI folder, I will have a look (and your clover version)