This enables the Broadcaster to receive a RIST stream. 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 Broadcaster supports RIST streams from any compliant RIST device.
...
| Parameter | Description |
|---|---|
| Stream parameters | |
| Profile | Select one of the following RIST profiles that matches the input stream:
|
| Simple Profile Parameters | |
| Local 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. |
| Multicast IP | If multicast, type the Multicast IP address (or leave blank in the case of Unicast). |
| SSM Source IP | Specify the source IP for a source-specific multicast. |
| Remote Port | Specify the remote port in the source RIST device. Default: 0 (any port) |
| Type | Select one of the following protocol types from the drop-down list:
|
| 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. |
| Max. bitrate [kbps] | Specify the maximum expected bitrate for memory allocation. Recommended: 2X the actual bitrate, which will prevent buffer overruns (especially with VBR streams). Default: 8000. Note – Overflows will typically occur when the Max Bitrate isn’t sufficient. |
| Max Latency [ms] | Specify the maximum latency of the stream in milliseconds. Default: 1000 |
| Keep RTP Headers | Selecting this checkbox will keep the RTP headers of the input. Keeping the input's RTP headers will propagate RTP headers to later processing steps, including failover groups and outputs (relevant for RTP inputs only). When used together with failover group – enabling this option enables using SMPTE 2022-2 FEC and 2022-7 hitless failover together. The failover group will use 2022-7 and will merge streams based on sequence in the RTP header, and not on content with DNA matching. When creating the Failover Group select the Keep RTP Headers again (in the failover group screen) to keep the RTP headers after the merge. If it is not selected, Zixi will merge based on the headers (using SMTE 2022-7), but then drop the headers thereafter. Combining Keep RTP Headers with Outputs:
|
| Main Profile – Push Parameters | |
| Local 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. |
| Multicast IP | If multicast, type the Multicast IP address (or leave blank in the case of Unicast). |
| SSM Source IP | Specify the source IP for a source-specific multicast. |
| Remote Port | Specify the remote port in the source RIST device. Default: 0 (any port) |
| Type | Select one of the following protocol types from the drop-down list:
|
| 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. |
| Max. bitrate [kbps] | Specify the maximum expected bitrate for memory allocation. Recommended: 2X the actual bitrate, which will prevent buffer overruns (especially with VBR streams). Default: 8000. Note – Overflows will typically occur when the Max Bitrate isn’t sufficient. |
| Max Latency [ms] | Specify the maximum latency of the stream in milliseconds. Default: 1000 |
| Use DTLS | Select this checkbox to encrypt the stream dynamically using DTLS and specify the User and Password. |
| Keep RTP Headers | Selecting this checkbox will keep the RTP headers of the input. Keeping the input's RTP headers will propagate RTP headers to later processing steps, including failover groups and outputs (relevant for RTP inputs only). When used together with failover group – enabling this option enables using SMPTE 2022-2 FEC and 2022-7 hitless failover together. The failover group will use 2022-7 and will merge streams based on sequence in the RTP header, and not on content with DNA matching. When creating the Failover Group select the Keep RTP Headers again (in the failover group screen) to keep the RTP headers after the merge. If it is not selected, Zixi will merge based on the headers (using SMTE 2022-7), but then drop the headers thereafter. Combining Keep RTP Headers with Outputs:
|
| Main Profile – Pull Parameters | |
| Remote Host | Specify the IP Address of the remote RIST device from which the stream will be pulled. |
| Remote Port | Specify the port of the remote RIST device from which the stream will be pulled. Default: 0 (any port) |
| Local Port | Specify the local port to which the stream will be pulled. Default: 0 (any port) |
| Type | Select one of the following protocol types from the drop-down list:
|
| 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. |
| Max. bitrate [kbps] | Specify the maximum expected bitrate for memory allocation. Recommended: 2X the actual bitrate, which will prevent buffer overruns (especially with VBR streams). Default: 8000. Note – Overflows will typically occur when the Max Bitrate isn’t sufficient. |
| Max Latency [ms] | Specify the maximum latency of the stream in milliseconds. Default: 1000. |
| Use DTLS | Select this checkbox to encrypt the stream dynamically using DTLS and specify the User and Password. |
Ignore TLS certificate errors | When this option is selected, Zixi Broadcaster will ignore the TLS certificate errors and transmit the stream to its destination. |
| Keep RTP Headers | Selecting this checkbox will keep the RTP headers of the input. Keeping the input's RTP headers will propagate RTP headers to later processing steps, including failover groups and outputs (relevant for RTP inputs only). When used together with failover group – enabling this option enables using SMPTE 2022-2 FEC and 2022-7 hitless failover together. The failover group will use 2022-7 and will merge streams based on sequence in the RTP header, and not on content with DNA matching. When creating the Failover Group select the Keep RTP Headers again (in the failover group screen) to keep the RTP headers after the merge. If it is not selected, Zixi will merge based on the headers (using SMTE 2022-7), but then drop the headers thereafter. Combining Keep RTP Headers with Outputs:
|
| Billing Codes | Billing codes are used to identify and differentiate traffic on a Zixi Broadcaster for billing purposes. When a billing code is added to a Source or Target, Zixi can track the traffic on that Broadcaster input or output separately from other inputs and outputs on the same Broadcaster. Billing codes are created by Zixi personnel on the Zixi Customer Portal for a particular organization. |
| 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. |
| Enable time shift | Select this checkbox to record the stream content and broadcast it after a specified delay. To deploy an input stream that uses the current stream's time shift, you need to configure a "Delayed" input stream. (See Adding Delayed Streams). |
Maximum delay [hh:mm:ss] (for Time Shift enabled) | Specify the maximum time delay of this input. |
Enable multicast on pull outputs | Select this checkbox to enable the transmission of this stream’s outputs as multicast. A Zixi receiver that will pull the stream will receive it in multicast. By default Zixi Broadcaster is configured to allow transparent fallback to unicast if it is out of the LAN. Requires enabling Multicast Pull in the Settings. |
Multicast-Only (for multicast enabled) | Selecting this checkbox will force the transmission of this stream only in multicast. |
Enable Encryption | Select this checkbox to encrypt the Input stream. For more information, see Encrypting an Input Stream in Zixi Broadcaster. |
Encryption type (for Encryption enabled) | Specify the type of Encryption (AES 128/192/256). |
Encryption key (for Encryption enabled) | Click Generate to generate an encryption key. The generated encryption key must be sent to the end-user to decipher the received encoded stream. |
Recording parameters | Select this checkbox to customize the recording parameters. |
Destination Type | Select the radio button for the desired storage type and then fill in the relevant parameters.
|
Record to Disk Parameters | |
File Name Template | Specify the file name pattern that Zixi will use to generate when saving the recorded content. A separate file will be generated for each recording up to the time specified in the Max recorded file duration parameter (see above). After this duration a new file will be generated. The file name pattern can include any string and up to five variables listed below. Only the %T=HH.MM.SS creation time is mandatory. You can change the order of these variables and add text as long as you maintain the legitimate structure of the file in Linux and Windows:
For example, the following pattern %Y_recording%T.ts will generate the following file name 2017_recording15:32:35.ts. |
Max recorded file duration [hours] | Specify the maximum time allotted for recording a video stream. Default: 2 hours |
Keep recorded files for [hours] | Specify the maximum time for storing the recording. Default: 0 hours |
Custom Path | Optionally specify a storage location for the recorded files that is relative to the root folder. This location bypasses the location specified as the root folder in the Settings > General screen. |
Record to S3 Parameters | |
File Name Template | Specify the file name pattern that Zixi will use to generate when saving the recorded content. A separate file will be generated for each recording up to the time specified in the Max recorded file duration parameter (see above). After this duration a new file will be generated. The file name pattern can include any string and up to five variables listed below. Only the %T=HH.MM.SS creation time is mandatory. You can change the order of these variables and add text as long as you maintain the legitimate structure of the file in Linux and Windows:
For example, the following pattern %Y_recording%T.ts will generate the following file name 2017_recording15:32:35.ts. |
Max recorded file duration [hours] | Specify the maximum time allotted for recording a video stream. Default: 2 hours |
URL | Specify the URL of the S3 bucket. |
Ignore TLS certificate errors | TLS certificate for S3 bucket might be detected as faulty if bucket name contains dot[s]. When this option is selected, Zixi Broadcaster will ignore the TLS certificate errors and transmit the stream to its destination. |
Access Key | The access key that is used for accessing the S3 bucket. |
Secret Key | The secret key that is used for accessing the S3 bucket. |
...