WP44 STREAMING MEDIA SPOTLIGHT SERIES APRIL/MAY 2018 SPONSORED CONTENT
WHAT CMAF DOES…AND DOESN’T DO
As stated at the top, one of the challenges of implementing
any new technology is how it fits in with existing technologies.
To examine that within the context of CMAF, let’s consider
Scenario 1 - You create a new mobile app targeting only
the latest iOS and Android phones. A single CMAF set of
files should be able to support all target endpoints. You see
this in Figure 6, where the encoder inputs a single file and
outputs a CMAF ABR set with MPD manifests for DASH and
M3U8 manifests for HLS. These are uploaded to the CDN
from which they can be delivered to devices and played as is.
Scenario 1. 5 - You start a subscription pay-per-view live
service, say for live music events. You monetize via advertising
support for newer devices and browsers only, or using an
Apple TV app. To support all the available endpoints, two
DRMs are deployed; Widevine and FairPlay. As shown in
Figure 7, a single CMAF set of files with HLS and DASH
manifests and CBC encryption can support the required
devices using FairPlay for HLS and Widevine for DASH.
Figure 6. A single set of CMAF formatted files can serve the latest iOS and Android devices.
Figure 7. A single set of CMAF file with dual manifests and two DRMS.