3 ms·
>Winning benchmarks was no use if watching a youtube video would nuke my battery life Part of that, of course, will be because YouTube forces video codecs that
by garblegarble 3y ago
>Winning benchmarks was no use if watching a youtube video would nuke my battery life
Part of that, of course, will be because YouTube forces video codecs that may not have hardware acceleration on your platform, preferring their bandwidth over your power consumption (which, of course, is their right - and is a cross-browser issue)
- FirmwareBurner 3y ago>Part of that, of course, will be because YouTube forces video codecs that may not have hardware acceleration on your platform Codecs supported by Youtube (VP9 and x264) have had GPU HW acceleration support on most PCs and laptops sold in the last 8-10 years or longer, just that browsers on Linux never enabled it out of the box because of the wild number of variable on the graphics HW acceleration stack (Mesa, Wayland, VA-API, Nvidia, FOSS/proprietary driver, etc) made it impossible to guarantee it would actually work out of the box, so it defaulted to SW, and HW acceleration was left for the user to tinker figure out on his own, unlike on Windows where you never even had to think about it, it was always working the moment you installed the bowser.
- supertrope 3y agoI think the point they were making is that the ecosystem of VP9 decoding GPUs and the driver, OS, browser stack on top is smaller than the ecosystem of H264. av1 even more so.