Rob Walch
Rob Walch
@krseager it looks like all the feedback has been addressed - did I miss anything? Any ETA on adding tests?
I'd recommend contacting your DRM provider and verifying that the license and certificate URLs and parameters are correct.
The key message is converted to a Uint8Array here: https://github.com/video-dev/hls.js/blob/6e0656ac710f0d46a417cb98480e0d8104070bdb/src/controller/eme-controller.ts#L1009
> I don't think the issue comes from drm provider No, but they should provide technical support with regards to your configuration, and help verify that the license is delivered...
Useful information provided in #6865, not included in this issue's description: > hls.js 1.5.17 > Safari 17.5 (19618.2.12.11.6) > mac OS 14.5 (23F79) SONOMA > > MediaPackage AWS service, and...
I have some testing experience with AWS MediaPackage SPEKE v2 media (DRM Today / Castlabs). The setup that works is as follows. Note that you need to include a 'x-dt-custom-data'...
- Related to discussion #6214
You can instantiate as many instances of hls.js as you want, but you are responsible for performance. Parsing errors are a result of content issues, but stalling and network errors...
I recommend unchecking "Auto-recover media-errors" before capturing logs, so that we only get the logs up to the point of failure. Looks like an issue with decoding sn 13, but...
@symit-dev are you still able to reproduce this issue in hls.js v1.5.17 or v1.6.0-beta.1?