Contribute
Register

Radeon RX 4XX/5XX standalone system, AMDRadeonX4250.kext (GVA support H264) does not support HEVC HW

Status
Not open for further replies.
Yes has been known a while back as the Mac Pro's do not have IGPU's.
My comment/question was regarding the new iMacPro's with the AMD GPU's.
If I spent $13k on an iMacPro, I'd expect it to be able to do a very good job producing H.264 output and quickly !
This is just the output of H264. If you add complex effects to video editing, the Mac Pro will demonstrate the absolute advantages of Xeon.
 
i have similar problem

i can export h.265 (compressor/fcpx) in both 8 or 10 bits

i cannot export h.264 (compressor/fcpx)

i do not have igpu, using all the config listed in https://www.tonymacx86.com/threads/...c-pro-successful-build-extended-guide.229353/

I dont need h.265 as much as I need h.264 working

Could you please give advice?

Issue should related to IOGVACodec, no matter use AMDU7V4 or AMDU6V3, FCPX share as H264 still failed, finally remove key IOGVACodec from dummy kext info.plist, so far so good, except AirPlay no longer show up in Display Preference.

Try change device ID to 0x67EF, on 10.13.4 IOGVACodec still not enabled in AMDBaffinGraphicsAccelerator, FCPX share as H264 should work.
Old Fake ID method easy cause black screen issue, do not inject ATI / FB name, use ssdt or Clover / Devices / Arbitrary for device ID injection, see below sample.
upload_2018-4-23_20-51-44.png


If OK, then use dummy kext re-enable AMD HEVC support.
 
Last edited:
Worked for me! Thanks.
With compressor the only export label "red" as non available is HEVC 8bit.
Export of H264 is not fast as quicksync but works and I can keep disable the iGpu.
Thanks!
A.


Issue should related to IOGVACodec, no matter use AMDU7V4 or AMDU6V3, FCPX share as H264 still failed, finally remove key IOGVACodec from dummy kext info.plist, so far so good, except AirPlay no longer show up in Display Preference.

Try change device ID to 0x67EF, on 10.13.4 IOGVACodec still not enabled in AMDBaffinGraphicsAccelerator, FCPX share as H264 should work.
Old Fake ID method easy cause black screen issue, do not inject ATI / FB name, use ssdt or Clover / Devices / Arbitrary for device ID injection, see below sample.
View attachment 327315

If OK, then use dummy kext re-enable AMD HEVC support.
 
With compressor the only export label "red" as non available is HEVC 8bit.

When using device-id 0x67EF, AMDBaffinGraphicsAccelerator will load, it does not natively support AMD HEVC need dummy kext to enable AMD HEVC. Below injection method from other site work well.
upload_2018-5-3_5-47-10.png


See attached dummy kext sample.
 

Attachments

  • Dummy.kext.zip
    1 KB · Views: 261
Hi Shunhung,
I assume that I have to put the dummy kext under /other in clover efi. Right?
I noticed another thing: in Geekbench 4 my OpenCl score dropped form 140.000 to 100.000 since I disabled the iGpu and eraased Lilu+WG. I had to disable iGpu due to not proper sleep/awake and black screen at start. I removed every FB and now Geekbench says I have an "AMD Radeon HD Baffin Unknown Prototype" :)
Thanks a lot!
A.


When using device-id 0x67EF, AMDBaffinGraphicsAccelerator will load, it does not natively support AMD HEVC need dummy kext to enable AMD HEVC. Below injection method from other site work well.
View attachment 329238

See attached dummy kext sample.
 
Issue should related to IOGVACodec, no matter use AMDU7V4 or AMDU6V3, FCPX share as H264 still failed, finally remove key IOGVACodec from dummy kext info.plist, so far so good, except AirPlay no longer show up in Display Preference.

Try change device ID to 0x67EF, on 10.13.4 IOGVACodec still not enabled in AMDBaffinGraphicsAccelerator, FCPX share as H264 should work.
Old Fake ID method easy cause black screen issue, do not inject ATI / FB name, use ssdt or Clover / Devices / Arbitrary for device ID injection, see below sample.
View attachment 327315

If OK, then use dummy kext re-enable AMD HEVC support.

thanks for your advice, sadly im not able to change the device id. im little new to clover patching etc...
after finding my PciAddr of 193:0.0 (hope that is right...pcidebug) if i inject EF670000 nothing happens, upon inspection in ioreg i have still the same device-id under GFX0@0, that is DF670000
 
I assume that I have to put the dummy kext under /other in clover efi. Right?

Yes, place it to Clover/kexts/Other.

I noticed another thing: in Geekbench 4 my OpenCl score dropped form 140.000 to 100.000 since I disabled the iGpu and eraased Lilu+WG. I had to disable iGpu due to not proper sleep/awake and black screen at start. I removed every FB and now Geekbench says I have an "AMD Radeon HD Baffin Unknown Prototype"

It just a temporary workaround, some features may be missing, if OpenCL performance drop after video playback, quit all video player apps and Safari, clear apps cache by put computer to sleep, after system wakeup, OpenCL performance will be normal.
 
thanks for your advice, sadly im not able to change the device id.

Try attached dummy kext, HEVC support for AMDBaffinGraphicsAccelerator enabled, swap RX device ID lists between AMDBaffinGraphicsAccelerator and AMDEllesmereGraphicsAccelerator, place it to Clover/kexts/Other.
 

Attachments

  • swapID.kext.zip
    1.3 KB · Views: 357
Try attached dummy kext, HEVC support for AMDBaffinGraphicsAccelerator enabled, swap RX device ID lists between AMDBaffinGraphicsAccelerator and AMDEllesmereGraphicsAccelerator, place it to Clover/kexts/Other.

you fixed it thank you!
im gonna dive into that ssdt/aml/ioreg soon and hopefully will manage next time

btw do you think this problem is the same for vega graphics?
 
Status
Not open for further replies.
Back
Top