MP 1,1-5,1 Activate AMD hardware acceleration

[cdf]

if you boot cpus=1 (single core / thread) is the issue gone?

Yes, this allows the system to boot (although it seems a little sluggish at first).

 

[08380728]

Hello there. I have a Z77 Hackintosh that I would like to start using over my Mac Pro. Are you using the HD4600 for QuickSync or the GPU? Thank you in advanced for this input.

Hey mate, following up on this, I’ve read the Quick Sync on the Intel HD 4600 Graphics in my 4790K z97 machine doesn’t support HEVC encoding only H.264/MPEG-4 AVC, VC-1 and H.262/MPEG-2.

Intel Quick Sync Video - Wikipedia

en.wikipedia.org

So it seems your options are to buy a Radeon for use in your Mac Pro and configure it to get full h264/h265 decode/encode, or fire up the Z77 and put a Radeon inside it. I’m in Australia and bought an MSI Armor OC 8GB Radeon RX580 for about $250 AUD, I feel this is good value.

I’m uncertain if the link below that contains info on accelerating hardware supporting the different codecs is based on physical hardware not supporting the codecs or their software is limiting supprt to just a few devices, but it may have some value as a quick lookup table for compatibility even if you not intend to use this software (cheesy Windows ported rubbush):

VideoProc's Full GPU Acceleration Makes Video Editing Faster

Full GPU hardware acceleration makes large (4K) video conversion, editing, rendering faster, and terminates freezes, laggy playback, endless buffering, etc.

www.videoproc.com

I tested playback and encoding of h264 & h265 in QT Player & Movist Pro and Handbrake VideoToolBox encoders, While these operations were running I issued the command h9826790 posted to confirm use of the Radeon.

I used sample videos found here http://jell.yfish.us/.

QT Player could not cope with the higher bit rate file jellyfish-400-mbps-4k-uhd-hevc-10bit.mkv it stopped stalled and restarted a few times, but Movist Pro Player had no such issues, silky smooth.

hope this is useful.

 

[Warriors Photo]

Hey mate, following up on this, I’ve read the Quick Sync on the Intel HD 4600 Graphics in my 4790K z97 machine doesn’t support HEVC encoding only H.264/MPEG-4 AVC, VC-1 and H.262/MPEG-2.

Intel Quick Sync Video - Wikipedia

en.wikipedia.org

So it seems your options are to buy a Radeon for use in your Mac Pro and configure it to get full h264/h265 decode/encode, or fire up the Z77 and put a Radeon inside it. I’m in Australia and bought an MSI Armor OC 8GB Radeon RX580 for about $250 AUD, I feel this is good value.

I’m uncertain if the link below that contains info on accelerating hardware supporting the different codecs is based on physical hardware not supporting the codecs or their software is limiting supprt to just a few devices, but it may have some value as a quick lookup table for compatibility even if you not intend to use this software (cheesy Windows ported rubbush):

VideoProc's Full GPU Acceleration Makes Video Editing Faster

Full GPU hardware acceleration makes large (4K) video conversion, editing, rendering faster, and terminates freezes, laggy playback, endless buffering, etc.

www.videoproc.com

I tested playback and encoding of h264 & h265 in QT Player & Movist Pro and Handbrake VideoToolBox encoders, While these operations were running I issued the command h9826790 posted to confirm use of the Radeon.

I used sample videos found here http://jell.yfish.us/.

QT Player could not cope with the higher bit rate file jellyfish-400-mbps-4k-uhd-hevc-10bit.mkv it stopped stalled and restarted a few times, but Movist Pro Player had no such issues, silky smooth.

hope this is useful.

Very! Thank you.

 

[08380728]

The developers of Clover abandoned the development and are now focusing on OC, so everybody in the hackintosh build world should switch over to OC.

This aint true bruv,

Clover General discussion

www.insanelymac.com

 

[startergo]

This aint true bruv,

Clover General discussion

www.insanelymac.com

Good to know for whoever wants to use Clover.

 

[Warriors Photo]

Good to know for whoever wants to use Clover.

Exactly, which I am one of them. I have liked the customization we have inside of Clover.

 

[eVasilis]

I can post the whole procedure here. My test shows very safe actually, worst case just some apps can’t open, and a warning window pops up.

WARNING: only do the following if the WhateverGreen method in post #1 doesn’t work, AND you know how to recovery the ENTIRE OS.

1) Remove all Lilu, WhateverGreen, and boot argument if applicable. (If you need innie, you can keep Lilu). If you remove boot argument by NVRAM reset, you have to disable SIP again in order to modify system files.

2) Go to System⁩ ▸ ⁨Library⁩ ▸ ⁨PrivateFrameworks⁩

3) right click AppleGVA.framework

4) Duplicate this file

5) single click the ORIGINAL AppleGVA.framework

6) Press “Command + i”

7) in the pop up window, rename “AppleGVA.framework” to “AppleGVA.framework.bak” (the file icon should now change to normal folder icon)
View attachment 841933

8) Rename the duplicated “AppleGVA copy.framework” to “AppleGVA.framework”. (This file’s permission should be wrong at this moment, but tests shows no adverse effect. In fact, make it easier for us to mod. For beta testing, I intentionally keep this “wrong” file permission)

9) double click the current AppleGVA.framework, you should able to open it.

10) continue to Version -> A, and locate “AppleGVA” (this file has no extension)
View attachment 841938

11) open this AppleGVA file with a Hex editor.

12) find 37 42 41 35 42 32 44 39 45 34 32 44 44 44 39 34 (should have TWO match result in Mojave. If you want to try this in 10.15, you may find only one result)
View attachment 841940 View attachment 841939

13) replace BOTH by 46 32 32 31 42 45 43 38 00 00 00 00 00 00 00 00 (make sure you replace the original byte, NOT insert).
View attachment 841942 View attachment 841941

14) save the file

15) open terminal

16) enter

sudo codesign -f -s - /System/Library/PrivateFrameworks/AppleGVA.framework/Versions/A/AppleGVA

17) in Finder, in that folder “A”, continue go into folder “Resources”

18) open the info.plist with text editor

19) search 7BA5B2D9E42DDD94
View attachment 841944

20) replace that by F221BEC8
View attachment 841943

21) Reboot.

The Hardware acceleration state now should be same as using the WhateverGreen method.

For those who prefer to keep SIP ON. Once you confirm everything is working as expected, you may now turn SIP back on.

Optional steps to repair all modified files' permission.

22) In terminal, enter

sudo codesign --deep -fs - /System/Library/PrivateFrameworks/AppleGVA.framework

23) Enter

sudo chown -R root:wheel /System/Library/PrivateFrameworks/AppleGVA.framework

24) Enter

sudo update_dyld_shared_cache -force

If anything wrong. Do the following recovery action.

A) go to System⁩ ▸ ⁨Library⁩ ▸ ⁨PrivateFrameworks⁩

B) delete AppleGVA.framework

C) rename AppleGVA.framework.bak to AppleGVA.framework (you should able to see the icon change again).

Now, your system should back to normal.


One of the advantage of using this alternate method is that you can turn ON/OFF hwaccel without reboot.

To turn OFF:

1) Rename the modded AppleGVA.framework to AppleGVA.framework.mod.bak.

2) And rename the original AppleGVA.framework.bak to AppleGVA.framework.


To turn it back ON:

1) Rename the original AppleGVA.framework to AppleGVA.framework.bak.

2) And rename the modded AppleGVA.framework.mod.bak to AppleGVA.framework.

Hi and thanks for the mod! I followed it and now I get this:

Is it normal for the the HEVC acceleration to be disabled?

Once again, thanks a lot!

 

[h9826790]

Is it normal for the the HEVC acceleration to be disabled?

Please read post#1 Q19

 

[eVasilis]

Please read post#1 Q19

My bad and apologies.
Thanks a lot!
[automerge]1576865319[/automerge]

Please read post#1 Q19

Truly great! Video as smooth as a baby's bottom CPU only at 9% engaging only 3 cores (3, 2 and one bars respectively)
Cheers!

 

[solaris8x86]

I've revisited this.

When I upgraded to the Vega 56, it turns out I had a bunch of old kexts installed, including WEG and Lilu. So, after removing all that cruft, I started with a fresh, unaltered version of AppleGVA and disabled SIP.

Instead of editing the AppleGVA binary, I simply added a board-id entry in Info.plist for the Mac Pro 5,1. I then turned all the gva variables on (defaults write com.apple.gva...):

defaults write com.apple.AppleGVA gvaForceAMDKE -bool YES
defaults write com.apple.AppleGVA gvaForceAMDAVCEncode -bool YES
defaults write com.apple.AppleGVA gvaForceAMDAVCDecode -bool YES
defaults write com.apple.AppleGVA gvaForceAMDHEVCDecode -bool YES

I now have hardware-assisted playback of H.264 and H.265 without modifying AppleGVA's binary. Swordsmith and Jellyfish playback beautifully.

Confirmed that it is also loading the GPU in FCPX for H.264 encode.

I have the same setup like yours (VEGA 56 in Mac Pro 2010) and have achieved the same result like yours.

The hardware Encoding and Decoding of H265 (HEVC) works on almost everything (VLC, QuickTime, Handbrake...etc) excepts on FCPX (latest version 10.4.8). Do you have a cure and trick to gets it work on FCPX? (My FCPX only works with HW accelerated h264 only, the HW accelerated HEVC doesn't work out no matter in timeline editing a HEVC clip or exporting(sharing) to a HEVC movie). It still bounds with CPU power only.

 

[solaris8x86]

I also added:

defaults write com.apple.AppleGVA forceATI -boolean yes
defaults write com.apple.coremedia hardwareVideoDecoder force

Although I don't know if that makes any difference.

Confirmed. These statements also enable HEVC decoding in the timeline of FCPX or a playback. But it doesn't work on encoding a movie in FCPX.

 

[solaris8x86]

I've also tried the following. But HEVC hardware-accelerated-exporting still doesn't work in FCPX. Hope someone can figure it out. Then the last piece of puzzle of ALL h264/HEVC accelerations will be done on my Mac Pro 2010 + Vega 56 working on all apps.

defaults write com.apple.coremedia hardwareVideoEncoder force


I've also compared to the benchmarks of my hardware accelerated Vega 56 on Mac Pro 2010 on most benchmark apps (Heaven, FCPX FPS, Geekmark 4, LuxMark 3.1...etc.)

The FPS results are almost identical to a stock iMac Pro 2017/Vega 56.

And it is about +10% faster than a MacBook Pro 2018 + eGPU Vega64 when testing on all those benchmark applications. Which to believe that the thunderbolt-to-eGPU chasis should have some performance lost during thunderbolt bus conversion. Some performance is lost thru eGPU chasis.

Thus, the old cMP (2009, 2010, 2012) has become the best graphic card upgrade platform among all old/new Mac... which is ridiculous but it is true. Because only the old cMP Mac can draw 100% performance from the new graphic cards directly thru PCI slot without the need of thunderbolt bus conversion. The benchmarks told it seems that way.

 

[Warriors Photo]

I've also tried the following. But HEVC hardware-accelerated-exporting still doesn't work in FCPX. Hope someone can figure it out. Then the last piece of puzzle of ALL h264/HEVC accelerations will be done on my Mac Pro 2010 + Vega 56 working on all apps.

defaults write com.apple.coremedia hardwareVideoEncoder force


I've also compared to the benchmarks of my hardware accelerated Vega 56 on Mac Pro 2010 on most benchmark apps (Heaven, FCPX FPS, Geekmark 4, LuxMark 3.1...etc.)

The FPS results are almost identical to a stock iMac Pro 2017/Vega 56.

And it is about +10% faster than a MacBook Pro 2018 + eGPU Vega64 when testing on all those benchmark applications. Which to believe that the thunderbolt-to-eGPU chasis should have some performance lost during thunderbolt bus conversion. Some performance is lost thru eGPU chasis.

Thus, the old cMP (2009, 2010, 2012) has become the best graphic card upgrade platform among all old/new Mac... which is ridiculous but it is true. Because only the old cMP Mac can draw 100% performance from the new graphic cards directly thru PCI slot without the need of thunderbolt bus conversion. The benchmarks told it seems that way.

Thank you for looking into this. I've seen even the Radeon VII cards not perform at their fullest potential in Mac OS. The performance hits could also be drivers. I am considering getting another RX480 8GB card as I feel that'll be the best price to performance card available to me.

What do you think?

 

[tsialex]

Thank you for looking into this. I've seen even the Radeon VII cards not perform at their fullest potential in Mac OS. The performance hits could also be drivers. I am considering getting another RX480 8GB card as I feel that'll be the best price to performance card available to me.

What do you think?

Dual GPU cards only make sense for applications that are multi GPU aware, most work better with more powerful GPUs than multiple GPUs. A lot of people are finding this the hard way with MP7,1.

 

[krakman]

I am considering getting another RX480 8GB card as I feel that'll be the best price to performance card available to me.

What do you think?

the RX480 is Polaris and it is not supported in Mac os Catalina 10.15.2

Edit - My mistake i was referencing a post made here which claimed HVEC had been removed: hwaccel


Support might return in a future update but then it might not....so unless you want to stay with Mojave i would suggest the best choice is Vega 56

CMMChris advised Apple removed HEVC HWAccel for all Polaris GPU in the latest Catalina beta.

 

[startergo]

the RX480 is Polaris and it is not supported in Mac os Catalina 10.15.2

Mine works. No problems whatsoever. By the way RX-580 is also Polaris.

 

[krakman]

Mine works. No problems whatsoever. By the way RX-580 is also Polaris.

Noted - I was referencing a post made earlier.

 

[solaris8x86]

Thank you for looking into this. I've seen even the Radeon VII cards not perform at their fullest potential in Mac OS. The performance hits could also be drivers. I am considering getting another RX480 8GB card as I feel that'll be the best price to performance card available to me.

What do you think?

I’ve watched a YouTube video demonstrating Vega VII would run twice faster than Vega 64 when the timeline has multiple effects applied. For example, Vega 64 can be applied a Noise effects 4 times to a clip without lag problem. The Vega VII can do 8 times effects without lag problem.

but it seems that it is related to the ram size problem only because Vega VII has twice the amount of memory more than Vega 64. so u are technically just buying the benefit of the amount of memory when working on FCPX.

However, when exporting a h264 movie from FCPX. The export time are very close in between them. Vega VII does not have a major benefit in this area. Also, Vega VII has fan noise problem that the fan once runs at top speed. It never comes down.....

In most game demos. Vega VII is about 10%-20% FPS rate faster than Vega 64 on a Mac. But In some benchmarks apps are almost 100% faster if PSU can provide such ampere current to the GPU.

In terms of $$$ investment. It is a concern whether worth spending twice the amount of $$$ to gain only +10-20% performance (vega 64 vs VII). In your case. I think Vega 56 or 64 are more likely a wise choice.

 

[Warriors Photo]

I’ve watched a YouTube video demonstrating Vega VII would run twice faster than Vega 64 when the timeline has multiple effects applied. For example, Vega 64 can be applied a Noise effects 4 times to a clip without lag problem. The Vega VII can do 8 times effects without lag problem.

but it seems that it is related to the ram size problem only because Vega VII has twice the amount of memory more than Vega 64. so u are technically just buying the benefit of the amount of memory when working on FCPX.

However, when exporting a h264 movie from FCPX. The export time are very close in between them. Vega VII does not have a major benefit in this area. Also, Vega VII has fan noise problem that the fan once runs at top speed. It never comes down.....

In most game demos. Vega VII is about 10%-20% FPS rate faster than Vega 64 on a Mac. But In some benchmarks apps are almost 100% faster if PSU can provide such ampere current to the GPU.

In terms of $$$ investment. It is a concern whether worth spending twice the amount of $$$ to gain only +10-20% performance (vega 64 vs VII). In your case. I think Vega 56 or 64 are more likely a wise choice.

This is one reason I am not looking into the Radeon VII as much as two RX 480 GPUS. Double the RAM and FCPX can utilize two GPUS very well. It's well written to do so. Thank you for the input.
[automerge]1577146894[/automerge]

Dual GPU cards only make sense for applications that are multi GPU aware, most work better with more powerful GPUs than multiple GPUs. A lot of people are finding this the hard way with MP7,1.

I only use FCPX to edit and it does fully utilize dual GPUS if they are the same model. I've seen this already with dual RX560 cards. That was a great set up on my old Hackintosh. Thank you for the input, BTW. You and the input are highly appreciated.

 

[solaris8x86]

This is one reason I am not looking into the Radeon VII as much as two RX 480 GPUS. Double the RAM and FCPX can utilize two GPUS very well. It's well written to do so. Thank you for the input.
[automerge]1577146894[/automerge]

I only use FCPX to edit and it does fully utilize dual GPUS if they are the same model. I've seen this already with dual RX560 cards. That was a great set up on my old Hackintosh. Thank you for the input, BTW. You and the input are highly appreciated.

In FCPX. I think dual 56 or dual 64 are wise choice. But need one more PSU externally. Also need a Mod.
The used Vega 64 are getting cheaper and cheaper recently. Worth spending to get a used dual configuration.

 

[eVasilis]

Merry Christmas to all and to those that do not celebrate it, no offense intended.
Catalina, according to VideoProc, has H264 hardware acceleration activated. To those who wish to follow the Hex method, you will have a hard time as the "AppleGVA.framework" cannot be edited, changed or replaces unless one is prepared to break through catalina's security and thus mount the system partition with read/write access. That of course, as pointed out in other posts in this thread, is pointless unless you have a Vega GPU.

One question: Whenever I try to use the H264 (videobox) conversion in Handbrake, it fails. All other conversions, the ones that do not leverage the GPU, work fine. Has anybody observed that with Handbrake and Catalina?

Cheers

 

[Warriors Photo]

In FCPX. I think dual 56 or dual 64 are wise choice. But need one more PSU externally. Also need a Mod.
The used Vega 64 are getting cheaper and cheaper recently. Worth spending to get a used dual configuration.

I found two/three Vega 56 cards locally for a great deal. I am considering them for this reason as well. Although, I may put them into a hackintosh I have sitting around instead. What kind of a performance gain could I expect from two Vega 56 cards vs. two RX 480 cards? Thank you for the follow ups. I appreciate it.
[automerge]1577392967[/automerge]

Merry Christmas to all, and to those that do not celebrate it, no offense intended.
Catalina, according to VideoProc, has H264 hardware acceleration activated. To those who wish to follow the Hex method, you will have a hard time as the "AppleGVA.framework" cannot be edited, changed or replaces unless one is prepared to break through catalina's security and thus mount the system partition with read/write access. That of course, as pointed out in other posts in this thread, is pointless unless you have a Vega GPU.

One question: Whenever I try to use the H264 (videobox) conversion in Handbrake, it fails. All other conversions, the ones that do not leverage the GPU, work fine. Has anybody observed that with Handbrake and Catalina?

Cheers

Hey, thank you for the Holiday wishes. That's very kind of you.

 

[h9826790]

One question: Whenever I try to use the H264 (videobox) conversion in Handbrake, it fails. All other conversions, the ones that do not leverage the GPU, work fine. Has anybody observed that with Handbrake and Catalina?

Just tested, no problem for both H264 and HEVC conversion in Handbrake with VideoToolBox in Catalina

 

[eVasilis]

Just tested, no problem for both H264 and HEVC conversion in Handbrake with VideoToolBox in Catalina

Could it be your Vega card vs my Polaris (rx 580 pulse)?

 

[h9826790]

Could it be your Vega card vs my Polaris (rx 580 pulse)?

I am not sure, but H264 HWAccel should be OK, Apple only removed the HEVC HWAccel for Polaris in 10.15.2

If you use Hex edit method, please restore the edited files, and try latest Lilu and WEG.