[MSE] Enable MP4 support instead of WebM on Windows

RESOLVED FIXED in mozilla36

Status

()

defect
RESOLVED FIXED
5 years ago
4 years ago

People

(Reporter: ajones, Assigned: ajones)

Tracking

(Blocks 1 bug)

Trunk
mozilla36
All
Windows 8.1
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments, 1 obsolete attachment)

Enable MP4 support for MSE on Windows and disable WebM support. This will get more testing for MP4 playback on Windows.
Assignee: nobody → ajones
Status: NEW → ASSIGNED

Updated

5 years ago
Attachment #8521099 - Flags: review?(cajbir.bugzilla) → review+
Attachment #8521099 - Attachment is obsolete: true
Comment on attachment 8521972 [details] [diff] [review]
Enable MSE support for MP4 on Windows and disable WebM

I'm assuming you've tested that mp4 is working.

I'll look into getting mp4 CI testing running ASAP.
Attachment #8521972 - Flags: review?(karlt) → review+
This bug is necessary for basic playback of EME video on Windows.
Blocks: eme-m1
https://hg.mozilla.org/mozilla-central/rev/fe5ae33fc62d
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla36
Posted image Capture.PNG
youtube.com/html5 isn't detecting MSE/H.264 (see attached)
(In reply to Jet Villegas (:jet) from comment #8)
> Created attachment 8523120 [details]
> Capture.PNG
> 
> youtube.com/html5 isn't detecting MSE/H.264 (see attached)

What is the value of media.mediasource.mp4.enabled in your profile?

(In reply to Matt Woodrow (:mattwoodrow) from comment #9)
> What is the value of media.mediasource.mp4.enabled in your profile?

true.

The JS on youtube.com looks like this:

checkMSECompatibility('video/mp4; codecs="avc1.4d404f"'));

Do we support that codec?
From reading our parsing code, it looks like it's taking 4f (79) as the AVC level. 

I can't find anything about levels higher than 5.2 (52), so I guess that's why its failing. I don't know why youtube is using an AVC level that doesn't appear to exist though.
That's interesting, they're not using that codec for actual videos (that I've seen so far), just for the feature test on youtube.com/html5.

We could do the same as chrome as report that we support all avc1.* codecs, hardcode this specific one, or contact youtube and ask them to test with a real codec.

What do you think Anthony?
Flags: needinfo?(ajones)
I've already asked YouTube about this but didn't get an actionable answer. I will follow up on it.
Is this change permanent? (That is, do we give up spreading WebM completely?) If not, "hardcode this specific one" would be a sensible option until Google responds.
(In reply to Masatoshi Kimura [:emk] from comment #15)
> Is this change permanent? (That is, do we give up spreading WebM
> completely?)

No.

> If not, "hardcode this specific one" would be a sensible option
> until Google responds.

The youtube.com/html5 page is bogus but YouTube itself functions correctly.
Flags: needinfo?(ajones)
No longer blocks: eme-m1

Updated

4 years ago
Depends on: 1118528

Comment 17

4 years ago
The YouTube HTML5 page was fixed back in November. If this issue was about improper reporting on that page, it appears to now be fixed.

(On Mac, H.264 + MSE still is red/false; This is accurately reflecting the fact that the Cisco OpenH264 plugin doesn't support the extended profiles needed for MSE H.264 playback.)
MSE playback with MP4 should be available on Mac OSX in beta, aurora and nightly.

Comment 19

4 years ago
all 60fps youtube videos refuse to play and eventually fallback to another codec. Windows7 FF36.
MSE support was turned off for Firefox 36 because there were still too many problems with it (the crash volume was too high). It should work in Firefox 37 and up.
(In reply to Emanuel Hoogeveen [:ehoogeveen] from comment #20)
> MSE support was turned off for Firefox 36 because there were still too many
> problems with it (the crash volume was too high). It should work in Firefox
> 37 and up.

Bug 1127925 and bug 1128170.
You need to log in before you can comment on or make changes to this bug.