Setting up MPTS Outputs - AWS Elemental Conductor Live 3

This is version 3.17 of the AWS Elemental Conductor Live 3 documentation. This is the latest version. For prior versions, see the Previous Versions section of AWS Elemental Conductor Live 3 Documentation.

Setting up MPTS Outputs

Step A. Create the MPTS Outputs

To create an MPTS output

  1. On the Multi-Protocol Transport Service (MPTS) screen, choose New MPTS. The Create a New MPTS dialog appears.

    
                     Image file create-mpts-output.png
  2. Complete the dialog as follows:

    Field Description Comment
    Name Any name. Required
    Transport Stream ID The PID for the transport stream in the MPTS output. Required
    Node

    The node where the MPTS is created: where the muxing of the individual programs occurs. You must select this node.This list shows all nodes except those that are set up as backup nodes in a redundancy group.

    Select the correct node. Be aware of the node types and choose:

    • Any node if you are creating an MPTS consisting only of Constant Bitrate (CBR) programs.

    • An node with the Statmux option if you are creating an MPTS that includes at least one Statmux program.

    • An AWS Elemental Statmux standalone node if you are creating an MPTS that includes at least one Statmux program.

    Required
    Transport Stream Bitrate The total bitrate of the MPTS output in bits/second. The muxer ensures that the combined bitrate of the individual SPTS channels (the video, audio, captions, and data bitrates) in the MPTS does not exceed this number. Required
    Video Allocation

    The bitrate allocated for video traffic in the MPTS output in bits/second.

    The muxer ensures that the combined video bitrate of the individual channels in the MPTS does not exceed this number.

    Required
    Output Tab
    Field Description Comment
    Destination 1

    The primary destination for the MPTS output. This can be a UDP or RTP location. This must be completed.

    Format:

    <protocol> ://<IP address > :<port >

    Required
    Interface The interface; we recommend that the interface be explicitly defined. Optional
    Virtual Source Address The virtual source address. Complete if desired.
    Destination 2

    The secondary destination, interface, and virtual source address. Optional.

    Completing a secondary destination provides “network failure redundancy” for the MPTS. The muxer sends the output to both destination 1 and destination 2; if one destination fails, downstream systems can obtain it from the other.

    If you are not setting up for “network failure redundancy,” leave these fields blank.

    Optional
    Interface Optional
    Virtual Source Address Optional
    Forward Error Correction (FEC) Complete as desired to enable FEC on the MPTS output as per SMPTE 2022-1 through 2022-4. FEC is enabled to allow the downstream system to reconstruct data when packets are lost. Select one of the following.
    • Disabled.

    • Include Column FEC-Only. More fields appear:

      • Columns: The number of RTP packets per column (the D parameter as per SMPTE-2022-1). Range 4-20. Rows x columns ≤ 100.

      • Rows: Always treated as 1.

    • Include Column and Row FEC. More fields appear:

      • Columns: The number of RTP packets per column (the D parameter as per SMPTE-2022-1). Range 4-20. Rows x columns ≤ 100.

      • Rows: The number of RTP packets per column (the L parameter as per SMPTE-2022-1). Range 1-20.

    Optional
    UDP Buffer Size The size of the network output buffer. This buffer is used to limit PCR jitter on the network.
    • Auto: Selects optimal size based on the video elementary stream properties.

    • Custom: Determines an integer value for the number of bits to use for the buffer.

    • Off: Smooths bursts in the network output but does not attempt to limit PCR jitter; this can be used to achieve low-latency streams where output devices do not require buffer-compliant outputs.

    Optional
    Redundancy Tab
    Field Description Comment
    Output Listening Interval

    This field is used to set up for output redundancy with output listening and applies only if your statmux deployment involves nodes as the encoders and an AWS Elemental Statmux node as the muxer. See Combination: Statmux Node Redundancy with Output Listening.

    If you are not setting up for this type of redundancy or if the node is both the encoder and muxer, do not check the box.

    Optional
    Allocation Message Priority

    This field is used to set up for multiplexer redundancy and applies only if your statmux deployment involves nodes as the encoders and an AWS Elemental Statmux node as the muxer; see Statmux Node Redundancy.

    If you are not setting up for this type of redundancy or if the node is both the encoder and muxer, leave the default value.

    Optional
    Advanced
    Field Description Comment
    Additional Statmux System Latency

    Specify additional time (in milliseconds) to add to the “maximum encoding latency”- the time between when the Single Program Transport Stream (SPTS) channels send their complexity data to the muxer and when the muxer expects the related encoded content for all channels.

    Typically, specify additional time only if the Buffer Size (set in the video stream) for one of the SPTS channels is longer than typical or if an SPTS channel is set up for 4K HEVC encoding via bonded Live 401 or 402 encoders.

    Note that you are not able to change this value while the MPTS is running; you have to stop the MPTS output and then restart it. This is the only field on the MPTS that you cannot change after creating it.

    Optional
    PAT Interval Set as desired. Optional
    SDT Interval Set as desired. The box to the left of the value must be checked before edits can be made.
    TDT Set as desired.
    NIT Interval Set as desired. Enable Network Information Table (NIT) must be checked before edits can be made.
    Network ID Set as desired.
    Network Name Set as desired.
  3. Choose Save. The MPTS output is created.

    
                     Image file mpts-outputs.png

Step B. Create a Profile for MPTS Channels

If you are creating a profile to be used by a channel that provides input into an MPTS, you must set up the fields specifically for that purpose .

Within the UDP/TS output, set the MPTS fields as follows:

Area Field Description
Outputs The profile must include at least one UDP/TS output.
UDP/TS Output MPTS Membership This field must be set to Remote.
UDP/TS Output Primary Destination

The destination for the SPTS. This can be a UDP or RTP location.

The address must be a multicast address that is not being used by any other service.

Format:

<protocol > ://<IP address > :<port >

UDP/TS Output Primary Complexity Transmit Destination

The channel is configured to send complexity information to this location while the muxer is configured to look for complexity requests at this location.

The location must be a multicast address that is not being used by any other service.

Format:

<protocol > ://<IP address > :<port >

UDP/TS Output Primary Allocation Receipt Destination

The muxer is configured to send allocation values to this location while the channel looks for allocation values in this location.

The address must be a multicast address that is not being used by any other service.

Format:

<protocol > ://<IP address > :<port >

UDP/TS Output Secondary Destination

Optional. Complete these fields only if you are setting up for data exchange redundancy. See Implementing Redundancy in an MPTS.

If you are not setting up for data exchange redundancy, leave blank.

Secondary Complexity Transmit Destination
Secondary Allocation Receipt Destination
Stream for this UDP/TS Output Video Codec
  • If using CBR: any codec applicable to UDP/TS.

  • If using Statmux: H.264, HEVC, VC-1, MPEG-2.

Stream for this UDP/TS Output Rate Control Mode (Stream > Advanced)
  • CBR: If you want this stream (program) to have a constant bit rate inside the MPTS output.

  • Statmux: If you want this stream to have a variable bit rate inside the MPTS output.

  • Other values: These values are not valid for an MPTS.


               Image file mpts-channels-profile.png

Step C. Create the Channels

Create the individual channels that will be included in the Multi-Protocol Transport Service (MPTS). Create them in the usual way, specifying:

  • A profile that you created for use with an MPTS.

  • An node as the associated node (not an AWS Elemental Statmux node: this would not be correct, and, in any event, the web interface doesn’t let you select a Statmux node).

Step D. Add Channels to the MPTS Output

The channels you add must already exist: you cannot both create and add a channel to the MPTS output at the same time.

  1. On the MPTS screen, choose Channels (magnifier icon) beside the desired MPTS output. The Channels Details screen appears.

  2. Choose Add a Channel and choose from the list of channels that appears. This list contains the channels known to AWS Elemental Conductor Live 3 that are available to be added. To be eligible, a channel must have these characteristics:

    • An Output MPTS Membership set to Remote.

    • Not already be assigned to this MPTS.

    • Not already be assigned to an MPTS unless using CBR rate control.

      When a channel is using CBR for the Rate Control Mode, it can be used in unlimited MPTS applications.

      
                           Image file mpts-output-add-channels.png

      The Channels Detail screen reappears with the channel added. The PIDs all are set to blank.

  3. Assign values to the PIDs.

    • You can specify a range as “m-n”.

    • The same value cannot be assigned to two different fields within the channel or between two channels in the same MPTS.

    • If you leave a PID field blank, a value is automatically assigned.

      You can modify the channel later to remove the assigned PID value if needed.

  4. Choose Save.

The MPTS output is now set up. You can now start the MPTS output. See Starting an MPTS Output.