Packaging
The Packaging function in MK.IO Beam prepares your live or file-based content for delivery across different devices and streaming platforms. It converts encoded outputs into adaptive bitrate (ABR) formats like HLS and DASH, ensuring smooth playback for viewers.
You can configure packaging profiles, segment settings, DRM options, and delivery targets directly in the MK.IO Beam interface. The system handles the underlying workflow for you, making it easy to control how your streams are delivered without managing the technical details.
High-level architecture
MediaKind Packaging main building blocks are given in the diagram below:
Definitions
Catalog: The catalog is the link between the outputs and the assets. It must be created first to host the outputs and be filled with assets. All assets added to the catalog can be delivered by any outputs from the catalog.
Output: An output is a set of specific delivery parameters for a defined input stream. It contains the processing and encryption parameters. It is added to the catalog to serve the content to the users. It can deliver all the assets existing in the catalog.
Asset: An asset is either live or on-demand content.
Live Packaging service: Configuration of the live input parameters. Once associated with a catalog, the service will be available for delivery using the outputs existing in the catalog.
On-Demand Packaging service: Associated to the catalog, it allows visualization of the existing assets. All assets listed can be delivered using the outputs existing in the catalog.
Configuration steps
This diagram shows a typical configuration workflow:
- Create a catalog to host the outputs and add assets.
- Add an output to deliver the assets from the catalog repository.
- Create an On-Demand or Live Packaging service.
- Associate it to the catalog to deliver the assets.
The delivery is done from the origin server. The output and asset used depends on the user request.
The delivery URL is a concatenation of the output access URL and the asset access URL.