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.
I think not every 4K is demanding, use the 'swordsmith' sample video H98 mentioned in the first post to test, if you've got GPU acceleration then you won't see any hiccups around 50s (when sword is dipped into the water).

Download permitted at the moment: https://drive.google.com/uc?export=download&id=1wLqFqextNvtLRmQaCh5xgx6wHxUTcxil
---
Edit: Found another link.

Yes, the Mac Pro with RX 580 fails to play correctly the Swordsmith video without hardware acceleration.

Interesting while QT Player stresses the GPU, Iina stresses much more the CPU, but both fail.

QT Player.png Iina.png
 
Last edited:
  • Like
Reactions: octoviaa
Now with a fresh installed EFI RX 580 in my Mac Pro I have a question.

My macOS 10.14.6 is (yet) totally unpatched, and VideoProc of course indicates no hardware acceleration:

View attachment 851308

But when I play h.264 footage e.g. with VLC it indicates no some CPU usage and the RX 580 does all the work:

View attachment 851310

Does that mean h.264 hardware decode acceleration is working without any patching in macOS 10.14.6 ?

Exactly which card/model did he send you, and is it also using the Radeon frambuffer?
 
Last edited:
  • Like
Reactions: crjackson2134
Last edited:
  • Like
Reactions: orph and Synchro3
I use the "toughest" version of this as a simple test to see whether hardware acceleration is working or not.

Note the release notes from VLC 3.0.7 "VLC 3.0 activates hardware decoding by default, to get 4K and 8K playback!"
That said, without the AMD Hardware mod stated at the beginning of this thread, jellyfish won't play.
 
Last edited:
sorry guys, how can I see if Lilu.kext is uninstalled?
I reset the nvram and deleted the WhateverGreen.kext
thanks.
 
sorry guys, how can I see if Lilu.kext is uninstalled?
I reset the nvram and deleted the WhateverGreen.kext
thanks.

Simply remove that from the folder.

If not sure where Lilu installed, and can't search it. Then you can check if Lilu exist in the Extensions section in System info.
HWAccel Catalina.png
 
Hi there
I just updated to macOS 10.14.6 on my Mac Pro 5,1. My question is if Kext method has positive impact on general use or using Final Cut Pro and is it safe to do in macOS 10.14.6?
Screen Shot 2019-08-08 at 1.45.16 PM.png

Untitled.png

Screen Shot 2019-08-08 at 1.55.08 PM.png


regards
 
Yes it has a positive impact on general use and FCPX.
It is as safe to use on 14.6 as it was on 14.5, perhaps even more so. There seem to be mixed reports, depending on the AMD GPU you have installed.
I haven't noticed any unusual impacts when using my RX580.
 
  • Like
Reactions: Chung123
Yes it has a positive impact on general use and FCPX.
It is as safe to use on 14.6 as it was on 14.5, perhaps even more so. There seem to be mixed reports, depending on the AMD GPU you have installed.
I haven't noticed any unusual impacts when using my RX580.
thanks
if something went wrong fresh macOS install reverts the change, am I right?
because I don't want to do the complicated alternate procedure
 
10.14.6 seems to have fixed stability issues with my 5,1 and RX580 and Final Cut Pro X. So I've been really happy so far. (I followed the hex procedure.)
 
  • Like
Reactions: h9826790
A fresh install is a fresh install, so no AMD hardware acceleration.
You can also follow @h9826790 instruction to use Automator to switch on or off, at least with the Hex method.
thanks will do that
now with H/W Acceleration off I get about 500% CPU in Sony Swordsmith HDR UHD 4K Demo playback but it is buttery smooth

after Kext method it should be around 20% , my question is if they playback is smooth as the software decoding mode
same frame rate, ....

I know export time in Final Cut Pro decreases about 70% , what about realtime playback in Final Cut Pro?


Screen Shot 2019-08-09 at 3.56.20 AM.png
 
I know export time in Final Cut Pro decreases about 70%
Keep in mind that performance is affected by your export parameters. It's not an "across the board" acceleration. Choosing h.264 (VideoToolbox) is what triggers the GPU hardware assist. That may or ma not fit what you're looking for.
 
  • Like
Reactions: h9826790
Keep in mind that performance is affected by your export parameters. It's not an "across the board" acceleration. Choosing h.264 (VideoToolbox) is what triggers the GPU hardware assist. That may or ma not fit what you're looking for.

I'm more interested in real-time performance in general use as well as real-time play back in Final Cut Pro

Is H/W Acceleration smooth as software decoding on real-time playback?
 
In FCPX, timeline editing seems smooth. As reported in this thread, some have had issues with RX580 in a timeline with lots of effects. These reports seem less so with 14.6.
I think the best thing I can recommend is to go ahead and give it a try and see how it works for you. The Lilu approach took me only about 20-30 minutes - most of this is spect rebooting to turn SIP on and off.

I'd never used a hex editor before, and wasn't following the instructions exactly, so I had some pilot errors using this method. It was good that I had another bootable disk. But now that I have the hang of it it take 10-15 minutes. I''ve done it on 2 other cMPs. Again, much of that time is booting around disabling and re-enabling SIP. All in all, perhaps less time than unboxing a new GPU card and installing it. And if it doesn't wrk for you, easy enough to get back to where you started.
 
Last edited:
In FCPX, timeline editing seems smooth. As reported in this thread, some have had issues with RX580 in a timeline with lots of effects. These reports seem less so with 14.6.
I think the best thing I can recommend is to go ahead and give it a try and see how it works for you. The Lilu approach took me only about 20-30 minutes - most of this is spect rebooting to turn SIP on and off.

I'd never used a hex editor before, and wasn't following the instructions exactly, so I had some pilot errors using this method. It was good that I had another bootable disk. But now that I have the hang of it it take 10-15 minutes. I''ve done it on 2 other cMPs. Again, much of that time is booting around disabling and re-enabling SIP. All in all, perhaps less time than unboxing a new GPU card and installing it. And if it doesn't wrk for you, easy enough to get back to where you started.

Thank that was very helpful
I have two final questions
1 : which HEX Editor do you use?
2 : you mentioned it's easy enough to get back to where we started
What is the easiest method to get back if anything goes wrong
 
I went into the App Store and found iHex, which is free. There are others available by using google to search.

For the hex method, if you keep a copy of the 14.6 combo updater around, you can just re-apply that. Easy, though execution time is 30-40 minutes. But the end result is assurance of a nice, pristine OS. Alternately, you can just swap the appropriate files as outline in the instructions. For the hex method, no rebooting or anything.

For the Lilu method, it's resetting the NVRAM, also very straightforward. It may also be re-applying the 14.6 Combo Updater, but I haven't tried that method.

In both cases, there may be a few minutes devoted to disabling/enabling SIP, or at least verifying.

As with all cMP surgery, I strongly recommend reading up on everything before proceeding. @h9826790 was very careful to create instructions for "back-out" safety nets. They work. If you have an alternate bootable drive, there's nothing to worry about. Worst case, you boot from it and re-install 10.14.6.
 
Thank
I went into the App Store and found iHex, which is free. There are others available by using google to search.

For the hex method, if you keep a copy of the 14.6 combo updater around, you can just re-apply that. Easy, though execution time is 30-40 minutes. But the end result is assurance of a nice, pristine OS. Alternately, you can just swap the appropriate files as outline in the instructions. For the hex method, no rebooting or anything.

For the Lilu method, it's resetting the NVRAM, also very straightforward. It may also be re-applying the 14.6 Combo Updater, but I haven't tried that method.

In both cases, there may be a few minutes devoted to disabling/enabling SIP, or at least verifying.

As with all cMP surgery, I strongly recommend reading up on everything before proceeding. @h9826790 was very careful to create instructions for "back-out" safety nets. They work. If you have an alternate bootable drive, there's nothing to worry about. Worst case, you boot from it and re-install 10.14.6.
Thanks again
The problem is I can't disable SIP with RX580 because the lack of Boot screen
I have to swap to my HD5770
Re-installing with bootable drive is not possible because 5770 is not metal support
For Mojave I had to install Sierra first then update the OS to High Sierra (because for some reason bootable USB with high sierra in it didn't work for me) then swap the card for RX580 then install Mojave
That's why I'm careful in doing any change

So I think best method for me is doing Lilu method and hope it to work
Then if any thing goes wrong just Install 14.6 combo update.
I would be appreciated if you could give me a download link for 14.6 combo update
I couldn't find it by Google search.
 
Thank

Thanks again
The problem is I can't disable SIP with RX580 because the lack of Boot screen
I have to swap to my HD5770
Re-installing with bootable drive is not possible because 5770 is not metal support
For Mojave I had to install Sierra first then update the OS to High Sierra (because for some reason bootable USB with high sierra in it didn't work for me) then swap the card for RX580 then install Mojave
That's why I'm careful in doing any change

So I think best method for me is doing Lilu method and hope it to work
Then if any thing goes wrong just Install 14.6 combo update.
I would be appreciated if you could give me a download link for 14.6 combo update
I couldn't find it by Google search.

Just hold command + R to boot to recovery partition. Boot screen is NOT required for accessing recovery partition.

My procedures doesn't need boot screen, doesn't need any other GPU more than a single RX580. If that's required, I will state that clearly in the procedures.
 
  • Like
Reactions: kohlson
Just hold command + R to boot to recovery partition. Boot screen is NOT required for accessing recovery partition.

My procedures doesn't need boot screen, doesn't need any other GPU more than a single RX580. If that's required, I will state that clearly in the procedures.
Wow... you are a life saver
The problem was recovery mode didn't use my main monitor, RX580 was sending screens to my other monitors which the were off,

Thank a lot.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.