-
Notifications
You must be signed in to change notification settings - Fork 133
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[Proposal] DRM: add
failOnEncryptedAfterClear
keySystems option
An application reported to us an issue where they couldn't play a content of mixed clear and encrypted contents on PlayReady devices. After a LOT of attempts at work-arounds, some of them described [here](#1403), we didn't succeed to actually find a good solution that would both allow smooth transition between Periods and a mix of encrypted unencrypted content. So I attempted to play the same content with other players: - dash.js didn't had a smooth transition between Periods here, it first loaded and played the clear content, then once finished loaded and played the encrypted content with a black screen and license request in-between. - The shaka-player failed to play the content, I tried to debug it but I did not succeed to make it play the content. This is very probably an issue with PlayReady, yet they historically haven't been quick to fix issues we reported, so we may have to provide a perhaps-temporary solution here. That's why I'm introducing the for-now undocumented (and experimental feature?) `keySystems[].failOnEncryptedAfterClear` `loadVideo` option. When set to `true`, we'll reload if an encrypted Period is encountered after a clear Period has been played. The logic for now is not perfect with very rare risks of false negatives. NOTE: I also profited from this commit to add the `canFilterProtectionData` option to the streams. Previously it was implicitly enabled when the `drmSystemId` was defined.
- Loading branch information
1 parent
c7c2c60
commit 4dc8296
Showing
14 changed files
with
426 additions
and
176 deletions.
There are no files selected for viewing
This file contains 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 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 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 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 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 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.