Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.

calmasacow

macrumors member
Jun 13, 2012
53
8
Houston, TX
Please read post #1 FAQ
I just searched every post that the RX 580 is mentioned in the FAQ There is nothing specific about it that I see. There is nothing saying that the HVEC doesn't work. By everything I have read here the Lilu, WEG Method should work for both. it is after all the base graphics in the latest Mac Pro.

I did see a not saying that the HEX method is very stable in the Beta But there is also a post saying that things are stable in the 10.14.6 final.

Sorry I'm not trying to be difficult. simply curious if anyone might have some advise to resolve this situation.


Also I forgot to mention card is the Sapphire Pulse 8GB version with stock Bios
 

Ludacrisvp

macrumors 6502a
May 14, 2008
797
363
I just searched every post that the RX 580 is mentioned in the FAQ There is nothing specific about it that I see. There is nothing saying that the HVEC doesn't work. By everything I have read here the Lilu, WEG Method should work for both. it is after all the base graphics in the latest Mac Pro.

I did see a not saying that the HEX method is very stable in the Beta But there is also a post saying that things are stable in the 10.14.6 final.

Sorry I'm not trying to be difficult. simply curious if anyone might have some advise to resolve this situation.


Also I forgot to mention card is the Sapphire Pulse 8GB version with stock Bios
Assuming you are on 10.14.6 ...
Using the latest WEG and Lilu with the correct NVRAM flags the 580 provides H264 encode and decode and HEVC decode only (no encode) ... if you want encode there are some other steps needed at this time (opencore).
 

h9826790

macrumors P6
Original poster
Apr 3, 2014
16,656
8,587
Hong Kong
I just searched every post that the RX 580 is mentioned in the FAQ There is nothing specific about it that I see. There is nothing saying that the HVEC doesn't work. By everything I have read here the Lilu, WEG Method should work for both. it is after all the base graphics in the latest Mac Pro.

I did see a not saying that the HEX method is very stable in the Beta But there is also a post saying that things are stable in the 10.14.6 final.

Sorry I'm not trying to be difficult. simply curious if anyone might have some advise to resolve this situation.


Also I forgot to mention card is the Sapphire Pulse 8GB version with stock Bios

Please re-read post #1 Q5, Q17, Q19. I believe that covered your question already. Unless you already try the suggested sample HEVC video, and UDV doesn’t work.

P.S. I am not trying to be harsh to you. I just believe that you missed the point. And better to re-read the FAQ section carefully. Also, don’t search the word “RX580”, otherwise you may miss a lot of general info that true for all applicable GPU.
 
Last edited:

MiguelAnge

macrumors newbie
Oct 1, 2018
12
3
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.

Hello,

Many thanks for all these hints. After evaluation, I selected the HEX way I found less complex.

My cMP 2012 with an AMD RX580 running Mojave 10.14.6 has now H264 and H265
 
  • Like
Reactions: h9826790

MiguelAnge

macrumors newbie
Oct 1, 2018
12
3
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.

Hello,

Many thanks for all these hints. After evaluation, I selected the HEX way I found less complex.

My cMP 2012 2 x Hex 3.46GHz with an AMD RX580 running Mojave 10.14.6 has now HW acceleration.

Before the patch, I was not able to read fluently the jeely fish video sample with VLC. After, all is fine. Nevertheless while VIDEOPROC detects well the H264 acceleration, for H265, still no support detected nothing: encode or decode... What did I miss..?
 

two-mac-jack

macrumors member
Mar 25, 2016
38
17
Before the patch, I was not able to read fluently the jeely fish video sample with VLC. After, all is fine. Nevertheless while VIDEOPROC detects well the H264 acceleration, for H265, still no support detected nothing: encode or decode... What did I miss..?

You didn't miss anything, you did everything right!

The hex edit method gives you H.264 decode and encode, and HEVC decode -- but not HEVC encode.

After the hex edit procedure, VideoProc will show (correctly) that H.264 decode/encode is enabled. It will also show (incorrectly) that HEVC decode/encode is disabled -- even though HEVC decode is actually working.

Based on experience in this thread, when VideoProc shows H.264 encode/decode as enabled after the hex edit, you can assume that HEVC decode is also working.

If you want to verify, just play back a large high-res HEVC video with VLC -- like you did with the jellyfish video. If it plays back smoothly, and you see low CPU core usage in Activity Monitor (Window > CPU Usage) after the first few seconds, then you know HEVC decode is working.
 

MiguelAnge

macrumors newbie
Oct 1, 2018
12
3
If you want to verify, just play back a large high-res HEVC video with VLC -- like you did with the jellyfish video. If it plays back smoothly, and you see low CPU core usage in Activity Monitor (Window > CPU Usage) after the first few seconds, then you know HEVC decode is working.

Hi,

I confirmed for HVEC decode support by reading fluently many 4k/8k videos on the tube and monitoring GPU. Althrough with 8k, GPU is highly loaded while one of my Xeon is also getting loaded (50%).

I also Videoproc crashes during H265 evaluation (systematic).

I would have following questions:
1) I read H265 encode possible as well: it means the other method is more appropriate?

2) Is the method with Catalina working as well, even so I have a dual Xeon configuration?

3) With my Mini 2018, the Intel CPU is systematically selected while encoding through iMovie, while I have a eGPU with a Vega 64: is this in link with the Vsync stuff?

Thanks in advance!
 

ZeroKool79

macrumors newbie
Jan 11, 2019
10
0
France
The Easy Way To Edit .plist file

Step1:


Open a terminal session: Finder –> Applications –> Utilities –> Terminal (See Figure 1.)


View attachment 889707


Figure 1.


Change to super user by entering the following command: sudo -s and then enter your password and press enter again. (See Figure 2.)


View attachment 889704


Figure 2.


Change to the required directory (cd /Path/to/file) then hit enter. (See Figure 3.)


View attachment 889706


Figure 3.


Edit the .plist file file by typing: (nano filename.plist) then hit enter. (See Figure 4.)


View attachment 889705


Figure 4.

Thank you very much I finally managed to modify the .plist file
 

ZeroKool79

macrumors newbie
Jan 11, 2019
10
0
France
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
Code:
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
Code:
sudo codesign --deep -fs - /System/Library/PrivateFrameworks/AppleGVA.framework

23) Enter
Code:
sudo chown -R root:wheel /System/Library/PrivateFrameworks/AppleGVA.framework

24) Enter
Code:
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.

This method didn't work for me :(
 

Attachments

  • Capture d’écran 2020-01-25 à 11.06.56.png
    Capture d’écran 2020-01-25 à 11.06.56.png
    124.6 KB · Views: 185
  • Capture d’écran 2020-01-25 à 11.27.19.png
    Capture d’écran 2020-01-25 à 11.27.19.png
    63.3 KB · Views: 214

astonius86

macrumors member
Apr 25, 2017
93
32
Mt Juliet, TN
Using SMBIOS spoofing and the latest versions of Lilu/WhateverGreen and the post #594 config, I can get HVEC encode/decode working, however I don't see Sidecar in my System Prefs and AirPlay video is still not working. Any ideas?
 

h9826790

macrumors P6
Original poster
Apr 3, 2014
16,656
8,587
Hong Kong
Using SMBIOS spoofing and the latest versions of Lilu/WhateverGreen and the post #594 config, I can get HVEC encode/decode working, however I don't see Sidecar in my System Prefs and AirPlay video is still not working. Any ideas?

Oh, my fault, the latest config.plist will still let the cMP ident as 5,1. Therefore, Sidecar won't be activated automatically. I forgot to update the into in post #1.

The goal of this thread is to activate HWAccel with minimum change to the system.

If you want Sidecar, you may try this patcher

 

astonius86

macrumors member
Apr 25, 2017
93
32
Mt Juliet, TN
Oh, my fault, the latest config.plist will still let the cMP ident as 5,1. Therefore, Sidecar won't be activated automatically. I forgot to update the into in post #1.

The goal of this thread is to activate HWAccel with minimum change to the system.

If you want Sidecar, you may try this patcher


Thank you! What about AirPlay video? Audio works, but AirPlay video just shows a black screen.
 

h9826790

macrumors P6
Original poster
Apr 3, 2014
16,656
8,587
Hong Kong
Just tested both 10.14.6 (18G3020) and 10.15.3 (19D76), nothing changed for OpenCore method. All H264, HEVC, hardware encode, hardware decode, DRM streaming still work as expected.

[N.B. As precaution, my config.plist in post #594 does NOT provide OS update in Catalina. You can either update Catalina by yourself. Or turn ON VMM flag AND RequestBootVarRouting in the config.plst, then update Catalina in system preferences natively]

10.14.6.png

10.15.3.png
 

Cracticus

macrumors newbie
Jan 28, 2020
17
11
greetings - I am looking to speed up my Mac Pro 5,1 for FCPX - my current 9570 Tahiti is slow at export 4K - has no Hardware h264 option in VideoProc - so When buying an RX 580 - can it be any RX 580 for this or is it better to get the Sapphire RX 580 Pulse 8Gb version? the Asus and Gigabyte 580s seem cheaper but maybe not suited to the above hack?
 

h9826790

macrumors P6
Original poster
Apr 3, 2014
16,656
8,587
Hong Kong
greetings - I am looking to speed up my Mac Pro 5,1 for FCPX - my current 9570 Tahiti is slow at export 4K - has no Hardware h264 option in VideoProc - so When buying an RX 580 - can it be any RX 580 for this or is it better to get the Sapphire RX 580 Pulse 8Gb version? the Asus and Gigabyte 580s seem cheaper but maybe not suited to the above hack?
Any RX580
 
  • Haha
Reactions: Cracticus

Cracticus

macrumors newbie
Jan 28, 2020
17
11
btw my AMD Radeon 7970 3Gb does not give any start-up screen (4K LG on HDMI port) in Mojave 10.14.6 Mac Pro 5,1 (option key) ; but if I (shut down) then first zap the pram (⌘-option-P-R) then immediately after the 2nd chime release those 4 keys then hold Option key - i do then get a low-res start screen on my 4K (with huge drive icons) to select which drive to start from. It's helpful as I don't have the original card or a smaller display to swap back n forth.
 

Grumply

macrumors 6502
Feb 24, 2017
285
194
Melbourne, Australia
Hi guys,

I want to thank everyone for their work on this. Amazing stuff all round.

I'm just finalising my new 5,1 build:

- 12-core 3.46Ghz
- 96GB RAM
- Radeon VII (downvolted to 204w and running off internal power thanks to h9826790)

I went through steps 0-13 in Post #594 and have been able to reboot successfully into Mojave 10.14.6, and my About This Mac page is showing the rounded-up Ghz for the CPUs:

Screen Shot 2020-01-31 at 6.50.53 pm.png


However, when I go into VideoProc it tells me that I have no Hardware Acceleration going:

Screen Shot 2020-01-31 at 6.53.10 pm.png


I figured something had failed, but then I decided to try some playback of HEVC footage (the 4k 400Mbps Jellyfish sample, and another 4k 60fps HEVC capture of a broadcast) along with some 8k footage in Youtube, and everything is playing BUTTERY smooth.

And when I go into iStat Pro it's showing (for the 4k HEVC and h264 files playing in VLC) 1% CPU usage, and seemingly all of the load going to the GPU:

HEVC processing.jpg


What does this mean?

Is VLC natively able to push the processing of HEVC and h264 footage to the GPU? And if so, is the super smooth playback simply the result of the Radeon VII being such a powerful GPU?

Or does this mean that the hardware acceleration has actually been activated, and VideoProc simply isn't detecting that it has?

Being an idiot and totally out of my depth here, I didn't actually test playback of these files before I ran through the Hardware Acceleration process, so I have no idea how smoothly they were playing before I attempted the upgrade.
 

h9826790

macrumors P6
Original poster
Apr 3, 2014
16,656
8,587
Hong Kong
Hi guys,

I want to thank everyone for their work on this. Amazing stuff all round.

I'm just finalising my new 5,1 build:

- 12-core 3.46Ghz
- 96GB RAM
- Radeon VII (downvolted to 204w and running off internal power thanks to h9826790)

I went through steps 0-13 in Post #594 and have been able to reboot successfully into Mojave 10.14.6, and my About This Mac page is showing the rounded-up Ghz for the CPUs:

View attachment 891500

However, when I go into VideoProc it tells me that I have no Hardware Acceleration going:

View attachment 891501

I figured something had failed, but then I decided to try some playback of HEVC footage (the 4k 400Mbps Jellyfish sample, and another 4k 60fps HEVC capture of a broadcast) along with some 8k footage in Youtube, and everything is playing BUTTERY smooth.

And when I go into iStat Pro it's showing (for the 4k HEVC and h264 files playing in VLC) 1% CPU usage, and seemingly all of the load going to the GPU:

View attachment 891502

What does this mean?

Is VLC natively able to push the processing of HEVC and h264 footage to the GPU? And if so, is the super smooth playback simply the result of the Radeon VII being such a powerful GPU?

Or does this mean that the hardware acceleration has actually been activated, and VideoProc simply isn't detecting that it has?

Being an idiot and totally out of my depth here, I didn't actually test playback of these files before I ran through the Hardware Acceleration process, so I have no idea how smoothly they were playing before I attempted the upgrade.

Try that little “reload” icon in VideoProc
 
  • Like
Reactions: MIKX and Grumply

MIKX

macrumors 68000
Dec 16, 2004
1,815
691
Japan
Try that little “reload” icon in VideoProc
I hadn't thought of that either !

Brilliantly simple solution that I really should have thought of.

Should the 'reload' be pressed DURING the Jellyfish playback ? I'm assuming so.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.