Ingesting from VSF TR-01 in a TS - AWS Elemental Live

This is version 2.18 of the AWS Elemental Live documentation. This is the latest version. For prior versions, see the Previous Versions section of AWS Elemental Live and AWS Elemental Statmux Documentation.

Ingesting from VSF TR-01 in a TS

AWS Elemental Live supports VSF TR-01 ingest over a transport stream (TS). Support for TR-01 provides a solution to migrating from SDI infrastructure to an all-IP infrastructure. Handling of IP inputs using TR-01 is almost feature-equivalent to the handling of SDI inputs.

The presence of TR-01 means that the video and audio are TR-01-compliant, as described below. In addition, SMPTE-2038 is required in a TR-01-compliant TS.

Supported Sources

Video in TR-01

The video source must be encoded with JPEG 2000 and can be one of the following:

Definition Resolutions Maximum Bitrate Color Space
SD 576i/25 and 480i/29.97 200 MBps ITU-R BT 601-6
HD-SDI Up to 1080i/25/29.97 and 720p/50/59.94 200 MBps ITU-R BT 709-5
3G-SDI 1080p/50 and 1080p/59.94 200 MBps ITU-R BT 709-5

Audio Codecs in TR-01

The audio source can contain up to eight audio signals. Each audio signal is wrapped in SMPTE-302. At any given point in the source, the SMPTE-302 can contain:

  • One AES3 signal pair of Dolby AC3. The AES3 pair is wrapped in SMPTE-337.

  • One AES3 signal pair of Dolby E-AC3.The AES3 pair is wrapped in SMPTE-337.

  • One AES3 signal pair of Dolby E. The AES3 pair is wrapped in SMPTE-337. There is support for multi-program Dolby E streams, in which case individual programs can be selected

  • Or one uncompressed PCM audio stream.

There is support for source monitoring of audio codecs carried in SMPTE-302. If the audio codec (or type) changes, AWS Elemental Live detects the change and processes the new codec appropriately.

AWS Elemental Live enforces the rule about the contents of the SMPTE-302 as follows:

  • For the audio codecs other than PCM, if the SMPTE-302 contains invalid content (there is more than one signal pair in the SMPTE-302), then only the first signal pair will be processed and the remaining signal pairs will be discarded.

  • For PCM, if the SMPTE-302 contains invalid content (there is more than one signal pair in the SMPTE-302), then AWS Elemental Live will process both. The probable result will be garbled audio.

  • If the audio source contains an unsupported codec or format, AWS Elemental Live logs a message, displays an alert on the web interface, and inserts silence. AWS Elemental Live continues monitoring the source and detecting the format.

Setting Up a New Event

Perform the following steps to set up a new event:

  1. In Input, set the Input type to Network Input. In Network Location, specify an IP address.

  2. In Input > Advanced, set the Prefer SMPTE-2038 field as appropriate:

    • If you do not want AWS Elemental Live to look at the SMPTE-2038, uncheck this field. When the Prefer SMPTE-2038 field is unchecked (default), then AWS Elemental Live follows the legacy behavior. It looks for ancillary data in the native TS. Even if a SMPTE-2038 PID is present, AWS Elemental Live ignores that PID.

    • If you want to use the SMPTE-2038 ancillary data, and assuming the stream contains well-formed SMPTE-2038 (above), then check this field.

      For information about how SMPTE-2038 ancillary data is extracted and processed, see Ingesting Ancillary Data from SMPTE-2038 in an MPEG-2 TS.

  3. In Input > Video Selector and Input > Audio Selector, set up the video and audio in the usual way. There are no special steps for setting up TR-01 video or audio inputs.

  4. Set up the remainder of the event in the usual way.

The video identified in the video selector and the audio identified in the audio selector are extracted from the TR-01 in the TS. The video and audio are processed in the usual way, as specified in the output sections of the event. The ancillary data (if used) is extracted from the SMPTE-2038 and processed as described in Ingesting Ancillary Data from SMPTE-2038 in an MPEG-2 TS.

Migrating from SDI Inputs to TR-01 Inputs

If you have an event that is configured to use an SDI input, you can easily adapt it to use an IP network feed that contains TR-01-compliant video and audio. Change the existing event as follows:

  • Change the Input Type to Network Input. In Network Location, specify an IP address.

  • Set the Prefer SMPTE-2038 box as appropriate:

    • If you do not want AWS Elemental Live to look at the SMPTE-2038, uncheck this field. When the Prefer SMPTE-2038 field is unchecked (default), then AWS Elemental Live follows the legacy behavior. It looks for ancillary data in the native TS. Even if a SMPTE-2038 PID is present, AWS Elemental Live ignores that PID.

    • If you want to use the SMPTE-2038 ancillary data, and assuming the stream contains well-formed SMPTE-2038 (above), then check this field.

      For information about how SMPTE-2038 ancillary data is extracted and processed, see Ingesting Ancillary Data from SMPTE-2038 in an MPEG-2 TS.

    There is no requirement to change any other fields: the event should now perform the same processing as previously.

The video identified in the video selector and the audio identified in the audio selector are extracted from the TR-01 in the TS. The video and audio are processed in the usual way, as specified in the output sections of the event. The ancillary data (if used) is extracted from the SMPTE-2038 and processed as described in Ingesting Ancillary Data from SMPTE-2038 in an MPEG-2 TS.