2 ms·
> Apple is refusing to enable it in software because... Ambiguous, are you saying that they're not enabling the already-present hardware decoding on their devi
by bscphil 7y ago
> Apple is refusing to enable it in software because...
Ambiguous, are you saying that they're not enabling the already-present hardware decoding on their devices in their software, or that they're not adding software decoding to their devices that don't support hardware decoding?
I read it as the latter at first, which had be very confused, so now I assume you meant the former?
- vetinari 7y agoEvery single Intel GPU they ship in their computers has supported VP9 decoding for years. OTH, AMD GPUs they use in some models do not support VP9 in their DSPs; under Windows, AMD used a shader-based decoder for DXVA acceleration up until models with VCN (Raved Ridge APUs), which do support VP9. They have just chosen not to expose it to the userland. In past, they did something similar with Microsoft's VC-1 too: there's not a GPU that doesn't support VC-1 hw decoding, but Apple never exposed it either.
- nwallin 7y agoThe former. iPhones and Intel CPUs have hardware that decodes many different codecs, including vp9 and h264. iOS and OSX have drivers that make hardware decoding available for h264, however they do not make available vp9 decoding, despite the fact that the hardware is perfectly capable of doing it. So you fallback to software decoding, which is problematic at 4k/60fps. People falsely blame YouTube/Google, when it's actually Apple's problem.