FCPX Artifacts - High Sierra - RX580 - Skylake

[poorman9]

I'm running OSX 10.13.6 and Final Cut Pro X 10.4.6. H264 encoding is working as expected, sleep/wake, bluetooth, audio, running a 4k monitor with out any issues, no crashes, etc. From the info video on MacX Video Converter I do have Hardware Encoding Supported (see screenshot).

My only issues is during playback in FCPX I get intermittent glitches/artifacts in my viewer (see below). This happens often enough that it interrupts my flow while editing (which is this machine's only purpose).

Hardware specs:

Processor	I7-6700 4.00 GHz - LGA 1151
Graphics Card	MSI RX 580 Armor MK2 8GB
Motherboard	Gigabyte LGA1151 Z170 GA-Z170X-UD5 TH
Ram	Ballistix 64GB Kit (16GBx4) DDR4 2400 MT/s
Wifi/Bluetooth Card	Apple Broadcom BCM94360CD
SSD	Samsung 850 EVO 500GB SSD
Power Supply	EVGA 850 GS, 850W Power Supply

Clover Settings:

Bios Settings:
I have Internal Graphics turned off. I've tried turning them on, but then I can't get H264 encoding to work, or get FCPX to launch.

My config.plist is attached.

I've seen this issue a few times while searching the forums and have tried all the solutions listed in the replies.

 

[pastrychef]

iMac17,1 system definition should have IGPU enabled.

 

[poorman9]

iMac17,1 system definition should have IGPU enabled.

Thanks for the reply. In the bios I've switched Internal Graphics to Enabled. When I do this my machine boots fine, but Final Cut won't launch and throws this error.

Also, under system information I'm not seeing any internal graphics listed. Only the RX580, which make me think there's something else I need to do for my system to see the IGPU – maybe a clover fake ID or ig-platform-id?

Thanks again

 

[pastrychef]

Thanks for the reply. In the bios I've switched Internal Graphics to Enabled. When I do this my machine boots fine, but Final Cut won't launch and throws this error.
View attachment 435736
Also, under system information I'm not seeing any internal graphics listed. Only the RX580, which make me think there's something else I need to do for my system to see the IGPU – maybe a clover fake ID or ig-platform-id?

Thanks again

View attachment 435737

When configured correctly, IGPU should not appear in System Information > Graphics/Display.

Intel HD 530 is natively supported. You should not need to fake any device-id or to set any ig-platform-id.

What kexts do you have in /EFI/CLOVER/kexts/Other/?

Try this config.plist.

 

[poorman9]

When configured correctly, IGPU should not appear in System Information > Graphics/Display.

Intel HD 530 is natively supported. You should not need to fake any device-id or to set any ig-platform-id.

What kexts do you have in /EFI/CLOVER/kexts/Other/?

Try this config.plist.

Thanks for sending that, I've got it loaded up now and have Internal Graphics enabled. Looks like I still have FCP X crashing on start up. When I look into this, I have found a few other hackintoshers with similar IGPU related FCPX crashes, here's three –

Final Cut Pro Crash on Boot
Help! FCP X Crashing on High Sierra/Sierra with my RX 580
FCPX Crash on Launch (Mojave 10.14.1 + RX 580 + i7 6700K)

Here's what's inside of the /EFI/CLOVER/kexts/Other/ directory

 

[pastrychef]

Thanks for sending that, I've got it loaded up now and have Internal Graphics enabled. Looks like I still have FCP X crashing on start up. When I look into this, I have found a few other hackintoshers with similar IGPU related FCPX crashes, here's three –

Final Cut Pro Crash on Boot
Help! FCP X Crashing on High Sierra/Sierra with my RX 580
FCPX Crash on Launch (Mojave 10.14.1 + RX 580 + i7 6700K)

Here's what's inside of the /EFI/CLOVER/kexts/Other/ directory
View attachment 435741

Please try updating AppleALC and Lilu to latest versions and also add WhateverGreen.kext.

Here's an updated config.plist.

 

[poorman9]

Please try updating AppleALC and Lilu to latest versions and also add WhateverGreen.kext.

Here's an updated config.plist.

I'm now running AppleALC 1.4.2, Lilu 1.3.8 and WhateverGreen 1.3.3 (newest versions). With that and your updated config.plist FCPX launches without issue and after scrubbing the timeline and some playback it looks like the artifact issue might be fixed!

I'll give it another day or two and follow up based on some more thorough testing. Thanks so much for the help!

 

[LuiCS507]

I'm now running AppleALC 1.4.2, Lilu 1.3.8 and WhateverGreen 1.3.3 (newest versions). With that and your updated config.plist FCPX launches without issue and after scrubbing the timeline and some playback it looks like the artifact issue might be fixed!

I'll give it another day or two and follow up based on some more thorough testing. Thanks so much for the help!

Did you need InjectIntel>YES?

 

[pastrychef]

Did you need InjectIntel>YES?

Not needed.

 

[poorman9]

After several hours of testing, I haven't had a single playback artifact. Much smoother editing in FCPX now and no other issues to report. Thanks @pastrychef!