Closed
Bug 1463213
Opened 7 years ago
Closed 7 years ago
Decoder error when changing from clear to encrypted content
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1454630
People
(Reporter: modmaker, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36
Steps to reproduce:
Play MSE content that contains multiple initialization segments where the first is clear and the second is encrypted.
WebM:
https://shaka-player-demo.appspot.com/demo/#asset=https://storage.googleapis.com/shaka-demo-assets/_bugs/firefox-clear-then-encrypted/dash.mpd;license=https://cwip-shaka-proxy.appspot.com/no_auth;lang=en-US;build=uncompiled;play
MP4:
https://shaka-player-demo.appspot.com/demo/#asset=https://storage.googleapis.com/shaka-demo-assets/_bugs/firefox-clear-then-encrypted/mp4.mpd;license=https://cwip-shaka-proxy.appspot.com/no_auth;lang=en-US;build=uncompiled;play
Actual results:
Decoder errors after getting to past the clear lead of the encrypted content (at about 1:10).
Expected results:
The video should play fine to the end. This plays fine in Chrome.
This is created from two different assets that appear in the drop-down menu on that site; the first minute is from the 'Sintel 4k (multicodec)' asset, the second minute is from the 'Sintel 4k (multicodec, Widevine)' asset. Both assets play fine by themselves.
Both clips above contain the same source content, but one is WebM and one is MP4. Both cause errors, but the WebM version gets explicit decoder error events while the MP4 one just causes visual playback problems.
Note that the Player attaches a MediaKeys object before appending the first clear segments. The browser also gets the required keys from the license server, so it isn't because of missing keys.
Comment 1•7 years ago
|
||
This may be duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=1454630
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•