vod_drm_clear_lead_segment_count

The `vod_drm_clear_lead_segment_count` directive controls the number of initial video segments in a video on demand (VOD) stream that remain unencrypted for Digital Rights Management (DRM) purposes.

Syntaxvod_drm_clear_lead_segment_count number;
Defaultnone
Contexthttp, server, location
Arguments1

Description

The vod_drm_clear_lead_segment_count directive specifies how many leading segments in a video stream should be transmitted in an unencrypted format, which is particularly important in scenarios where DRM is applied to video content. This directive is useful when content providers want to ensure that the initial part of the video is available without encryption to allow for faster playback start times. By default, subsequent segments are encrypted for protection purposes, while the leading segments can be served without any restriction.

When this directive is set, its parameter defines the count of unprotected segments delivered to the player before switching to the secured and encrypted streams. This can significantly improve the user experience, as it allows buffers to fill more quickly while still adhering to content protection policies. When using this functionality, it's important to ensure compliance with the content protection policies applicable to the media being served.

The directive can be placed in the http, server, or location context, making it flexible and applicable to various configurations within the NGINX server setup, depending on the level of granularity needed. Adjusting this value can optimize loading times and user experience while keeping compliance with DRM regulations.

Config Example

location /videos {
    vod_drm_clear_lead_segment_count 2;
}

Ensure that the number specified is appropriate for your content and DRM requirements, as setting it too high may lead to potential content protection issues.

Misconfiguring this directive could either lead to playback issues or expose content that should be encrypted.

← Back to all directives