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
Interestingly, I'm getting a crash from FCPX now when starting up saying it's quitting unexpectedly while using the AppleGVA plug-in. This may be because I'm sitting merging HDR images in Lightroom too, but have a crash report here anyway
I'm curious... I assume sidecar requires HW accelerated encoding in the Mac in order to push the virtualized screen to an iPad.
Does the patch work in Catalina (with a RX580 or similar) to allow a cMP to use sidecar?
I've seen mention it works over either BT 4 (which would require a new Wifi/BT card) or over a direct cable.
Does the patch work in Catalina (with a RX580 or similar) to allow a cMP to use sidecar?
I've seen mention it works over either BT 4 (which would require a new Wifi/BT card) or over a direct cable.
Thanks for the report.
According to you’re signature, that’s a RX580, correct?
And you mean you are using the WhateverGreen plugin, right?
Also, with 10.14.5?
I am now running 10.14.6 DP3, with the hex edit method. Literally zero stability issue. I performed lots of tests. It seems this combination is very solid.
If you want a more stable setup. You may consider this. Especially this kind of .1 update (OS) is mainly bug fix, often run better than the previous official release.
No, sidecar need HEVC hw encoding. Which is actually the only missing puzzle for us now.
And I tried both WhateverGreen and Hex edit method. None of them has any effect. (The AppleGVA.framework changed quite a bit, may need to mod another file. I will look into that later).
However, this is a very early stage beta, most likely Lilu and WhateverGreen also need time to update to become fully compatible to Catalina. So, the hope still there.
RX580, 10.14.5 and hexedit, started getting lockups with Lilu/Whatevergreen, so the DP of the latest update is the only difference, and didn't think there were any updates to AppleGVA ...
For the past week, I've been running the Mac Pro with the hardware acceleration with no issues. I thought the problem went away.
Until last night, when I fired up Final Cut Pro X.
Did a quick playback of timeline, scrubbed back to play another section and bam! Unresponsive Mac requiring hard reboot.
This morning, I got my second crash just browsing the web.
(Random notes: I know my Bluetooth Magic Mouse occasionally disconnects, and remember doing a good 3x PRAM reset last week. Would disconnecting bluetooth mouse cause crash? I also had disconnected my Luna Display Dongle as a troubleshooting step last week also.)
Can't wait to try 10.14.6.
Until last night, when I fired up Final Cut Pro X.
Did a quick playback of timeline, scrubbed back to play another section and bam! Unresponsive Mac requiring hard reboot.
This morning, I got my second crash just browsing the web.
(Random notes: I know my Bluetooth Magic Mouse occasionally disconnects, and remember doing a good 3x PRAM reset last week. Would disconnecting bluetooth mouse cause crash? I also had disconnected my Luna Display Dongle as a troubleshooting step last week also.)
Can't wait to try 10.14.6.
After running the Lilu mod for some time without issues, I wanted to try the Hex method. Unfortunately, it did not work for me, using the Jellyfish video as the indicator. I did verify that the video could be played, then after NVRAM reset and disabling SIP, again verifying that the Jellyfish video would no longer play.
With my very light hex editing skills, I duplicated the Apple GVA framework, downloaded iHex from the App Store, and find and replace the 2 instances. But, I was unable to save the file. Instead, I saved to a different name, then renamed in Finder. As well, I was unable to save the plist, so saved and renamed there, too.
On restart, the Jellyfish video runs perfectly - the first time. It does not run properly after that, until a reboot. And when I try and use Handbrake/FreeSolo (see #266) and select H.264 (VideoToolBox) the encode fails.
I'm pretty sure this is pilot error on my part, since many others have successfully enabled this method. Any ideas? One thought is the original AppleGVA file within the framework is an alias, and when I saved the file as a different same and then renamed, the resulting file was no longer an alias.
With my very light hex editing skills, I duplicated the Apple GVA framework, downloaded iHex from the App Store, and find and replace the 2 instances. But, I was unable to save the file. Instead, I saved to a different name, then renamed in Finder. As well, I was unable to save the plist, so saved and renamed there, too.
On restart, the Jellyfish video runs perfectly - the first time. It does not run properly after that, until a reboot. And when I try and use Handbrake/FreeSolo (see #266) and select H.264 (VideoToolBox) the encode fails.
I'm pretty sure this is pilot error on my part, since many others have successfully enabled this method. Any ideas? One thought is the original AppleGVA file within the framework is an alias, and when I saved the file as a different same and then renamed, the resulting file was no longer an alias.
Seems you have the permission issue.
If can't follow the exact steps in post #205.
Then after step 4, copy the AppleGVA.framework to your desktop, mod it at there.
After step 14, copy this modded file back into System/Library/PrivateFrameworks.
And do all 24 steps.
Just checking - you mention before step 22:
>>Optional steps to repair all modified files' permission (NOT tested on my own system yet, use at your own risk.
Do you recommend completing steps 22-24 to reset permissions?
Yes, and don't worry, I tested these extra steps already, will update that part now.
(Quoting myself here, I know)
I think I've found where I went wrong... I didn't use the method in the post to make a copy of the framework, I'd done it using terminal, however, if you do it this way, some symlinks (aliases for those not familiar with UNIX filesystems) aren't preserved, and this is what I think is messing me up. *IF* you decide to do it this way, use cp -R (Capital R) on it, as this will preserve them, I've redone things this way and Final Cut is happy again, about to install the public beta of 10.14.6 though
Once I did this correctly, it worked - thanks!
Question: does this need to happen on the same drive you boot from? I tried booting from an HS drive, and editing the Mojave drive. But after completing the steps the login screen didn't show for Mojave on reboot. I finally tried booting into Mojave, and it was successful. Is that a requirement?
Last edited:
My procedures assume you mod the files directly from the boot drive.
If you mod from another drive, more likely you will have permission issue.
Confirmed this mod still works in 10.14.6 DP4. Again, nothing more, nothing less, still no HEVC hardware encode.
Both 10.14.6 DP2 and DP3 has zero crash / freeze (GPURestart) with RX580 on my cMP. And now, let's see if DP4 can keep the stability.
So far, my personal recommended combination for RX580 is "10.14.6 DP3 + Hex edit". This combination is so stable that I don't want to further update my primary boot drive actually. But I still bite the bullet and start my stability test for DP4, hopefully Apple can keep this until official release (I have a 10.14.6 DP3 backup clone).
Both 10.14.6 DP2 and DP3 has zero crash / freeze (GPURestart) with RX580 on my cMP. And now, let's see if DP4 can keep the stability.
So far, my personal recommended combination for RX580 is "10.14.6 DP3 + Hex edit". This combination is so stable that I don't want to further update my primary boot drive actually. But I still bite the bullet and start my stability test for DP4, hopefully Apple can keep this until official release (I have a 10.14.6 DP3 backup clone).
Last edited:
Could it be that this hack is more stable with Vega cards, because it's masquerading as an iMac Pro, which only ships with Vega GPUs? I wonder if it would be more stable for Polaris cards to instead pretend to be a Mac that ships with Polaris GPUs like the iMac 5K.
The reason that iMac Pro is the target is because, like MP5,1, the Xeon used don’t have Quicksync. If the Mac has a processor that supports Quicksync, GPU encoding/decoding is not used.
So, changing to iMac5K will get us nothing.
For the Record. I recently just did a 12h heavy-load postproduction in fcpx and the acceleration worked flawlessly! Vega 56 here.
H264 hardware decoding and encoding start working in 10.15 DP4 (19A512f) now (it did not work in previous DP)
BOTH HEVC hardware decoding and encoding do NOT work. So, not as good as Mojave (HEVC hardware decode can work in Mojave).
I haven't test hex edit method, but only do the board-id injection method (with Lilu and WhateverGreen).
I also manually edit the PlatformSupport.plist to let Catalina boot "natively" without the need of
"-no_compat_check" boot argument.
BOTH HEVC hardware decoding and encoding do NOT work. So, not as good as Mojave (HEVC hardware decode can work in Mojave).
I haven't test hex edit method, but only do the board-id injection method (with Lilu and WhateverGreen).
I also manually edit the PlatformSupport.plist to let Catalina boot "natively" without the need of
"-no_compat_check" boot argument.
HWaccel still working in 10.14.6 Beta (18G78a). AppleGVA framework has no change in this minor update.
No need to do anything for Lilu + WhateverGreen method. Just keep using it.
[doublepost=1563823436][/doublepost]Confirmed 10.14.6 Final work as expected. Safe to update.
I keep using the latest beta in last few weeks, really 100% stable for RX580 (with hex edit method). I highly suggest all Polaris users update to 10.14.6 ASAP if you want hwaccel. Even though there is no guarantee that 10.14.6 final is as good as beta. But there is a reasonable high chance that RX580 can now provide flawless hwaccel in 10.14.6. Worth to update ASAP rather than stay at 10.14.5 which may hit the GPURestart bug.