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.

MacManu77

macrumors regular
Jan 31, 2018
110
4
I can follow the 13 steps to post 594 to get the full gpu acceleration and stay with Mojave 10.14.6 from how I understand... Right?

I did not understand if the turbo Boost will work well or not, and if anyway the cpu will have all the cores active and working well.
 

h9826790

macrumors P6
Original poster
Apr 3, 2014
16,656
8,587
Hong Kong
I can follow the 13 steps to post 594 to get the full gpu acceleration and stay with Mojave 10.14.6 from how I understand... Right?

I did not understand if the turbo Boost will work well or not, and if anyway the cpu will have all the cores active and working well.

You can do everything in post 594 to get full HWAccel now. It will stay until you select another boot drive in system preference -> startup disc, or perform a NVRAM reset. This also serve as a fail safe protection.

If HWAccel / OpenCore is disabled, you can simply do step 7+8+13 to re-enable OpenCore on the next boot.

For TurboBoost, it will be disabled at this moment if you follow the exact steps in post 594 to use OpenCore 0.5.4. But if you go 0.5.5 beta, then TurboBoost will work flawlessly. I will update post 594 once 0.5.5 go official. But IMO, you can safely go 0.5.5 beta now. I keep testing the latest 0.5.5 beta, very stable on my cMP.
 
  • Like
Reactions: w1z

MacManu77

macrumors regular
Jan 31, 2018
110
4
You can do everything in post 594 to get full HWAccel now. It will stay until you select another boot drive in system preference -> startup disc, or perform a NVRAM reset. This also serve as a fail safe protection.

If HWAccel / OpenCore is disabled, you can simply do step 7+8+13 to re-enable OpenCore on the next boot.

For TurboBoost, it will be disabled at this moment if you follow the exact steps in post 594 to use OpenCore 0.5.4. But if you go 0.5.5 beta, then TurboBoost will work flawlessly. I will update post 594 once 0.5.5 go official. But IMO, you can safely go 0.5.5 beta now. I keep testing the latest 0.5.5 beta, very stable on my cMP.


Yes, I'm interested in coding/decoding of h264 that hevc.

Can I start the procedure with Mojave 10.14.6 in the nvme in the signing?
The other hd physicists are discovering them all.
 

MIKX

macrumors 68000
Dec 16, 2004
1,815
691
Japan
VideoProc is giving away a free license - must register the " giveaway license " before Feb. 14th 2020.

Just activated my license.

LINK https://www.videoproc.com/giveaway/?mail=JanGV00

VideoProc free license Feb 1st. 2020.png
 

w1z

macrumors 6502a
Aug 20, 2013
692
481
Thanks for sharing the catalina config.plist file.


2020-02-01_00-02-57.png


Replaced boardid with Mac-27AD2F918AE68F61 (MP7,1) and instead of using the prefilled Patch section, I used -wegtree ie.

Code:
-no_compat_check cwae=2 -wegtree shikigva=80
 
  • Like
Reactions: h9826790

kohlson

macrumors 68020
Apr 23, 2010
2,425
737
mojave securityupdate 2020-001 overwrites the appleGVA.framework
Yup. It has sharpened my "skills" in performing this modification. I use the hex method. Now, start to finish, it takes me less than 15 minutes. Most of this is reboot time for disable/enable SIP. The only real challenge for me is that I have installed this on a couple of friends' cMP, and it takes longer to drive to their place than to do the update.
 

h9826790

macrumors P6
Original poster
Apr 3, 2014
16,656
8,587
Hong Kong
If I add a second Radeon VII into the machine, will it provide hardware acceleration automatically? Or is there a part of the process that needs to be repeated?

I don't think so.

All HWAccel is done via VideoToolBox, which the user has no control at all. Which means, for HWAccel, we have no way to assign one GPU for task A, and the other GPU for task B.

Also, I believe only the GPU that has PCIe name GFX0 can do HEVC hardware encoding.
 
  • Like
Reactions: Grumply

tsialex

Contributor
Jun 13, 2016
13,454
13,601
I don't think so.

All HWAccel is done via VideoToolBox, which the user has no control at all. Which means, for HWAccel, we have no way to assign one GPU for task A, and the other GPU for task B.

Also, I believe only the GPU that has PCIe name GFX0 can do HEVC hardware encoding.
I'm hoping that Apple will refactor the VideoToolBox code to enable multiple GPUs hardware encoding. Makes sense for multiple MP7,1 GPUs and DUO MPXs.

For now, just GFX0 is working, like you said.
 
  • Like
Reactions: JedNZ and h9826790

MacManu77

macrumors regular
Jan 31, 2018
110
4
Hi,

With the open core 0.5.5 what you say is best updating the post # 594 with the updated files?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.