Packager settings fields - AWS Elemental MediaPackage

Packager settings fields

  1. For Packaging type, choose DASH-ISO.

  2. (Optional) For Segment duration, enter the duration (in seconds) of each segment. Enter a value equal to, or a multiple of, the input segment duration. If the value that you enter is different from the input segment duration, AWS Elemental MediaPackage rounds segments to the nearest multiple of the input segment duration.

    Important

    If you enable Number with duration in Segment template format, you can't change the segment duration after you've created the endpoint.

  3. (Optional) For Manifest window duration, enter the total duration (in seconds) of the manifest.

  4. (Optional) For Profile, choose a DASH profile that determines the segment and manifest formats of the output.

    • None – the output doesn't use a DASH profile.

    • Hbbtv 1.5 – the output is compliant with HbbTV v1.5. For information about HbbTV v1.5, see the HbbTV specification website.

    • Hybridcast – the output is compliant with Hybridcast. For more information about Hybridcast, see the IPTV Forum Japan Hybridcast specification. If you enable the Hybridcast profile on your packaging configuration, you can't use DASH Period triggers.

    • DVB-DASH 2014 – the output is compliant with DVB-DASH 2014. For more information about DVB-DASH 2014, see the DVB-DASH specification.

  5. (Optional) For Manifest layout, choose if you want MediaPackage to serve a full or compact manifest in response to playback requests.

    • If you choose Full, MediaPackage presents the SegmentTemplate and SegmentTimeline tags for every Representation in the manifest.

    • If you choose Compact, MediaPackage combines duplicate SegmentTemplate tags and presents them at the start of the manifest. This shortens the manifest and makes it easier for some devices to process it.

    For more information about the manifest layout options, see Compacted DASH manifests.

  6. (Optional) For Min update period, enter the minimum amount of time (in seconds) that the player should wait before requesting manifest updates. A lower value means that manifests are updated more frequently, but a lower value also contributes to request and response network traffic.

  7. (Optional) For Min buffer time, enter the minimum amount of time (in seconds) that a player must keep in the buffer. If network conditions interrupt playback, the player will have additional buffered content before playback fails, allowing for recovery time before the viewer's experience is affected.

  8. (Optional) For Suggested presentation delay, enter the amount of time (in seconds) that the player should be from the end of the manifest. This sets the content start point back x seconds from the end of the manifest (the point where content is live). For example, with a 35-second presentation delay, requests at 5:30 receive content from 5:29:25. When used with time delay, MediaPackage adds the suggested presentation delay to the time delay duration.

  9. (Optional) For Segment template format, choose how MediaPackage and playback requests refer to each segment.

    • If you choose Number with timeline, MediaPackage uses the $Number$ variable to refer to the segment in the media attribute of the SegmentTemplate tag. The value of the variable is the sequential number of the segment. SegmentTimeline is included in each segment template.

    • If you choose Number with duration, MediaPackage uses the $Number$ variable and replaces the SegmentTimeline objects with a duration attribute in the segment template.

      Note

      This option isn't supported in combination with multi-period DASH.

    • If you choose Time with timeline, MediaPackage uses the $Time$ variable to refer to the segment. The value of the variable is the timestamp of when on the manifest timeline the segment starts. SegmentTimeline is included in each segment template.

    For more information about the formatting options of the SegmentTemplate tag, see DASH manifest segment template format.

  10. (Optional) For UTC timing, select the method that the player uses to synchronize to coordinated universal time (UTC) wall clock time. This enables the player and MediaPackage to run on the same UTC wall clock time. This is a requirement, otherwise playback timing or synchronization issues can occur.

    The options are HTTP-HEAD, HTTP-ISO, HTTP-XSDATE, and NONE. This value will be set as the @schemeIdURI attribute for the UTCTiming element in the outbound Media Presentation Description. For information about UTCTiming, see DASH, UTC Timing Descriptor, 5.8.4.11.

  11. (Optional) For UTC timing URI, specify a URI to use for UTC synchronization. This is the URI used to fetch the timing data according to the scheme defined by UTC timing. This value is only valid if UTC timing is not NONE. This value will be set as the @value attribute for the UTCTiming element. For information about @value, see DASH, DASH UTC Timing Schemes, 5.8.5.7.

  12. (Optional) Select Include IFrame only stream to include an additional I-frame only stream along with the other tracks in the manifest. MediaPackage generates an I-frame only stream from the first rendition in the manifest. The service inserts an <EssentialProperty schemeIdUri="http://dashif.org/guidelines/trickmode" value="X"/> descriptor, where X is the ID of the original Adaptation set, and then generates and includes an I-frame only rendition in the stream. If you use encryption, MediaPackage encrypts the I-frame only rendition with the same content key as the original video rendition. This rendition enables player functionality like fast forward and rewind.

  13. For Period triggers, choose how MediaPackage creates media presentation description (MPD) periods in the DASH output manifest. Choose from the following:

    • None – MediaPackage doesn't create additional periods. It formats the manifest as a single period and doesn't include SCTE-35 markers in the segments.

    • Trigger new periods on ads – MediaPackage creates and inserts in the manifest multiple periods based on SCTE-35 ad markers from the input content. These periods separate portions of the content, such as setting boundaries between the main content and ad content. For more information about how MediaPackage configures periods in the manifest, see DASH manifest options in AWS Elemental MediaPackage.

      Important

      Multiple periods are required if you use AWS Elemental MediaTailor for personalized ad insertion in DASH content. For more information about this service, see the AWS Elemental MediaTailor User Guide.

SCTE-35 Options

The following fields dictate how MediaPackage processes SCTE-35 messages from the input stream. For more information, see SCTE-35 message options in AWS Elemental MediaPackage.

  1. (Optional) For Ad triggers, choose the SCTE-35 message types that you want to be treated as ad markers in the output. If you don't make a selection here, MediaPackage inserts ad markers in the output manifest based on these message types:

    • Splice insert

    • Provider advertisement

    • Distributor advertisement

    • Provider placement opportunity

    • Distributor placement opportunity

  2. (Optional) For Ads on delivery restrictions, choose what ad insertion action MediaPackage takes based on delivery restriction flags in the segmentation descriptors of SCTE-35 messages.

    • None – MediaPackage doesn't insert any ad markers in the output manifest.

    • Restricted – MediaPackage inserts ad markers when there are delivery restrictions in the SCTE-35 message types that you indicated in Customize ad triggers.

    • Unrestricted – MediaPackage inserts ad markers when there aren't delivery restrictions in the SCTE-35 message types that you indicated in Customize ad triggers.

    • Both – MediaPackage inserts ad markers whether or not there are delivery restrictions in the SCTE-35 message types that you indicated in Customize ad triggers.

    If you choose not to insert ad markers, MediaPackage also won't create periods. The output manifest is contained in a single period.