Why CMAF Ingest Matters for Modern Live Streaming
Summary
- Interoperability is important for live streaming workflows, which combine products from different vendors and across multiple networks and locations.
- CMAF is a standardised media container format based on fragmented MP4 (fMP4), designed to enable compatible media segments to be used with both Apple HTTP Live Streaming (HLS) and MPEG-DASH.
- CMAF ingest enables downstream processing or packaging systems to receive live media as CMAF fragments.
- CMAF ingest can improve compatibility between supported components from different vendors, and support workflows that combine on-premises and Cloud-based infrastructure.
- This gives media organisations greater flexibility when designing their infrastructure and can make it easier to scale workflows and adapt them to changing requirements.
- The EasyTools Video Processing solution supports the features required for CMAF ingest.
In live streaming workflows, reliable interoperability is essential for two reasons.
The first is that many workflows contain best-of-breed products from different vendors. It’s important to ensure they can all talk with each other reliably and consistently.
The second is that workflows are becoming increasingly distributed. Different packagers and processing tools are often located in different infrastructures – some packagers might be on-premises while other packagers and processing tools are in the Cloud. On top of being able to communicate with each other, these tools need to do so across different networks.
Traditionally, broadcast and IPTV workflows have often delivered MPEG Transport Streams to downstream processing systems over UDP, often using IP multicast on managed networks. While this enables low-latency distribution to multiple receivers, it has one big drawback: it usually relies heavily on the capabilities of the underlying infrastructure.
CMAF ingest changes that.
What is CMAF?
CMAF stands for “Common Media Application Format.” It is a standardised media container format based on fragmented MP4 (fMP4). CMAF is designed to allow compatible audio and video segments to be used with both of the widely deployed adaptive streaming formats: Apple’s HTTP Live Streaming (HLS) and MPEG -DASH.
Historically, a service might create one set of segments for HLS and another for DASH. With compatible CMAF packaging, the same encoded audio and video segments can often be used for delivery with both formats, reducing duplication in the packaging and storage workflow.
CMAF is not a codec or a network transport protocol. It defines the structure of the media fragments, while HLS and DASH define how those fragments are described and delivered to playback clients.
What is CMAF ingest?
CMAF ingest simply means that a downstream processing or packaging system receives live media as CMAF fragments, typically using fragmented MP4 over an HTTP/TCP-based connection. An encoder can produce the CMAF media directly. Alternatively, an upstream packager or processing system can receive a contribution stream in another format, such as MPEG Transport Stream (MPEG-TS) over UDP, and convert it into CMAF fragments.
Greater Freedom with Interoperable CMAF Ingest
While CMAF ingest might not be the best solution for every connection in every workflow, it provides a practical, standards-based exchange between packaging and processing systems. Let’s take a look at some of the benefits it brings:
Freedom to Combine Components: CMAF ingest can provide a common exchange method between supported packagers and downstream processing systems. This can reduce dependence on proprietary connections between products from a single vendor, making it easier to combine packaging, DRM, and CDN-delivery components from different vendors.
Freedom of Location: Because CMAF ingest commonly uses HTTP and TCP, it is particularly well suited to workflows that combine on-premises equipment with cloud-based services. It does not require the communicating devices to be located on the same local network or within the same infrastructure.
Freedom to Evolve: A standards-based ingest interface can make it easier to introduce new processing or packaging components over time. In other words, it becomes easier not only to scale, but also to adapt the infrastructure as requirements change. For example, one can:
- introduce new cloud-based processing components while re-using existing infrastructure
- move packaging capacity closer to a target audience
- integrate third-party cloud services without redesigning the entire workflow.
Support for Multiple OTT Outputs: CMAF ingest can provide a consistent media input for downstream packaging and distribution. A packager can use the incoming CMAF media to create the HLS and DASH outputs required by different distribution services.
How EasyTools Supports CMAF Ingest
The EasyTools Video Processing solution, which includes packagers, supports the features required to integrate CMAF ingest into modern live streaming workflows. In this solution, packagers support CMAF ingest as an output from the packaging workflow. They can also perform additional functions, such as DRM management or CDN-specific packaging.
This gives media organisations more freedom in how they assemble their workflows, with the flexibility to combine on-premises equipment, Cloud services, and products from different vendors.
By combining CMAF ingest with cloud-ready deployment models and support for multiple distribution platforms, EasyTools helps broadcasters and streaming service providers connect the components they already use while preparing for future changes.
Learn more about the EasyTools solutions.
FAQ
What is CMAF?
CMAF stands for Common Media Application Format. It is a standardised media container format based on fragmented MP4 (fMP4). CMAF enables compatible media segments to be used with both Apple HTTP Live Streaming (HLS) and MPEG-DASH.
What is CMAF ingest?
CMAF ingest enables upstream systems to send CMAF media fragments to a downstream packager.
Is CMAF a streaming or transport protocol?
No. CMAF is a media container format, not a codec or network transport protocol.
Can CMAF work with both HLS and MPEG-DASH?
Yes. Packagers can use compatible CMAF media segments to create both HLS and MPEG-DASH outputs. This reduces the need to generate separate media segments for each streaming format.
What are the benefits of CMAF ingest?
CMAF ingest can improve interoperability between supported video-infrastructure tools. It can also enable workflows that combine equipment and services from different vendors, networks, and locations.
Can CMAF ingest replace MPEG-TS over UDP?
CMAF ingest can provide an alternative to some MPEG-TS over UDP workflows, particularly when exchanging media across conventional IP networks, cloud environments, or firewalled connections.
Is CMAF ingest suitable for hybrid workflows?
Yes. Because CMAF ingest is commonly based on HTTP and TCP, it can be well suited to workflows that connect on-premises systems with cloud-based packagers and processing services.
Does CMAF ingest support multiple OTT platforms?
CMAF ingest can provide a consistent media input for a packager producing multiple OTT outputs – both HLS and MPEG-DASH.
Does EasyTools support CMAF ingest?
Yes. The EasyTools Video Processing solution supports the features required to integrate CMAF ingest into modern live streaming workflows.


