Closed
Bug 1072719
Opened 11 years ago
Closed 6 years ago
Provide way for GMPs to specify what profiles/levels they support
Categories
(Core :: Audio/Video: GMP, defect, P3)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: cpearce, Unassigned)
References
Details
We need to be able to tell what H.264 profiles/levels/constraints a GMP can play. Ditto for AAC.
We need this so that HTMLMediaElement.canPlayType() and MediaKeys.isTypeSupported() can accurately report what H.264/AAC levels/profiles we can play.
I describe the H.264 codecs parameters.
http://blog.pearce.org.nz/2013/11/what-does-h264avc1-codecs-parameters.html
For example, avc1.4D401E is main, level 3. We've been identifying H.264 in GMPs .info file by the tag "h264", but web content actually identifies H.264 by a "codecs=avc..." string as in the previous example.
The naive implementation would be to enumerate them in the GMP's .info file. But for H.264, there are at least 17 levels and at least 3 profiles we care about. I don't know how many permutations of the constraint flags we need to care about. So there would be lots of permutations, so that's not an elegant solution...
| Reporter | ||
Comment 1•11 years ago
|
||
For the first Adobe/Windowns >= Vista release we can just assume that their decoder can play everything that WMF's decoder can play. So we don't need to be fancy in the short term. Long term, a better solution would be nice.
Comment 2•11 years ago
|
||
These bugs are fit and finish issues that might block EME uplift to Aurora.
Blocks: eme-m3
Updated•10 years ago
|
Component: Audio/Video → Audio/Video: MSG/cubeb/GMP
Updated•10 years ago
|
Component: Audio/Video: MediaStreamGraph → Audio/Video: GMP
Updated•10 years ago
|
Rank: 25
Priority: -- → P2
Comment 3•8 years ago
|
||
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
| Reporter | ||
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•