I have HW GPU Decoding on my RX 6600 8GB on latest Ventura 13.1, but I have a problem. I am not able to HW Decode video higher than 4k. For example I tried 5.3K 60Fps HEVC from GoPro and it uses the CPU to decode the video. I think this is because there is a limitation imposed by the OS (Max Resolution or Max Level). The GPU is able to decode 5.3K 60, so it is just a limitation imposed. Is there a way to force HW Decode for every video?
Moreover, I am not able to encode video at 10bit HEVC using Hardware Encode, but it uses CPU Encoding, even if NAVI has 10bit HW Encoding.
Did you try 5.3K 24FPS? If that doesn't work, then I believe Apple locked the AMD HWAccel to 4K regardless which hardware we have.
When the 7,1 release, AMD HWAccel only works up to 4K, and no 10bit hardware encoding. I won't be too surprised that there is no update on this function since 2019. Especially they moved to Apple silicon, and want to make people believe how strong their chip is.
Thanks for the report. So, no matter how long you wait, Kernel task still stay at ~50%?
My package aim for providing some sort of one stop solution, may be some kext / function is not required in your setup, which cause that extra CPU usage. I only have time to test if the package can boot and function as expected. No time to monitor such issue on my own cMP. It's good to know that you can create your own config which fit your own cMP.
Anyway, may I know if the whole EFI folder is the same (especially the same kexts are used), but you just re-do the config by yourself?
I always completely rewrite EFI so as not to confuse either kexts or configs
Kernel task runs non-stop for the whole day
I had a problem with Kernel Task for several years because of the Radeon Pro W5700
I made many posts earlier
there was no problem with rx580, rx570 or with Radeon Pro W5500
after updating to Radeon Pro W6800, the kernel task did not appear either
what is the problem? I haven't been able to find out...
although startergo wrote ssdt for me and the kernel task disappeared for one day, I worked all day, tested the work and was happy
but the next morning after turning on the computer, the kernel task reappeared
taught by experience, if I make any changes in the system or programs, I constantly turn on monitoring and check the processes
what remark can I make from personal experience
I updated the blender version a month ago and noticed a strange situation - my blender 3.4.1 began to render slower, and after the blender shut down, I noticed that appeared Kernel Task 10%
I was surprised, reset nvram process disappeared
but if I ran blender 3.4.1 after it the kernel task appeared
but when working in blender 3.3.2 everything is fine
and I thought that the developers of blender just released a bad beta version
But when I had time to research, I realized my mistake: I didn’t notice that now blender for macos is available in two versions: macos intel and macos arm
Kernel task appears due to a program written for arm
I can assume that some conflicting setting appeared in OC 0.8.8, as the developers tend to run Ventura, which is written for arm, and our hardware is not supported at all
Did you try 5.3K 24FPS? If that doesn't work, then I believe Apple locked the AMD HWAccel to 4K regardless which hardware we have.
When the 7,1 release, AMD HWAccel only works up to 4K, and no 10bit hardware encoding. I won't be too surprised that there is no update on this function since 2019. Especially they moved to Apple silicon, and want to make people believe how strong their chip is.
if I understand correctly your files are H265 and neither an AMD GPU nor a xeon CPU can handle that.
here an intel quicksync CPU of the newest generation or an apple silicon would be necessary for it.
as a solution I would recommend you the conversion using free shutter encoder in prores422.
if I understand correctly your files are H265 and neither an AMD GPU nor a xeon CPU can handle that.
here an intel quicksync CPU of the newest generation or an apple silicon would be necessary for it.
as a solution I would recommend you the conversion using free shutter encoder in prores422.
if I understand correctly your files are H265 and neither an AMD GPU nor a xeon CPU can handle that.
here an intel quicksync CPU of the newest generation or an apple silicon would be necessary for it.
as a solution I would recommend you the conversion using free shutter encoder in prores422.
AMD GPU can decode / encode HEVC for quite a few years already. But of course, has resolution / colour depth limit.
But at this moment, still not enough info to know if his videos are outside the hardware limit. Or Apple has extra software limit.
A quick search shows that 6600 has HEVC hardware decode support up to 8K, but just up to 8K24, not 8K60. So, anything above 4K may be limited to 24FPS.
AMD GPU can decode / encode HEVC for quite a few years already. But of course, has resolution / colour depth limit.
But at this moment, still not enough info to know if his videos are outside the hardware limit. Or Apple has extra software limit.
A quick search shows that 6600 has HEVC hardware decode support up to 8K, but just up to 8K24, not 8K60. So, anything above 4K may be limited to 24FPS. View attachment 2142269
Question: After updating to 8.8 can you update to the new Mac OS without doing anything else or same as before swap the config file first then install the upgrade, then after upgrading put the original 8.8 config file back into folder as before?
*Currently running 12.6.1, Mac Pro 5.1 Mid 2012 2X 3.46GHz w/128 GB Ram, Running RX 580.
Question: I keep reading about spoofing serial numbers, is this something I would need to do before upgrading to Ventura? If so, is there a master list of instructions that is posted that I am just not seeing in this thread? If yes, is it located on page one under the open core section?
Basically, I am just concerned that I am doing everything right and not missing a step.
Adding to the collective here; I believe I've solved (or at least improved) my issues of loginwindow crashing on waking from sleep by setting the "HDMI audio" in my config file to "false." Seems leaving this on the default "true" likely did not agree with my monitor set-up. (An MSI 4GB RX560 feeding dual DVI monitors.)
Never did get the (stock 2012) legacy wifi working, however...
I created a new "easy to install package" as per many requested (based on the official OpenCore). [The attached package updated to 0.8.8]
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 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:
Boot screen (via GOP for unflashed card, including some Nvidia card)
Firmware protection (to run Windows in EFI mode without risking the cMP bootROM)
HWAccel (H264 / HEVC hardware decode + encode in Mojave and newer macOS)
ability to watch DRM streaming content (Mojave and newer macOS)
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)
NVMe and SATA drives on PCIe card show up as internal
Support for Apple USB SuperDrive
TRIM (regardless trimforce status)
Ability to run non-GUI 32bit software in Catalina
Ability to reset NVRAM in boot picker (disabled at this moment to align with the native Apple boot manager)
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]
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]
Sleep should work (tested on my cMP, but I can't guarantee it also work with your setup)
Possible to run 8x32GB RAM in macOS (user need to mod the config.plist manually. Replace the false below CustomMemory to true)
Enable HDMI Audio for some graphic cards
Ability to monitor modern AMD GPU's temperature (by using the attached RadeonGadget. Credit to Aluveitie)
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
[Optional] 3x NVRAM reset to avoid some unknown issues.
Disable SIP (must do, especially if you performed step 1)
Download the attachment in this post (if the newer package has compatibility issue. You may download the older package, same installation procedures.)
Follow the steps in this video (please turn on and read the subtitle)
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.
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.
Hello,
Here is my configuration: Mac pro 4.1 --> 5.1 - 2 x 3.46GHz / 96Gb / 5700XT flashed / Titan Ridge 2.0 flashed / Monterey 12.6.2 / OpenCore 0.8.8 Martin Lo package
The peripherals (nvme disk, usb key...) connected to my thunderbolt station are not recognized on the 1st boot, I have to disconnect/reconnect the thunderbolt cable and restart the system to see them appear.
I decided to do a Pram reset and since opencore won't boot anymore, I have a black screen. I have to choose the disk by pressing "option" at startup to be able to boot.
The problem of peripherals connected to the thunderbolt station is not solved either.
Also I have a problem with USB ports, when I disconnect a device it cannot be reconnected. Same with thunderbolt.
everything normal
after a NVRAM reset OC must be reblessed again.
thunderbolt needs an initiaslization followed by a reboot.
since bigsur many USB devices are only available when connected to an active USB hub.
Hi all, first time post/question. Thanks to everyone who has made hardware acceleration possible amongst all the other great things OpenCore provides. This has probably been asked to death so apologies in advance if the solution is simple and I missed it throughout reading all the posts here, but I'm really struggling to identify why HEVC is not showing up as enabled in VideoProc. Thus I'm not sure if HEVC is in fact working as a result. Is there something I need to do beyond just installing OC to get it to run and display? I'm running OpenCore on my Mac Pro 5,1 with Mojave 10.14.6 with a RX580.
As an aside, I curious if anyone can confirm whether Topaz Video Enhance AI 2.6.4 or version 3 can run on a Mac Pro 5,1, either with or without OC/hardware acceleration. I have the X5690 chip on my machine, but I'm assuming its too outdated to run a demanding application.
Topaz Video Enhance AI 2.6.4 or version 3 can run on a Mac Pro 5,1, either with or without OC/hardware acceleration. I have the X5690 chip on my machine, but I'm assuming its too outdated to run a demanding application.
I tested V3.0.12. Both GPU decoding and encoding can work.
As you can see from the above screen capture.
The bottom left shows both UVD and VCE have been used. In fact, the UVD (AMD hardware decoder) has been used during I ran the preview. And the above capture was done during export, at the moment of VCE (AMD hardware encoder) has been called.
But for this kinds of video processing, the main bottleneck usually is the "processing" itself, not decoding or encoding. So, you may feel little to no difference regardless the software is using the GPU to decode / encode or not.
As per the capture above, I selected the "upscale to 4K and convert to 60FPS" profile. Which only performed at 1.2FPS. Even my W3690 can encode 4K HEVC video faster than that. Therefore, hardware encoding isn't that critical for this particular process.
Besides, the CPU loading isn't high at all, your X5690 should be more than enough. Of course, the single thread performance may be still the limiting factor. As you can see, the GPU loading also isn't that high. So, it shouldn't be GPU processing power limiting in my test.
And for info, if you want to use hardware encoding with this software for whatever reason, it seems only H264 works. Both HEVC export options use software encoding in my test, and seems no way to change it.
Assuming you never patch any macOS files, please see post #1 Q29.
I tested V3.0.12. Both GPU decoding and encoding can work. View attachment 2145110
As you can see from the above screen capture.
The bottom left shows both UVD and VCE have been used. In fact, the UVD (AMD hardware decoder) has been used during I ran the preview. And the above capture was done during export, at the moment of VCE (AMD hardware encoder) has been called.
But for this kinds of video processing, the main bottleneck usually is the "processing" itself, not decoding or encoding. So, you may feel little to no difference regardless the software is using the GPU to decode / encode or not.
As per the capture above, I selected the "upscale to 4K and convert to 60FPS" profile. Which only performed at 1.2FPS. Even my W3690 can encode 4K HEVC video faster than that. Therefore, hardware encoding isn't that critical for this particular process.
Besides, the CPU loading isn't high at all, your X5690 should be more than enough. Of course, the single thread performance may be still the limiting factor. As you can see, the GPU loading also isn't that high. So, it shouldn't be GPU processing power limiting in my test.
And for info, if you want to use hardware encoding with this software for whatever reason, it seems only H264 works. Both HEVC export options use software encoding in my test, and seems no way to change it.
Thank you for your reply. regarding your reference to post #1 Q29, I did see that VideoProc doesn't display HEVC though it is apparently working. I've also refreshed the two options via VideoProc but it still does not display HEVC as enabled. I used your latest OC package and have not done any patching - can you advise if patching is required to get it to display and function properly? I'd be happy to read any instructions if you can point me to the right one.
Thanks for confirming Topaz VEAI would work on the Mac Pro 5,1 with my specs. Strangely, none of the models on either version 2.6.4 and the latest load and I always get error messages when I try to export anything out. I've tried to do what the instructions in the attached from the program specified but nothing has worked, thus I believed Topaz VEAI would not work on this machine. Now I have no idea what is going on. The first more detailed error is from version 2.6.4 and the second is from the latest version.
Thank you for your reply. regarding your reference to post #1 Q29, I did see that VideoProc doesn't display HEVC though it is apparently working. I've also refreshed the two options via VideoProc but it still does not display HEVC as enabled. I used your latest OC package and have not done any patching - can you advise if patching is required to get it to display and function properly? I'd be happy to read any instructions if you can point me to the right one.
Thanks for confirming Topaz VEAI would work on the Mac Pro 5,1 with my specs. Strangely, none of the models on either version 2.6.4 and the latest load and I always get error messages when I try to export anything out. I've tried to do what the instructions in the attached from the program specified but nothing has worked, thus I believed Topaz VEAI would not work on this machine. Now I have no idea what is going on. The first more detailed error is from version 2.6.4 and the second is from the latest version.
Any consensus on "Hash Mismatch detected on volume..."?
Currently using MartinLo's 8.6.0, firmware 9144.0.8.6.0, on 12 Core MacPro4-1,->5,1 with Sapphire Radeon RX 580 8GB.
Periodically, every few weeks or so, I will have a day or two where I will get several "Hash Mismatch" warning popups for my macOS 12.6 boot volume. Is there any consensus as to how to deal with these warnings? Is reinstalling macOS 12.6 or moving MartinLo's 8.8 likely to resolve?
I don’t think there’s a consensus. My current hypothesis is that this is due to a) having concurrent APFS volumes or b) FeatureUnlock. I’ve resolved the issue by reinstalling Monterey (making sure that the corresponding volume is the only APFS one by converting my fallback Mojave installation to HFS+) and replacing FeatureUnlock by NightShiftEnabler (sufficient for my needs).
what could be the issue when my bootpicker is static? like i see it but i don't see the selected drive changing on screen (althou it is changing it). I was working before and just suddently stopped...
I don't have 2.6.4. Did you follow the suggestion to lower the Max VRAM, and reduce machine load?
On the other hand, there is no need to patch the OS, in fact, better not to (that's why we use OpenCore to achieve what we want).
Anyway, I just check Topaz's official website. Mojave only has CPU support. If you want to utilise your GPU, you have to upgrade your macOS. View attachment 2145575
Just wanted to say thank you for your responses and help - I really appreciate it. I updated my OS to Catalina and that seemed to have resolved my issues. I see both H264 and HEVEC enabled in VideoProc now, and I can run Topaz VEAI on my Mac Pro 5,1. Amazing work on this to those responsible!
Yup! Very smooth install. A pretty quick one as well, much quicker than other Monterey installations. Then again, we're just getting security updates at this point and no new features. Will ride this Mac Pro for as long as I can!
I am having issue with bluetooth. I am running Monterey 12.6.3 and the bluetooth was working couple of days ago. When I go to system preference I can't turn Bluetooth on. In my config.plist, I have both BluetoolFixUp and BlueTooth-Spoof enabled. The weird thing is when I restart the computer and the boot picker shows up I am a to move the cursor with the bluetooth trackpad. But when the computer goes to the login screen the bluetooth stops working. Any suggestions on how to fix this issue?
I am having issue with bluetooth. I am running Monterey 12.6.3 and the bluetooth was working couple of days ago. When I go to system preference I can't turn Bluetooth on. In my config.plist, I have both BluetoolFixUp and BlueTooth-Spoof enabled. The weird thing is when I restart the computer and the boot picker shows up I am a to move the cursor with the bluetooth trackpad. But when the computer goes to the login screen the bluetooth stops working. Any suggestions on how to fix this issue?
