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

[MapleGreen]

I did Lilu method
It acted strange at stage 14

After restarting my computer was laggy as hell, videoProc took 5 minutes to open and after opening :

But somehow in Sony 4k test file it shined and cpu process was just 11%

So it worked but not completely

 

[kohlson]

It's been awhile since I did it this with Lilu, but that doesn't look familiar. And, once I had it installed the only effects were positive.

For me, I use the jellyfish video as an indicator for having this installed correctly. It's very binary. It either works (correctly installed) or it doesn't (not installed correctly). I use the one on the last row - 400 mbps.

 

[MapleGreen]

It's been awhile since I did it this with Lilu, but that doesn't look familiar. And, once I had it installed the only effects were positive.

For me, I use the jellyfish video as an indicator for having this installed correctly. It's very binary. It either works (correctly installed) or it doesn't (not installed correctly). I use the one on the last row - 400 mbps.

I exactly followed the procedure and I did it two times

even reseting NVRAM didn't revert the change, I lost H/W acceleration but any app that video related opens very slow
(5 min appox.)
I just downloaded Combo update , hope it revert the change

 

[MapleGreen]

Even Installing Combo update didn't revert the changes
so I have to do fresh macOS Install

 

[h9826790]

I exactly followed the procedure and I did it two times

even reseting NVRAM didn't revert the change, I lost H/W acceleration but any app that video related opens very slow
(5 min appox.)
I just downloaded Combo update , hope it revert the change

If hwaccel is disabled (after NVRAM reset), that means that slow down shouldn't be hwaccel directly related. There are many people went through this process, and this is not one of the known side effect.

Anyway, if you haven't perform clean installation yet, you can simply delete Lilu.kext (if you follow the exact procedure, this will also delete WEG kext). This will 100% revert all the changes.

Also, if you already perform clean installation. I suggest you do this hwaccel mod before installing any other software. So that, if that slow down suddenly appear again, you can trace back which software cause this compatibility issue.

 

[MapleGreen]

If hwaccel is disabled (after NVRAM reset), that means that slow down shouldn't be hwaccel directly related. There are many people went through this process, and this is not one of the known side effect.

Anyway, if you haven't perform clean installation yet, you can simply delete Lilu.kext (if you follow the exact procedure, this will also delete WEG kext). This will 100% revert all the changes.

Also, if you already perform clean installation. I suggest you do this hwaccel mod before installing any other software. So that, if that slow down suddenly appear again, you can trace back which software cause this compatibility issue.

thanks again, I performed the clean install, you helped a lot. I think maybe it was a program compatibility issue as you said, maybe I try this again after updating to Catalina with new Method.
by the way I deleted Lilu.kext and I did NVRAM reset, I checked them if they performed or not
after reseting NVRAM macOS gave me notification like this :

means SIP enabled again

and thanks again for telling me that" booting into recovery doesn't need macOS EFI GPU"

I used that to disable/enable SIP with my RX580 as well as Clean installing Mojave without boot screen
I never thought it is possible

 

[RaoulDuke42]

I just performed this trick on my MacPro5,1 with an RX580 in it... wowzas! All the 4k clips I've thrown at it-- and even some 1080 60fps stuff that used to play all slide-showy are now buttery smooth. Thank you so much! Adds all kinds of useful lifespan to this already eight year old MacBeasht. Thank you thank you thank you!

 

[PowerMike G5]

Yeah, this really is a great "upgrade".

I recently upgraded to a Radeon VII. I was honestly expecting something to be an issue as I was having sleep issues with the Vega Frontier Edition. And with this being a much newer GPU just being added with support as of 10.14.5, I wasn't fully confident.

But wow, the Radeon VII had provided a flawless experience in 10.14.6 so far. NO issues whatsoever. It's compute performance is certainly faster and using this hardware acceleration in Premiere Pro has allowed for more effortless 4K media playback for editing. Premiere seems to really max out the GPU usage and balances that more along with the CPUs now. This really has given my cMP some extended life here.

Really great! Thank you!

 

[MapleGreen]

update :
I just managed to do the Alternate Method
H264 is activated
and in Sony Swordsmith HDR UHD 4K Demo CPU process dropped to 11%

until now everything works OK

so what about HEVC Codec? (I have RX580)

 

[h9826790]

update :
I just managed to do the Alternate Method
H264 is activated
and in Sony Swordsmith HDR UHD 4K Demo CPU process dropped to 11%
View attachment 853344
View attachment 853346


until now everything works OK

so what about HEVC Codec? (I have RX580)

That Sony Swordsmith video is encoded in HEVC

 

[MapleGreen]

That Sony Swordsmith video is encoded in HEVC
View attachment 853357

so why Video proc can't detect hardware acceleration in HEVC section?

 

[h9826790]

so why Video proc can't detect hardware acceleration in HEVC section?

No idea. But HEVC encoding isn't working yet.

 

[MapleGreen]

in HEVC encoding QuickTime gave me 20 hours to Complete encoding
(video length : 2 hours)

 

[Ludacrisvp]

in HEVC encoding QuickTime gave me 20 hours to Complete encoding
(video length : 2 hours)
View attachment 853362

Correct because only HVEC decode works.

 

[ayawlex]

I just noticed last night thgough videoproc that my vega56 isn't recognized for h264 and hevc decoding.

which is easier or has less headache, changing the SMBios that doesn't have iGPU or should I still do this with the current SMBios?

I'm running 10.14.6

 

[h9826790]

I just noticed last night thgough videoproc that my vega56 isn't recognized for h264 and hevc decoding.

which is easier or has less headache, changing the SMBios that doesn't have iGPU or should I still do this with the current SMBios?

I'm running 10.14.6

Are you running Hackintosh?

 

[ayawlex]

Are you running Hackintosh?

yes but I do own a macbook pro 13" 2017 but videoproc doesn't seem to recognize hevc & h264.

been googling and results regarding SMBios or something but IDK

 

[h9826790]

yes but I do own a macbook pro 13" 2017 but videoproc doesn't seem to recognize hevc & h264.

been googling and results regarding SMBios or something but IDK

Sorry, I am confused. MBP 2017 should use QuickSync, but not the Vega's video acceleration.

For Hackintosh, use iMac Pro SMBIOS.

 

[ayawlex]

Sorry, I am confused. MBP 2017 should use QuickSync, but not the Vega's video acceleration.

For Hackintosh, use iMac Pro SMBIOS.

I'm sorry for the confusion. at first, videoproc didn't recognize the h/w acceleration for my macbook pro but it's enabled now.

as for my hackintosh, I'm still trying to figure out why the Vega 56 is still not recognized when 10.14.6 should have native drivers for it.

iMac Pro SMBIOS or specific ones?

 

[PBMB]

Sorry, I am confused. MBP 2017 should use QuickSync, but not the Vega's video acceleration.

It is still not quite clear to me why VideoProc does not use the discrete GPU to accelerate video processing when Intel Graphics are present. Do you have any insight? I asked their support but they never replied.

 

[Ludacrisvp]

It is still not quite clear to me why VideoProc does not use the discrete GPU to accelerate video processing when Intel Graphics are present. Do you have any insight? I asked their support but they never replied.

Because apple only supports dGPU hardware acceleration for very new Macs that come with a cpu that doesn’t support quick sync. In this case that is only the iMacPro1,1 right now, the MacPro6,1 has some form of acceleration from what I cant tell but not to the same level as the iMacPro.
Apple didn’t want to use the dGPU for this in their other Macs. My guess would be related to thermal and power consumption.
[doublepost=1566614486][/doublepost]Martin could be use the same approach here and have his MBP use the NVRAM argument (or probably hex edit preferred) to have the MBP use his VEGA for the things that intel quicksync is handling now?

 

[h9826790]

Martin could be use the same approach here and have his MBP use the NVRAM argument (or probably hex edit preferred) to have the MBP use his VEGA for the things that intel quicksync is handling now?

No idea, Apple said HWaccel on eGPU should be enabled by default now, but they didn't tell me if there is any restriction on Mac model.

Also, I only have cMP but no other Mac now, can't test it.

 

[PBMB]

Because apple only supports dGPU hardware acceleration for very new Macs that come with a cpu that doesn’t support quick sync. In this case that is only the iMacPro1,1 right now, the MacPro6,1 has some form of acceleration from what I cant tell but not to the same level as the iMacPro.
Apple didn’t want to use the dGPU for this in their other Macs. My guess would be related to thermal and power consumption.

But VideoProc is not Apple software. If I understand the problem well, it is up to the developers of VideoProc to program their software so that it can use the full GPU potential in a Mac (Intel UHD graphics + discrete GPU). Heat is not a problem in recent machines, e.g. the 2019 iMacs. I tried it and the iMac stays really cool and inaudible during video processing using the Intel graphics for acceleration, so there is definitely room for more.

 

[johnnymcc]

Is the benefit of doing this only for video production? Any benefit for photography or gaming? I have a Vega 64.

 

[h9826790]

Any benefit for photography or gaming?

No