Prepare content source: source stream requirements
Overview
The Serverside.ai service adheres to industry standards to ensure optimal streaming performance. This document outlines the required specifications for source streams and content creation.
VoD and live manifest requirements
The VoD or live manifest must meet the following requirements:
- The manifest (.m3u8 for HLS or .mpd for MPEG-DASH) must be publicly accessible via the origin (PULL method).
- The origin endpoint mustn't require authentication.
- The origin must deliver the manifest, submanifests, and segments over HTTPS.
- Source segments (HLS and DASH) can be hosted on your own infrastructure and enabled for CDN delivery (for instance, via Akamai).
- The SSAI service requests only the manifest file, while the player requests the segments from the origin.
Packager and origin requirements
Configure your packager or origin server to produce manifests for HLS or DASH that are compatible with the specific requirements:
- Codec and profile (such as, resolution, profile, fps, bitrate) should be consistent for each piece of content in a given channel (live) or playlist (VoD).
- The GOP size (also known as the keyframe interval or keyframe rate) must be 1.92 seconds (for 25 fps and 48 kHz audio) to ensure compatibility and alignment of audio and video segments.
- For live streams, the ad marker must be present as an SCTE-35 inline marker, retaining the cue-out information and the duration of the break.
- Ensure that the source origin or server sets the HTTP Access-Control headers as shown:
- Access-Control-Allow-Origin: *
- Access-Control-Allow-Credentials: *
- Access-Control-Allow-Methods: *