# SCTE-35 message options in AWS Elemental MediaPackage SCTE-35 messages This section describes the options that AWS Elemental MediaPackage offers for configuring how SCTE-35 messages are handled in live TS and CMAF outputs. SCTE-35 messages accompany video in your source content. These messages signal where MediaPackage should insert ad markers when it packages the content for output. By default, MediaPackage inserts markers for the following message types in the source content: + Splice insert + Break + Provider advertisement + Distributor advertisement + Provider placement opportunity + Distributor placement opportunity + Provider overlay placement opportunity + Distributor overlay placement opportunity + Program When these commands are present, MediaPackage inserts corresponding ad markers in the output manifests: + For daterange in HLS manifests on TS and CMAF origin endpoints, MediaPackage inserts `EXT-X-DATERANGE` tags. + For SCTE-35 enhanced on TS and CMAF origin endpoints, MediaPackage inserts `EXT-X-CUE-OUT`, `EXT-X-CUE-IN`, and related CUE tags. + For DASH manifests on CMAF origin endpoints, MediaPackage inserts `EventStream` tags to create multiple periods, when you have multi-period manifests enabled. The following sections describe how you can modify MediaPackage SCTE-35 message handling behavior. **Topics** + [How it works](scte-works.md) + [SCTE-35 settings](scte-settings.md) + [HLS EXT-X-DATERANGE ad markers](ext-x-daterange-ad-marker.md) + [HLS CUE tag ad markers](ext-x-cue-ad-marker.md) + [DASH ad markers](dash-ad-markers.md) # How SCTE-35 messages work in AWS Elemental MediaPackage works How it works The **Ad markers** and **SCTE filtering** settings work together to determine what MediaPackage does with SCTE-35 messages from the source content. When there are SCTE-35 messages in the source content, MediaPackage takes the following actions based on the value that you selected in **Ad markers**: + For **Daterange**, MediaPackage inserts `EXT-X-DATERANGE` tags to signal ads and program transition events in HLS output manifests. + For **SCTE-35 enhanced**, MediaPackage inserts `EXT-X-CUE-OUT`, `EXT-X-CUE-IN`, and related CUE tags to signal ads and program transition events in HLS output manifests. + For **XML** or **Binary**, MediaPackage inserts EventStream elements in the DASH manifests, with the selected signaling type, and create new periods when detecting markers defined as Ad markers. **Important note on SCTE-35 data tracks** MediaPackage also signals SCTE-35 markers present in the source that are not ad markers. MediaPackage selects the first available data track from the input content for SCTE-35 signal processing (typically identified as PID 500). For proper handling by MediaPackage, ensure that your SCTE-35 ad signals are included in this first data track. For DASH manifests, SCTE-35 markers that aren't ad markers don't create a new period. Instead, MediaPackage places these markers in the period that corresponds to the marker timing. # SCTE-35 settings in MediaPackage SCTE-35 settings You can modify how MediaPackage interacts with SCTE-35 messages from your source content. Configure the following settings on your origin endpoints. For more information, see the following: + For the MediaPackage console, see [Creating an origin endpoint in AWS Elemental MediaPackage](endpoints-create.md). + For the MediaPackage API, see [CreateOriginEndpoint](https://docs.aws.amazon.com/mediapackage/latest/apireference/origin_endpoints.html#origin_endpointspost) in the *AWS Elemental MediaPackage Live API Reference*. **Important** To modify how MediaPackage handles SCTE-35 messages, you should be familiar with the SCTE-35 standard. You can view the most recent standards here: [SCTE Standards Catalog](https://www.scte.org/standards/library/catalog/). You should also be familiar with how SCTE-35 is implemented in your source content. The SCTE configuration is achieved through settings available both at the segment level and at the manifest level. ****Enable SCTE support**** This setting is available on TS and CMAF origin endpoints, in the Segment settings parameters group. When enabled, it allows to define the SCTE configuration options in both the Segment settings and Manifest definitions parameters groups. ****SCTE filtering**** This setting is available on TS and CMAF origin endpoints. **SCTE filtering** specifies which SCTE-35 message types MediaPackage uses to create new periods in the output manifest. All SCTE-35 markers are preserved and passed through to the endpoint manifest, but only the markers that match your specified filter will trigger period boundaries. If you don't change this setting, MediaPackage treats these message types as ads: + Splice insert + Break + Provider advertisement + Distributor advertisement + Provider placement opportunity + Distributor placement opportunity + Provider overlay placement opportunity + Distributor overlay placement opportunity + Program ****Ad markers**** This setting is available for both HLS and DASH manifests, in the SCTE configuration section of the Manifest definitions parameters group. **Ad markers** allows you to specify what MediaPackage does when it detects SCTE-35 messages. These are the options for HLS manifests: + **Daterange** - inserts `EXT-X-DATERANGE` tags with SCTE-35 data + **SCTE-35 enhanced** - inserts `EXT-X-CUE-OUT`, `EXT-X-CUE-IN`, and related CUE tags For DASH manifests on CMAF endpoints, these are the options: + **XML** - inserts EventStream elements with the `urn:scte:scte35:2013:xml` scheme + **Binary** - inserts EventStream elements with the `urn:scte:scte35:2014:xml+bin` scheme ****SCTE in segments**** Choose whether to include SCTE-35 messages in the segment files of MediaPackage outputs. This setting works independently of the **SCTE filtering** and **Ad markers** settings. Choose from the following options: + **None** – SCTE-35 messages are not included in segment output. This is the default setting. + **All** – All SCTE-35 messages are embedded in the segment data, allowing downstream players and ad insertion systems to access the messages directly from segments without parsing manifest files. When you enable SCTE in segments: + For TS segments, SCTE-35 messages are embedded directly in the transport stream. + For CMAF segments, SCTE-35 messages are embedded in the segment data. + For DASH manifests, MediaPackage adds an `InbandEventStream` element with `schemeIdUri="urn:scte:scte35:2013:bin"` to signal the presence of SCTE-35 messages in the segment data. Your downstream components or players must be implemented to consume SCTE-35 messages from segments to take advantage of this feature. If your players cannot handle SCTE-35 messages in segments, playback may fail when this setting is enabled. # HLS EXT-X-DATERANGE ad markers in AWS Elemental MediaPackage HLS EXT-X-DATERANGE ad markers Daterange ad markers are used to signal ads and program transitions in live HLS manifests. When you enable daterange ad markers on your origin endpoint, MediaPackage inserts `EXT-X-DATERANGE` tags into the manifest where there are SCTE-35 `time_signal` or `splice_insert` tags present. `EXT-X-DATERANGE` is used in concert with `EXT-X-PROGRAM-DATE-TIME` tags. For information about the `EXT-X-DATERANGE` and `EXT-X-PROGRAM-DATE-TIME` tags for HLS, see the [HTTP Live Streaming 2nd Edition Specification](https://tools.ietf.org/html/draft-pantos-hls-rfc8216bis-07#section-4.4.5.1). The following table describes how to enable daterange ad markers in MediaPackage. ------ #### [ Console ] To enable daterange ad markers when creating or editing an origin endpoint, in the MediaPackage console, under the HLS or LL-HLS manifest settings, **SCTE configuration**, **Ad markers**, choose **Daterange**. If you choose daterange, you *must* also enter a **Program date/time interval (sec.)** value of 1 or greater. The program date/time interval is set in the same manifest fields as the ad marker settings. ------ #### [ AWS CLI ] To enable daterange ad markers for your origin endpoint, run the following command in the AWS CLI replacing *region* with your own information: ``` aws --endpoint=https://mediapackagev2.region.amazonaws.com mediapackage --region region create-origin-endpoint --channel-id test_channel --id hlsmuxed --hls-package "{\"ProgramDateTimeIntervalSeconds\":60,\"AdMarkers\":\"DATERANGE\"}" ``` **Important** You must set a `ProgramDateTimeIntervalSeconds` value that's greater than 0 (zero). ------ #### [ API and SDK ] To learn how to enable daterange ad markers for TS and CMAF origin endpoints via the MediaPackage live API or AWS SDK, see the following: + [MediaPackage Live API reference ](https://docs.aws.amazon.com/mediapackage/latest/apireference/origin_endpoints.html) + [AWS SDK](https://aws.amazon.com/getting-started/tools-sdks/) ------ ## Enabling daterange via the MediaPackage API or AWS SDK To learn how to enable daterange ad markers for TS and CMAF origin endpoints via the MediaPackage live API or AWS SDK, see the following: + [MediaPackage Live API reference ](https://docs.aws.amazon.com/mediapackage/latest/apireference/origin_endpoints.html) + [AWS SDK](https://aws.amazon.com/getting-started/tools-sdks/) ## Example HLS manifest showing SCTE-35 EXT-X-DATERANGE signaling This example shows a HLS manifest generated by MediaPackage using `EXT-X-DATERANGE` and `EXT-X-PROGRAM-DATE-TIME` tags to signal events in the live stream. **Note** The `DURATION`, `PLANNED-DURATION`, and `END-DATE` attributes of the `EXT-X-DATERANGE` tag are optional. If these attributes aren't present in the SCTE-35 input, or aren't set when you create your origin endpoint via the MediaPackage API, then they are omitted from the generated manifests. ``` #EXTM3U #EXT-X-VERSION:3 #EXT-X-TARGETDURATION:8 #EXT-X-MEDIA-SEQUENCE:11 #EXT-X-DATERANGE:ID="2415919105",START-DATE="2020-05-03T00:01:00.018Z",PLANNED-DURATION=29.988,SCTE35-OUT=0xFC303000000002CDE400FFF00506FE00526C14001A021843554549900000017FC00000292EA80A04ABCD0001300000D6F17117 #EXT-X-DATERANGE:ID="2147483649",START-DATE="2020-05-03T00:00:30.030Z",PLANNED-DURATION=90.006,SCTE35-CMD=0xFC303000000002CDE400FFF00506FE00293D6C001A021843554549800000017FFF00007B9ABC0A04ABCD0001100000680F3B4B #EXT-X-PROGRAM-DATE-TIME:2020-05-03T00:01:08.040Z #EXTINF:7.560, index_1_11.ts?m=1588607409 #EXTINF:7.560, index_1_12.ts?m=1588607409 #EXTINF:6.846, index_1_13.ts?m=1588607409 #EXT-X-DATERANGE:ID="2415919105",START-DATE="2020-05-03T00:01:00.018Z",END-DATE="2020-05-03T00:01:30.006Z",DURATION=29.988 #EXTINF:0.714, index_1_14.ts?m=1588607409 #EXTINF:7.560, index_1_15.ts?m=1588607409 #EXTINF:7.560, index_1_16.ts?m=1588607409 #EXTINF:7.560, index_1_17.ts?m=1588607409 #EXTINF:6.636, index_1_18.ts?m=1588607409 #EXT-X-DATERANGE:ID="2147483649",START-DATE="2020-05-03T00:00:30.030Z",END-DATE="2020-05-03T00:02:00.036Z",DURATION=90.006,SCTE35-CMD=0xFC304A00000002CDE400FFF00506FE00A4D8280034021843554549800000017FC000000000000A04ABCD0001110000021843554549800000027FFF00007B9ABC0A04ABCD000210000061166A61 #EXT-X-DATERANGE:ID="2147483650",START-DATE="2020-05-03T00:02:00.036Z",PLANNED-DURATION=90.006,SCTE35-CMD=0xFC304A00000002CDE400FFF00506FE00A4D8280034021843554549800000017FC000000000000A04ABCD0001110000021843554549800000027FFF00007B9ABC0A04ABCD000210000061166A61 #EXTINF:0.924, index_1_19.ts?m=1588607409 #EXTINF:7.560, index_1_20.ts?m=1588607409 #EXT-X-PROGRAM-DATE-TIME:2020-05-03T00:02:08.520Z #EXTINF:7.560, index_1_21.ts?m=1588607409 #EXT-X-ENDLIST ``` # HLS CUE tag ad markers in AWS Elemental MediaPackage HLS CUE tag ad markersAdded support for HLS CUE tags MediaPackage now supports HLS and LL-HLS CUE tag ad markers for `time_signal` or `splice_insert` tags in the manifest. CUE tag ad markers are used to signal ads and program transitions in live HLS manifests using industry-standard CUE tags. When you enable SCTE-35 enhanced ad markers on your HLS or LLHLS origin endpoint, MediaPackage inserts `EXT-X-CUE-OUT`, `EXT-X-CUE-IN`, and related CUE tags into the manifest where there are SCTE-35 `time_signal` or `splice_insert` tags present. This format provides the same SCTE-35 information as DATERANGE tags but in a different manifest format that's compatible with legacy ad insertion systems. The CUE tags generated by MediaPackage include: + `EXT-X-CUE-OUT` - Signals the start of an ad break + `EXT-X-CUE-IN` - Signals the end of an ad break + `EXT-X-CUE-OUT-CONT` - Continuation of ad break across segments + `EXT-OATCLS-SCTE35` - OATCLS-specific SCTE-35 data + `EXT-X-ASSET` - Asset identification tags For information about CUE tags for HLS, see the [HTTP Live Streaming 2nd Edition Specification](https://tools.ietf.org/html/draft-pantos-hls-rfc8216bis-07#section-4.4.5.1). The following table describes how to enable CUE tag ad markers in MediaPackage. ------ #### [ Console ] To enable CUE tag ad markers when creating or editing an origin endpoint, in the MediaPackage console, under the HLS or LL-HLS manifest settings, **SCTE configuration**, **Ad markers**, choose **SCTE-35 enhanced**. ------ #### [ AWS CLI ] To enable CUE tag ad markers for your origin endpoint, run the following command in the AWS CLI replacing *region* with your own information: ``` aws --endpoint=https://mediapackagev2.region.amazonaws.com mediapackagev2 --region region create-origin-endpoint --channel-group-name test_channel_group --channel-name test_channel --origin-endpoint-name hls_endpoint --hls-manifests "[{\"ManifestName\":\"main\",\"ScteHls\":{\"AdMarkerHls\":\"SCTE35_ENHANCED\"}}]" ``` ------ #### [ API and SDK ] To learn how to enable CUE tag ad markers for TS and CMAF origin endpoints via the MediaPackage live API or AWS SDK, see the following: + [MediaPackage Live API reference ](https://docs.aws.amazon.com/mediapackage/latest/APIReference/API_ScteHls.html) + [AWS SDK](https://aws.amazon.com/getting-started/tools-sdks/) ------ ## Example HLS manifest showing SCTE-35 CUE tag signaling This example shows a HLS manifest generated by MediaPackage using CUE tags to signal events in the live stream. ``` #EXTM3U #EXT-X-VERSION:3 #EXT-X-TARGETDURATION:8 #EXT-X-MEDIA-SEQUENCE:11 #EXTINF:3.3600001, segment_h264_720p25_731013628.ts #EXT-OATCLS-SCTE35:/DBhAAAAAAAAAP/wBQb/tnKlYABLAklDVUVJBAAAE3//AAApQPAOM0I6UDJJbm5pbmcxT3ZlcjMsUDpQMixUOk92ZXIsUzozLEk6MSxDOlBSLTI1LTAxODM1MTQAAAAAF2kX6w== #EXT-X-ASSET:CAID=0x423A5032496E6E696E67314F766572332C503A50322C543A4F7665722C533A332C493A312C433A50522D32352D303138333531 #EXT-X-CUE-OUT:30.04 #EXTINF:3.36, segment_h264_720p25_731013629.ts #EXT-X-CUE-OUT-CONT:ElapsedTime=3.36,Duration=30.04,CAID=0x423A5032496E6E696E67314F766572332C503A50322C543A4F7665722C533A332C493A312C433A50522D32352D303138333531,SCTE35=/DBhAAAAAAAAAP/wBQb/tnKlYABLAklDVUVJBAAAE3//AAApQPAOM0I6UDJJbm5pbmcxT3ZlcjMsUDpQMixUOk92ZXIsUzozLEk6MSxDOlBSLTI1LTAxODM1MTQAAAAAF2kX6w== #EXTINF:2.4, segment_h264_720p25_731013630.ts #EXT-X-CUE-OUT-CONT:ElapsedTime=5.76,Duration=30.04,CAID=0x423A5032496E6E696E67314F766572332C503A50322C543A4F7665722C533A332C493A312C433A50522D32352D303138333531,SCTE35=/DBhAAAAAAAAAP/wBQb/tnKlYABLAklDVUVJBAAAE3//AAApQPAOM0I6UDJJbm5pbmcxT3ZlcjMsUDpQMixUOk92ZXIsUzozLEk6MSxDOlBSLTI1LTAxODM1MTQAAAAAF2kX6w== #EXTINF:2.4, segment_h264_720p25_731013631.ts ... #EXT-X-CUE-OUT-CONT:ElapsedTime=27.36,Duration=30.04,CAID=0x423A5032496E6E696E67314F766572332C503A50322C543A4F7665722C533A332C493A312C433A50522D32352D303138333531,SCTE35=/DBhAAAAAAAAAP/wBQb/tnKlYABLAklDVUVJBAAAE3//AAApQPAOM0I6UDJJbm5pbmcxT3ZlcjMsUDpQMixUOk92ZXIsUzozLEk6MSxDOlBSLTI1LTAxODM1MTQAAAAAF2kX6w== #EXTINF:2.68, segment_h264_720p25_731013640.ts #EXT-OATCLS-SCTE35:/DBaAAAAAAAAAP/wBQb/tpyBAABEAkJDVUVJBAAAE3+/DjNCOlAySW5uaW5nMU92ZXIzLFA6UDIsVDpPdmVyLFM6MyxJOjEsQzpQUi0yNS0wMTgzNTE1AAD7WvT6 #EXT-X-CUE-IN #EXTINF:2.4, segment_h264_720p25_731013641.ts #EXT-X-ENDLIST ``` # DASH ad markers in AWS Elemental MediaPackage DASH ad markers DASH EventStream elements are used to signal all SCTE-35 `time_signal` or `splice_insert` markers present in the source. When you configure the ad markers to use the XML signaling, all the SCTE-35 markers parameters will be described through multiple nested XML elements inside the Event element. When you configure the Ad markers to use the Binary signaling, all the SCTE-35 markers parameters will be described through a Signal element including a binary base64-encoded representation of the SCTE marker, nested inside the Event element. For more information about the XML and Binary signaling schemes for DASH, see section 5.5.2 of the [DASH Industry Forum IOP Guidelines v5](https://dashif.org/docs/IOP-Guidelines/DASH-IF-IOP-Part5-v5.0.0.pdf). The following table describes how to enable DASH ad markers in MediaPackage. ------ #### [ Console ] To enable DASH ad markers when creating or editing an origin endpoint, in the MediaPackage console, under the DASH manifest settings, **SCTE configuration**, **Ad markers**, choose **XML** or **Binary**. ------ #### [ AWS CLI ] To enable DASH ad markers for your origin endpoint, run one of the following commands in the AWS CLI replacing *region* with your own information: ``` aws --endpoint=https://mediapackagev2.region.amazonaws.com mediapackage --region region create-origin-endpoint --channel-id test_channel --id test _endpoint --dash-package "{\"AdMarkerDash\":\"XML\"}" ``` or ``` aws --endpoint=https://mediapackagev2.region.amazonaws.com mediapackage --region region create-origin-endpoint --channel-id test_channel --id test _endpoint --dash-package "{\"AdMarkerDash\":\"BINARY\"}" ``` ------ #### [ API and SDK ] To learn how to enable DASH ad markers for DASH manifests on CMAF origin endpoints via the MediaPackage live API or AWS SDK, see the following: + [MediaPackage Live API reference ](https://docs.aws.amazon.com/mediapackage/latest/apireference/origin_endpoints.html) + [AWS SDK](https://aws.amazon.com/getting-started/tools-sdks/) ------ ## Example DASH manifest showing SCTE-35 EXT-X-DATERANGE signaling This example shows a DASH manifest generated by MediaPackage using XML signal approach to signal a `splice_insert` event in the live stream. ``` ``` This example shows a DASH manifest generated by MediaPackage using Binary signal approach to signal a `splice_insert` event in the live stream. ``` /DAlAAAAAyiYAP/wFAUAAABjAOCAABuOsIAAKTLgAAEBAQAAbK+RAw== ```