I'm using a custom origin

If you're using a custom origin ("Your Origin"), you can apply ultra low latency (ULL) to streamline delivery of your live content through AMD.

Player requests must include the "live-ull" element

Ensure that you include the appropriate live-ull element in a player request path to achieve ultra low latency. Optimizations are automatically applied to a playback URL if the request includes the appropriate media-format path element:

  • /hls/live-ull/*
  • /dash/live-ull/*
  • /cmaf/live-ull/*

Update your AMD property

Set up the appropriate rule and match criteria for requests that you want to apply ULL. In that rule, you need to set up these behaviors.

Task 1 Description
Configure the Origin Server behavior

Since you're using your own unique origin to deliver live content, you'd select Your Origin and configure the applicable options.

Configure the Segmented Media Delivery Mode behavior

Apply these settings in this behavior to support CTE:

  • Set Mode to Live.
  • Set Enable ULL Streaming to On.

See Segmented Media Delivery Mode and AMD for details on the remaining options.

Add the Segmented Media Streaming - Prefetch behavior

There isn't a standardized way to list a partial segment for an HLS stream. So, a partial segment "chunk" may not be listed correctly in the playlist, and MSL wouldn't be able to include it in the appropriate header for playback. To address this, you need to add the Segmented Media Streaming - Prefetch behavior, and set it to "On." You also need to configure your environment to support prefetching. See How to implement Prefetching for complete details.

With prefetching enabled, Akamai edge servers will request a new segment before the player receives the playlist. This will reduce the latency in fetching the segment.

Note: The Segmented Media Streaming - Prefetch behavior is required, regardless of the format of media you're live streaming—HLS or DASH.

Understand Property Manager rule logic

Segmented Media Delivery Mode is a required behavior that's automatically included in the Default Rule, and the Default Rule applies to all requests. If you add another rule to your AMD property and include the Segmented Media Delivery Mode in that rule, a request that meets its match criteria will use that rule's Segmented Media Delivery Mode settings. However, if you add another rule and do not include the Segmented Media Delivery Mode behavior in it, what you've set in the Default Rule for Segmented Media Delivery Mode is used.

Remember this logic when setting up the your AMD rule for ULL support.

1 These tasks only describe what you need to enable ULL support in an AMD property rule. See Define Property Configuration Settings for full information on rule configuration.