WebM Lacing 3 not supported on Media Source Extensions
Reported by
download...@gmail.com,
Apr 22 2018
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36 Steps to reproduce the problem: 1. Get a webm media file containing Blocks that are encoded using lacing 3. 2. Break it into initialization and media segments as per https://www.w3.org/TR/mse-byte-stream-format-webm/ 3. Use sourceBuffer.appendBuffer() to append the segments to a MediaSource that is attached to a video tag. It seems that lacing 3 (EBML lacing) is not supported for webm clusters that are appended to an MSE SourceBuffer. The video plays fine when the file is opened in a tab though, so it can definitely render the laced frames, but won't for a MediaSource. What is the expected behavior? Media plays normally. What went wrong? Error in the console that says: MediaError {code: 3, message: "CHUNK_DEMUXER_ERROR_APPEND_FAILED: Lacing 3 is not supported yet."} Did this work before? N/A Does this work in other browsers? N/A Chrome version: 66.0.3359.117 Channel: stable OS Version: 10.0 Flash Version: I checked out line 202 of media/webm/webm_cluster_parser.cc and it seems as though the cluster parser specifically does not support lacing of any kind. Since lacing is supported when playing media from a file directly, is there any reason it can't be supported for webm clusters from MSE?
,
Apr 23 2018
reporter@ - Thanks for filing the issue...!! Could you please provide a sample test file/url to test the issue from TE-end. This will help us in triaging the issue further. Thanks...!!
,
Apr 25 2018
I actually can't seem to replicate this now. I've just re-run the test and it still crashes, but now it just says:
MediaError {code: 4, message: "DECODER_ERROR_NOT_SUPPORTED: audio decoder initialization failed"}
No further information in media-internals. Same file, so I'm not sure what changed.
,
Apr 25 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 26 2018
@Reporter: From the link provided in original comment(C#0) would you please highlight which link should be picked to test the issue i.e., providing with the specific link which is related to test case would help us in triaging the issue in a better way. Thanks!
,
May 31 2018
As there is no response from the reporter for more than one month. Hence, closing the issue as wontFix. Please feel free to raise a new issue if the issue is reproduced with latest chrome builds. The latest chrome builds can be downloaded from the below URL: https://www.chromium.org/getting-involved/dev-channel Thanks...!! |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by susan.boorgula@chromium.org
, Apr 22 2018