---
title: Adding RIST Outputs
slug: zixi-broadcaster-zec-current-version/adding-rist-outputs
docTags:
createdAt: 2024-12-26T15:04:53.524Z
---
The RIST output can be push streams or have them pulled to/from a RIST-enabled device. RIST seeks to provide reliable, high-performance media transport by using UDP at the transport layer to avoid the inefficiencies of TCP, then layering on top Forward Error Correction and Retransmits to add the reliability inherently absent from UDP.
Zixi supports the following RIST profiles:
- **Simple Profile** **(PUSH only)** - The RIST Simple Profile provides best-in-class packet protection, as well as support for multi-link bonding and seamless switching.
- **Main Profile (PUSH/PULL) **– The RIST Main Profile builds upon the features of the Simple Profile to provide backwards compatibility, while opening the door for additional features, including:
- **Encryption and authentication** - RIST Main Profile uses industry-standard DTLS or PSK with a variety of available cyphers to ensure the most up-to-date protection, while being flexible to accommodate local legal regulations. Support for pre-shared keys is also included, which makes RIST Main Profile compatible with one-to-many environments such as satellite or multicast distribution.
- **Native tunneling and multiplexing **- the ability to combine multiple Simple Profile RIST streams into one single connection, optionally with one single encryption and authentication step, using industry-standard GRE over UDP.
- **Bandwidth optimization **- by deleting NULL packets at the source and re-inserting them at the destination.
- **Support for high bit rate streams** - The RIST Main Profile includes an RTP header extension which increases the sequence number size to 32 bits, and therefore increases the maximum size of retransmission buffers, and thus opens the door for higher bitrate streams, such as lightly compressed (e.g., JPEG 2000, Tico) and uncompressed video.
Contact your Zixi representative to learn more about interoperability testing between Zixi Broadcaster and 3rd party devices. More details about RIST can be found at [www.rist.tv](http://www.rist.tv/).
## To Create a RIST Output:
::::WorkflowBlock
:::WorkflowBlockItem
In the Zixi Broadcaster **Outputs** page, click **+ New Output**.
The **New output** window is displayed.
:::
:::WorkflowBlockItem
Note that the settings will be different if you select the **Main Profile - **include **Push** and **Pull** options, which also have different settings.
:::
:::WorkflowBlockItem
Select the **RIST** option (radio button).
:::
:::WorkflowBlockItem
Type in the unique identifier for this output in the **Output Name.**
:::
:::WorkflowBlockItem
Select an **Input Stream** to be made available on this output from the adjacent drop-down list.
:::
:::WorkflowBlockItem
Select the Show in Matrix check box to display this stream in the Matrix (see [Using the Matrix](docId\:bP6MO9f2QbxmU6gURKoG4)). Default: Selected.
:::
:::WorkflowBlockItem
Select the **Log this stream** checkbox if you would like to generate event logs for this output.
:::
:::WorkflowBlockItem
Specify the **Output parameters** (see [Output Stream Parameters Table](docId\:c7l7wsvTwzmDl6LrwR_ca) below).
:::
:::WorkflowBlockItem
Click **OK**.
The new RIST Output with its settings is created and now appears on the **Outputs** screen.
:::
::::
### Output Stream Parameters Table
| **Parameter** | **Description** |
| ------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ***Output Parameters*** |
|
| Profile | Select one of the following RIST profiles that matches the input stream:
* Simple Profile (default)
* Main Profile |
| Type (Main Profile) | Select the stream direction:
* Push
* Pull |
| Host | Specify the destination IP address or URL of the host to which the stream will be pushed. |
| Port | Specify the target RIST port. |
| TTL | Specify the time-to-live (TTL). Used mainly to limit the range (or “scope”) of a multicast transmission. Leaving it blank uses the default value specified by the operating system. |
| 204B TS Packet
| Enable this option if the stream has an MPEG-TS that uses 204 bytes packets. This will allow the UDP packets to be aligned with MPEG-TS packets. |
| SSRC
| Enter an SSRC identifier for the RTP session. The SSRC identifier is a
randomly chosen value meant to be globally unique within a particular RTP session. |
| Smoothing \[mms] | Enables transmission of the output at the correct rate. Required when the receiving device is sensitive and can’t lock onto the stream (in such a case, the recommended latency is 100 - 1000 ms). |
| SMPTE-2022 FEC | In the SMPTE-2022 FEC standard, 1-D and 2-D parity codes are systematic FEC codes of decent complexity that provide protection against bursty or random losses.
This setting can be modified without interrupting an existing stream.
To enable SMPTE-2022 FEC (Forward Error Correction) select one of the following parity options from the drop-down menu:
* **1D** - SMPTE-2022 1D can fix a problem in ONE packet per row. This means that the number of rows specified should consider the packet loss rate - the shorter the row, the more error resilience can be achieved at the expense of the bitrate level. However, longer rows increase the delay that the FEC will add. It is recommended to select this option when the packet loss is sporadic. The stream will occupy the source port and two ports above it (e.g., if the source port is 8988, it will occupy 8990).
* **2D **- SMPTE-2022 2D uses a table of packets, which includes rows and columns. This option is more error resilient, but it increases the delay by (row\*column) packets and increases the bitrate with R+C packets per each table of R\*C packets. It is recommended to select this option when packet loss is bursty. The stream will occupy four ports above (e.g., if the source port is 8988, it will occupy 8992). |
| Bind to IP | Select from the drop-down list the local IP address to be used for this Input, OR select *Any *to enable any IP to be used. |
| Local Port | Specify from which local port to source the stream, if desired (instead of randomly chosen by the operating system). |
| ***RIST main profile parameters*** |
|
| Use DTLS | Select this option to connect using DTLS, which offers authentication and encryption. |
| Ignore TLS certificate errors (PUSH) | Select this option when streaming to a trusted server that does not have a valid certificate. When this option is selected, Zixi Broadcaster will ignore the TLS certificate errors and transmit the stream to its destination. |
| User | Enter the authentication credentials |
| Password | Enter the authentication credentials |
| ***Billing Codes***
| |
| Billing Code
| Enter the billing code that corresponds to this stream. The relevant billing can be obtained from the organization that received the billing code from Zixi. |
| Billing password
| Enter the password that corresponds to this billing code. |
| ***Remultiplex/Pad*** | Select this checkbox to enable remuxing from VBR MPEG-TS to MPEG-TS CBR (used for professional IRDs) or padding with null packets. |
| Mode | Select one of the following:
* Pad – adds NULL packets and adjusts the stream clock (PCR) in order to make the stream CBR.
* Remultiplex - performs demux->mux and rebuilds the stream according to the parameters below. |
| Target bitrate \[kbps] | Specify the CBR bitrate to target for the padded stream (Pad) or a re-multiplexed stream (remultiplex). |
| PCR interval \[ms] | Specify the frequency at which Program Clock Reference is inserted into the outputs Transport stream in milliseconds (default - 90). |
| Buffer size \[ms]
| Specify the size of the buffer that will be used for the remixing. A larger buffer increases the quality, but also increases latency. |
| No NULL packets
| Select this option to re-multiplex the stream to CBR but remove the NULL packets in order to maintain a low bitrate. |
| **Enable Decryption** | Select this checkbox to decrypt an encrypted stream. |
| Decryption type | If the stream has been encrypted, you can decrypt it through the output by selecting this checkbox and specifying the type of encryption that was used.
Select **Automatic** to decrypt a stream that has been encrypted using **Automatic** encryption.
Only if the stream has not been encrypted, select **None** (default).
***Important Notice: if the stream has been encrypted, you must decrypt it in the output.*** |
| Decryption key | If the decryption type includes a key, enter the key to decrypt the stream during output. |
## Advanced Mode
The fields discussed below are optional and available only in **Advanced Mode**.
To enter Advanced Mode add the URL parameter `?advanced=1` to the Zixi Broadcaster URL in your browser and press Enter/Return to reload the page:
::Image[]{src="https://api.archbee.com/api/optimize/amUtKWPrNQCS-26DKyGuI-5OBE4QsRN0icABdoD4ciK-20250421-173825.png" size="70" width="800" height="55" position="center" alt="Advanced Mode URL Param" darkWidth="800" darkHeight="55" showCaption="false"}
:::hint{type="info"}
Note the Advanced Mode settings are generally intended for advanced users and special cases. If you do not understand the settings, you should probably accept the default values.
:::
### General
- **Latency offset \[ms]** - Specify the additional buffering time in milliseconds. Increasing this value can improve stream stability in unstable network conditions, but will increase end-to-end delay. Default: 0 ms
### Output Parameters
- DSCP - Specify the Differentiated Services Code Point (DSCP) value for the stream. This 6-bit value (ranging from 0 to 63) is embedded within the IP header of the network packets to classify the traffic type and define its priority level across the network routing infrastructure.
- **ECN** - Explicit Congestion Notification (ECN) lets a congested router mark a packet to signal congestion rather than dropping it. The sender declares "I understand ECN" by marking its packets as ECN-capable; a congested router along the path can then flip the bits to signal congestion without packet loss. Note that this is only a request that depends on all devices downstream being ECN-capable. In most cases, enabling ARQ and FEC is a more reliable way of ensuring video delivery on congested networks. Options are:
- Non-ECT - ECN is disabled. If the network gets congested, the router will drop packets.
- ECT0 - Indicates to network routers that the sending and receiving devices support ECN. If congestion occurs, routers will mark the packets rather than drop them.
- ECT1 - Functions identically to ECT0. It is an alternative code indicating the same ECN-capable status to the network routers.
- **Bind to NIC** - Select from the drop-down list the CIDR that represents the IP range where the desired NIC is accessed.
- **Traffic Shaping \[kbps]** - Specify a value in kbps to use the **Traffic shaping **network management technique to control and optimize the flow of data.
- **Don't fragment** - Sets the IP "Don't Fragment" bit on outgoing packets, preventing routers from fragmenting them in transit. Packets exceeding the path MTU are dropped rather than fragmented. This is useful to guarantee packet integrity on networks where fragmentation causes issues.
- **Max packet payload** - Maximum UDP payload size in bytes. When set (>0), the Broadcaster aggregates multiple TS packets into a single UDP datagram up to this size, reducing packet rate/overhead. Set to 0 for default behavior (no aggregation). Note: enabling this also implies **Don't Fragment**.
- **Buffer fill time \[ms]** - Only relevant when **Max packet payload** is set. The maximum time to wait for a packet to fill up before sending it partially full. Caps the latency added by packet aggregation (default 5 ms for push outputs).
### Remultiplex/Pad
- **Restamp DTS** -
### Enable IFB/Talkback
- **Port** - Specify the port to listen on. This port must be open on all firewalls between the Zixi Broadcaster and other devices it is communicating with.