# Creating a SMPTE 2110 input
SMPTE 2110 inputSMPTE 2110 inputs

The guide now includes information about working with SMPTE 2110 inputs.

This section describes how to set up the source content on the upstream system, and how to create an SMPTE 2110 input that connects the upstream system to MediaLive. Create the input before you create the channel that ingests the input.

**Note**  
SMPTE 2110 inputs are supported only on AWS Elemental MediaLive Anywhere deployments. For more information about these deployments, see [Setting up AWS Elemental MediaLive Anywhere](setup-emla.md).

With an SMPTE 2110 input, MediaLive connects to the multicast IP address when the channel starts and *pulls* the sources. 

To perform this setup, you must work with the video engineer in your organization who created the SDP files for the SMPTE 2110 source.

**Topics**
+ [

# Obtain information
](setup-s2110-pull-obtain-info.md)
+ [

# Create a SMPTE 2110 input
](setup-input-s2110-pull.md)

# Obtain information
Step 1: Obtain information

Obtain the following information from the video engineer who created the SMPTE 2110 SDP files:
+ The location (URL) and file name of all the SDP files for the video, audio, and ancillary streams for the SMPTE 2110 source. 

  There should be only one video SDP file. There can be 0 or more audio SDP files, and 0 or more ancillary SDP files.
+ The number of video lines (v=) in the single video SDP file. If there is more than one video line, find out which line you must use. 

  You need the number of lines because you will need to identify the line to use by specifying its position in a zero-based media index. For example, if you need to use the third video line, the index is 2.
+ The number of audio lines (a=) in each audio SDP file.

  You need the number of lines because you will need to create a zero-based media index of the audio lines whenever there is more than one SDP file, and/or whenever there is more than one audio line in an SDP file.

  For example, there might be two audio SDP files, one with one lines and one with two lines. For the first file, you will create an index with one member (0), and for the second file you will create an index with members 0 and 1.
+ A list of the audio selectors you must create and the IDs of the channel groups (audio tracks) to include in each selector. (You don't need this information for video or ancillary streams.)

  MediaLive assigns a track number to each channel group, starting with the first channel group in the first line in the first SDP file, and covering all the audio lines in all the audio SDP files. The tracks are numbered from 1.

# Create a SMPTE 2110 input
Step 2: Create input

After you have obtained information from the upstream system, you can create a SMPTE 2110 input.

**To create an SMPTE 2110 input**

1. Make sure that you have the information from [step 1](setup-s2110-pull-obtain-info.md).

1. Open the MediaLive console at [https://console.aws.amazon.com/medialive/](https://console.aws.amazon.com/medialive/).

1. In the navigation pane, choose **Inputs**. On the **Inputs** page, choose **Create input**.

1. Complete the **SMPTE 2110 Receiver Group** section as described in the table that follows this procedure. 

1. In the **Tags **section, create tags if you want to associate tags with this input. For more information, see [Tagging resources](tagging.md).

1. Choose **Create**.

   MediaLive creates the input and adds it to the list of inputs. The input identifies the locations of the SDP files that contain information about the SMPTE 2110 streams. 

   When you start the channel, MediaLive will retrieve the SDP files. It will obtain the location of the SMPTE 2110 streams from the files. It will connection to those locations and pull the content that you specified when you [attach the input to the channel](creating-a-channel-step2.md).

**Fields for a SMPTE 2110 input**


| Field | Description | 
| --- | --- | 
| Video SDP | Enter the URL for the video SDP file. If you obtained a number that identifies the video line to extract, enter it in the Media index field. This index is zero-based. So if you need to extract the third line, enter 2. | 
| Audio SDPs | Enter information for each for each audio SDP file and audio line combination.See the example after this table. | 
| Ancillary SDPs | Enter information for each for each ancillary SDP file and audio line combination.See the example after this table. | 

You might have obtained the following information about the SDP files and their media lines:
+ One video file at `http://172.18.8.19/curling_video.sdp`. You need to extract the third video (index member 2).
+ The following audio SDP files and their audio lines:

  `http://172.18.8.19/curling_audio_1.sdp` with one audio line. 

  `http://172.18.8.19/curling_audio_2.sdp`, with two media lines.
+ One ancillary SDP file and their ancillary lines:

  `http://172.18.8.19/curling_ancill.sdp` with two media lines.

You will set up the Receiver Group fields as follows:


| SDP | SDP URL | Media index | 
| --- | --- | --- | 
| Video SDP | http://172.18.8.19/curling\$1video.sdp | 2 | 
| Audio SDP | http://172.18.8.19/curling\$1audio\$11.sdp | 0 | 
|  | http://172.18.8.19/curling\$1audio\$12.sdp | 0 | 
|  | http://172.18.8.19/curling\$1audio\$12.sdp | 1 | 
| Ancillary SDP  | http://172.18.8.19/curling\$1ancill.sdp | 0 | 
|  | http://172.18.8.19/curling\$1ancill.sdp | 0 |