Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
MP 1,1-5,1 Activate AMD hardware acceleration
- Thread starter h9826790
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
QuickTime Player cannot export this sample video. This is normal, but not because HWAccel is not working. Some video / audio codec cannot be export in QuickTime. No idea why, but it's been like that for many years already.
QuickTime Player is not a good video converter anyway. It has this kind of function, but very limited.
HWAccel also has its own limitation, e.g. some encoding parameters cannot be changed.
I already showed you this particular video and be fully hardware decode and hardware encode in VideoProc. The screen recording also show you the parameters used. You may try the same thing, and see if get the same result.
Last edited:
In fact, your screen capture in this post suggest that everything is working as expected. That “Intel” is just cosmetic, doesn’t really matter, it’s about how fast you can decode / encode now.
31 FPS is what your GPU can do. Did you monitor the CPU usage? That should be nearly idle. Which is a clear sign that HWAccel was working. Otherwise, which piece of hardware was doing the conversion?
You may also try the same hardware setup, but boot Without HWAccel, and do the same conversion again (of course, no HWAccel indication will be available in the settings page), and see how many FPS you can get for the same video conversion, and what’s the CPU loading. At least, VideoProc should show “CPU”, but not “Intel” anymore.
I haven’t try it yet, not at home now. However, my understanding, Perian only makes QuickTime Player able to play some extra videos codecs. Since QuickTime already can play this sample video, it shouldn’t help anything. And I don’t think it gives QuickTime Player any extra encoding / export ability.
This woke up some long-dormant brain cells. Perian was essentially an extension to Quicktime. The old 32-bit version was described as a Swiss army knife, and all sorts of "add-ons" could extend functionality. The project was shut down in 2012. IIRC, this was shortly before the transition to what we now call Quicktime Player - 64-bits and not very extensible.
Have you considered patching the latest version of the framework instead?
HEVC encoding/decoding still works in Mojave with the latest compiled debug versions of WEG, Lilu and open core.efi with smbios spoofing as iMac Pro. So no hope for Catalina as I can't even boot with iMac Pro smbios spoofing (dual Xeons). The situation is getting worst unless WEG developers step up to the plate.
"Dual Socket User Note: Do note that macOS Catalina no longer supports dual socket CPUs and that the macOS kernel only supports a maximum of 64 threads. So for baller setups please be aware.
Bye bye dual Xeons. Single CPU's might have luck
- Intel Atoms
- Intel Celerons
- Intel Pentiums
- Intel X79/LGA 2011
- Intel X99/LGA 2011-V3
- Intel X299/LGA-2066 `
Bye bye dual Xeons. Single CPU's might have luck
Last edited:
My single W3690 works well in 10.15.2, I still get full HWAccel by using Opencore.
I installed the latest official release of Lilu and WEG, but only use Shikigva=64.
I tested 160 or 144 some time ago, won’t do anything better but worse. So, I just stick with 64, at least HWAccel always work, and I can get some (only some) DRM streaming playing correctly in the TV apps (same as iTunes movies in Mojave).
TBH, if not because Catalina lack of 32bit software support, I will be to switch to Catalina. But at this moment, I still occasionally need to use some 32bit apps. So, even my single processor setup can works well in Catalina. My daily OS still Mojave at this moment.
I installed the latest official release of Lilu and WEG, but only use Shikigva=64.
I tested 160 or 144 some time ago, won’t do anything better but worse. So, I just stick with 64, at least HWAccel always work, and I can get some (only some) DRM streaming playing correctly in the TV apps (same as iTunes movies in Mojave).
TBH, if not because Catalina lack of 32bit software support, I will be to switch to Catalina. But at this moment, I still occasionally need to use some 32bit apps. So, even my single processor setup can works well in Catalina. My daily OS still Mojave at this moment.
64 is even worst at least for the decoder check tool where it says decoder failed and acceleration is not working same as before.
That’s strange, 64 work perfectly for me (of cost, except Safari can’t really play DRM content), but everything else work as expected.
What boot argument you actually use in OpenCore?
Except Lilu and WEG, any other kext?
Did you try the non debug version kext?
Do you use OpenCore to rename GFX0?
What boot argument you actually use in OpenCore?
Except Lilu and WEG, any other kext?
Did you try the non debug version kext?
Do you use OpenCore to rename GFX0?
Code:
<key>boot-args</key>
<string>-v -liludbgall liludump=10 debug=0x144 -no_compat_check agdpmode=pikera -wegtree shikigva=64 shiki-id=Mac-7BA5B2D9E42DDD94</string>No
Not yet
Yes look at the boot arguments above
Everything was working fine in 10.15.1
Remove shiki-id=Mac-7BA5B2D9E42DDD94. We use OpenCore to spoofing the SMBIOS directly, no need this argument.
Remove -wegtree, use OpenCore ACPI patch to rename PXS1 to GFX0 (mot WEG), you may refer to my shared config.plist
shikigva=64 is just for helping to get some DRM streaming work. If no DRM streaming work for you, you can also remove this argument.
What do you mean set the full blown SMBIOS of the imacpro in the config file? As I mentioned before if I do that I get kernel panic on boot in Catalina due to my dual xeons setup, so this is not an option for me.
My dual-processor machine has had no issues with Catalina or SMBIOS spoofing...
Essentially. Although my configuration is a work in progress. Originally, I had the ACPI patch for GFX0, but now I use the WEG boot argument.
Still no boot with your exact file. Maybe you can attach the kexts and the opencore.efi for testing. I got the latest they are not posted yet I have compiled them.
I have reinstalled a fresh unmodified Catalina10.15.2 on another drive. But still panic on boot:
Then I reduced the boot arguments to :
which put it into continuous reboot loop (I guess because debug=0x144 is not there) with the same kernel panic as I can catch on the fast changing screen. It might be those specific processors I have. @cdf what are yours?
Edit: just look at your signature. It looks you are using x5680.
Code:
*** Panic Report ***
mp_kdp_enter() can't get x86_topo_lock! Debugging anyway! #YOLO
panic(cpu 14 caller 0xffffff802006520a): Kernel trap at 0xffffff7fa4b1dcf9, type 13=general protection, registers:
CR0: 0x000000008001003b, CR2: 0x00007f9296c01000, CR3: 0x000000002529b000, CR4: 0x00000000000226e0
RAX: 0xffffff8113940ae0, RBX: 0xffffff8020a89238, RCX: 0x000000000000205c, RDX: 0x0000000000000000
RSP: 0xffffff8e221d0e80, RBP: 0xffffff8e221d0eb0, RSI: 0xffffff8117f69860, RDI: 0x0000000000000002
R8: 0x0000000000000001, R9: 0x0000000000000000, R10: 0x0000000000000000, R11: 0x0000000000000000
R12: 0x00000000000000a8, R13: 0x0000000000000000, R14: 0xffffff8020a55648, R15: 0xffffff8114b75b00
RFL: 0x0000000000010082, RIP: 0xffffff7fa4b1dcf9, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x00007f9296c01000, Error code: 0x0000000000000000, Fault CPU: 0xe VMM, PL: 2, VF: 0
Backtrace (CPU 14), Frame : Return Address
0xffffff801fd58220 : 0xffffff801ff3bb1b
0xffffff801fd58270 : 0xffffff80200733e5
0xffffff801fd582b0 : 0xffffff8020064e5e
0xffffff801fd58300 : 0xffffff801fee2a40
0xffffff801fd58320 : 0xffffff801ff3b207
0xffffff801fd58420 : 0xffffff801ff3b5eb
0xffffff801fd58470 : 0xffffff80206d24f9
0xffffff801fd584e0 : 0xffffff802006520a
0xffffff801fd58660 : 0xffffff8020064f08
0xffffff801fd586b0 : 0xffffff801fee2a40
0xffffff801fd586d0 : 0xffffff7fa4b1dcf9
0xffffff8e221d0eb0 : 0xffffff802006e3a3
0xffffff8e221d0f20 : 0xffffff802006e082
0xffffff8e221d0f60 : 0xffffff802006cf83
0xffffff8e221d0f80 : 0xffffff802006465b
0xffffff8e221d0fd0 : 0xffffff801fee2bed
0xffffff8e3441bf40 : 0xffffff801ff609b7
0xffffff8e3441bf80 : 0xffffff801ff60b78
0xffffff8e3441bfa0 : 0xffffff801fee213e
Kernel Extensions in backtrace:
com.apple.driver.AppleIntelMCEReporter(115.0)[11008172-3D20-36B6-876F-7886A3C18DE4]@0xffffff7fa4b18000->0xffffff7fa4b2afff
dependency: com.apple.iokit.IOACPIFamily(1.4)[3467C105-9354-3BD2-85F3-E5AEF94BD275]@0xffffff7fa1035000
dependency: com.apple.iokit.IOPCIFamily(2.9)[1286D5E5-A6A1-3C44-A244-04C068903DB2]@0xffffff7fa092f000
BSD process name corresponding to current thread: kernel_task
Boot args: -v -liludbgall liludump=10 debug=0x144 -no_compat_check -wegtree shikigva=160 shiki-id=Mac-7BA5B2D9E42DDD94
Mac OS version:
19C57
Kernel version:
Darwin Kernel Version 19.2.0: Sat Nov 9 03:47:04 PST 2019; root:xnu-6153.61.1~20/RELEASE_X86_64
Kernel UUID: C3E7E405-C692-356B-88D3-C30041FD1E72
Kernel slide: 0x000000001fc00000
Kernel text base: 0xffffff801fe00000
__HIB text base: 0xffffff801fd00000
System model name: iMacPro1,1 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: YES (0x0)
System uptime in nanoseconds: 78945583769
EOF
Model: MacPro5,1, BootROM 144.0.0.0.0, 12 processors, 6-Core Intel Xeon, 3.46 GHz, 128 GB, SMC 1.39f11
Graphics: Radeon RX 480, Radeon RX 480, spdisplays_pcie_device, 8 GB
Graphics: Radeon RX 480, Radeon RX 480, spdisplays_pcie_device, 8 GB
Memory Module: DIMM 1, 16 GB, DDR3 ECC, 1333 MHz, 0x0000, -
Memory Module: DIMM 2, 16 GB, DDR3 ECC, 1333 MHz, 0x0000, -
Memory Module: DIMM 3, 16 GB, DDR3 ECC, 1333 MHz, 0x0000, -
Memory Module: DIMM 4, 16 GB, DDR3 ECC, 1333 MHz, 0x0000, -
Memory Module: DIMM 5, 16 GB, DDR3 ECC, 1333 MHz, 0x0000, -
Memory Module: DIMM 6, 16 GB, DDR3 ECC, 1333 MHz, 0x0000, -
Memory Module: DIMM 7, 16 GB, DDR3 ECC, 1333 MHz, 0x0000, -
Memory Module: DIMM 8, 16 GB, DDR3 ECC, 1333 MHz, 0x0000, -
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.106.98.102.31)
Bluetooth: Version 6.0.14d3, 3 services, 27 devices, 1 incoming serial ports
Network Service: Ethernet 1, Ethernet, en0
Network Service: Wi-Fi, AirPort, en2
PCI Card: Radeon RX 480, Display Controller, Slot-1
PCI Card: pci1002,aaf0, Audio Device, Slot-1
PCI Card: Radeon RX 480, Display Controller, Slot-2@11,0,0
PCI Card: pci144d,a808, NVM Express Controller, Slot-2@20,0,0
PCI Card: pci1002,aaf0, Audio Device, Slot-2@11,0,1
PCI Card: pci144d,a808, NVM Express Controller, Slot-2@19,0,0
PCI Card: pci1b21,625, AHCI Controller, Slot-4@7,0,0
PCI Card: pci1b21,625, AHCI Controller, Slot-4@6,0,0
PCI Card: pci1b21,2142, USB eXtensible Host Controller, Slot-2@18,0,0
PCI Card: pci1b21,2142, USB eXtensible Host Controller, Slot-2@16,0,0
Serial ATA Device: OWC Mercury Electra 6G SSD, 240.06 GB
Serial ATA Device: Samsung SSD 840 Series, 120.03 GB
Serial ATA Device: HL-DT-ST DVD-RW GH61N
Serial ATA Device: WDC WD50EZRX-00MVLB1, 5 TB
Serial ATA Device: WDC WD1001FALS-403AA0, 1 TB
Serial ATA Device: WDC WD2500AAJS-75M0A0, 250 GB
Serial ATA Device: ADATA SU800, 512.11 GB
USB Device: USB 2.0 Bus
USB Device: USB 2.0 Bus
USB Device: USB2.0 Hub
USB Device: USB 2.0 Camera
USB Device: USB Bus
USB Device: USB Bus
USB Device: USB Bus
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB Bus
USB Device: USB Bus
USB Device: USB Bus
USB Device: Hub in Apple Pro Keyboard
USB Device: Microsoft USB Optical Mouse
USB Device: Apple Pro Keyboard
USB Device: USB 3.1 Bus
USB Device: USB 3.1 Bus
FireWire Device: built-in_hub, Up to 800 Mb/sec
Code:
-v -no_compat_check -wegtreeEdit: just look at your signature. It looks you are using x5680.
Last edited:
WEG changes an hour ago:
[automerge]1576233708[/automerge]
HEVC decoding on AMD GPUs broken in 10.15.2 #613
https://github.com/acidanthera/bugtracker/issues/613
Code:
- Fixed accelerator name update logic for X4xxx kexts
- Fixed Verde IOGVACodec injection to make hardware video decoder work
- Enable software TV+ decoding on all CPUs without IGPU (`shikigva=256`)
- Added HEVC capabilities to AMD6 decoders for all GPUs
#### v1.3.5
- Added Lilu 1.4.0 support, which is now the minimum supported versionHEVC decoding on AMD GPUs broken in 10.15.2 #613
https://github.com/acidanthera/bugtracker/issues/613
Oh yeah, I completely forget that, which CMMChris alerted me before. Polaris HEVC HWAccel was took away by Apple when 10.15.2 still in beta stage. And we actually discussed that in this thread.
https://forums.macrumors.com/thread...n.2180095/page-31?post=27985584#post-27985584
When I saw your KP report about RX480, that caught my eyes, but I can't tell why, because I forget about this issue.
Then everything make sense now, why it work on my setup, but not yours.
Last edited: