How manifests work - AWS Elemental MediaLive

How manifests work

The following sections describe how manifest paths work.

How manifest paths work by default

The manifests that MediaLive creates include information about the paths to other files, specifically:

  • The content inside the main manifest includes a path to each child manifest.

    By default, the syntax of this path is the following:

    base_filename name_modifier extension

    For example:

    curling_high.m3u8

    The path is relative to the location of the main manifest.

  • The content inside each child manifest includes a path to its media files.

    By default, the syntax of this path is the following:

    base_filename name_modifier optional_segment_modifier counter extension

    For example:

    curling_high_000001.ts

    The path is relative to the location of the child manifest.

How custom paths work

If the default paths inside the manifests are not suitable for the way that the downstream system handles the three sets of files, you can complete the base URL fields:

  • Complete the Base URL manifest fields so that MediaLive constructs custom paths to the child manifests.

  • Complete the Base URL content fields so that MediaLive constructs custom paths to the media files.

When you customize the paths, the syntax changes.

  • When you complete the Base URL manifest fields, the syntax for the child manifest path (inside the main manifest) is the following:

    base_url_manifest base_filename name_modifier extension

    For example:

    http://viewing/sports/curling_high.m3u8
  • When you complete the Base URL content fields, the syntax for the media file paths (inside the child manifests) is the following:

    base_url_content base_filename name_modifier optional_segment_modifier counter extension

    For example:

    http://viewing/media/sports/curling_high_000001.ts