`NS_ERROR_DOM_MEDIA_METADATA_ERR` while playing webm containing H.264
Categories
(Core :: Audio/Video: Playback, defect)
Tracking
()
People
(Reporter: glob, Unassigned)
Details
Attachments
(1 file)
|
7.82 MB,
video/webm
|
Details |
Using Nightly 108.0a1 (2022-10-27) on macOS.
https://bugs.chromium.org/p/chromium/issues/detail?id=1379879 has a webm that Firefox fails to play, while Chrome and ffplay can play seemingly without issue. Safari also has problems with this video.
The browser console reports:
Media resource https://bugs.chromium.org/p/chromium/issues/attachment?aid=575114&signed_aid=ieZ1xNHhqJ42rJPXvBdS_g==&inline=1 could not be decoded, error: Error Code: NS_ERROR_DOM_MEDIA_METADATA_ERR (0x806e0006)
Using ffprobe -v error -count_frames -threads auto -hide_banner 1379879-107.webm reports:
[matroska,webm @ 0x7ff65d804ac0] File ended prematurely at pos. 8200757 (0x7d2235)
Comment 1•4 years ago
|
||
INFO : b'[Child 18664, MediaDecoderStateMachine #1] WARNING: Decoder=1a6670a5100 state=DECODING_METADATA Decode metadata failed, shutting down decoder: file /builds/worker/checkouts/gecko/dom/media/MediaDecoderStateMachine.cpp:370'
INFO : b'[Child 18664, MediaDecoderStateMachine #1] WARNING: Decoder=1a6670a5100 Decode error: NS_ERROR_DOM_MEDIA_METADATA_ERR (0x806e0006): file /builds/worker/checkouts/gecko/dom/media/MediaDecoderStateMachineBase.cpp:151'
This bug is not a regression. I can reproduce it at least as far back as Firefox 65 from 2018 on Windows.
Comment 2•4 years ago
|
||
ffprobe shows the file contains H.264 video track:
Stream #0:0(eng): Video: h264 (Constrained Baseline), yuv420p(progressive), 1280x720 [SAR 1:1 DAR 16:9], 30.30 fps, 30 tbr, 1k tbn (default)
Currently, we don't support H.264 in WebM. See bug 1562862.
Updated•4 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Description
•