DASH
After completing your DASH ingest setup for MSL5, configure your encoder to capture and push your stream to the entry points.
DASH Publishing URL
The encoder publishes primary and backup streams for the DASH protocol according to the following URL syntax.
| Stream | Hostname | Path | Example |
|---|---|---|---|
| Primary | p-ep{stream_id}.i.mslentrypoint.net | {stream_id}/{event_name} | https://p-ep50002.i.mslentrypoint.net/50002/event1/manifest.mpd |
| Backup | b-ep{stream_id}.i.mslentrypoint.net | {stream_id}-b/{event_name} | https://b-ep50002.i.mslentrypoint.net/50002-b/event1/manifest.mpd |
The MSL5 system defines a stream as a combination of stream_id and event_name. All ingested content, such as variant playlists, bitrate playlists, and segments, should have a common event_name in the path.
In Backup URLs, note the -b in the path.
DASH Playback URL
To play DASH streams, construct the DASH according to this URL syntax.
The following URLs are used for playback. The {stream_id} and {event_name} placeholders correspond to the stream's configuration.
| Stream | Path | Example |
|---|---|---|
| Primary | dash/live/{stream_id}/{event_name}/{filename}.mpd | https://<cdn_hostname>/dash/live/50002/event_1/index.mpd |
| Backup | dash/live/{stream_id}-b/{event_name}/{filename}.mpd | https://<cdn_hostname>/dash/live/50002-b/event_1/index.mpd |
In Backup URLs, note the -b in the path.
Low latency for DASH streams
When using DASH as the protocol for a live stream in MSL5, you can enable low latency for an aggregating response that helps to reduce latency and decrease overall transfer time of live streams.
To use low latency for DASH, you need to distribute your MSL5 streams using the Adaptive Media Delivery (AMD) product. AMD requires that you create a property configuration using Property Manager, and apply specific behaviors that determine how to deliver your streams. Refer to Go Live in AMD with MSL5 origin for detailed instructions.
Ensure that you include the /dash/live-ull/* element in the request path to enable low latency for the stream playback. Optimizations are automatically applied to a playback URL if the request includes the appropriate media-format path element.
Updated 20 days ago
