-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebOS 3.5 is throwing "Failed to execute 'webkitGenerateKeyRequest' on 'HTMLMediaElement': The key system provided ('com.microsoft.playready') is not supported" error. #7770
Comments
@subhanahmed047 tbh it looks like PlayReady is not supported anymore on WebOS, but that would be very surprising. Can you show us a result of |
Where have you seen that it is not supported? According to the webos developers it is supported... https://webostv.developer.lge.com/develop/specifications/streaming-protocol-drm |
@avelad I meant this particular device claims it's not supported, I haven't seen any indication of that on LG documentation. We need to find out is it really not supported sometimes or do we have some issue in our polyfill. |
Closing due to inactivity. If this is still an issue for you or if you have further questions, the OP can ask shaka-bot to reopen it by including |
This is another occurrence of #2915 probably caused by introducing Preload Manager |
I can reproduce this on WebOS 3.0 with both Widevine and Playready. I tried debugging it, but looks like there's some EME polyfill missing, but couldn't figure out where exactly. Sorry if this isn't too helpful 😅 |
Fixes #7770 Webkit DRM heavily relies on video element, so it needs to be provided in proper order to avoid any issues. --------- Co-authored-by: Álvaro Velad Galván <[email protected]>
Fixes #7770 Webkit DRM heavily relies on video element, so it needs to be provided in proper order to avoid any issues. --------- Co-authored-by: Álvaro Velad Galván <[email protected]>
Fixes #7770 Webkit DRM heavily relies on video element, so it needs to be provided in proper order to avoid any issues. --------- Co-authored-by: Álvaro Velad Galván <[email protected]>
@subhanahmed047 sad to hear that, as this fix is working for us internally. |
@tykus160 I just tried the following Widevine-protected HLS stream from Shaka's demo page:
|
@subhanahmed047 do you see it only on Widevine now, or on PlayReady as well? |
It's both. I just chose Widevine for the above test. I did try playready too. |
Are you able to look into this? I'm afraid I'm not able to reproduce it now. Probably you'd need to dive into logic I changed before and check what can be adjusted. |
No worries, I'll look at it next week when I'm in front of a WebOS3. |
Have you read the FAQ and checked for duplicate open issues?
Yes
If the problem is related to FairPlay, have you read the tutorial?
No
What version of Shaka Player are you using?
4.12.4
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from
main
?Yes
Are you using the demo app or your own custom app?
Demo App
If custom app, can you reproduce the issue using our demo app?
Yes
What browser and OS are you using?
Chrome 38 on WebOS 3.5 (LG 2017)
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
Software Version: 05.70.35
What are the manifest and license server URIs?
I'm using the Axinom test vectors. You can find the demo as well the URLs here -> https://github.com/subhanahmed047/shaka-player-demo/blob/main/index.js#L1-L8
What configuration are you using? What is the output of
player.getNonDefaultConfiguration()
?What did you do?
Simply run the above-mentioned demo.
What did you expect to happen?
I expected to see the playback. The current version I'm running with working playback is v4.7.11.
What actually happened?
I get the following error:
This exact error has been fixed in the past here -> #6558
However back then the issue would come up as a
4032
error instead of the6006
error.Are you planning to send a PR to fix it?
Maybe, I just wanted to raise this issue to see if I can get some pointers.
The text was updated successfully, but these errors were encountered: