The SSDT method works with my setup which consists of an Asus Prime Z370 A ii, 9600k stock clock, XFX RX 5700, and Headless iGPU on the SMBios iMac19,1.
Weg is active with ShikiGVA=80 and agdpmod=pikera.
Note: I'm using DisplayPort, not HDMI, the connector furthest from the motherboard. I just tried a film in Apple TV+, and Netflix in Safari and DRM
works.
@slim.jim you might find that interesting.
I see a notable increase in GeekBench scores (37k to 66k in Metal, and a jump from 40k to 58k in OpenCL) and if I'm not mistaken the BruceX FCPX test went faster by one second. I'm mainly interested in real world performance in Final Cut Pro X and Compressor, so here's some things I discovered:
I noticed that with CMMChris's kext and no Weg, I was able to convert ProRes to h.264 using QuickTime. While not a very sophisticated method, it's very useful me. Using the SSDT with or without Weg, I ran into the -12912 Error and it stops. This doesn't happen in FCP.
The wording is of the error is "The operation could not be completed An unknown error occurred (-12912)"
Exporting my own ProRes file to h.264 using Compressor, Intel Power Gadget indicates a huge spike in the iGPU
and the CPU - both seem to max out at 4.5ghz and 1.3gz respectively. Transcoding a 6-minute 1080p file takes 1:21.
The same file, sharing out of FCP, takes 1:37. Not a huge difference, but what I noticed is that in Power Gadget, the iGPU shows similar numbers to just playing the Sony HEVC 4k sample at 0.40mhz - which is low. I've concluded that FCPX doesn't use the GPU for outputting h.264. If selecting an h.265 setting via Compressor, iGPU usage fluctuates between about 0.67 and 0.85mhz usage.
None of these tests change the fact that QuickTime gives me an error trying the "Export As">1080p. This isn't a dealbreaker, but this is a super handy feature for how I use my machine. I'm trying to figure out what
@CMMChris's kext does that makes QuickTime exporting work compared to
@mattystonnie's SSDT.
Feel free to throw any more tests my way.