Skip to content
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

HDCP-LEVEL capping and EME error handling #4923

Closed
3 tasks done
robwalch opened this issue Sep 23, 2022 · 0 comments · Fixed by #5150
Closed
3 tasks done

HDCP-LEVEL capping and EME error handling #4923

robwalch opened this issue Sep 23, 2022 · 0 comments · Fixed by #5150

Comments

@robwalch
Copy link
Collaborator

robwalch commented Sep 23, 2022

Is your feature request related to a problem? Please describe.

Filter levels based HDCP level attribute when using EME keys.

Describe the solution you'd like

  • Support a maxHdcpLevel setting that caps level selection to variants with an equal or lower HDCP-LEVEL attribute value of:
    • 'NONE' (lowest)
    • 'TYPE-0'
    • 'TYPE-1'
    • 'TYPE-2' (highest)
      Setting maxHdcpLevel would filter out levels that do not specify HDCP-LEVEL.
  • Selected levels where key status changes to 'output-restricted' should be removed and result in a level switch.
  • Moved HDCP-LEVEL filtering with HDCP Policy Check #5149 When available, use MediaKeys.getStatusForPolicy (https://wicg.github.io/hdcp-detection/) to filter levels prior to requesting a license.

Additional context

See HDCP-LEVEL under https://datatracker.ietf.org/doc/html/draft-pantos-hls-rfc8216bis#section-4.4.6.2

@robwalch robwalch added this to the 1.3.0 milestone Sep 23, 2022
@robwalch robwalch changed the title HDCP variant filtering and EME error handling HDCP-LEVEL variant filtering and EME error handling Sep 27, 2022
@robwalch robwalch changed the title HDCP-LEVEL variant filtering and EME error handling HDCP-LEVEL capping and EME error handling Jan 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

1 participant