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

Is it possible to implement different DRM keys for different resolutions in MPEG-DASH? #1548

Open
Nixon197 opened this issue Oct 23, 2024 · 1 comment

Comments

@Nixon197
Copy link

Nixon197 commented Oct 23, 2024

Hi, are there any developments regarding implementation of different DRM keys per resolution #1321

@erankor
Copy link
Contributor

erankor commented Nov 9, 2024

Nope :) that last comment in the issue you mentioned still applies.
Don't know if using multiple keys on a single set works well now across all different devices, it's been a long time since we tried it... But I don't think it's really needed, you can implement the solution so that there are 2 adaptive sets for each video - one with the higher resolution renditions that uses key X, and another with the lower resolutions only that uses key Y. In other words - the player always sees a single key, but the users who player the lower resolution stream won't get the key used in the playback of the higher resolutions.
What I probably would change however, if I had the time, is to make it easier to implement different keys for video / audio. The audio & video often use different decoding paths, and sharing the key between them is not recommended. Currently, using different keys for audio/video requires separating them to different sequences in the JSON, which can be cumbersome.
I implemented something like that in our live packager -
https://github.com/kaltura/media-framework/tree/master/nginx-pckg-module#pckg_enc_scope

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants