Select your cookie preferences

We use essential cookies and similar tools that are necessary to provide our site and services. We use performance cookies to collect anonymous statistics, so we can understand how customers use our site and make improvements. Essential cookies cannot be deactivated, but you can choose “Customize” or “Decline” to decline performance cookies.

If you agree, AWS and approved third parties will also use cookies to provide useful site features, remember your preferences, and display relevant content, including relevant advertising. To accept or decline all non-essential cookies, choose “Accept” or “Decline.” To make more detailed choices, choose “Customize.”

Preferences
Contact Us
Feedback
AWS Documentation
Create an AWS Account
POST: Add an SPTS to an MPTS - Conductor Live
HTTP Request and Response

POST: Add an SPTS to an MPTS

PDF

Add an SPTS to the specified MPTS output.

HTTP Request and Response

Request URL

POST http://<Conductor IP address>/mpts/<ID of mpts>/mpts_members

Call Header

  • Accept: Set to application/xml

  • Content-Type: Set to application/xml

If you are implementing user authentication, you must also include three authorization headers; see Header Content for User Authentication.

Request Body

The request body contains XML content consisting of one mpts_member element with the following elements.

Element Value Description
type String The type is always “conductor.”
program_number Integer The program number to use for this SPTS program. 1 – 65535. This must be unique within this MPTS output.
pid_map See below.

The PID assignments to use for this member in the MPTS output. If no values are provided, PIDs are assigned automatically.

All PIDs must be unique among all SPTS programs in the MPTS output (not just unique within the individual SPTS program).

Support is provided for both PID keys with single values and those with multiple values. See below for details.
channel_id Integer

The ID of the Conductor Live channel that produces the desired SPTS. To obtain the ID of a specific channel, see GET List: Get List of Channels.

This channel:

  • Can belong to a maximum of two different MPTS outputs.

  • Must include at least one UDP output that is set up to produce input into an MPTS: in other words, the MPTS field is set to Remote (not to Local or None).

For information on all the special requirements for the channel, see Create a Profile for MPTS Channels in the AWS Elemental Conductor Live User Guide.

PID Map

The PID map is XML content consisting of one <pid_map> element that contains the following elements.

<pid_map> 0 or 1 instances Object

<pmt_pid>

<video_pid>

<pcr_pid>

<scte35_pid>

<klv_data_pid>

<dvb_teletext_pid>

<etv_platform_pid>

<etv_signal_pid>

<timed_metadata_pid>

<private_metadata_pid>

<ecm_pid>

<arib_captions_pid>

 0 or 1 instances Integer
<audio_pids> 0 or 1 instances Object
<audio_pid> 1 or more instances Integer
<dvb_sub_pids> 0 or 1 instances Object
<dvb_sub_pid> 1 or more instances Integer

For example:

<pid_map> 
  <pmt_pid>888</pmt_pid>
  <audio_pids type="array">
    <audio_pid>240</audio_pid>
    <audio_pid>241</audio_pid>
  </audio_pids> 
</pid_map>

Response

The response repeats back the data that you posted with the addition of:

  • id: The newly assigned ID for the mpts_member.

The response is identical to the response to a GET MPTS Member. See below for an example.

Next topic:

Example

Need help?

PrivacySite termsCookie preferences
© 2025, Amazon Web Services, Inc. or its affiliates. All rights reserved.