3 ms·
Doesn't the Media Capabilities API [1] provide a way to determine if a codec is "power efficient" (presumably meaning hardware supported)? So then you can switc
by AshleysBrain 3y ago
Doesn't the Media Capabilities API [1] provide a way to determine if a codec is "power efficient" (presumably meaning hardware supported)? So then you can switch to another codec if AV1 isn't hardware-supported.
[1] https://developer.mozilla.org/en-US/docs/Web/API/Media_Capabilities_API/Using_the_Media_Capabilities_API https://developer.mozilla.org/en-US/docs/Web/API/Media_Capab...
- jorvi 3y agoThat might be, but on (most?) Chromium browsers you have to install h264ify to force-disable AV1/VP9 on devices that have no AV1 hardware decode. What is even more annoying is that you can only do a full disable. You can’t disable AC1/VP9 video decode but leave image decode intact.
- AshleysBrain 3y agoWhat I'm saying is in an ideal world web content should be able to detect whether some codecs are not hardware-accelerated, and so such workarounds should not be necessary. Of course, lots of naive web content might just check if it's supported and use it anyway... but surely the big sites like YouTube get this right? Software decode has its uses - if you just want a small GIF-style looping clip, hardware support doesn't matter much, and it's nice to have one codec that can be relied upon to work everywhere.
- blibble 3y agogoogle is far more interested in not paying royalties than your battery life on youtube
- samtheprogram 3y agoThanks for shouting out h264ify. I run older hardware and have been (mostly passively / randomly) trying to figure out how to use less resources. A lot of older hardware isn’t _too much slower_ than today’s with the exception of these codecs wasting system resources.