webm file which is not playable on Firefox but playable on Chrome and normal video player
Categories
(Core :: Audio/Video: Playback, defect)
Tracking
()
People
(Reporter: xidorn, Unassigned)
Details
Attachments
(1 file)
|
779.49 KB,
video/webm
|
Details |
The attached media file is not playable on Firefox, either inside a page (from jira) or open it directly with Firefox. However this file is playable on Chrome and VLC.
I also used ffprobe to dump its metadata, and its codec seems to be quite normal:
Input #0, matroska,webm, from 'xxx.webm':
Metadata:
encoder : w69b-mediawriter
Duration: 00:00:15.18, start: 0.000000, bitrate: 420 kb/s
Stream #0:0(eng): Audio: opus, 48000 Hz, mono, fltp (default)
Stream #0:1(eng): Video: h264 (Constrained Baseline), yuv420p(progressive), 1366x768, SAR 1:1 DAR 683:384, 16.67 tbr, 1k tbn, 2k tbc (default)
Firefox should probably support this kind of file as they may appear in the wild.
|
||
Comment 2•7 years ago
|
||
Sure
|
|
||
Comment 3•7 years ago
|
||
Xidorn, WebM containers are only supposed to carry VP8 or VP9 video. [0]
Bryce, are you aware of any move to support H.264 in WebM in Firefox?
[0] https://developer.mozilla.org/en-US/docs/Web/HTML/Supported_media_formats#WebM
|
Reporter | |
Comment 4•7 years ago
|
||
I see.
But the file is not produced by me. It appears that there is at least some software produces this kind of combination, and Chrome doesn't have problem playing it. It might cause web compatibility issue?
I'm not sure about interoperability on media... if this is a combination which shouldn't be accepted, should we ask Chrome to remove it?
(In reply to Nico Grunbaum [:ng] from comment #3)
Xidorn, WebM containers are only supposed to carry VP8 or VP9 video. [0]
Bryce, are you aware of any move to support H.264 in WebM in Firefox?
[0] https://developer.mozilla.org/en-US/docs/Web/HTML/Supported_media_formats#WebM
I'm not aware of any plans at this time. I'm going to hold the NI to remind me to discuss this and confirm one way or the other.
(In reply to Xidorn Quan [:xidorn] UTC+10 from comment #4)
I see.
But the file is not produced by me. It appears that there is at least some software produces this kind of combination, and Chrome doesn't have problem playing it. It might cause web compatibility issue?
I'm not sure about interoperability on media... if this is a combination which shouldn't be accepted, should we ask Chrome to remove it?
It would be ideal if other applications didn't create or play such files, since they're not specified (the webm docs only mention VP8 and 9). It seems production of such files from Chrome's media recorder is intentional though, so I'm not sure how willing they'd be to change their behaviour there.
|
|
Reporter | |
Comment 6•7 years ago
|
||
(In reply to Bryce Seager van Dyk (:bryce) from comment #5)
It seems production of such files from Chrome's media recorder is intentional though, so I'm not sure how willing they'd be to change their behaviour there.
This link doesn't seem to be related to this issue. Wrong link maybe?
|
|
||
Comment 7•7 years ago
•
|
||
Bug 1422891, mentions that Chrome's media recorder records to Matroska (which is a superset of WebM). Perhaps the file was renamed?
(In reply to Xidorn Quan [:xidorn] UTC+10 from comment #6)
(In reply to Bryce Seager van Dyk (:bryce) from comment #5)
It seems production of such files from Chrome's media recorder is intentional though, so I'm not sure how willing they'd be to change their behaviour there.
This link doesn't seem to be related to this issue. Wrong link maybe?
Thanks for the heads up. I've corrected the link now.
|
|
Reporter | |
Comment 9•7 years ago
|
||
Filed an issue to WebM: https://bugs.chromium.org/p/webm/issues/detail?id=1628
|
|
Reporter | |
Comment 10•7 years ago
|
||
Based on reply from the WebM issue tracker, the file is actually not a WebM file, but a Matroska container. And indeed Chrome seems to be able to play arbitrary MKV file (via simply rename them to .webm).
I'm not sure what should be done here, then...
|
|
Reporter | |
Comment 11•7 years ago
|
||
Filed an issue to Chromium: https://bugs.chromium.org/p/chromium/issues/detail?id=967100
I'm marking this as a dupe of bug 1422891. While this bug is around webm, I believe the crux of this issue if we choose to support .mkv. Webm is largely a constrained form of Matroska, but Chrome have been choosing to relax their constraints on handling Webms such that they're now handling what is (IMO) essentially mkv files. So in order to support these kinds of files we're going to need to at least in part support mkv.
Description
•