Known issues with Media Encryption

There are some known issues that currently limit the use of Media Encryption (ME) in some scenarios.

Issue Description
HLS byte-range playlists cannot be used with Media Encryption

When Media Encryption is enabled for an HLS stream with byte-range MPEG-TS segments, incorrect byte ranges can be reported in the playlist file. So, when a player transitions from one bit rate to another, it can fail to append the new segment to the previous one in its playback buffer.

Some symptoms of this issue include the following:

  • Playback on an hls.js-based player fails. This occurs when the master playlist file is used for the playback of Media Encryption-protected content.
  • Playback fails on ExoPlayer. Similar to the above, playback will fail if the player requesting content was built using ExoPlayer.
  • Audio and video are out of sync. The audio can be ahead of the video after a certain amount of playback, and can progressively get worse.
Existing stream-level encryption not supported If content served by your AMD property is already encrypted using stream-level encryption (such as data encrypted via a DRM system implemented in your Media Origin), it is denied for processing, because it is already encrypted. In addition, the pass-through of pre-encrypted content is not supported. Attempts to do so are met with an error when the content is recognized as encrypted.