---
title: Adding RTMP Targets
slug: zen-master/adding-rtmp-targets
docTags:
createdAt: 2024-12-27T19:19:10.566Z
---
ZEN Master enables you to 'Push' a channel to an RTMP server. You can configure redundant RTMP hosts to ensure consistency. To learn more about redundancy in ZEN Master see [Redundancy in ZEN Master](https://zixidocumentation.atlassian.net/wiki/spaces/ZMUG/pages/420184080/Redundancy+in+ZEN+Master).
The following procedure describes how to add an RTMP Target in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below.
## To add a new RTMP Target:
:::::WorkflowBlock
:::WorkflowBlockItem
In the main navigation, click **Targets**.
:::
:::WorkflowBlockItem
Click **+ Add**.
The **Create New Target** window is displayed.
::Image[]{src="https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/zvFxXsgvX6d6ikzJ2Qcmd_image.png" size="80" width="730" height="1406" position="center" alt="Create New Target window" darkWidth="730" darkHeight="1406" showCaption="false"}
:::
:::WorkflowBlockItem
Click on **RTMP**.
The **Create New RTMP Target** window is displayed.
::Image[]{src="https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/mHx78oYN253bRsH91HXRn-20251104-145151.png" size="80" width="1380" height="3016" position="center" darkWidth="1380" darkHeight="3016" showCaption="false"}
:::
:::WorkflowBlockItem
In the **Info** section, in the **Name** field, enter a logical name for the **RTMP** target.
:::
:::WorkflowBlockItem
In the **Tags** field, select one or more of the predefined Tags from the drop-down list.
Tags are used for access control. By selecting a Tag you are relating this target to that Tag. Tags are associated with certain roles (through the Users & Roles screen), and roles, in turn, are associated with users and user groups. If you would like to create a new Tag, see [Creating a Tag](docId\:YpM9tw81ap6nq8sTKv4Rd) .
:::
::::WorkflowBlockItem
In the **Events Configuration Profile** field, select from the dropdown list the profile that you would like to apply to this Target. By default, the Default profile is applied.
:::hint{type="info"}
*Events Profiles *consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger.
:::
::::
:::WorkflowBlockItem
The Target's location is used to represent it in the proper position in the Map display (see [Maps](docId\:sFZM6JvoRvuigo7X0dNUE)). By default, the location is determined automatically based on the Target's IP. If you would like to manually set the location of the Target (Optional), use the following procedure:
1. Click on the **Edit** icon next to the **Location **field.
A search box is shown below the **Location** field.
2. Enter identifying info for the location (e.g. street address, zip code, coordinates).
Search results are displayed below the search box as you type.
3. Click on the desired location.
The selected location populates the **Location** field.
:::
:::WorkflowBlockItem
In the **Configuration** section, under **Channel Type** select the type of Channel that the Target will receive. Options are: *ZEN Master Channel* or *AWS MediaLive Channel*.
:::
::::WorkflowBlockItem
In the **Configuration** section, in the **Channel** field, select from the drop-down list the channel that will be sent to the target. (Optional field)
:::hint{type="info"}
The target will only become functional once a channel has been assigned to it. However, you can configure the target settings and then add a channel to the target after the initial configuration.
:::
::::
::::WorkflowBlockItem
In the **Source Preference** field, select one of the following options:
- **Any Source** – the Target will establish a connection to any available source in the Channel. Upon any disconnects with the current source, the Target will reconnect to another available source in the Channel.
- **Primary Sources Only** – the Target will establish and maintain connection to a source designated as Primary in the Channel. Upon loss of connection to that source, the Target will establish a connection to another available Primary source in the Channel.
- **Backup Sources Only** – the Target will establish and maintain connection to a source designated as Backup in the Channel. Upon loss of connection to that source, the Target will establish connection to another available Backup source in the Channel.
- **Specific Source** – select one of the specific sources listed. The Target will only establish a connection to the selected source and will not try to connect to any other source in the Channel.
:::hint{type="info"}
It is not possible to select "Prefer Primary Sources" or "Prefer Backup Sources". This means you cannot have a Target failover from a Primary to a Backup source in the Channel unless "Any Source" is selected.
:::
::::
:::WorkflowBlockItem
In the **Single Output** checkbox, select this option if you want there to be a single output. This option provides less redundancy but is required for servers that do not properly support concurrent connections.
:::
:::WorkflowBlockItem
If you have selected the *AWS MediaLive Channel *as the channel type option, in the **Transcoding Profile** field, select the desired transcoding profile.
:::
:::WorkflowBlockItem
In the **Target** field, enter the URL of the primary RTMP server.
:::
:::WorkflowBlockItem
In the **Alt.** **Target** field, enter the URL of a backup RTMP server. (Optional field)
:::
:::WorkflowBlockItem
In the **Stream Name** field, enter the RTMP stream name as defined in the RTMP server (Target).
:::
:::WorkflowBlockItem
In the **Username** field, enter the RTMP stream access credentials – User name.
:::
:::WorkflowBlockItem
In the **Password** field, enter the RTMP stream access credentials – Password. Click **Show** to display the password.
:::
:::WorkflowBlockItem
If you would like to apply a **PID Mapping** profile to this Target, then in the **PID Mapping Profile** field, select the desired profile from the dropdown list. For more information, see [PID Mapping Profiles](docId\:OFVPYMHYVq4XqhIi3UMnS) .
:::
:::WorkflowBlockItem
In the **Initial State** section, select the **Disabled** checkbox if you would like to disable this Target upon initial configuration.
:::
:::WorkflowBlockItem
Select the **Muted** checkbox if you would like to disable error/recovery notifications for this Target upon initial configuration.
:::
::::WorkflowBlockItem
:::hint{type="info"}
You can Enable/Unmute the Target at any time.
:::
::::
:::WorkflowBlockItem
Under **Protections**, select the **Channel reassignment protection** chekbox if you want to prevent the reasssignment of this Target to another Channel. This is helpful in cases where you are switching the channel on multiple targets at once and can accidetaly select a Target that should not have been switched to the new Channel.
:::
:::WorkflowBlockItem
If you use POIS, expand the **SCTE-35 Manipulation (POIS)** section to see additional options.
:::
:::WorkflowBlockItem
Select **Enable SCTE-35 Manipulation** to enable insertion and management of SCTE-35 messages (used typically to create ad breaks).
:::
:::WorkflowBlockItem
If you have created [SCTE-35 Modification Profiles](docId:-QYmFFVMc18NqpumZ7T3d) and want to apply it to this target, select it from the dropdown list. Note that if you select a profile, the Remove Existing SCTE-35 option will automatically be checked and non-editable - the way the modification works is that the Broadcaster will remove all SCTE-35 messages, and then re-insert them in original or modified form acccording to the rules defined in the profile.
:::
:::WorkflowBlockItem
In the **NULL Packet Search Window **field, specify the time window in milliseconds of NULL packets to search for in order to insert SCTE-35 messages into the stream:
- If the stream is **VBR**, set the value to `0` - SCTE-35 messages can be inserted anywhere, and do not need a NULL packet
- If the stream is **CBR**, the downstream receiver *may* need a CBR stream. Inserting the SCTE-35 message into a NULL packet ensures the stream will remain CBR; however, it may delay the insertion of the message up to the length of the search window
:::
:::WorkflowBlockItem
In the **SCTE-35 PID** field, specify a specific PID number for SCTE-35 insertion.
:::
:::WorkflowBlockItem
If you are using an external POIS or ESNI system, enter the **External ID** that you use to reference the ZEN Master object in the other system. See the **Parameters** table below for more information.
:::
:::WorkflowBlockItem
In the **POIS Latency Offset **field, if you would like to offset the POIS modification path to allow for API latency, enter a value in miliseconds. This value can be zero, but it establishes that this output should receive POIS SCTE conditioning.
:::
:::WorkflowBlockItem
If you want the timeline adjusted (normalized) to account for insertion and/or removal of SCTE-35 messages, select **Make Timeline Continuous** (note that the processing will add approximately 100ms to latency).
:::
:::WorkflowBlockItem
If you would like to configure advanced settings, click on **Advanced **and enter values for the desired fields - see the **Paramaters Table** below for explanations of the fields.
:::
:::WorkflowBlockItem
Click **Save.**
:::
:::::
## RTMP Target Configuration Parameters Table
| **Parameter** | **Description** |
| ------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ***Info*** | |
| Name | Specify a name for the RTMP Target in ZEN Master. |
| Tags | Select one or more of the predefined Tags from the drop-down list.
Tags are used for access control. By selecting a Tag, you are relating this Target to that Tag. Tags are associated with certain roles (through the Users & Roles screen), and roles, in turn, are associated with users and user groups. If you would like to create a new Tag, see [Creating a Tag](docId\:YpM9tw81ap6nq8sTKv4Rd) . |
| Events Configuration Profile | Select from the dropdown list the profile that you would like to apply to this Target. By default, the *Default* profile is applied.
Note: *Events Profiles* consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. |
| Location (Optional) | The Target's location is used to represent it in the proper position in the Map display (see [Maps](docId\:sFZM6JvoRvuigo7X0dNUE)). By default, the location is determined automatically based on the Target's IP. Enter identifying info for the location (e.g. street address, zip code, coordinates) and select the desired location from the suggestions that are shown. |
| ***Configuration*** | |
| Channel Type | Select the type of Channel that the Target will receive. Options are: *ZEN Master Channel* or *AWS MediaLive Channel*. |
| Channel
(Optional) | Select from the drop-down list the Channel that will be sent to the Target.
Note: The Target will only become functional once a Channel has been assigned to it. However, you can configure the Target settings and then add a Channel to the target after the initial configuration. |
| Source Preference | Select from the drop-down list one of the following:
* **Any Source** – the Target will establish a connection to any available source in the Channel. Upon any disconnects with the current source, the Target will reconnect to another available source in the Channel.
* **Primary Sources Only** – the Target will establish and maintain connection to a source designated as Primary in the Channel. Upon loss of connection to that source, the Target will establish a connection to another available Primary source in the Channel.
* **Backup Sources Only** – the Target will establish and maintain connection to a source designated as Backup in the Channel. Upon loss of connection to that source, the Target will establish connection to another available Backup source in the Channel.
* **Specific Source** – the Target will only establish a connection to the source specified by the user and will not try to connect to any other source in the Channel.
Note: It is not possible to select "Prefer Primary Sources" or "Prefer Backup Sources". This means you cannot have a Target failover from a Primary to a Backup source in the Channel unless "Any Source" is selected. |
| Single Output | Select the Single Output mode if you want there to be a single output. This option provides less redundancy but is required for servers that do not properly support concurrent connections. |
| Transcoding Profile (AWS MediaLive Channel) | Select the desired transcoding profile. |
| Target | Enter the URL of the primary RTMP server. |
| Alt. Target
(Optional) | Enter the URL of a backup RTMP server. |
| Stream Name | Enter the RTMP stream name as defined in the RTMP server (Target). |
| Username | Enter the RTMP stream access credentials – User name. |
| Password | Enter the RTMP stream access credentials – Password. Click **show** to display the password. |
| PID Mapping Profile (optional) | If you would like to apply a PID Mapping profile to this Target, then select the desired profile from the dropdown list.
To create a new PID Mapping Profile, see [Adding PID Mapping Profiles](docId\:gFTCaYurPL7DInoUyd14z). |
| ***Initial State*** | |
| Disabled | Select this checkbox if you would like to disable this Target upon initial configuration. |
| Muted | Select this checkbox if you would like to disable error/recovery notifications for this Target upon initial configuration. |
| ***Protections*** | |
| Channel reassignment protection | Select this option if you want to prevent the reasssignment of this Target to another Channel. This is helpful in cases where you are switching the channel on multiple targets at once and can accidetaly select a Target that should not have been switched to the new Channel. |
| ***SCTE-35 Manipulation (POIS)*** | |
| Enable SCTE-35 Manipulation | Select to enable insertion and management of SCTE-35 messages (used typically to create ad breaks). |
| NULL Packet Search Window (ms) | Specify the time window in milliseconds of NULL packets to search for in order to insert SCTE-35 messages into the stream:
* If the stream is **VBR**, set the value to `0` - SCTE-35 messages can be inserted anywhere, and do not need a NULL packet
* If the stream is **CBR**, the downstream receiver *may* need a CBR stream. Inserting the SCTE-35 message into a NULL packet ensures the stream will remain CBR; however, it may delay the insertion of the message up to the length of the search window. |
| SCTE-35 PID | Specify a specific PID number for SCTE-35 insertion |
| Remove Existing SCTE-35 packets | For ESNI/ ESAM operations, where SCTE markers are manipulated based on an external decisioning server (POIS server), you can select this option to remove the original inputs SCTE data. The modified SCTE data will be placed where the old data was removed. |
| External ID | The ID that is used when integrating ZEN Master with an external ESNI/ESAM server. The ID is whatever you use in the external system to reference the ZEN Master object, though depending on what you are doing, it might serve different purposes:
* used by POIS to identify the source of SCTE-35 messages
* used by ESNI to identify the audience that is receiving the content
Regardless, the External ID is the same whether entered in the **SCTE-35 Manipulation** settings or the **Advanced** settings, and you cannot enter different values in the two fields. |
| POIS Latency Offset \[ms] | If you would like to offset the POIS modification path to allow for api latency, enter a value in miliseconds. This value can be zero, but it establishes that this output should receive POIS SCTE conditioning. |
| Make Timeline Continuous | Select this option to normalize the timeline, making it continuous. Note that it will add 100ms latency and it creates a variant of the input, which means that it doubles your input. |
| ***Advanced*** | |
| Billing Code | If you would like to track usage for this Target, enter your **Billing Code** details, see [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ) . (Supported for Broadcasters v14.8+) |
| Billing Password | Enter the password that corresponds to this billing code. |
| Billing Channel ID | An optional arbitrary string - you can enter anything you want to for your record-keeping. This is **not** related to ZEN Master Channels. |
| External ID | The ID that is used when integrating ZEN Master with an external ESNI/ESAM server. The ID is whatever you use in the external system to reference the ZEN Master object, though depending on what you are doing, it might serve different purposes:
* used by POIS to identify the source of SCTE-35 messages
* used by ESNI to identify the audience that is receiving the content
Regardless, the External ID is the same whether entered in the **SCTE-35 Manipulation** settings or the **Advanced** settings, and you cannot enter different values in the two fields. |