Closed Bug 1265043 Opened 9 years ago Closed 9 years ago

"Shaka Error DRM.REQUESTED_KEY_SYSTEM" when trying to play Widevine WebM video "Feelings"

Categories

(Core :: Audio/Video: Playback, defect, P3)

defect

Tracking

()

RESOLVED INCOMPLETE
Tracking Status
firefox47 --- ?
firefox48 --- affected

People

(Reporter: cpeterson, Assigned: cpearce)

References

()

Details

STR: 1. Load http://shaka-player-demo.appspot.com/demo/ 2. Play the YouTube / "Feelings" video. RESULT: The video fails with a red "Error code 6001" message. The video plays correctly on Chrome. I see the following errors in the web console: Player error Object { category: 6, code: 6001, data: Array[0], message: "Shaka Error DRM.REQUESTED_KEY_SYSTE…", stack: "shaka.util.Error@http://shaka-playe…" }main.js:140:3 shakaDemo.onError_()main.js:140 shakaDemo.load/<()asset_section.js:170 (Async: promise callback) shakaDemo.load()asset_section.js:167 (Async: EventListener.handleEvent) shakaDemo.setupAssets_()asset_section.js:84 (Async: promise callback) shakaDemo.init()main.js:79 (Async: EventListener.handleEvent) <anonymous>main.js:156
No longer depends on: 1265040
Works if you set media.webm.enabled=false; this is a Shaka Player bug.
or it is nestegg bug 1261900, which was reported by a Shaka developer.
Depends on: 1261900
No longer depends on: 1261900
Shaka Player should not assume Widevine support implies EME support for WebM. This is Shaka Player issue #342, which should be fixed in the next Shaka Player release. https://github.com/google/shaka-player/issues/342 Firefox will add EME support for WebM in bug 1257716.
Depends on: webm-eme
Priority: -- → P2
Summary: "Shaka Error DRM.REQUESTED_KEY_SYSTEM" when trying to play Widevine video "Feelings" → "Shaka Error DRM.REQUESTED_KEY_SYSTEM" when trying to play Widevine WebM video "Feelings"
No longer depends on: webm-eme
Depends on: 1279077
Mass change P2 -> P3
Priority: P2 → P3
The current Shaka Player demo page does not allow the YouTube "Feelings" video to be selected in Firefox (or Edge or Safari). We can reopen this bug is reproducible later.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.