CPIX Best Practices
Request current and next keys
Packagers should request current and next keys. Packages should use a rolling window for key information, with the current information in the manifest and then switching over to the next and next+1 keys at a point in the future. By requesting two keys, clients can request the keys before use. Multiple keys are signaled within the Widevine or Playready PRO 4.2.0.0 (or above) Protection System Specific Header. If Playready PRO 4.1.0.0 or 4.0.0.0 is used, each requested key has a unique Protection System Specific Header.
Content Protection Data
The CPIX service returns the element ContentProtectionData which should be used to populate the ContentProtection element within the DASH manifest. Verimatrix may include additional information within the block to assist the player.
Key ID may be changed
Per DASH-IF CPIX specification Verimatrix CPIX service may update the Key ID. The packager must respect this change and signal the returned key ID within the manifest.
Updated over 1 year ago