Video robustness SW_SECURE_DECODE does not play in Chrome Desktop
See original GitHub issueHave you read the FAQ and checked for duplicate open issues? Yes
What version of Shaka Player are you using? 3.0.3
Can you reproduce the issue with our latest release version? Yes
Can you reproduce the issue with the latest code from master
?
Yes
Are you using the demo app or your own custom app? My own
If custom app, can you reproduce the issue using our demo app? Yes
What browser and OS are you using? Chrome Windows 84.0.4147.135 Stable Chrome Mac 85.0.4183.83 Beta
For embedded devices (smart TVs, etc.), what model and firmware version are you using? n/a
What are the manifest and license server URIs? emailed
What did you do?
Tried to play Widevine content with videoRobustness = SW_SECURE_DECODE
in Shaka config and content key “security_level = 2”(SW_SECURE_DECODE) in the license.
What did you expect to happen? The content to play, based on EME configuration content type and video robustness level promises resolving, (see attached screen grab)
What actually happened? Shaka Error code 4012 with restrictedKeyStatus of ‘internal-error’ (See attached Console screen grab)
I am able to play the content with video robustness and key security level of SW_SECURE_CRYPTO
Thanks!
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (5 by maintainers)
Top GitHub Comments
With Chrome 85 stable on Windows, I see error 6001 (
REQUESTED_KEY_SYSTEM_CONFIG_UNAVAILABLE
), rather than 4012 (RESTRICTIONS_CANNOT_BE_MET
). If the requested robustness level can’t be satisfied, 6001 would be expected. But it’s not clear why you got 4012 instead.I’ll double-check with the Chrome CDM team to see if
SW_SECURE_DECODE
is expected to work for video on desktops.Thanks, Xiaohan, good to hear from you, too! Please say hi to everyone from me.
After more testing yesterday I was worried that the single key was the issue. The partner we are working with currently does not support multi-key. I’ve been working with them to add support, hopefully they will have it soon.
I will use SW_SECURE_CRYPTO for now and close this issue. Thanks to you and @joeyparrish !