

# Creating a Microsoft Smooth output group
<a name="opg-mss"></a>

When you create a AWS Elemental MediaLive channel, you might want to include a Microsoft Smooth output group. For information about the use cases for a Microsoft Smooth output group, see [Containers, protocols, and downstream systems](outputs-supported-containers-downstream-systems.md).

**Topics**
+ [Organize encodes in a Microsoft Smooth output group](organize-mss-package.md)
+ [Coordinate with the downstream system](origin-server-mss.md)
+ [Create a Microsoft Smooth output group](creating-smooth-output-group.md)

# Organize encodes in a Microsoft Smooth output group
<a name="organize-mss-package"></a>

A Microsoft Smooth output group is typically set up as a video ABR stack. A video ABR stack is an output group that contains the following:
+ More than one outputs.

Each output can contain the following:
+ One video encode (rendition). Typically, each video encode is a different resolution.  
+ One or more audio encodes.
+ One or more captions encodes. The captions are always sidecar format.

There are two ways to organize the encodes, depending on whether the audio encodes must be bundled or each in their own rendition. You should have already [obtained this information](identify-dss-video-audio.md) from your downstream system.

**Downstream players that require bundled audio**

Plan for the output group to contain the following:
+ One output for each video encode. This output holds one video encode, all the audio encodes, and all the captions encodes (if the captions are embedded). 

  The same audio encodes will appear in each output. For example, the English and French encodes will appear in the high-resolution output, then the same English and French encodes will appear in the low-resolution output.
+ One output for each captions encode. Sidecar captions always go in their own output.

This diagram illustrates a Microsoft output group with bundled audio.

![\[Output group diagram showing V, A, A components bundled with V, A, A, and separate C, C outputs.\]](http://docs.aws.amazon.com/medialive/latest/ug/images/output12-ABR-2V-2A-2C.png)


**Downstream players that require separate audio**

Plan for the output group to contain the following:
+ One output for each video encode. This output holds one video and all the captions encodes (if the captions are embedded). 
+ One output for each audio encode.

  The audio encodes might be for different languages, or they might be for different bitrates, or they might be for different languages and bitrates.
+ One output for each captions encode. Sidecar captions always go in their own output.

The arrangement of the audio encodes in this output group is called an *audio rendition group*.

This diagram illustrates a Microsoft Smooth output group with an audio rendition group.

![\[Output group containing six outputs: two V, two A, and two C, arranged in a row.\]](http://docs.aws.amazon.com/medialive/latest/ug/images/output14-ABR-2V-2Asep-2C.png)


# Coordinate with the downstream system
<a name="origin-server-mss"></a>

You and the operator of the downstream system must agree about the destination for the output of the Microsoft Smooth output group.

1. Decide if you need two destinations for the output: 
   + You need two destinations in a [standard channel](plan-redundancy.md).
   + You need one destination in a single-pipeline channel.

1. Talk to the operator at the Microsoft IIS server to agree on a full path for the output. Make a note of the URLs that you agree on. For example:

   `https://203.0.113.55/sports/curling`

   `https://203.0.113.82/sports/curling`

1. Arrange with the operator to set up user credentials, if the protocol is HTTPS. 

1. Find out if the downstream system has special connection requirements. These connection fields are in the **General configuration** section for the Microsoft Smooth output group. To display this page on the MediaLive console, in the **Create channel** page, in **Output groups** section, choose **Add**, then choose **Microsoft Smooth**. Choose the group, then in **Microsoft Smooth settings**, open **General configuration**.

# Create a Microsoft Smooth output group
<a name="creating-smooth-output-group"></a>

When you [planned the workflow for your channel](identify-downstream-system.md), you might have determined that you want to include a Microsoft Smooth output group.

## The procedure
<a name="smooth-create-procedure"></a>

1. On the **Create channel** page, in the **Output groups** section, choose **Add**. 

1. In the **Add output group** section, choose **Microsoft Smooth**, and then choose **Confirm**. More sections appear:
   + **Microsoft Smooth group destination** – This section contains fields for the [destination of the outputs](smooth-destinations.md).
   + **Microsoft Smooth settings** – This section contains fields for the [container](smooth-container.md), the [connection to the downstream system](smooth-destinations.md), and [resiliency](mss-other-fields.md#smooth-resiliency). 
   + **Microsoft Smooth outputs** – This section shows the single output that is added by default.
   + **Event configuration** – This section contains fields for the [destination of the outputs](smooth-destinations.md) and the[container](smooth-container.md).
   + **Timecode configuration** – This section contains fields for the [timecode](mss-other-fields.md#smooth-timecode) in the outputs.
   + **Sparse track** – This section contains fields for the [container](smooth-container.md).

1.  If your plan includes more than one output in this output group, then in **Microsoft Smooth outputs**, choose **Add output** to add the appropriate number of outputs. 

1. In **Microsoft Smooth outputs**, choose the first **Settings** link to view the sections for the first output:
   + **Output settings** – This section contains fields for the [output destination](smooth-destinations.md), and the [container](smooth-container.md).
   + **Stream settings** – This section contains fields for the [output streams](smooth-streams-section.md) (the video, audio, and captions).

1. (Optional) Enter names for the output group and the outputs:
   + In **Microsoft Smooth settings**, for **Name**, enter a name for the output group. This name is internal to MediaLive; it doesn't appear in the output. For example, **Sports Curling**.
   + In the **Output settings** section for each output, for **Output name**, enter a name for the output. This name is internal to MediaLive; it doesn't appear in the output. For example, **high resolution**.

1. To complete the other fields, see the topics listed after this procedure.

1. After you have finished setting up this output group and its outputs, you can create another output group (of any type), if your plan requires it. Otherwise, go to [Save the channel](creating-a-channel-step9.md).

**Topics**

# Fields for the output destination
<a name="smooth-destinations"></a>

The following fields configure the destination of each Microsoft Smooth output.
+ **Output group** – **Microsoft Smooth group destination** section
+ **Output group – Event configuration – Event ID mode** 
+ **Output group – Event configuration – Event ID**
+ **Microsoft Smooth settings** section – **General configuration** section:
  + **Connection retry interval** 
  + **Num retries**
  + **Filecache duration**
  + **Restart delay**
  + **Certificate mode**

## Complete the fields on the console
<a name="smooth-specify-destination"></a>

The full path for each output in a Microsoft Smooth output group consists of the following:

`URL eventID streamInformation `
+ The URL and event ID are know as the *publishing points*. For example:

  `https://203.0.113.18/sports/Events(1585232182)`
+ MediaLive generates the event ID using information that you provide. For more information, expand **Event Configuration** on the console, and choose the **Info **link next to each field.
+ MediaLive generates the stream ID. It assigns a unique number to the stream, starting from 0. For example: `/Streams(stream0)`.

  You will be able to see the stream information when you look at the MediaLive logs for the output.

**To specify the path and connection to the downstream system**

1. Complete the **URL** fields in the **Microsoft Smooth group destinations** section. Specify two destinations if the channel is set up as a standard channel, or one destination if it is set up as a single-pipeline channel. Don't worry about the event ID. You will specify that in another field.

    For example:

   `https://203.0.113.55/sports/curling`

   `https://203.0.113.82/sports/curling`

1. Complete the **Credentials** section, if the downstream system provided you with a user name and password. For the password, enter the name of the password stored on the AWS Systems Manager Parameter Store. Don't enter the password itself. For more information, see [Requirements for AWS Systems Manager password parameters](requirements-for-EC2.md). 

1. If you obtained values to configure the connection, enter those values in the **General configuration** section on the **Microsoft Smooth group** page.

1. Set up the event ID in the following fields: 

   **Output group settings – Event configuration – Event ID Mode**

   **Output group settings – Event configuration – Event ID**

   You can set up the event ID in three ways:
   + With an event ID that you specify – Set **Event ID mode** to **USE\$1CONFIGURED**. Then specify the ID. For example, **curling**. The event ID will look like this: **/Events(curling)**
   + With a timestamp – Set **Event ID mode** to **USE\$1TIMESTAMP**. MediaLive generates a Unix timecode based on the time that you start the channel. The event ID will look like this: **/Events(1585232182)**
   + With no event ID – set **Event ID mode** to **NO\$1EVENT\$1ID**. We strongly recommend that you don't use this method.

# Fields for the container
<a name="smooth-container"></a>

The following fields configure the container in each output.
+ **Microsoft Smooth settings** section – **General configuration** section – **Fragment length** 
+ **Event configuration** – **Stream manifest behavior**
+ **Event configuration – Event stop behavior**

These fields let you configure some of the streaming behavior. For information about a field, choose the **Info** link in the MediaLive console. 

# Fields for the encodes
<a name="smooth-streams-section"></a>

The following fields relate to the encoding of the video, audio, and captions streams (encodes) in the output. 
+ **Stream settings** section

For information about creating encodes, see the following sections:
+ [Set up the video encode](creating-a-channel-step6.md)
+ [Set up the audio encodes](creating-a-channel-step7.md)
+  [Set up the captions encodes](creating-a-channel-step8.md)

# Fields for other Microsoft Smooth features
<a name="mss-other-fields"></a>

## Fields for resiliency
<a name="smooth-resiliency"></a>

The following field relates to implementing resiliency in a Microsoft Smooth output. 
+ **Microsoft Smooth output group** – **Microsoft Smooth Settings** section – **General configuration** section – **Input loss action**

Optionally change the value of **Input loss action**. 

Choose the **Info** link in the MediaLive console to decide which option to choose. For more information, see [Handling loss of video input](feature-input-loss.md).

## Fields for timecode
<a name="smooth-timecode"></a>

The following fields relate to configuring the timecode and timestamp in all the outputs in the output group. 
+ **Microsoft Smooth output group** – **Timecode Configuration** section 

For details about a field, choose the **Info** link next to the field in the MediaLive console.

## Fields for SCTE-35
<a name="smooth-s35"></a>

The following fields relate to configuring the timecode and timestamp in all the outputs in the output group. 
+ **Microsoft Smooth output group** – **Timecode Configuration** section 

If you want all the outputs in this output group to include the SCTE-35 messages that are already present in the input, choose **Sparse track**. The messages will be included in a sparse track. For more information, see [Processing SCTE 35 messages](scte-35-message-processing.md) and specifically [Enabling decoration – Microsoft Smooth](procedure-to-enable-decoration-ms-smooth.md).