MSE with webm/vp9 should be automatically enabled on platform with VP9 hardware decoder

NEW
Unassigned

Status

()

P3
normal
3 years ago
9 months ago

People

(Reporter: jya, Unassigned)

Tracking

(Depends on: 1 bug, Blocks: 2 bugs)

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox48 affected)

Details

(Reporter)

Description

3 years ago
We currently override the media.mediasource.webm.enabled value if:
1- mp4/h264 isn't available
2- h264 isn't hardware accelerated
3- We can decode vp9 quickly enough.

We should also enable it on machines that have hardware VP9 capabilities (some haswell and later intel, or android devices)
(Reporter)

Updated

3 years ago
Depends on: 1260305
(Reporter)

Updated

3 years ago
Duplicate of this bug: 1268886
(Reporter)

Updated

3 years ago
Depends on: 1268886
Mass change P2 -> P3
Priority: P2 → P3
Jean-Yves - is this still an issue?
Flags: needinfo?(jyavenard)
(Reporter)

Comment 4

9 months ago
yes it is... it should be done. The enabling of MediaCapabilities however may alleviate the problem, as following bug 1409664, will be able to properly detect if hardware decoding is enabled or not

Removing the dependency on 1399019, as facebook doesn't use vp9 but h264.
No longer blocks: 1399019
Flags: needinfo?(jyavenard)

Comment 5

9 months ago
@jya Actually, this is blocking bug 1399019 in part, since *some* Facebook videos do play vp9 :) Not all videos have vp9 encodings, but some do. Specifically, most 360 videos do play VP9 by default on Desktop. I'm on the 360 videos team @ FB and we just disabled VP9 delivery on Firefox Windows after discovering it wouldn't play (had previously disabled it for MAC only following bug 1403412, but we did not know that it was now disabled on Windows as well.
(Reporter)

Updated

9 months ago
Blocks: 1399019
You need to log in before you can comment on or make changes to this bug.