Dynamic Delivery: Change to Sources Returned

Product(s)
Video Cloud
Role(s)
Player Developer
API Developer
Device SDK Developer

This topic explains a small change in the sources returned for Dynamic Delivery videos.

Notice: change to sources

During March, 2019, Brightcove is updating the infrastructure for Dynamic Delivery to make a small change in the sources that are returned by the CMS/Playback APIs, and therefore delivered to the Brightcove Player and native SDK players.

For the great majority of Video Cloud users, this change is completely transparent. There is nothing you need to do. For a few customers who have built integrations relying on the exact structure of the existing sources, these integrations will need to change.

What is changing?

Currently Dynamic Delivery returns 2 flavours (v4 and v5) of HLS when Playback API requests come in. In some special cases, usually delivery to a specific device, accounts are also enabled for v3 delivery.

For each of those, we also return the following DRM types:

  • V3: Clear / AES-128 (if your account is enabled for v3)
  • V4: Clear / AES-128
  • V5: Clear / AES-128 / Fairplay

The only reason we deliver HLSv5 is that it supports Fairplay - for Clear and AES-128, the video and manifests we return are identical.

Because the URLs for them are different however (they contain "v4" or "v5"), we are doubling the amount of content that we need to deliver and cache, which is wasteful and impacts the performance of both Dynamic Delivery and SSAI.

Therefore, we are changing the infrastructure so that only the Fairplay manifest is returned for v5, so that the sources set will now look like this:

  • V3: Clear / AES-128 (if your account is enabled for v3)
  • V4: Clear / AES-128
  • V5: Fairplay

Would this impact my players?

  1. If you do not use Clear DRM or AES-128 encryption, this change makes no difference
  2. If you do use Clear DRM or AES-128 encryption, but let the player select the source automatically, this change makes no difference (the player will select the v4 source)
  3. If you do use Clear DRM or AES-128 encryption, and have written custom code to force the player to use the v5 source URLs, this change result in the player not having a playable source - the solution is to allow the player to auto-select the source, or to modify you code to select the v4 source instead.