webcompat / web-bugs

A place to report bugs on websites.
https://webcompat.com
Mozilla Public License 2.0
742 stars 65 forks source link

www.youtube.com - video or audio doesn't play #59621

Closed webcompat-bot closed 4 years ago

webcompat-bot commented 4 years ago

URL: https://www.youtube.com

Browser / Version: Firefox 81 Operating System: Windows 10 Tested Another Browser: Yes Internet Explorer

Problem type: Video or audio doesn't play Description: The video or audio does not play Steps to Reproduce: https://support.mozilla.org/en-US/questions/1307849 Hello, the following issue concerns all (new) browsers Firefox, Edge Chromium, Chrome and Opium, from what I have tested. I have noticed the issue when using my 2016 notebook which has an intel n3710 cpu.

The issue: 60 fps videos on youtube have severe framedrops (15-20%) on all those browsers. The catch:(old) Edge and Internet Explorer have 0 framedrops. How can this be?

Two things:

  1. By default Youtube uses the VP9 codec for video playback. The (old) Edge browser automatically disables VP9 and fallsback to AVC1 codec, when your hardware doesn't support VP9 decoding. All the newer browsers do not fallback to AVC1, which means even if your hardware doesn't support it, by default VP9 is used, which means high cpu usage, framedrops on 60fps videos, lower battery life. Why do the new browsers not fallback to AVC1 codec on youtube, if the hardware doesn't support it?

  2. There are ways to force the AVC1 codec on youtube on the newer browsers via third party addons, or tweaks in the "about:config", which I already did. Stats-for-nerds on Youtube report that the AVC1 codec is being used, still, 60 fps videos have 15-20% framedrops. Hardware acceleration is active, obviously.

TLDR: Edge (old), Internet Explorer -> Youtube 60fps = 0 framedrops Firefox, Edge Chromium, Chrome -> Youtube 60fps = framedrops

Browser Configuration
  • None

From webcompat.com with ❤️

softvision-oana-arbuzov commented 4 years ago

Thanks for the report, but since the issue concerns all (new) browsers (Firefox, Edge Chromium, Chrome and Opium), this is not a Compatibility issue.

For this project we try to focus our effort on layouts, features or content that works as expected in one browser but not in another. Closing the issue as Non-compat.