About the path for output destinations - AWS Elemental MediaLive

About the path for output destinations

HLS outputs consist of three sets of files: the main manifest, the child manifests, and the media files (segments).

MediaLive sends all these sets of files to the same destination (protocol, domain, path). The file names are different for each.

The syntax for the URLs of HLS files

The full URLs have the following syntax.

The syntax for the URL for main manifest files

The syntax is the following:

protocol domain path base_filename extension

For example, the URL for the master manifest for the curling output might be:

http:// 203.0.113.55/sports/delivery/curling.m3u8

The syntax for the URL for child manifest files

The syntax is the following:

protocol domain path base_filename modifer extension

For example, the URL for the child manifest for the high-resolution renditions of the curling output might be:

http://203.0.113.55/sports/delivery/curling_high.m3u8

The syntax for the URL for the media files (segments)

The syntax is the following:

protocol domain path base_filename modifer optional_segment_modifier counter extension

For example, the URL for the file for the 230th segment might be:

http:// 203.0.113.55/sports/delivery/curling_high_00230.ts

Note that the URLs for all the files are identical to each other, up to and including the base_filename.

How MediaLive constructs these URLs

These URLs are constructed as follows:

  • You specify the protocol, domain, path, base_filename, modifier, and segment_modifier.

  • MediaLive inserts the underscore before the counter.

  • MediaLive generates the counter, which is always six digits starting at 000002.

  • MediaLive inserts the dot before the extension.

  • MediaLive selects the extension:

    • For manifest files – always .m3u8

    • For media files – .ts for files in a transport stream, and .mp4 for files in an fMP4 container