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

[glofter1]

I'm with 10.14.3, System Z77 / i5-2500 / Sapphire RX 560-4GB. So My IGUP are Disable from bios. I use Waterver + Lilu + Dummy141.
I try SMBIOS 14.2 / 18.3 , right now I'm on 18.3 Graphics are OK but can not understand HEVC / H264 are work or not.
So Video confer show this

In IOReg not show AMDRadeonX4250.
So Is it OK or not ?

Wen I play VLC h264 or HEVC . CPU are load 60W and max freq

 

[shuhung]

I try SMBIOS 14.2 / 18.3 , right now I'm on 18.3 Graphics are OK but can not understand HEVC / H264 are work or not.
So Video confer show this

On 10.14.3, H264 encoder will not work, HEVC encoder work but very unstable.
On 10.14.4 beta1, use SMBIOS iMacPro1,1, both AMD H264 / HEVC GVA encoder work stably.

In IOReg not show AMDRadeonX4250.

From 10.13.4 up, AMDRadeonX4250 no longer exist, now is AMDRadeonX4000.

 

[glofter1]

On 10.14.3, H264 encoder will not work, HEVC encoder work but very unstable.
On 10.14.4 beta1, use SMBIOS iMacPro1,1, both AMD H264 / HEVC GVA encoder work stably.



From 10.13.4 up, AMDRadeonX4250 no longer exist, now is AMDRadeonX4000.

How to use SMBIOS iMacPro1,1 / with boot flags shikigva=32 shiki-id=Mac-7BA5B2D9E42DDD94
or I should change it on config.plist ?

 

[shuhung]

How to use SMBIOS iMacPro1,1 / with boot flags shikigva=32 shiki-id=Mac-7BA5B2D9E42DDD94
or I should change it on config.plist ?

Change SMBIOS to iMacPro1,1 from config.plist, native support hwe420, does not need any shiki boot flags.

 

[apriliars3]

I have full hardware acceleration with AMDRadeonPro.kext in macOS 10.14.3, but VideoProc still freezing with hardware information.

 

[mitch_de]

Independent which Video App you use for encoding tests, it is always good to check which GPU, iGPU or RX 5xxx or both are really used!
You can do this by running INTEL Gadget for looking after usage/load (= full speed MHz) on IGPU and other Tools like HWMonitor2 to look same (load/usage) on RX 5xx card.

Only if you verify that the GPU has much load (=working on encoding) you can be sure that your setting is OK.
Often users think RX is enoding but in reality isnt because iGPU (QSV) did the encoding...

PS:
./VDADecoderChecker
Hardware acceleration is fully supported
Is only for iGPU / QSV check - NOT for normal GPU (RX 5xx ).

It's ****ing beautiful guys.

Radeon RX 580 + 10.14.4-beta1 + dummy141.kext + (boot flags shikigva=32 shiki-id=Mac-7BA5B2D9E42DDD94)

I was able to export my movie from iMovies and use ffmpeg to convert with hardware acceleration.


View attachment 383564

 

[shuhung]

PS:
./VDADecoderChecker
Hardware acceleration is fully supported
Is only for iGPU / QSV check - NOT for normal GPU (RX 5xx ).

VDADecoderChecker only verify GVA H264 not GVA HEVC, work with both IGPU and RX4XX/5XX DGPU.

 

[zakklol]

Independent which Video App you use for encoding tests, it is always good to check which GPU, iGPU or RX 5xxx or both are really used!
You can do this by running INTEL Gadget for looking after usage/load (= full speed MHz) on IGPU and other Tools like HWMonitor2 to look same (load/usage) on RX 5xx card.

Only if you verify that the GPU has much load (=working on encoding) you can be sure that your setting is OK.
Often users think RX is enoding but in reality isnt because iGPU (QSV) did the encoding...

PS:
./VDADecoderChecker
Hardware acceleration is fully supported
Is only for iGPU / QSV check - NOT for normal GPU (RX 5xx ).

This is not the case. It checks for the successful creation of a decoder via VDADecoderCreate(), which can be any supported accelerated decoder that's available. There is no way to tell the API to favor one of the other, the system(AppleGVA) framework determines which hardware decoder to use.

The one it uses is a combination of available hardware, various IORegistry entries, and the system BoardID (AppleGVA contains per-model rules in its Info.plist). I believe it uses the same rules for both the encoder and decoder, WEG/Shiki's forceOfflineRenderer fix/flag can also change which hardware is used for decode.

Generally, if you are using an SMBIOS where the real apple hardware contains an IGPU (even one not connected to anything) it's probably going to favor using the intel hardware unless you use shiki flags to patch out forceOfflineRenderer

Unfortunately there's no API to to tell which hardware the decoder chose

 

[itwas]

This is not the case. It checks for the successful creation of a decoder via VDADecoderCreate(), which can be any supported accelerated decoder that's available. There is no way to tell the API to favor one of the other, the system(AppleGVA) framework determines which hardware decoder to use.

The one it uses is a combination of available hardware, various IORegistry entries, and the system BoardID (AppleGVA contains per-model rules in its Info.plist). I believe it uses the same rules for both the encoder and decoder, WEG/Shiki's forceOfflineRenderer fix/flag can also change which hardware is used for decode.

Generally, if you are using an SMBIOS where the real apple hardware contains an IGPU (even one not connected to anything) it's probably going to favor using the intel hardware unless you use shiki flags to patch out forceOfflineRenderer

Unfortunately there's no API to to tell which hardware the decoder chose

videotoolbox framework is the low-level framework that provides direct access to hardware encoders and decoders.

VideoToolbox
Work directly with hardware-accelerated video encoding and decoding capabilities.

Video Toolbox | Apple Developer Documentation

Work directly with hardware-accelerated video encoding and decoding capabilities.

developer.apple.com

 

[zakklol]

videotoolbox framework is the low-level framework that provides direct access to hardware encoders and decoders.

VideoToolbox
Work directly with hardware-accelerated video encoding and decoding capabilities.

Video Toolbox | Apple Developer Documentation

Work directly with hardware-accelerated video encoding and decoding capabilities.

developer.apple.com

VideoToolBox has no documented API for choosing which hardware decoder to use, nor to find out which one a given session is actually using. It's possible there are undocumented property keys that provided this, but I haven't found them yet.

It has the same limitation as the VDA framework, in that it picks the decoder for you based on the system's setup. I'm pretty sure VDA is just a thin wrapper around VTDecompressionSession anyways.