Low res encrypted VP9 fails to play |
||||||||
Issue descriptionChrome Version (from "Chrome Settings > About Chrome"): Version 58.0.3029.96 (64-bit) CDM Version: 1.4.8.977 Device (if CrOS): Ubuntu Linux Steps to reproduce: Open https://shaka-player-demo.appspot.com/demo/#asset=//storage.googleapis.com/shaka-demo-assets/_bugs/cdm-vp9-lowres/dash.mpd;license=//widevine-proxy.appspot.com/proxy;lang=en-US;noadaptation;play Observed behavior: Media source fails to append content, with "Append: stream parsing failed. Data size=92844 append_window_start=0 append_window_end=60.062" Expected behavior: Video should play Frequency: 100% Additional comments: The asset linked above only contains VP9/Opus and only at low resolutions (240p and under). If I try the same with higher res tracks (even 360p), or with H264/AAC, or in the clear, the content plays fine. The bug only reproduces with the specific combo of VP9, low res tracks, and CDM. If the content is somehow broken or mis-encoded, please tell me how so I can re-encode our test assets. Thanks!
,
May 4 2017
+wolenetz from MSE side I'll take a look first to see whether there's anything obvious.
,
May 5 2017
I can repro this on ToT. It does seem to be a parsing issue. Assign to wolenetz@ to take a look.
[1:1:0504/171450.467323:VERBOSE1:chunk_demuxer.cc(820)] AppendData(076246a7-c104-4855-bf5f-8d63f93ba9bf, 92844)
[1:1:0504/171450.467538:VERBOSE2:webm_stream_parser.cc(126)] ParseInfoAndTracks()
[1:1:0504/171450.467748:VERBOSE1:webm_stream_parser.cc(121)] ChangeState() : 1 -> 2
[1:1:0504/171450.468468:VERBOSE1:webm_stream_parser.cc(121)] ChangeState() : 2 -> 3
[1:1:0504/171450.468672:ERROR:render_media_log.cc(30)] MediaEvent: MEDIA_ERROR_LOG_ENTRY {"error":"Append: stream parsing failed. Data size=92844 append_window_start=0 append_window_end=60.062"}
,
May 6 2017
,
May 9 2017
Is it necessary that this issue be restricted to Googlers?
,
May 9 2017
,
May 9 2017
Re #5: I don't think so.
,
May 9 2017
,
May 9 2017
,
May 9 2017
,
Jun 13 2017
wolenetz: This is still happening. Do you have any idea whether this is a Chrome issue, or just bad content?
,
Jun 13 2017
I have repro with Linux Chrome 59.0.3071.86 (Official Build) (64-bit)
Using devtools to inspect the $('video').error object reveals the new MediaError.message:
MediaError {code: 3, message: "CHUNK_DEMUXER_ERROR_APPEND_FAILED: Append: stream …44 append_window_start=0 append_window_end=60.062"}code: 3message: "CHUNK_DEMUXER_ERROR_APPEND_FAILED: Append: stream parsing failed. Data size=92844 append_window_start=0 append_window_end=60.062"__proto__: MediaError
tl;dr: It looks like bad content. I'll take a closer look with a debug build to see what the precise error is (and maybe add that detail to MediaError.message in future).
,
Jun 13 2017
Hmm. I'm now unable to repro with a local Debug ToT build. xhwang@, how did you obtain repro in #3?
,
Jun 13 2017
I think I just got it reproed on ToT back then in a debug build....
,
Jun 13 2017
@#14/xhwang@: thanks - I'll look further - either it's a timing issue or something got fixed since M59.
,
Jun 13 2017
It was a Chrome issue, not bad content: Bisection of internal builds showed clearly that https://chromium.googlesource.com/chromium/src/+/7b5d7cc2759780ff45bba356566ba9c76e70c957 is responsible for no longer allowing repro. +bustamante@, kqyang@, vasanthap@ per bug 728773 : This report of a shaka player issue with Chrome without the fix for bug 728773 may support the merge request of the fix to M60. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by joeyparrish@chromium.org
, May 4 2017