It's bad. However, luckily 10.14.0 is NOT a bad OS at all. I am happy to keep it but not further update it.
May be it's time to check the Hackintosh forum about how they activate the hardware encode / decode
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.
HDR 4K video support - macOS vs Windows
- Thread starter CreeptoLoser
- Start date
- Sort by reaction score
It's bad. However, luckily 10.14.0 is NOT a bad OS at all. I am happy to keep it but not further update it.
May be it's time to check the Hackintosh forum about how they activate the hardware encode / decode
Wouldn't they mainly just use Quick Sync, since almost all of those are using Core CPUs? Or are you talking specifically about cases where they've used old Xeon server pulls or something?
In fact, NO. macOS basically not support iGPU / dGPU switching. Lots RX580 Hackintosh users actually disabled their iGPU, and really using the RX580 for hardware decode / encode.
That's why in the Hackintosh forum, they are still looking for a way to activate that in Mojave, but not discuss how to use the iGPU for video hardware acceleration.
Heck, I'd be happy even just doing so (hardware decode mainly) in High Sierra. Reckon they have a hack that'd work for us to enable that?
You can try. The hack looks very easy to me.
0) BACK UP your data, know your recovery plan if this hack brick the OS.
1) Locate AMDRadeonX5000.kext in System -> Library -> Extensions
2) Open info plist
3) Copy the setting of IOGVACodec, IOGVAHEVCDecode, IOGVAHEVCEncode, IOGVAVTCapabilities
4) Paste this inside AMDRadeonX4000.kext info.plist
5) Fix permission as required.
will the "hack" or "fix" work in all versions of osx? & can i use text edit?
ill try it on one of my osx installs on a usb stick
wow im amazed osx is not using the iGPU to a large extent what are you doing apple you only have one computer with no iGPU !
edit ops i miss understood >,< my bad
ill try it on one of my osx installs on a usb stick
wow im amazed osx is not using the iGPU to a large extent
what are you doing apple you only have one computer with no iGPU !edit ops i miss understood >,< my bad
Last edited:
wow im amazed osx is not using the iGPU to a large extent
No, no...we’re talking about hardware decode with dGPU (specifically RX 580 in cMP). They use Quick Sync on most everything else, aside from iMac Pro, which uses AMD’s Unified Video Decoder on Vega 56/64.
Last edited:
ah ops, gess i cant run to conclusions.
iv herd of how few apps relay take advantage of the IGPU which always amazes me, it's astounding how adobe never used the IGPU until recently in PP seeing how much of a boost it gave to performance.
back in CS5 there was a plugin made by Intel for PP that used the IGPU (thats 2011!!)
https://software.intel.com/en-us/bl...r-plug-in-for-adobe-pro-and-consumer-products
so i do see it just underused in lots of applications
i gess this is just in regard to pure video decode features and i over reached.
so is text edit ok for editing the .plist file? if so ill try it on a copy of osx i have on a usb stick.
edit
found this from adobe forums, https://forums.adobe.com/message/3693281#3693281
the Intel plugin halved the export/trans coding time, for that use case back in 2011
iv herd of how few apps relay take advantage of the IGPU which always amazes me, it's astounding how adobe never used the IGPU until recently in PP seeing how much of a boost it gave to performance.
back in CS5 there was a plugin made by Intel for PP that used the IGPU (thats 2011!!)
https://software.intel.com/en-us/bl...r-plug-in-for-adobe-pro-and-consumer-products
so i do see it just underused in lots of applications
i gess this is just in regard to pure video decode features and i over reached.
so is text edit ok for editing the .plist file? if so ill try it on a copy of osx i have on a usb stick.
edit
found this from adobe forums, https://forums.adobe.com/message/3693281#3693281
the Intel plugin halved the export/trans coding time, for that use case back in 2011
Last edited:
will the "hack" or "fix" work in all versions of osx? & can i use text edit?
ill try it on one of my osx installs on a usb stick
wow im amazed osx is not using the iGPU to a large extent
edit ops i miss understood >,< my bad
Definitely not for any OSX / macOS. Even the small .1 update may break this hack.
I won't be back in front of my Mac Pro until tomorrow night or Tuesday, but I'll give this a try then.
Tried this just now, and did not have success. Still runs at 300-600% CPU and develops choppiness at times. Made sure to rebuild kext caches, and verified X4000 driver was loaded in System Profiler (although w/ the modification, it does mention "Kext signature validation error code -67030"). This was on 10.13.6. Any other ideas on what to check?
Not sure, that’s what I see in that thread, I never tried that myself, not sure if I missed any key element.
This is because the OS or GPU is not sending the metadata flag to the display or tv.
This was also the problem in the beginning with HDR in Windows.
Something like madVR could fix this in the Mac.
A-ha....watching the Apple Event and the Mac product manager doing the Mac mini intro spilled it that the T2 chip does HEVC encode...which kinda answers whether the iMac Pro was doing its HEVC encode decode via Vega or T2....
...so I guess HEVC on the RX 580 for us was just a pipe dream tease. Boo.
...so I guess HEVC on the RX 580 for us was just a pipe dream tease. Boo.
found this white paper from apple, but only talks about security
https://www.apple.com/mac/docs/Apple_T2_Security_Chip_Overview.pdf
https://www.apple.com/mac/docs/Apple_T2_Security_Chip_Overview.pdf
Thanks, I think.
While I took 2 years of German in high school, I was never fluent and most of it escapes me now! I guess I can try to Google Translate. Or if you care to summarize... I was busing on something else recently (e.g. apply liquid metal to my CPU and GPU
). So, didn't out any time to this hardware HEVC encoding / decoding mod test.Also, it seems this test only available in HS, and I am with Mojave already.
A-ha....watching the Apple Event and the Mac product manager doing the Mac mini intro spilled it that the T2 chip does HEVC encode...which kinda answers whether the iMac Pro was doing its HEVC encode decode via Vega or T2....
...so I guess HEVC on the RX 580 for us was just a pipe dream tease. Boo.
Didn't watch that, but test was done in another thread by the iMac Pro users, and quite sure it's the Vega do all the HEVC jobs, not the T2 chip.
Any recommended method to roll back from 10.14.1 to 10.14.0 for HEVC encoding on a Polaris card? Data doesn't need to persist.
Also, it seems like we only have confirmation that Polaris decoding was broken in 10.14.1. Do we know what the status is with Vega decoding as of that release (56, 64, and FE)?
Also, it seems like we only have confirmation that Polaris decoding was broken in 10.14.1. Do we know what the status is with Vega decoding as of that release (56, 64, and FE)?
Don't need keep data -> clean install.
In fact, I downgraded once during the beta 10.14.1 period with the exact same reason. I simply run the full installer (from the backup HS boot drive) and select the 10.14.1 partition as destination.
Something like the Canon printer driver have to be re-installed, but other than that, the system is very normal (I want to keep the data).
Dear experts:
Could you please tell me in the simplest terms possible if the new
Mac mini 2018 is capable of correctly working with HDR10(+) and/or Dolby Vision content? Will the Blackmagic eGPU be required for the job?
Could you please tell me in the simplest terms possible if the new
Mac mini 2018 is capable of correctly working with HDR10(+) and/or Dolby Vision content? Will the Blackmagic eGPU be required for the job?