pckg_mpd_profiles

The 'pckg_mpd_profiles' directive is used to specify MPD profiles for segment-based media streaming in Kaltura.

Syntaxpckg_mpd_profiles profile_name;
Defaultnone
Contexthttp, server, location
Arguments1

Description

The 'pckg_mpd_profiles' directive allows you to define specific MPD (Media Presentation Description) profiles within the Kaltura Media Framework, facilitating optimized streaming for adaptive bitrate delivery. When this directive is set, it instructs NGINX to utilize the specified profiles for generating the MPDs that are essential for serving media segments following protocols like HLS or DASH effectively.

In practice, you can configure this directive to inform the backend components which profiles to use during the packaging and streaming of media. This can help control aspects such as video and audio encoding settings or the selection of appropriate variants for different playback scenarios. When retrieving or serving media, the Kaltura controller and media components will refer to these profiles to ensure that the delivery is aligned with the defined characteristics for your streaming setup. Thus, the 'pckg_mpd_profiles' plays a crucial role in ensuring that media is served in a way that optimizes player compatibility and streaming performance across varying network conditions.

The directive can be used in 'http', 'server', and 'location' contexts, making it flexible for different levels of configuration within NGINX. However, users must be cautious when defining these profiles, ensuring they are correctly named and correspond to the actual profiles available in their Kaltura implementation to prevent delivery issues.

Config Example

server {
    listen 80;
    server_name example.com;

    location /stream {
        pckg_mpd_profiles main_profile;
        # other configurations...
    }
}

Ensure that the profile names are valid and match those defined in the Kaltura system.

Incorrect or undefined profiles can lead to media delivery errors or mismanaged streaming attributes.

This directive is context-specific; using it outside the defined contexts (http, server, location) may cause configuration errors.

← Back to all directives