--- title: Adding RIST Targets slug: zen-master/adding-rist-targets docTags: createdAt: 2024-12-27T19:19:13.106Z --- ZEN Master enables you to create a RIST output on a Broadcaster or MediaConnect Flow. You can configure redundant 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 a RIST Target in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. ## To add a new RIST 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 **RIST**. The **Create New RIST Target** window is displayed. ::Image[]{src="https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/4BJ2xGvhk1mvSNrZT5unE-20251103-192725.png" size="82" width="1372" height="2977" position="center" alt="New RIST Target" darkWidth="1372" darkHeight="2977" showCaption="false"} ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, enter a logical name for the RIST 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 *MediaConnect Flow*. ::: ::::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 Under **Profile**, select the RIST profile to be used. Options are *Simple* or *Main*. ::: :::WorkflowBlockItem In the **Host/IP **field, enter the hostname or IP address of the Broadcaster or MediaConenct Flow. ::: :::WorkflowBlockItem In the **Port** field, enter the Target port on the receiving device. ::: :::WorkflowBlockItem In the **Bind to local NIC by CIDR **field**, **enter the CIDR that represents the IP range where the desired NIC is accessed. ::: :::WorkflowBlockItem Select the **DTLS** checkbox if you would like to encrypt the stream dynamically using DTLS. (This option is only available if you are using Main profile. This feature is only supported for Broadcasters running v12.2+.) ::: :::WorkflowBlockItem In the **SMPTE 2022 FEC** section, select the desired error correction method. Options are: *Disabled (default), 1D or 2D.* ::: :::WorkflowBlockItem If you selected *1D *or *2D* for the FEC, then fill in the desired number of rows and columns. *Default values: 10x10*. ::: :::WorkflowBlockItem In the **Remux Bitrate** field, enter the desired bitrate (in kbps). ::: :::WorkflowBlockItem Under **Remux mode**, select one of the following: - **Pad** - in the Padding mode a VBR stream is turned into a CBR stream in a non-transformational way, by adding null packets and adding some minor PCR corrections. This mode is used when the stream is compliant with broadcast quality but needs minor PCR correction and padding to make it CBR. - **Remux** - Remux mode is transformational and is used to try to fix streams that are typically non-compliant with broadcast quality IRD’s, often originating at consumer-level software encoders or other misconfigured/non-compliant encoding sources. The system unpacks the original TS, separates the audio and video, assembles the frames and then re-packages them. As part of this process the PIDs may be changed and a new PCR clock may be created. This mode assumes that the stream includes a single audio and video source. ::: :::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. :::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. ![SCTE-35 Settings](https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/u_kJpVt3DRHk78LSBYop7-20260326-183853.png) ::: :::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 **Parameters Table** below for explanations of the fields. ![](https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/tUAVNDF4d8R5BLsd_KhT2_rist-target-advanced.png) ::: :::WorkflowBlockItem Click **Save**. ::: ::::: ## RIST Target Configuration Parameters Table | **Parameter** | **Description** | | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the Zixi Pull 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 | Verify that **ZEN Master Channel** is selected (default). | | 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** – 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.
**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. | | Profile | Select the RIST profile to be used. Options are *Simple* or *Main*. | | Host/IP | Enter the hostname or IP address of the Broadcaster or MediaConenct Flow. | | Port | Enter the Target port on the receiving device. | | Bind to local NIC by CIDR
| Enter the CIDR that represents the IP range where the desired NIC is accessed. | | DTLS (for Main) | Select this checkbox if you would like to encrypt the stream dynamically using DTLS. (This feature is only supported for Broadcasters running v12.2+.) | | SMPTE 2022 CEF | Select the desired error correction method. Options are: *Disabled (default), 1D or 2D.*
If you selected *1D *or *2D* for the FEC, then fill in the desired number of rows and columns. *Default values: 10x10*. | | Remux Bitrate \[kbps] | Specify the desired bitrate (in kbps). | | Remux mode | Select one of the following:
* **Pad** - in the Padding mode a VBR stream is turned into a CBR stream in a non-transformational way, by adding null packets and adding some minor PCR corrections. This mode is used when the stream is compliant with broadcast quality but needs minor PCR correction and padding to make it CBR. * **Remux** - Remux mode is transformational and is used to try to fix streams that are typically non-compliant with broadcast quality IRD’s, often originating at consumer-level software encoders or other misconfigured/non-compliant encoding sources. The system unpacks the original TS, separates the audio and video, assembles the frames and then re-packages them. As part of this process the PIDs may be changed and a new PCR clock may be created. This mode assumes that the stream includes a single audio and video source. | | 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.
**Note: in Broadcasters prior to v19, if the value is set to anything other than 0, the search window will be 2 seconds.** | | SCTE-35 PID | Specify a specific PID number for SCTE-35 insertion | | Remove Existing SCTE-35 | If you wish to override any existing SCTE-35 messages with your own, you can elect to have existing ones 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. | | MTU | If you would like to configure the **Maximum Transmission Unit** (largest data packet that a network-connected device will accept) for the pulling of the stream, enter the MTU in bytes in the **MTU** field. | | External ID | The ID that is used when integrating ZEN Master with an external ESNI/ESAM server. For more detail, contact your Zixi representative. |