You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Hi, are there any developments regarding implementation of different DRM keys per resolution #1321
The text was updated successfully, but these errors were encountered: