Requirements for players are the same as the requirements to support the HLS (RFC 8216) and MPEG-DASH standards. For a more comprehensive documentation, DASH-IF Implementation Guidelines are also available.
broadpeak.io only interacts with manifests and will specifically introduce changes in the stream when inserting new or different content.
Regardless of the input provided to broadpeak.io, if supported, the platform generates a multi-period manifest when contextualization occurs. This means that the player must be able to understand multiple time periods in a single manifest. You can find more information here.
According to the HLS specification document, the
EXT-X-DISCONTINUITY tag is being used to announce a change in the stream to the player, such as:
- encoding parameters
- encoding sequence
When contextualization occurs on broadpeak.io, the system introduces
EXT-X-DISCONTINUITY tags in media manifests to notify the player that a change in the stream is happening.
The context management mechanism of broadpeak.io introduces an HTTP redirect (307) that allows the system to introduce specific query parameters that identify the session. See Understanding broadpeak.io behavior for more information.
What does it mean?
The HTTP redirect is forwarded to the client, which needs to correctly interpret and query the path found in the
location header of the response. The location value is a path without FQDN, so the player needs to reuse the existing FQDN. This is pretty standard and most players support it natively. Contact us at [email protected] if you have any problem.
broadpeak.io only works with a relative path (in input and output), so the generated manifest contains the relative path to the resources. It is assumed that media can be routed based on path differentiation at the CDN level. For more information about CDN configuration, see the Using broadpeak.io with a CDN section.
Updated about 2 months ago