Contribute
Register

Radeon Compatibility Guide - ATI/AMD Graphics Cards


Thank you for the reply and the suggestion, but its offbeat the second GPU dont show any video feed..
Even with Whatevergeen v1.3.3 & Lilu v1.3.8 the boot flags "agdpmod=pikera" / "agdpmod=vit9696"
Or even using a SSDT with the data from IORegistryExplorer.

When activating the TB3 trough Windows the second GPU gives on all ports a video feed.. So it's not broken..
And in 10.14 in the monitor tab in this "about this mac" + System overview shows exactly the monitor details attached to second GPU.

I have also tried to changed the SMBIOS to a 6.1 version for testing , but also the same problem.. :problem:
If needed I have to purchase a eGPU for the Radeon VII if that works hopefully !

The benefit of this is then, I can also put the FW PCIe card back for my external soundcard..
Otherwise I need also to upgrade my motu 828 FW to a TB3 soundcard :lol:
 
Hello, I just reasently installed Catalina 10.15.1 into my system, using default product name of iMac 14,2 model name, have Lilu and Whatevergeen kexts installed into Clover bootloader folder. In about my mac Graphics: Radeon RX 580 8 GB looks okay
Under system report is
Radeon RX 580:

Chipset Model: Radeon RX 580
Type: GPU
Bus: PCIe
PCIe Lane Width: x16
VRAM (Total): 8 GB
Vendor: AMD (0x1002)
Device ID: 0x67df
Revision ID: 0x00e7
Metal: Supported, feature set macOS GPUFamily2 v1
Displays:
LG ULTRAWIDE:
Resolution: 3840x1600 (Ultra-wide 4K)
UI Looks like: 3840 x 1600 @ 60 Hz
Framebuffer Depth: 30-Bit Colour (ARGB2101010)
Main Display: Yes
Mirror: Off
Online: Yes
Rotation: Supported
Automatically Adjust Brightness: No
Connection Type: DisplayPort
Television: Yes

Also looks good, but when I'm using Davinci Resolve 16 the CPU is max loaded and GPU slightly touched. In Mojave Davinci Resolve 16 GPU used about 60-70%, what can I say rom activity monitor, also Davinci Resolve crashing a lot.

Is any way to check is my GPU is fully working?
 
Good evening guys, I have a question and any help is welcome. When I connect the screen to my hackintosh with dvi cable then I have the night shitft, but when I connect it to hdmi then the night shift disappears. Any ideas on how to get it out of the dvi cable again? My graphics card is the XFX RX570 8Gb, and the MacOSX Catalina.
Thank you very much in advance.
 
Good evening guys, I have a question and any help is welcome. When I connect the screen to my hackintosh with dvi cable then I have the night shitft, but when I connect it to hdmi then the night shift disappears. Any ideas on how to get it out of the dvi cable again? My graphics card is the XFX RX570 8Gb, and the MacOSX Catalina.


@babis306,

Not sure why the option disappeared for you ....
You could try installing the NightShiftUnlocker Lilu plugin :-



It might help ...

Cheers
Jay
 
Avoid XFX in general.

I know you've done a lot of testing in FCPX.. In this post, the poster says that with iMacPro1,1 system definition and IGPU disabled, HEVC export is not accelerated. Has this been your experience as well?
 
I know you've done a lot of testing in FCPX.. In this post, the poster says that with iMacPro1,1 system definition and IGPU disabled, HEVC export is not accelerated. Has this been your experience as well?

Last time I checked FCPX, both HEVC and H264 were accelerated with iMac Pro 1,1 SMBIOS. Since my main system doesn't have IGPU, I can't test with it enabled/disabled.

Let me know if you'd like me to test anything with the current system and FCPX.
 
Last time I checked FCPX, both HEVC and H264 were accelerated with iMac Pro 1,1 SMBIOS. Since my main system doesn't have IGPU, I can't test with it enabled/disabled.

Let me know if you'd like me to test anything with the current system and FCPX.

I was just wondering if what he was reporting was isolated to his build or if it happens to everyone.

According to his findings, with iMacPro1,1 system definition and IGPU disabled in BIOS:
  • FCPX HEVC encode is NOT accelerated. (It doesn't crash or anything. Just HEVC exports are slower than they should be.)
  • HEVC encode encode is enabled in QuickTime.
  • VideoProc reports HEVC working.
He also reported that using iMacPro1,1 with IGPU enabled in BIOS allows FCPX HEVC exports to be significantly faster.

If all of this is true for everyone, I will have to change my recommendations to other users.
 
I was just wondering if what he was reporting was isolated to his build or if it happens to everyone.

According to his findings, with iMacPro1,1 system definition and IGPU disabled in BIOS:
  • FCPX HEVC encode is NOT accelerated. (It doesn't crash or anything. Just HEVC exports are slower than they should be.)
  • HEVC encode encode is enabled in QuickTime.
  • VideoProc reports HEVC working.
He also reported that using iMacPro1,1 with IGPU enabled in BIOS allows FCPX HEVC exports to be significantly faster.

If all of this is true for everyone, I will have to change my recommendations to other users.

Here are some tests and hope this helps and gives you some extra information. As mentioned, my system is X299 and does not have an iGPU so I don't have anything else to test. I guess I can cross reference on my MacBook Pro (2018, 6core)?

I believe the lack of HEVC hardware encoding has something to do with the T2 chip (which has its own H264/HEVC encoder/decoder and it's own basic OS), especially on the iMac Pro 1,1 SMBIOS when iGPU is disabled. macOS does different things to different SMBIOses behind the scenes. If it doesn't see a T2 chip, it just fallbacks to CPU perhaps? In the compressor preferences there is a setting to use multiple instances of the processor cores, and you can max out all the CPU during exporting, which will increase speeds.

It's more surprising to me that the Radeon VII isn't taken advantage of even by Adobe Media Encoder, because it's such a good computational card. If Apple supports eGPU's natively (and officially), then I am not sure why performance isn't pushed to the limit on these cards.

I think what happened was Apple had tapped into the Intel QuickSync tech for a while and got tired of it so when they developed their own T2 chip, they threw hardware encoder/decoders in there so in the future when all Macs have a T2 chip, they don't have to rely on AMD/NVIDIA/Intel for H264/HEVC decoding/compression. This means more control to them and less reliance on external companies...and also an easier transition to the ARM architecture? But I am just guessing here, because the AMD Radeon VII and the other recent cards like NAVI ones have great onboard HEVC/H264 encoder/decoders...Applications such as Davinci Resolve do take advantage of these other GPUs.

Hope this helps.


Latest FCPX shows Radeon VII:
RadeonVIIFCPX.png


FCPX H264 export uses GPU (but not at 100%, and it is not loading the CPU):
FCPX_H264.png




FCPX HEVC 8Bit export doesn't seem to use GPU, but uses CPU instead:
FCPX_HEVC_4k_8Bit.png


FCPX HEVC 10Bit export (through compressor, with GPU enabled) doesn't seem to use GPU, but uses CPU instead:
FCPX_HEVC_4K_10Bit.png


Adobe Media Encoder CC2019 for H264 (with hardware enabled in settings, and OpenCL, since Metal is slower) uses GPU (but not at 100%):
AME_H264_4k.png


Adobe Media Encoder CC2019 for HEVC (with hardware enabled in settings, and OpenCL, since Metal is slower) uses GPU (but not at 100%):
AME_HEVC_4k.png


QuickTime Player H264 exporter uses GPU but at a very low amount:
QT_H264_4k.png


QuickTime Player HEVC exporter uses GPU but at a very low amount:
QT_HEVC_4k.png



Davinci Resolve 16 H264 heavily uses GPU for export:
RESOLVE_H264_4k.png


Davinci Resolve 16 HEVC heavily uses GPU for export:

RESOLVE_HEVC_4k.png


VideoProc sees both H264 and HEVC:
VideoProc.png
 

Attachments

  • FCPX_HEVC_4k_8Bit.png
    FCPX_HEVC_4k_8Bit.png
    193.3 KB · Views: 60
Last edited:
Back
Top