- #FINAL CUT PRO X 10.3.4 CRASH HOW TO#
- #FINAL CUT PRO X 10.3.4 CRASH PATCH#
- #FINAL CUT PRO X 10.3.4 CRASH FULL#
- #FINAL CUT PRO X 10.3.4 CRASH MAC#
#FINAL CUT PRO X 10.3.4 CRASH FULL#
On Gigabyte the the setting is easy to find, but on ASUS, ASRock, MSI motherboard the setting is disguised as IGPU Multi-Monitor. Enabling the iGPU full time is necessary to get Hardware Encoding for FCPX. The next setting is to enabled the iGPU at all times since it’s used by FCPX. The first is setting is changing the Initial or Primary Display/Graphics to either the dGPU or iGPU as leaving it on Auto will cause performance to suffer. In BIOS there are two very important settings that are going to make or break whether you can use FCPX reliability. It’s important that GFX0 -> iGPU is before PEGP -> GFX0 Verify you have the following under DSDT -> Patches.In ist Select Acpi on left-side column of Clover Configurator.Without these patches the fixes in this guide wont persist through sleep and everything will break.
#FINAL CUT PRO X 10.3.4 CRASH PATCH#
HECI -> IMEI Patch is needed in ist in order for the iGPU + dGPU to still function properly after sleep, along with the other two DSDT patches GFX0 -> IGPU and PEGP -> GFX0 patch when you have integrated and dedicated graphics running at the same time. Click or add -disablegfxfirmware under Arguments.Select System Parameters on left-side column.Paste FakePCIID.kext and FakePCIID_Intel_HD_Graphics.kext to EFI/CLOVER/kexts/Other.Copy FakePCIID.kext and FakePCIID_Intel_HD_Graphics.kext from the Release folder of Rehabman-FAKEPCIID.
Download the most recent version of FAKEPCIID.Paste NvidiaGraphicsFixup.kext into EFI/CLOVER/kexts/Other.Download the most recent version of NvidiaGraphicsFixup.kext.Paste WhateverGreen.kext into EFI/CLOVER/kexts/Other.
#FINAL CUT PRO X 10.3.4 CRASH MAC#
FCPX makes use of the Intel CPU/iGPU in conjunction with the dGPU for rendering, so it’s best we try and make use of the iGPU and have it work along side the AMD RX 580 or whatever graphics card the way a real Mac would.Īfter applying the below fixes all my rendering issues went away and my Bruce 5k Test dropped to an insane 9 seconds exporting time in High Sierra 13.2 using these:Īfter mounting the EFI partition we need to make sure we our using the latest version of each of these kexts as they fix various compatibility issues with the latest hardware. These kind of issues are a result of H.264 & H.265 support not being enabled. This is a graphical/encoding/decoding issue that is caused by improper settings not optimized for video editing. What’s the point of building a new hackintosh for video editing if it’s going to perform poorly and can’t even be used to export?įortunately this can be fixed. I’ve been getting a lot of questions asking about poorvideo performance and can see what you guys are talking about.
#FINAL CUT PRO X 10.3.4 CRASH HOW TO#
Here’s how to fix the video rendering issues and performance problems on Intel based Hackintoshes using AMD RX Polaris, Nvidia graphic cards or an iGPU in Final Cut Pro X or any other video encoding/decoding/render processes by enabling hardware encoding and or HEVC support.Ī lot of people seem to have crashing issues with High Sierra and FCPX 10.X on their new Hackintoshes.