-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Improve EME Controller: Add PlayReady support #1918
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
Closed
Closed
Changes from all commits
Commits
Show all changes
25 commits
Select commit
Hold shift + click to select a range
4fb5fdb
add support for pssh in manifest
ssreed b1e50f8
move util function into it's own file
ssreed 3b423f5
add docs, clean up names
ssreed 5d2a4ac
add unit tests
ssreed fef1409
add support for multi-drm manifests
ssreed 6713568
add docs
ssreed 294d8af
add playready support
ssreed 8236809
clean up
ssreed d77f6d0
move playready header logic to separate function
ssreed d04049e
update playready challenge logic
ssreed 685e6df
fix: use for loop instead of forEach
ssreed 7c670cc
move playready header logic to separate file
ssreed 0401518
fix typo
ssreed 00025d1
don't initialize emeController if eme isn't enabled
ssreed 09d9660
simplify playready headers
ssreed a9d9e8f
clarify and update function name to more accurately reflect returned …
ssreed 1c9021f
Merge branch 'master' of https://github.com/video-dev/hls.js into add…
ssreed 56a357f
optimize and improve readability of capturing initData
ssreed ca9bcc3
fix unit test
ssreed 49e22ca
remove unnecessary code
ssreed 897257d
add documentation, add initDataTypes enum
ssreed 177b1e7
fix functional test
ssreed 61494eb
add key rotation support
32215cc
Merge branch 'master' into add-playready
ssreed e840bfb
fix unit test
ssreed File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i m not sure we need that, or we need something different in terms of API.
at least you need to expose an enum on the API with the possible values, and/or document what values
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There could be a better way to do this but I was leaving it up to the consumer to figure out what type of DRM system is supported for a particular environment. So for example, if there was a manifest that is multi DRM, the client can choose their preferred system based on the browser/CDM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but as a common purpose project, our responsability is finding common denominator solutions with future proof APIs that will cover many possible use-cases.
For example what we should do is allow to configure a preference priority-list of DRM systems. Then, the key-systems are tried for existence on the platform in that order.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Btw such a config parameter is optional, isn'it? :) We can figure out inside our code if there is a DRM system that fits the ones in the media manifest.
So, what we really want in the end is to set a preferred system (or a prio list of), and the values in there would be the values of the key-system enum, right?