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 set up (with tsialex!) a MP 5.1 with a RX 5700xt and Monterey, under OCLP. In Videoproc software hardware acceleration and encoding are available for the 5700xt. There are all the greenlights. However in Videoproc, Handbrake, QuickTime and Compressor only CPU is used for HEVC encoding.
Final Cut rendering is GPU accelerated. But encoding isn't.
 
Last edited:
  • Like
Reactions: John Fu
I set up (with tsialex!) a MP 5.1 with a RX 5700xt and Monterey, under OCLP. In Videoproc software hardware acceleration and encoding are available for the 5700xt. There are all the greenlights. However in Videoproc, Handbrake, QuickTime and Compressor only CPU is used for HEVC encoding.
Final Cut rendering is GPU accelerated. But encoding isn't.
Did you specifically choose hardware encoding? Any screen capture of the settings you use for encodings?
 
  • Like
Reactions: zazaki
Hi thanks for your support. So under Monterey with OCLP:

I tried encoding HEVC on latest version of FCP and on 10.5.1 (standard Apple 4K HEVC) ; on Compressor 4.6.3. (standard Apple 4K HEVC) and on Quicktime : nothing in GPU History monitor

In Handbrake (Fast 2160p HEVC) : nothing in GPU History monitor, slow

In VideoProc (4K HEVC) : small GPU use, 2min to encode a 1min ProRes film

Please note rendering in FCP seems hardware accelerated and in the contrary to HEVC, H264 encoding do use a little GPU. Also Capture One is using the GPU for exporting.
 

Attachments

  • Capture d’écran 2023-05-15 à 13.13.43.png
    Capture d’écran 2023-05-15 à 13.13.43.png
    183.7 KB · Views: 103
  • Capture d’écran 2023-05-15 à 19.32.46.png
    Capture d’écran 2023-05-15 à 19.32.46.png
    495.5 KB · Views: 108
  • Capture d’écran 2023-05-15 à 19.20.49.png
    Capture d’écran 2023-05-15 à 19.20.49.png
    390.8 KB · Views: 100
  • Capture d’écran 2023-05-15 à 19.19.20.png
    Capture d’écran 2023-05-15 à 19.19.20.png
    542 KB · Views: 96
Last edited:
Hi thanks for your support. So under Monterey with OCLP:

I tried encoding HEVC on latest version of FCP and on 10.5.1 (standard Apple 4K HEVC) ; on Compressor 4.6.3. (standard Apple 4K HEVC) and on Quicktime : nothing in GPU History monitor

In Handbrake (Fast 2160p HEVC) : nothing in GPU History monitor, slow

In VideoProc (4K HEVC) : small GPU use, 2min to encode a 1min ProRes film

Please note rendering in FCP seems hardware accelerated and in the contrary to HEVC, H264 encoding do use a little GPU. Also Capture One is using the GPU for exporting.
From your screen capture, VideoProc was using GPU encoding.

Forget about that GPU usage monitor, HWAccel usage won’t show up there.

For GCN generations GPU, I am 100% sure we can monitor UVD / VCE by using OpenGL Driver monitor. But I am not quite sure if we can do the same thing for VCN generations GPU. I don’t have such card, and no one ever report that.

On the transcoding screen, both “CPU” and “Intel” light up. Because the source video is a ProRes video, need CPU to decode. Then VideoProc can use GPU to encode.

However, since hardware encoding is a system level function in MacOS, and VideoProc has no control of it. Therefore, it always assume “HWAccel in MacOS” is using Intel QuickSync. This is why it show you “Intel”, but not “AMD”.

If you transcode a H264 video to HEVC in VideoProc, then only “Intel” should be lighted up, because now both decoding and encoding can be handled by GPU.

For FCP, I haven’t try if we can use GPU to export HEVC directly in the latest version. But for previous version, my test so far need Compressor to use GPU HEVC encoding, and must disable “allow frame reordering”

This is the sample video to show how to export HEVC from FCP. Please try it with identical settings (except bitrate, which obviously not related), and see if you can get GPU HEVC encoding.
 
  • Like
Reactions: zazaki
Many thanks. I disabled “allow frame reordering” and the HEVC encoding time is so fast! In Compressor 4.6 this option has disappeared for 4K Apple Device setting and seems activated by default. To access this function, we must use MPEG setting, then HEVC format.

Also Capture One is working great.
 
  • Like
Reactions: h9826790
I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package updated to 0.9.2]

For those who only need HWAccel, post #594 has everything you need. This new package mainly offer HWAccel + boot screen. Also, this package should work in Catalina and newer macOS for dual processor cMP.

I don't mind you guys discuss anything about this package, but I have no plan to provide any explanation about OpenCore at here. If you want to know more, please join cdf's OpenCore thread. For new joiners, please make sure read through the FAQ in post #1 before you ask anything.

The attached packaged included Clover Configurator (for mounting the EFI partition only, please do NOT use it to edit the OpenCore config) and a complete preconfigured OpenCore. All credits goes to the developer teams. If you want to show your support, please give them donation (declaration of interest: I am NOT in any of their developer teams)

For Clover Configurator and OpenCore developers teams, please let me know if you want me to remove the associated software inside my attachment in this post.

This is a "one package fit all" solution. So, it's designed to fit as much setup as possible, which may not be optimized for your setup (e.g. I haven't provide HiDPI boot screen, for those who are running 4K screen, the Apple logo may be quite small during boot). You have to do the optimization by yourself (details in the OpenCore manual, some info also available in cdf's OpenCore thread).

Anyway, for those who have RX 460 or newer AMD GPU, this package should gives you:
  1. Boot screen (via GOP for unflashed card, including some Nvidia card)
  2. Firmware protection (to run Windows in EFI mode without risking the cMP bootROM)
  3. HWAccel (H264 / HEVC hardware decode + encode in Mojave and newer macOS)
  4. ability to watch DRM streaming content (Mojave and newer macOS)
  5. Boot picker (only support EFI systems, tested with Apple wired keyboard, Magic Mouse, and Magic Keyboard, 10s timeout. If you can't see this. Just don't touch the keyboard, and your cMP should continue to boot to desktop)
  6. NVMe and SATA drives on PCIe card show up as internal
  7. Support for Apple USB SuperDrive
  8. TRIM (regardless trimforce status)
  9. Ability to run non-GUI 32bit software in Catalina
  10. Ability to reset NVRAM in boot picker (disabled at this moment to align with the native Apple boot manager)
  11. Ability to run any natively supported ancient OSX with modern graphic card e.g. Radeon VII in 10.6.8 (only can display, no acceleration) [Update 5th May 2020: Sierra and High Sierra may not fully supported yet. Thanks for pierrox's report]
  12. Ability to boot Catalina / Big Sur / Monterey and the associated Recovery Partition [SurPlus (credit to Syncretic) is included and enabled by default to fix the racing condition in macOS 11.3 or later][AVXPel is also included. another credit to Syncretic][ASPP-Override is included for macOS 12.3, credit to dortania]
  13. Sleep should work (tested on my cMP, but I can't guarantee it also work with your setup)
  14. Possible to run 8x32GB RAM in macOS (user need to mod the config.plist manually. Replace the false below CustomMemory to true)
  15. Enable HDMI Audio for some graphic cards
  16. Ability to monitor modern AMD GPU's temperature (by using the attached RadeonGadget. Credit to Aluveitie)
  17. Possible to run AQC107S 10Gbps network card up to Monterey 12.2.1 (any macOS at or higher than 12.3 won't work)
It's impossible for me (and other voluntary helpers) to test every single function in all situations. So, as usual, use at your own risk. But you are welcome to report back if there is any problem / error.

Pre-installation:
  • Recommend to backup your BootROM between step 1 and 2 (e.g. by using ROMTool, credit to Dosdude, password "rom")
  • If you want to test OpenCore, you can install this package onto a bootable USB thumb drive.
  • Quite a few users reported that can't boot OpenCore from NVMe, analysis shows that depends on hard drives config. It's hard to explain which exact scenario may hit this bug. So, please avoid to install this package on NVMe. You can install this package on ANY SATA drive with virtually no performance lost, not necessary your boot drive.
  • If you want to remove OpenCore, please mount the EFI partition by using Clover Configurator, then remove BOOT and OC folders inside the EFI folder on EFI partition.
  • If your cMP stuck at boot. After shutdown, please pull out the hard drive that contain OpenCore, then perform NVRAM reset. If still doesn't work, then please install your emergency graphic card that has boot screen. Hold Option to boot, then select your backup boot drive. This should disable OpenCore.
  • For those who want to report issue / error. Please provide details (e.g. which graphic card, OpenCore installed on NVMe / SATA drive, the issue's details, etc) otherwise it will be extremely hard (or even impossible) for me to work out what's wrong.
  • If you installed Lilu for whatever reason (e.g. because of innie), or applied my previous non-OpenCore HWAccel mod, please remove them or revert them. For Lilu + WEG, that means delete Lilu.kext in /Library/Extensions/ and reboot (caution: these kexts may be installed in System/Library/Extensions/ as well). For hex edit method, that means delete AppleGVA.framework in /System/Library/PrivateFrameworks/ and rename AppleGVA.framework.bak to AppleGVA.framework. Warning: My packages already have Lilu and WEG included, "double installation" of these kexts will cause macOS boot failure.
  • For PULSE RX580, users reported that only can see boot screen when boot from gaming mode. There may be no UEFI GOP in the compute mode's ROM.
I tried to make the installation as simple as possible. However, I still demand you to learn some very basic skills. Those skills are very useful in the recovery process if something goes wrong. Anyway, here is what you need to do
  1. [Optional] 3x NVRAM reset to avoid some unknown issues.
  2. Disable SIP (must do, especially if you performed step 1)
  3. Download the attachment in this post (if the newer package has compatibility issue. You may download the older package, same installation procedures.)
  4. Follow the steps in this video (please turn on and read the subtitle)
  5. For Big Sur and Monterey, if some ports on your graphic card are disabled, please follow the steps in this video to re-enable them.
  6. Reboot

For existing OpenCore users, you may follow the step in this video to update OpenCore [For those who installed OC onto the Windows drive, please make sure you only replace the OC files, but not the whole EFI folder]


Additional option 1: If you have 4K screen, and you want to have "Retina" boot screen. You may do this. [Depreciated in 0.7.6, which Retina should be enabled automatically on 4K monitor]

Additional option 2: If you have a flashed Thunderbolt 3 card, you can install that in slot 4, then enable Thunderbolt 3 support by doing this.

Additional option 3: If you want to enable the ability to install / update Catalina, Big Sur and Monterey, please follow the steps in this video. [N.B. you should revert the changes after macOS installation completed. This special setting is not designed for daily use]

Additional option 4: If you have legacy wifi card, you may try the follow steps to re-activate the old wifi card in Big Sur (only avail in my 0.6.4 package or above)

Additional option 5: To enable legacy BT support in the latest unsupported OS, you may turn on both BlueToolFixUp and BlueTooth-Spoof kext.

Additional option 6: Since 0.6.3, I allow OC to take over SIP control. There are various reasons, but anyway, that's defaulted to be disabled. If you want to re-enable SIP, please follow the steps in this video. (please turn on the English subtitle when you watch this video, some useful info at there)

For FCP(X) users, if you want to export HEVC video by using HWAccel, you will need Compressor.
[N.B. The setting MUST identical to the one that I show in the video. Otherwise, HEVC hardware encoding may not work]

If you want to completely uninstall my OpenCore package, please follow the steps in this video.

N.B. Unflashed graphic card means "the ROM is never modified". For those who bought used card, and can't see the boot screen, most likely the last user flashed the card with modified ROM (e.g. downvolt for mining). In this case, you can go to TechPowerUp to find a ROM that fit your own card, and flash it.

P.S. If you want to support my work, please donate via the following link. Million thanks in advance! https://www.paypal.com/paypalme/martinlo420

[Last update:13 May 2023, OpenCore 0.9.2, Lilu 1.6.5, WhateverGreen 1.6.4, RadeonSensor 0.3.3, AppleALC 1.7.8, FeatureUnlock 1.1.4, SurPlus, AVXpel, ASPP-Override]
I'm using the latest package, everything is fine, and so i dual boot with windows 11 , opencore let me choose between Mac OS and W11, perfect... Until i reset NVRAM , Windows is hidden now, i can't choose it anymore !
I spent the whole day trying to understand, i uninstalled Windows, installed again... And nope, if i ever do NVRAM reset, Windows will disappear from the boot picker. Terrible.
Any fix ?
 
I'm using the latest package, everything is fine, and so i dual boot with windows 11 , opencore let me choose between Mac OS and W11, perfect... Until i reset NVRAM , Windows is hidden now, i can't choose it anymore !
I spent the whole day trying to understand, i uninstalled Windows, installed again... And nope, if i ever do NVRAM reset, Windows will disappear from the boot picker. Terrible.
Any fix ?
Thanks for the report.

I never heard/seen this issue. I personally performed NVRAM reset (both natively or via OpenCore) and new firmware flashing (which will also clear NVRAM) many time on my cMP with both macOS and WIN11 installed.

May I know if your WIN11 is on a NVMe? (P.S, my WIN11 is on a SATA SSD)

Do you know if you WIN11 drive has any potential compatibility issue on cMP?

Did you check if the backplane battery has enough voltage?

Did you try if install OpenCore onto the Win 11 drive’s EFI partition (and bless it accordingly) can help anything?
 
Thank you for answering.
Windows 11 is on a separate SATA SSD hard drive, Opencore is on a totally separate Sata HDD.
I looked for a lot of information, i didn't find anything about compatbility issue.

I'd like to be able to see Windows 11 Efi partition from Mac OS, but i can't see it at all, and when i try to mount if with terminal, it just keep refusing.

I also noticed that wiping the efi partition and install Opencore Legacy Patcher on it works, i can see my W11 again. So weird !

EDIT : I tried to remove my NVME disk, boot to opencore to see if Windows 11 show again, but i have nothing just infinite black screen.
I switched to OCLP , it works again.
I put the latest package you provide, it doesn't show windows anymore. I can't understand
 
Last edited:
Thank you for answering.
Windows 11 is on a separate SATA SSD hard drive, Opencore is on a totally separate Sata HDD.
I looked for a lot of information, i didn't find anything about compatbility issue.

I'd like to be able to see Windows 11 Efi partition from Mac OS, but i can't see it at all, and when i try to mount if with terminal, it just keep refusing.

I also noticed that wiping the efi partition and install Opencore Legacy Patcher on it works, i can see my W11 again. So weird !

EDIT : I tried to remove my NVME disk, boot to opencore to see if Windows 11 show again, but i have nothing just infinite black screen.
I switched to OCLP , it works again.
I put the latest package you provide, it doesn't show windows anymore. I can't understand

With all your Windows attempts in Uefi Mode ensure that you didnt catched certificates in your NVRAM.

You can check it with my tool: https://forums.macrumors.com/thread...es.2333460/page-4?post=32055801#post-32055801
 
Thank you for answering.
Windows 11 is on a separate SATA SSD hard drive, Opencore is on a totally separate Sata HDD.
I looked for a lot of information, i didn't find anything about compatbility issue.

I'd like to be able to see Windows 11 Efi partition from Mac OS, but i can't see it at all, and when i try to mount if with terminal, it just keep refusing.

I also noticed that wiping the efi partition and install Opencore Legacy Patcher on it works, i can see my W11 again. So weird !

EDIT : I tried to remove my NVME disk, boot to opencore to see if Windows 11 show again, but i have nothing just infinite black screen.
I switched to OCLP , it works again.
I put the latest package you provide, it doesn't show windows anymore. I can't understand
Check NVRAM first as per Macschrauber's suggestion. This is the very first "must do now" item. Only proceed forward when you know the cMP is safe.

After that, boot to any OS (e.g. via OCLP) , check what's in the Windows drive EFI partition (which should call itself NO NAME at this moment).

There should be an EFI folder inside. Then BOOT and Microsoft folder inside.

If the above is right, then you may try to install my package onto the Windows 11 EFI drive.
  1. Rename the NO NAME partition to EFI
  2. Keep the Microsoft folder
  3. Backup and replace the BOOT folder
  4. Install the OC folder
Then you can run the bless tool. This will make the cMP boot from your Windows drive's OpenCore. Assuming the SSD itself has no compatibility issue, this should give your cMP better protection, and keep it auto boot to OpenCore.

And now, let's see if the cMP boot from the same drive's EFI partition, can it see the Windows 11 that also on the same drive.
 
Check NVRAM first as per Macschrauber's suggestion. This is the very first "must do now" item. Only proceed forward when you know the cMP is safe.

After that, boot to any OS (e.g. via OCLP) , check what's in the Windows drive EFI partition (which should call itself NO NAME at this moment).

There should be an EFI folder inside. Then BOOT and Microsoft folder inside.

If the above is right, then you may try to install my package onto the Windows 11 EFI drive.
  1. Rename the NO NAME partition to EFI
  2. Keep the Microsoft folder
  3. Backup and replace the BOOT folder
  4. Install the OC folder
Then you can run the bless tool. This will make the cMP boot from your Windows drive's OpenCore. Assuming the SSD itself has no compatibility issue, this should give your cMP better protection, and keep it auto boot to OpenCore.

And now, let's see if the cMP boot from the same drive's EFI partition, can it see the Windows 11 that also on the same drive.
i used the tool for NVRAM, here's what it gives me:

Firmware 144.0.0.0.0 (latest)
Serial from firmware: CK94605SBXE
CRC32 checksums: ok
Crossflash 4.1->5.1 (bootblock of MP51.007F.B03)
Base_19c hardware descriptor
Boot000x is EFI\OC\OpenCore.efi (LauncherOption: Full)
OCLP: 0.6.5 | -allow_fv | MacPro5,1
0 boots since last garbage collection, MTC counter: 13
VSS1 VSS2
1 (1 active) 1 Memory Configs g (ok)
1 (1 active) 0 Memory Configs h (ok)
1 (1 active) 1 Memory Configs i (ok)
1 (1 active) 1 Memory Configs j (ok)
0 0 Microsoft certificates (ok)
1 (1 active) 1 BluetoothInternalControllerInfos (ok)
1 (1 active) 1 current-network (ok)
52812 bytes free space of 65464
VSS1 (Formatted) (Healthy)
VSS2 (Formatted) (Healthy)

Looks good i think.
My problem with the Windows EFI partition is i can't get access to it from Mac OS.
I can mount OC EFI partition with no problem, but Windows EFI will never let me access.
 

Attachments

  • Capture d’écran 2023-05-18 à 13.07.34.png
    Capture d’écran 2023-05-18 à 13.07.34.png
    214.7 KB · Views: 64
i used the tool for NVRAM, here's what it gives me:

Firmware 144.0.0.0.0 (latest)
Serial from firmware: CK94605SBXE
CRC32 checksums: ok
Crossflash 4.1->5.1 (bootblock of MP51.007F.B03)
Base_19c hardware descriptor
Boot000x is EFI\OC\OpenCore.efi (LauncherOption: Full)
OCLP: 0.6.5 | -allow_fv | MacPro5,1
0 boots since last garbage collection, MTC counter: 13
VSS1 VSS2
1 (1 active) 1 Memory Configs g (ok)
1 (1 active) 0 Memory Configs h (ok)
1 (1 active) 1 Memory Configs i (ok)
1 (1 active) 1 Memory Configs j (ok)
0 0 Microsoft certificates (ok)
1 (1 active) 1 BluetoothInternalControllerInfos (ok)
1 (1 active) 1 current-network (ok)
52812 bytes free space of 65464
VSS1 (Formatted) (Healthy)
VSS2 (Formatted) (Healthy)

Looks good i think.
My problem with the Windows EFI partition is i can't get access to it from Mac OS.
I can mount OC EFI partition with no problem, but Windows EFI will never let me access.


Looks ok, keep the file as a recovery if you will get certificates. One time booting Uefi Windows directly it will sign the NVRAM.

Flashing back the rom dump will get you in that state you backed the rom up.

As you have a crossflash 4.1 the NVRAM is more fragil than real MP5,1.
 
Hello ,
i upgraded MP5,1 from High Sierra to Mojave, and would like to leave it that way for the time being.
However, noticed that on both HS and Mojave, with RX 580 8GB (flashed for bootscreen), there is no HW-accelleration for Handbrake and Videoproc. Have i got something wrong in my setup or do i need OPenCore for that?
Thanks very much.
 
My problem with the Windows EFI partition is i can't get access to it from Mac OS.
I can mount OC EFI partition with no problem, but Windows EFI will never let me access.
Did you say you can boot / see Windows when boot via OCLP?

Or I misunderstood your meaning?
 
Hello ,
i upgraded MP5,1 from High Sierra to Mojave, and would like to leave it that way for the time being.
However, noticed that on both HS and Mojave, with RX 580 8GB (flashed for bootscreen), there is no HW-accelleration for Handbrake and Videoproc. Have i got something wrong in my setup or do i need OPenCore for that?
Thanks very much.
That's normal. Apple never enable any HWAccel on the Mac Pro until 7,1.

If you don't need HEVC hardware encoding, but just want the decoding functions. Then you can go to post #1, and see how to enable that without OpenCore.

But by personal suggestion is just to follow the steps in post #1314 to install OpenCore and enjoy full HWAccel. Especially if you have a flashed card, and running a natively supported macOS, nothing can go wrong.
 
That's normal. Apple never enable any HWAccel on the Mac Pro until 7,1.

If you don't need HEVC hardware encoding, but just want the decoding functions. Then you can go to post #1, and see how to enable that without OpenCore.

But by personal suggestion is just to follow the steps in post #1314 to install OpenCore and enjoy full HWAccel. Especially if you have a flashed card, and running a natively supported macOS, nothing can go wrong.

I still use the „Native“ method from post #1 on my main machine with Mojave and a RX560 to get hardware accelerated Video playback.
 
I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package updated to 0.9.2]
If trying to start safe I get the this mac os is not supported on machine message. Turned on voice control now machine crashes at desktop. Wont try that again once I fix it. You have done a lot of new oc versions since I installed but should not be that much different.
 
If trying to start safe I get the this mac os is not supported on machine message. Turned on voice control now machine crashes at desktop. Wont try that again once I fix it. You have done a lot of new oc versions since I installed but should not be that much different.
To enter safe mode, you should first boot to the boot picker, then press the Shift key and select macOS.

If you hold Shift key to boot, that command the cMP to bypass OpenCore, and boot straight to the macOS safe mode. And since the macOS isn’t supported natively. Therefore, it says “not supported”.

I really never try voice control. But if you don’t really need it, then may be just turn it off.
 
could not get to safe mode. Downloaded the 12.6.6 version of Monterey but the installation reboots with message of
No port micro restart ( we don't support SMC on this platform). Wonder if even doing this would fix it.. problem of barely getting to desktop and crashing, from enabling this "feature". Maybe this version is wrong, may only support with apple chip?

Edit: I had to change the setting from video tutorial to update to 12.6.6. However, still reboots at desktop. Is there a way to disable voice control by erasing something? Or the plist to edit to disable voice control again?

Edit: Even after reinstalling it did not fix the problem. I have booted into another account ok (Made mistake of using safe mode boot arg. Cant mount EFI!) Going to try to get out of safe mode by booting Mohave and maybe disable gatekeeper too and give some terminal commands to get EFI. Still at a loss to get account back without knowing where the plist is to turn off voice control unless maybe I implement the suggested fix here a minute ago if I manage to fix this mess... AVX

Edit: I guess that would not work cause I have sip on.... Blast! ... Now windows diskpart says no volume selected when assigning letter WTF, running out of ideas ..oh well put the drive in another machine and edit the efi

Seemingly with OC is you have safe boot in boot args then if you boot windows Diskpart fails. Because that has never happened to me before with diskpart.
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.