# Supported features by output type
<a name="processing-applicability-by-output-type"></a>

This section describes which SCTE 35 features apply to the various types of outputs that MediaLive supports. 

**Topics**
+ [Archive output with MPEG-2 container](archive-output-with-mpeg-2-container.md)
+ [Frame capture output](framecapture-output.md)
+ [HLS output](hls-output.md)
+ [MediaPackage output](mediapackage-output.md)
+ [Microsoft Smooth output](ms-smooth-output.md)
+ [RTMP output](adobe-rtmp-output.md)
+ [UDP or SRT output](udp-ts-output.md)

# Archive output with MPEG-2 container
<a name="archive-output-with-mpeg-2-container"></a>

In an Archive output (a transport stream in an MPEG-2 container), MediaLive supports SCTE 35 features as follows:
+ Passthrough of the SCTE 35 messages – Supported.
+ Manifest decoration – Not supported because these outputs don't have manifests.
+ Blanking and blackout – Applicable. Content in the output is blanked or blacked out if the features are enabled at the channel level.

Be careful of setting up so that you have removed messages from the input (passthrough disabled) and you have not enabled blanking and blackout. In this case, the video content that was marked by messages (in the input) will not be marked (in the output). 
+ If you have the rights to that video content, there is no problem setting up this way.
+ If you don't have the rights, then the only way to find that content will be to look for the IDR i-frames that identify where the SCTE 35 message used to be.

# Frame capture output
<a name="framecapture-output"></a>

In a Frame capture output, MediaLive supports SCTE 35 features as follows:
+ Passthrough of the SCTE 35 messages – Not applicable. 
+ Manifest decoration – Not supported because these outputs don't have manifests.
+ Blanking and blackout – Applicable. Content in the output is blanked or blacked out if the features are enabled at the channel level.

A Frame capture output doesn't support passthrough of the SCTE 35 messages. However, if blanking or blackout is enabled (at the channel level), then content that falls between the start and stop of the blackout is blanked or blacked out, even though no SCTE 35 messages are present. 

# HLS output
<a name="hls-output"></a>

In an HLS output (a transport stream), MediaLive supports SCTE 35 features as follows:
+ Passthrough of the SCTE 35 messages – Supported.
+ Manifest decoration – Supported.
+ Blanking and blackout – Applicable. Content in the output is blanked or blacked out if the features are enabled at the channel level.

MediaLive supports the following combinations of passthrough and manifest decoration:
+ Passthrough enabled, decoration enabled.
+ Passthrough disabled, decoration enabled.
+ Passthrough disabled, decoration disabled. Be careful of setting up with this combination but leaving blanking and blackout disabled. In this case, the video content that was marked by messages (in the input) are not marked (in the output). In addition, the manifests don't have information for identifying that video content. 
  + If you have the rights to that video content, there is no problem setting up this way.
  + If you don't have the rights, the only way to find that content is to look for the IDR i-frames that identify where the SCTE 35 message used to be.

# MediaPackage output
<a name="mediapackage-output"></a>

In a MediaPackage output, MediaLive supports SCTE 35 features as follows:
+ Passthrough of the SCTE 35 messages – Always enabled.
+ Manifest decoration – Always enabled.
+ Blanking and blackout – Applicable. Content in the output is blanked or blacked out if the features are enabled at the channel level.

# Microsoft Smooth output
<a name="ms-smooth-output"></a>

In a Microsoft Smooth output, MediaLive supports SCTE 35 features as follows:
+ Passthrough of the SCTE 35 messages – Not applicable. SCTE 35 messages are never included in this output. 
+ Manifest decoration – Not supported because these outputs don't have manifests. However, you can set up to include instructions in the sparse track.
+ Blanking and blackout – Applicable. Content in the output is blanked or blacked out if the features are enabled at the channel level.

Be careful of setting up so that you have the following combination:
+ You have not enabled sparse track.
+ You have not enabled blanking and blackout. 

In this case, the video content that was marked by messages (in the input) is not marked (in the output). 
+ If you have the rights to that video content, there is no problem setting up this way.
+ If you don't have the rights, it is impossible to find these blanks and blackouts programmatically in a Microsoft Smooth output.

# RTMP output
<a name="adobe-rtmp-output"></a>

In an RTMP output, MediaLive supports SCTE 35 features as follows:
+ Passthrough of the SCTE 35 messages – Not applicable.
+ Manifest decoration – Not supported.
+ Blanking and blackout – Applicable. Content in the output is blanked or blacked out if the features are enabled at the channel level.

# UDP or SRT output
<a name="udp-ts-output"></a>

In a transport stream output (for example, UDP or SRT), MediaLive supports SCTE 35 features as follows:
+ Passthrough of the SCTE 35 messages – Supported.
+ Manifest decoration – Not supported because these outputs don't have manifests.
+ Blanking and blackout – Supported.

Be careful of setting up so that you have removed messages from the input (passthrough disabled) and you have not enabled blanking and blackout. In this case, the video content that was marked by messages (in the input) is not marked (in the output). 
+ If you have the rights to that video content, there is no problem setting up this way.
+ If you don't have the rights, then the only way to find that content is to look for the IDR i-frames that identify where the SCTE 35 message used to be.