---
title: Adding a Zixi Source – Broadcaster Push
slug: zen-master/adding-a-zixi-source-broadcaster-push
docTags:
createdAt: 2024-12-27T16:33:35.726Z
---
## Adding a Zixi Source – Broadcaster Push
You can add an input from a Zixi Broadcaster to a Broadcaster cluster to be managed as a source in ZEN. This is done by selecting **Zixi** in the New Source menu. You can use either ***Push*** or ***Pull*** method to send the Source from the Broadcaster. In this case, the Broadcaster is referred to as the **Origin Broadcaster** which streams to the **Ingest Broadcaster**.
- **Network bonding - **When configuring a Source using a Push stream from a Zixi Broadcaster you can apply *Network Bonding* to the stream. This divides the stream into several network channels using multiple NICs and subsequently reunites them at the Ingest Cluster. When using Network Bonding, you need to specify which NICs will be used for this Source.
- **Multiple inputs -** You can select several inputs from a single Broadcaster to simultaneously create a new Source in ZEN Master for each input, by selecting the **Create multiple Sources from multiple Inputs** option.
The following procedure describes how to add a Zixi Broadcaster in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below.
Also see [Adding a Zixi Source – Broadcaster Pull](docId\:nQWathihsJwRWFWlB1086)
### To add a Broadcaster Push Source:
:::::WorkflowBlock
:::WorkflowBlockItem
In the main navigation, click **Sources**.
:::
:::WorkflowBlockItem
Click **+ Add**.
The **Create New Source selection** window is displayed.
:::
:::WorkflowBlockItem
Click on **Zixi**.
The **Create Zixi Source** window opens.
:::
:::WorkflowBlockItem
Be sure to set the **Mode** to **Push** and the **Application** to **Broadcaster** to get the correct fields.
:::
:::WorkflowBlockItem
In the **Info** section, in the **Name** field, type a logical name for the Zixi source.
:::
:::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 Source 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 Source. 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 Source'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 Source's IP. If you would like to manually set the location of the Source (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 **Broadcaster** field, select from the drop-down list one of the available Broadcasters.
:::
:::WorkflowBlockItem
If you would like to create a Source from a single input, then in the **Broadcaster Input** field, select the desired input from the drop-down list of available inputs.
:::
::::WorkflowBlockItem
If you would like to create Sources from multiple inputs, select the **Create Sources from Multiple Inputs **checkbox.
:::hint{type="info"}
- When you select this option, each input that is selected creates a separate Source in ZEN Master. Each Source is named independently in the Broadcaster Inputs section and the Name field in the Info section is disabled.
- You can create up to 25 Sources at once.
:::
A list of available Inputs on that Broadcaster is displayed. Take the following steps:
- Select one or more Inputs by clicking the **+** button for the desired input.
::Image[]{src="https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/dM6xcJa0t0ZPXDh0Fbzsb_image.png" size="90" width="801" height="382" position="center" alt="Broadcaster Inputs" darkWidth="801" darkHeight="382" showCaption="false"}
- Selected Inputs are shown above the Filter box. (You can remove an Input by clicking the **-** button for that Input).
- For each input that is selected you can edit the name of the Source in the **Name** field. Default: the name of the input on the Broadcaster.
If you would like the output configured in ZEN Master to replace any current outputs configured on the Broadcaster, select the **Replace existing manual outputs** for selected inputs.
::::
:::WorkflowBlockItem
If you want the Source to be sent over a single NIC (i.e. no bonding) then do the following:
1. Do not select the **Bonding **checkbox.
2. In the **Broadcaster Output NICs** field, if you would like to specify which NIC is used, then select the IP of that NIC from the drop-down list. By default, *Any* is selected.
:::
::::WorkflowBlockItem
If you would like to use Bonding, then do the following:
- Select the **Bonding** checkbox.
- Select two or more NICs by clicking the **+** button for each of the desired NICs.
- Selected NICs are shown above the **Filter** box. (You can remove a NIC by clicking the **-** button for that NIC).
- For each NIC that is selected you can adjust the following parameters:
- In the **Max Bitrate **field, enter the maximum bitrate to be used on this NIC.
- If you want to use this NIC only when there isn’t sufficient bandwidth available on the other NICs, then select the **Backup **checkbox.
:::hint{type="info"}
If the **Backup** checkbox is not selected then this NIC is used in parallel with the other selected NICs.
:::
::::
::::WorkflowBlockItem
If you selected **Pull** Method, then use the following procedure to configure the input:
- In the **Host** field, enter the IP address of the Broadcaster from which the stream is being pulled.
- In the **Port** field, enter the port through which the Broadcaster receives the stream from another Broadcaster server. Default: 2088
:::hint{type="info"}
The default input port for Zixi Broadcaster is UDP port 2088. This port must be open on any firewalls between Zixi Broadcaster and other devices it is communicating with.
:::
- In the **Stream ID** field, enter the precise Stream ID (case sensitive) assigned to this stream on the input broadcaster.
- If you are using a password for this stream, in the **Password** field, enter the string for authentication. It must be identical to the string configured on the input broadcaster.
::::
:::WorkflowBlockItem
In the **Configuration** section, check the **Use Private IPs** checkbox if you want to use private IP addresses.
:::
:::WorkflowBlockItem
in the **Ingest Cluster** field, select from the drop-down list one of the available Ingest Clusters as the destination for the Source.
:::
::::WorkflowBlockItem
In the **Target Broadcaster/s** field, select your broadcaster preferences. Either select a specific broadcaster to be used OR specify your preference for using primary vs. backup broadcasters, options are: Prefer Primary Broadcasters, Primary Broadcasters only, Backup Broadcasters only or Prefer Backup Broadcasters.
:::hint{type="info"}
For managed clusters, it is not recommended to select a specific broadcaster, as the broadcaster’s availability may not remain stable.
:::
::::
:::WorkflowBlockItem
In the **Latency \[ms]** field, select the latency time for the stream (default 4000).
:::
:::WorkflowBlockItem
If you would like to enable the Zixi auto encryption feature for encrypting the source stream, select the **Enable Encryption **checkbox.
:::
:::WorkflowBlockItem
For Push inputs, if you would like to set a password to authenticate the stream from the input broadcaster, in the **Source Password** field, enter a password or generate a random password by clicking on **Random.** You need to enter the identical password (case sensitive) on the input broadcaster.
:::
::::WorkflowBlockItem
If you would like to apply a PID Mapping profile to this Source, then in the **PID Mapping Profile** field, select the desired profile from the dropdown list.
:::hint{type="info"}
Using this method creates a single Source in ZEN Master with PID Mapping applied. If you would like to maintain a Source with the original PIDs and create an additional Source with PID Mapping (e.g. if you want to create several different PID Mapped variations), then use the method described in [Adding a Source - PID Mapping](docId\:goCKL3uPsD8V14Ia2an6g).
To create a new PID Mapping Profile, see [PID Mapping Profiles](docId\:OFVPYMHYVq4XqhIi3UMnS).
:::
::::
:::WorkflowBlockItem
If you would like to generate email notifications whenever a PID change is detected, select the **Alert on PID changes **checkbox.
:::
:::WorkflowBlockItem
Check the **Minimize Latency** checkbox to enable **Dynamic Latency** (see [Latency Considerations](docId\:TVGsP9rBQsk-c0PWvqq9b) for more information about Dynamic Latency).
:::
::::WorkflowBlockItem
Select the **Log SCTE-35** checkbox if you would like to log SCTE-35 markers for this stream.
:::hint{type="info"}
- To log SCTE-35 markers, SCTE-35 needs to be enabled both on the Ingest Cluster and on the Source configuration.
- SCTE-35 logging is only available for v13.1.40262+ Broadcasters.
:::
::::
:::WorkflowBlockItem
If **Log SCTE-35** was selected, you can choose to receive alerts for SCTE-35 markers by selecting the **Enable SCTE-35 alerts** checkbox.
:::
:::WorkflowBlockItem
In the **Public Output** field, if you would like to allow access to the stream directly through a supported player, select the **Allow** checkbox.
:::
:::WorkflowBlockItem
If you selected the **Allow** checkbox, then enter a password in the **Password **field to authenticate access to the stream.
:::
::::WorkflowBlockItem
Under **Content Analysis **select one of the following options:
- **Full **- select this option if you would like to enable full Content Analysis (CQA), including analysis of the stream's audio and video content, including audio levels, audio silence detection, frozen video detection, and more.
- **TR101 Only** - select this option to perform TR101 analysis only (without video and audio content analysis). The analysis can be used to check the integrity of the TS and the most important elements of the stream. The analysis includes priority 1 and 2. To learn more about TR101 analysis see [TR 101 290 Technical Report](https://www.etsi.org/deliver/etsi_tr/101200_101299/101290/01.03.01_60/tr_101290v010301p.pdf).
- **None **- no content analysis is enabled.
:::hint{type="info"}
It is generally recommended to enable full Content Analysis unless it is causing technical problems. If Content Analysis is disabled, the system won't detect errors in the video and audio content of the stream and won't generate warnings for such events.
:::
::::
::::WorkflowBlockItem
If you would like to monitor CEA-608 and/or CEA-708 closed captions, select the **Monitor CEA-608 **and/or** CEA-708 **checkbox**.**
:::hint{type="info"}
Note: Broadcaster versions earlier than v18 will not distinguish between 608 and 708 captions.
:::
::::
::::WorkflowBlockItem
If you would like to disable auto-pull, select the **Disable Auto-Pul**l checkbox.
:::hint{type="info"}
Disabling Auto-Pull will lock Channels using this Source to the Source's Ingest Cluster and Targets to the Source's current active Broadcaster. This setting only applies to Pass-Through Channels.
:::
::::
:::WorkflowBlockItem
If Auto-Pull is *enabled*, in the **Auto-Pull Latency \[ms]** field, specify the maximum latency for auto-pull actions. The Broadcaster will update the latency as required, by using the maximal defined latency and then reducing the latency gradually. (Default: 1000 ms)
:::
:::WorkflowBlockItem
If *Pull* was selected in *step 7 *and the Source is using AES encryption, in the **Decryption Key** field, enter the static key that was used for encryption.
:::
::::WorkflowBlockItem
In the **WebRTC Playback** section, select the desired playback method.
:::hint{type="info"}
WebRTC enables you to monitor the stream via web browsers and mobile applications with real-time communication (RTC). WebRTC needs to be activated independently for each Source in ZEN Master (by default it is disabled).
:::
Select one of the following options:
- **Disabled **- users will not be able to view this Source using WebRTC (default)
- **Pass-Through** - passes the stream through to WebRTC without transcoding. This option *can only be used *if the input stream is already in a WebRTC compliant format (video - H.264 codec with *Baseline *or *Main *profile and no B frames, Audio - Opus codec).
- **Auto **- ZEN Master automatically transcodes the stream using the optimal profile for each specific user. In this option Zixi Broadcaster will decode the video, transforming it into RAW frames, which will be passed to the WebRTC library, where it will be re-encoded for each individual user.
:::hint{type="info"}
Best quality. However, if monitored by multiple users this can consume extensive resources.
:::
- **1080p/720p/480p/360p** - ZEN Master transcodes the stream to a WebRTC compliant profile with the specified resolution. The transcoding is done by Zixi Broadcaster's transcoder.
:::hint{type="info"}
This method requires a Zixi Broadcaster with X264 or Nvidia for transcoding. This method allows many users to monitor the stream without encoding separately for each individual user, which saves CPU capacity. Since there is only one stream version, it is recommended to encode to a low resolution and low bitrate so that the stream will be viewable by all users monitoring the stream.
:::
::::
:::WorkflowBlockItem
In the **Initial State** section, select the **Disabled** checkbox if you would like to disable this Source upon initial configuration.
:::
::::WorkflowBlockItem
Select the **Muted** checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration.
:::hint{type="info"}
You can Enable/Unmute the Source at any time.
:::
::::
:::WorkflowBlockItem
If you would like to adjust the advanced settings, click **Advanced**.
The **Advanced** settings fields are displayed.
:::
::::WorkflowBlockItem
If you would like to track usage for this Source, enter your **Billing Code** details. See [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ).
:::hint{type="warning"}
Note that billing codes are **not** supported for **Push Sources** until Broadcaster **v19+**.
:::
::::
:::WorkflowBlockItem
If you would like to track auto-pull usage separately, enter you **Auto-Pull Billing Code** details.
:::
:::WorkflowBlockItem
For either or both billing codes, click the **Validate billing code button** to verify that the code is valid.
:::
:::WorkflowBlockItem
**Traffic shaping** is a network management technique used to control and optimize the flow of data. Check the box to enable it (this setting will be ignored for Broadcasters earlier than v18.2).
:::
:::WorkflowBlockItem
**FEC **(Forward Error Correction) helps to fix transmission problems by sending redundant data that will allow reconstruction of lost packets instantly. By default the redundant data is limited to 30% of the actual data stream, but you can set the percentage to a lower value (this setting will be ignored for Broadcasters earlier than v18.2).
:::
::::WorkflowBlockItem
**Adaptive FEC** improves the efficiency of FEC by adjusting the amount of extra data sent according to network conditions. By default Adaptive FEC is turned on, but there are some cases where fixed FEC is needed and you will want to disable it.
:::hint{type="warning"}
Note that if the you disable Adaptive FEC and later disable and reenable the source, Adaptive FEC will be turned on again, and you will need to edit the source and disable it again.
:::
::::
:::WorkflowBlockItem
**Frame Thinning** allows non-critical frames to be dropped to reduce latency - check the box to enable it. **Note:** this option is available for Push sources only coming for Broadcaster 18.2 or later.
:::
:::WorkflowBlockItem
In the **Auto Pull MTU** field, specify the maximum transmission unit (largest data packet that a network-connected device will accept) in bytes for the Auto Pull.
:::
:::WorkflowBlockItem
To set the detection of frozen video, in the **Frozen Video Minimal Duration** field, specify the default minimal duration in seconds of frozen video after which the Broadcaster will trigger a Frozen video alert. Default: 10 seconds. This setting is supported for Broadcaster version 16.3 and higher.
:::
:::WorkflowBlockItem
To set the detection of blank video, in the **Blank Video Minimal Duration** field, specify the default minimal duration in seconds of blank video after which the Broadcaster will trigger a Blank video alert. Default: 10 seconds. This setting is supported for Broadcaster version 16.3 and higher.
:::
:::WorkflowBlockItem
See the **Parameters Table** below for additional advanced fields.
:::
:::WorkflowBlockItem
Click **Save**.
:::
:::::
### Zixi Broadcaster Source Configuration Parameters Table
| **Parameter** | **Description** |
| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| ***Info*** | |
| Name | Specify a name for the Zixi Source 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 an Tag, you are relating this Source 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 Source. 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 Source'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 Source'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. |
| ***Input*** | |
| Mode | To create a Zixi Broadcaster Source, select the mode used for sending the Source. Options are: *Push* or *Pull*. |
| Application | To create a Zixi Broadcaster Source, select the **Broadcaster** radio button. |
| ***For Push Mode*** | |
| Broadcaster | Select from the drop-down list the desired Broadcaster. |
| Create multiple Sources from multiple Inputs | If you would like to create Sources from multiple inputs, select this checkbox.
When you select this option, each input that is selected creates a separate Source in ZEN Master. Each Source is named independently in the Feeder Inputs section and the Name field in the Info section is disabled.
Note: You can create up to 25 Sources at once. |
| Broadcaster Input | Select from the list one or more of the Inputs that are available on the selected Broadcaster.
For multiple Inputs, click on the **+** button for each of the desired Inputs.
Selected Inputs are shown above the Filter box. (You can remove an Input by clicking the **-** button for that Input).
For each input that is selected you can adjust the following parameters:
* In the **Name **field, edit the name of the Source. Default: the name of the input on the Broadcaster.
* In the **Max Bitrate** field, select from the drop-down list the maximum bitrate for this Source.
Make sure that the value is greater than the max bitrate of the input. The default is set automatically based on the current bitrate of the input. |
| Replace existing manual outputs | If you would like the Source configured in ZEN Master to replace (i.e. stop) any current Outputs configured on the Broadcaster, select this checkbox. |
| Bonding | Select the checkbox if you would like to use bonding. |
| Broadcaster Output NIC/s | If you would like to specify which NIC is used, then select the IP of that NIC from the drop-down list. By default, *Any* is selected.
If you selected the Bonding checkbox, then click the **+** button for each of the NICs that you would like to use.
Selected NICs are shown above the Filter box. (You can remove a NIC by clicking the **-** button for that NIC).
For each selected NIC, you can adjust the following parameters:
* In the **Max Bitrate** field, enter the maximum bitrate to be used on this NIC.
* If you want to use this NIC only when there isn’t sufficient bandwidth available on the other NICs, then select the **Backup** checkbox.
If the **Backup** checkbox is not selected then this NIC is used in parallel with the other selected NICs. |
| ***Configuration*** | |
| Ingest Cluster | Select from the drop-down list one of the available Ingest Clusters as the destination for the Source. |
| Target Broadcaster/s | Specify which Broadcaster/s within the cluster on which ZEN Master can deploy the source. Either select a specific Broadcaster to be used OR specify your preference for using primary vs. backup Broadcasters. Options are: *Prefer primary Broadcasters, Primary Broadcasters only*,* Backup Broadcasters only *or* Prefer Backup Broadcasters.*
Note: For managed clusters, it is not recommended to select a specific Broadcaster, as the Broadcaster’s availability may not remain stable. |
| Input NIC (Pull) | If you would like to specify which NIC is used, then select the IP of that NIC from the drop-down list. By default, *Any *is selected.
|
| Latency \[ms] | Select the latency time for the stream (default 4000). |
| Enable Encryption | If you would like to enable the Zixi auto encryption feature for encrypting the Source stream, select this checkbox. |
| PID Mapping
(Optional) | If you would like to apply a PID Mapping profile to this Source, then select the desired profile from the dropdown list.
To create a new PID Mapping Profile, see [Adding PID Mapping Profiles](docId\:gFTCaYurPL7DInoUyd14z).
Note: Using this method creates a single Source in ZEN Master with PID Mapping applied. If you would like to maintain a Source with the original PIDs and create an additional Source with PID Mapping (e.g. if you want to create several different PID Mapped variations), then use the method described in [Adding a Source - PID Mapping](docId\:goCKL3uPsD8V14Ia2an6g) . |
| Alert on PID changes | If you would like to generate email notifications whenever a PID change is detected, select this checkbox. |
| Minimize Latency | Let Zixi adjust latency dynamically to optimize it for network conditions - see [Latency Considerations](docId\:TVGsP9rBQsk-c0PWvqq9b) for more information. |
| Log SCTE-35 | Select this checkbox if you would like to log SCTE-35 markers for this stream.
Note: To log SCTE-35 markers, SCTE-35 needs to be enabled both on the Ingest Cluster and in the Source configuration.
Note: SCTE-35 logging is only available for v13.1.40262+ Broadcasters. |
| Enable SCTE-35 alerts (for Log SCTE-35) | If you would like to receive alerts for SCTE-35 markers, select this checkbox. |
| Public Output | If you would like to allow access to the stream directly through a supported player, select the **Allow** checkbox. |
| Password (for Public Output) | If you selected **Allow** in the *Public Output* field, specify a password in this field to authenticate access to the stream. |
| Content Analysis | Select one of the following options:
* **Full **- select this option if you would like to enable full Content Analysis (CQA), including analysis of the stream's audio and video content, including audio levels, audio silence detection, frozen video detection, and more.
* **TR101 Only** - select this option to perform TR101 analysis only (without video and audio content analysis). The analysis can be used to check the integrity of the TS and the most important elements of the stream. The analysis includes priority 1 and 2. To learn more about TR101 analysis see TR 101 290 Technical Report.
* **None** - no content analysis is enabled.
**Note:** It is generally recommended to enable full Content Analysis unless it is causing technical problems. If Content Analysis is disabled, the system won't detect errors in the video and audio content of the stream and won't generate warnings for such events. |
| Hide Thumbnail | Select this option to hide the Source's thumbnail from where it is displayed (e.g., the Preview Pane, Grids, etc.). |
| Monitor CEA-608/CEA-708 Closed Captions | If you would like to monitor CEA-608/CEA-708 closed captions, select this checkbox.
Note: Monitoring CEA-608/CEA-708 Closed Captions requires using a version 14.4 or newer Broadcaster. |
| Monitor CEA-608/CEA-708 Closed Captions | If you would like to monitor CEA-608/CEA-708 closed captions, select this checkbox.
Note: Monitoring CEA-608/CEA-708 Closed Captions requires using a version 14.4 or newer Broadcaster. |
| Disable Auto-Pull | If you would like to disable auto-pull, select this checkbox.
Note: Disabling Auto-Pull will lock Channels using this Source to the Source's Ingest Cluster and Targets to the Source's current active Broadcaster. This setting only applies to Pass-Through Channels. |
| Auto-Pull Latency \[ms] | Specify the maximum latency for auto-pull actions. The Broadcaster will update the latency as required, by using the maximal defined latency and then reducing the latency gradually. (Default: 1000 ms) |
| Decryption Key (for *Pull*) | If the Source is using AES encryption, enter the static key that was used for encryption. |
| WebRTC Playback | Select the desired playback method.
Note: WebRTC enables you to monitor the stream via web browsers and mobile applications with real-time communication (RTC). WebRTC needs to be activated independently for each Source in ZEN Master (by default it is disabled).
Select one of the following options:
* **Disabled** - users will not be able to view this Source using WebRTC (default).
* **Pass-Through** - passes the stream through to WebRTC without transcoding. This option *can only be used *if the input stream is already in a WebRTC compliant format (video - H.264 codec with *Baseline* or *Main *profile and no B frames, Audio - Opus codec).
* **Auto **- ZEN Master automatically transcodes the stream using the optimal profile for each specific user. In this option Zixi Broadcaster will decode the video, transforming it into RAW frames, which will be passed to the WebRTC library, where it will be re-encoded for each individual user.
Note: Best quality. However, if monitored by multiple users this can consume extensive resources.
* **1080p/720p/480p/360p** - ZEN Master transcodes the stream to a WebRTC compliant profile with the specified resolution. The transcoding is done by Zixi Broadcaster's transcoder.
Note: This method requires a Zixi Broadcaster with X264 or Nvidia for transcoding. This method allows many users to monitor the stream without encoding separately for each individual user, which saves CPU capacity. Since there is only one stream resolution, it is recommended to encode to a low resolution and low bitrate so that the stream will be viewable by all users monitoring the stream. |
| *Initial State* | |
| Disabled | Select this checkbox if you would like to disable this Source upon initial configuration. |
| Muted | Select this checkbox if you would like to disable error/recover notifications for this Source upon initial configuration. |
| ***Advanced*** | |
| Billing Codes | If you would like to track usage for this Source, enter your **Billing Code** details, see [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ) . (Supported for Broadcasters v14.8+)
**Note** that billing codes are **not** supported for **Push** Sources until Broadcaster **v19+**. |
| 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. |
| Billing Password | Enter the password that corresponds to this billing code. |
| Auto-Pull Billing Code | If you would like to track usage for this Source when using Auto-Pull connections, 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. |
| Auto-Pull Billing Password | Enter the password that corresponds to this auto-pull billing code. |
| Traffic Shaping | Traffic shaping is a network management technique used to control and optimize the flow of data. It ensures a smooth streaming experience by prioritizing video traffic and managing bandwidth usage. Set at 0 (default) for no traffic shaping, or 1 for automatic traffic shaping. **Note: **this option is only for sources for Zixi Broadcaster **18.2** or later. |
| Max FEC Overhead % | Allows you to limit the additional data added for FEC (Forward Error Correction). Available for sources for Zixi Broadcaster **18.2** or later. |
| Adaptive FEC | **Adaptive FEC** improves the efficiency of FEC by adjusting the amount of extra data sent according to network conditions. By default Adaptive FEC is turned on, but there are some cases where fixed FEC is needed and you will want to disable it. Some examples of cases where fixed rate FEC is preferable:
* When network bonding is used, and one of the network links periodically fails
* When low latency is required, the lost packet rate is high, and lost packet rate is high the round-trip-time is long (meaning ARQ can't get replacements for lost packets quickly enough) |
| Frame Thinning | Allow non-critical frames to be dropped to reduce latency. **P** |
| MTU/Auto Pull MTU \{bytes} | Specify the maximum transmission unit (largest data packet that a network-connected device will accept) in bytes for the Auto Pull. (For Pull sources only.) |
| Frozen Video Minimal Duration \{seconds} | Specify the default minimal duration in seconds of frozen video after which the Broadcaster will trigger a Frozen video alert. Default: 10 seconds. This setting is supported for Broadcaster version 16.3 and higher. For existing sources, you may need to restart the source. |
| Blank Video Minimal Duration \{seconds} | Specify the default minimal duration in seconds of blank video after which the Broadcaster will trigger a Blank video alert. Default: 10 seconds. This setting is supported for Broadcaster version 16.3 and higher. For existing sources, you may need to restart the source. |
| Ignore Monitoring PIDs | Ignore PIDs with empty audio streams to prevent false warnings - enter a comma-delimited list of PID numbers that should not be monitored for null content. |