-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
better support multi-DRM with one ContentProtection element #71
Comments
This could even be needed without app-specific extensions to ContentProtection. For example: <ContentProtection schemeIdUri="urn:mpeg: dash:mp4protection:2011" value="cenc"/> For some apps, this should be enough to supply a list of DrmSchemeInfos with license server endpoints for all the various DRM schemes that content provider uses. |
Add new ContentProtection interpretation API that allows applications to return multiple DRM configurations for each ContentProtection element and to parse raw ContentProtection XML elements. This patch deprecates DrmSchemeInfo in favor of DrmInfo. Furthermore, DrmSchemeInfo will be removed post v1.5.0. * Replace DrmSchemeInfo with DrmInfo. * Move Restrictions class definition into its own file. * Populate initData values from explicit PSSHs without application intervention. * Allow explicit PSSHs to differ between Representations Issue #71 Issue #137 Closes b/23428584 Change-Id: Ib8d6ba630b930ee64f923a3f4a3e518abacccf88
This was broken during the DrmInfo refactor. Issue #71 Change-Id: I5fb02cfa1723cf7bceaa5f84ba0d7d3ef51f2bdf
Could not find shaka.player.DrmInfo class on version 1.5.0 as stated in https://shaka-player-demo.appspot.com/docs/shaka.player.DashVideoSource.html#ContentProtectionCallback Maybe, this file is not up to date I think that, this line of code should be inserted: |
The library does not export return [{
'keySystem': 'com.widevine.alpha',
'licenseServerUrl': LICENSE_SERVER_URL,
'withCredentials': true
}]; |
Thank you, It's is working now. |
Currently, shaka.player.DashVideoSource.ContentProtectionCallback only allows the creation of one DrmSchemeInfo object per ContentProtection element. So although it is possible for a provider to support multiple DRM schemes, the must then use multiple ContentProtection elements as well.
Since ContentProtection can make use of application-specific extensions, there is no reason one ContentProtection element cannot describe, in an app-specific way, multiple DRM schemes. A future refactor of ContentProtection interpretation should take this into account and provide a natural API for generating multiple DrmSchemeInfos.
The text was updated successfully, but these errors were encountered: