Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 Activate AMD hardware acceleration
- Thread starter h9826790
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
For now it's just a possibility, lot's of things are being developed, but no one succeed with HEVC acceleration with Catalina yet.
Remembering that Clover is not compatible with MP5,1, and shouldn't be used at all unless you can repair bricked SPI, so we are looking at OpenCore.
After update Mojave 10.14.6 and follow the #1 method, VideoProc says H.264 HW Encode and Decode is enabled. Kexts are loaded. Yesterday JellyFish-300mpbs-4k-uhd-hevc-10bit test file burn my system, today it works like a charm 
I thought that my CPUs are Nehalem (E5520 2.26).
By the way, I have no audio problem both built-in speaker output and DisplayPort Monitor output. Am I missing something?
I thought that my CPUs are Nehalem (E5520 2.26).
By the way, I have no audio problem both built-in speaker output and DisplayPort Monitor output. Am I missing something?
Correcting my previous error, Gainestown is the family name for Nehalem-EP processors with dual QPI made for dual socket servers/workstations. Gulftown are the Westmere-EP processors for with dual QPI made for dual socket servers/workstations, you need these if you want to run Mojave.After update Mojave 10.14.6 and follow the #1 method, VideoProc says H.264 HW Encode and Decode is enabled. Kexts are loaded. Yesterday JellyFish-300mpbs-4k-uhd-hevc-10bit test file burn my system, today it works like a charm
I thought that my CPUs are Nehalem (E5520 2.26).
By the way, I have no audio problem both built-in speaker output and DisplayPort Monitor output. Am I missing something?
Yes, all dual processor Nehalem-EP processors are not supported anymore with Mojave and have stuttering audio after 10.14.3, when Apple removed support for Nehalem-EP/Gainestown Xeons.
[automerge]1571825768[/automerge]
@miracatici Strange Audio Issue on MP 4,1>5,1 Mojave 10.14.4
Last edited:
Well, luckily I have no such a problem.
However, I have no improvement on Adobe Premiere Pro. All my videos are ARRI 3424x2202 (3.4k OpenGate). Mercury Playback - Metal is selected. While I'm exporting the video with H.264 1080p settings, all works is done on my CPU, not GPU. So rendering time is too much. Is there any experienced about that?
However, I have no improvement on Adobe Premiere Pro. All my videos are ARRI 3424x2202 (3.4k OpenGate). Mercury Playback - Metal is selected. While I'm exporting the video with H.264 1080p settings, all works is done on my CPU, not GPU. So rendering time is too much. Is there any experienced about that?
High Sierra or Mojave? Video acceleration only works correctly with 10.14.5 or 10.14.6.Well, luckily I have no such a problem.
However, I have no improvement on Adobe Premiere Pro. All my videos are ARRI 3424x2202 (3.4k OpenGate). Mercury Playback - Metal is selected. While I'm exporting the video with H.264 1080p settings, all works is done on my CPU, not GPU. So rendering time is too much. Is there any experienced about that?
Mojave 10.14.6, Premiere Pro 13. However, I thought that is highly correlated with video codec.
Well, luckily I have no such a problem.
However, I have no improvement on Adobe Premiere Pro. All my videos are ARRI 3424x2202 (3.4k OpenGate). Mercury Playback - Metal is selected. While I'm exporting the video with H.264 1080p settings, all works is done on my CPU, not GPU. So rendering time is too much. Is there any experienced about that?
What's your export setting? If may be easier to find out the reason if you can provide the export settings screen capture
@miracatici Are you using AME or PPro for your exports/conversions? Do you convert or process footage on intake at all?
According to Adobe support when dealing with an NVIDIA issue on the previous OS and versions, the Mercury engine on MP5,1 machines mainly does all scaling functions and leaves the CPU for the actual encode through AME. If you export to AME from PPro, there are some additional things that can be accelerated. Personally avoid doing that whenever possible. Prefer to render timeline in PPro, export matching timeline settings, then bulk/batch in AME when possible.
If you're stacking ANY effects on your timeline or footage, make sure those are GPU accelerated. Remember: even color correction is an effect layer.
According to Adobe support when dealing with an NVIDIA issue on the previous OS and versions, the Mercury engine on MP5,1 machines mainly does all scaling functions and leaves the CPU for the actual encode through AME. If you export to AME from PPro, there are some additional things that can be accelerated. Personally avoid doing that whenever possible. Prefer to render timeline in PPro, export matching timeline settings, then bulk/batch in AME when possible.
If you're stacking ANY effects on your timeline or footage, make sure those are GPU accelerated. Remember: even color correction is an effect layer.
It's audio stuttering, not video. W3680 is a Gulftown/Westmere Xeon, those are still supported, and it's a single socket processor. Only Gainestown Xeons (x55xx), installed in dual CPU trays have the problem.
OMG, this is awesome. Got a RX580 today to get rid of my Nvidida GTX680. The GTX680 took 9 hours to render a 4k (60FPS) 90 min clip. Testing the RX580 today I got the same render time 9hours. After activating hardware acceleration the render of the video only takes 2,5 hours which is awesome!
Now I almost want to put my old GTX680 inside and see how much better it runs.
Thank you so much for this!
Now I almost want to put my old GTX680 inside and see how much better it runs.
Thank you so much for this!
glad to see you got a great improvement!
The GTX 680 wont run any different than before.
This hardware acceleration is ONLY for AMD cards.
One question about SIP. Does it need to be turned off only while activating hardware acceleration or can I enable it after?
If you're using the hex edit method, you turn SIP off, do the hex edit, and then you can turn it back on. That's what I did.
Hello everyone, noob here, I have a Mac Pro 5,1 running Catalina (I'd be fine with no HEVC, just h264), with the following specs:
CPU: 2 x 2,4 GHz Intel Xeon quad-core
RAM: 20GB 1066 mhz DDR3
GPU: Radeon RX 560 4 GB
Boot disk: Samsung 840 Evo SSD
I just tried the standard method to enable hardware acceleration but without success, as I still can't seem to make the GPU work... I'll try the alternative, more complicated method in the future, but just as a test I tried to convert a 70GB 4K HEVC file into a 1080p H264 one using Handbrake's x264 video option, and it's averaging under 12fps, while my late 2013 MacBook Pro Retina (2,3 Ghz quad core i7, 16GB RAM, Nvidia GT750M 2GB), converting the same file to 1080p H264 using Handbrake's h264 Video ToolBox option is averaging just under 18fps, and in activity monitor the GPU is basically not doing anything, so it's all CPU work.
I know the Mac Pro is old, but shouldn't it perform better anyway?
Is Video ToolBox the best option if you want to decode/encode using the GPU? Is it not compatible with my MacBook Pro's GPU?
CPU: 2 x 2,4 GHz Intel Xeon quad-core
RAM: 20GB 1066 mhz DDR3
GPU: Radeon RX 560 4 GB
Boot disk: Samsung 840 Evo SSD
I just tried the standard method to enable hardware acceleration but without success, as I still can't seem to make the GPU work... I'll try the alternative, more complicated method in the future, but just as a test I tried to convert a 70GB 4K HEVC file into a 1080p H264 one using Handbrake's x264 video option, and it's averaging under 12fps, while my late 2013 MacBook Pro Retina (2,3 Ghz quad core i7, 16GB RAM, Nvidia GT750M 2GB), converting the same file to 1080p H264 using Handbrake's h264 Video ToolBox option is averaging just under 18fps, and in activity monitor the GPU is basically not doing anything, so it's all CPU work.
I know the Mac Pro is old, but shouldn't it perform better anyway?
Is Video ToolBox the best option if you want to decode/encode using the GPU? Is it not compatible with my MacBook Pro's GPU?
The 2013 mbp is using Intel Quicksync through video toolbox which uses the integrated gpu to speed up the encode time. The thread kext when properly applied under Mojave allows you to use your Polaris GPU in your Mac Pro with video toolbox. This should beat the 2013 mbp which doesn't use the GT 750M at all. YMMV on Catalina.
Last edited:
Not supported, at least at this time.
I have a MP4/5,1, 32 GB, and single 6x3.33 x5680, 580 w/8GB. My late 2013 top spec regularly keeps up with and even surpasses in various encoding tasks. Watching Activity Monitor, it does appear that the 2 onboard gpu's are working in tandem. But, with the hex method and proper encoding settings, the MP is now the one to beat. No contest.
The latest security update (18G1012) will revert the hex edited AppleGVA.framework. You can either backup the patched one, replace the new one with the patched version. Or perform another hex edit to the new one (safer).
Last edited:
Finally, FULL HWaccel achieved (including HEVC hardware encode)
The exact condition still unknown due to few variables exist.
My understanding so far. The requirements are
1) OpenCore
2) Inject iMac Pro SMBIOS (via OpenCore)
3) Rename the graphic card APCI name to GFX0 (via OpenCore)
Since we ident the cMP as iMac Pro 1,1 now. There is no need to patch the AppleGVA framework anymore.
However, I am not 100% sure if WhateverGreen still require (boot argument is 100% not required anymore, but the existence of WhateverGteen may be crucial)
The exact condition still unknown due to few variables exist.
My understanding so far. The requirements are
1) OpenCore
2) Inject iMac Pro SMBIOS (via OpenCore)
3) Rename the graphic card APCI name to GFX0 (via OpenCore)
Since we ident the cMP as iMac Pro 1,1 now. There is no need to patch the AppleGVA framework anymore.
However, I am not 100% sure if WhateverGreen still require (boot argument is 100% not required anymore, but the existence of WhateverGteen may be crucial)
I look forward to one of your awesome detailed guides on the full process (when you are finished testing, and have the time of course)...