- Sep 21, 2013
- Gigabyte Z390 Designare
- i9 9900KS
- RX 580
- Classic Mac
- Mobile Phone
Not sure about spoofing CPU or the need to do that.
There are plenty of folks here with a 9900KS cpu.
You have set your model id to iMacPro1,1.
That system does NOT have an IGPU.
My aging 3770K does have an IGPU BUT I turn it off in the BIOS and use iMacPro1,1.
That's is the only way I can get FCPX (10.4.6) to use the RX580 for encode and decode oh H.264 & HEVC.
VideoProc is a strange one. I get it to work even though it says "Graphics N/A":
View attachment 465466
It actually works pretty well in using the RX580 in transcoding H.264 to HEVC and HEVC to H.264.
See these :
View attachment 465467View attachment 465468
Regarding your config, it's looks like you are NOT using Whatevergreen.kext.
I now use it. It takes care of a lot of issues - Black Screen patch, correct number of video ports, ACPI renaming (GFX0,IGPU,etc), GPU power management just to name a few. If you had an IGPU, it takes of connector-less framebuffers, etc.
Can't tell from your config if you have turned off your IGPU but you may want to try that with iMacPro1,1 model-id you are using.
You have a great CPU so may wish to consider using iMac19,1 that closely matches your system and the IGPU of that CPU is pretty decent for H.264 & HEVC encode/decode too.
Okay, thanks. I'm already using iMP and WEG, etc. I am very pleased with how well FCPX, Compressor, Motion, Resolve, LR6, and CS6 all employ the RX580. The issue was with VideoProc itself. Unless they've updated their software to support MAcOS and AMD, the problem was/is this:
Thanks for contacting us.
I contacted our develop team and the Mac do does not suppport AMD GPU for hardware acceleration at present. And we will add this feature in the near future.
Will you accept a half refund and keep the full version for future use?
Please let us know if we could be of any further assistance.
 I paid for two licenses.
 It didn't work as advertised.
 They only wanted to refund to me half of what I paid.
Conclusion: VideoProc is fine for showing whether hardware acceleration can work in supported software. It just doesn't use the GPU for its own tasks. Run an export from FCPX to Compressor and one will see that the right setup works well. But not VideoProc.