You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{"debug": true,"enableWorker": true,"lowLatencyMode": true,"backBufferLength": 90,"widevineLicenseUrl": "",/* I can not provide this for security reason */"emeEnabled": true}}
The stream has correct Access-Control-Allow-Origin headers (CORS)
There are no network errors such as 404s in the browser console when trying to play the stream
Steps to reproduce
The error could be reproduced in the demo page. But I can not provide a test stream for security reason. If you need one please email me wenjieshao@tubi.tv .
Expected behaviour
The DRM content that can not be played, should throw out an error.
What actually happened?
The content will stop without any error playing after several seconds. I filtered the output log by eme. You can see the key status changed from usable to internal-error. But the hls instance didn't throw out any error. It just waiting for new session, which is useless.
In my testing the key-status changed to 'output-restricted' which results in HDCP level filtering (but not HDCP levels were specified). As all variants share the same key, none of them are playable. Adding an HDCP-LEVEL attribute to each variant would result in skipping attempts to load other levels with the same HDCP level or higher. The error should surface as fatal faster this way.
I can't speak to why you got a "internal-error" status. I saw a mention of this being related to the device not having the resources to the handle another key-system session. According to the spec this status is not actionable.:
internal-error | The key is not currently usable for decryption because of an error in
the CDM unrelated to the other values. This value is not actionable by the application.
We could treat it like output-restricted but it looks like this already should be escalated to fatal. You should be able to handle it yourself, and without handling it, hls.js is expected to stop on fatal errors:
What version of Hls.js are you using?
1.5.7
What browser (including version) are you using?
Chrome 119.0.6045.199
What OS (including version) are you using?
Mac OS 13.6
Test stream
No response
Configuration
Additional player setup steps
Nothing
Checklist
Steps to reproduce
The error could be reproduced in the demo page. But I can not provide a test stream for security reason. If you need one please email me wenjieshao@tubi.tv .
Expected behaviour
The DRM content that can not be played, should throw out an error.
What actually happened?
The content will stop without any error playing after several seconds. I filtered the output log by
eme
. You can see the key status changed fromusable
tointernal-error
. But the hls instance didn't throw out any error. It just waiting for new session, which is useless.Console output
The text was updated successfully, but these errors were encountered: