Contribute
Register

Radeon Compatibility Guide - ATI/AMD Graphics Cards

jaymonkey

Moderator
Joined
Aug 27, 2011
Messages
3,895
Motherboard
ASRock-Z97 EX6
CPU
i7-4790K OC @ 4.8GHz
Graphics
Vega 64LC + HD4600
Mac
  1. MacBook Air
  2. MacBook Pro
Mobile Phone
  1. Android
  2. iOS
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
 
Joined
Aug 17, 2011
Messages
12
Motherboard
Gigabyte Z370-HD3P
CPU
i5-8400
Graphics
RX 570
Mac
  1. iMac
Mobile Phone
  1. Android
@babis306,

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



It might help ...

Cheers
Jay

It didn't help.......
 

pastrychef

Moderator
Joined
May 29, 2013
Messages
16,442
Motherboard
Gigabyte Z390 M Gaming
CPU
i9-9900K OC'd @ 5.0GHz
Graphics
Vega 56 (Bios flashed to 64)
Mac
  1. MacBook
  2. Mac Pro
Classic Mac
  1. iBook
  2. Power Mac
  3. PowerBook
Mobile Phone
  1. iOS
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?
 
Joined
Feb 24, 2013
Messages
2,545
Motherboard
ASUS WS X299 SAGE/10G
CPU
i9-9980XE
Graphics
Radeon VII
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
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.
 

pastrychef

Moderator
Joined
May 29, 2013
Messages
16,442
Motherboard
Gigabyte Z390 M Gaming
CPU
i9-9900K OC'd @ 5.0GHz
Graphics
Vega 56 (Bios flashed to 64)
Mac
  1. MacBook
  2. Mac Pro
Classic Mac
  1. iBook
  2. Power Mac
  3. PowerBook
Mobile Phone
  1. iOS
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.
 
Joined
Feb 24, 2013
Messages
2,545
Motherboard
ASUS WS X299 SAGE/10G
CPU
i9-9980XE
Graphics
Radeon VII
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
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: 29
Last edited:

pastrychef

Moderator
Joined
May 29, 2013
Messages
16,442
Motherboard
Gigabyte Z390 M Gaming
CPU
i9-9900K OC'd @ 5.0GHz
Graphics
Vega 56 (Bios flashed to 64)
Mac
  1. MacBook
  2. Mac Pro
Classic Mac
  1. iBook
  2. Power Mac
  3. PowerBook
Mobile Phone
  1. iOS
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 adn 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:
View attachment 435602

FCPX H264 export uses GPU (but not at 100%, and it is not loading the CPU):
View attachment 435603



FCPX HEVC 8Bit export doesn't seem to use GPU, but uses CPU instead:
View attachment 435605

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

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

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

QuickTime Player H264 exporter uses GPU but at a very low amount:
View attachment 435609

QuickTime Player HEVC exporter uses GPU but at a very low amount:
View attachment 435610

VideoProc sees both H264 and HEVC:

View attachment 435611

Ah yes!! I completely forgot about how the T2 factors in... That makes perfect sense! Thank you!
 
Joined
Feb 24, 2013
Messages
2,545
Motherboard
ASUS WS X299 SAGE/10G
CPU
i9-9980XE
Graphics
Radeon VII
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
Ah yes!! I completely forgot about how the T2 factors in... That makes perfect sense! Thank you!

No problem!

I edited the post and added Davinci Resolve 16 results, and it's definitely using the AMD HEVC/H264 engine to almost it's full potential.

So the culprits here are:

  • Lack of T2 chip
  • Lack of iGPU (in my system, or when disabled)
  • Hardware-tied applications like FCPX (ie it looks for T2/Intel QuickSync and ignores AMD)
  • Lack of performance improvements for Adobe (they suck!)

What IS interesting is, for example in FCPX, when I enabled stabilization on a 1 minute clip, the GPU usage shot up to 100% on the Radeon VII! So it is indeed using the GPU, just not for HEVC exports (H264 it uses it, but not at 100%). Which makes sense.
 

pastrychef

Moderator
Joined
May 29, 2013
Messages
16,442
Motherboard
Gigabyte Z390 M Gaming
CPU
i9-9900K OC'd @ 5.0GHz
Graphics
Vega 56 (Bios flashed to 64)
Mac
  1. MacBook
  2. Mac Pro
Classic Mac
  1. iBook
  2. Power Mac
  3. PowerBook
Mobile Phone
  1. iOS
No problem!

I edited the post and added Davinci Resolve 16 results, and it's definitely using the AMD HEVC/H264 engine to almost it's full potential.

So the culprits here are:

  • Lack of T2 chip
  • Lack of iGPU (in my system, or when disabled)
  • Hardware-tied applications like FCPX (ie it looks for T2/Intel QuickSync and ignores AMD)
  • Lack of performance improvements for Adobe (they suck!)

What IS interesting is, for example in FCPX, when I enabled stabilization on a 1 minute clip, the GPU usage shot up to 100% on the Radeon VII! So it is indeed using the GPU, just not for HEVC exports (H264 it uses it, but not at 100%). Which makes sense.

I know you are on X299, but the original poster reported that by using iMacPro1,1 system definition and ENABLING IGPU in BIOS, he got accelerated HEVC exports in FCPX. So it seems that FCPX itself will use T2 if available and, if not, it will look for QuickSync but it will not use dGPU for HEVC encode.
 
Joined
Feb 24, 2013
Messages
2,545
Motherboard
ASUS WS X299 SAGE/10G
CPU
i9-9980XE
Graphics
Radeon VII
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
I know you are on X299, but the original poster reported that by using iMacPro1,1 system definition and ENABLING IGPU in BIOS, he got accelerated HEVC exports in FCPX. So it seems that FCPX itself will use T2 if available and, if not, it will look for QuickSync but it will not use dGPU for HEVC encode.

Yeah, I think it falls back to iGPU when it doesn't see a T2 chip for HEVC...so it goes in this order:

T2 > iGPU > CPU

I just don't get why it uses AMD for H264 (even if it's only 30%?)...really weird and messy.

Eventually T2 (or whatever new name they'll use) will be included in all Macs. macOS Catalina still supports non T2 supported Macs, so I assume Apple is just keeping iGPU support until they don't have to. Maybe they will even dump Intel QuickSync support when they all supported Macs have T2 chips.
 
Top