[space] Zixi Documentation Home [title] ZEN MASTER August 2020 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates were pushed to ZEN Master on August 5, 2020. Old UI End of Life Notice In April 2020 Zixi introduced a new UI for ZEN Master. In the June 3rd release the new UI was set to be the default with a button allowing the user to switch to the old UI. In this release that button is removed but the old UI is still available, for emergency purposes, by specifying its URL in the browser. In the early August release of ZEN Master, the old UI will be retired completely and no longer available. NDI Sources and Targets NDI Sources and Targets can now be configured in ZEN Master. To create an NDI Source, select NDI on the Create New Source page. Next, after selecting the Target Broadcaster, the NDI Stream pull down will show NDI streams available on the local network where the Broadcaster is hosted. Choose the desired NDI stream from the list. Because NDI streams are provided to the Broadcaster as raw video frames, you next need to select an encoding profile so that the stream can be encoded. If you do not have existing encoding profiles then you will need to create one. Note, the encoding profile cannot pass through video or audio, it must encode both with encoding parameters of your choosing. Unlike many other Source types, PID mapping and SCTE 35 logging are not available with NDI because this data does not exist in NDI streams. Redundancy Enhancements Over the coming months we will be enhancing the types of redundant architectures that can be deployed and monitored in ZEN Master. The enhancements below are components of this effort: • Added option to disable auto-pull on Sources • Added the ability to have Backup Broadcasters in AWS/Azure/GCP • Added 'Prefer Backup' failover option for Sources Minor Improvements and Bug Fixes • Improved Sources page load performance • SCTE messages are now reported with detection time instead of processing time • Added API control and 4MB default socket size to all Pull Inputs created in ZEN Master • Added NIC selection to UDP Sources • Added note to Broadcaster version selection if the current selected version has been retired. Broadcaster clusters will continue to use the already selected Broadcaster version, even if retired, unless the Broadcaster version is explicitly updated by the user. • Added GPU ID to warning/error events on GPU usage thresholds • Added per GPU performance graphs for Broadcasters with multiple GPU cores • Added a limit of 25 to the number of Sources that can be created at one time in the ZEN Master UI. The ZEN Master API is recommended for bulk operations. • Fixed missing TR-101 section when Content Analysis on Sources was disabled • Fixed unable To Mute/Unmute, Disable/Enable All on Sources page • Fixed issue where user was unable to create Zixi pull targets with device "other” in hitless failover mode [title] Zixi ZEN Master Release Notes [path] Zixi Product Updates/ - [ZEN Master 17 Feb 2026 Release](docId\:OoFzWLdON5zOITzU-OQ1O) - [ZEN Master 18 November 2025 Release Notes](docId:1nkcg7LUZ1XXWJofimd0A) - [ZEN Master 12 August 2025 Release Notes](docId\:NS7OEYQ0K_3ZNva_9GaU3) - [ZEN Master 20 May 2025 Release Notes](docId\:ABAymtIClX7BlHlw8EXFQ) - [ZEN Master 1 April 2025 Release Notes](docId:-hgVDwTUqK3tiCpHHZAYF) - - [ZEN MASTER January 2025 RELEASE NOTES](docId\:Z8osvc11HIVMeb6faH0RM) - [ZEN MASTER December 2024 RELEASE NOTES](docId\:Q13hSH_bObdLaEPJtrrAW) - [ZEN MASTER September 2024 RELEASE NOTES](docId:3RVAnO5pO5ii32qJr86Ky) - [ZEN MASTER June 2024 RELEASE NOTES](docId\:Hc1SPXg0Mv8nrGXxyNfTk) - [ZEN MASTER April 2024 RELEASE NOTES](docId\:FiUi-dNspYlEAZ9bkRTtv) - [ZEN MASTER February 2024 RELEASE NOTES](docId\:qt5raN9nQPB4N_ZsWme4Y) - [ZEN MASTER October 2023 RELEASE NOTES](docId\:J3cQn3AIs9EXtbQOXA-Rt) - [ZEN MASTER September 2023 RELEASE NOTES](docId\:p4EWhM3V1w3jXtupddoti) - [ZEN MASTER July 2023 RELEASE NOTES](docId\:Dq2HsNhQN9pLicnHW3Nfz) - [ZEN MASTER June 2023 RELEASE NOTES](docId\:iSljQesArg2SbENcnNUuN) - [ZEN MASTER April 2023 RELEASE NOTES](docId\:YVCzQwWAD4l3XgEzLSWws) - [ZEN MASTER March 2023 RELEASE NOTES](docId:53zw438q6vQO-qNmvLSzv) - [ZEN MASTER December 2022 RELEASE NOTES](docId\:oTVBVaeOpLbsvdaN6mEQ4) - [ZEN MASTER September 2022 RELEASE NOTES](docId:-EBw15YOSA55KqxyjZFF-) - [ZEN MASTER May 2022 RELEASE NOTES](docId\:MpQ_vJi8AuU75vUa1gHHw) - [ZEN MASTER January 2022 RELEASE NOTES](docId\:zGNQ8lpApO4ZIEJ4MWUFB) - [ZEN MASTER November 2021 RELEASE NOTES](docId\:eT5t8d9AP3P1MEvxSpnFp) - [ZEN MASTER August 2021 RELEASE NOTES](docId\:MpqTwk3HtTlbjiHMLewu_) - [ZEN MASTER July 2021 RELEASE NOTES](docId:-FVi9KtQakqMvWNdNHQ0P) - [ZEN MASTER June 2021 RELEASE NOTES](docId:-vBpG-SiGbuPAVbDoj_X7) - [ZEN MASTER May 2021 RELEASE NOTES](docId:6qqyGKYW5pxEmJVbh7ULg) - [ZEN MASTER APRIL 2021 RELEASE NOTES](docId\:Ruy1BsRmqDsnc9XT_-KCV) - [ZEN MASTER March 2021 RELEASE NOTES](docId\:FqvDfwQCvpxWCcJ7axCNY) - [ZEN MASTER February 2021 RELEASE NOTES](docId\:VcMA43d1YsSs5dvCL5D1a) - [ZEN MASTER January 2021 RELEASE NOTES](docId\:CcPvL0stubG3SGrLikaXq) - [ZEN MASTER December 2020 RELEASE NOTES](docId\:nxJd9KrxmNsFrtshN0bmS) - [ZEN MASTER November 2020 RELEASE NOTES](docId\:zRQRuSYNv48je8ryvNccJ) - [ZEN MASTER October 2020 RELEASE NOTES](docId\:XFjurS4JPnXoYMria1Cek) - [ZEN MASTER September 2020 RELEASE NOTES](docId:1kxUoZNixlNxwhYblVrbH) - [ZEN MASTER August 2020 RELEASE NOTES](docId\:M0D7npoiwlPSLB4_Y1QA_) - [ZEN MASTER July 2020 RELEASE NOTES](docId\:qsQNqtJlAAdVxJBKI49uQ) - [ZEN MASTER June 2020 RELEASE NOTES 2](docId\:bgocHHkKVp-mjug-w9WMy) - [ZEN MASTER June 2020 RELEASE NOTES](docId:-v_VXRzYSuxz7Ymwg_tNC) - [ZEN MASTER May 2020 RELEASE NOTES](docId\:K4mA0j94gr7whr8AVED7I) - [ZEN MASTER April 2020 RELEASE NOTES](docId\:QqdNR6ndI6hGyQZinFCBA) - [ZEN MASTER March 2020 RELEASE NOTES](docId\:E8Zl1KVz4ZYstUr4tG20r) - [ZEN MASTER February 2020 RELEASE NOTES](docId\:fLOHlTrGLbUXxPW4HPKnY) - [ZEN MASTER January 2020 RELEASE NOTES](docId\:P-pfACROjOYNywm7Cxykf) - [ZEN MASTER December 2019 RELEASE NOTES](docId\:yRTRLpUZEJAv2lKAWG6L3) - [ZEN MASTER November 2019 RELEASE NOTES](docId\:VD1ID4zrTj1D9e8wWtWkz) - [ZEN MASTER October 2019 RELEASE NOTES](docId\:oeB90ghKF7W07uDGoKslD) - [ZEN MASTER September 2019 RELEASE NOTES](docId:8HJ9m1-7oXtbMeymNPRsM) - [ZEN MASTER August 2019 RELEASE NOTES](docId\:L1b-kIIrfHphctJElMhmD) - [ZEN MASTER July 2019 RELEASE NOTES](docId\:SVJy8uTriQy1xSz_Y2g8D) - [ZEN MASTER May 2019 RELEASE NOTES](docId:29qW-L8lj9cqwwWYHjGpp) - [ZEN MASTER April 2019 RELEASE NOTES](docId:0ZPHBdhLtTe3RtiRDy3-Y) - [ZEN MASTER March 2019 RELEASE NOTES](docId\:kB_BLEHkUA_HA-6-57kI_) - [ZEN MASTER February 2019 RELEASE NOTES](docId:9VjXVy1QUOuKplumRpqfz) - [ZEN MASTER January 2019 RELEASE NOTES](docId:_7WZNSxS7hwEPplHBRVyI) - [ZEN MASTER DECEMBER 2018 RELEASE NOTES](docId\:E92Z6tQf6DghS-cEzLD2R) - [ZEN MASTER NOVEMBER 2018 RELEASE NOTES](docId\:pIOd3yL6zWUlQOzoCewqy) - [ZEN MASTER OCTOBER 2018 RELEASE NOTES](docId\:FexPEy7dKVV4Hx852tmKS) - [ZEN Master - July 30 Deployment Details 2018](docId\:FnopN9OzYnMoPn3pPSGEv) [title] ZEN MASTER October 2023 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be included in the ZEN Master June 13, 2023 release. Features The following new features were implemented in this release: Incidents are now available to non-Admin users • Admins can mark incidents as public for all users. • Users can be designated as an Incident Manager allowing them access to all Incidents. o In previous iterations of ZEN Master, incidents were only available to Admin Users. o This update allows incident viewing privileges to be provided to Operations Users without the need to elevate Users to full Admins. o In addition, the new Incident Manager User Type allows a User to modify incidents including adding notes, annotations, closure, etc. o The new User type can be added to new, or existing Users: Additional Improvements and Changes The following additional improvements and changes were implemented in this release: • Exposed missing failover config options in Failover Channels: o Failover options are now available in Failover Channels: • Added optional PID Mapping column to Source and Target lists: o If a Source or Target uses a PID Map rule, the rule will be listed here. o This allows Users to sort and filter by PID Map rules and easily identify and find all sources and targets using a specific rule. • Added timestamps to Kafka event messages: o Timestamps, which were previously present in the Kafka entry metadata, are now added to the Kafka entry payload. • Live Events dashboard - Active/Locked Sources are highlighted. • Improved recovery time for Zixi Pull targets under some failure scenarios. • Added ZM assigned Broadcaster hostnames to Broadcaster details page. • ZECs are now available in Grids. • Reverting changes from change tracking will now display a restart confirmation when necessary. • Added Segment Path setting to HTTP Targets: o ZEN Master is updated to support the functionality previously available in the Zixi platform. o The path to the destination can be formed in one of the following ways: ▪ Full path • //? ▪ Path in parameters • ? ▪ Flat path • /*?* *• Any "/" in path should be replaced with "*" ▪ See platform documentation for further information. o This option is available under the advanced section of the HTTP Target type: • UI Polish o Cosmetic Dark Mode update. o Improved sorting of Broadcaster by Streams in Broadcaster table. o Broadcaster/Clusters listing selection is now persistent. o Broadcasters list table rows setting no longer resets on navigation. o Added feature guide to Dashboard. o Trailing whitespaces in object names will now cause an error. o Clarified state column in Incidents list. o Proliferation of copy-to-clipboard buttons. o Fixed issue with filtering on Grid table view. o Editing an "unmanaged" Zixi Push Source will display a warning that a config change is required on the client. o API Key copy is only displayed once ZEN Master has retrieved the key from AWS. o General styling and UI cleanup. ## Bug Fixes The following issues were resolved: • Automatic PULLs of Inter-cluster Sources now pull from the Inter-cluster Source correctly. • IO servers will now maintain a fixed ed25519 host key after recovery. • Resolved rare issue where ZM will report a reconnection error on a Source/Target that did not reconnect. • Fixed a validation error preventing creation of audio only transcoding profiles. • Thumbnails constantly refreshing on Grid Groups page. • IO server redirection always redirecting to private ports. • Incorrect Nvidia/Cuda driver version on AWS AMIs for v16 Broadcasters. API The following updates were implemented in the ZEN Master API: • Page count is now returned in Failover Channel list API. [title] ZEN MASTER January 2020 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates were pushed to ZEN Master on January 13, 2019. Direct Management of Access Tags ZEN Master has added a new Access Tags screen to the Settings menu. On this screen you can add new Access Tags, edit the names of existing Access Tags and delete (unused) Access Tags. (Previously, Access Tags could only be created within the flow of creating Roles and then they could not be edited or deleted.) 1\. Under Settings, select Access Tags. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/XWKc20P18Fx3vwCyiNk8y_image.png" size="50" width="1232" height="700" position="center" showCaption="false"} 1. On the Access Tags screen you can add a new Access Tag by click the "+ Add" button. Or you can edit or delete an existing tags by clicking on the desired action for that tag. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/oQ99VUUgsNvF4rth9xC4b_image.png" size="86" width="1904" height="624" position="center" showCaption="false"} Transcoder Outputs – H.264 or H.265 (HEVC) ZEN Master now supports transcoded outputs using H.265 (HEVC) codec (in addition to H.264). For H.265 you can choose between Encoding Profiles Main or Main 10. (For H.264 the available Encoding Profiles are Baseline, Main or High.) 1\. In the add New Transcoding profile dialogue, select the desired video Codec and then select the desired Encoding Profile. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/yoWWAk8kku5lt8pb53TNz_image.png" size="62" width="1416" height="1122" position="center" showCaption="false"} Network Bonding for Broadcaster and Feeder Sources ZEN Master now supports Network Bonding for Sources from Zixi Feeders and Zixi Broadcasters. For Broadcasters, you can now manually select specific NICs to be used for bonding. For Zixi Feeders, in addition to the existing option of automatic bonding, which uses any available NIC, ZEN Master also supports manual bonding. ### Bonding Broadcaster Sources 1\. When configuring a Zixi Broadcaster Source, you can activate network bonding by selecting the Bonding checkbox. You then need to select which NICs are used by clicking the "+" button next to each NIC. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/LxIctUUI-asos-odX8Unk_image.png" size="62" width="1336" height="998" position="center" showCaption="false"} 1. For each selected NIC, specify the Max Bitrate and whether or not it is designated as a Backup. o If you want to use this link only if there isn't enough bandwidth in the other links, select the Backup checkbox. o If you want to use this link in parallel to other links, DO NOT select the Backup checkbox. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/hWbrGXenYGM8hC-I_-5sM_image.png" size="86" width="1414" height="1086" position="center" showCaption="false"} ### Bonding Feeder Sources 1\. When configuring a Zixi Feeder Source, you can select one of the following options: • None – no bonding • Manual – you specify which NICs are used for bonding • Auto – any available NICs are used for bonding 2\. 3. When you select Manual, you need to specify which NICs are used, by clicking the "+" button next to the NIC. For each selected NIC, specify the Max Bitrate and whether or not it is designated as a Backup. Pass-through Option for Transcoded Channels You can now pass the original Source through when creating a Transcoded Channel. 1\. If you would like to pass the Source through, in the Add New Transcoded Channel dialogue, select the Includes Source checkbox. Then, enter the Bitrate for this source. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/S5YbTZ44hR_JQVEB-laDS_image.png" size="64" width="1266" height="1026" position="center" showCaption="false"} Pull Sources from MediaConnect ZEN Master added support for Pull (in addition to Push) sources from AWS MediaConnect. 1\. When configuring an AWS MediaConnect Source, select the radio button next to the desired Mode. Options are Pull (default) or Push. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/3o0M5-UyZZPIH2Jql24hP_image.png" size="64" width="1596" height="904" position="center" showCaption="false"} ### MINOR IMPROVEMENTS AND BUG FIXES • For a Target that is Not Assigned and also Disabled, show status as Disabled (as this takes precedence over the lesser issue of being unassigned). • ZEN Master now uses mean CPU/GPU (over the past 3 minutes) to determine availability of a broadcaster. • ZEN Master now supports unlimited MediaConnect flows. • Push targets are no longer affected by load balancing, rather they remain on the original broadcaster. • Updated Nvidia drivers for transcoding on AWS and GCP. • Updated AWS instances that are available for AWS Broadcaster Clusters, setting t3a as the default selection. • Fixed issue – some searches had been returning incomplete results. • Fixed issue – minor UI problems with the new Automation feature. • Fixed issue – had been showing mistaken error message for a Channel with two Sources sent to a MediaConnect target. • Fixed issue – mistakenly assigning Hitless Failover Sources to backup broadcasters. • Fixed issue – GCP broadcasters ignoring network configuration. • Fixed issue – SQL error when deleting a Source that is being used by an inter-cluster Source. • Fixed issue – problems with updating CBR padding of transcoded Sources. [title] ZEN MASTER December 2019 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates were pushed to ZEN Master on November 26, 2019. SCHEDULING AND AUTOMATION ZEN Master now includes the ability to create sets of tasks and then execute those sets of tasks with the push of a button or on a user defined schedule. This capability is found under the Automation menu item. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/mfoa6vNXZxz7gkghZMz81_image.png" size="38" width="560" height="934" position="center" showCaption="false"} To define a set of automation tasks, click the ADD button, enter a name for the task set, and define the access tags to control users that will have access to this task set. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Y9G-U8BOmGT6qf3KMdA3f_image.png" size="68" width="1552" height="754" position="center" showCaption="false"} Initially an automation task set will have no defined tasks or schedules. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/fXex6xu7pqui9_iMr6ZoA_image.png) To add a task, click ADD TASK under the Tasks tab. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/EuP-bUdrVRVUWVWrJXJ0v_image.png" size="76" width="1708" height="560" position="center" showCaption="false"} A variety of tasks can be automated, as shown in the Task Type pulldown. After providing a name for the task, select a task type. Each task type will have a relevant set of fields to complete. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/gkS9r5yU72z4gqV-10rgS_image.png" size="60" width="1290" height="1448" position="center" showCaption="false"} Tasks in a task set will be run immediately by default, when a task set is run. If desired, a start time relative to the start of execution of the task set can be defined allowing for tasks to be sequenced. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/QNaeq9KaXQVLk00bmRyHC_image.png" size="72" width="1944" height="522" position="center" showCaption="false"} Once the tasks in the task set are defined, a schedule to execute the task set can be defined. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/H3x6KayWHCuKY0B_LKXSN_image.png" size="86" width="1966" height="396" position="center" showCaption="false"} A schedule allows you to set a start date/time, end date/time, and the repeat frequency including once, daily, weekly, monthly, last day of the month, or repeat on a provided number of minutes, hours, days, weeks, or months. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/tAlz9dmQFvargBNHfmEyp_image.png" size="56" width="1338" height="1826" position="center" showCaption="false"} Multiple schedules can be defined for a task set to accommodate complex schedules. tab shows all of the defined schedules with start date, end date, and the next execution time. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/99bkS4pDIcPLSWOnnKWb8_image.png) The Events tab shows a history of task sets being created and scheduled, and a status of tasks that were executed. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/yh8zOfhqRLywC02yGZOs8_image.png) MINOR IMPROVEMENTS AND BUG FIXES • Added the following AWS instance types for Broadcaster Clusters: g4dn.xlarge, g4dn.2xlarge, g4dn.4xlarge • Adjust error/warning message to specify the correct cloud provider – AWS, Azure, or GCP (ZM-311) • Added API for Active Broadcaster ID for Targets (ZM-379) • Added Max VA Diff setting to transcoding profile video advanced page (ZM-388) • Added warning that player might stall if less than 5 segments are configured (ZM-389) • Removed unsupported Channels element from selection options for stats reports. (ZM-394) • Improved events search performance with database optimizations (ZM-65) • Improved cluster Pull target uniform load balancing (ZM-163) • Fixed inter-cluster Sources using Target cluster DTLS config instead of Source cluster (ZM-372) • Fixed issue where failed launch of Broadcaster on GCP stays in warning state (ZM-377) • Fixed UI errors when editing inter-cluster Source (ZM-383) [title] ZEN MASTER April 2023 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be included in the ZEN Master April 11, 2023 release. Features The following new features were implemented in this release: • AWS Broadcasters now support custom Names and Streaming/Private Ips. Previously, when creating Clusters in AWS, individual Broadcasters were named per parent Cluster, followed by a unique random sting. In this update, the ability to override the random post-fix and specify a specific Broadcaster name is introduced: • Source Multiplexing. A new ZEN Master Source type, accessible in the “Create New Source” menu, is provided to support the current Multiplexing capability of the Zixi Broadcaster: Once selected the ZEN Master operator can: \- Set a target bitrate for the final multiplexed MPTS. \- Select multiple individual SPTS sources to include in the MPTS. \- For each component program of the final stream, configure: o The program name. o Program ID. o Base PID. PIDs will increment consecutively from the base PID within each program. Once the new source configuration is saved, the target Broadcaster of the Multiplex Source acquires all input sources, (either locally, or where necessary via auto-pull from corresponding broadcasters) and constructs the final MPTS. The MPTS output appears as a new source and is available as an input for Channels etc. The Transport Stream structure can be verified by selecting the new Source, and inspecting the stream details for the contained Programs. • Demux Sources. In addition to Multiplex Sources, Demuxing is now supported and is accessible in the “Create New Source” menu: The Source configuration provides the ability to choose an existing MPTS source. Once an MPTS is selected, the “Program Number” dropdown allows the user to select the specific program from within the MPTS that should be broken out as a standalone SPTS. Once the other common source parameters are set, and the Demux Source is saved, the new Source appears in the Sources list and is available as an input for Channels. • Fully customizable Roles. Permissions are now managed by object type and more control is provided to Admins to assign read, write, and notification permissions across system objects: • PID mapping Sources now display the changes in the PID tree. The before-and-after PID number is highlighted in the transport stream details when mapping rules have taken effect, enabling Users to easily confirm that a PID number change has occurred: • Re-designed SCTE35 tracking/alerting on Sources. SCTE-35 monitoring on Sources has been updated to only check for SCTE existence in a time window. This allows for alerting of all SCTE messages that do not fall within the window, including those that do not adhere to the SCTE specification: o SCTE35 alerting is now the same as closed-captions alerting, ZM will alert if there are no SCTE35 messages for some period of time. o At least one SCTE message is required before ZM will alert. o The alert is disabled by default. • VIP Tags. Admins can now assign VIP status to a tag. Any object that contains one or more VIP tags will have its alerts elevated as VIP: Objects tagged as VIP will be clearly labeled in the object details page: In addition, object list tables can highlight, and be sorted by, VIP objects: • In-application User Guide - Event profiles only for now. Beginning with the Event Profiles, ZEN Master introduces detailed in-application links to context specific help documentation. Additional Improvements and Changes The following additional improvements and changes were implemented in this release: • Source sharing updates: • Added link management and password protection. The previous release introduced the ability for users to share a Source details page with external partners and others without ZEN Master accounts. The latest release builds on this by adding password security. External users with the share link are required to enter the password before accessing the stream details: • Added elementary stream bitrate graphs. Once the shared link is accessed and the correct password provided, the external user is now provided with an additional bitrate graph: • ZECs are now presented in Source/Channel/Target diagrams. • PID Mapping profiles now allow list of PIDs or ranges of PIDs. • Grids can now be filtered by Broadcaster version. • Administrators can now modify User Notes, all Note changes are now logged. • MPGA (MPEG-1 layer 2) Audio transcoding. • Support for SASL\_SCRAM Kafka Authentication. • Thumbnail will now display the previous picture with a warning if a refresh fails. • Automatic disabling of Channels is now optional at completion of Live Events. • Added description field support to the MediaConnect Channel type. • General UI Polish. [title] ZEN Master 18 November 2025 Release Notes [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be included in the ZEN Master release for November 11th, 2025. ## Features The following new features were implemented in this release: :::Heading{depth="3" indent="1"} API Keys: ::: :::Paragraph{listStyleType="disc" indent="2"} API Keys now have an expiration date, along with the option to attach 1 or more Roles. The addition of Roles means now possible to set granular permissions on API keys to control what API operations are allowed using that key. ::: :::Paragraph{listStyleType="disc" listStart="2" indent="2"} All existing API keys, those created prior to the November 18th update, will expire 1 year from the release, on November 18th 2026. ::: :::Paragraph{listStyleType="disc" listStart="3" indent="2"} For new keys created after the release, the default and max. expiration is 1 year. ::: :::Paragraph{listStyleType="disc" listStart="4" indent="2"} See [Configuring API Keys](docId\:y5VWL7q34grAoPRjlHzuI) ::: ![Create New API Key](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/2JFdhHf8uYDirjReXt3Yn-20251111-132829.png) :::Heading{depth="3" indent="1"} Live Events: ::: :::Paragraph{listStyleType="disc" indent="2"} As of November 18th 2025, Zixi will begin the process of transitioning Live Events to use Failover Sources as part of the planned deprecation of Failover Channels. ::: :::Paragraph{listStyleType="disc" listStart="2" indent="2"} The Live Events UI is updated to work with Failover Sources. ::: :::Paragraph{listStyleType="disc" listStart="3" indent="2"} To support Failover Sources, two new API parameters are introduced: ::: :::Paragraph{listStyleType="disc" indent="3"} NEW - failover\_source\_ids for POST/PUT. ::: :::Paragraph{listStyleType="disc" listStart="2" indent="3"} NEW - failoverSources for GET/responses. ::: :::Paragraph{listStyleType="disc" listStart="4" indent="2"} As of the release. Two API parameters are being marked as deprecated. Both parameters will remain fully functional until their scheduled retirement in April 2026: ::: :::Paragraph{listStyleType="disc" indent="3"} Deprecated - failover\_channel\_ids. ::: :::Paragraph{listStyleType="disc" listStart="2" indent="3"} Deprecated - failoverChannels. ::: :::Paragraph{listStyleType="disc" listStart="5" indent="2"} See [Adding a Live Event](docId\:sFGlqBrA-439CjrUtdUvb) ::: :::Heading{depth="3" indent="1"} Failover Channels deprecation: ::: :::Paragraph{listStyleType="disc" indent="2"} In the August 18th release of ZEN Master, Zixi ceased further duplicative development of Failover channels and transitioned to focusing on Failover Sources. ::: :::Paragraph{listStyleType="disc" listStart="2" indent="2"} Existing Workflows and API endpoints remain until the planned completion in April 2026. ::: :::Paragraph{listStyleType="disc" listStart="3" indent="2"} As of November 18th, 2025, the Failover Channel UI is marked for deprecation and moved to the “More Options” menu in the New Channel page for this release. ::: :::Paragraph{listStyleType="disc" listStart="4" indent="2"} We will begin the process of transitioning Live Events to use Failover Sources directly, and associated UI updates in the next release. ::: :::Paragraph{listStyleType="disc" listStart="5" indent="2"} See ::: :::Heading{depth="3" indent="1"} **ESNI UI:** ::: :::Paragraph{listStyleType="disc" indent="2"} The November 18th release introduces the monitoring tools for the ESNI Scheduling back-end. ::: :::Paragraph{listStyleType="disc" listStart="2" indent="2"} The UI is available when the ESNI server module of ZEN Master is enabled and configured. ::: :::Paragraph{listStyleType="disc" listStart="3" indent="2"} Speak to your technical representative to arrange a demo. ::: :::Paragraph{listStyleType="disc" listStart="4" indent="2"} See ::: ![ESNI Schedule](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/CvIX-sCIUbHfJkbONw0fV-20251105-193956.png) :::Heading{depth="3" indent="1"} Change Tracking ::: :::Paragraph{listStyleType="disc" indent="2"} Will now record the initial creation of the object in order to store the initial configuration ::: :::Paragraph{listStyleType="disc" listStart="2" indent="2"} Applie only to objects created after this release ::: :::Paragraph{listStyleType="disc" listStart="3" indent="2"} See [Change Tracking](docId\:hc-KMARjxkvIaZ69v6IVv) ::: ![Change Tracking](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/Cwyw8R_NR3cGwD020b3ub-20251111-132556.png) :::Heading{depth="3" indent="1"} Support Private-IP-Only for AWS Cluster administration: ::: :::Paragraph{listStyleType="disc" indent="2"} When selecting a VPC with a NAT Gateway - there is no longer a need to attach a public ipv4 to instances for administration. ::: :::Paragraph{listStyleType="disc" listStart="2" indent="2"} This has multiple potential benefits: ::: :::Paragraph{listStyleType="disc" indent="3"} Reduces public IPV4 costs. ::: :::Paragraph{listStyleType="disc" listStart="2" indent="3"} Allows the use of a second NIC with a Public IP for DPDK server without the need to allocate an additional elastic IP. ::: :::Paragraph{listStyleType="disc" listStart="3" indent="3"} Potential security benefits. ::: :::Paragraph{listStyleType="disc" listStart="3" indent="2"} See [Adding a Broadcaster Cluster - Managed](docId:6sLx4TD__ZKr2XFhO8qZ6) \* ::: :::Heading{depth="3" indent="1"} ‘Private IP’ support for Zixi PUSH Sources: ::: :::Paragraph{listStyleType="disc" indent="2"} ‘Private IP’ is now supported for Zixi PUSH Sources between systems within ZEN Master. ::: :::Paragraph{listStyleType="disc" listStart="2" indent="2"} NOTE: If checked, only the specific Broadcasters as selection options for ‘Target Broadcaster’. ::: :::Paragraph{listStyleType="disc" listStart="3" indent="2"} The resulting ‘Private IP’ will be displayed in the source details. ::: :::Paragraph{listStyleType="disc" listStart="4" indent="2"} See [Adding a Zixi Source - Broadcaster Push](docId\:vuNNBbUKYIyBi9EYCRX3C) ::: ![Use Private IP Zixi Push Source](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/9yd10j8Jz3UUKEnKeAzTd-20251111-132419.png) :::Heading{depth="3" indent="1"} Broadcaster Upgrade detailed dialog: ::: :::Paragraph{listStyleType="disc" indent="2"} Continuing progress for broadcaster version tools within ZEN Master, the Broadcaster dialog is once again available via the Broadcaster’s top right menu. ::: :::Paragraph{listStyleType="disc" listStart="2" indent="2"} As of the November release the “Install Version” option provides the more details Broadcaster Installation Dialog: ::: ![Broadcaster Upgrade Dialog](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/bhpBs-x8I2yig63zJg3xF-20251110-194835.png) :::Paragraph{listStyleType="decimal" listRestartPolite="1" indent="2"} Broadcaster active metrics. ::: :::Paragraph{listStyleType="decimal" listStart="2" indent="2"} Current, and Target Version selection. ::: :::Paragraph{listStyleType="decimal" listStart="3" indent="2"} System Architecture confirmation details. ::: :::Paragraph{listStyleType="decimal" listStart="4" indent="2"} The ‘Active Objects’ table allows users to disable/mute objects before upgrading. ::: :::Paragraph{listStyleType="decimal" listStart="5" indent="2"} “Error Message’ panel. ::: :::Paragraph{listStyleType="decimal" listStart="6" indent="2"} The ‘Install’ action button. ::: :::Paragraph{listStyleType="disc" indent="2"} ‘Install’ will upload the selected installer to the Broadcaster and initiate the upgrade. ::: :::Paragraph{listStyleType="disc" listStart="2" indent="2"} The Installation script runs as before, and ZEN Masters standard monitoring cycle continues to monitor during the process ::: :::Paragraph{listStyleType="disc" listStart="3" indent="2"} Pre/Post-Installation Objects Status shown side by side: ::: ![Object Status Before/After Upgrade](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/xT4kwjOb_YLFf5sjrV596-20251110-195541.png) :::Paragraph{listStyleType="disc" indent="2"} As the Installation begins: ::: :::Paragraph{listStyleType="decimal" listRestartPolite="1" indent="2"} The ‘Initial Status’ column records an historical snapshot of the pre-install object 2.3.4.status. ::: :::Paragraph{listStyleType="decimal" listStart="2" indent="2"} The current object ‘Status’ column continues to monitor the objects. ::: :::Paragraph{listStyleType="decimal" indent="3"} a.Users can therefore compare the original and current status of an object as the upgrade progresses and connections are restored. ::: :::Paragraph{listStyleType="decimal" listStart="3" indent="2"} The ‘Broadcaster’ column will also reflect if a PUSH or PULL source has failed over to another broadcaster in the cluster if it was considered to do so. ::: :::Paragraph{listStyleType="decimal" listStart="4" indent="2"} Upgrade completion, error messages, etc. will appear in the GUI as the installation progresses, and be logged. ::: :::Paragraph{listStyleType="disc" indent="2"} Note – The historical status and any other data preserved in the dialog is front-end only and will be lost when the Operator exits the dialog. ::: :::Paragraph{listStyleType="disc" listStart="2" indent="2"} Conversely, Users wishing to perform consecutive upgrade, such as to step through an interim version to reach the final version, can re-use the dialog without the need to exit. ::: :::Paragraph{listStyleType="disc" listStart="3" indent="2"} See [Actions on Broadcasters](docId\:B1y6nShFZcUwCd0_GSPG-) ::: :::Heading{depth="3" indent="1"} Automatic recovery all ZM Sources/Channels/Targets on AWS broadcasters that get terminated/restarted by AWS: ::: :::Paragraph{listStyleType="disc" indent="2"} AWS Instances can be terminated for a variety of reasons outside of ZEN Masters control, such as AWS retirement, manual termination via the AWS Console, underlying system loss, etc. ::: :::Paragraph{listStyleType="disc" listStart="2" indent="2"} A subset of ZEN Master managed configurations exists locally in the instance, such as those of Zixi PULL inputs, UDP Outputs, etc. ::: :::Paragraph{listStyleType="disc" listStart="3" indent="2"} ZEN Master will now automatically recreate these configurations on the new instance that is launched by the AWS Auto-Recovery system, thus no longer requiring a manual restart of the object by the ZEN master operator. ::: :::Paragraph{listStyleType="disc" listStart="4" indent="2"} See [Zixi and AWS](docId\:B_CAPfgyTnyegRTtSssM1) ::: :::Heading{depth="3" indent="1"} New multi-select confirmation dialogs and tools: ::: :::Paragraph{listStyleType="disc" indent="2"} Dialogs confirming changes on multiple objects now display the list of objects and the result of the action, successful or otherwise, for each object. ::: :::Paragraph{listStyleType="disc" listStart="2" indent="2"} When performing a group action, such as muting many sources at once, the rearchitected table provides improved clarity and filtering for object management. ::: :::Paragraph{listStyleType="disc" listStart="3" indent="2"} See [Actions on Sources](docId:7RiDbifG03IGgIwYl9E8X) ::: ![Confirm Actions on Multiple Objects](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/EWu-kz7oFEATdhxrEHxVc-20251111-132227.png) ## Improvements and Changes :::Heading{depth="3" indent="1"} Multi-edit forms now support updating Cluster/Target Broadcaster: ::: :::Paragraph{listStyleType="disc" indent="2"} Users can update the ‘Processing Cluster’ and ‘Target Broadcaster’ for multiple Channels at the same time. ::: :::Heading{depth="3" indent="1"} ZEN Master diagrams can now be exported as PNG files. ::: :::Heading{depth="3" indent="1"} Full screen mode for tabs/panels in details view: ::: :::Paragraph{listStyleType="disc" indent="2"} Enhances ability to easily monitor singular tabs and details screens in NOCs etc. ::: :::Heading{depth="3" indent="1"} Zixi Pull Sources now support alternative hosts: ::: :::Paragraph{listStyleType="disc" indent="2"} For Disaster Recovery configurations involving the Alt. Host mechanism, PULL Sources are now supported. ::: :::Heading{depth="3" indent="1"} It is now possible to stop/start AWS Broadcasters without deleting them: ::: :::Paragraph{listStyleType="disc" indent="2"} Individual broadcasters in AWS Clusters can now be disabled and enabled. ::: :::Paragraph{listStyleType="disc" listStart="2" indent="2"} Note: This feature requires an IAM policy update. ::: :::Heading{depth="3" indent="1"} Live Events can now be ordered by countdown. ::: :::Heading{depth="3" indent="1"} Support for new AWS instance types ::: :::Paragraph{listStyleType="disc" indent="2"} Options now include instances from the c8gn family, as well as c7gn.4xlarge. ::: :::Heading{depth="3" indent="1"} Added an event log when objects are put into flapping ::: :::Heading{depth="3" indent="1"} Remote IP is now logged on connection/reconnection for Sources.state. ::: :::Heading{depth="3" indent="1"} “Automatically switch to Preferred Source” is now the default for new Failover Sources. ::: :::Heading{depth="3" indent="1"} Opening a link to an object that doesn't exist will now show a ‘404 landing’ page ::: :::Heading{depth="3" indent="1"} Further optimizations to Channel/Target list page initial loading times. ::: :::Heading{depth="3" indent="1"} Added WebVTT positioning to Transcoded/Adaptive Channels. ::: :::Paragraph{listStyleType="disc" indent="2"} In the Channel **advanced** section, the controls appear when ‘Convert CEA-708 to WebtVTT’ AND ‘Custom WebVTT Positioning’ are both enabled. ::: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/dGpEkEJBdtBpe5UHSH5cY-20251111-183457.png) - See: - [Adding Transcoded Channels](docId\:xwF-mFNvRA5E3jQL2YMjU) - [Adding Adaptive Channels](docId\:rKvnZF-Tft8VGnzZsb79b) :::Heading{depth="3" indent="1"} Added playback (VLC/WebRTC) buttons to thumbnail Grids: ::: :::Paragraph{listStyleType="disc" indent="2"} VLC Playback option is available in the Grid element hover-over. ::: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/PaJkk6VV2StvzNdu1LlEq-20251111-184111.png) - See [Viewing Thumbnail Grid Display](docId\:AlRDeKalu0zYp5IFvAayO) ### Added used packet counters to Failover Source diagrams: ![Used Packets Failover Sources](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/0EBGEx3EtztLCCBShvzkn-20251111-190142.png) :::Heading{depth="3" indent="1"} Removed the ZEN Master generated ID’s from TAG Multiviewer source implementation. ::: :::Heading{depth="3" indent="1"} Exposed Adaptive FEC controls on Zixi Sources/Targets. ::: :::Paragraph{listStyleType="disc" indent="2"} See the docs on adding Zixi Sources and Targets ::: :::Heading{depth="3" indent="1"} Added SDT table to existing Stream Analyzer: ::: :::Paragraph{listStyleType="disc" indent="2"} For Operators with the need to confirm SDT entries in the DVB tables. ::: ## API Changes ### New API Endpoints - Broadcasters (AWS Clusters only): - NEW: PUT /broadcasters/\{id}/enable or /disable. - No payload. - New API to list recent SCTE-35 messages on a Source: - NEW: GET /scte35. - List SCTE-35 messages for the specified Sources. - Targets: - NEW: PUT /targets/assignToChannelByExternalId. - Assign a Target to a Channel using External IDs. ### API Field Additions - All object types: - NEW object\_link. - Live Events: - NEW external\_link. - Optional URL String. - Default: empty. - Channels: - NEW WebVTT positioning fields. - Adaptive, Transcoded Channels. - Clusters: - NEW private\_ips\_only. - Optional boolean. - Default: false. - Failover Channels and Failover Sources: - NEW automatic\_max\_bitrate boolean. - SCTE-35 manipulation on Targets (POIS only for now): - Types: rist, rtmp\_push, srt\_targets, udp\_rtp, zixi pull/push. - NEW enable\_scte35\_insertion. - NEW scte35\_insert\_on\_null\_timeout. - REMOVED scte35\_replace\_with\_null. - SCTE-35 manipulation on Sources: - NEW scte35\_insert\_on\_null\_timeout. - REMOVED scte35\_replace\_with\_null. - Sources / Targets: - NEW adaptive\_fec. - Optional boolean. - Default: true. - Sources: Zixi Pull, Push, ZEC Push, MediaConnect. - Targets: Push. - Sources - Zixi Pull: - Updated remote\_host: Can now be a comma separated list of hosts. - Transcode Profiles: - New fields for logo insertion. ### API Documentation Updates and Changes - All: - Standardized all ZM API Response Codes. - Broadcasters, Feeders, Receivers: - Updated tunnel\_username to string. - Channels: - Combined Channels under one group. - Events log: - Added details about pagination. - MediaConnect Sources: - Added Documentation. - Roles: - Added API Keys schemas. - Added new permissions. - Sources: - Added Error Concealment and SCTE-35 Manipulation. [title] ZEN MASTER September 2022 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be included in the ZEN Master September 6, 2022 release. Features The following new features were implemented in this release: • Added propagation of ZEN Master tags on Broadcasters to AWS EC2 machines. Requires updating policy on AWS with example found under Configuration->Amazon AWS and then editing and re-saving Broadcaster Cluster. • Added read-only API keys • Added support for spinning up Graviton2 EC2 instances on AWS • Added ability to configure HTTP Targets for YouTube Live • Added support for E-AC3 Dolby Digital Plus audio output in transcoding profile • Added ability to select a specific Broadcaster for a pass-through Channel • Added individual alerts for each CQA scenario – frozen video, blank picture, silent audio, and audio clipping – so they can be configured individually • Added Active Objects tab to Broadcaster page that shows Sources/Targets/Channels that are currently active on that Broadcaster • Enabled installation of AgentZ on ZEN Master managed Broadcasters. AgentZ pushes analytics and statistics data from the Broadcaster machine to ZEN Master and replaces the current pull based model. AgentZ will enable additional data, such as machine and OS related data, to be collected by ZEN Master and used in the Intelligent Data Platform. AgentZ will automatically be installed on newly spun up Broadcasters. For existing Broadcasters, the Broadcaster Detail page contains a link that will install AgentZ on that Broadcaster. • Intelligent Data Platform: o Added “Automated Multi-Object Correlated RCA Attribution”. IDP now automatically groups together signal degradation errors, based on not-recovered packets, across multiple Sources and Targets into correlated Incidents. It helps determine root cause by showing what the involved objects have in common: a client network, server network, or Broadcaster, and identifies the offending network or Broadcaster. It also shows relevant ratios for the root cause attribution, such as the percentage of connected objects on a Broadcaster that failed. o Updated the detailed Incident View with an expanded blast radius view that shows Incidents that span multiple Channels including an advanced table view of all involved Sources and Targets. Also improved graph order and locking control and made Incident details and notes more prominent. Additional Improvements and Changes The following additional improvements and changes were implemented in this release: • Added ability to mute an individual Broadcaster in a Broadcaster Cluster • Added separate Broadcaster and Cluster filters in the Events Log • Added ability to change Source/Channel Target Broadcaster with no restart • Added Network/Location changes in the Broadcaster event log • Added new warning alert when Sources are not binary identical in a Failover Source with hitless merge enabled, set to log only by default • Added a 404 page if user enters an invalid URL • Improved Target Channel switching time by using the Broadcaster's switch Input feature when possible • Improved table format on Sources and Channels pages with new capabilities such as dragging columns to a new location and resizing columns • Improved AWS cluster implementation including: o differentiating between machines launched by the user or AWS o reusing the same Broadcaster object in ZEN Master when AWS replaces an instance o logging successful elastic IP assignment • Improved display of multiple alerts on Grid thumbnails • Replaced Notes auto-save with save/delete buttons • Exposed Failover Source switching and slate locking to public API • Failover Sources now default to non-hitless. The more advanced merge mode options are now found under a "Show more options" toggle. • Adaptive Channel type is now hidden behind a "Show more options" toggle • Clarified error message when a Cluster delete is blocked by a Pass-through Bug Fixes The following issues were resolved: • Fixed thumbnails missing for users with read-only permissions • Fixed issue with cloning UDP/RTP Sources • Fixed issue with Channel diagrams on disabled Channels • Fixed multiple issues on Source forms • Fixed EC2 instances with no name after launch, requires Cluster edit • Fixed resetting latency on Zixi Pull "Other" Target types • Fixed incorrect Source Offline message appearing for a minute after a Source is created • Fixed multiple issues displaying a restart warning on edit • Fixed issue where editing PID mapping Source changes it to an Inter-cluster Source • Fixed credentials error when writing to Azure Blob Storage • Fixed incorrect Target offline error even when it is working • Fixed sync issue between ZEN Master and Broadcaster when editing Sources in use by Failover Sources • Fixed Targets connecting to invalid Sources after a Channel/Target Edit • Fixed switching Channels on Targets with specific Source preference breaking sync between ZEN Master and Broadcaster configurations • Fixed inconsistent values on candle stick history graphs when zooming in/out [title] ZEN MASTER April 2020 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates were pushed to ZEN Master on April 20, 2020. New UI ZEN Master has launched a new user interface (UI) with a streamlined look and feel and improved responsiveness. The new UI can be accessed by clicking on the button in the header bar. In next month’s release the new UI will become the default, with a button to roll back to the old UI. The following sections highlight some of the improvements in the new UI. ### Info Pages When you select an object instance (Feeder, Broadcaster, Receiver, Source, Channel or Target), or other list element (Automation, Report or License), the list will become narrow showing only the element name and detailed info about the selected element is shown. In the new UI this info is shown on the right side of the screen (as opposed to the bottom), and can be viewed either in tab view or in accordion view (with collapsible sections). Also, the Details tab/section for Sources now includes a thumbnail preview of the stream. The following are examples of the information display for a Source in accordion view and tab view. Accordion View In accordion view, selectable in the top right-hand corner, there are two columns of information panels, if browser width allows. The UI is responsive and the two columns will become a single column on narrow browser windows or mobile devices. Each information panel can be minimized and maximized with the and buttons on the top left of the panel. The min/max state of panels remains persistent while viewing other objects of the same type, Sources for instance. It will reset once you view other object types. ### Tab View In tab view, selectable in the top right-hand corner, information is organized into tabs similar to the previous ZEN Master UI. However, the information panel is to the right of the object list and not below as before. The information in each tab is displayed responsively to adjust for browser width. ### Grids The Grids screen has been improved to include a thumbnail view of Sources with the typical formatting capabilities of Grids or, as before, Grids can show status and key data for all object types. The Grids can now be shown in full screen mode and also in dark mode, which may be preferable for monitoring streams in a NOC. Viewing Source thumbnails using Grids replaces the option of viewing the Sources screen in Thumbnail mode. Note: ZEN Master automatically generates a default Grid that includes all Sources. In addition, you can create any number of custom Grids and Grid Groups to monitor customized groupings of ZEN Master resources. ### Working with Lists The new UI makes it easier to search and sort the elements shown in lists (e.g. Broadcasters, Sources, Reports etc.). ### Search Filter The search feature now shows results that match the search text for any data element. This includes the data shown in each column as well as the Access Tags associated with the element. So, for example, if you enter the search text “Demo” on the Sources screen, results are shown for Sources that have “Demo” as part of the Source Name, Ingest Cluster, Input etc. ### Sort You can sort all lists by the data elements shown in each of the columns. When the full list screen is shown, click on the desired column headings. You can reverse the order by clicking the heading a second time. When the list is shown side by side with the info pane (i.e. once an element has been selected), sorting is done as follows, including by columns that are not displayed: 1\. Click on the Sort by button. A drop-down list of parameters is shown. Select the parameter that you would like to sort by. The sorted results are shown together with the column for the sorting parameter (e.g. Status). ### History Graphs The History tab for Sources and Targets shows graphs representing the instance’s performance over time. Several improvements have been introduced to these graphs. • Time Ranges: ZEN Master now offers a broad selection of preset time ranges (default: 24 hr), as well as the option to set a custom range. The time range selected will apply to all displayed graphs. Note, currently one year of history is saved in the ZEN Master database even though the graphs show larger timeframes. Contact Zixi if you require more than one year of history. • Graph Refresh Frequency: You can set the frequency that the graph automatically refreshes. The default is blank which means no automatic refresh. You can set the refresh frequency or manually refresh by clicking . • Graphs Coordination: ZEN Master now treats all graphs as a single component so that the zoom time range set for one graph is automatically applied to all graphs on that screen. Similarly, when you hover over a point on one graph, the tool-tip values are shown for the same point in time on all of the graphs. ### Data Forms Previously, forms used for user input were a popup dialog, possibly with multiple pages that you would navigate through; this was not ideal for mobile or touch based devices. In the new UI, forms are no longer a popup dialog and instead the browser navigates to a new page for each form. For forms that are especially long, navigation links at the top of the page will take you directly to the desired section of the form. Also, some sections of the form, such as the “Advanced” section, will start out collapsed and can then be expanded by the user. New Supported Input/Output Protocols ZEN Master has added support for additional protocols in the new UI.. • RIST: RIST is supported for Targets and Sources using both Simple and Main profile. Simple profile runs on Zixi Broadcasters v13+ and Main profile runs on v14 broadcasters. For Targets, only Push is supported; for Sources, both Push and Pull are supported. • SRT: SRT is supported for Sources as Push or Pull. • UDP/RTP: Support for UDP/RTP was added for Sources as Push or Pull. This is in addition to the existing support for UDP/RTP as a Push Target. ### Summary of new Protocols Protocol Target Source Push Pull Push Pull RIST Simple √ X √ X RIST Main √ X √ √ SRT X X √ √ UDP/RTP √ X √ X Note: For all of the above protocols, Push Sources need to have a specific Broadcaster assigned (not Any Primary/Secondary Broadcaster). ### MediaConnect Flows ZEN Master now supports full integration of MediaConnect with ZEN Master in the new UI. This enables you to create and manage new MediaConnect Flows from within the ZEN Master UI (i.e. without accessing the MediaConnect console or using their APIs). Aside from the convenience of working exclusively within the ZEN Master UI, this method provides the following advantages: • Create MediaConnect Sources independently of MediaConnect Flows (Channels), enabling flexibility to interchange between MediaConnect Sources and Channels. • Show History graphs, TR101 warnings and Event logs Media Connect Integration Methods ZEN Master now supports two different methods for integrating MediaConnect Flows. • Method 1 - Partial Integration (existing): The previously existing method uses existing MediaConnect Flows as a Source or Target in ZEN Master. • Method 2 – Native Flow Management (new): The new method involves creating and managing a completely new MediaConnect Flow in ZEN Master and connecting it to Sources and Targets defined in ZEN Master. The following is a description of the procedures for each method. ### Method 1 - Partial Integration Bring a MediaConnect Flow into ZEN Master as a Source using the following procedure: 1\. Have a pre-existing MediaConnect Flow or create a MediaConnect Flow using the MediaConnect console or APIs. 2\. 3. In ZEN Master, create a new Zixi Source. In the Input section of the Source configuration, select the desired Mode, either Push or Pull. 4\. For the Application, select AWS MediaConnect. 5\. 6. Fill in the rest of the fields as desired and Save the Source. In ZEN Master, connect the Source to a Channel and Target using standard procedures. Send a ZEN Master Source to MediaConnect for further processing and distribution using the following procedure: 1\. Have a pre-existing MediaConnect Flow or create a MediaConnect Flow using the MediaConnect console or APIs. 2\. 3. 4. In ZEN Master, set up the Source and Channel using standard procedures. In ZEN Master, create a new Zixi Target. In the Type section of the Target configuration, select AWS MediaConnect as the Type. (The Channel Type is automatically set as ZEN Master Channel since you are getting the stream from a standard ZEN Master Channel.) [title] ZEN MASTER NOVEMBER 2018 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates were pushed to ZEN Master on November 5, 2018. NOTIFICATION AND ERROR ESCALATION CONFIGURABILITY Email notifications in ZEN Master result from a sequence of events and, with this update, the user will now have more control over how objects transition to an error state and when notifications are sent. Previously, when a TR-101 or Content Quality event occurred on an object, such as a source, that object would transition to a Warning state. If the same event continued to happen on the same object for a two minute period of time, the object would transition to an Error state. Upon transition to the Error state, an email notification would be sent to users based on roles and groups. Note that more critical events, such as a source going offline, immediate transition to an Error state and notifications are sent. WARNING TO ERROR ESCALATION Now the user can set the escalation time window and set an escalation occurrence threshold. Warnings will escalate to an Error if the object remains in a Warning state for longer than the escalation window or if the number of warnings within the escalation window is greater than the occurrence threshold. To edit the escalation window and occurrence threshold for a particular type of event, select an existing Warning from an object Event log and click Manage. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/LVnCe02ul1XhCHoOKlGpM_image.png" size="74" width="2052" height="558" position="center" showCaption="false"} Next, choose if you want to update the escalation for this type of event only on the current object, or all objects of this type, and set the escalation time window and occurrences threshold. You can also choose to disable escalations of this type of event from Warning to Error. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/IebAb3YrFdOf6eWHTKXX9_image.png" size="44" width="1210" height="1174" position="center" showCaption="false"} If you still want the object to escalate to an Error in the log files, but not change state to Warning, which is shown as orange indicators in the UI, select “Hide Warning state”. If you want this event to not be saved to the log and to not escalate to Warning or Error state and to not create notifications, select “Disable logging, DO NOT change state and DO NOT notify” . Once an event has been escalated to Error state, the event needs to not occur again for the length of the escalation time window for the object to fall back to OK state. If the event happens again during the time window, the clock resets on the time window and the object remains in Error state. For example, if the escalation window is set for 15 minutes, the object will only return to OK state if the event does not happen for 15 minutes. If the event happens 5 minutes into the 15 minute window, then a new 15 minute window begins where the event must not happen for the object to return to OK state. Existing Warning to Error escalations can be managed under Settings->Notifications. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/XPwyscAyJaaZ3YnFelB5x_image.png" size="34" width="800" height="446" position="center" showCaption="false"} Note: An Admin is able to overwrite a user’s escalation configuration, but the user can then recreate new escalation configurations. NOTIFICATIONS When an object transitions to Error state, a notification is sent. Previously, all notifications for an object could be muted and this capability has not changed; it can be useful for misbehaving objects. Now, Error notifications for each type of event, such as “Incorrect continuity-count”, can be enabled/disabled on a per user, per group, or per account basis. To disable an event notification, click on Manage in the Events list for an object in Error state. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/I4WJYtpb8AUdzHJt9mLAP_image.png" size="86" width="2062" height="540" position="center" showCaption="false"} Next, if you are an admin user you can enable or disable the notification as account default or group default or only for your user ID. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/bT-Kk82_mitmYlq8Yoq-4_image.png) Individual users can override this default just for their user ID. If you are not an admin user, you cannot set the account default or group default and can only enable or disable a notification for your user ID. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/0OEy1g9fTBqcoymUvlJsV_image.png" size="42" width="924" height="558" position="center" showCaption="false"} Next, you choose to disable the notification for only the current object or another object of the same type that you select from the pulldown or for all objects of the same type as the current object. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/J3pqxtwhMynzJMCqGXxHn_image.png" size="44" width="1084" height="658" position="center" showCaption="false"} FLAPPING DETECTION CONFIGURABILITY Flapping detection will automatically mute notifications on an object that repeatedly changes state. As long as the state changes continue to occur the object will remain muted. The user can now set the size of the time window, number of state changes, and cooldown period; previously it was hardcoded. Flapping detection parameters are set under Settings->Notifications. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/AuxfChEm0LmvcnIsR0MN-_image.png" size="48" width="808" height="444" position="center" showCaption="false"} ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/1wrxz-cPXpxSoFwOW9Zo2_image.png" size="82" width="1598" height="744" position="center" showCaption="false"} UPDATED LINKS FOR FEEDERS AND RECEIVERS The Configure link for opening the Feeder and Receiver UI remotely is now the Open Link. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/1fsK07ppD2PRfC2eGElYP_image.png" size="76" width="1810" height="726" position="center" showCaption="false"} UPDATED LINKS FOR BROADCASTERS The Configure link for opening the Broadcaster UI remotely is now the Open Link. The CPU and Memory history graph for the Broadcaster can now be found by clicking the Details link. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/fm92Z2cO2JnUH_6rWOYe6_image.png" size="86" width="2058" height="700" position="center" showCaption="false"} ## DTLS Broadcasters being managed by ZEN Master will now use DTLS to encrypt streams. The Broadcaster version must be v12.2 or later. ZEN Master will automatically create certificates for DTLS so there is no need to manually create and upload certificates. DTLS is enabled/disabled on each Broadcaster Cluster on the cluster configuration dialog. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/2FJ3lJuGVsByqBMfEeCCw_image.png" size="62" width="1286" height="1772" position="center" showCaption="false"} Feeders and Receivers connected to the Broadcaster can be v1.11 or v12. When using V1.11 Feeders and Receivers, select Ignore DTLS certificate on the cluster configuration dialog. Normally, new Broadcasters in a cluster with DTLS enabled will have DTLS configured automatically. If DTLS is not successfully configured, click the Details link on the Broadcaster and select Configuration and click Update Configuration. This will rewrite the configuration to the Broadcaster and restart it and will show error messages than can help debug any issues. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/SJo8bk-h0eCfXyhwPaEz9_image.png" size="82" width="1920" height="1020" position="center" showCaption="false"} USER DISABLE Instead of needing to delete a user account and then recreate it, user accounts can now be disabled by an admin and then re-enabled at a later time. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Wa8TqvJysJdK5v4Fk1gEA_image.png" size="74" width="1460" height="1008" position="center" showCaption="false"} TRANSCODING ZEN Master will now show more detailed transcoding errors. The transcoding profile dialog now allows the user to maintain the source aspect ratio. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/PzpGfBQNRA3Tx41wTXQKy_image.png) Transcoding enabled via ZEN Master now supports the Nvidia GPU and Intel GPU, if the Broadcaster reports that they are supported. ## EVENT FILTERING BY ACCESS TAG Events can now be filtered by Access Tags. ::Image[Events can now be filtered by Access Tags.]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/NR6xHdoiEp9j4CtXCjFV9_image.png" size="78" width="1270" height="602" position="center" showCaption="false"} SOURCE THUMBNAIL VIEWER Thumbnails will now be displayed even when the source is in an Error state. The display of thumbnails is now more compact allowing more thumbnails per page. Error messages are now displayed as an overlay on the thumbnail instead of in whitespace between thumbnails. Finally, thumbnails wider than 16:9 aspect ratio are now displayed properly. MINOR IMPROVEMENTS AND BUG FIXES • Changed Configure link to 'Open' for clarity • Fixed SQL error in gui when attempting to delete account owner, now shows a pretty error • It is now impossible to create 2 users with the same email • Fixed missing play button on sources with TR-101/CQA errors, play button will only be hidden if the source is offline. • Source selection in table when loading a new page, now paginates to the correct page instead of searching until there is only one page of data • Fixed source history graphs reloading on their own • Fixed 'duplicate entry' error on Firefox browser • Fixed push outputs reporting ok state when they are actually offline (caused by bad state reporting from the broadcaster) [title] ZEN MASTER September 2019 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be pushed to ZEN Master on September 9, 2019. STATS, UPTIME & OUTAGE, AND USAGE REPORTING ZEN Master now provides the ability to generate Stats, Uptime & Outage, and Usage reports. The user defines the granularity and time period for the report into a report configuration, then generates the report, and then downloads the result as an .xls file. To use the new reporting feature, an admin first needs to update Roles to include viewing or editing Reports. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/OMKox4Xfn_H07hhmBZPAo_image.png" size="80" width="1588" height="942" position="center" showCaption="false"} Next, users with Edit permissions can select Reports in the left-hand menu and click on the “+ ADD” button. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ZM8ELt_vkDV2Zl842AIKK_image.png" size="86" width="1868" height="1230" position="center" showCaption="false"} On the new report dialog, provide a name for the report, select the Access Tags, choose the report type and then configure the report parameters. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/CM-Jwk2mnONgtv7E3KhYJ_image.png" size="92" width="1852" height="1014" position="center" showCaption="false"} Creating and saving the report does not actually run the report, it just saves the report configuration so that it can be run at any time in the future. When you select an existing report configuration, you will see the basic details of the report in the Details tab. Click on “Generate Report” to bring up a dialog for generating the report. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/TcdUtGwQJPZdh6XDSv7h6_image.png" size="86" width="1856" height="890" position="center" showCaption="false"} Provide a name for this instance of the report. This name will be used for the Excel file that is generated and made available for download. You can also update the time period and time zone of the report from the default in the report configuration. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/yB7EP77a_tYflDtBDMflE_image.png" size="60" width="1096" height="764" position="center" showCaption="false"} Depending on their complexity, some reports can take quite a while to generate – minutes to hours. For longer duration reports, the recommendation is to use the largest granularity possible. The “Run History” tab displays the generated reports. they are in the process of generating. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/h6Z3ZErjGOtMzT7UQ5dXc_image.png" size="80" width="1858" height="926" position="center" showCaption="false"} After the report generation is complete, the results can be downloaded and deleted. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/mPCbCV6BdZrLaBTGyp3W1_image.png" size="78" width="1856" height="882" position="center" showCaption="false"} The data available in reports depends on the type of report – Stats, Uptime & Outage, or Usage – and the type of object being reported on. ### STATS REPORT The Stats report provides data on the following object types, as shown in the tabs of a downloaded .xls file. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/dyUFTFKC4O_lgOqXWzXMB_image.png" size="94" width="1882" height="82" position="center" showCaption="false"} The statistics available for Broadcasters, for instance, are the following: Name Max Disk Usage Max Nvidia Decoder Cluster Avg. Disk Usage Avg. Nvidia Decoder Access Tags Min Disk Usage Min Nvidia Decoder Time Max Install Disk Usage Max Nvidia Encoder Max Receive Bitrate \[kbps] Avg. Install Disk Usage Avg. Nvidia Encoder Avg. Receive Bitrate \[kbps] Min Install Disk Usage Min Nvidia Encoder Min Receive Bitrate \[kbps] Max CPU Max Nvidia Memory Max Send Bitrate \[kbps] Avg. CPU Avg. Nvidia Memory Avg. Send Bitrate \[kbps] Min CPU Min Nvidia Memory Min Send Bitrate \[kbps] Max Memory Max Nvidia Usage UdpRcvbufErrors Avg. Memory Avg. Nvidia Usage UdpSndbufErrors Min Memory Min Nvidia Usage Each type of object will have different available statistics. Below is an example of a Stats report on Broadcasters: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/mJ3_DDNOJA5Okv2-QFGQ-_image.png" size="88" width="1872" height="318" position="center" showCaption="false"} ### UPTIME & OUTAGE REPORT The Uptime & Outage report is available for Sources and allows you to see the uptime of Sources as shown in the example below: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/xXUJZWwLHS476kV9_zAQB_image.png" size="88" width="1838" height="316" position="center" showCaption="false"} The Outages tab show details on each Source outage, including TR-101 errors and CQA errors. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/fjKD_PAeas_5xGJ7AnukP_image.png" size="88" width="1898" height="524" position="center" showCaption="false"} Uptime and Outage reports can be used to quantify the quality and consistency of video feeds being provided by content originators. ### USAGE REPORT The Usage report shows bytes sent and active time for Sources and Targets and bytes transcoded for transcoded channels over the period of time for the report. It can be used to provide data necessary for usage-based billing. An example of a Usage report as shown below: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/-Ggm65TWrvLp21DdJMs4T_image.png" size="86" width="1900" height="350" position="center" showCaption="false"} SINGLE SIGN-ON USER AUTHENTICATION ZEN Master now supports single sign-on (SSO) user authentication via OAuth 2.0. Any OAuth 2.0 provider should work, but thus far Microsoft Office 365, Google Identity, and Okta have been validated with ZEN Master. Feedback on any others is welcome. Once SSO has been configured on a ZEN Master domain by an admin, the login screen will first have you choose the SSO provider, as shown in the following example. Normally an organization will only use one SSO provider, but ZEN Master can support multiple SSO providers or multiple instances from one SSO provider on one ZEN Master domain, where that is useful. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/fn4fsWk08U4ZGm2773ewN_image.png" size="30" width="626" height="686" position="center" showCaption="false"} By clicking the “Sign In with ZEN Master credentials” link at the bottom of the page, legacy ZEN Master accounts can continue to be used until the email address associated with an account has been associated with an SSO provider, upon which time the SSO system must be used to login to ZEN Master. For new SSO user accounts, there will be an account activation process with the SSO provider similar to the example below from Okta. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/d6L6F0PXJIXLkfUVr95hu_image.png" size="46" width="938" height="880" position="center" showCaption="false"} Once you select an SSO provider on the ZEN Master sign-in page, you will next enter your SSO credentials. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/zx4mFNeJmM0KyPA2X178N_image.png" size="44" width="704" height="1010" position="center" showCaption="false"} If your SSO configuration has multi-factor authentication enabled, you will complete that step next and will then be logged in to your ZEN Master domain. As usual, your permissions and groups will be set up by an Admin who has configured your account. ### CONFIGURING SINGLE SIGN-ON If you do not have an existing SSO provider, the example below demonstrates setting up SSO on Google Identity to highlight the key steps required to configure any SSO with ZEN Master. However, documenting setup of SSO providers, in general, is beyond the scope of this document. To configure SSO in ZEN Master, select Account Settings from the Settings menu. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/MvEyWrb69vlsElrtVuwyT_image.png" size="38" width="778" height="414" position="center" showCaption="false"} Next, click “+Create SSO Configuration” . ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/PQogOr0mvuENhcc2On_rD_image.png" size="74" width="1860" height="1064" position="center" showCaption="false"} The Create New SSO Configuration dialog shows us the information we need to get from the SSO provider as well as the callback URL information for ZEN Master that is provided to the SSO provider. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/tvk4fCkXUSa6Utmh_OeuT_image.png" size="50" width="866" height="898" position="center" showCaption="false"} For Google Identity Platform, start by enabling it. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/3IRCkezs7BkNtY10Ou7gw_image.png" size="78" width="1692" height="1012" position="center" showCaption="false"} Next create a new OAuth client ID. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ekEoyugVn1wkysGvuBuQ-_image.png" size="72" width="1764" height="922" position="center" showCaption="false"} Next, fill in the redirect URL from the ZEN Master form above and enter the Javascript origin, which is the same as the redirect URL without the path. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/1zN0nR48Mxv9EpO17DaDE_image.png" size="90" width="1888" height="1854" position="center" showCaption="false"} Download the JSON from the SSO provider as it will include the information needed for ZEN Master: • Authorization URL • Token URL • Client ID • Client Secret Next, click the OAuth consent setting link and fill in necessary details on the OAuth consent screen. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/AOkpkfxf1PKNOLykZDyvq_image.png" size="88" width="1212" height="1168" position="center" showCaption="false"} Finally, copy the pertinent data shown in bold from the downloaded JSON file `{"web":` `{"client_id":"123456533461-rb2qo4ih2asi5sl5dq8nao0ukdbslrr7.apps.googleusercontent.com",` `"project_id":"tim-zen-master-integration",` `"auth_uri":"https://accounts.google.com/o/oauth2/auth",` `"token_uri":"https://oauth2.googleapis.com/token",` `"auth_provider_x509_cert_url":"https://www.googleapis.com/oauth2/v1/certs",` `"client_secret":"12345E3Q4begAQdjYukZkj_o",` `"redirect_uris":["https://zixi.staging.zixi.com/auth/oauth2/callback"],` `"javascript_origins":["https://zixi.staging.zixi.com"]` `}` `}` into the SSO configuration form in ZEN Master. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/nF7BvcYX7uDZ4UtTR4VyS_image.png" size="52" width="962" height="986" position="center" showCaption="false"} When ‘Allow pre-registered users only’ is enabled, only users who already have an account setup in the ZEN Master domain will be able to log in via SSO. When it is not enabled, any user in the SSO can log into the ZEN Master domain but they will not have membership in any Access Groups and will not have any permissions until an admin adds these. When a ZEN Master domain is first setup for a customer, a non-SSO admin account will be created. That admin can then set up SSO, including for the email address of that admin account, and then login via the SSO. It is possible to have only SSO accounts accessing a ZEN Master domain or, if desired, it is possible to have a mix of SSO and non-SSO accounts. An example of the later case is everyone within an organization would login to ZEN Master via the organization’s SSO but partners or others outside of the organization can be given non-SSO accounts in the same ZEN Master domain. NETWORK BONDING Zixi's Network Bonding feature enables you to divide a stream into several network paths by utilizing multiple NICs and IP links and then subsequently reuniting the divided streams at the Zixi Broadcaster. Network Bonding supports Push streams from the Zixi Feeder to the Zixi Broadcaster. To enable Network Bonding, edit the Source and select Any for Feeder Output NIC and then enable Bonding. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/NXSIxTUQQfXB8SR6iGP4A_image.png" size="80" width="1808" height="1748" position="center" showCaption="false"} Under the Details tab of the source you will see the NICs with their IP addresses that are being used in the bonded connection as well as the bitrate of data being send out over each link. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/CQ8OQG1nvN37Qs3rkygy2_image.png" size="80" width="1860" height="912" position="center" showCaption="false"} In the History tab for the source you can see a graph over timer of the jitter, RTT, and bitrate of each IP link. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/YjzwPin9LFvllf5HSbFu2_image.png" size="90" width="1838" height="1108" position="center" showCaption="false"} ZIXI PLATFORM V13 FEATURES With the general availability of the Zixi Platform V13, the following new features are now available in ZEN Master when using V13 Broadcasters. ESTIMATED PSNR The Zixi Broadcaster is now able to estimate the Peak Signal-to-Noise Ratio (PSNR) of a Source video without a need for the reference video. Estimated PSNR (ePSNR) is calculated for each frame of the video and is displayed in ZEN Master as a continuous graph and as a heat map of histograms. To view the ePSNR graph, select the History tab when viewing a Source and expand the Content Analysis graph. The scale for ePSNR is on the right axis. If there are multiple video PIDs available in the Source content, the desired PID to be viewed can be selected. The resolution of the graph depends on the zoom level and is as low as 1 datapoint per minute. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/gpeBqv9WtJg-k__zRlxs1_image.png" size="80" width="1840" height="808" position="center" showCaption="false"} To view the ePSNR heat map, select the History tab when viewing a Source and expand the Encoding Quality graph. Each vertical column in this graph represents a histogram of the ePSNR values of all video frames over a 10 minute window. The scale for ePSNR is 11 to 60 with higher values being higher quality. A higher encoding quality video source will produce a heat map with red color at the higher end of the scale. If there are multiple video PIDs available in the Source content, this graph only shows data for the first video PID found in the Source content. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/uVOpGEBSvhnZpIrWv3eIp_image.png) ePSNR in the Zixi Broadcaster may be a separately priced and licensed feature. ePSNR analysis does not support MPEG2 or HEVC/H.265 content, but does support most flavors of H.264 content. ### STREAM DELIVERY Working in tandem, the Zixi Broadcaster and Zixi Receiver are now able to identifies dropped packets from a Broadcaster to a Receiver on a per PID basis. The impact of dropped packets for video or audio PIDs is corrupted video or audio. The impact of dropped packets for Ad markers (SCTE-35) is those Ads would not be properly loaded and displayed in the downstream system. In ZEN Master, the percentage of successfully delivered packets is displayed on a graph. The resolution of the graph depends on the zoom level and is as low as 1 datapoint per minute. To view the stream delivery graph, select the History tab when viewing a Target and expand the Stream Delivery graph. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/87m6WmjJRg13-NjlCqObK_image.png" size="84" width="1878" height="736" position="center" showCaption="false"} Stream Delivery analysis in the Zixi Broadcaster may be a separately priced and licensed feature. ### STREAM QUALITY ANALYSIS Stream quality analysis identifies missing or corrupt video or audio frames from a Feeder to a Broadcaster on a per PID basis. A frame is considered corrupt if the frame’s data is completely missing, partially missing or if it depends on a frame whose data is completely missing or partially missing. For example, if an I-frame is corrupt then it as well as all following P-frames until the next I- frame will be corrupt as well because they depend on the I-frame and previous P-frames. If a P-frame is corrupt, then the following P-frames up to the next I-frame will be corrupt. In ZEN Master, the % of good frames, i.e. not corrupt and not missing, out of the total frames per PID is displayed on a graph. The resolution of the graph depends on the zoom level and is as low as 1 datapoint per minute. To view the stream quality graph, select the History tab when viewing a Source and expand the Stream Quality graph. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/-hxZQqowsEFOUFSE-pf9u_image.png) In the example above we see 93% good frames, which is not the 100% we would normally expect. If we analyze the network statistics, below, we see that at that particular point in time there were some network packets that needed to be recovered and all of them were successfully recovered. This tells us the missing or corrupt frames did not occur during transmission but instead occurred in the source. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/JNSfGvGQM9peqrwzO0ROx_image.png" size="74" width="1844" height="644" position="center" showCaption="false"} If we look at the TR-101 analysis in the Content Analysis graph, we see that there were CC errors during that time period. Since there were no unrecovered packets during transmission, the CC errors are in the source stream itself and that accounts for the bad frames shown in the stream quality graph. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/l7uHt-imDzYxI5pqK-kus_image.png" size="76" width="1830" height="620" position="center" showCaption="false"} Stream Quality analysis in the Zixi Broadcaster may be a separately priced and licensed feature. ### TRACEROUTE The Zixi Broadcaster now collects traceroutes from Feeders to the Broadcaster and from the Broadcaster to Receivers. To view the current traceroute results in the ZEN Master UI, select the Trace Route tab when viewing a Source or Target. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/jE7KrzHqk64mLf57gJVSN_image.png" size="94" width="1826" height="738" position="center" showCaption="false"} Click the refresh button to update the traceroute results. Historical traceroute results are also available on the History tab of Sources and Targets. The history graphs shows round trip times (RTT) to each server in the route between the Source and Broadcaster or Broadcaster and Target. The resolution of the graph depends on the zoom level is as low as 1 datapoint per minute. If there are persistent large round trip times through particular servers, a network reconfiguration may be necessary to alleviate the issue. When routing through fixed fiber or MPLS connections, the round trip time history graph may prove useful in debugging and resolving network bottlenecks. In the example displayed below, routes through the AWS network are continuously optimized and thus we do not see persistent large round trip times. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/EW6Bv-616l8y-T9hoqfoo_image.png) To see the host IP address and round trip time of a particular server, hover the mouse over one of the plots and a popup will display this information. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/VciGt7UiWSQjuMY76LOKg_image.png) Traceroute analysis in the Zixi Broadcaster may be a separately priced and licensed feature. ### PACKET TIMING ANALYSIS Packet timing analysis displays a histogram of packet arrival time (recovered if necessary) from Push and Pull Sources. This analysis can be used to see a history of latency from the Source and to fine tune latency targets. In the graph, the vertical axis is time in milliseconds with the max value set to the latency target and the horizontal axis is user specified minutes, hours, days, etc. Darker red in the histogram means more packets arrive at that particular latency. In the graph below, most packets arrived under 1 second but some arrived just over 1 second. Since the target latency was set to 4 seconds, FEC in the Zixi algorithm would have been essentially disabled. Looking at the historical data, if desired, it would be reasonable to set the target latency around 1 second and then the dynamic use of FEC in the Zixi protocol would be used when necessary. Clearly, setting a latency target of 500ms under these network conditions would not be reasonable. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/sokfR9kVzjxLabvozyNMJ_image.png" size="88" width="1858" height="914" position="center" showCaption="false"} WRITE HLS/DASH TO MEDIASTORE The Zixi Broadcaster now supports writing HLS and Dash streams to AWS Elemental MediaStore. In the ZEN Master UI, select HTTP for the target type and then select MediaStore for the type. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/oO774lzdhpRwiXNi2QSy9_image.png" size="52" width="1048" height="544" position="center" showCaption="false"} ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ESd3Ecfpp5ni54wnaBBM7_image.png" size="52" width="1040" height="1774" position="center" showCaption="false"} ### AAC-HE AUDIO ENCODING Transcoding in the Zixi Broadcaster now supports AAC High Efficiency audio encoding. In the ZEN Master UI, select the desired encoding style in the Audio Profile pull down when Audio transcoding is selected. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/1CF30onmCOd9sAlR9M3Mb_image.png" size="62" width="980" height="740" position="center" showCaption="false"} ### VIDEO CROPPING (ZM-237) Transcoding in the Zixi Broadcaster now supports video cropping by percentage or pixel ranges. The cropping is specified on the transcoded channel definition as shown below. The cropping is specified on the input and thus all renditions of the stream will be cropped the same. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/fyepx1xpmphFizRR5f4UC_image.png" size="80" width="1842" height="1244" position="center" showCaption="false"} ### MINOR IMPROVEMENTS AND BUG FIXES • Added UDP Send errors to Broadcaster History (ZM-278) • Added flag to force users to update password on next login (ZM-279) • Fixed issue where unable to delete domain as Zixi admin (ZM-268) • Fixed incorrect channel diagram (ZM-270) • Fixed REST API For Targets of Pass Through Channels Missing Channel ID (ZM-261) • Fixed no play button for Azure Targets (ZM-271) • Fixed issue where max Bit Rate does not display on ZENM when editing pre-existing source (ZM-269) • Fixed issue with forced user logout [title] ZEN MASTER June 2023 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be included in the ZEN Master June 13, 2023 release. Features The following new features were implemented in this release: • IDP MOCA Auto-Incidents In this release we have made a major update to IDP Multi-Object Correlation Analysis (MOCA) to auto-generate incidents based on any errors observed by ZEN Master, not just unrecovered packets. Incidents provide a roll-up of errors when they become particularly significant so you can see outages in a single view with context to help you understand what’s going on and how to fix it, and to reduce the noise of low-level alerts. On the left side is the list of affected objects. On the right, the root cause is at the top and related measurement graphs are listed below. The description of the incident shows some root cause details including the shared resource and the incident type. • **Incident Definition and Thresholds** Incidents are reported when there are 3 or more Sources or Targets having errors at the same time that share a common resource, and when at least 50% of the objects that share that resource are experiencing errors at the same time. Errors that happen on these objects within 10 minutes of a previous error are grouped together into the incident. It is possible to have multiple related incidents if there is a period of more than 10 minutes without any errors. In some cases, if there are multiple shared resources the system may also report multiple related incident records. • **Shared Resources** \- Client Network – the network where Source or Target objects are connected. Networks are identified by network ASN (Autonomous System Number), country code, and region code. For example, US\_OH\_123 is a network in Ohio in the United States with ASN 123. \- Server Network – the network where a Broadcaster is connected. \- Network Path – the connection between a Source and a Broadcaster. \- Broadcaster – the shared Zixi Broadcaster. •** Types** Incidents can be of type Network Error or Object Error. Object Error incidents can be triggered by a TR101-CC error on a Source, or a Broadcaster max CPU error, or any error reported in ZEN Master. •** Root Cause, Blast Radius** The Root Cause description for an auto-generated incident includes the incident type, the shared resource, and some details about how many objects that share the shared resource (a network path, for example) are involved in the incident (sometimes called “impact” or “blast radius”) compared to the total number of objects connected. Examples: \- Client Network Error: 57% of Sources (8/14) on network US\_OH\_123 have network errors. \- Object Warning – Network Path: 67% of Targets (4/6) on network path (US\_OH\_123- US\_CA\_456) have Object Errors. In Incident View, Object Error incident records show the relevant errors for the selected time- period for all related objects, as well as network and other measurement graphs. • Table View for Grids. The ZEN Master Grid screen now allows the user to toggle between the standard Grid view, and a List View using the new tables architecture: To toggle the view, choose the list icon from the view icon pair above the Grid: With the new view selected the User gains all the additional filter controls available in standard tables, as well as the displayed / hidden column controls and the ability to generate a quick report. • Broadcaster customization is now available on Azure and GCP Clusters. Already supported for ZEN Master managed AWS Scaling Clusters, customization of a Broadcaster’s name and private / streaming IP settings is now supported for Clusters launched in both Azure and GCP. This can be configured in the Create New Broadcaster dialog when selecting ‘Add Broadcaster’ in the Cluster details section, or via the ZEN Master API: • AgentZ is now available for manual installation without causing a Broadcaster restart. Whilst the AgentZ telemetry gathering tool can still be installed from ZEN Master, it can now also be installed manually on a Broadcaster. Unlike the ZEN Master install, the manual install does not force a Broadcaster restart. The manual AgentZ installer can be downloaded from the Zixi Customer Portal, and instructions are provided in the Zixi AgentZ User Guide. • User management security notifications. A new “Account Management” log object is introduced to log, track, and search for updates and changes to security objects including: \- Users \- Groups \- Roles These log entries are available for Admin user only, and can be searched for in the Event Log filter: All Admin users will receive specific Account Management email notifications for changes to any security objects in the ZEN Master environment: If needed, Admin Users can opt out of receiving these emails in the ‘My Account’ section: • Improved support and useability for AWS Elastic IP’s. When using Elastic IPs for AWS Scaling Clusters, ZEN Master now introduces an option to prevent instances from launching if there are no more designated EIP’s available. The option, included in the Cluster advanced configuration settings, will explicitly prevent AWS from launching a new instance when no further Elastic IP addresses are available, to guard against a Cluster adding a Broadcaster with an unknown public IP address: Regardless, the Cluster now displays available/used Elastic IPs and provides UI warnings when launching instances where there are none are available. • Broadcaster system logs can now be downloaded via the Broadcaster ‘Details’ page. The Broadcaster details page now provides a link to download Broadcaster system logs directly, without the User needing to navigate and log-in to the Broadcaster GUI directly: Additional Improvements and Changes The following additional improvements and changes were implemented in this release: • Filtering in tables now evaluates on Error/Warning message contents: o The event log message is now an option when using ‘Add Filters’ in the Sources and Channels tables: • When selecting transcoding profiles, the list now displays codec. • Private IP streaming now works on Clusters with DTLS enabled. • Improved error handling in case users break ZM AWS IAM role. • Added AWS instance ID to Broadcaster details page. • Renamed VIP tags to Priority. • Disabled AZ rebalance process for AWS Clusters. o This will only affect new or updated Clusters. • Added Pad to CBR options to Demux Sources. • Ignore PCR Accuracy errors when monitoring VBR streams. • Multiplex Sources now support auto-pulls: o Requires Broadcaster v16.7. • Added options to customize the cloud-init launch script on AWS Clusters. • PID mapping changes are now tracked and displayed for all PID mapping modes. • Event log object names are now links to the specific objects. • Created features guide for new Tables. • Automation task delay is now limited to 15 minutes. • ZM Tags now propagate to Azure. • Added Billing Codes to Zixi Push Targets. • Applied new tables everywhere + other UI improvements. Bug Fixes The following issues were resolved: • Fixed duplicate incidents. • Missing SCTE-35 alarm no longer stops working after an hour of missing SCTE messages. • Users unable to reset their own password. • Some fields always blank in Grids. • Editing Inter-Cluster Source no longer creates an infinite loop. • Fixed diagrams showing broken active Broadcaster in some cases. • Fixed unable to enable targets in some cases. • Removed Alternative host from Zixi push output in AWS MediaConnect targets. • Automation tasks will no longer fail if execution takes longer than 3 minutes. • Fixed Grids in Grid Groups missing an All-Good indicator when there is nothing to display in the Grid. • Fixed pull connections to Broadcasters/ZECs not reconnecting on zero bitrate when a better Source is available. • Requires Broadcaster v16.7. • Failover Sources/Channels will now work with auto-pulls. • Added missing force delete options when deleting multiple tags. • ZM will now ignore certain irrelevant Broadcaster errors when redirecting pull connections, e.g. full hard drive. • Update default adaptive FEC settings on Zixi Pull Sources. [title] ZEN MASTER January 2019 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates were pushed to ZEN Master during the month of December 2018. NVIDIA GPU TRANSCODING SUPPORT ZEN Master now allows you to select Amazon EC2 G3 instances, which provide access to NVIDIA Tesla M60 GPUs for hardware accelerated transcoding and can be used in conjunction with Broadcaster v12.3.32721 or later. The AWS g3.4xlarge reserved instance cost, for example, for a 24/7 channel with 8 typical output renditions will be about 40% of the cost of using the software transcoder on a c5.9xlarge instance. On demand pricing for g3.4xlarge instances is about 37% of the cost of on demand c5.9xlarge instances based on 10 channels with 8 typical output renditions running on a g3.4xlarge instance and 5 channels each running on two c5.9xlarge instances. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/kJAG9biAOaYEP56-G33hs_image.png" size="62" width="1224" height="944" position="center" showCaption="false"} MINOR IMPROVEMENTS AND BUG FIXES • Implemented a retry mechanism when accessing Feeders and Receivers to prevent false positive offline errors. This mechanism already existed for Broadcasters. • Fixed transcoding profiles with 'High' profile not working. • Fixed an issue with Broadcaster sources flapping between OK and Error state when they are actually in an Error state. • Fixed an issue with tunnel/redirect servers losing DTLS support if the AWS instance fails. [title] ZEN MASTER September 2023 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be included in the ZEN Master Sept 12, 2023 release. NOTE: An Updated version of this document will be made available after the release. Features The following new features were implemented in this release: • ZEN Master’s AWS IAM policy has been updated and will become REQUIRED in early 2024; it is recommended to update now. o The policy change allows ZEN Master to support changes to the AWS instance launch system that will come into effect at the beginning of 2024. o Updating the IAM Policy of the AWS account will be required ahead of the Dec. 31st AWS cutoff date. o Customers can update their policy using the JSON documented under Configuration, AWS Accounts, Documentation. • Object Version Change Tracking o Change Tracking is now implemented for all major object types including ZECs, Broadcasters/Clusters, Sources, Channels, and most Target types. o The feature is not yet implemented for MediaConnect/MediaLive Channels and Targets. o The Change Tracking panel logs the change history and user and provides individual, and batch revert tools. IDP - New Insights and Incidents integration: o Insights - Multi-select Broadcasters, Sources, or Targets and clicking the Insights button displays their metrics on a single panel allowing comparison and easy identification of outliers. o Incidents - On Source or Target details page there is now an Incidents tag showing all the Incidents the selected object has been in. • IDP - New Incidents dashboard o Easier at-a-glance comparison – compare metrics from different objects in the same graph, rather than having to scroll through separate graphs for each. o Graph annotations – allows user to mark points on the timeline, note important moments during the incident, or external events such as maintenance or equipment failures. • Show Broadcasters without Cluster grouping o Users can now toggle the Broadcasters table between Clusters and Broadcasters to list and work with a table of all Broadcasters, providing the appropriate column options and multi-selection tools. • Broadcaster recovery o When deleting or disabling a Broadcaster the user is now presented with an option to migrate all current objects to another Broadcaster. o Triggering the recovery is currently manual-only. • Target PID Mapping o PID Mapping, previously available in Sources, is now available on Targets o The feature supports configurations for delivering multiple PID Mapped variants of a single Channel to meet differing target requirements. • Private IP auto detection o On AWS/Azure/GCP broadcaster ZM will automatically track the current private IP allowing for private IP streaming without manual configuration. • TAG Multi-viewer integration o Configure TAG MCM-9000 instance to create new multiview Source in ZEN Master from user selected ZEN Master Sources. • Live events re-work o The update provides a revamped Live Event Dashboard to better accommodate new and future features. o Custom stages allow users to add and rename as many event stages as needed for the event, such as ▪ ‘Pre-game build up’ ▪ ‘post-match studio analysis’ ▪ Etc. o Clip insertion tools allow the user to specify one or more promo clips which can be played out from clip-start on stage transitions or manual insert. Once the clip is finished the output reverts to the primary feed. Additional Improvements and Changes The following additional improvements and changes were implemented in this release: • Added In-application Features Guide on Incidents page • Added Features Guide for Tags and User permissions • Added support for AWS g5g - ARM with Nvidia GPU instance types • Added an Active Incidents widget to the main Dashboard • Added Min/Max bitrate graphs for MediaConnect Sources • Added maintenance, muted, and muted\_until to Broadcaster API calls • Added all Failover Modes to Zixi Pull Targets o Alt. Host o Stream Switch o Hitless Merge • Added auto-bonding support for Zixi Push Targets o The configuration will use all NICs available to the Broadcaster at the time of creation • Added "Ongoing" Incident count to the left-side main navigation menu • Added pagination support to Failover Channel API • Updated AWS AMIs that ZEN Master uses for Broadcasters to reduce costs and improve security o Initially this will only apply to new or updated Clusters and not AWS g5g instance types • Exposed auto-latency toggle on Zixi Pull Sources • Exposed verify Stream ID for SRT listener Sources • Exposed Stream ID for SRT caller Targets • Failover Channels are no longer limited to 3 Sources • De-escalating warnings/errors now state when the status will clear • Active Objects table enhancements: o Filters o Limited multi-select and multi-edit • Active Source in a Failover Source/Channel is now highlighted in diagrams and details pages • Broadcaster Private/Public IPs are now displayed in the Broadcaster Details panel • Failover Sources now allow switching back to a Preferred Source (requires Zixi Broadcaster v17) • Network IDs are now consistent in Incidents and Networks • Saving after editing an object will now automatically paginate to the page that has the relevant object in the table Bug Fixes The following issues were resolved: • Fixed MediaConnect sources not using DTLS when pushing to a ZM cluster • Fixed Targets not displayed on Grids when selecting with Tags • Fixed Billing Codes applied inconsistently on auto-pulls • Fixed v16+ Broadcasters issue on GCP Nvidia machines • Fixed incorrect instance type displayed on AWS broadcasters after an auto-recovery if the type was changed on the Cluster • Fixed missing validation allowing users to create infinite loops with Sources that use other Sources, such as an Inter-Cluster Source that pulls itself • Fixed multiple issues with non-Admin Users unable to use ZEC Sources • Fixed "Failed to acquire streaming IP address" warning spam under some over-load conditions • Fixed object locations defaulting to North Dakota • Fixed multi-editing Live-Events providing an option to update events profile • Fixed missing error message when attempting to delete a PID mapping profile that is already in use • Fixed an issue preventing WebRTC playback from working when the Source is working but has de-escalating errors • Fixed MediaConnect source details page failing to open from links • Fixed downloading an Event Log failure for some Administrator users when filtering by Tags • Fixed disabling/enabling Source component of multiplex source incorrectly affecting related Program in MPTS Source • Fixed missing error handling when creating conflicting SRT targets • Fixed SRT pull Target hostname configuration not working when the Target is assigned to a MediaConnect Flow • Fixed AWS IAM role failing to update in AWS backend on Cluster updates • Fixed users being prevented from editing the Encryption mode on SRT Targets • Fixed c7g instances never launching in AWS • Fixed an unexpected AWS error when editing very old AWS clusters • Updated AWS IAM policy to remove harmless warnings in AWS console • Non-Admin users will no longer get logged out of ZM when navigating to the Networks page • Deleting a Remote-Access object no longer leaves the object in a broken state in the table • Attempting to delete a Broadcaster with Termination Protection now shows proper error message • PID mapping failures now have a detailed error message [title] ZEN MASTER February 2019 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates were pushed to ZEN Master on February 4, 2019. CONTENT QUALITY ANALYSIS ENABLED/DISABLE Content Quality Analytics (CQA) can now be enabled and disabled when creating a new source or editing an existing source. By default, CQA is enabled when a new source is created. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/GlrHv-G4lVQwoJur3mOLo_image.png" size="80" width="1722" height="1512" position="center" showCaption="false"} DASHBOARD CONFIGURATION The user can now select which panels are displayed on the dashboard page. The settings are preserved in local storage and will be preserved on the same browser after logout and login. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/8Gjjmz-VutkuUhvEZCRGg_image.png" size="68" width="1204" height="484" position="center" showCaption="false"} TRANSCODING UPDATES ### NVIDIA HEVC TRANSCODING Previously ZEN Master only allowed AWS g3s.xlarge and g3.4xlarge NVIDIA GPU instances to be selected for scaling Broadcaster clusters. These instance types do not support HEVC decoding. Now, ZEN Master also allows p3.2xlarge NVIDIA GPU instances to be selected; this instance type supports both HEVC decoding and encoding. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/9LcbHPEJsp_z7IeDxdq8E_image.png" size="64" width="1220" height="842" position="center" showCaption="false"} ### RENDITION PLAYBACK Under the Details tab, ZEN Master now allows you to play the stream for each rendition of an adaptive transcoded channel. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/eA_OwVzOxcImRgeiydnTZ_image.png" size="76" width="1812" height="676" position="center" showCaption="false"} ### PROFILE TOOLTIP Under the Details tab, ZEN Master now provides a tooltip showing details of the transcode profile. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Wrx9bRb4uGafoi8XiUPqI_image.png" size="78" width="1780" height="674" position="center" showCaption="false"} ### PULL TARGETS WITH OUTPUTS Pull targets can now be configured with multiple Receiver/Broadcaster outputs. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/lsF5vSfrhSGrWNnBQB9ui_image.png" size="52" width="940" height="980" position="center" showCaption="false"} BROADCASTER NAMES When adding a Broadcaster to a manual scaling cluster, there is no longer a length restriction on the name. Also, instead of being locked after a Broadcaster is created, the Broadcaster name can now be edited any time. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/-3j8cVDg_IqVXXyprZWyR_image.png" size="84" width="1990" height="474" position="center" showCaption="false"} ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/7i6YtiUKBWs44KROTyGAv_image.png" size="52" width="920" height="756" position="center" showCaption="false"} ## MODIFYING AWS CLUSTER SUBNETS Instead of being locked after a cluster is created, AWS cluster subnets can now be updated any time. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/2l2UxJuadqpncglAOaxGa_image.png" size="56" width="960" height="768" position="center" showCaption="false"} AWS IAM POLICY UPDATES The AWS IAM policy was updated to allow the AWS Autoscaling activity log to be merged into the ZEN Master events log. The user must update their IAM policy in AWS to take advantage of this change. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ABDlgx8mY-dWVGKDFtCqi_image.png" size="86" width="1752" height="682" position="center" showCaption="false"} MINOR IMPROVEMENTS AND BUG FIXES • ZEN Master now monitors the Authorization configuration status on v12.3.32764+ Broadcasters • Fixed history graphs not updating when selecting a different object • Invalid/expired license will no longer prevent editing of an AWS cluster • Fixed licenses page becoming unresponsive if user adds an invalid license key • Fixed Broadcaster upgrades that were not working through ZEN Master tunnels • Worked around Akamai dot (.) requirement to support publishing adaptive channels to Akamai; requires creating new sources • Fixed http target monitoring throwing errors if target path ends in a master playlist file, e.g. https\://zixi-cloudstream.s3.amazonaws.com/woooozer/master.m3u8 • Removed extraneous information in event Log reports when there are warnings in the log [title] ZEN MASTER February 2021 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates were pushed to ZEN Master on February 2, 2021. Improvements Support for Existing AWS MediaConnect Flows Previously, existing MediaConnect Flows could be defined as a new Source in ZEN Master or new MediaConnect Flows could be created in ZEN Master. Now, existing AWS MediaConnect Flows can be imported into ZEN Master and will then be managed with ZEN Master. Note that some MediaConnect specific features, such as Entitlements and VPC interfaces, are not currently supported. Support for AES Decryption on Zixi Sources For Zixi Sources from devices that are not managed directly by ZEN Master and have AES encryption enable, they can now be decrypted. These could be Push Sources of type “other” or Pulls from an external Source. The same static key that was used to encrypt simply needs to be entered when defining the Source. Zixi Sources that are managed by ZEN Master use DTLS session-based encryption if enabled by the user when defining the Source. Support for File Based Sources A Source can now be created using a file that already exist on a Broadcaster. To create a file based Source, a specific Broadcaster needs to be selected. As usual with Broadcasters, the files need to be transport stream (.ts). The files are expected to be in the Root folder as defined on the Broadcaster. The default Root folder is currently /zixi/zixi\_broadcaster-centos7-transcoder/files for Broadcasters spun up with ZEN Master; this may change with OS updates in the future. Manually created Broadcasters may have a different Root folder and the Root folder on any Broadcaster can be changed by remotely accessing the Broadcaster UI from ZEN Master. Note, ZEN Master does not provide for uploading and managing files on the server hosting the Broadcaster. Numerous web-based file managers and even SSH can be deployed for remote file management on the server hosting the Broadcaster. Included below are additional improvements in this ZEN Master release: • Added “copy to clipboard” buttons • Added report button to all major tables Bug Fixes • Fixed zoom in/out on Channel diagrams • Active Broadcaster/client IP now logged on Pull Target connection • Fixed SRT graphs showing values too large by a factor of 1 million • Fixed an issue with creating PID Mapping sources that have custom pass rules • Fixed an issue with SRT target stuck in Pending/Error states • Various UI Improvements [title] ZEN MASTER June 2022 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be included in the ZEN Master June 21, 2022 release. Features The following new features were implemented in this release: • Live events and occasional use scheduling and management including new failover Channels. This feature is beta and hidden by default. If you have live event and occasional use workflows, please speak with your Zixi representative about getting a demo and access to the beta. Additional Improvements and Changes The following additional improvements and changes were implemented in this release: • Added new AWS Intel/AMD instance types - c6a.large, c6a.xlarge, c6a.2xlarge, c6a.4xlarge, c6a.8xlarge, c5n.large, c5n.xlarge, c5n.2xlarge, c5n.4xlarge, and c5n.8xlarge. Older instance types are now only visible by enabling the "Show Outdated Instance Types" checkbox. • Added support for YouTube Live HLS HTTP Targets • Added input NIC selection on all relevant Sources - Zixi Pull, PID mapping, Inter-cluster, SRT, and RIST • Added support for DVR playlists in HLS Targets • Added Location and Network to Broadcaster details page • Added support for SRT Targets on AWS MediaConnect Channels • The Licenses page has been removed. See the Zixi Customer portal - portal.zixi.com for license monitoring. • The Broadcaster link in diagrams now takes you to the Broadcaster details page instead of the Cluster Bug Fixes The following issues were resolved: • Fixed issues with objects immediately going into error or warning state on create or enable • Fixed failover Source not recovering from component Source reconnection or enable/disable • Fixed PID Mapping not working on Sources originating from AWS MediaConnect • Fixed multiple issues with AWS MediaLive integration • Fixed failover Sources labelled as “Hitless" when the merge mode is set to non-hitless • Fixed issue with billing codes not always saved correctly • Fixed issue with dynamic Target output names on Broadcaster not matching ZEN Master configuration • Fixed issue with AWS MediaConnect Targets not displaying the correct URL in the Target column • Fixed multiple issues with Maps • Fixed Targets not assigned to Adaptive channels showing up in the Channel’s Targets list • Fixed reporting errors on Targets that are working properly when using load-balanced Clusters • Fixed Broadcaster auto pulls not being cleaned up in rare scenarios • Fixed broken export/print on IDP Incidents and not using saved time range • Fixed issue with API for create RTMP Targets not returning resource tags [title] ZEN MASTER November 2019 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates were pushed to ZEN Master on November 26, 2019. SCHEDULING AND AUTOMATION ZEN Master now includes the ability to create sets of tasks and then execute those sets of tasks with the push of a button or on a user defined schedule. This capability is found under the Automation menu item. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Ce_BK8uxUMIbA4QQuuccA_image.png" size="26" width="612" height="922" position="center" showCaption="false"} To define a set of automation tasks, click the ADD button, enter a name for the task set, and define the access tags to control users that will have access to this task set. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/sY4MJqsTar7BEDHxetWb6_image.png" size="58" width="1536" height="756" position="center" showCaption="false"} Initially an automation task set will have no defined tasks or schedules. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/LODBCATxQ1H9EjFRAU2jX_image.png" size="76" width="1748" height="1262" position="center" showCaption="false"} To add a task, click ADD TASK under the Tasks tab. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/89mXJwcXJ8mT4SqAek3XD_image.png" size="82" width="1704" height="588" position="center" showCaption="false"} A variety of tasks can be automated, as shown in the Task Type pulldown. After providing a name for the task, select a task type. Each task type will have a relevant set of fields to complete. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/3XMIjbO0HmuT5kRmjOqgQ_image.png" size="68" width="1302" height="1470" position="center" showCaption="false"} Tasks in a task set will be run immediately by default, when a task set is run. If desired, a start time relative to the start of execution of the task set can be defined allowing for tasks to be sequenced. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/vQp0IJZne_ooQIbyqaWH2_image.png" size="90" width="1924" height="514" position="center" showCaption="false"} Once the tasks in the task set are defined, a schedule to execute the task set can be defined. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Kv7CIPx3lw-xoNNJVK6XR_image.png" size="80" width="1906" height="366" position="center" showCaption="false"} A schedule allows you to set a start date/time, end date/time, and the repeat frequency including once, daily, weekly, monthly, last day of the month, or repeat on a provided number of minutes, hours, days, weeks, or months. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/6e9kztwD91grP2Yf35R0a_image.png" size="64" width="1272" height="1764" position="center" showCaption="false"} Multiple schedules can be defined for a task set to accommodate complex schedules. The Schedules tab shows all of the defined schedules with start date, end date, and the next execution time. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/0tT52noOdy9z7CbnFAfo7_image.png) The Events tab shows a history of task sets being created and scheduled, and a status of tasks that were executed. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/NkjUo90FiD3XVgYATnGBv_image.png) ### MINOR IMPROVEMENTS AND BUG FIXES • Added the following AWS instance types for Broadcaster Clusters: g4dn.xlarge, g4dn.2xlarge, g4dn.4xlarge • Adjust error/warning message to specify the correct cloud provider – AWS, Azure, or GCP (ZM-311) • Added API for Active Broadcaster ID for Targets (ZM-379) • Added Max VA Diff setting to transcoding profile video advanced page (ZM-388) • Added warning that player might stall if less than 5 segments are configured (ZM-389) • Removed unsupported Channels element from selection options for stats reports. (ZM-394) • Improved events search performance with database optimizations (ZM-65) • Improved cluster Pull target uniform load balancing (ZM-163) • Fixed inter-cluster Sources using Target cluster DTLS config instead of Source cluster (ZM-372) • Fixed issue where failed launch of Broadcaster on GCP stays in warning state (ZM-377) • Fixed UI errors when editing inter-cluster Source (ZM-383) [title] ZEN MASTER March 2023 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be included in the ZEN Master March 02, 2023 release. Features The following new features were implemented in this release: • Re-designed "state" based alerts management and escalation mechanisms. The ZEN Master alert escalation mechanism has been updated to provide better controls for determining when, or when not, underlying issues require escalation to the user via either a warning state, or a full error alert. Previously, ZEN Master used the number of contiguous events in a polling-cycle window, to escalate from good to warning, and from warning to error, before deescalating at the end of a clean window. In the updated model the following enhancements and clarifications are introduced: \- For state-based alerts, ZEN Master now uses the % of a given time window that an object spends in a non-positive state, to determine if it should escalate. \- Warnings and Errors use independent escalation and de-escalation windows, allowing users to better refine the escalation. o e.g., a source reporting blank picture for 5% of 60 minutes as a whole might constitute a warning only, to be looked at later. But a source reporting blank picture for 10% of a 15- minute window, can be configured to escalate to an error. \- 2 distinct mechanisms now control the behavior of each alert, Thresholds and Delays. ### Thresholds Thresholds determine the severity of the alert. There are 2 types of thresholds, Value thresholds, and State-Over-Time Thresholds: Value Thresholds - e.g., CPU/GPU/License expiration, these are simple, they have a warning value and an error value and the severity is determined by the measured value compared to the configured thresholds: ### State-Over-Time Thresholds For alerts that are based on a Boolean state, whether it is Boolean (e.g., Source Offline) or because the exact value is not important (e.g., CC errors or not recovered packets) the threshold is defined by a time window and a percentage of time of that window spent in the relevant state. \- E.g., 50% out of 6 minutes is an error threshold, so if a source reports a blank picture for 3 minutes out of the 6 min window, ZM will put it into an error state. \- To prevent edge cases where warning is always ignored, the system validates against the following configuration limits: o warning threshold must be lower than error threshold. o warning window must be greater or equal to error window. ### Delays In addition to the threshold ZEN Master also now provides an escalation delay and a de- escalation delay for each threshold: a. b. De-escalation – Primarily used to protect against flapping, to de-escalate to a lower state the object must spend a de-escalation delay worth of minutes in a lower state than the current one. Escalation – Similar to the de-escalation window, the object needs to spend the configured number of minutes in a higher alert state before ZEN Master will register it as an error. Usually left at zero, but in some cases, users may require an escalated state persist for a sustained period before being alerted. i. For example, users may not be concerned with short CPU spikes, but want to be alerted to sustained high CPU usage. Note that all defaults and any existing edited rules in customer event alert profiles have been converted to a best-case match to approximate the old setting using the new mechanism. • Alert Rule Details and Edit Panel As with previous releases, any objects log of events contains an actions column for warnings and errors escalated by the alert event profile, that thus far contained 2 actions: 1\. Create an incident. 2\. Take the user directly to the full rule page for the alert Event Profile that was used to escalate the event to the log and elevated status. As of this release, the action that previously took the user to the full event profile list, is now replaced with an action to bring up a panel related to the specific rule that triggered the alert. The panel: \- Still provides access to the full event profile, but also \- Provides in-band controls to edit the specific rule in place and propagate to all objects using the profile. \- Provides the option to clone the full profile and assign the new profile, along with any changes, to this object alone. 1\. To continue to and, if needed, edit the original profile, click the Events Profile name to jump to the full original event profile page 2\. Here, edits to the rule, and how it deals with issue s and escalated then to errors and warnings can be made. 3\. In the update portion of the dialog: a. select ‘Overwrite’ to make changes and propagate to all objects sharing the existing profile. b. select ‘Create New’ to make a clone the existing profile, that is otherwise identical except for the changes to this rule. This will prompt the user for a required name for the new event profile. • Networks page showing the current networks in use by the customer and the objects on them. The Network tracking page is now available via a new top-level left-hand menu: The page is self-populated by auto discovery It provides details and object states about each network. Clicking on a network again provides the details tab, and a tab showing the specific objects that are active on the network. • Ability to share an abbreviated Source page with a non-ZM user. Provides the ability to share a source object thumbnail page via a public link/URL with external users, without requiring them to have a ZEN Master account. This can be used to share visibility into a source with user such as live event producers, service. customers, external department, 3rd parties, and others with a need to view a source as a live looking-in or during a live event. The ZEN Master operator can select or view a source and bring up the sharing controls. The share controls provide start and end time controls to limit the longevity of the shared URL, which is generated by choosing “Create Link” . NOTE: in version 1, there is no link management or additional features. The link will expire when the end-time is reached. At this release, links are limited to 24 hours. User with access to the link will be able to view the temporary source details external user landing page, which visibility to: \- Name \- Status \- Thumbnail \- Bitrate \- Uptime \- Optional Overlay • AWS Wavelength Zone support ZEN Master now supports 5G Contribution and Distribution using the AWS Wavelength Zone service, by: \- Providing the ability to launch an instance within the Wavelength Zone \- Supporting the new instance-types \- Applying the appropriate carrier IP This can be achieved once the following pre-requisites have been met: Before launching a wavelength zone instance, opt into the wavelength zone service by enabling the feature via your AWS console. Once the service is available, the appropriate networking must be provided: \- A VPC in your region \- A carrier gateway \- A subnet in a Wavelength Zone Once complete, ZEN Master enables the user to launch an instance in the Wavelength Zone subnet with a Carrier IP address applied: Note that due to instant type and public IP differences, wavelength zone and non-wavelength zone subnets are not interchangeable, and clusters can only choose one. Please see the AWS documentation for more information on configuring your AWS Wavelength Zone network: What is AWS Wavelength? https\://docs.aws.amazon.com/wavelength/latest/developerguide/what-is-wavelength.html Get started with AWS Wavelength: https\://docs.aws.amazon.com/wavelength/latest/developerguide/get-started-wavelength.html Available Wavelength Zones https\://docs.aws.amazon.com/wavelength/latest/developerguide/available-wavelength- zones.html • External Authorization support for Zixi Push Sources and Zixi Pull Targets To date, Target pull requests reaching the I/O server are handled exclusively by ZEN Master application, validating the request against the Target configuration to authorize the connection. Just as the Zixi Broadcaster can redirect the authorization of connections to an external server, ZEN Master now supports a similar functionality. When configured, in addition to the standard internal authorization process, the requests redirected to an external service for confirmation. An example of this could be an external pay-per-view application, which confirms that a requesting end-device belongs to an account that has paid for a live event. Another example could be some external security management application that is managing firewalls accepting requests from dynamic IPs in a consumer network. Configure external authorization in a Clusters’ advanced settings... \- Configuration requires an external authorization URL for the server endpoint \- Optional Authorization header schema and credentials • Re-architected AWS MediaLive Integration to allow sharing a single AWS MediaConnect Flow Previously, a separate AWS MediaConnect Flow was required for each MediaLive workflow. With this update, a single MediaConnect Flow can be created, which is then able to act as the source of many MediaLive engines. Existing MediaConnect to MediaLive channels will convert seamlessly to the new architecture, allowing additional MediaLive outputs from historically active Flows. • UPD/RTP Target support for AWS MediaLive Channels The new option can now be found in the Create New UDP/RTP Target dialog. • Improved Filtering for Tables Along with the updated tables component ZEN Master now introduces more refined filtering capabilities. While the simple search bar still matches a search against all columns of the tables, the new filter provides additive column specific filter options that are specific to the column types of the correspond table. This allows the user to set more fine-grained filter parameters such as searching for text in specific columns, filtering with relational operators on numerical columns, or specifying time ranges etc. Filters are additive, so a sources search with a filter for uptime > 2 days, and a second for uptime \< 3 days, will yield a result of all sources with uptimes between 2 and 3 days In this release the new filters appear on all major list pages, ZECs, Broadcasters, Sources, Channels, and Targets, and persist if set before the user navigates away from the page and then returns. Additional Improvements and Changes The following additional improvements and changes were implemented in this release: • Updated look and feel. • UI Polish • All high-level tables, including those on list pages and others, are updated to the new code. • AgentZ now support ARM hardware. • Live Events list and detail pages now represent the live state of each live event with no delay. • Added Channel Name, IP, and Bitrate support to Targets in Grids • Added an option to control AWS "Detailed Monitoring” of CloudWatch for AWS clusters, providing users with ability to better control costs. o On all existing clusters this is turned on o For new cluster, the option will default to off. • Reorganized data presentation of Source details page, grouping categories for clarity. • Added Support for NDI Audio Channel mapping. • Added Option to create an AWS MediaConnect Source from a ZEC • Updated Channel list table to show Source or Target name instead of a count when a Channel has only 1 of either. • ZEN Master will now correctly update existing and create any newly required auto-pull configurations for a channel, whenever a Source’s target broadcaster is edited. o This saves the user from a manual disable/enable cycle on affected Channels and Targets • AWS MediaLink is now its own Source type in the UI o As with the AWS MediaLink encoder directly supported outputs, ZEN Master MediaLink Source destinations are limited to an AWS MediaLive channel only. • Updated the list of supported and available instance type options for AWS Clusters o Some unused instance type options were removed. o Support is added for c7g and c6in families. • Improved the ZEN Master logic for Pull Target redirection when considering scenarios such as offline sources. o e.g., Offline Source error are now considered lower priority than CQA/TR-101 • Updated and clarified the Event Log message for Broadcaster Maintenance mode. • ‘Broadcaster Restarted’ alert, which was previously captured by the Broadcaster Status Error alert rule, now has its own standalone rule for finer control. • Thumbnails in Source list are now off by default. o This will not affect any browser that you already used to navigate to a Sources list on, so they will remain for customers that did not turn them off already. Bug Fixes The following issues were resolved: • Fixed multiple issues with new tables selection and updates when an object is deleted. • Fixed Broadcaster Terminated alert not obeying alerting profile rules. • Fixed bonding on AWS MediaConnect Sources • Live Events list page stage filter now persists after navigation. • Source links on Live Event dashboard now correctly take user to the source details page. • User group details page now displays the actual role details. • API - Target GET with an invalid ID now returns HTTP Code 404 instead of 500. • Resolved multiple issues with export to Excel quick reports in new tables. • Maintenance mode warning display now correctly obeys users read permissions on a cluster. • Removed irrelevant "requires restart" warning when editing a cluster. • Resolved DST issues with automation. • Editing a Live Event no longer resets its Channel selection. • Enabling a Source Automation will no longer restart already Enabled sources. o Remains true when enabled via the UI or the ZEN Master API • ZM will now log SCTE-35 messages with invalid CRC. • Resolved and issue preventing function with Azure transcoding broadcasters. [title] Zixi Product Updates [path] / ## [Zixi ZEN Master Release Notes](docId:9RHxAcarYBvZt6lniuleV) ## [Zixi Broadcaster Release Notes](docId\:ECKNlLEJZhCqz5hpntnJ2) [title] ZEN MASTER April 2024 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be included in the ZEN Master April 1, 2024 release. Features The following new features were implemented in this release: ### New details UI for Sources • ZEN Master Source details screens are now updated to align with Broadcaster screens UI, this includes: o Persistent vital statistics information in the top panel. o Configurable widget's view. o VLC and WebRTC playback from the top panel. ### Thumbnails on Targets • Where applicable, Target details pages now include thumbnails. ### Auto-login into Broadcasters, ZECs, Feeders, and Receivers • When accessing the GUI of Broadcasters and ZEC’s via ZEN Master, the system now logs Users in directly without the need to copy and paste in credentials. ### SCTE35 logs can be colored by type • SCTE-35 logs can now be optionally color-coded by using the show/hide colors toggle to help with rapid identification and confirmation. ### Added the option to export SCTE35 UI logs • Data can be downloaded as an xml report. ### Priority client support for Zixi Push Other Sources • ZEN Master now supports the Broadcaster Priority Dource functionality for the ZIxi- Push-Other Source Type. ### Azure Public IP Prefixes support • Unlike AWS, there is no IP pool feature in Azure. • Azure Admins will need to create a Public IP Prefixes pool and create public IPs. • The ID/Name of the Public IP pool can be provided in the cluster settings. • ZEN Master will then create IPs on demand from the pool. ### Redirection Routing rules for Pull requests: • ZEN Master now provides the ability to set specific routing rules for Pull requests from clusters or CIDR IP Ranges. • The rules can be accessed and created via “+Add Rule” button on the new “Redirection Rules” tab of the cluster page: • Rules can be applied to the client end-point Cluster, or IP CIDR Range, from where the pull request is initiated: o When using ‘Cluster’ the rule applies to auto-pull requests only. o CIDR rules apply to any Zixi pull request, including those from ZECs, IRDs etc. • Rules are evaluated in order from lowest order to highest. • The first matching rule will apply. • Latency is determined by the following order: Redirection rule latency -> source auto- pull/pull target latency -> default 1000ms • Additional Notes: o If there is no match, the default rule Prefer public IP with DTLS will be used. o Private/NIC CIDR do not support DTLS and will redirect to a non-DTLS port. o A configuration conflict is possible, such as a cluster enabled for DTLS only, where a private/NIC redirection will never successfully connect. o It is possible to use this as feature as an allow list by creating a 0.0.0.0/0 block rule and give it the highest order. In this case, any connection not matched by a rule with a lower order will finally be matched by the blocking rule. Additional Improvements and Changes The following additional improvements and changes were implemented in this release: • Azure Broadcasters no longer use NVIDIA images from Azure marketplace. o Zixi now fully manages Azure images. • HLS Ad markers moved from the events log to their own log/page in the UI. • Client IP is now logged for Zixi Push Sources on connection/reconnection. • ZEN Master now shows the last time TR101/CQA stats were reset. • Failover Sources will now recover correctly when re-enabling their component Sources. • Added optional billing code column to Sources list. • Renamed ‘Termination Protection’ to ‘Deletion Protection’ for clarity in the scaling cluster settings. • Added table column selection to Broadcasters sub-table in Clusters list. • Improved WebRTC error handling/reporting. • Moved WebRTC pass-through mode to ‘more options’ Source setting. • Added missing common fields to Multiview Source form. • Added max bitrate setting to Demux Sources. • Added target Broadcaster configuration to Failover Channels. • Exposed threads configuration for x264 transcoding. • Exposed authentication options for HTTP Targets. • Added DTLS only mode for Clusters. • Small UI improvements ### Bug Fixes The following issues were resolved: • Clusters with no Broadcasters are now in a gray/pending state instead of a green/ok state. • Fixed unnecessary restart warnings. • Fixed download SSH key option available and on imported keys. • Fixed IO Server host key download. • Fixed automation actions grayed out after some actions. • Fixed Live Events timeline becoming "shorter" on every manual refresh. • Fixed AWS MediaConnect TR101 info not available. • Removed HTML overlay input from Transcoded Channels. • Fixed transcoding errors not generating ZEN Master events/alerts. • Fixed Transcoding channel transcoding errors escalating too fast. • Fixed issue preventing creation of Failover Sources when using Frozen/Blank video rules. • Fixed ZEN Master not updating Cluster DNS settings when all Broadcasters are in an error state . • Fixed invalid password detection + Windows Broadcaster stuck in error state. • Fixed TAG Multiviewer not working with self-signed HTTPS certificates. • Fixed AWS/Azure/GCP Broadcasters not launching when using redundant I/O servers. • Fixed issue with loading more SCTE-35 messages in main SCTE-35 log. [title] ZEN MASTER June 2024 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ ZIXI ZEN MASTER RELEASE NOTES The following updates will be included in the ZEN Master June 17th, 2024, release. Features The following new features were implemented in this release: ### o Zixi ESAM (Event Signaling and Management) Agent support o Zixi Introduces the Broadcaster ESAM Agent to manage ESAM SCTE requests. o The Agent is a lightweight side-car application running alongside the Broadcaster o ESAM policy instructions and SCTE signals are relayed between an external Signal Decision System and the Zixi Broadcaster for processing and signal switching. o The Agent leverages the Broadcasters pts-switching to make the switches based on commands from an external ESAM service ▪ (requires Broadcaster version 17.4 or greater). o The Agent is fully compliant with ESAM standard CableLab I03. o In this release, ZEN Master logs switching requests and confirmations. o Contact your technical representative for more details. ### o MPEG2 Transcoding support o Added option to transcode to the MPEG2 output format in Transcode Profiles: ### o Added Error Concealment support on Failover Channels o Options to correct transport stream for downstream IRDs are now supported in ZEN Master: o The advanced mode Broadcaster features are available via the input's ‘fix’ menu: o The options appear in ZEN Master in the Error Concealment section of the Failover Channel configuration: ### o Updated Event Profiles configuration UI o The Alert Event Profile rules table is updated to the standard table architecture, simplifying navigation, and highlighting or ordering by modified, disabled, or rule Group. o Text and layout of the event rule definition tools have also been updated for greater clarity: Additional Improvements and Changes The following additional improvements and changes were implemented in this release: ### o Support for ZECs (Zixi Edge Compute) added to maps o Missing option on the mapping page is now corrected: ### o Added option to control label location on Grids o Added an option to provide more control of name location on grids, allowing positioning on either the top or the bottom of the object ### o Added filtering to Source SCTE35 table SCTE Tables now include the ability to filter on message text as well as to limit the search window with a start and/or end time: ## Bug Fixes The following issues were resolved: o Editing stages of active Live Events now correctly updates the pre-live schedule. o Automation not working when selecting objects with Tags. o Fixed bug preventing some Mac and Windows Broadcasters from connecting to ZEN. o Transcoding Channel with slate not returning to primary Source upon recovery. o Unable to create ZEC Sources/Targets in some situations. o Offline broadcaster reporting ports error instead of offline. o Unable to reset TR101 failing on some ZEN Master accounts. o Target thumbnails will not be displayed when the target is offline. o Resolved an issue with some Insights graphs not working. o Deleting VPCs from AWS (Amazon Web Services) will no longer break ZM UI that depends on them. o Incidents list not updating when switching between different networks. o Targets menu option missing for some non-Admin users. o Change tracking not working for adaptive/transcoded channels with many bitrates. o Incorrect error displayed for offline push Sources from managed Feeders. o Azure Broadcasters entering a restarting loop when auto-install AgentZ enabled. o Disabling/deleting an unmanaged Zixi Push Source sometimes leaves it connected. o AgentZ not working or not installing on some platforms. o UI Polish. ## API The following updates were implemented in the ZEN Master API: • Resolved issues reverting broadcaster API password changes. • API no longer allows creating Live Events in the past. [title] ZEN MASTER March 2021 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates were pushed to ZEN Master on March 1, 2021. Improvements • Added ability to disconnect from a MediaConnect Flow and delete it only in ZEN Master • Added ability to export Grids & Maps details to an Excel report • Added an option to display Broadcaster information in tiles instead of a table • Improved layout of Channel diagrams with failover Sources • Added ability to edit Zixi Source origin type – Feeder, Broadcaster– and input • Added new optional ‘Active Broadcaster’ column to Sources list • Added support for report names with special characters • Added additional Copy to Clipboard buttons • Added Notes to MediaConnect Channels • Minor UI improvements Bug Fixes • Fixed issue with 500+ active tunnels causing Source and Target connection issues • Fixed issue with disabled notifications still being emailed • Fixed SCTE-35 duplicate/timeouts issues • Fixed missing global search result while it worked on Broadcasters page • Fixed issue where a Broadcaster being deleted was not clear in the events log • Fixed missing display of events in Channels; events were properly saved in the database • Fixed “Error (71)” to now show proper message • Fixed Connection/Reconnection messages for Zixi Pull Targets missing data and showing up when no connection happened • Fixed issue with remote-access tunnels blocking requests • Fixed issue with Zixi Pull latency always displaying blank when editing • Fixed issue with Channel Page auto refresh • Fixed issue with latency being required on Zixi Push Other Sources when latency is set by the client and cannot be overridden in ZEN Master • Fixed issue with Broadcaster/Feeder input not filtering properly when adding/editing a MediaConnect or Zixi Source • Fixed issue with “Enable Encryption” being displayed on Zixi Source type Other when it should not be displayed [title] ZEN MASTER May 2020 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates were pushed to ZEN Master on May 18, 2020. Kafka Integration ZEN Master now exports events to Apache Kafka. Kafka is a data streaming platform that allows you publish to and subscribe to streams of data, store them, and process them. ZEN Master is a “publisher” that uses the Kafka Producer API to send event data to a Kafka server. Once the event data from ZEN Master is streaming to a Kafka server, connectors are available to pull data from the Kafka server into third party applications and services including Elasticsearch, Splunk, Azure Event Hubs, AWS Cloudwatch, AWS S3, and more. The ZEN Master Kafka integration has been validated with the Confluent Cloud service but should be compatible with all Apache Kafka implementations. To add a new Kafka integration, open the new ZEN Master UI: Next, select Configuration->Notifications in the left-hand menu. Select the Kafka Configuration tab and click Add. Fill out the form using information from your Kafka service or server and enable the Events box. Note, the Topic needs to have already been created on the Kafka server and Username / Password authentication is required. After configuring the Kafka integration, you can test it from the configuration tab where Kafka integrations are listed. Once configured, the Kafka integration operates with admin privileges meaning all events will be sent to Kafka regardless of Access Tags. You can stop events being published to the Kafka topic by editing the configuration and disabling the Events box. Also, if you disable logging for certain types of events on certain objects (such as a Source), those events will no longer be written to the ZEN Master events database or sent to Kafka servers. ### MINOR IMPROVEMENTS AND BUG FIXES The following minor improvements were implemented: • Updated Automation to support recently added Source and Target types including RIST, SRT, UDP, and MediaConnect • Pass-through channel Targets are now monitored for low bitrate and unrecovered packets • Added ability to filter Broadcasters list by HostID and IP • Added instance type to Broadcaster details page • Added "Open" link to Channels diagram nodes to open remote Feeder/Receiver UI • Updated PID analysis panel with new fields, including PTS, DTS, and Chroma, for consistency with the Broadcaster UI • Renamed Stream Quality/Delivery to Frame Delivery % and Packet Delivery % • Updated missing fields for some Target types in public API The following issues were resolved: • Fixed issue where monitoring was ignoring Targets Broadcaster configuration causing invalid Channel diagrams • Fixed issue where pass-through Channel active Broadcaster logic was ignoring Source Target Broadcaster configuration • Fixed issue where the Receiver was not reconnecting on 0 bitrate source and required restarting the Target • Fixed issue where monitor only Sources could be played even when public output was disabled • Fixed issue with Automation tasks stuck in executing state on overlapping schedules [title] ZEN MASTER January 2021 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates were pushed to ZEN Master on January 13, 2020. Improvements ### Dynamic Zixi Pull Targets Most useful for occasional use and live events, ZEN Master now provides the ability to create a single “Dynamic” Pull Target in ZEN Master that is automatically connected to multiple Receiver devices without needing to define a Target for each Receiver device individually. This feature provides a live video MeetMe room capability to simplify distributing live content to different organizations on an event by event basis. To create a dynamic Pull Target, simply select “Dynamic” on the Target. On the Targets list you will now see that dynamic Target you just created. Next supply the stream parameters to organizations with Zixi Receivers that will Pull the stream. Once Receiver devices connect to the Target’s Host/Port/StreamID, they will be listed in the Targets list and in the Child Targets section on the Target detail page. Child targets are named using the parent Target name and the ID of the Zixi Receiver. For a standalone Zixi Receiver the ID is changed in Settings->General. For Zixi Receiver integrations in IRDs and other devices, the ID would be defined in the device UI or may be automatically defined. Note, all Receiver devices Pulling from a single dynamic Target must have unique ID’s. If you want to Pull a Channel into a Receiver twice for redundancy, you will set up two dynamic Targets connected to the same Channel and then Pull from each dynamic Target. Child Targets are not editable; they assume all of the settings of the parent Target and can only be deleted. However, you can release a child Target from its parent, as shown below, and then it can be edited as it no longer assumes the settings of the parent. Deleting a parent Target will also release all child Targets to be regular Targets; deleting a parent Target does not delete child Targets and thus causes no stream disruption. If the Channel of a parent Target is changed, this will only affect newly connected child Targets after that change and will not disrupt existing child Targets. To change the Channel on multiple child Targets, change the Channel of the parent and then select the desired child Targets in the Target list and delete them. They will then reconnect and assume the new Channel setting from the parent Target. ### Boolean Search Filter fields in ZEN Master now support Boolean operators AND, OR, and NOT to simplify filtering the visible objects. The ( ) \[ ] characters are also supported for grouping the Boolean expressions. Filter fields are available on object lists, such as Sources or Broadcasters, and on Grids. As before, filter fields are sticky such that filter expressions previously entered will remain when returning to previously browsed pages. ### Automatic Clustering of Objects on Maps Objects on maps will now be clustered based on zoom level of the map so that multiple objects in one area will not overlap. The icon for the clustered objects shows the number of objects in each state in the order OK, Warning, Error, and Offline. For example, “2/5/4” as shown in the image on the left below shows that 2 objects are in OK state based on the green color, 5 objects are in Error state based on the red color, and 4 objects are in offline state. The image on the right shows the objects with clustering turned off. Clustering is automatic based on zoom level but the user can also manually uncluster objects using the button shown below. ### Show/Hide List Columns The user can now select which columns to display on lists such as the Sources list or Channels list. This can be useful on devices with smaller screens, such as phones or tablet, or just to remove unnecessary information from the page. The column setting is sticky meaning that when you browse away from the page or log out of ZEN Master and then come back to the page, the same columns will be enabled and disabled. The settings are stored on a per browser basis such that the browser on your tablet might have certain columns enabled and disabled while the browser on your laptop would have different columns enabled and disabled. The column selector is next to the Filter box as shown below. Included below are additional improvements in this ZEN Master release: • System wide performance upgrade • Auto-pull latency on Sources is now configurable • Added Search Window and Merge Mode on Hitless Failover Sources • Broadcaster thread priority is now low by default on AWS/GCP/Azure clusters • Global search now includes MediaConnect objects • GCP targets now have Cache-Control headers automatically set to allow playback directly from GCP Storage Bug Fixes • Fixed filtering by Tags in Events Log • Fixed UDP/RTP Target cloning giving an Invalid Parameters error • Fixed text in Channel diagrams overflowing outside of boxes due to Chrome update • Fixed issue with Targets showing error None in some cases • Fixed links to Sources in Channel diagrams • Fixed issue with custom SCTE reporting configuration being deleted • Fixed issue with deep links not surviving SSO login • Numerous UI fixes [title] ZEN MASTER April 2019 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates were pushed to ZEN Master on April 1, 2019. STREAM VISUALIZATION Stream visualizations graphically display the components that make up a ZEN Master Channel - Source(s), Target(s), Feeder(s), Broadcaster(s), Receivers(s), and Cluster(s) – as well as the connections between these components. For each of these components, their current state is shown as well as additional details. A link to navigate directly to each component’s page is also shown. Currently, Chrome and Firefox are supported for stream visualization whereas Internet Explorer and Edge are not. To visualize a channel, select the Diagram tab when viewing the channel. ::Image[To visualize a channel, select the Diagram tab when viewing the channel. ]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/WUyu2JlPuDOWX_hIkMV-L_image.png" size="82" width="1826" height="674" position="center" showCaption="false"} ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/0DN1qQwSt8R3bEshypdJL_image.png" size="84" width="1840" height="632" position="center" showCaption="false"} The diagram can be zoomed out to fit the width of the current window by clicking the zoom button. For narrow screens the diagram will be oriented in a vertical direction. The zoom button has no effect in this orientation. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/KekSasS5nnJ4rqLuLMWgW_image.png" size="44" width="934" height="1290" position="center" showCaption="false"} SETTING BROADCASTER CLUSTER ALERT THRESHOLDS When adding or editing a Broadcaster Cluster, the user now can modify the error alert threshold values for Broadcaster CPU usage, Memory usage, Hard Drive usage, GPU usage, GPU Memory usage as well as the warning alerts threshold values for GPU Decoder usage and GPU Encoder usage. The GPU thresholds are only relevant for transcoding workflows using Intel Quick Sync and NVIDIA GPUs. To set the thresholds, click on SHOW ADVANCED when adding or editing a Broadcaster cluster. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/AY3ndjbSK-F-q40cfNaF6_image.png" size="50" width="942" height="1812" position="center" showCaption="false"} SETTING HLS/DASH SEGMENT CONFIGURATION When adding or editing a Broadcaster Cluster, the user now can modify segment count and durations for HLS and DASH streams. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/DdJLhkYcsuo_ixr538Fy5_image.png" size="52" width="924" height="1750" position="center" showCaption="false"} MINOR IMPROVEMENTS AND BUG FIXES • More detailed errors are returned on unsuccessful Channel add/edit • Source errors are now displayed in the Channel details tab • GPU encoder/decoder usage error downgraded to a warning • Bug fixes in Events filtering and Notes tab and Feeder edit form [title] ZEN Master 1 April 2025 Release Notes [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be included in the ZEN Master release for April 01, 2025. ## Features ### Map range support for PID Mapping profiles - PID Mapping by Category and Type now supports the Zixi Broadcaster’s Map Range functionality - Corresponding matching PIDS are mapped consecutively from the provided starting PID number ![Map Range for PID Mapping](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-eC3GgTyZMXbfDIzmjKaIc-20250628-191147.png) ### Frame thinning support on Zixi Sources and Targets - Advanced settings now include an option for Frame thinning - Requires Broadcaster v18 or greater ![Frame Thinning for Zixi Sources and Targets](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-dYTZXmlvUNEml17eGm5iy-20250628-191436.png) ### FEC and Traffic Shaping controls for Zixi Sources and Targets - Advanced settings now include Traffic Shaping and Max FEC Overhead Parameters - Supported for - Push / Pull Sources - Push Targets - Requires Broadcaster v18.2 for Pull, and 18.3 for Push or greater ![FEC and Traffic ShapingFrame Thinning for Zixi Sources and Targets](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-HW4iC67D6YKDnCpq3CW77-20250628-191757.png) ### Added option to show downstream Sources/Channels on Source diagrams and details pages - The next tier of objects can be toggled on/off for diagrams and are also shown in a new ‘Downstream’ tab ![Downstream Objects on Source Diagrams](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-6u7-GBdykFHqTkyPTU84r-20250628-192055.png) ## Additional Improvements and Changes ### AWS MediaConnect Thumbnails and Information support - To enable thumbnails, be sure to check ‘Enable Thumbnails’ in the MediaConnect Flow Channel configuration: ![Enable MediaConnect Thumbnails](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-RlbcSqUGacFjhQ1q0e6aR-20250628-192422.png) - Once enabled, thumbnails will begin to update in the AWS Media Source Stream tab ![Sample Thumbnail for AWS Media Sources](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-B0IKlKt_r9vCWM5wWO-KY-20250628-192600.png) - Note that the frequency of thumbnail updates is limited by the AWS Account API rate limits, and the scope of information available for display in the transport stream tree from AWS is a subset of that of the standalone Zixi Broadcaster capability. ### Time zone selection updates - Allow resetting to local time - Allow setting datetime format to EU/US formats ![Time Zone Selection New Options](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-W9oFxMFYN-MFoNT3_Y598-20250628-192859.png) ### Transcoding Profiles now list Sources that use them ![Sources Using a Transcoding Profile](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-6t9NTFS9Uau3cgUXUl4UO-20250628-193051.png) ### Updating Dynamic Pull Targets now propagates to child Targets - A checkbox is added to the Dynamic Target configuration to dictate the behavior of edits to the parent on corresponding child Targets - For changes do not require a restart, such as Tags or Event Profile, etc.: - All existing child Targets, as well as the parent Dynamic Target, will update to reflect the changes - For changes requiring a restart: - All existing (including offline) child Targets will be deleted - Active clients will automatically reconnect and acquire the new settings - If unchecked, the parent Dynamic Target is updated, and only future child Targets take the new configuration ![Changes to Dynamic Pull Targets Propagate to Child Targets](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-B8wobRkbKc527ytEMtnTM-20250628-193513.png) ### Separated 608/708 closed captions monitoring - 608 and 708 captions are now isolated and can be monitored and distinguished in the alert body ![Monitor 608 and 708 Captions Separately](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-tl-Bvgj7TUrW6vVCciEAS-20250628-193739.png) - Added support for Minimize Latency for Zixi Sources - Added support for billing codes on public outputs on Sources - Added Hover over Source details on active live events - Added new SCTE-35 to HLS Ad marker conversion controls - Added filters and more details to Channel/Target assignment dialogs - Updated Event reports to download a simple list of events instead of trying to break them down into per object sheets - Updated Target thumbnails to no longer require permissions on the current active Source - Updated Source monitoring to take error concealment/PID mapping into account - Updated Tag filter on tables to allow selecting from existing tags - Added audio support for HTML overlay. Requires v18.2 Broadcaster or greater. - Added more configuration info to object details pages - Added distinct monitoring rule for error concealment statistics - Implemented front-end performance improvements for Pass-through Channels with dozens of Targets - Implemented major performance improvements on Channels and Targets list pages ## ESNI & ESAM ### ESNI - Match signal now respects the @reusable attribute - Fixed inconsistencies with ViewingPolicy reuse - Wrong audit messages on update - Match time is now ignored if there is a conflicting Match signal - Media with matchTime outside of effective/expires range will now be rejected - Respect SCTE-35 PTS when triggering ESNI switches - Various Policy related tweaks ### ESAM: - Syslog logging support - Added controls/logic to handle slow/late responses from decision server - Fixed POIS based on input acquisitionPointIdentity - Updated handling of unsolicited messages to support multiple ResponseSignal and AlternateContent elements - Logging improvements ## API API documentation has been added or updated for fields in the following sections: ### Sources - Create (general) - Update By Id - List Sources - Get Source By Id - TR101 status summary and details - New endpoint for SCTE-35 message insertion - /sources/\{sourceId}/scte35 ### Failover Channels ### Pass-Through Channels ### Adaptive Channels ### MediaConnect Channels - Added: enable\_thumbnails ### Users - Added: - is\_objects\_manager - is\_incident\_manager - Removed Zixi internal fields ### New fields: - traffic\_shaping\_kbps - max\_fec\_overhead\_percent - For: - Zixi Push Targets - ZEC Push Sources - Broadcaster Push/Pull Sources ### RTMP Push Sources - Added public\_url ### Tags - Added vip field - Remote Access [title] Release Notes: Zixi Broadcaster Version 16 [path] Zixi Product Updates/Zixi Broadcaster Release Notes/ ### v16.13.45476 (20 June 2024) ### Improvements - AgentZ is now automatically installed by the Broadcaster installer, similar to v17. ## v16.12.45243 (15 Feb 2024) ### Improvements - The transcoder (and re-multiplex) now supports up to 10 audio streams - Added discontinuity tag when there is a gap in HLS segments - Made duration calculation more accurate for audio streams in adaptive groups - Allow, with a warning message, sending Zixi Push input with RTP headers as RTP/RIST output stream with RTP in the payload, or with non-transport stream keep the original payload - Clear 'Low target bitrate' error after 5 seconds of no error on demuxed streams ## v16.11.45011 (12 Nov 2023) ### Improvements - Exposed "decompression\_errors" network receive statistics counter, instead of having a permanent "compression error" state that can be caused by a single packet. - Added error message when transcoding a source with crop setting enabled when also keeping original video stream. ## v16.10.44940 (21 Sep 2023) ### Improvements - Added "updates" field to inputs/outputs network statistics. The counter indicates how many times the statistics were updated. - Reduced TR101 warnings on a CBR padded stream ## v16.9.44823 (7 Aug 2023) ### Improvements - Allow sending multiple SRT push outputs to the same port for applications that can accept multiple streams on one port, stream is identified by IP+Port+Stream ## v16.8.44765 (26 June 2023) ### Improvements - Added support for non-public S3 file sources with pre-signed URL ## v16.7.44709 (14 May 2023) ### Improvements - Added all audio PIDs and channels to NDI outputs - Added Active/Active failover support for Zixi inputs on ZEC - Added option to reconnect on low bitrate on Pull inputs from multiple hosts. When enabled, it behaves like the standalone Zixi receiver. The default behavior, which is reconnect on disconnected stream, has not changed. - Added monitoring for inputs to the multiplexer. If all inputs are offline, it will report an error. If one or more inputs are offline, but at least one is still active, the multiplexer will pad the generated MPTS stream with NULL packets in order to meet the requested bitrate. - Added listing of SPTS configured components of multiplexed streams in the inputs listing API endpoint - Improved performance of DTLS by using AES 128 on both Intel and Graviton by default instead of AES 256 on Intel and CHACHA on Graviton. ## v16.6.44654 (29 March 2023) ### Improvements - ECM/EMM PIDS are now passed through when de-multiplexing an MPTS source - Improved timing of WebVTT captions converted from 708 - Added support for failover groups with Zixi Pull inputs to Zixi Edge Compute (ZEC) - Added validation for segment duration and segment count on adaptive groups - Exposed “Keep RTP headers” setting on RTP, RIST, and Failover inputs - Reduced memory utilization of RTP inputs to enable higher density ## v16.5.44584 (27 Feb 2023) ### Improvements - Added ability to convert 608 Closed Captions to WebVTT; previously only supported 708 to WebVTT. - Updated NDI library to v5.5 ## v16.4.44543 (3 Jan 2023) ### Improvements - Added support for mpeg2 video and mpeg1 layer2 audio to software transcoding - Added CQA tests on individual PID in MPTS for failover group switching - Added custom header configuration to AWS S3/MediaStore outputs - Added URL encoding for streamid and password for SRT inputs/outputs so non-HTTP compatible characters can be used - Added suppression of pcr\_accuracy reporting if the stream is VBR and gray it out in the TR-101 p1/p2 dialog - Added pid\_map, HTTP file and MPTS sources to Broadcaster's "New Output" dialog - Improved handling when switching from CBR to VBR in transcoding - Improved MPTS multiplexor to provide indication if streams are not "ready" - Improved reliability of startup process for transcoder channels - Updated to use TR101 MGB2 profile for bitrate calculation, previously used MGB1 - Updated to allow any PID to be specified during PID mapping even when PID not found by PAT/PMT parsing - Updated Zixi Pull output latency to be static instead of dynamic, which reduces output jitter when doing Zixi push in + Zixi pull out when the Push input is jittery Eliminated unnecessary re-connection of Push sink or any other sink when switching its source seamlessly - Exposed VBR/CBR in the TR-101 PID under STATUS - Increased default de-jitter buffer of transcoded sources to reduce audio/video drops ## v16.3.44466 (9 Nov 2022) ### Improvements - Added support for software-based transcoding on ARM processors - Added support for NVIDIA GPU transcoding on machines with ARM processors and NVIDIA GPUs. Testing and validation was performed on AWS G5g EC2 instances. - Added "minimize latency" feature on push/pull Zixi inputs. In this mode the latency target will be adjusted down from the user setting to automatically find the lowest error-free latency. - Added support for access control by stream ID on SRT streams - Added support for editing inputs/outputs/adaptive parameters without restarting the Broadcaster. This feature is only available via API only using 'no\_restart' parameter. - Added support for locking on a particular input in failover group. The locked input will be used even if it is offline. This feature is only available via API. - Added support for adjusting freeze & blank detection timeout values. This feature is only available via API. - Added support for chunked HTTP transfer for predefined TS HTTP inputs - The PID MAP type input now uses its original input max-bitrate instead of a hard-coded value of 10mbps for its max-bitrate setting ## v16.2.44358 (6 Sep 2022) ### Improvements - Improved stability of TR-101 analyzer - Improved stability of file inputs and smoothing on ARM platforms ## v16.1.44331 (4 Aug 2022) ### ARM Architecture Support The Zixi Broadcaster/ZEC is now being built for ARMv8 64-bit in addition to the existing X86 64-bit architecture on Linux; Windows builds are still only available for X86 64-bit. Currently, two unique ARM builds are being created. The first is compiled with the “-mcpu=neoverse-n1” flag, as recommended by AWS for Graviton2/3 VMs, and the second is compiled with no flags for Raspberry Pi 4. These builds can be used on AWS Graviton2/3 VMs, Ampere VMs on GCP, Azure, and OCI, Raspberry Pi 4 devices, and other ARMv8 64-bit devices. ### TR-101 Analyzer The Zixi Broadcaster/ZEC now includes an internally developed TR-101 analyzer that replaces the 3rd-party TR-101 analyzer used previously. The new analyzer has better performance and stability while producing equivalent results to the previous analyzer and can be compiled for necessary architectures, currently X86 64-bit and ARMv8. ### Transport Stream Multiplexer The Zixi Broadcaster now includes a transport stream multiplexer which combines multiple Single Program Transport Streams (SPTS) into one constant bitrate Multi Program Transport Stream (MPTS). The multiplexer supports automatic sequential PID renaming to ensure unique PIDs in the resulting MPTS. PID mapping can also be used to create user defined PID numbering. Multiplexing is a licensed feature in the Zixi Broadcaster/ZEC and may be subject to additional commercial terms. When configured in the Broadcaster UI, automatic PID renumbering will be used. Use of the Broadcaster API is required to perform multiplexing combined with PID mapping. ### SCTE-35 injection The Zixi Broadcaster/ZEC now includes the ability to inject SCTE-35 messages into transport streams created from any input type. All transport stream outputs connected to those inputs will include the SCTE-35 messages. When SCTE-35 injection is enabled, a SCTE-35 PID will be added to the transport stream. SCTE-35 injection is available via the Broadcaster API and uses the base64 binary form of SCTE-35 messages. ### HTTP File Input The Zixi Broadcaster now supports file input from an HTTP/HTTPS URL, such as an S3 bucket. Previously, file input only supported files on the local file system. When the input is started, the file will be copied from the remote server to a temporary location on the local file system and then ingested into the Broadcaster. As with local file input, the container of the remote file must be transport stream (.ts). A typical use case for file inputs is to use it as a backup in a failover group such that if the primary and secondary streams disconnect, there is a backup from the file input. ### WebRTC ingest The Zixi Broadcaster now includes the capability to capture a WebRTC stream from a browser that has access to a user’s webcam and microphone. Zixi provides sample code to be integrated into the customer’s web page that captures the audio and video. This is an advanced feature. Please discuss with your Zixi representative to learn more about it. ### Zixi Edge Compute The standalone Zixi Feeder and Zixi Receiver software have been replaced by Zixi Edge Compute (ZEC) software which shares the same codebase as the Zixi Broadcaster, but functions like the Feeder and Receiver. The Zixi Feeder allowed you to ingest UDP/RTP and ASI streams and then outputs Zixi streams to a Zixi Broadcaster. Similarly, ZEC allows you to ingest UDP/RTP and ASI streams but also adds SRT, RIST, RTMP, and RTSP input streams and then outputs Zixi streams to a Zixi Broadcaster. The Zixi Receiver allowed you to pull Zixi streams from a Zixi Broadcaster and then outputs UDP/RTP and ASI streams locally. Similarly, ZEC allows you to pull Zixi streams from a Zixi Broadcaster and then output UDP/RTP and ASI streams locally but also adds SRT, RIST, and RTMP output streams. Like the Zixi Feeder and Zixi Receiver, ZEC requires a license to be activated but is free to use. The Zixi Broadcaster and ZEC use the same installed binary in the same installation folder. The license activated determines whether the binary operates in Broadcaster mode or ZEC mode. Prior to licensing, the web UI will have a black banner at the top. After being licensed the banner will be green in Broadcaster mode and the banner will be red and blue in ZEC mode. ### Installation Directory Changes With the addition of ARM builds on Linux, the installation directory name for Zixi Broadcaster/ZEC has been updated. Previously, the Linux X86 64-bit Broadcaster was extracted to a directory named “zixi\_broadcaster-centos7-transcoder”. The new directory for the Linux X86 64-bit Broadcaster is “zixi\_broadcaster-linux64”. The directory for the Graviton2 build is “zixi\_broadcaster-graviton2” and the directory for the Raspberry Pi build is “zixi\_broadcaster-raspberry”. When you upgrade a Broadcaster from Linux X86 64-bit V15 to v16 using the web UI, the new directory will be created and the necessary config files will be copied over to the new directory. The previous “zixi\_broadcaster-centos7-transcoder” directory is not removed. Also, the zixibc service which runs the Broadcaster as a service will be updated to point to the v16 Broadcaster in the “zixi\_broadcaster-linux64” directory. If you need downgrade back to V15, the original “zixi\_broadcaster-centos7-transcoder” directory will be used again and the zixibc service needs to be updated to point to the v15 Broadcaster in this directory. Also, if you made any changes to the Broadcaster configuration while using v16, the configuration files need to be copied over to the v15 Broadcaster directory. If you made any license changes to the Broadcaster configuration while using v16, the license file needs to be copied over to the v15 Broadcaster directory. The following steps will downgrade your installation from the v16 Broadcaster to the original v15 Broadcaster: ```bash $ service zixibc stop $ cd zixi_broadcaster-centos7-transcoder $ cp ../zixi_broadcaster-linux64/*.xml . $ cp ../zixi_broadcaster-linux64/broadcaster.lic . $ ./installMe.sh ``` ### License Server Update Starting with V16 of the Zixi Broadcaster, a new license server is being used by the Broadcaster and needs to be whitelisted in firewalls on networks hosting the Zixi Broadcaster. The new FQDN to whitelist is license2.zixi.com. The existing FQDN license.zixi.com is also still in use and needs to be whitelisted. ### Protocol Updates - Zixi - Added FEC only mode in the Zixi protocol - SRT - Updated to v1.4.4 of SRT library (libSRT) - UDP/RTP - Added selection between "Arrival time" or "RTP timestamps" for RTP input dejittering. Default is 20ms dejitter in RTP/UDP inputs." - Fixed RTP input misfiring high bitrate alerts because of FEC bitrate - HLS - Fixed missing CC line in main manifest when closed captions are present in the stream - Added index to HLS input name in case there are streams with duplicate bandwidth values - DASH - Fixed issue with DASH live playlist not recorded when adaptive recording enabled - RTSP - Fixed incorrect counter of disconnections for RTSP inputs ### Transcoder Updates - The Zixi Broadcaster now supports encoding audio to Dolby Digital Plus, also known as Enhanced AC-3, during transcoding in addition to the existing AAC and OPUS audio encoding. ### Performance/Memory Improvements - Significantly improved total throughput. Note, on AWS EC2 instances it is now possible to exceed the egress limits on compute optimized VMs and you may need to switch to network optimized VMs for high throughput workflows. - Improved load time with large configuration files) - Improve the Broadcaster service restart time by about 50% - Reduced memory allocation of Pull inputs and outputs - Changed authentication queue to LIFO to prevent long recovery after Broadcaster restart when authentication is slow - Improved server side connection speed for many simultaneous connections - Added pagination for Broadcaster inputs/outputs listing in the UI and API enabling larger quantity of inputs and outputs ### Additional Improvements - Added ability to customize ciphers on DTLS server. A new field for DTLS ciphers is available in the web UI in advanced mode. - Thumbnail extraction is now portable across different CPU - Higher quality thumbnails are now created when the input stream is higher quality - Added PID mapping for MPTS sources - Added ability to output logs to STDOUT [title] ZEN MASTER February 2024 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be included in the ZEN Master February 20th, 2024 release. Features The following new features were implemented in this release: ### Customizable Multi-Region IO Server Options o I/O servers can now be placed in additional regions for increased redundancy and monitoring performance. o In environments with multi-region I/O servers, Zix Broadcasters will maintain parallel routes. o The ZEN Master monitoring system will track connection performance and use the lowest latency route for system health and streaming metrics collection. o In the event of connection issues or performance degradation, the monitoring system will use the alternative route. o Co-ordinate with your Zixi representative to discuss further options and the process and requirements for adding an additional I/O server in the region of choice. ### Transcoded Channels Now Support Technical Slates o Previously available for Failover Channels. o When transcoding to a multi-bitrate ladder and not passing through the original source, ZEN Master now allows users to set a technical fallback slate. ### New Broadcaster and Cluster details pages ZEN Master introduces changes to the Cluster and Broadcaster details pages to: o Allow for customization of the layout if desired, that will persist on a per-user basis. o Allows for continually changing vital statistics (i.e. CPU or RAM), and other desired data to be pinned to the top of the screen regardless of which tab the users is on or how far they have scrolled at any time. o Provides a new multi-widget tab that can be further customized to display information from multiple individual tabs in position-able, sizeable widgets on a single screen. To customize the layout: o Click the ‘layout help’ icon in the bottom right of the Broadcaster or Cluster screen for an in-application tour of the controls. o Then hit ‘unlock’ to put the screen in edit mode. Users can then: o Drag the individual data panels left and right to order in the top two rows. o Delete panels from the second row. o Add new panels from the available list. o Choose to pin/unpin each row. In addition, now that the button to access a Broadcaster's UI directly is now moved to the top right action menu: In tabbed mode, individual tabs work as previously, selecting the tab to display its data in the main panel. The selected tab is highlighted: In Multiview mode, using the final 2x2 ‘grid’ icon, select or de-select the tabs of the widgets to display in the combined view: Each displayed widget contains a control set in the top right to expand or contract the tab, as well as a handle to manually move the widget or set the width: Widgets can be added or removed, and placed in the order and positions desired: Finally, the screen can be locked, or changes reverted, or reset to default: ### New Diagram design with better layout and more details controls We have made improvements to the way diagrams are rendered: • The release provides an upgraded rendering engine which creates better layouts. • Previously, Broadcasters and workflow components were mixed together. • The new diagrams render in a more sensible way, focusing on the workflow steps first, and then tying them to the specific active Broadcaster. Below is an example of the updated layout, showing the rendering in both simple and detailed modes, and adding in the details for the active Broadcaster in the cluster. Distribution channel using the new diagram in standard mode: Distribution channel using new diagram, with details enabled: Distribution channel using new diagram, with details and Broadcaster info enabled: Additional Improvements and Changes The following additional improvements and changes were implemented in this release: • More details when selecting an AWS instance type. o Added some additional information to the listed instances regarding CPUs and throughput. • Ignore transcode thresholds is now a permanent property of a Source/Channel. • HTML Overlay support: o ZEN Master now provides support for the HTML Overlay platform feature. o Users can specify an external URL in the advanced section of Transcode Sources and Transcoded Channels configuration. o The external HTML is pulled directly to the processing Broadcaster and rendered over the transcoded video output. • SCTE-35 table improvements: o Improved breakout of SCTE event information in the table. o New columns. o Each event in a multi-event message is broken into its own line. • Added Zixi session details to Source and Target pages: o Additional Platform information detailing the session, certificate, encryption, and origin device of a stream is now displayed in the ZEN Master details tab for sources and target endpoints. • Support name/value tags integrations with AWS/Azure/GCP: o Tags named using the ‘=’ sign can be used to group objects in a key/value pair. o For Broadcasters launched in 3rd party clouds such as AWS, tags containing an ‘=’ sign are split and used to create corresponding name / value pair cloud tag. • Alert profile/rules editing moved to a single form. • Events log filters are now stored in URL parameters allowing sharing and reloading without manually resetting the filters. • Encryption of AWS EBS by default: o All new/updated clusters will now have EBS encryption enabled using the default AWS KMS/EBS key. • Added option to hide clear text Broadcaster credentials. • Improved email notification "grouping" to reduce number of emails sent when multiple errors occur simultaneously. • General UI updates. Bug Fixes The following issues were resolved: • Fixed UI crash on sources with hundreds of PIDs: • ZM will display/process up to 50 PIDs. • Adaptive/transcoded bitrate errors are now more accurate. • Fixed validation issue on Cluster edit that allowed creating Clusters with no Broadcaster password. • Fixed a bug in software-only transcoding and added relevant controls to UI. • Fixed Failover Channels in Grids linking to invalid pages/URLs. • Fixed UDP Target flapping state when Source is offline/zero bitrate. • Fixed an interaction issue between Failover Source and Inter-cluster Sources. • Fixed an invalid error when enabling Failover Channels with Zixi Push Targets requiring Sources with auto-pull enabled. • Fixed issues running v17 Broadcaster in AWS/GCP/Azure. • Fixed multiple issues causing false positive unknown status errors. • Fixed CORS error for analytics service on many ZM pages. • Fixed Source share links not working when non-SSO login is disabled. • Fixed an issue with dynamic Targets ability to reconnect to alternative Sources. • General UI Fixes. API The following updates were implemented in the ZEN Master API: • Added ‘broadcaster\_version’ parameter to Cluster creation API allowing creating a Cluster with just a version string. • Fixed inconsistency in Transcoding Profiles API name. • Improved API validation error clarity. • Exposed Live Events stage controls functionality in public API. • Added pagination support to Broadcaster Cluster public API. [title] ZEN MASTER August 2019 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be pushed to ZEN Master on August 5, 2019. MINOR IMPROVEMENTS AND BUG FIXES • "Disable/Enable" of Broadcaster now shows a confirmation dialog. • Added filter clusters by Broadcaster name in Broadcasters/Clusters page. • When enabling a Broadcaster/Receiver a “Broadcaster/Receiver is disabled” error will show instead of a “Bad Gateway Error” when the Broadcaster/Receiver is in an error state. • License details for Feeders now shows correct information. • Added anti-CSRF tokens to protect against CSRF attacks • Edit Target takes very long time to load. Added "Loading..." message while data is fetched from the back-end. Updated title from "Add new target” to “Edit Target”. • Fixed issue where view link from search result did not work for Broadcaster clusters. • Fixed global search by Broadcaster name not working. • Fixed issue with Remote Access not being highlighted on status widget in Dashboard or Menu • Fixed issue with Source listed twice, with second one in Error state. • Fixed issue where login with non-admin user and then browse to “Setting -> My account” causes a logout. • Fixed issue where Source link doesn't paginate to selected Source. • Fixed occasional error message when switching Channel selection • Fixed diagram draw error on some Channels • Fixed direct link to objects with URL encoded names e.g. http\://localhost:3000/#/targets/udp\_rtp/test%252Fslash%252F • Fixed missing UI error when update action fails on an AWS cluster, e.g. add Broadcaster on an AWS cluster that was manually deleted in AWS console. [title] ZEN MASTER May 2019 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ ## TRANSCODING ON AZURE BROADCASTER CLUSTERS ZEN Master now supports transcoding in Broadcaster clusters on Azure. When adding or editing a Broadcaster cluster, select an instance name such as “Standard\_N\*” to choose an instance with an embedded NVIDIA GPU. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/qkCt1gLr3xMnQianzc3y1_image.png" size="50" width="828" height="1018" position="center" showCaption="false"} WRITING HLS/DASH TO MEDIASTORE ZEN Master now supports writing HLS and Dash streams to AWS Elemental MediaStore. To use MediaStore select HTTP for the target type and then select MediaStore for the type. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/uX3VzMrLO2AShG-TI-oVv_image.png" size="46" width="1026" height="2386" position="center" showCaption="false"} MINOR IMPROVEMENTS AND BUG FIXES • Improved styling of stream visualization Channel diagram and made it the default tab when selecting a Channel. • Stream visualization diagram now include Hitless and Transcoded Sources. • Improved errors when Channel create/enable failed, e.g. if Broadcaster version doesn't support required features the feature will be mentioned with the minimal required version. • Creating or cloning a Target will now select the Target. • Monitoring of S3 Targets no longer requires the S3 bucket to be public. • Removed 'Low video quality' from Content Quality Analytics. It is superseded by ePSNR analysis that will be available with Broadcaster V13. • DASH outputs are now named “DASH + fMP4 HLS” . Preview playback is currently available only for the fMP4 HLS. Preview for DASH will be added later. • Added a white background to TR-101 status icons in Grids for better contrast. • Added info icons with tool-tips to clarify some fields. • Can now force Remote Access tunnels to use regular HTTP; automatic HTTPS/HTTP detection fails on some devices. • Improved Source stats API. • Improved events log filtering. • Removed Azure locations that don't support the required API commands. • Improved Source detection logic when multiple Broadcaster inputs with the same ID exist on multiple Broadcasters in the same cluster. Should prevent ZEN Master monitoring an intra-cluster Pull instead of the actual Source. • Improved /events API command to include additional filtering options and response fields. • Improved validation on many UI input fields. • Fixed ZEN Master reporting a generic error instead of input offline when the input is offline for a Broadcaster “Configure & Monitor” Source. • Fixed a rare race condition causing notification emails to not be sent. • Fixed object stats API call failing on time windows of more than 30 days. • Fixed stream visualization when user has no view permissions on some objects in the Channel graph. • Fixed an issue preventing Broadcasters on AWS EC2 from being deleted if the machine failed or was terminated via the AWS console. • Fixed an issue causing pages to load with empty object list when using a link to a specific object with cached search filter. • Fixed monitor only Pull stuck in pending mode when monitoring a saved Pull with a stream redirection. [title] ZEN MASTER OCTOBER 2018 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates have been pushed to ZEN Master on October 1, 2018. ## HITLESS FAILOVER CONFIGURATION FOR SOURCES ZEN Master now allows for configuration of Hitless Failover, which provides seamless switching between multiple binary identical source streams. V12 Broadcaster is required for Hitless Failover. To enable Hitless Failover, Add a new source and select Hitless Failover. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/V-iboqNGUCdI6_9PUiQXe_image.png" size="64" width="1574" height="1124" position="center" showCaption="false"} Next, select two or more binary identical sources ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/NAkDggNtgN1BoQ_3ZbcCv_image.png" size="54" width="1354" height="216" position="center" showCaption="false"} and save the new source. The new Hitless Failover source can then be added to a channel like any other source. X264 SOFTWARE TRANSCODING If a Broadcaster is licensed for the X264 software encoding codec, ZEN Master will automatically use that codec when configuring the transcoding profile for the Broadcaster. V1.11 Broadcaster or later is required to use the X264 codec. NOTIFICATION MUTE AND ACKNOWLEDGE When muting notifications, the user can now specify that the mute should be active until a date/time, after which it will automatically unmute. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/aFfQ67R3A2KRgrS7BVYjt_image.png" size="38" width="858" height="352" position="center" showCaption="false"} Additionally, the user can now acknowledge an error state on an item. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Az92XQepw0Tzba6PfFe5h_image.png" size="52" width="1190" height="474" position="center" showCaption="false"} When acknowledged, the red light on the item will be a lighter shade of red and a check mark will display next to the item showing it is in an acknowledged state. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/-5AU6p0PcDbAdU9U2V4OY_image.png" size="46" width="824" height="290" position="center" showCaption="false"} The item will also not be counted in the error totals in the Dashboard Status ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/AmHENbAQLysba6KJguJI5_image.png" size="56" width="1566" height="702" position="center" showCaption="false"} and on the left-hand pane of the ZEN Master page. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/h-CVXS-gsIdZXyVNgRt2P_image.png" size="18" width="494" height="434" position="center" showCaption="false"} Finally, the acknowledged item will not display on the OPEN ISSUES list on the Dashboard. SOURCE THUMBNAIL ROTATION DELAY The minimum delay on source thumbnail rotation is now 10 seconds instead of the previous 15 second delay. TIME AND AUDIO OVERLAY HIDING Overlays on the Sources thumbnail view can now be disabled in the case where they are covering important information. Visibility of the overlays is controlled by clicking the “OVERLAY (ON/OFF)” button. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/wQxuOyzeh5Ho910EjeoOx_image.png) DATE RANGE SELECTION ON HISTORY GRAPHS When viewing history graphs, the user can now select a predefined time period or specify a custom date/time range ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Gvy4KBc347Tsmj-mudPq7_image.png" size="20" width="358" height="550" position="center" showCaption="false"} ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/StSzSbVADmCiouW6vBuus_image.png" size="52" width="1458" height="704" position="center" showCaption="false"} and all history graphs on the page will adjust to the selected date/time period. FREE FORM NOTES The user can now enter free form notes on objects in ZEN Master including Feeders, Broadcast Clusters, Receivers, Sources, Channels, and Targets. Notes are autosaved as they are typed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/KF8QcD0E-OAbJFYrZ2tDh_image.png" size="82" width="2058" height="666" position="center" showCaption="false"} BROADCASTER BANDWIDTH LIMITS Input/output bandwidth limits for monitoring can now be set on the Advanced page when adding or configuring a Broadcast Cluster. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/53ZStE_dL8zp-OVOJL70a_image.png" size="46" width="1058" height="1982" position="center" showCaption="false"} When the bandwidth on a Broadcaster in a cluster exceeds the cluster limit, the Broadcast cluster will go immediately to an Error event. If notifications are enabled, bandwidth events will create notifications the same as other events. For clusters with manually created Broadcasters, the bandwidth limit can be set on the manual Broadcaster on the Advance page. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/GyShfCCzbUljImiqXED3M_image.png" size="52" width="914" height="1398" position="center" showCaption="false"} Limits on the manual Broadcaster takes precedence over limits on the Broadcaster cluster. CLONING CHANNELS AND TARGETS Previously, Sources could be easily cloned. Now, both Channels and Targets can be easily cloned. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/G_5bAC84SYoZQcurFERPf_image.png" size="82" width="2066" height="262" position="center" showCaption="false"} ## UDP/RTP TARGETS UDP/RTP targets are now supported. IP WHITELIST IMPROVEMENTS IP Whitelist on AWS clusters can now control the AWS security groups. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/MdfhjybxWhRmynO3TgFeT_image.png" size="40" width="1024" height="1240" position="center" showCaption="false"} LOGGING IMPROVEMENTS User actions are now logged with more details including mute and acknowledge and enable/disable have unique messages. [title] ZEN MASTER March 2019 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates were pushed to ZEN Master during the month of March 2019. GRID STATUS DISPLAY ZEN Master now includes a grid-based status display that provides a high density way to monitor Channels as well as all other objects being managed by ZEN Master. The grid display is highly configurable, including how many objects to show on one page, how much information to include in the status box for each option, and what type of objects to display. The example below shows a large number of channels on one page with only the channel name in the status box and with channels in error state sorted to the top. Additional details for a particular channel can be found by clinking on the channel name. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/w0zo-3i-ST5LHN5QSVbI1_image.png) The next example shows a “penalty box” where only sources in error state are displayed with relevant details in the status box. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/2c9mU5JKrZF7-sb-D0AmY_image.png" size="84" width="1836" height="654" position="center" showCaption="false"} The next example shows multiple object types – Feeders, Broadcasters, Sources, etc. – displayed on one page. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/vEUcRJaNzOUYkLRbMc2-9_image.png) To configure a new grid, select Grids in the left-hand pane and then click ADD GRID. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/LynobuCGaJTyIzQtLi0l9_image.png" size="88" width="1856" height="406" position="center" showCaption="false"} Next, provide a name for the grid and select desired parameters. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/lTCBvZe1oZywb2KJ0XTz-_image.png" size="88" width="1834" height="1770" position="center" showCaption="false"} To show multiple grids on one page for multiple object types, select Grids in the left-hand pane and then click ADD GRID GROUP. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/oV6mlyJ2XWtV4nqxjlhL2_image.png) Next, provide a name for the grid group, choose the grids you want to include, and select other desired parameters. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/mWHqGaQNfzrJUDwSweAP9_image.png" size="84" width="1820" height="994" position="center" showCaption="false"} Note that admin users can share grids to other users in the same ZEN Master domain; these grids will show up on the Public Grids pull-down. Grids defined by non-admin users will show up on the Your Grids pull-down. NVIDIA GPU MONITORING When using an NVIDIA GPU for transcoding, the details graph for Broadcasters now displays usage of the GPU decoder pipelines, usage of the GPU encoder pipelines, and usage of the GPU CUDA pipeline. GPU memory consumption is now also displayed in the details graph. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/qW2bSbaBjqQ_CrJWRWZon_image.png" size="76" width="1850" height="1218" position="center" showCaption="false"} BROADCASTER CLUSTERS IN AZURE ZEN Master now supports standard Broadcaster clusters in Azure. Support for NVIDIA transcoding Broadcasters will be supported in a future release. To run Broadcasters in Azure, click Microsoft Azure from the Settings in the left-hand pane and follow the displayed instructions. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/JaZJwejhy8YLymmHqsa-P_image.png" size="42" width="928" height="732" position="center" showCaption="false"} MINOR IMPROVEMENTS AND BUG FIXES • Fixed users without edit permissions getting logged out when attempting to edit notes • Confirmation popup, on delete action, will now close only after the action is done. • Modified adaptive channels on AWS clusters to default to 6 second segments to match the default on Zixi Broadcasters. The default segment duration can be updated under Advanced Options when creating/editing a transcoding Channel. • Reduced chance of false positive transcoded Channel/Source error reporting. • Fixed Broadcaster bandwidth monitoring that was not counting UDP outputs. • Fixed Broadcaster warnings in AWS clusters that were not escalating to errors. [title] ZEN Master 12 August 2025 Release Notes [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ ## New Features The following new features were implemented in this release: ### SPTS Multiplex Sources: - A new ZEN Master Source type is included, to support the Broadcaster’s SPTS Multiplexer (requires Broadcaster v19). - The result is a new SPTS stream with the interleaved PIDs. ![SPTS Source](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-lggW6hFV7nYR39_anRCyT-20250826-140904.png) - The User chooses the primary Source and lists the PIDs they wish to keep. - PIDs are specified with a comma separated list: - source\_pid, source\_pid - and can be optionally mapped with a ‘:’ symbol: - source\_pid\:target\_pid - PIDs must be entered, leaving the PIDs blank results in a Broadcaster error. ### Source stream information is now displayed in Target details - The Targets Stream Tab now displays the transport stream tree alongside the thumbnail. ![Source Stream for Target](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-It6Ymx1Kmac5GhxEBhhaQ-20250826-141306.png) ### Added option to ignore PIDs in TR101/CQA monitoring. ### Logo insertion on Transcode Profiles ![Logo Insertion in Transcode Profile](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-TysdIBlzK-Ae-d8_Bt4Aj-20250826-141551.png) - Logo can be enabled, via the transcode profile. - Its position (in pixels or percentages) can be configured along with the alpha channel value. - The logo is burned into the resulting video. ### Added 'External Link' to Live Events ### Live event objects can now include an external link. - The feature allows event creators to link an event to an external system for additional event metadata and scheduling information etc. ![External Link for Live Event](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-RSL5itoKVoXUoH_qDm7D9-20250826-142133.png) ### Broadcaster version upgrade/downgrade from ZEN Master - Manual Broadcaster upgrades can now be initiated from directly within the ZEN Master interface. - The installation tool is opened via the Broadcaster’s top right menu: ![Upgrade/Downgrade Broadcaster](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-XUieW5hojnyEK2ZTJgLvs-20250826-142701.png) - Once opened, the User can select a new version from the available list (as managed in the Customer Portal). - Hitting ‘Install’ uploads the version installer and initiates the upgrade. ![Select New Broadcaster Version](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-EuuD6fXUhbduWaQbRMIW8-20250826-142929.png) ## Improvements and Changes ### New monitoring rules for Low Video and Low Audio bitrates - Low bitrate thresholds are now definable in the event profile. ![Set Source Low Bitrate Thresholds](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-spKauPVSU5KpzODzwvcH7-20250826-143458.png) ### New monitoring rules for UDP send/receive errors on Broadcasters. ### Source selection in forms now uses full tables with advanced filtering. ### Added lifecycle logging to Tags. ### Added SAR/DAR, Language, PTS, Audio Channel info to stream information tree. ### Diagrams will now consolidate Targets into a single box when there are many of them. ### Where it makes sense added copy to clipboard button to table cells and details tiles. ### Added option to show Targets on Source diagrams and downstream objects tab. ### Reworked SRT passphrase to match SRT functionality. ### Added SCTE-35 logging to Failover Channels. ### Added Pass all PIDs toggle to Transcode Sources. ### Added DTS/PCR delta configuration to NDI Sources. ### ZEN Master will now log Broadcaster versions on connection and change. ### Renamed Multiplex Sources to MPTS Multiplex. ### Improved Failover Source/Channel Max bitrate calculation and added an override option. ### Updated Max Bitrate monitoring: - Use actual bitrate data instead of Broadcaster status to alert on Bitrate > Max Bitrate. - Alert on Max Bitrate too high (Max bitrate >= 40 Mbps and Actual bitrate \< Max Bitrate / 8. ### ZEN Master will now alert for invalid Broadcaster configuration of MPTS Multiplex Sources. ### Added x264 option to NDI Sources. ### Added many missing configuration options to details and info panels. ### Added raw SCTE-35 HEX column to SCTE-35 log tables. ### Implemented SCTE-35 support in Kafka. ### Implemented Error Concealment on all relevant Source types: - Zixi Pull, Inter-cluster, Failover, Rist, Srt, Udp/Rtp, PID Map, Demux, SPTS/MPTS, Mux, HLS, RTMP. ### Frame Thinning is now a boolean configuration: - API change - existing field is now treated as boolean instead of a number. - For v18 Broadcaster the latency is set to 1000ms. ### Error message polish. ### Frame Thinning is now a Boolean setting to match v19 Broadcasters: - On Broadcaster version 18, this will default to 1000ms. ## ESNI & ESAM ### ESAM - No longer trying to switch on PTS when there is no PTS. - Fixed POIS latency not doing anything. - Added Error Concealment support to POIS loopbacks. - Cleaned up 'no outputs' found logging. - Updated config template file with more realistic defaults. ### ESNI - Reworked switch on PTS to apply policy on PTS then switch. - Implemented full support for ISO 8601 durations. - Added missing @duration to Apply tags in Media GET response. - Added version endpoint. - XMLNS no longer required in 224 XML document. - Targets will now prioritize Channels with matching Target Broadcaster settings. - Use Audience ID and Audience namespace elements to math ZEN Master Targets. [title] Release Notes: Zixi Broadcaster Version 17 [path] Zixi Product Updates/Zixi Broadcaster Release Notes/ ## v17. 9.45910 (28 Jan 2025) ### Improvements - Added ability to bind to local port on SRT Push output and SRT Pull - Added scte\_hex parameter to add\_stream\_scte.json API endpoint to allow hex payload ## v17.8.45822 (2 Dec 2024) ### Improvements - Improved accuracy of SRT jitter metric - Added support for non-MPEG-TS large packets over DTLS, such as ATSC 3.0 - Added support for J420I color space in transcoding - Added support for non-AWS S3 compatible object storage ## v17.7.45729 (15 Oct 2024) ### Improvements - Exposed new "local port" parameter in advanced mode on Pull input and Push output. Allows control over source port so that specific ports can be opened on the firewall. - Allow 'seamless switching' of inputs that are connected to Pull outputs ## v17.6.45597 (21 Oct 2024) ### Improvements - Added support for user defined 'encoding width' which may be different than resolution width and will modify the aspect ratio in the video elementary stream. Supported for H264 (NVIDIA, x264) and HEVC (NVIDIA). - Added new UI option for MPTS multiplexer called "Drop inactive streams". When enabled (checked) the multiplexer will drop an input from the PAT table when it has been quiet for 5 seconds. When disabled (not checked) quiet inputs will not be dropped. Default is to be disabled (not checked). - Added retry mechanism when SCTE reporting to HTTP endpoint is unsuccessful - Added support\_scte configuration in streams.json API endpoint to indicate that SCTE-35 injection is enabled on an input - Updated transcoder behavior such that when "pass all PIDs" is selected it will protect against too frequent SDT and only allow SDT every 500ms ## v17.5.45533 (17 July 2024) ### Improvements - Added SCTE-35 injection via API on RIST sources - Improved SMPTE-2022-7 stream matching for failover on identical streams with corruption or long inactivity - Added support for High Performance Networking with DPDK on Oracle Cloud Infrastructure (OCI) with Mellanox NICs - Allow updating direction of ports on the fly when using High Performance Networking with DPDK - Added support for switching source on output according to the PTS of the NEW source in redirect\_client.json API endpoint - Added local UTC time to streams.json API endpoint results, alongside UTC time of last frame with PTS, and of last SEI timecode in analyzer - Reduced frequent log messages of push outputs from error to debug - Added SCTE-35 track in DASH MPD even if stream is not segmented on SCTE-35 messages ## v17.4.45467 (14 June 2024) ### Improvements - Updated analyzer to work on streams with multiple transport stream IDs. The active transport stream ID is displayed under PAT in analyzer PID tree in Broadcaster UI. - Added 'transport stream ID' field to MPTS demux input in Broadcaster UI. Not required and can be left blank. - Renamed "Support MultiAudio" option in Broadcaster UI adaptive group to "Send distinct audio/video elementary streams" - Added 'PCR interval' for Padding mode (under Remux) on UDP output in Broadcaster UI - Added user\_data field to streams.json API endpoint return value for PID map and failover\_group inputs - Added ability to manually change between inputs in a failover group using 'lock' feature in ZEN Master UI without creating CC errors - Added CBR padding option to error concealment in Broadcaster UI - Added support for HTML overlay with 4:2:2 sources during software transcoding; NVIDIA does not support 4:2:2 - Added Registration, CueIdentifier SCTE descriptors for SCTE injection - Added new "Drop inactive streams" checkbox option in Broadcaster UI on MPTS input streams ## v17.3.45386 (6 May 2024) ### Improvements - Improved performance of software transcoding on Intel & AWS Graviton 2/3 CPUs - Added support for transcoding from 4:2:2 chroma, which NVIDIA does not support, to 4:2:0 chroma, which NVIDIA does support. The decode uses CPU while the encode uses NVIDIA GPU for optimal performance. - Added Broadcaster ID to the add\_stream.json API response to enable verifying the API call was made to the intended Broadcaster instance - Added “Registration Descriptor” and “Cue Identifier Descriptor” to SCTE-35 injection - AgentZ is now included in the Broadcaster installer ## v17.2.45345 (2 April 2024) ### Improvements - Added ability to switch sources on Zixi Push outputs when provided PTS was detected on the specified source video PID, API only feature - Split “Toggle recording" under the Marked menu in the UI into two separate actions: 1. Start recording and 2. Stop recording. - Added new global setting to allow "Minimize Latency" to be default on automatic Zixi Push inputs - Added more informative error when libSRT cannot open a socket - Added ability to control audio gain in the transcoding audio profile, valid for all audio codecs - Added support for Closed Caption extraction from MPGV video sources. Captions are re-encoded into H.264 and HEVC output streams, but are not re-encoded into MPGV streams. - Added WallClockTime parameter to SCTE-35 reporting ## v17.1.45293 (Feb 2024) ### Improvements - Added support for parsing of SCTE-35 messages with time\_signal command, splice command type 6 - Added parsing of SCTE-35 type 6 and converting to splice\_insert command for adaptive streaming - TR101 analyzer now exposes PIDs not associated to any program (excluding MPEG-TS tables) - TR101 dialog now shows audio levels for Opus audio codec when CQA is enabled - Allow clean-up of automatic push inputs and clearing of automatic push inputs in error state - Disabled 'user' login by default for improved security - Upgraded libSRT library to 1.5.3 - Optimized CPU for Push input flows - Improved the error concealment of bad frames to have less - Added output of hostid info used for licensing to syslog - Updated DASH timing information to include number of PCR wraparounds since 1.1.1970 - Added support for PLANED\_DURATION in DATARANGE tag in HLS - Updated traceroute timeout to be configurable and automatically refresh results when ready with ETA timer, removed manual 'refresh' button from traceroute - Improved bonding by avoiding sending data packets over congested networks - Optimized tc qdisc queue limit on all Linux OSes - Updated Inter-packet gaps on RTP input to use RTP timestamps instead of arrival times when dejittering is on, to reflect the real IAT - Add 'dist\_overflows' statistics to sources, to indicate internal buffer overflows on the outputs of the source due to performance ## v17.0.45227 (9 Jan 2024) ### High Performance Networking Throughput of the Zixi Broadcaster has been improved by about 3X for UDP based streams – Zixi, RIST, RTP/UDP – by using the Data Plane Development Kit (DPDK) to bypass the operating system for network interface card (NIC) management. Of course, it is recommended to use the Zixi protocol whenever possible for the best reliability and error recovery. When using DPDK, one NIC in the machine will be dedicated to UDP-based video traffic and is managed completely by the Broadcaster. As a result, on modern hardware you can expect a Gigabit per second or more per vCPU and you will no longer have UDP port bandwidth limitations of 500Mbps or so per port. On a machine with many CPUs, the NIC itself and not the operating system will likely be the bottleneck. 10Gbps NICs or greater are recommended. Because one NIC is completely dedicated to video traffic in and out, the machine must have a second NIC for typical operating system functions and to access the Broadcaster’s web UI. DPDK requires certain Linux kernel versions, certain network cards and driver versions, and certain BIOS versions. Zixi will provide AMIs for AWS upon request by sharing the AMI to the customer’s account. Reach out to your Zixi representative to make the request. On AWS, the Broadcaster’s High Performance Networking is supported on machines with either X86 64-bit or Graviton 2/3 ARM 64-bit processors and an Elastic Network Adapter (ENA). For more information on ENA, see [https://docs.aws.amazon.com/whitepapers/latest/real-time- communication-on-aws/use-enhanced-networking-ec2-instance-types.html](https://docs.aws.amazon.com/whitepapers/latest/real-time-communication-on-aws/use-enhanced-networking-ec2-instance-types.html). On non-AWS machines, X86 64-bit will be supported, but ARM 64-bit may or may not be supported. The specific ARM system will need to be evaluated first to determine compatibility. For images on other cloud vendors or to use DPDK on bare metal servers please reach out to your Zixi representative for further assistance. Support for Broadcasters using High Performance Networking in ZEN Master will be addressed in future ZEN Master releases, but initially ZEN Master will not support launching and managing these Broadcasters. ### Live Preroll/Midroll Switching The Zixi Broadcaster now allows you to switch from a live stream input to the beginning of a file input and then back to the live stream input when the file reaches its end. This feature makes it possible to insert an advertisement or a fixed length slate or blackout directly into the live stream output. During the playout from the file, the live stream input is not sent to the output. This feature will be available via API only for integration into stream switching or live event management solutions such as the Live Events page in ZEN Master. ### Timeline Normalization The timeline normalization feature repairs timelines (PCR, PTS, DTS) in the transport stream. Timeline errors could have been introduced by upstream encoding and processing or by ingesting other protocols into the Broadcaster, such as HLS, that may not have clean timelines. Some IRDs are very sensitive to timeline issues and this feature may improve stream ingest by those IRDs. Timeline normalization is available under the “Fix” option on the menu on each input. Using the Fix option, a new input stream will be created with the appropriate processing while the original input is left untouched. ### Frame Error Concealment The frame error concealment feature will replace video frames containing errors with skip frames while keeping the audio in sync. This feature may be helpful when there is unrecoverable packet loss on input streams that corrupts some video frames. It currently works with the video with the following parameters: - Codec: H.264 - Chroma sub sampling: 4:2:0 , 4:2:2, or 4:4:4 - Chroma/luma bit depth: 8-bit or 10-bit - Scan: progressive or interlaced Some video players, such as VLC, have their own techniques for masking errors so comparing the original stream and the error concealed stream in VLC may not show an improvement. However, downstream devices that do not have their own techniques for masking errors may benefit from this feature. Frame error concealment is available under the “Fix” option on the menu for inputs. Using the Fix option, a new input stream will be created with the appropriate processing while the original input is left untouched. ### HTML Overlays The Zixi Broadcaster can now render and overlay HTML web pages on top of a transcoded video stream. This feature can be used for adding scoreboards, lower thirds, scrolling tickers, and other dynamic graphics to live video streams. Currently this feature is only available on AWS EC2 instances with an X86 64-bit processor and an NVIDIA GPU. Zixi will provide AMIs for AWS upon request by sharing the AMI to the customer’s account. Reach out to your Zixi representative to make the request. On these AMIs the Zixi Broadcaster cannot be upgraded via the Broadcaster UI so Zixi will make AMIs available for each release and/or provide instructions for upgrading the Broadcaster via command line. ### macOS Support The Zixi Broadcaster and ZEC are now available for Intel and Apple silicon (M1/M2/M3) based Mac computers. The Broadcaster is officially supported on macOS releases currently supported by Apple, but it should work on macOS 10 and later. In this release, transcoding is not supported on Mac, which also means NDI and webRTC will not be available as they use transcoding. ### Operating System Update V17 of the Zixi Broadcaster should work on operating system versions previously used on V16 Broadcasters. However, Zixi strongly recommends upgrading from RHEL 7.x and 8.x equivalent operating systems, such as CentOS or Oracle, to RHEL 9.3 equivalent operating systems, such as Alma 9.3 or Rocky 9.3, as 7.x and 8.x have been or will be end-of-life soon. On AWS, Zixi recommends upgrading from Amazon Linux 2 to Amazon Linux 2023. See the V17 for more details. ### ZEN Master Update Due to some infrastructure changes, ZEN Master will not, by default, be able to launch V17.0 Broadcasters on AWS/GCP/Azure until the February 20, 2024 ZEN Master release. Until then you can have ZEN Master launch a V16.11 Broadcaster and then upgrade to V17.0 in the Broadcaster UI or you can make a request to your Zixi representative to have your account in ZEN Master updated to be able to launch V17.0 Broadcasters. ### Licensing Update The V17 Broadcaster has two additional licensing servers that it needs to communicate with. If you have previously needed to whitelist licensing servers in your firewall, please add the following IPs to your whitelist: - 3.140.62.221 - 3.137.16.26 ### Protocol Updates Listed below are improvements and bug fixes to the various protocols supported by the Zixi Broadcaster. - Zixi - - Add traffic shaping option to limit the momentary bitrate spikesRIST - Add traffic shaping option to limit the momentary bitrate spikes - Fixed issue with multiple RIST Main profile Pull inputs allowed to use the same remote\_ip/remote\_port - UDP/RTP - Fixed inability to select checkbox "keep RTP headers" on RTP inputs - Fixed rare case of packet drop in RTP stream, when one of the streams in a failover group is not RTP, but others are RTP. - HLS - Fixed issue with HLS playlists having EXTINF values set to 0 instead of the segment duration - DASH - Fixed issue with upload of DASH .mpd playlist - Fixed issue with chunking for DASH due to bad PTS - Fixed recording on DASH with only video - Fixed segment duration sizes not showing correct in Manifest files - Fixed webVTT subtitles file path for DASH with flat path - Fixed segment path in DASH with flat path - SRT - Updated SRT library to v1.5.2 - Fixed issue with multiple SRT clients allowed to use the same port ### Transcoding Updates The V17 Broadcaster now requires NVIDIA CUDA 12 and related driver versions; the v535.129.03 driver or later is supported. The V16 Broadcaster used CUDA 11. If you upgrade from a V16 Broadcaster to V17, the Broadcaster will not recognize the NVIDIA card until the NVIDIA drivers are updated as well. Reach out to your Zixi representative for guidance on updating the drivers if you need help. Other changes are listed below: - Updated x264 library to build 164 for software based H.264 transcoding ### Performance/Memory Improvements Improvements to the performance of Zixi Broadcaster are listed below. - Reduced memory utilization for Zixi inputs and outputs - Reduced memory utilization for RTP inputs and outputs - Reduced memory utilization for adaptive streaming - Updated minimum CPU requirements on Intel builds to be 'westmere' architecture or newer (SSE 4.2 instructions) ### Additional Improvements - Added search filter for displaying NIC statistics on the Settings page in the UI. Fields that have a value of 0 are not displayed. - Added warning when different stream content is detected in failover group in failover merge mode - Added a setting that allows a failover group to remain on the Secondary stream even when the Preferred stream returns - Eliminated unnecessary CC errors in TR-101 analysis when the input stream has TS discontinuities - Added stream name in logs for TR-101 logging - Added support for seamless input switching on HEVC and MPGV streams; H.264 streams were previously supported. - Added updating the SDT table when mapping or removing a program - Improved inputs and outputs ports configuration on Settings General page in the UI - Removed possibility of ports settings issues that could be caused by incorrect API call - Added the "All" option for NICs for bonded outputs. Needed for feature parity for ZEC with the end-of-life Zixi Feeder. - Updated OpenSSL library used for DTLS and HTTPS to v3.1.1 - Added bitrate and buffer size in TR-101 stream analysis for HEVC stream - •Updated ARM Broadcaster install directories to be more descriptive of the actual compiler optimizations for the build – “graviton2” is now “neoverse-n1” and “raspberry” is now “arm64” - Added detection of more processor models on the Status page, instead of showing "Not Specified" - Increased maximum supported bitrate for adaptive HLS streaming to \~70mbps - Added "Remote" to host/port/stream parameters label on pull and SRT input types, to avoid confusion between local and remote Stream IDs ### API Updates - Added new parameter called “priority\_switch\_mask” in failover group API that allows a failover group to remain on the Secondary stream even when the Preferred stream returns. - Added "tsid" param to the PID mapping API. This parameter will tell the PID mapper which "transport\_stream\_id" it needs to lock on. This will prevent the PID mapper from restarting when there are several PAT packets with different "transport\_stream\_id" if not provided or if set to -1, the PID mapper will use the first "transport\_stream\_id" it detects. - Added "switch to file" API for server side ad insertion - Added support for journalctl API to download log messages instead of /var/log which does not exist on Amazon Linux 2023 - Live preroll/midroll switching described above ### Downgrading from V17 to V16 To have installation folder names that represent the compiler optimization for ARM builds instead of brand names, the old folder name “zixi\_broadcaster-graviton2” is now “zixi\_broadcaster-neoverse-n1” and “zixi\_broadcaster-raspberry” is now “zixi\_broadcaster- arm64”. When you upgrade a Broadcaster from V16 to v17 using the web UI, the new directory will be created and the necessary config files will be copied over to the new directory. The previous directory is not removed. Also, the zixibc service which runs the Broadcaster as a service will be updated to point to the v17 Broadcaster in the new folder. If you need downgrade back to V16, the original directory will be used again and the zixibc service needs to be updated to point to the v16 Broadcaster in this directory. Also, if you made any changes to the Broadcaster configuration while using v17, the configuration files need to be copied over to the v16 Broadcaster directory. If you made any license changes to the Broadcaster configuration while using v17, the license file needs to be copied over to the v16 Broadcaster directory. The following steps will downgrade your installation from the v17 Broadcaster to the original v16 Broadcaster: ```bash $ service zixibc stop $ cd zixi_broadcaster-graviton2 $ cp ../zixi_broadcaster-neoverse-n1/*.xml . $ cp ../zixi_broadcaster-neoverse-n1/broadcaster.lic . $ ./installMe.sh ``` or ```bash $ service zixibc stop $ cd zixi_broadcaster-raspberry $ cp ../zixi_broadcaster-arm64/*.xml . $ cp ../zixi_broadcaster-arm64/broadcaster.lic . $ ./installMe.sh ``` This change only affects Linux ARM builds of the Broadcaster when updating from V16 to V17; X86 builds are not affected. However, X86 installation names were updated between V15 and V16. If you need to downgrade from V17 to V15 a process similar to that shown above would be used, but with different folder names. [title] ZEN MASTER January 2022 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be included in the ZEN Master January 26, 2022 release. Features The following new features were implemented in this release: • Insights view in the Intelligent Data Platform (IDP) o Infrastructure Insights identify outliers among various operating parameters on Zixi Broadcasters, such as memory and CPU, that impact video delivery. o Channels Insights identify network anomalies on Sources and Targets that impact video delivery. • Management of Zixi Edge Compute (ZEC) endpoint devices. More details on ZEC devices are coming soon. • Dark mode across whole ZEN Master site • Multi-edit for Tags and Event Profiles. The user can now multi-select objects and edit the selected objects to overwrite, add, or remove Access Tags. The user can also multi- select objects and update the Event configuration profile used for those objects. • CDI & JPEG-XS Sources and Targets in AWS MediaConnect Flows • Maintenance mode for Broadcasters that prevents new streams from being assigned to that Broadcaster. This feature might be used in the following scenarios: o Scheduling a Broadcaster to be taken out of service for maintenance or upgrade o Adding a new version of a Broadcaster to a cluster for testing and validation prior to enabling production usage o Adding a Broadcaster to a cluster where necessary configurations on the Broadcaster, such as firewall setup, are still pending • Primary/Backup Sources on Pass-through Channels with Source preference selection on Targets Additional Improvements The following additional improvements were implemented in this release: • Updated Transcoding Channel output paths on HLS origin servers to remain constant even when moving the Channel between Broadcasters or Clusters • Updated sorting by status to be consistent across all object types • Improved time to first connection when using Pull targets on clusters with multiple Broadcasters • Added alert on missing CEA-608/708 closed captions on Sources • Added API key name to API logging for better visibility • Added the display of active Source to Targets on diagrams and Source type to Sources on diagrams • Added field for Maximal DTS-PCR delta on transcoded CBR Sources • Added FFA authentication support for RTMP push Sources • Added support for selectable NIC on RTMP Pull sources Additional Improvements for Use with V15 Broadcasters The following additional improvements were implemented in this release: • Added indication on Source detail page when RTP headers are included on Zixi sources • Added display of declared bitrate and HRD buffer size in TR-101 data • Added radio selector to enable CBR by padding mode for UDP/RTP and RIST Targets • Added estimated VMAF history graph for Sources • Updated audio transcoding profiles to apply to all audio PIDs Bug Fixes The following issues were resolved: • Fixed multiple issues with diagram rendering • Fixed SCTE reporting errors • Fixed issue not being able to choose port auto-select for RIST Pull Source • Fixed multiple issues when using Monitor Only Sources as inputs for other Sources • Fixed issue with packet delivery % graph showing bitrate in % instead of kbps • Fixed API timeout issues between ZEN Master and Broadcasters causing inconsistent states when configuring Channels • Fixed issue with SCTE35 graphs on Sources not showing any data • Fixed SRT graphs showing bitrate in hours instead of kbps • Fixed issues with diagrams not loading for users that have partial permissions on objects • Fixed issue with pass-through Channels with no Targets reporting missing Source errors • Fixed issue with Events configuration profile is not being displayed on the Cluster detail page or the Broadcaster detail page • Fixed issue with Push Targets to MediaConnect • Fixed issue with MediaConnect Pull Targets only working for first connected device • Added appropriate error messages for WebRTC playback issues • Fixed error when adding AWS Account • Fixed issue with "target not found in cluster" errors • Fixed “unexpected error” issue HTTP Target history graphs • Fixed issue with missing alert notification emails [title] ZEN MASTER June 2020 RELEASE NOTES 2 [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates were pushed to ZEN Master on June 22, 2020. Multiple GPU Management You can now manage Zixi Broadcaster instances with multiple GPUs, so that when you are running heavy transcoding activities, you can ensure that the load is distributed among several different GPUs. For each transcoding activity done on a Source or a Channel you can now specify which GPU instance it is assigned to, enabling you to balance the load. Currently, multiple GPUs are only supported on Broadcaster instances launched by ZEN Master on AWS and the AWS instance needs to have multiple GPUs, such as the g4dn.12xlarge. Assigning Multiple GPUs for Transcoded Sources The Create/Edit Transcoded Source screens now include an Assign to GPU checkbox. You can select this checkbox in order to assign the transcoding to a Broadcaster with multiple GPUs and specify which GPU instance to use. This feature is only relevant for Sources for which the Ingest Cluster includes a Broadcaster with multiple GPUs (or can spin up a multi GPU instance). 1\. 2. Select the Assign to GPU checkbox. Click on the field that opens below the checkbox and select a GPU instance (instances are designated as 0-3 in this example). ### Assigning Multiple GPUs for Transcoded Channels The Create/Edit Transcoded Channel screens now include an Assign to GPU checkbox. You can select this checkbox in order to assign the transcoding to a Broadcaster with multiple GPUs and specify which GPU instance to use. This feature is only relevant for Channels for which the Processing Cluster includes a Broadcaster with multiple GPUs (or can spin up a multi GPU instance). 1\. 2. Select the Multi GPU checkbox. For each Transcoding Profile that you apply, specify which GPU instance it is assigned to (instances are designated as 0-3 in this example). Configuring SCTE-35 Conversion and Timecode for HLS For HLS Adaptive and Transcoded Channels you can now control the system behavior for SCTE- 35 cue point conversion (ZM-900) and timecode insertion. ### SCTE Conversion The default behavior is to convert both CUE-OUT and CUE-IN cues. In the Advanced settings, you can now choose to convert only CUE-OUT cues or to not convert any SCTE-35 cues. ### Timecode Insertion You can also adjust the settings for timecode insertion. The default behavior is to insert the timecode based on the system time. In the Advanced settings you can now choose to insert the timecode using the SEI Timecode or to not insert the timecode at all. ### MINOR IMPROVEMENTS AND BUG FIXES The following minor improvements were implemented: • A Help link is now available in the header bar that directs you to the ZEN Master online documentation. The following issues were resolved: • Fixed issue where ZEN Master was unable to launch GCP Broadcasters without GPU • Fixed issue where editing a Target was erroneously warning of a Broadcaster restart • Fixed sorting by status on some pages • Fixed error message text when attempting to delete a Broadcaster from a Cluster • Fixed many UI typos and missing fields and implemented general UI polish • Updated PID mapping feature to match Broadcaster v14.0.39309 [title] ZEN MASTER July 2020 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates were pushed to ZEN Master on July 8, 2020. Old UI End of Life Notice In April 2020 Zixi introduced a new UI for ZEN Master. In the June 3rd release the new UI was set to be the default with a button allowing the user to switch to the old UI. In this release that button is removed but the old UI is still available, for emergency purposes, by specifying its URL in the browser. In the early August release of ZEN Master, the old UI will be retired completely and no longer available. SCTE Logging ZEN Master now enables you to monitor, in real-time, the SCTE-35 markers (including metadata) for live video content in Zixi Broadcasters; it is available in both v13.1.39560+ and in v14. ZEN Master shows recent SCTE-35 markers in both event list and graphical form, flags issues in the ad marker sequences that may require attention, and saves the logs for historical analysis. This enables the user to remediate problems that occur in real-time and also to provide their customers with proof that the SCTE-35 markers triggering insertion of advertisements were transmitted successfully to their destination. A Zixi Broadcaster receiving contribution feeds can provide SCTE-35 analysis on that segment of the workflow while a Broadcaster located at the receiving location and ingesting distribution feeds can provide SCTE- 35 analysis on the whole workflow. ZEN Master monitors SCTE-35 markers on any inputs that natively use transport stream including Zixi TS, TS over RTP/UDP, RIST, SRT, and HLS with TS segments. The SCTE-35 markers are captured on ZEN Master Sources and analyzed on the Sources page in the UI. SCTE-35 event logs are stored in ZEN Master for one month. SCTE-35 events can also be sent to a Kafka server for further processing and long term storage. SCTE-35 events that escalate to warning or error will also be captured in the standard event log as alerts. ### Activating SCTE-35 Logging Because SCTE-35 logging can be resource intensive, the default behavior is not to log SCTE-35 markers. If you would like to log SCTE-35 markers for a particular Source you need to activate SCTE-35 logging in the Source configuration and also in the Broadcaster Cluster configuration of the Ingest Cluster that is being used. First select the Log SCTE-35 checkbox in the Broadcaster Cluster configuration to enable SCTE- 35 on the Ingest Cluster and the Broadcasters in that Cluster. Next select the Log SCTE-35 checkbox in the Source configuration to enable SCTE-35 logging on that particular Source. Once you have enabled SCTE-35 logging, you have the option to also select Enable SCTE-35 alerts. Selecting this checkbox enables ZEN Master to flag issues in the ad marker sequences that may require attention. ### SCTE-35 Logs All SCTE-35 messages for all Sources (with SCTE-35 alerts activated) are shown on the Logs > SCTE-35 screen. A record is shown for each SCTE-35 event with general info about the message. In addition, you can click on the Details button to view a JSON containing the raw message and a parsing of the message content. The results on this screen can be filtered by one or more of the following filters: Message text, Date Range, Access Tags (multi-select), and Sources (multi-select). You can send all SCTE-35 logs to a Kafka server by selecting SCTE-35 in the Kafka configuration. ### SCTE-35 Alerts For Sources on which SCTE-35 alerts are enabled, alerts are generated whenever ZEN Master identifies a problematic sequence of ad markers. These alerts are shown on the Logs > Events screen together with other alerts generated in ZEN Master. SCTE-35 alerts are generated for problematic sequences, such as: • When an End marker occurs with no related Start marker. • When no End marker is detected within the expected timeframe following a Start marker. ### SCTE-35 Source Display When you select a Source on the Sources screen, detailed info about the Source, divided into sections is shown on the right side of the screen. For a Source that has SCTE-35 logging and alerts activated, the following info is shown: • The Details section shows the status for Log SCTE-35 and SCTE-35 Alerts as Enabled. • The SCTE-35 section shows the SCTE-35 Alerts that were logged for this Source. • The History section shows a graph with the distribution of SCTE-35 messages of various types over time. Hovering over a data point shows details about the message content. You can select from the legend which PIDs to display. ### Minor Improvements and Bug Fixes The following minor improvements and bug fixes were implemented: • TTL is now configurable for UDP/RTP Targets • Added SRT Targets to Automation • Fixed issue where disabling a Channel was deleting UDP Sources • Fixed issue where SRT Targets were not deleted when disabling/deleting a Channel • Fixed monitoring S3/MediaStore Targets with custom playlist names • Fixed issue with Broadcaster events log being spammed with "output updated" on Azure and GCP Targets • Fixed issue with SRT targets displayed with incorrect status/color in Grids • Fixed issue with being unable to configure active/active Targets in the new UI • Fixed backend error when creating/enabling a pass-through Channel with 2 Sources and SRT targets [title] ZEN MASTER June 2020 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates were pushed to ZEN Master on June 3, 2020. PID Mapping ZEN Master with v14 Zixi Broadcaster now allows PIDs in Source streams to be mapped to different PID numbers or to have their content nulled out or to have the PID with its content removed. The PIDs to be processed can be selected by the existing PID number, or by the stream category, or by the stream type. PID mapping in ZEN Master uses the concept of profiles where you define one or more PID mapping profiles and then those profiles are applied to Sources. To create a PID mapping profile, select Transformations->PID Mapping Profiles from the left menu. Add a new profile. Give the profile a name, select Access Tags, select the Default Action (see below) and select whether the Source stream will be a SPTS or MPTS. In the case of MPTS you will also select the Program Number of the stream inside the MPTS that you want to process. Next, choose the rule type. Select Elementary PID # to select by the PID #. Use the Action pulldown to choose to map it to a new PID number, set the content to null, or remove the content. The Stream Category selection allows you to specify a category of PID that will be mapped to a new PID \#. The first PID found in the stream that matches that category will be mapped to the new PID #. The Stream Type selection allows you to specify the type of PID that will be mapped to a new PID #. The first PID found in the stream that matches that type will be mapped to the new PID \#. Use the Plus button to define multiple PID mapping rules. After saving the PID mapping profile, you have two ways to use it. One way is to map the PIDs on a Zixi, UDP/RTP, SRT or RIST Source, which will result in all Targets connected to the Channel using that Source receiving the same mapped stream. The second way is to create one or more new Sources, with different PID mappings, from an existing Source. With this method, you can set up multiple Channels with different PID mappings so that you can send differently mapped streams to different Targets. To PID map a normal Source, select the PID Mapping profile when adding or editing the Source. To create Sources with different PID mappings from the same Source, create a new “PID Mapping” Source as many times as necessary. Fill in required fields for the new Source and select the PID mapping profile. With either method, Channels and Targets using these Sources will include the specified PID processing. ### MINOR IMPROVEMENTS AND BUG FIXES The following minor improvements were implemented: • The new UI introduced in April 2020 is now default. The old UI is still available via a button in the banner. • Added support for SRT Pull type Targets. Note, SRT requires v14 Broadcaster. • Added a confirmation dialog when editing an object would require a restart of the object since restarting that object would result in a temporary stream disruption. • Improved validation and error handling in Name fields • Added Broadcaster Cluster search by dns\_prefix • AWS/GCP/Azure account names are now visible in Cluster details • Added link to Transcoding Profile in transcoded Source details • Now shows 0 bitrate on Sources at 0 bitrate The following issues were resolved: • Fixed issue with creating a second transcoded Source on a single Source • Added missing error handling on Add Broadcasters button [title] ZEN MASTER October 2019 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates were pushed to ZEN Master on October 28, 2019. TRANSCODER LOAD BALANCING When ZEN Master assigns a new Channel to a Broadcaster in a Broadcaster cluster, it looks for a Broadcaster that is already connected to the relevant Source and for a Broadcaster that is currently in a good state. A Broadcaster is in a good state so long as its error thresholds - HDD, CPU, Memory, GPU, GPU Encoder, GPU Decoder, GPU Memory – do not exceed the default or user specified values. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/H5YNEUym8w32oAncXaAXi_image.png" size="74" width="1748" height="704" position="center" showCaption="false"} If no Broadcasters are currently connected to the relevant Source and are in a good state, then ZEN Master will look for another Broadcaster in the cluster in a good state, connect the Source, and deploy the Channel. When adding a typical non-transcoding Channel to a Broadcaster, the CPU and memory usage will increase a small incremental amount with each new Channel. For this reason, thresholds can be relatively high without risking have a new Channel take the threshold over 100. However, transcoding channels use significantly more CPU, GPU, and memory and adding a transcoding Channel to a Broadcaster already at 85% GPU, for example, could take the GPU consumption to 100% and cause performance issues. ### TRANSCODER THRESHOLDS To increase the reliability of deploying new transcoding channels or restarting transcoding channels if Broadcaster servers go offline, ZEN Master now provides a second set of thresholds used specifically for assigning transcode Channels to a Broadcaster in a cluster. The thresholds are used to define the good state of a Broadcaster, as mentioned previously, specifically for transcode channels. The thresholds have default values and can defined by the user by clicking Transcode Thresholds when adding or editing a Broadcaster cluster. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/P6EiUtK_cFXru-U6HJSGZ_image.png" size="58" width="1162" height="2206" position="center" showCaption="false"} Depending on how much CPU, GPU, and memory the transcode profiles being used will consume, the thresholds can be set to optimal values to allow as many transcode channels as possible to be assigned to the Broadcaster without overloading it. If no Broadcasters in a good state are available in the cluster, the user will be notified upon trying to save the new Channel. TRANSCODER BROADCASTER ASSIGNMENT ZEN Master also offers an alternative approach to managing the load of transcoding on Broadcasters by allowing the user to explicitly assign transcode Channels to specific Broadcasters in a cluster. When creating a new transcode Channel, a dropdown called Target Broadcaster allows the user to choose a specific Broadcaster from the processing cluster selected just above in the dialog. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/rZNTbV2HE0yNnxawJ02FV_image.png" size="48" width="1116" height="1012" position="center" showCaption="false"} Note, this approach can only be used for non-AWS clusters. When using AWS clusters, AWS manages the virtual machine instances, including automatic removal and replacing of instances experiencing hardware issues. In this case, there is no consistent identity for a Broadcaster instance to link to the Channel so ZEN Master cannot assign specific Broadcasters to the Channel. The transcoder threshold approach, described in the previous section, is recommend for AWS clusters. For Azure, GCP, and manually created Broadcaster clusters, the user will be able to select which Broadcaster to use for the Channel. It is the responsibility of the user to determine that the selected Broadcaster will not be overloaded by the new transcode Channel, and if so, move that Channel to another Broadcaster. ### MINOR IMPROVEMENTS AND BUG FIXES • Added paging for long lists of Grids. (ZM-306) • Added filter by Access Tag to reports. (ZM-327) • Updated VLC plug-in links to v13 (ZM-321) • Duplicate Sources in delivery Channel are no longer allowed. (ZM-348) • Removed and deprecated Quick Report button on the dashboard. It will be replaced by a new events log functionality in a coming release. (ZM-317) • Fixed issue where Broadcasters were not visible to non-admin users in Grid display. (ZM-305) • Fixed issue where editing objects with no changes causes UI .update() error. (ZM-312) • Fixed Receivers rendering as r\_xxx when user doesn't have any permissions on the Receiver. (ZM-313) • Fixed error when attempting to delete Target after it's Channel has been deleted. (ZM-339) • Fixed issue where editing access tags causes a full re-implementation of some Targets. (ZM-341) • Fixed issue with "No active broadcaster" showing on Channel diagram instead of Broadcaster name and green status when user has no permissions on the Source. (ZM-342) • Fixed error when muting AWS clusters. (ZM-343) • Fixed issue where users without permissions still see Delete, Edit, and Mute buttons. (ZM-345) • Fixed “Error 401 Unauthorized” when adding new Targets. (ZM-349) • Security update – Enhanced permissions and now sanitizes all input for HTML/JavaScript. (ZM-314) • Security update – Require current password on user self-edit, enforce strong password policy, and block weak cyphers/imported public keys. (ZM-315) • Security update - Session timeout reduced to 10 minutes. (ZM-316) [title] ZEN MASTER DECEMBER 2018 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates were pushed to ZEN Master on December 5, 2018. CREATING NEW SOURCE FROM TRANSCODED SOURCE ZEN Master now allows you to create a new Source from a transcode of an existing source. A typical use case for this feature would be to create a rendition of a live stream suitable, in terms of bitrate and codec, for publishing to YouTube Live or Facebook Live via RTMP. For the RTMP example, start by adding a new source and select the type “Transcoded”. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/umGR1HuN6wFo90tSJrZGM_image.png" size="78" width="1814" height="1428" position="center" showCaption="false"} Define the name and other parameters for the source and choose one of your pre-existing Transcoding profiles. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/5hcgE-OllReBZGW5TsjGl_image.png" size="90" width="1390" height="1320" position="center" showCaption="false"} Next, define a new pass-through channel using the source that you just created. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Aq46K4tRDzIF788c3wX_L_image.png" size="68" width="1310" height="998" position="center" showCaption="false"} ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/D0NJGqmNfcOMKkGT1Z6Qe_image.png" size="68" width="1404" height="936" position="center" showCaption="false"} Next, create a new RTMP target. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/OdXgtXHUciehrZZ__pAQg_image.png" size="58" width="1098" height="1126" position="center" showCaption="false"} Finally, select the channel you just created for the new target and fill in the publishing details for the RTMP server. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/tm3A7rLwO8FEyjK6zzkDc_image.png" size="64" width="1168" height="1528" position="center" showCaption="false"} HITLESS FAILOVER CONFIGURATION FOR RECEIVERS Hitless Failover provides seamless switching between multiple binary-identical source streams. Previously, ZEN Master allowed configuration of Hitless Failover between multiple sources feeding a channel on a Broadcaster cluster. ZEN Master now allows for configuration of Hitless Failover on Receiver endpoints. To enable Hitless Failover, Add a new source and select Hitless Failover. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ztJQEXe9aBq7F1Eb7ib7u_image.png" size="78" width="1616" height="1224" position="center" showCaption="false"} Define multiple identical sources for this new Hitless Failover source. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/sPxxiYo5HB3kcQe9lZ_XW_image.png" size="74" width="1560" height="1158" position="center" showCaption="false"} Create a new passthrough channel with the new Hitless Failover source and then add a new target and select Pull. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/yzqZmdOdGiPkzogzt1CS0_image.png" size="74" width="1554" height="1766" position="center" showCaption="false"} Select Active/Active in the Pull target dialog to enable Hitless Failover. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/U_S7tmJsApm2qXjbVjoP9_image.png" size="68" width="1546" height="534" position="center" showCaption="false"} If the channel has two sources defined, the Receiver will pull both sources of the channel and combine them using Hitless Failover, starting with v12.2 Receivers, or it will configure two inputs for one output on older Receivers. V12 Broadcaster is required for Hitless Failover. BITRATES CALCULATION FOR HLS/DASH MANIFEST When defining transcode profiles for a transcoded channel, the bitrate value that will be stated in the HLS/DASH manifest file for each profile must be calculated. In the case where the video or audio is passed through and not transcoded, ZEN Master does not know the bitrate value and thus cannot calculate the value to include in the manifest. The user will be required to enter a bitrate value. Note that the bitrate values in the manifest are used by playback devices to switch to the appropriate stream rendition based on current network bandwidth so it is important to enter an accurate value. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/UDx57Oqsj4RwRr6noyfTj_image.png" size="70" width="1826" height="990" position="center" showCaption="false"} When both the video and audio are transcoded, ZEN Master calculates the bitrate for the manifest file automatically. The calculation is the video bitrate plus audio bitrate plus a small amount added to account for streaming overhead. MINOR IMPROVEMENTS AND BUG FIXES • More detailed transcoding error reporting including specific error messages instead of a generic "Transcoding Error" • Presentation Time Stamp (PTS) reported on SCTE35 Cue-in events • Verify that the Broadcaster license supports virtual machines when launching on AWS • 32kbs and 64 kbps options now available for transcoding audio bitrate • Added option to select NIC on Feeders and Receivers • Added pagination support for channels, targets and sources in the API • Fixed an issue rewriting ports config on the Broadcaster tunnel connection • Fixed an issue preventing the Add Pull Target dialog from closing without an error • Fixed Pull targets requiring up to one minute to connect when enabling a channel • Fixed issue with unintended outputs being created on the Broadcaster when using Pull targets • Fixed issue with the full warning message not showing in object details in some cases • Fixed missing source DTLS/encryption icon • Fixed issue with deleting remote access devices • Fixed issue with attempting to configure DTLS on v10 Feeders, Broadcasters, and Receivers where DTLS is not supported [title] ZEN MASTER July 2021 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be included in the ZEN Master July 6, 2021 release. Bug Fixes The following issues were resolved: • Fixed issues with “Log on, do not update object state” setting in Event rules • Fixed missing Delete Broadcaster user event message on Broadcaster Clusters • Fixed diagrams containing Broadcaster Clusters with complex names • Fixed incorrect Broadcaster error message for a bad license • Fixed repetitive license error messages for expired/over activations limit licenses on managed Broadcaster Clusters • Acknowledge user events now includes user name/email and a better description of what was acknowledged ## [title] ZEN MASTER October 2020 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates were pushed to ZEN Master on October 8, 2020. Infrastructure Improvements • Moved events database to Elasticsearch to improve events performance Minor Improvements and Bug Fixes • Instance type is now displayed on Broadcaster cluster list for AWS/Azure/GCP clusters • Added filtering by tags in grids display • Added option to reset TR101/CQA and stream info on Source details page • TR101/CQA timestamps will now be displayed in local time • Improved IO server redirection performance to support hundreds of reconnecting Zixi Pull targets in parallel • Added option to disable CMAF (DASH + fMP4 HLS) on adaptive and transcoding Channels • Editing Channel tags will no longer restart the Channel • Fixed Broadcaster authorization warning showing up constantly in the log • Fixed remote access going into pending state on tag changes • Fixed license keys that expire soon showing “expired error”, will now show “expiring soon” • Fixed trace route display error on monitor only Pull targets • Various small UI fixes [title] ZEN MASTER December 2024 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be included in the ZEN Master release for December 10, 2024. Features The following new features were implemented in this release: ### o Akamai Connected Cloud Clusters: o ZEN Master introduces managed cluster support for Akamai Connected Cloud (previously Linode). o Add a Akamai Connected Cloud / Linode account connection under: ▪ Configuration -> Akamai Linode. o Name the connection and apply the Akamai Connected Cloud / Linode API Key: o When creating a new Cluster, under “Management Type”, select the newly created Akamai Connected Cloud / Linode Connection: o Then select the appropriate networking and instance settings per your Akamai Connected Cloud / Linode environment. ### o DPDK support: o AWS Clusters within ZEN Master now include support for very high-performance networking via the Zixi Platform’s implementation of DPDK (Data Plane Development Kit). o When enabled for DPDK, ZEN Master will apply a second NIC to the launched instance. o Select “DPDK Support” in the cluster configuration options to enable. o Provide the pre-configured AWS Subnet and Security group for the additional DPDK Network Interface, ensuring they are available to the instance in the selected region. o Add any optional elastic IP’s if needed. ### o Live Events table update: o ZEN Masters Live Events Manager introduces additional tools to manage multiple parallel events from within the updated main events table. o Rather that mixing all past and future events, “Completed” , “Active”, and “Scheduled” events are now separated to different table listings accessible with the named radio button options: ▪ The “Completed” table lists information for audit and confirming past event runs. ▪ The “Scheduled” list provides info on future events, ideal for programmers and schedulers needing a look-ahead view. ▪ The “Active” list is for Operational Users. It displays Live Events that are taking place now and includes additional new columns for the current state, including the primary output, and status and hover over thumbnails for all component sources and slates. The table view also includes the option to include events scheduled in the immediate future at 30, 60, or 90 minute look-ahead, allowing operators to start multiple upcoming events early when needed. o Additional functionality in the Active list provides Ops Users with the ability to Drop or Go-to-Slate directly within the table row: o Multi-selection of event rows brings up action controls to switch to manual, go to next stage, and end events in parallel: o As an additional safe guard, upon selecting the action, the Operations User is presented with the multi-select confirmation dialog: o This provides an opportunity to confirm the selection group for the action. o It also allows the User to remove an event from the selection list, if necessary. o Once confirmed, select the final action to affect all events in parallel, or the Cancel button. Additional Improvements and Changes The following additional improvements and changes were implemented in this release: o Incidents are now aligned with event profiles. o When alerts are silenced for an object, no incidents will be generated on that object. o Backend performance improvements. o Health Score has been removed from ZEN Master. o Added TSID (transport stream ID) parameter to Transcode sources. o Improved node layout and edge paths in diagrams. o ZEC and Targets Details pages. o Added a new user type to allow users to see the live events scheduler without having account management capabilities. o Account Administrator: ▪ This is the old “Administrator” account type, with all permissions including account management. ▪ Existing Admin Users have been migrated. These accounts can do everything (old Administrator). o Administrator: ▪ New “Administrator” users can do everything except account management, e.g. create users. o Alt/DR Path polish: o Alt/Primary path status is now displayed in tables. o Improved error handling in confirmation dialog. o Confirmation dialog remaining open on logout/session timeout. o Improved default Target Broadcaster values when they must be updated on failover. o Remux/Padding support on SRT Targets. o Dejitter support on UDP/RTP Sources. o SRT push Sources and pull Targets single port support. o Display time of day when creating/editing Live Events stages. o Fullscreen widgets in new details pages. o Synchronize playback is now always enabled on HLS/Local files Sources. o Added External Id column to Channels and Targets. o Live Event switch to manual mode is now logged with timestamp and user info. o Added Source information to SCTE-35 reports. o Exposed HLS Ascending Playlist Order control in Transcoded Channel - Advance parameter section. o ZEN Master Zixi Pull Targets will use seamless switching whenever possible. o Added Transcoder Muxer resets graph to Sources and Channels. o Updated AWS Account documentation to clarify required permissions. o Added option to specify manual bonding on Zixi Push Targets. o Added support for Azure SSO roles/groups. ## Bug Fixes The following issues were resolved: o Issue updating Target Channel. o Fixed occasional DB load issue causing false positive unknown status errors. o Zixi Pull Targets showing incorrect Offline error when pulling monitor only Sources. o Offline Target no longer shows active thumbnail. o Empty values in Targets table export. o False positive "HLS validation: subtitles missing" error: o This error has been reworked to use Alerting Profile rules instead of a special threshold on the target itself. o Target create button in Channel Targets tab now correctly opens creation dialog. o Failover channels with MPTS Sources required manual PID map: o Fix requires Broadcaster v18. o Transcode Channel breaking in some edge cases when updating an upstream Source. o Updating "Automatically switch to Preferred Source" option on Failover Sources/Channels requiring a manual disable/enable to apply. o Updating "Frozen/Blank Video Minimal Duration" parameters on sources requiring a manual disable/enable to apply. o ZEN Master not updating SCTE reporting URL when it looks valid but isn't. o Unable to remove PID mapping profile from file Source. o Public Grids/Grid Groups not working for non-Admin users. o HTTP basic auth popup should no longer show up on session timeout, harmless but annoying. o Event Configuration Profile on Pass-Though Channel updates don't save. o PID Mapping on SRT Targets requiring a manual disable/enable to apply. o Updating "External Id" parameter on UDP/RTP Targets requiring a manual disable/enable to apply. o Duplicate Broadcaster names breaks diagram layout. o ZEN Master leaving ghost Broadcaster VMs in AWS when AWS policy doesn't allow ZM to delete them. o Invalid Parameter error on SSO creation. o ZEC Output filter/search now works in Zixi Target form. o Invalid validation error when creating a MediaConnect Flow with a long name. o Redundant tunnel configuration on Broadcaster applied inconsistently when using redundant IO servers. o SCTE-35 graph not updating when selecting a new source with the graph visible. o Create Incident buttons visible to regular users. o NDI Target issues. o Removing a ZEC output from a Target requiring a manual disable/enable to apply. o "Prefer Primary" Zixi Pull Targets taking minutes to failover to "Backup" source in rare cases: o e.g. when both Sources have errors. API ### Resources Information about the ZEN Master API Reference and Getting Started documents can be found In the Customer Portal: ### Feedback You can now provide feedback related to documentation in the ZEN Master API Reference: • Email: apifeedback\@zixi.com [title] ZEN MASTER January 2025 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be included in the ZEN Master release for January 7, 2025. Features -------- The following new features were implemented in this release: ### o POIS support via ESAM agent o Zixi Broadcaster and ZEN Master introduce support for POIS (Placement Opportunity Information Service) for identifying and managing content placement opportunities within audio and video streams, primarily for advertising purposes. o Zixi Broadcaster provides SCTE-35 replacement features that work in conjunction with the Zixi ESAM Agent. o The Zixi ESAM Agent has been updated to support POIS messaging and the POIS Broadcaster interface. o SCTE-35 replacement commands are logged locally via the ESAM Agent, and also in ZEN Master. Requires a 3rd party POIS Server, Zixi’s ESAM Agent, and Broadcaster v18.0.45862 or later. ### o "Target" thumbnails Grids o Support for Target objects is now added to thumbnail grids: ### o Time zone selection o For teams and environments spanning multiple time zones, ZEN Master provides the ability for users to set a global time zone to assist with coordinating support and incident management. o It can now be set via the time zone picker at the top right of the console. o When changed, all Date/Time data updates to the corresponding time in the selected time zone: ## Additional Improvements and Changes The following additional improvements and changes were implemented in this release: o Separate Audio/PCR overlay controls on thumbnail Grids o Users can now separately choose to display these overlays: o Improved loading times for Channels and Live-Events pages o Diagrams added to ZEC/Feeder/Receiver pages o Support for S3 compatible storage o Source monitoring will now report error concealment and PID mapping errors o Traceroute on Sources is now available from ZEC/client Broadcaster to server Broadcaster o DPDK Improvements o UI Improvements ## Bug Fixes The following issues were resolved: o CIDR pattern validation allowed some invalid values o Repeating Network/IP updated events log messages when ISP has special characters in the name o Repeating TR-101 analysis stopped messages in Broadcaster events log o Error configuring Zixi Push bonded Source o SRT Push Sources will not go into error state until the first connection o Unable to import AWS MediaConnect workflow o Invalid parameters errors on some clone actions o Various ESNI/ESAM/POIS bug fixes API --- The following updates were implemented in the ZEN Master API: ### API Additions o Return 'cloud\_id' with the Broadcaster list & get responses o For Broadcasters managed and launched via ZEN Master, the corresponding internal cloud instance\_id is included in the api responses. [title] ZEN MASTER February 2020 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ ### Minor Improvement and Bug Fixes The following issues were resolved: • Editing transcoded Channel beyond threshold causes all transcoded Channels to stop • Editing a Source to change from a Primary to Backup Broadcaster in the Cluster required Source to be disabled/enable) • Improved load balancing for Cluster Pull Targets • Hitless and transcoded Sources were not preferring primary Broadcasters • Generate shorter SSH user names for Feeders • Automatic pulls of Sources that end in - always fail • Azure VMs were remaining undeleted when deleted in ZEN Master • Events report error when encountering duplicate object names :::Iframe{code=""} ::: [title] ZEN MASTER December 2022 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be included in the ZEN Master December 12, 2022 release. Features The following new features were implemented in this release: • Intelligent Data Platform – Multi-Object Correlation Analysis (IDP MOCA) In this release IDP now automatically detects incidents comprised of multiple objects – Sources, Targets, and Broadcasters – and determines a root cause. IDP uses correlation analysis to determine the common factor in a set of errors across multiple objects that occur within a few minutes of each other to help operators and broadcast engineers see the root cause immediately, and with the most relevant supporting evidence. Key features: • Expanded blast radius – Now you can see all the objects that had an error at the same time and what relates them, even if they span multiple channels, all grouped together in a single incident. • Automated RCA attribution – Incident descriptions now include the common factor across all related errors, which can be the client-side network (of the Sources and Targets), the server-side network (of the Broadcaster), or the Broadcaster. It also shows the most relevant metrics for the incident in the default incident view. • Customizable RCA report – While the default Incident view shows the root cause and most relevant graphs, users can also add other graphs and notes to the report, change the time range, and export the report to share with other team members. Auto install AgentZ By enabling “Install AgentZ Automatically”, ZEN Master will automatically install AgentZ on any existing and future Broadcasters connected to the Cluster. The feature is off by default. Note that due to AgentZ installation requiring a restart, ZEN Master will not auto-install AgentZ on a Broadcaster that already contains any inputs to avoid disturbing active streams. The option to enable is located in the Advanced section of the Cluster: • Pull Targets that are unable to connect now display a more informative message. There are various reasons why a pull Target may not connect to the serving Broadcaster within a Cluster. More specific detail is now provided in the event of a failure, including a distinction where the issue is on DNS redirection, connection to the actual Broadcaster, etc. • Added support for RTMP Targets on MediaLive Channels • Frozen & Blank video detection thresholds can now be controlled and reduced to 10 seconds by default. The detection window sizes for Frozen Video and Blank Video are a Broadcaster input property and configuration is available in the Advanced section of the Zixi Source. • Added support for MediaConnect Entitlement Targets The new Target type can be found under the standard New Target list, and provides the standard parameter fields expected by AWS MediaConnect Entitlements: Additional Improvements and Changes The following additional improvements and changes were implemented in this release: • Added option to propagate ZEN Master Tags to S3/MediaStore on HLS Targets • Added option to clone MediaConnect Flows without transferring the Source to the new Flow - this is now the default behavior • Added Prefer Primary/Backup Source to Zixi Pull Targets • Added option to remove NULLs and SDT in PID Mapping profiles • Added a Preserve RTP headers option on UDP/RPT Sources • Added more max bitrate options to UDP/RTP Sources • Added more detailed alerts on performance related transcoding errors • Improved Target error messages when error is caused by Source Auto-Pull • MediaConnect/MediaLive errors on user actions are now logged in the ZEN Master events log • Email notifications now explain which Role caused the email to be sent to the user • HTTP Targets will now report more detailed error when possible • Zixi Pull Targets now display their current client IP on the details page • Stream info now shows GOP and Frame duration information • Broadcaster restarts are now logged - regardless of reason • Source/Channel failovers are now logged • Source reconnection event log now mentions which Broadcasters are involved in the event • Improved AWS Cluster implementation with better logging and reusing existing ZEN Master Broadcaster ID when an instance is replaced by AWS • Error count labels on the left-hand main menu are now clickable and link to the relevant page with a filter to show the objects that are in an error state • Added option to revert new list tables to default configuration • Auto rows are now back with a vengeance in new list tables + added an upper limit on number of rows • Cluster authentication monitoring is now consistent across all authentication modes • Restart confirmation now uses only backend logic preventing incorrect or missing restart prompts on edit • MediaConnect/MediaLive monitoring now scales to any number of Flows/Channels • UI Polish API • Using invalid IDs in API calls will now return an error with a 404 HTTP code Bug Fixes The following issues were resolved: • Event log report now contains all expected results • Fixed incorrect MediaConnect SRT Target status on dashboard • Fixed issue causing Zixi Pull Targets to get stuck on an offline Source when a working one is available in some scenarios • Fixed rare issue causing ZEN Master to report an offline error on Zixi Pull Targets when they are working • Failover Sources should now recover on all component Source changes/reconnections • HTTP Targets no longer allow deleting chunks in DVR mode • Fixed Automation tasks getting stuck in executing state • Non-Admin users can now switch Channels • Fixed issue causing Channels to save in a broken state when changing the Channels Cluster without manually updating the Target Broadcaster field • Creating an Incident from the event log will now have a more reasonable default start/end time • Fixed updating Adaptive channel component Sources not propagating to Broadcaster • Fixed Kafka test showing generic error message with no details • Auto-Pulls are no longer created when disabled or not needed • Updated Failover Rules UI to be more understandable • Clarified DTLS note on Clusters form • Fixed multiple issues with Targets on Grids - e.g. missing name/link to details page • Fixed WebRTC playback on Sources with multiple audios • Fixed multi-edit of Target tags hanging forever in some cases • Fixed spin up of Broadcaster on Azure Broadcaster failing displaying a generic error while the VM is successfully created • Correct smoothing configuration now applied to transcoded Source in CBR mode • Daylight Savings Time will no longer cause Automation tasks to run an hour early/late • Fixed an issue causing some SCTE-35 messages to not get logged [title] ZEN MASTER May 2021 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates are included in the ZEN Master May 6, 2021 release. Improvements • Added support for RTMP Push and Pull Sources • Reduced and added user controllable thumbnail refresh time on Grids thumbnails • Updated WebRTC preview player to fill entire browser window • Added option to disable/enable dynamic child targets • Added ability to see IDP Healthscore on Maps • Added Transcoding profiles and PID Mapping profiles endpoints to public API • General UI polish Bug Fixes • Fixed issue with events not filtering by tags and only matching on beginning or object name/event message • Fixed missing trace routes and trace route history • Fixed issue with cluster monitoring when a deleted AWS Broadcaster was in the list • Fixed issue with Content Analysis graph when zooming • Fixed missing ‘Play with VLC’ button on Sources • Corrected error message when enabling MediaConnect Sources • Fixed broken muting functionality • Fixed incorrect latency value display on child Targets • Fixed invalid params error when cloning Zixi Pull Targets with type Other • Fixed HLS Ad markers not being logged on adaptive Channels • Fixed issue with alerts not being sent to some users • Fixed GET Tag by id public API call returning all tags • Fixed public API issues related to returning Broadcaster list, Source creation, and deleting Broadcasters on GCP [title] ZEN MASTER March 2020 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates were pushed to ZEN Master on March 27, 2020. Improvements ZEN Master and the VLC Plugin for Zixi have been updated for low latency Source preview and the ability to select public or private IP’s. ### Low Latency Stream Preview When you click View Source in ZEN Master, the previous behavior was to download a .vlc file that when opened would launch VLC with the necessary parameters to view the Zixi stream. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/xUz0mI36rmmIUEXxh-QOm_image.png" size="70" width="1478" height="940" position="center" showCaption="false"} One of those parameters was a latency setting for the Zixi protocol and it was defaulted to 4 seconds. This provides very good resiliency for any network conditions but in some cases previewing sources as close to real-time as possible is preferable. ZEN Master has been updated to allow the user to choose between the previous high resilience mode and a low latency mode. For the low latency mode, the Zixi latency is set to 150ms. VLC itself requires about 300ms to 400ms for decode so the Zixi latency plus VLC decode will be about 500ms. With these changes, now when you click on the VLC play button shown above you will be taken to a Source preview landing page that allows you to choose between “Low Latency” and “High Resilience”, if the option is available on your platform. This setting is currently available for Windows and Mac. Note: The VLC plugin version needs to be 13.1.38157 or later to make use of this feature. Download links are available on the landing page. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/JKzlvQomzJOWcLqVv3xmn_image.png" size="80" width="1998" height="822" position="center" showCaption="false"} The Zixi VLC integration is not available on mobile so you will not see the buttons there. You may also see buttons to choose between “Public” and “Private” networks; this option will be described later. After selecting “Low Latency” or “High Resilience”, click the “Play” button. On Windows, a zixi:// URL will be opened which will cause the browser to display the following confirmation dialog: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/5-zioQ1HTz9aP3Vjvt_PJ_image.png" size="48" width="960" height="366" position="center" showCaption="false"} Click on “Open VLC media player” to view the stream in VLC. On some browsers you can “remember” this setting so that you do not need to click on this dialog each time. Your button selections on the landing page are saved in the browser and will be remembered from session to session in that browser. Also, you only need to click the “Play” button on the landing page the first time you view the page. After the settings have been remembered, the next time you preview Sources the browser will go to the landing page and start the playback sequence, which may or may not cause the confirmation dialog to appear depending on your browser. Of course, you can always close VLC and change settings on the landing page and then click play again. Note: Unlike before, you can now share the link for the landing page with other ZEN Master users if you want to easily share the source you are viewing with them. If they are already logged into ZEN Master the landing page will open on their browser and they can click Play. If they are not logged in, they will be taken to the ZEN Master login page first and then to the source preview landing page after logging in. ### Public vs Private IP Selection In some situations, Zixi Broadcasters are hosted on private networks and the preview of Sources in ZEN Master needs to remain on the private network, either inside the same facilities or remotely via VPN back to the facilities where the Broadcasters are hosted.. The “Public” vs “Private” network buttons on the landing page described above allow the user to choose. In ZEN Master, for a Broadcaster to have both a public and private IP address it needs to be a manually configured Broadcaster that has been linked to ZEN Master. Broadcasters spun up on AWS, GCP, or Azure through ZEN Master cannot have separate public and private IP addresses. To configure separate public and private IP addresses, edit the Broadcaster inside its Broadcaster cluster: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Vp5KN60nEyBEAjT4lfRFh_image.png" size="90" width="2002" height="490" position="center" showCaption="false"} Go to the advanced setting page ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/GfjOwaWK3Fbh1rtwTZ5f0_image.png" size="82" width="1716" height="888" position="center" showCaption="false"} Set the “Streaming IP” to the public IP address of the Broadcaster and the “Private IP” to the private IP address of the Broadcaster. Now when you select “Public” on the Source preview landing page, you will see the public address in the VLC zixi:// URL. When you select “Private” on the Source preview landing page, you will see the private address in the VLC zixi:// URL. Note that VPN servers typically have much less total throughput capability than an organization’s connection to the public internet. As such, multiple users viewing video through the VPN can overwhelm the VPN server. [title] Release Notes: Zixi Broadcaster Version 18 [path] Zixi Product Updates/Zixi Broadcaster Release Notes/ ## v18.12.46759) (19 April 2026) This release provides bug fixes only. ## v18.9.46557 (5 January 2026) ### *Improvements* - Improved seamless switch on input when I-Slice header is located up to 7 TS packets from its PES header ## v18.8.46391 (21 Oct 2025) ### *Improvements* - Added ability in transcoding to preserve screen resolution, but change the display aspect ratio (DAR) from 4:3 to 16:9 by applying scaler filter when encode width or profile width differ from source width - Added ability to specify custom position of WebVTT captions ## v18.7.46333 (4 Sept 2025) ### *Improvements* - Improved bonding to minimize use of links with low capacity - Reduced memory consumption in all types of failover groups, improved performance when there are many no-merge groups, and added memory usage, 'overflow' and 'outof-memory' statistics in no-merge-failover groups - Added support for non-alphanumeric characters in input name in SCTE reports sent to ZEN Master - Added graceful handling of RTP 2022-7 merge when RTP timestamps on a stream does not advance ## v18.6.46249 (28 July 2025) ### *Improvements* - Improved overlay blend performance on HTML5 overlay - Improved source switching on no-merge failover group to now detect an exit point (I or P frame on the source stream) before switching to the new stream - Improved memory allocation and performance in the TR-101 analyzer ## v18.5.46206 (8 July 2025) ### *Improvements* - Added additional stream stats, such as CC errors within a segment, on HLS inputs on input\_stream\_stats.json API endpoint ## v18.3.46065 (24 April 2025) ### *Improvements* - Added feature for including web audio in the HTML overlay during transcoding - Updated No Merge failover mode to use 'search window' parameter for inactivity detection, instead of 200m fixed time - Updated CPU detection for Graviton to be “Graviton2” or “Graviton3” instead of “Neoverse” - Added support for billing codes on transcoded sources, bytes going to the transcoder are counted - Added support for keeping RTP headers in SRT output when SRT input contains RTP headers - Added support for chroma sub sampling up conversion for software transcoding, including with HTML overlay ## v18.2.45997 (13 March 2025) ### *Improvements* - Added feature for including web audio in the HTML overlay during transcoding - Added feature to convert HLS inputs into a valid MPEG-TS which meets CBR and PAT/PMT repetition requirements - Added support PID mapped and/or error concealment on transcoded sources - Added support for seamless switching on audio only streams. The switch will occur on the first audio frame detected and is supported on AAC, AAC LATM, AC3, EAC3, Opus, MPGA1, MPGA2 and AES3. - Added support for seamless stream switch on RTP/UDP push outputs - Updated UI message about license expiration to appear two weeks before the expiration date - Added display of SDT and NIT table in TR-101 analyzer - Added support for bind to local port for SRT push output and SRT pull input - Updated jitter alert on RTP/UDP sources to turn off after 5 seconds - Added support for SRT inputs on the same port from different hosts with unique remote stream names - Added support for Time and Date Table (TDT) / Time Offset Table (TOT) in DVB transport stream on PID 0x14 in TR-101 analyzer - Improved performance of HTML overlay when using software transcoding - Added ability to disable metadata injection from UI for non-transport streams, such as ATSC 3.0 STLTP (Studio to Transmitter Link) streams - Added option to delay stream by one segment for HLS inputs in order to inject SCTE-35 packet in advance. Enabled via checkbox in the UI. - Updated SCTE-35 report to calculate wall clock time = SCTE-35 PTS – SCTE-35 packet PCR - Updated failover groups to reattempt a source previously considered faulty if there are no alternatives - Improved upload performance to S3 using AWS recommended settings - Added support billing codes for transcoded sources - Updated SRT library to v1.5.4 - Added support for capturing SCTE-35 MPU Format Identifier on HLS inputs - Added ability to dejitter RIST sources either by arrival times (default) or by RTP timestamps, as is done on RTP inputs - Added checkbox to keep RTP headers in input streams over a Unix socket. On output streams over a Unix socket, added checkbox to keep RTP headers and a checkbox to add new RTP headers to the stream. ## v18.0 (30 Dec 2024) ### Upstream Protocol Metadata The Zixi Broadcaster now saves stream health statistics on Zixi input streams as metadata stored in the transport stream. When a stream is sent through multiple Zixi Broadcasters, health statistics from each stage in the transport chain will be saved and if packet loss has occurred or CC errors have been introduced, it can be tracked down to a specific stage of the transport. The saved metadata can be viewed by hovering on the status light on inputs in the Input tab in the UI. ### Bitrate Reduction on Congested Network Links The Zixi Broadcaster and Zixi Edge Compute can now reduce stream bitrate on Zixi protocol Push and Pull outputs when the network link is congested without transcoding. It reduces the bitrate by selectively removing P-frames and B-frames while keeping the audio and metadata in sync with the video. Settings to enable this feature, called “Stream Thinner”, are on Push and Pull Output dialogs in the UI when advanced mode is enabled. For automatic Pull Outputs there is a global config as well. The Stream Thinner latency setting should be set to the GOP of the stream. ### Irdeto Digital Rights Management (DRM) Integration The Zixi Broadcaster and Zixi Edge Compute can now retrieve an encryption key from Irdeto DRM servers and encrypt adaptive HLS streams using that encryption key. This capability allows customers to use business rules enabled by Irdeto to allow or block playback of encrypted streams. Settings for this feature including credentials for Irdeto servers can be found on the Adaptive live stream dialog in the UI when advanced mode is enabled. Both Fairplay and Widevine are supported. ### Video Preview Using MPEG TS Over HTTP The Zixi Broadcaster has a new option for video preview which plays MPEG TS streams directly in the browser via an HTTP connection from the Broadcaster. With this feature, VLC is no longer required for video preview. However, not all codecs are supported by browsers so the VLC option is still available for maximum flexibility. Note, automatic HTTP pull outputs need to be enabled in the Broadcaster configuration to use this feature. ### NETINT Transcoding Accelerator Support The Zixi Broadcaster now supports accelerated transcoding using NETINT Quadra VPU accelerator cards. The price vs performance vs quality of the NETINT Quadra VPU offers advantages over GPU and CPU based transcoding. This feature is currently in preview while we www\.zixi.comwork closely with NETINT to optimize performance. NETINT Quadra cards can be purchased for bare metal servers and will also be available on Akamai Connected Cloud in early 2025. ### SCTE-35 Replacement Via POIS To support Placement Opportunity Information System (POIS) SCTE-35 replacement methodologies, the Zixi Broadcaster can now remove all existing SCTE-35 messages on an input stream while maintaining the existing SCTE-35 PID and then inject new SCTE-35 messages on the existing PID or a new custom PID. The feature works in conjunction with an ESAM agent provided by Zixi and 3rd party POIS servers. ### Protocol Updates Listed below are improvements and bug fixes to the various protocols supported by the Zixi Broadcaster. - Zixi - Implemented performance optimizations for Zixi protocol - HLS - Updated behavior of injecting SCTE-35 on CUE tags in HLS inputs. Now injects SCTE-35 message in advance, pointing to the PTS of the first video frame following the tag, instead of immediate injection at the time of transition. - Updated behavior on HLS inputs to increment splice\_event\_id when converting CUE points to SCTE-35 messages - SRT - Updated SRT implementation to allow multiple SRT outputs to share the sameport by using the stream name to uniquely identify them ### Transcoding Updates Improvements to transcoding in the Zixi Broadcaster are listed below. - Added ability to recognize and show NVIDIA Ada cards on the status page in the GUI - Added support for NETINT as discussed above - Added ability for user to select the transport stream ID (TSID) on an input being transcoded - Added display of transcoded sources in red if the original source is encrypted and not able to be decoded. TR-101 analysis must be enabled. - Added support for transcode of audio only sources - Implemented performance optimization in transcoder ### Additional Improvements - Added failover group events to logs - Exposed DAR and Display resolution in the TR-101 analyzer - Exposed inter-packet gaps maximum, average and standard deviation on UDP outputs, instead of timing histogram - Added ability to synchronize the timeline of file/HTTP sources by specifying ISO time to use for PTS at beginning of the file - Added count of 608 and 708 closed captions to input stream statistics. Data can be used to determine whether or not input streams contain 608 captions and/or contain 708 captions, as may be required by law. Currently the data is only available via the API. - Added ability to delay inputs in memory by up to three seconds - Added 'steal time' into reported CPU usage - Added support for delivering payloads of up to 1486 bytes, which may be necessary for payloads such as ATSC 3.0 - Implemented performance and memory optimizations in TR-101 analyzer [title] Zixi Broadcaster Release Notes [path] Zixi Product Updates/ - [Release Notes: Zixi Broadcaster Version 19](docId:4cz3kXeYhAd1_2ydw8j9n) - [Release Notes: Zixi Broadcaster Version 18](docId\:RadURZyqziy7DJ_BnSPqQ) - [Release Notes: Zixi Broadcaster Version 17](docId\:IHwLuSOxOiGEgAe2eYemP) - [Release Notes: Zixi Broadcaster Version 16](docId:2uqr_NqlWVDOrvkqr5Ca1) [title] Errors and Troubleshooting [path] / ## General Troubleshooting - [General Troubleshooting](docId:8G3vceiKZJsnPYLU1rQSH) ## ZEN Master - [ZEN Master - Errors and Troubleshooting](docId\:CYHMfI_-M9ldX5aSfojSN) ## Zixi Broadcaster - [Broadcaster - Errors and Troubleshooting](docId\:HUi-CQDzF218zY6PB1o9W) [title] ZEN MASTER July 2019 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be pushed to ZEN Master on July 9, 2019. RUNNING ZIXI BROADCASTERS ON GOOGLE CLOUD PLATFORM ZEN Master now supports Broadcaster clusters on Google Cloud Platform (GCP). Follow the steps below to configure ZEN Master to use GCP and launch Broadcasters on GCP. Login to your GCP service accounts console at https\://console.cloud.google.com/iam- admin/serviceaccounts and select your project and click 'Create Service Account'. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/EORzHRtyCQzkd6Rp2M4v__image.png) Name the account, e.g. 'ZEN Master' and click 'Create'. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/gaHAJtpZiuS5SCxmyY_Ce_image.png" size="82" width="1458" height="1054" position="center" showCaption="false"} ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/RivxebX2I9trjkTcYqzxb_image.png" size="82" width="1490" height="1206" position="center" showCaption="false"} Click 'Create Key' select the 'JSON' type and click 'Create' ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/nmGrVVIbPbI4n_KWom0n__image.png) ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/pvY_zMtHsMRYQztEniZgC_image.png" size="52" width="1228" height="838" position="center" showCaption="false"} Save the downloaded file and click 'Close'. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/2MPt3wwrZr-9ZeoglqZqU_image.png" size="78" width="1752" height="494" position="center" showCaption="false"} ::Image[Next, configure ZEN Master to use the GCP service account. Open the GCP configuration page under the Settings menu and click 'Add Account'.]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Z4evXhxbNhTCrmzPRPtVH_image.png" size="46" width="968" height="606" position="center" showCaption="false"} ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/usvkCc-zVOwUy1HudCD8i_image.png" size="82" width="1700" height="416" position="center" showCaption="false"} Name the account and upload the JSON file downloaded from GCP. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/3mUkoNNigyLL83XWlllfT_image.png" size="60" width="1298" height="638" position="center" showCaption="false"} Click 'Save' to confirm. To launch Broadcasters on GCP in ZEN Master, add a new Broadcaster Cluster and select the GCP scaling account that you just added. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/YH9YHfWqJezAi-lyGM-j7_image.png" size="86" width="1908" height="882" position="center" showCaption="false"} After clicking ‘Continue’, select the Region, Zones, Network and Machine Type. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/cdbF5uyRqiNrfjMf36HKW_image.png" size="72" width="1278" height="1132" position="center" showCaption="false"} If you will be using the Broadcaster for transcoding, also select the GPU type: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/rbK-TDFaE9BsAIJAXDms5_image.png" size="72" width="1284" height="284" position="center" showCaption="false"} Capabilities of the Tesla K80 and P100 can be found at https\://developer.nvidia.com/video-encode- decode-gpu-support-matrix. After completing the other required fields, you will now be able to launch Broadcasters on GCP. USING AZURE BLOB STORAGE FOR HLS AND DASH ZEN Master now supports storing HLS and DASH manifests and segments on Azure Blob storage, to be used as an origin for CDN delivery. Follow the steps below to configure ZEN Master to use Azure Blob storage. If you have not already linked an Azure subscription to ZEN Master, follow the detailed steps shown under on the Microsoft Azure page under Settings. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/fQA_Riki45OexhplvISQR_image.png" size="58" width="966" height="598" position="center" showCaption="false"} If you already have a linked Azure subscription or after linking the Azure subscription, you simply need to add a new role assignment for Azure Blob storage. Open Access control (IAM) under your Azure subscription, select the ‘Role assignments’ tab, and select ‘Add role assignment’. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/S8WTXLU_XKoNbMoFReWtO_image.png" size="76" width="1888" height="914" position="center" showCaption="false"} Select ‘Storage Blob Data Contributor’ and then select the same service principal that you created when you originally linked ZEN Master to the Azure subscription. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/s8nUTGorHN4RZrOC51HOO_image.png" size="44" width="950" height="1614" position="center" showCaption="false"} Click ‘Save’ and you will see that service principal under ‘STORAGE BLOB DATA CONTRIBUTOR’. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/2CP3UIwcfFTStUe6DO2Zu_image.png" size="84" width="1762" height="222" position="center" showCaption="false"} Next, when you create an HTTP target you can select Azure that the type and select the appropriate Azure account linked to ZEN Master. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/zPSa8WxktNxieJbBzMG6z_image.png" size="68" width="1300" height="1720" position="center" showCaption="false"} RTT AND JITTER HISTORY ON TARGETS Round trip time (RTT) and jitter is now available on the Network graph in the History tab for Targets. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/WW9r9HZ0AQnl04EI5dbJQ_image.png" size="84" width="1854" height="718" position="center" showCaption="false"} MINOR IMPROVEMENTS AND BUG FIXES • Improved error message when a Broadcaster configured with ZEN Master authorization that is not working properly. Previously displayed “Authorization” error in a Broadcaster status; will now report the exact error. • Transcode profiles can now be cloned. • Advanced transcode profile settings are now displayed details tab. • Traceroutes history is now off by default and needs to be manually enabled in Source/Targets advanced settings. • Added type to Sources table and filter buttons by Type. • Improved AWS Scaling Broadcaster Names. AWS broadcaster now follow the same naming convention as GCP/Azure \{cluster name}-\{unique id}. • Support floating-point HLS/DASH segment duration configurations - both as cluster default and per adaptive Channel. • Fixed version error message when transcoding license is missing. • Fixed issue where import Key does not have the key field as mandatory. • Fixed invalid FEC Row and Col error message. • Fixed issue with usage reports total not matching details. • Fixed issue with usage report not matching actual usage. • Fixed issue with graphs and traceroute menu refreshing periodically for no reason. • Fixed issue where it was impossible to delete a user that had custom notifications configured. • Fixed issue where View-Only user does not show Feeder/Broadcaster logo on source. • Fixed issue where View-Only user does not display all components in Channel view. • Now ignore unaligned PTS errors on transcoded channels as they are not relevant. • Fixed error when adding Receiver with same named outputs. [title] ZEN MASTER September 2020 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates were pushed to ZEN Master on September 8, 2020. WebRTC ZEN Master now supports using WebRTC to monitor streams with very low latency. With WebRTC you can monitor your streams using modern browsers and mobile devices without installing any external plugins such as the Zixi VLC plugin. WebRTC monitoring is enabled on Sources. The online documentation describes the various settings for WebRTC. Once a Source has WebRTC enabled, a WebRTC play button will be available on the Source details page. Upon playing a WebRTC source, a new browser tab will be opened with the WebRTC player. Minor Improvements and Bug Fixes • Added 'ignore DTLS certificate' option to Zixi push targets • Added TR-101 Performance "missed frames" to history graphs • Added 'Expand Table' button to all log tables for mobile/narrow screen support • Added Created At field for generated report run history • Improved SCTE related error messages • Improved error message when launching instances on Azure with invalid configs • Removed incorrect front-end auth requirement on access keys API calls • Fixed issue with hitless Source edit requiring manual enable/disable to apply config • Fixed issue with Targets filter not working in some cases • Fixed issue with automatic generation of DNS name field on Broadcaster Cluster form • Fixed issue where unable to enable Target because of disabled auto-pull • Fixed issue with MediaConnect Sources in Channel diagrams showing wrong status • Fixed issue with Source showing warning/error messages when disabled • Fixed issue displaying incorrect RTMP error message on Adaptive channel • Fixed issue with transcoding usage in usage reports always showing 0 minutes/bytes • Fixed issue where editing a bonded Zixi Source required a restart even when no changes were made • Fixed user name/email missing from user login events when using SSO • Fixed PID Mapping Sources Stuck In Pending State when on a different cluster than the original source • Fixed SRT Source issues when switching between Pull and Push modes [title] ZEN MASTER September 2024 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be included in the ZEN Master September 3rd, 2024 release. Features The following new features were implemented in this release: ### o ESNI/SCTE-224 o ZEN Master introduces relevant support for scheduling and program substitution switching via the SCTE-224 standard, also known as ESNI (Event Scheduling Notification Interface). o Based on the policy schedule, ZEN Master will switch Targets to an alternate Channel for alternate content or blackout. o ZEN Master provides a new API for scheduling Media, Policy, ViewingPolicy, and Audience. o Program substitution is initiated via both MatchTime and MatchSignal. o ESNI Server capability is available upon request. ### o ESAM o Zixi ESAM Agent provides support for program substitution and alternate content switching via solicited or unsolicited messages using the Cablelabs ESAM standard. o ZEN Master introduces logging of content switching via the ESAM Agent. o This feature requires: ▪ An external or 3rd part ESAM server. ▪ Installation and configuring of the Zixi ESAM Agent. ▪ The Agent to run locally alongside version 17.5 or greater of Zixi Broadcaster. ▪ An API key for communication between the ESAM Agent and ZEN Master. o Ask your technical representative for more information. ### Alternate Path Redundancy o ZEN Master now provides Alternate Path configuration failover for disaster recovery, maintenance windows, multi-cloud environments etc. o Alternate Paths are configured at the Cluster or Channel configuration: o Objects applied or attached to such configurations provide the capability to switch to the alternate. o When asked to switch, they will seek this information from the configuration, and re-attach to the alternate path, whilst maintaining a log of the original path and current state, for later revert. o For example: ▪ Channel (A) is applied to a Cluster in an Azure West region. ▪ A mirrored Channel (B) is configured to a cluster in GCP Central. ▪ All Delivery Targets are attached to Channel (A). ▪ In a disaster scenario, the Azure Cluster is lost. ▪ Individual, or multi selected targets can be instructed to ‘Go to Alternate’ . ▪ This information is acquired from the Channel Alternate Path setting and targets are immediately switched to the GCP Channel (B). o When Multi-Selecting Objects for Alternative Path Switching: o Users may select Objects with differing origin or destination switch configurations. o A new confirmation dialogue is introduced that provides users with both final confirmation of the switches that will take place and tools to make final alterations or remove objects from the switch. o Once final, selecting ‘Confirm’ will enact the switches, which are logged in the various corresponding Object Event Logs. ### o Grid Groups with Custom Layout o Custom Grids Groups now allow Users to define and position Multi-Grid Layouts o Once each Public or Private Grid is defined, they can be added to a Customer Grid b choosing the ‘Custom Layout’ Option. o Once the Grid Group is selected, the edit controls can be unlocked: o Users can then drag individual Grids and their size controls to position, size, and layout the Grids appropriately for the corresponding workflow. o Save and Lock the Grid to keep changes or Revert to the default. ### Error Concealment for Failover Sources and Channels o Zixi Broadcaster Error Concealment parameters are now supported via ZEN Master failover channels in the Error Concealment configuration section: ### Updated Channel Diagrams o A newly updated Channel diagrams offer improved details and introduces additional functionality such as: ▪ Thumbnail Display. ▪ Animated lines distinguishing active/in-active links. ### o Added CBR Transcoding to ZM o Zixi Broadcaster CBR Transcoding mode is now available in ZEN Master via the Transcode Profile settings: ### o A Source’s SCTE-35 event log now integrates the event timeline graph o In addition, a drag-zoom of the graph will filter the events list accordingly. ## Additional Improvements and Changes The following additional improvements and changes were implemented in this release: o Channel details page updated to new ZEN Master Objects Details Page style. o MediaConnect Source page updated to new ZEN Master Objects Details Page style. o Updated pages now include the customizable widget layout: o Failover locking will use seamless failover method when available. o Requires version Zixi Broadcaster Version 18+. o Requires all Sources to be present on the same Broadcaster. o Updated Source and Channel tables to consistently show active Broadcaster. o PID Mapping is now supported for File Sources. o Added an option to turn off TR-101 analysis completely on Sources. o Added missing/new Broadcaster options to ZM. o PCR Interval Setting to De-Mux Sources. o Drop Inactive Streams option to Multiplex Sources. o Drop First Segment and Segment on SCTE-35 to Adaptive Channels. o Bit Depth and High 10 Encoding profile to Transcoding Profiles. o Transcoding Profile resolution settings now have the same options as the Broadcaster. o Transcode aspect ratio. o Added UDP Errors graphs to Broadcaster insights. o Added support for more AWS (Amazon Web Services) instance types. o Added Billing Code column option for tables where relevant. o Change Tracking on Transcoding and PID Mapping profiles. o Improved incident prediction. o Reporting and more info in details added to user management pages. o UI Polish. ## Bug Fixes The following issues were resolved: o Fixed Inter-Cluster sources incorrectly pulling Failover with Error Concealment. o Failover Channel names no longer must be globally unique. o Add Event Profile screen is no longer a blank page. o Fixed ZEN Master not tracking Target failover between Broadcasters. o Fixed AgentZ not working with Broadcasters that use HTTPS API. o Fixed miss-reporting of AgentZ and SSH tunnel credentials issues. o Fixed missing failover events on Failover Channels. o Fixed ZEN Master creating invalid Broadcaster SSH tunnel configurations when using customer uploaded SSH keys. o Fixed Missing Lock/Unlock events on Failover Sources and Channels. o Fixed API doc export. o Fixed Users with read-only permissions on Broadcaster able to access the tunnel in some cases. o Fixed Live Events Force Slate stopping working after certain Live Event edits. o Fixed Live Events table empty when there are scheduled Events in some cases, triggered by editing a Live Event's stages. o Fixed Target PID Mapping changes not applying on existing Targets in some cases. o Fixed error creating Failover Source/Channel with silent audio rule using auto-pulls. o Fixed Zixi Pull Targets missing from Maps. o Fixed an issue with correctly applying Inter-Cluster latency configuration. o Fixed validation error on Target clone. o Fixed Inter-Cluster Sources inconsistently not created on BX after disable/enable. o Added some missing events to Kafka export. o Fixed an issue with the TAG Multiview integration layout not matching configuration. o Added an option to disable thumbnails on Sources. o Fixed ‘Missing Region’ error when generating a report. API The following updates were implemented in the ZEN Master API: o Added SCTE35 insertion via API. o Added ‘failover\_channel\_id’ parameter to Targets. o Adaptive Channel POST and PUT now take an optional ‘transcoded\_source\_id’ that overrides the ‘source\_id’ in bitrates. [title] ZEN Master 7 Apr 2026 Release [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be included in the ZEN Master release for **April 07th, 2026**. ## Features The following new features were implemented in this release: ### Live Events Timeline View This update introduces the timeline view for Live Events. The view allows operators and control room managers to see a look-ahead of upcoming events. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/861iqNeuWMO0BzrVMvkV3_image.png) - When toggled to the timeline view, events are visualized in a linear timeline, each row showing an event broken into its chronological stages. - Events are stacked on the left. - The arrow will take the user to the start of events that are offscreen. - Stages will begin at their corresponding time. - The hover over will show further details and, if available, a thumbnail of active stages. ### SCTE-35 Modification Agent Install from ZEN Master :::hint{type="info"} **Note:** This feature is a module addition. Please speak to your account rep for more information. ::: ZEN Master adds the ability to install a SCTE-35 Modification Agent directly from ZEN Master. ![Install SCTE Modification Agent](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/iTdRCABGc-1UECJ7ipDS0_image.png) ## Improvements and Changes The following additional improvements and changes were implemented in this release: ### SCTE-35 Modification Enhancements The following features collectively expand ZEN Master's SCTE-35 capabilities: - Added an option to convert triggering messages to TimeSignal (type 6) messages with descriptors. - Added an option to set PTS based on the triggering SCTE-35 PCR. - Added the ability to create time-delayed messages — for example, to convert and auto-return a return signal. - Removed the irrelevant "Remove Existing SCTE-35" option from the Target SCTE-35 Manipulation section. ### Error/Alert History Banners Warning and error alert banners now display the last 2 hours of history for each alert. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/OyYlscCZlxCvO085sgr8K_image.png) ### Failover Channels Deprecation - Failover Channels are now hidden. - Failover Sources are updated to support migrating existing Failover Channel users. - Tech leads will work with customers to ensure a seamless experience. ### HEVC Software Transcoding - Added support for HEVC/UHD software transcoding using the x265 library. - Software Transcoding is applied if the instance has no NVidia hardware, or the user selected software in sources or channels. ![Transcode Profile Options](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/leDEgJIUPNmNVYo9vLiY-_image.png) ### Retain Elastic IP on EC2 Restart Where possible, ZEN Master will now retain the Elastic IP (EIP) assigned to an EC2 instance after it has been terminated and spun back up. ### Show Active Source Name on Target Thumbnail Grid The currently connected ZEN Master Source name is now displayed on the Target thumbnail grid. ### Disable Source on Live Events with Failover Sources Added the ability to disable a Source on Live Events that use Failover Sources. ### Streamlined Filters UI - Improved filters UI on pages such as Live Events and Events/SCTE-35 logs. - Streamlined filters and cleaner UI. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/99bnZX2SojstQUVZ-iocu_image.png) ### S3 Output for AWS SSM Run Command - Added an S3 output option to the AWS SSM Run Command feature. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/7MFlhFAV_LbVxY2WbrXeM_image.png) - AWS SSM Commands can already be launched from the ZEN Master UI, and the output tail end is displayed to the ZEN Master UI. - As of this release, a bucket can be provided as a target to write the entire output for historical details or further investigation if an issue occurs. ### HLS Source – Remux & Target Bitrate Settings Added support for Platform capability to Remux HLS to MPEG-TS and Target Bitrate settings to HLS Sources. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ql0FoO9-WWGTq0sdZS3jU_image.png) ### Add Event Profile Change to Events Log & Kafka Event Profile Changes are now tracked in the Events Log and published to Kafka. ### AWS Amazon Linux 2023 AMI - ZEN Master now uses the latest AWS Amazon Linux 2023 AMI for non-Nvidia EC2 instances. - ZEN Master will launch or replace standard instances using the latest valid AWS Linux version. - New or replacement Nvidia instances continue to use the internally managed AMI. ## ESNI & ESAM The following updates were implemented for ESNI and ESAM: ### ESNI ESNI Metadata Options for Schedule View Added the option to use metadata info for schedule simulation and custom descriptions in the ESNI schedule view and mediapoints table. ESNI Switching Performance Improvement ESNI switching now performs a single Broadcaster scan per external ID instead of per Target, making switching a large number of Targets significantly faster. ESNI UI Enhancements Improved clarity of hover popups and added more detail in ESNI UI popups. ### ESAM ESAM Agent POIS Mode – UtcPoint Support Added UtcPoint support to the ESAM agent POIS mode. ## API Additions and Changes ZEN Master API documentation updates for the following sections. **Technical Reference:** For detailed field change technical reference, see the accompanying document: ZEN-Master-API-Updates-Reference-2026-04-updated0331.csv.zip — found in the Zixi Customer Portal. ### New API Endpoints **Clusters, Broadcasters** Created a new Terraform Cluster management type and related API endpoints. These endpoints will be used by cloud service deployments when using Terraform. - POST /clusters/terraform/\{clusterId}/broadcasters *(new)* - GET /broadcasters/\{broadcasterId}/access\_key *(new)* - GET /broadcasters/\{broadcasterId}/config *(new)* - GET /broadcasters/\{broadcasterId}/installer *(new)* - GET /broadcasters/\{broadcasterId}/license *(new)* ### API Field Additions/Updates **Access Keys** - Added rsa\_private for GET responses. - Exposed SSH tunnel private key for automation support (ZM-generated keys only). **Broadcaster, Feeder, Receiver, Remote Access, ZEC** - Added tunnel\_hostname for GET responses). **Live Events** - Renamed disable\_channel\_after\_done to disable\_after\_done . - For backwards compatibility, disable\_channel\_after\_done still exists. **Sources HLS** - Added remux\_hls - Target bitrate is only relevant if remux\_hls is enabled. **Targets** - Removed scte35\_remove\_existing. No longer needed for SCTE-35 manipulation. - Applies to: RIST, RTMP, SRT, UDP/RTP, Zixi Pull/Push. ### New API Functionality **Global** - Normalized filters and pagination on all API List endpoints. Functionality was previously released; QA finished in this sprint. **API Keys** - Fixed PUTs returning 200 OK when API key has read-only permissions on object. Create, Update, Delete will now return 403 Forbidden. **Channels, Sources** - Added x265 option to encoder selection. Supported for Transcoded Channels and Sources. **Failover Sources** - Fixed an API validation issue that could allow a user to inadvertently break a Failover Source/Channel configuration. **Sources** - Source stream\_id is now a configurable parameter when creating a Source. ### API Documentation Updates and Changes **Clusters (AWS)** - Set ami\_id as optional. It should not be specified unless the user is providing their own AMI. **Channels (Failover)** - Added a note that Failover Channels are deprecated. Instead, create a Failover Source and Pass-Through Channel. **Targets** - Added termination\_protection. - Applies to: HTTP, RIST, RTMP, SRT, UDP/RTP, Zixi Pull/Push. [title] ZEN MASTER June 2021 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be included in the ZEN Master June 16, 2021 release. Improvements This release of ZEN Master delivers a major rework of the event notification system in ZEN Master. With this release you can configure every alert that ZEN Master can generate including the rules that govern when an event is classified as a warning or an error based on user defined escalation and de-escalation thresholds, where applicable. Management of the new event notification system is under the Configuration->Events menu. Every ZEN Master account will start with default Event Profile (1). The user cannot modify the default profile but can make a new event profile using the clone button (2). After naming and saving the new event profile you will see it in the event profiles list (1). Now you can edit the event rules in the new event profile using the Edit Rules button (2). To see details for an event rule or edit it, click on the down arrow to drop down the details for the rule. Rules are grouped by resource type – Adaptive Channel, Broadcaster, Source, etc. - and then by an error group – Usage, Configuration, etc. - and then by an error code. Some rules have single reason for a warning/error, such as CPU usage values exceeding a threshold, while other rules have multiple reasons for the warning/error, such as an Adaptive Channel going offline. Depending on the type of rule there are relevant settings for thresholds and the generation of user notifications. The thresholds define whether the event is a warning event or an error event. If a ZEN Master resource has any related error events, it will be in error state. If there are no error events on the resource, then if it has any related warning events, it will be in warning state. When an event escalates to an error, a user notification can be generated if enabled in the event rule. When an event is no longer an error, an “OK” notification letting the user know that the error conditions has been de-escalated can be generated, based on setting in the event rule. Normally, the “OK” notification occurs when the ZEN Master resource no longer has any errors and thus is in “OK” state. However, if the "Ignore object state for notification generation" checkbox is checked, then the “OK” notification occurs when each error event has been de-escalated. Currently, all users who have access to a ZEN Master resource, based on Roles and Access Tags, will see the same notifications as defined in the event rules. Allowing different users to get different notifications is being considered for a future release. Different types of event rules with different escalation approaches are implemented based on the ZEN Master resource type and error group. The most common type of event rule escalates based on the number of times an event happens within a window of time. If the event type configuration is set to Warning, as shown in the example below, it will be a warning event upon the first occurrence of the event and will escalate to an error event based on occurrences and time window. If the event does not occur again in the time window, then it will de-escalate back to “OK” state. The event type configuration can also be set to Error, which means it will be an error event upon the first occurrence of the event. When event type is set to Error there is no de-escalation process. As always, user notifications happen on Error events. Another type of event rule is available for simple events where thresholds are relevant. This rule is used for situations like Broadcaster license expiration which progress towards a final error state and there is no need for de-escalation. In the example below, there is a threshold for a warning event at 14 days prior to the license expiration and an threshold for an error event at 7 days prior to the license expiration. As always, user notifications happen on Error events. Another type of event rule is slightly more complicated events where both thresholds are relevant, and de-escalation can occur. For this type of event, it is a warning event when the value crosses one threshold and an error event when the value crosses a higher threshold but if the value falls back below either threshold, for the specified time window, then it will de- escalate back to the appropriate state. As always, user notifications happen on Error events. The last type of event rule does not allow any user configuration for error escalation because it is a critical issue. However, the user can configure notifications just like all other event rule types. Whenever you modify an event rule, be sure to click the Save button. You can also see the save status of the rule next too its title. It will either say “Not Save” or “Modified”, after you save it. After having modified an event rule, you can always set it back to default values with the Reset button. Once you have defined the event rules to your liking, they are applied individually to each resource – Channels, Broadcasters, Sources, etc. – in ZEN Master. When creating or editing the resource you will see a pull-down menu titled “Events Configuration Profile” where you can select the appropriate event profile. Note that once this release is deployed, any customizations of the old Notifications system will no longer apply and will need to be re-implemented using the new system. The following additional improvements were implemented in this release: • Added DTLS status to Zixi and RIST Targets • Added support for HLS Sources • Added ability to manually switch active Failover Source • Visualize traceroutes on a map • REMOVED Zixi license management and monitoring from ZEN Master; please use Zixi Customer Portal • Added ability to sort Channels by Source and Target columns • Added active Broadcaster columns to Targets and Channels • Changed SRT default latency to 1000ms to match Broadcaster default • Updated Free-for-All (FFA) authorization mode UI to require at least one input/output setting • Added API endpoint to list child Targets • Added dns\_prefix validation to Clusters create and update API endpoint • CMAF (DASH + fMP4 HLS) is now disabled by default Bug Fixes The following issues were resolved: • Fixed incorrect Source information shown on multi-Broadcaster Clusters • Fixed issue with editing Zixi pull Target name requiring restart • Fixed issue with being able to import duplicate MediaConnect Flows • Fixed error when deleting a user that has custom Grids • Fixed invalid parameters error when cloning a Zixi Target • Fixed maps occasionally not auto-refreshing • Fixed some SCTE errors not being logged correctly • Events message search inconsistent when message includes dashes • Fixed missing tooltips on Events Log page • Fixed dashboard issues list being inconsistent with main menu error/warning counters [title] ZEN MASTER May 2022 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be included in the ZEN Master May 23, 2022 release. Features The following new features were implemented in this release: • Re-architected ZEN Master monitoring infrastructure to support, in a future release, higher frequency monitoring as well as monitoring of additional machine metrics from the Broadcaster’s host system • Added support for creating AWS MediaLive transcoding Channels • Added support for custom ports for Zixi Push Sources and Zixi Pull Targets • Added alert for low audio level • Added a 'Termination Protection' toggle to Broadcasters, Feeder, and Receivers to prevent accidental deletion • Added dedicated detail page for Broadcasters similar to detail pages available for other types of objects Additional Improvements The following additional improvements were implemented in this release: • Set dark mode to be the default; light mode can still be enabled • Added location and ISP data display on all objects when available • Added 'Reset Stats' option when multi-selecting Sources • Added an option to 'Force Delete' Tags when they are in use • Added an option to set MTU on Sources and Targets, useful for situations requiring different MTU such as AWS Wavelength Zone • Added support for drag to scroll in diagrams • Added option to select Source Preference on Targets not yet assigned to working Channels • Added filtering by client device type on Zixi Edge Devices page • Improved sorting of event profile rules • Improved security and performance in history graphs backend • Improved IP to geo-location logic such that it will no longer conflict with manually entered location • Intelligent Data Platform (IDP) o Added filtering for Channel Insights graphs o Improved Incident save function to store full current state in the database for easier sharing o Improved Incident graphs to show local time instead of UTC o Added health scores on Zixi Targets • API o Feeder, Receiver, and Broadcaster GET now returns API credentials o Fixed page counts when using pagination in multiple API endpoints Bug Fixes The following issues were resolved: • Fixed PID mapping on Zixi Sources from MediaConnect • Fixed a rare Duplicate Access Key error when creating an Azure Cluster • Fixed an issue where a Pass-through Channel could be created with an invalid Source • Fixed global search not working with leading whitespaces • Fixed issue with UDP Sources created when the selected port is already in use on the Broadcaster • Fixed v15 Broadcasters with NVIDIA GPU not working in GCP • Fixed Source previews on Adaptive Channels showing more Sources than are actually in the Channel • Fixed incorrect missing Source error on Channels with no Targets • Fixed an occasional UI crash when editing Targets • Fixed localhost loopbacks created on Broadcasters when using monitor only Source with Adaptive Channels • Fixed target status in Targets tab on Channel details page • Fixed confusing object name on propagated Source errors on Targets • Fixed Automation when selecting a non-local time zone • Fixed decryption for Zixi Pull Sources • Fixed switching selected Channel on RTP Targets not switching the Channel • Fixed Merge Mode on Failover Sources • Fixed IO server Public Key not available for download • Fixed 'Internal Server Error' when enabling some Targets with Automation [title] ZEN MASTER November 2020 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates were pushed to ZEN Master on November 6, 2020. Geographical Maps ZEN Master now provides display of objects – Feeders, Receivers, Broadcaster, Sources, Channels, and Targets – on a geographical map. Connections between these objects are displayed with connecting lines showing the direction of data flow. The objects displayed on the map are organized by layers where a layer can be defined by a Channel in ZEN Master showing all objects related to that Channel or layers can be created as a user defined collection of objects. The initial location of objects is determined by IP address unless the object was assigned a location when it was created. Objects can be moved to any desired location on the map by selecting and dragging them and the new locations will be saved. Other Improvements and Bug Fixes • Browser tab header is now updated on navigation to show current page • Improved MediaConnect integration error handling • Improved performance of traceroute history graphs • Added seconds to events timestamps in the UI • Deep links now survive login, e.g. navigating to https\://ACCOUNT.zen.zixi.com/#/sources will take you to the Source page after login. Also enables sharing of VLC and WebRTC player pages. • Pull Targets can now be created on Channels with auto-pull disabled Sources regardless of the Source’s status • Licenses now have a notes panel • Added link to create new Zendesk support ticket directly from help menu • Fixed issue with remote access of some Sencore devices • Fixed error when rendering very large Channel diagrams • Fixed issue with editing UDP/RTP Sources breaking the UI • Fixed issue with missing timestamps on quick reports [title] ZEN MASTER July 2023 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be included in the ZEN Master July 26, 2023 release. Features The following new features were implemented in this release: • Remote access support for Videon Edgecaster. Unlike many remote access devices linked to ZEN master that provide browser access directly to their local interface, Videon’s devices are managed via the Videon LiveEdge Cloud portal. This update allows Users to connect ZEN Master to the Videon cloud and choose a specific available edge device for each Remote Access entry. o When adding a Video device to Remote Access: \- Choose the new ‘Videon’ type. \- Enter the Access Token generated via the Videon EdgeCloud interface. \- Hit ‘Load Devices’ to complete the connection. \- If the token is valid, the drop-down list will be populated with available Videon devices. \- Select the required device and hit ‘Save’. o Once a device is added to Remote Access, it will appear in the available devices list. o Selecting and opening the device with provide access to Video EdgeCloud and the selected Device: Additional Improvements and Changes The following additional improvements and changes were implemented in this release: • Support for Verify Stream ID on SRT listener Sources. o Adding ZEN Master support for the existing Broadcaster feature to verify Stream ID on SRT listener inputs. • Support Stream ID on SRT caller Targets. o Adding ZEN Master support for the existing Broadcaster feature to include Stream ID on SRT caller outputs. • Static egress IPs for ZM. o The ZEN master architecture has been updated such that all outbound traffic from the ZM backend, such as data traffic provided to Kafka for example, now use static IPs to allow customers to whitelist. o Details available upon request. Bug Fixes The following issues were resolved: • Pull Targets unable to connect when providing a custom Streaming IP on the Broadcaster. • Not possible to edit Encryption setting on SRT Targets. • AWS IAM role changes in ZM not propagating to AWS on Cluster update. • UI showing Manually installed AgentZ 'Not Reporting' even though it's working and reporting. • Non-Admin Users unable to change their own password from My Account page. • ZEC inputs not populating in ZM Source form. • Editing a disabled Channel causes it to become enabled. [title] ZEN Master 17 Feb 2026 Release [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates were included in the ZEN Master release for Feb 17th, 2026. ## Features The following new features were implemented in this release: ### SCTE-35 modification **Related docs**: - [SCTE-35 Modification Profiles](docId:-QYmFFVMc18NqpumZ7T3d) - [Adding Targets](docId\:xiKxI521HxgGj5WEZLcL7) - Note: This feature is a module addition, please speak to your account rep for more information. - ZEN Master introduces the SCTE modification suite allowing users to insert, remove, or manipulate existing SCTE35 markers. - When enabled, SCTE-35 Modification Profiles appear under the ‘Transformations’ menu. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Ft5vOrTTVyXOCSqtBay-t_.blob) Begin by naming and tagging the profile, and defining the default action for SCTE-35 messages that do not match your rules. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/cLyddU8pegLyHsSIzdRgo_.blob) Once a new Rules is named and a default action set, specific matching triggers can be set up along with associated action: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/pJDYg53Zvz9xrAtFopep1_.blob) Each Rule is configured to Keep, Remove, or Modify a SCTE-35 message based on a matching trigger and in the case of a modification the subsequent replacement message: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/XBVgQFOixVf51cklIHIPD_.blob) All SCTE-35 messages on a target with the profile are evaluated against rules within the profile. If a SCTE-35 payload parameter matches the User defined triggering parameter value, then that SCTE-35 message will be kept, removed, or modified as per any outlined modification parameters. If there are multiple triggers, the SCTE-35 message should match ALL criteria in order to action the rule. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/NCYdIUx7DFZcCQEsNEaQV_.blob) ### SCTE-35 Modification Rule Simulator. Once created, SCTE-35 modification rules can be tested directly within the ZEN Master interface. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Md-Nn3jTy6uGzrX69H8Ck_.blob) - After choosing the Simulator tab, an example message can be entered in the input field and Users can ‘Run’ the input against the Rule. - The rules and associated priorities of actions will be matched in turn and applied against the example input. - The decoded message and modification result is made available in JSON or XML format. ### Rule Application. - Once Created, SCTE-35 Modification Profiles can be applied to Targets in the advanced SCTE-35 Manipulation section of the New/Edit Target Dialog: ### AWS SSM integration **Related docs:** - [Actions on Broadcasters](docId\:B1y6nShFZcUwCd0_GSPG-) - ZEN Master now provides the facility to run AWS SSM commands directly within the ZEN Master User Interface. - Whilst multifunctional, this feature is primarily provided in support of Infosec teams with system update and patching requirements. - The AWS SSM Tool can be launched from the selected Broadcaster details page: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/uubQ2K-fiHce5HtQaFa5g_.blob) ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/fxY-NQEfJb8cJVJQUxE3k-20260215-222932.png) ** When opened, the “Run SSM Command” dialog opens to display:** 1. Current Broadcaster details (un-editable). 2. A dropdown list of SSM Commands (e.g. ‘yum update’) available to ZEN Master. 3. The Broadcaster Active Objects table. 4. The Close / Run SSM Command action buttons. ** When running a command, ZEN Master: ** 1. Updates the active object status with the initial and current status of all objects. 2. Monitors the SSM status and displays the tail end of the command output in SSM. 3. Upon successful completion, notifies the User. 4. Should the script fail, the User can use the **error status** and **output notes** to facilitate further investigation. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/wsv_7dWPWq5lGpmfNIdJN_.blob) ### Instance Refresh **Related Docs:** \*[Actions on Broadcasters](docId\:B1y6nShFZcUwCd0_GSPG-) **AWS Instance Refresh** - ZEN Master provides the facility to refresh an AWS Instance. - This feature allows Users to ‘swap’ out the existing instance for a fresh instance, useful for OS patching, instance re-sizing, OS Updates etc. - The new instance will re-connect to ZEN Master “in-place” of the existing instance. - The Instance Refresh Tool can be launched from the selected Broadcaster details page: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/zH4IgwmeN5m-eRkMwu2o0_.blob) :::Paragraph{listStyleType="disc" indent="2"} When opened, the “Refresh Instance” dialog opens to display: ::: :::Paragraph{listStyleType="decimal" indent="3"} Current Broadcaster details (un-editable). ::: :::Paragraph{listStyleType="decimal" listStart="2" indent="3"} The Broadcaster Active Objects table. ::: :::Paragraph{listStyleType="decimal" listStart="3" indent="3"} The Close / Refresh Instance action buttons. ::: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/JDkAmj4NCfWIq6lD3j6US_.blob) When Refreshing an Instance, ZEN Master will: :::Paragraph{listStyleType="decimal" indent="2"} Update the active object status with the initial and current status of all objects. ::: :::Paragraph{listStyleType="decimal" listStart="2" indent="2"} Monitor the Broadcaster status. ::: :::Paragraph{listStyleType="decimal" listStart="3" indent="2"} Notify the User on completion success. ::: Note: to make changes to the instance details, customer AMI Used, instance type etc., edit the Cluster settings before running the Refresh Instance Tool. ### TAMS Support **Related Docs:** - [Adding Transcoded Channels](docId\:xwF-mFNvRA5E3jQL2YMjU) - [Adding HTTP Targets](docId\:Nth0upANEbiTHSEGzcKa3) ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/mheZHPiD5NKrripAdQc96_.blob) ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/D50KnXpifvYho-oT_olRP_.blob) ### TAMS Support ZEN Master adds coverage of the Zixi Broadcaster integration to Time Addressable Media Store (TAMS) format. :::Paragraph{listStyleType="disc" indent="2"} Requires Zixi Broadcaster v19. ::: **Channel Configuration: ** - the ‘TAMS Enabled’ in the Transcoded or Adaptive Channel in the New/Edit Channel dialog. - This will allow for the configuration of the addition video and audio UUID’s required by the TAMS format. - For Transcoded Channels, this will include the optional source pass through. - All other renditions will also provide a UUID entry field. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/n1YcbPDmfoiuR4VSow_Qd_.blob) - The presence of a value in the UUID field will result in the generation of an associated TAMS variant. **Target Configuration: ** - A TAMS Target Type can now be created via the New “HTTP” Target menu. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/UdQXGairHTmx1gPXy2kms_.blob) - Here the User is presented with: 1. The option to set a TAMS target sub-type. 2. The URL of the intended TAMS Server endpoint. 3. Credentials, Auth Token URL, and deletion Scope options. **** **** # Improvements and Changes The following additional improvements and changes were implemented in this release: - Backwards compatibility for **NULL Packet Search Window** field in SCTE-35 manipulation. - **Splice Inserts SCTE-35 messages** are now tracked separately in the graph based on into/out of network flag. o Updated decoded SCTE-35 display to use ‘threefive’ compatible format and added standard XML option. - **Date/Time selectors** now use User-selected Date/Time format. - **Added UI status** to **Failover Sources **when locked. - **Go to Alt. Path Targets **now prioritize switching to a Primary Source when an option. - **Optimized Failover Source locking** to improve API response times. o Added an alert for Broadcaster Distribution Overflows that can affect Sources. - Added **per-NIC bandwidth graphs** to Broadcasters. - Added **unassociated PIDs** to Source Stream Info panel. - Added a **multi-select action to clear existing alerts** of objects. - Added a **Now button** to Date/Time selection dialogs. - **“Ignored” PIDs **are now marked as such on details and graph panels. - Targets with PID Mapping display the PID mapped Stream Information instead of original. - Added a **new alert for Targets** connected to an incorrect Broadcaster input. - Will trigger an Offline – Other alert. - **Diagram Improvements** – Additional actions and detail added to Source, Channel, and Target Diagrams: - **Enable/Disable/Mute/Unmute **actions. - **URL File Source** names. - Better naming of exported diagram files. - **Updated API Keys table** with columns for new properties: - **Optimized Source listing from backend** to improve performance in multiple forms. - **Updated Share source** to allow for 90 day shares. o Added option to ignore TLS certificate validation on Zixi Pull Sources. - **Current AMI** is now tracked/displayed for AWS Broadcasters: - Applies to AMIs launched from the release date. # ESNI & ESAM The following updates were implemented for ESNI and ESAM: **ESNI ** - Improvements to ESNI UI Schedule Simulations. - Implemented Signal Tolerance support. - Added option to automatically remove expired Medias. - Improved internal logging to allow debugging bad 224 payloads. - Re-applying an active policy at a new priority will now update its priority. - Fixed a race condition that can happen when identical SCTE messages arrive at the same time on Sources with the same external ID. # API Additions and Changes ZEN Master API documentation updates for the following sections: **Technical Reference:** For detailed field change technical reference see the accompanying document: - ZEN-Master-API-Updates-Reference\_Feb\_2026.csv.zip in the Zixi Customer Portal **New API Endpoints:** **Channels**: NEW: **GET /channels** :::Paragraph{indent="1"} List all Channels in your account. ::: **Clusters**: NEW: **POST, PUT /clusters/linode** :::Paragraph{indent="1"} Create/update a Linode Cluster. ::: **SCTE-35: ** NEW: **GET /scte35\_modification\_profiles** :::Paragraph{indent="1"} List SCTE-35 modification profiles. ::: **API Field Additions:** **Channels, Targets: ** Time-Addressable Media Store (TAMS). :::Paragraph{indent="1"} New fields added to support TAMS. ::: **Clusters**: Added **object\_link** System-generated field to all responses. **Targets**: SCTE-35 Modification Profiles. :::Paragraph{indent="1"} Added **scte35\_modification\_profile\_id** ::: :::Paragraph{indent="1"} Supported Targets: RIST, RTMP, SRT, UDP/RTP, Zixi Pull/Push. ::: **Targets**: Target protections. :::Paragraph{indent="1"} Added **termination\_protection** ::: [title] ZEN MASTER APRIL 2021 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates are included in the ZEN Master April 12, 2021 release. Improvements • Added support for SRT Push Targets (Caller mode), SRT Pull Targets (Listener mode) was already supported • Added support diagrams on Targets, showing Channels and Sources that connected to the Target • Added support for matching PCR to Video PID in PID mapping • Added ability to monitor and alert when captions in the Source are not passed through to HLS WebVTT captions • Added logging for assignment and changes of Targets on Channels • Added option to ignore transcode GPU limit on transcoding Channels and Sources • Added option to create all objects types in a disabled or muted state • Added uptime column to Feeder, Broadcaster, and Receiver tables • Added support for running N2 machines in GCP • Various UI improvements Bug Fixes • Fixed issue with deleting RIST Targets in MediaConnect integration • Fixed issue requiring multiple save attempts when creating an MediaConnect Source • Fixed issue with incorrect error message when trying to disable/enable a MediaConnect Source • Fixed erroneous "Failed acquiring Stream IP address" event message • Fixed multiple issues where creating Channels or Sources will overwrite necessary configs on Broadcasters • Fixed issue where editing the playback URL on HTTP Targets restarted the output • Fixed issue with filtering using Boolean operators when search terms contained the Boolean operator [title] ZEN Master 28 July 2026 Release [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ # ZEN Master — July 28, 2026 Release Notes The following updates will be included in the ZEN Master July 28, 2026 release. ## Features The following new features were implemented in this release: ### Search - **Global search rework:** - Global search is updated to search across all object types and use frontend detailed filtering, breaking results out in the standard tables. - Networks are now included in global search results. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/KDs8dOY-ERmQLTMQipm_2_search-1.png" size="100" isUploading="false" position="center" width="1942" height="546" darkWidth="1942" darkHeight="546" showCaption="false" indent="2"} - **Implemented Preset Filters for Simplified Table Search Experience:** - Standard searched filters can now be saved as presets which persist across sessions and browsers. - Saved filters can be private or made public for wider use. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/F22kmDMNC95pnq3Ox0eWH_table-search.png) ### Channel Switching - Channel Switching button added to Target grids. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/VP7SHR3ajAlL6WSCL9VzS_channel-switching.png) ### Transport & Processing - UDP/RTP Target remux settings in ZM UI and API. - Remux support on Error Concealment sources. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/az-ruH_JQxPF104D_jgCH_remux-support-ec-targets.png) - Display and select SRT version on Sources/Targets: - Added option to select SRT library version on Sources/Targets. Note - requires version 19 and the selection is not enforced when version is not available. - Version selection is available in the Advanced section of the edit dialog. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ZxLCD1dgw22IWyGEU4iA7_select-srt-version.png) - "Bind to local NIC by CIDR" added to Zixi PUSH and SRT Caller Targets (parity with UDP/RTP). ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/65gTJ3K0HDmQvhEt_ajcz_nic-cidr.png) - "Discontinuity on CUE" flag added to adaptive/transcoded channels: - Exposed new "Discontinuity on CUE" flag on Transcoded/Adaptive Channels to provide platform parity. - Flag is available in advanced section of the dialog and the ZEN Master setting is propagated to the Broadcaster. - Rendition sort control on Transcode and Adaptive Channel ladders. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/3sik1_CsWSgi_CVWBIxmG_rendition-sort.png) - New Adaptive Group option to insert HLS PDT when using SEI timecode (Hotfixed): - Added Segmentation Time option to Adaptive Channel "Timecode (EXT-X-PROGRAM-DATE-TIME) Source". ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ogdB-BKHcJafT4Xh6cbe7_adaptive-group-option.png) - Cluster-level control to enable/disable PID 23 metadata injection, in the Advanced section of the cluster edit dialog. (Metadata injection is enabled by default.) ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/OeTRIfOgjGtOoAzZAX_dW_cluster-level-set-metadata-injections.png) - **NETINT transcoding card support provided with profiles for Broadcaster Version 19.** Current NETINT options include: 1. 8 Bit or 10 Bit PP 2. 420 chroma subsampling 3. Decode / Scale / Encode ### Cloud and Infrastructure - Multi-select for Broadcaster migration tools - Upgrade, Refresh, AWS SSM (at the cluster level). - Added support for g6.2xl to g6.12xl instance types in ZEN Master. - Managed AWS Nvidia cluster instances now launch with the latest validated AWS Linux 2023 AMI. - ZEN Master tags now propagate to all AWS resources on cluster/BX creation. - Dropdown list of Elastic IPs when selecting EIP reservation IDs. - Network settings editing disabled in the Broadcaster UI for machines in managed AWS, GCP, or Azure deployments. ### Auth and Security - PKCE SSO support for OAuth 2.0 login. ### Failover - Added "Source became inactive" event log for Failover Sources. - Lock / Unlock control added to the in-diagram context menu for Failover Sources. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/XTX_Z6g6dDsqTo6_F_D6X_failover-lock-unlock.png) ## Additional Improvements and Changes The following additional improvements and changes were implemented in this release: - Added SSM command execution logging — who ran it, timestamp, and the script executed. - Added lifecycle logging for SSH tunnel keys. - Enabled Event Log download for users with read access. - Added a log entry confirming Live Clip insertion via the Live Events workflow. - Added optional toggles to clone Tasks and/or Schedules when cloning an Automation. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/xxjB2ghYqyz_HeeDxfjQj_clone-task-set.png) - Added a landing page redirecting OnAir share links to the app. - Extended the Broadcaster restart detection window to capture restarts with downtime over \~30 seconds. - Object page layout controls moved to dropdown. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/jCwLb2Z3pszrXvWRJo1GC_object-page-layout-controls.png) - Added button to fit widget height to content. - Transcode profile logo insertion now shows a UI preview of logo placement. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Va0fFqRrlJhgDRCdDj6bV_logo-placement-preview.png) - Look and feel layout improvements to ZEN Master's VLC player page. - Updated DTLS encryption icon. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/9otn_AAC2SYpDK3SlHj5k_dtls-encryption-icon.png) ### ESNI - Added a button to re-trigger all currently active policies in the ESNI schedule view. - Added a Target "Sync with ESNI schedule" button to manually sync an ESNI-controlled Target with its schedule. - Re-fire already-active policy actions to re-apply SCTE-35 content IDs and similar signal actions. - ESNI as-run report export. ### SCTE - SCTE-35 modification: "Select from MID" operation allowing selection of specific UPID from a MID type UPID to pass on to downstream. ## API The following API additions and changes are included in this release: ### Technical Reference - For a detailed technical reference on field changes, see the accompanying document in the Customer Portal: - ZEN-Master-API-Updates-Reference-2026-07-28 ### New API Methods - **SCTE-35 Profiles:** to the existing endpoint, added methods: - POST /scte35\_modification\_profiles - GET by ID, PUT, DELETE /scte35\_modification\_profiles/\:scte35ProfileId ### API Field Additions/Updates - **Access Keys, Events Profiles, PID Mapping, Tags, Transcoding Profiles:** - Added name query parameters for efficient use. - **Channels, Targets:** - Added functionality for the name query parameter. - **Channels, Sources, Targets:** - Added Billing Channel ID. - Field: billing\_tag. - Transcoded Channels. - Sources: All except NDI, Monitor Only. - Targets: HTTP, RIST, RTMP, SRT, UDP/RTP, Zixi Pull/Push. - **Clusters:** - Added Billing Channel ID. - Fields: inputs\_billing\_tag, outputs\_billing\_tag. - **Sources:** - New filters for GET /sources. - Added type query parameter to filter by Source type. - Added cluster\_id query parameter to filter by Cluster. - **Sources, Channels:** - Remux support for Error Concealment. - Added error\_concealment\_remux\_mode. - Added error\_concealment\_remux\_buff\_size\_ms. - Added error\_concealment\_smoothing\_ms. - Sources: Demux, Failover, HLS, Inter-Cluster, Multiplex, Multiplex SPTS, RIST, RTMP, SRT, UDP/RTP, Zixi Pull. - Channels: Failover (deprecated). - **Targets UDP/RTP:** - Remux settings from the Broadcaster. - Added remux\_pcr\_interval. - Added remux\_buffer\_ms. - Added remux\_disable\_padding. ### Documentation Only - **Failover Channels:** deprecated endpoints will be removed in a future release: - PUT /channels/failover/\{channelId}/components/\{componentSourceId} - GET, POST /channels/failover - GET, PUT, DELETE /channels/failover/\{channelId} - GET /channels - response will no longer include Failover Channels. - **Failover Channel Objects:** deprecated objects will be removed in a future release: - GET, POST, PUT /live\_events - failover\_channel\_ids, failoverChannels. - POST /live\_events/\{eventId}/stages/\{stageName} - FailoverChannels. ### ESNI - **Signal on remove in ESNI schedule view:** - Updated ESNI schedule view to display triggering signal when a Remove activates a new policy. - Support PT0S for signalTolerance. - Scope UPID Format to Media. - **Don't fail on missing timestamps in simulation:** - Updated ESNI simulation engine to support MatchSignal only schedules. - ESNI future capped to 24hrs. - Signal and raw popup optimization. ### SCTE - ZM support for SCTE35 insertion on Zixi Push sources. - **Match Target SCTE log UI to that of Source SCTE log:** - Added SCTE-35 history graphs on Targets. - **SCTE-35 modification: allow changes before a Create rule:** - SCTE-35 create rules now apply in order. - Improve error handling on SCTE-35 modification simulation UI. - **"Install SCTE-35 Modification Agent" button now installs to the same directory as a manual install:** - Updated SCTE-35 Modification agent install folder to match manual install. - **Manual Channel Switching for POIS enabled Targets:** - Added Channel Switching support for POIS enabled targets when assigned to channels with a single Source. - **SCTE35 parser XML builder drops Avail Descriptor:** - Fixed MIST being unable to create Avail Descriptors in modified/created SCTE-35 signals. - **SCTE-35 modification: selecting "No UPID" on Create type 5 to 6 fails:** - Fixed SCTE-35 encoding error when creating a type 6 with "No UPID". - **SCTE-35 source graph collapses Time Signal events:** - Fixed all Type 6 (TimeSignal) SCTE-35 messages graphed as a single type. - **POIS output and loopback not being created:** - Fixed Target creation when using loopbacks silently failing due to port conflicts. Note - for UDP/RTP, RIST, and SRT client v19.0 broadcaster is required. ### Licensing and Usage - **License and Measure: new "Channel ID" field in UI and API:** - New "Billing Channel ID" field in UI and API to support new channel-based usage tracking. - **Usage reporting backend support for new counters in v19:** - The metrics include input quantity, output quantity, and transcode quantity. [title] ZEN Master - July 30 Deployment Details 2018 [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ • Audio levels now displayed in Source thumbnails view (requires v12 broadcaster) • Option to auto rotate pages in Source thumbnails view • Sources can now be targeted at specific broadcasters or broadcaster type (primary/backup) • Improved HTTPS detection in tunnel access to support tunneling to Elemental encoders • Can now customize Adaptive Channels HLS/DASH chunks configuration • New pull target load balancing mode in clusters, this distributes the targets evenly between all broadcasters in the cluster • New Content analysis info from v12 Broadcasters is now displayed under the TR101 tab for Sources and tracked in Source history • TR101 errors and warnings are now logged with the actual message instead of a generic TR101 error message • Source history graphs updated with much more information, including per PID bitrate and content analysis state. • AWS Broadcasters can now be configured with HDD size • User login events are now logged with email, source IP and time • Added login attempts rate limiting to prevent brute force attacks on passwords. • Moved authorization API to backend to prevent domain server issues from disabling the Zen service completely • Authorization API now works with HTTPS on v12 Broadcasters • AWS Cluster instance type can now be edited • Event Log reports • Can now set the playlist name in HTTP/S3 targets • VLC playback link for adaptive channels • RTMPS support • Channel access tags now optionally copied from sources on creation • Content Analysis and TR101 can now be enabled/disabled per customer • Global Search • Adaptive Channels now support Dash and HTTP Targets can select between HLS and DASH encapsulation • IP Whitelist - currently denies connections at the authorization level • Zen API support • Create multiple sources at the same time (Feeder, Broadcaster and Monitor Only Sources only) • Automatically stop non-Zen push outputs on feeders and receivers (to support overwriting existing configuration with Zen config) • PIDs monitoring feature, sends an alert when PIDs in a source change • Multi-tagging - all objects can now have multiple access tags • Source and Channel name uniqueness scoped to cluster • Notification emails now contain a link directly to the relevant object • Targets now have enable/disable functionality (previously to disable had to detach from channel) • Redesigned Events Log implementation to be much much faster • Flapping state detection • True monitor only sources • Redesigned pull targets and public outputs to use generated unique stream id (will require update to some existing configurations) • Tunnel connections now report a 'Connected' event with source IP instead of a generic 'OK' event • Zen architecture redesigned to support "cloud service" types of accounts - these are accounts without their own broadcaster clusters. • Usage is now tracked and displayed, currently there are 2 parameters, o Source Hours - number of hours a source was active (per source) o Output Bytes - total number of bytes sent by all targets on the account • Forgot my password! [title] ZEN MASTER December 2020 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates were pushed to ZEN Master on December 1, 2020. Improvements • Added option to reduce Broadcaster process priority on managed clusters • Added capturing of minimum and maximum statistics, RTT, jitter, and bitrate between API calls to the Broadcaster. Requires v14.1 Broadcaster. • Added Packet Loss % graph to Zixi Sources and changed Not Recovered to % as well • Added context sensitive links to online documentation in the Help menu • Added “Recent” tags selection where tag selection combo boxes will now display the last 5 used tags at the top • Added support for changing Program Numbers in PID Mapping. Requires v14.0.40996 Broadcaster. • Added option to clone Map configurations • Added ability to search for objects by Tags in Maps • Added edit functionality on AWS/GCP/Azure accounts to support updating credentials • Added option to mark Sources as 'backup' in Hitless Failover Sources, allows having two primary Sources with live content and a backup file Source for when both primaries are offline, as an example. • Searching for a hidden object on a Map will now display it Bug Fixes • Fixed issue with configuring CBR transcoding on older Broadcasters, does not affect any existing configs in production • Fixed issue causing GPU stats to show up on the incorrect Broadcaster in Broadcaster list • Fixed issue with editing Target tags causing a restart of the Target • Fixed issue with broken Channel based Maps after a Channel is deleted • Fixed Channel diagrams with more than a 100 targets showing an error, diagrams will now display less information the more objects are added • Fixed multiple issues with SRT/RIST/NDI Targets not displayed correctly on the Dashboard [title] ZEN MASTER August 2021 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be included in the ZEN Master August 19, 2021 release. Features The following improvements were implemented in this release: • Added support for Zixi Billing codes, which allow usage to be tracked at per Source and per Target granularity and allocated between multiple parties in a Zixi workflow. Zixi Broadcaster v14.8 is required. • Allow multiple NICs to be selected for managed Zixi Pull Targets • Implemented single Output mode for SRT Push Targets so that primary and backup streams are not simultaneously sent to the same SRT Target • Added support for SSO systems that require a separate User Info API call • Added support for Opus and 302M Audio to PID Mapping • Added Drill down tab when Intelligent Data Platform (IDP) is enabled. The drill down diagram shows key data features that influence the Source Health Score. UI Improvements The following UI improvements were implemented in this release: • Added maps configuration option to always show connections • Added Zixi License details to Feeder, Broadcaster, and Receiver details pages • Added option to easily create a Channel from Source on the Source page • Added option to easily create a Target from Channel on the Channel page • Removed Broadcaster Cluster types from the UI • Added Source thumbnails to Channel details page • Added sorting for files list in File Source form • Updated ZEN Master links to use Cluster name instead of DNS prefix • Added support for enabling “Don’t synchronize” on adaptive groups Bug Fixes The following issues were resolved: • Fixed incorrect error reported on offline Pull Targets • Fixed issue with global Search not returning NDI and MediaStore Targets • Fixed issue with PID Mapping profiles validation rules • Fixed error handling in multi-enable/disable dialogs • Fixed issue with RTMP Source edit form resetting Target Broadcaster selection • Fixed issue with cloning an object with expired muted flag creating a new muted object • Fixed missing ‘Convert to Regular Target’ button on child Zixi Pulls • Fixed missing error/warning details in some objects on Grids • Fixed missing data in Channel Diagram • Fixed issue with Force Notify option not saved in events profiles • Fixed SSH Key import always returning an error [title] ZEN Master 20 May 2025 Release Notes [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ ## Features ### Additional stage transition controls for Live Events: - Live event stage controls have been updated to provide more control and allow changes while an event is active, and to **allow mixing manual and automated** **stage transitions**. - Mixing manual and automated stage transitions allows you to automate known transition times while manually managing ones that cannot be known in advance - for example: - Sports events, where the start time is known, but breaks between periods and ending time will depend on things that happen during the event - A political speech or news conference, where the start time is known, but the duration is not ![Mixed Mode Stages for Live Events](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-6Jz2mCwzGfDPyyGgmxbFj-20250615-191843.png) - Creation Changes: - The event Staging Mode now sets the default for each stage, which can be overridden on a per stage basis. - Toggling the default will switch all existing stages and be obeyed by any further stages added. - Users can override the default for each stage, allowing for a live event where, if needed, specific stage transition settings can differ from the default. - The previous start time of the event is now simply the start time of the first stage. - Newly created events will require manual stages to have a notional start time even if set to manual. - Active Event Changes: - The event will automatically start on time if the first stage is ‘auto’, else it will require an operator to initiate the event with confirmation. - ![Live Event Stages Map](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-Tgw3GVK9hjIRBupKHyOez-20250615-192631.png) - All future transitions will behave similarly, based upon the auto or manual configuration of the next stage transition. - When starting a manual stage, or any manual advance, the user is now presented with a confirmation dialog that offers the operator a chance to keep all future stage transitions at their scheduled time, or to keep their scheduled durations and adjust the start times accordingly. - ![Confirm Choice of Maintaining Start Time or Duration for Stages](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-ZBP79_gBJ1gzQb5Fn4QK1-20250615-193520.png) - Events can be edited in progress via the edit button above the timeline: - ![Edit Stages while Event in Progress](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-BjF0AqSzFLRld8zt2mzAs-20250615-193728.png) - In practice: - All existing and familiar event stage flow are maintained, simply by setting the default of the event, or each stage to either manual or auto. The event will proceed as normal. - However, operators are now able to set each stage transition separately according to an events requirement. For example: - Sporting events start on time, but the end is usually not fixed: - Here, the event can be configured to have an auto start time and a manual end. - Now the stream can start automatically on time, and deliver the program feed, but will not end before an operator manually confirms the end point. - Schedule changes require alterations to the stage length while the event has already started. - Secondly, operators can adjust all future transitions accordingly: - If a game planned to automatically start is suddenly delayed, an operator can switch to manual. - However, when the operator eventually does move to the next stage, they can adjust stage start times accordingly, as each period will have a corresponding delay. - If on the other hand a broadcaster suddenly needs to start early for an unscheduled on-field attraction or incident, the official start times of the periods can be maintained. ### SCTE-35 manipulation controls on Sources: - When enabling SCTE Insertion (via the API), ZEN Master now adds support for SCTE Manipulation controls on Sources and Failover Channels. ![SCTE-35 Manipulation Options](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-FjRLzNvx5uCgLpUmpqLFI-20250615-205845.png) - Once enabled, it is now possible to dictate the PID into which the SCTE will be inserted. - An existing SCTE PID can be removed in place of a new PID or replaced with a NULL packet PID. ## Additional Improvements and Changes - Expose SCTE-35 controls on Failover Channels o SCTE-35 log updated to show correct pre-roll and PTS values taking PTS Adjustment into account - Optimized ZEN Master/Broadcaster API calls to improve performance of orchestration actions - Implemented paginated loading to Targets list to improve UI responsiveness ## ESNI and ESAM ### ESNI - Made XML namespace optional - Support for ID in ESNI create/update API - Added non-standard validation endpoints for SCTE-224 XMLs ## API ### API Additions - Created a “bulk Targets to Channel assignment” endpoint - Pass-through Channels only for now ### ZEN Master API Documentation Updates - PID Mapping Profiles - Add map\_range - Review and update - ZEC - Refactor and remove oneOf - Live Events - Update for revamp - Channels - Review and update - Transcoded o Fix sources as array of objects - Pass-Through - Sources - Separate 608/708 captions monitoring - monitor\_cei608\_cc - monitor\_cei708\_cc - Document fields - tr101.programs.epids object - Targets - New endpoint to assign multiple Targets to a Pass-Through Channel - /targets/assignToChannel - Review and update - RIST - RTMP - PULL - Add to PUT: update\_child\_targets - HTTP - UDP/RTP - NDI - SRT - CDI - JPEG XS - Entitlement - MediaLive HTTP - Frame thinning support - Add frame\_thinning\_latency - ZEC Push, Broadcaster Push Sources - Zixi Push Target [title] Zixi Documentation Updates [path] / ## 28 August 2026 ### New Documentation - [Using Zixi Documentation](docId\:lSBEYruIz4H_LcGzcrQRr) - Some tips for using this documentation site most effectively ### Updated Documentation - [Server Settings](docId\:Eg6UJizLtdcdIunEvOoDj) (Broadcaster) - Added explanation of Import/Export buttons - [ZEC Server Settings](docId\:hZYk9zZCwBK-IMSaKOwh1) - Added explanation of Import/Export buttons ## 13 August 2026 ### New Documentation - [Understanding Licensing](docId\:fE6v9ELwIKBfv9aTXt2MK) - Understand how Broadcaster licensing works - [ZEN Master Egress IPs](docId\:zWDaK6BRL9-HEDtaBH_9b) - Documented ZEN Master's 2 egress IP addresses for those who need to whitelist them for incoming data ### Updated Documentation - [Viewing Stream Statistics](docId\:EyGV42JXIoEan-bI4Ra0I) - Added new **Time Left **field ## 28 July 2026 - [ZEN Master 28 July 2026 Release](docId\:iGqPCiDiVwH-tvMUNyFrJ) - Many [ZEN Master](docId\:FG4D7DmllMvvFWAxtGNE2) docs updated, including adding sources, channels, and targets ## 2 July 2026 ### New Documentation - [Release Notes: Zixi Broadcaster Version 19](docId:4cz3kXeYhAd1_2ydw8j9n) - [Zixi Broadcaster/ZEC v19 Documentation](docId\:vqtUe3_40jdNjQL5ExR8c) - [Upgrading Broadcaster from legacy versions](docId:2s1ii1_U6bttJBoTJYMah) - [SRT Target overflow disconnects Troubleshooting guide](docId\:pQJZa8xfULF6SN7awEGMC) - [Encoder Bitrate Spike Troubleshooting Guide](docId:9ci3Oqw8sz_lqibokrQoO) ## 12 June 2026 ### New Documentation - [Source Status & Error Reference](docId\:HODONx74L3mVaP1b3g79Z) - A complete guide to status and error messages for sources - [Using Terraform with OCI](docId:-lvOa8WBVisluh40f5TZa) - Using Terraform to set up a Broadcaster on ### Updated Documentation - [Matrix Interface Elements](docId:1LSmSzgW5u6eotZhO_0hs) - Added note on how encrypted streams are marked in the Matrix - [Transcoding an Input Stream](docId\:xDNbYsXp-yJdeOgpGwOPJ) - Added info on how to merge HTML Overlays with the stream (requires the HTML Overlay Plugin) - [Adding SRT Outputs](docId\:ZVziRZpehLTSudX2idB7Y) - Added information on how to encrypt the SRT output - [Creating a Failover Group](docId\:RPF7OMEFoUSEAAtCvNi82) - The document incorrectly implied that the streams in the failover group must be identical in content; that is not the case ## 29 May 2026 ### New Documentation - [Adding HTML Overlays - ZEN Master](docId\:fHnebEFhWM0psrzv52tDo) - Understand how to create HTML Overlays and how they get added to videos during transcoding ## 1 May 2026 ### New Documentation - [Zixi On Air Pro Guide](docId:8mmLXna1om5BAcjoA-oiC) - Multi-page guide to using the new version of Zixi's app for sending streams to a Broadcaster directly from your iOS device - [Understanding MTPS and SPTS Inputs](docId\:wEF7s3Dygkl7bQoKvwIJA) ## 10 Apr 2026 This week's updates are most the for the April 7 ZEN Master release. ### New Documentation - [Viewing Live Events in Timeline View](docId\:xwWr0af64kKT7b0d7g24s) - [Adding a Zixi Source – OnAir](docId\:n4zdGFRpvVE3Kn4ek0z82) ### Updated Documentation - [Adding a Source - HLS](docId\:wkIFT3FbZB62f-6S4Zhbw) - [SCTE-35 Modification Profiles](docId:-QYmFFVMc18NqpumZ7T3d) - [Adding Zixi Pull Targets](docId:1tcWt65YZrnyWQiS7EAKA) - [Adding Zixi Push Targets](docId\:w7pgXYFK9SDyNQH_LRisd) - [Adding Zixi AWS MediaConnect Targets](docId\:E6rfLr5hPPecWd0nSWUOT) - [Adding RIST Targets](docId\:MrGwbni-X_Tm9L5upmkz8) - [Adding SRT Targets](docId\:f0RaMeGFw8RacR47wYlUO) - [Adding UDP/RTP Targets](docId\:UNZPMFAYf4TC32bChHPan) - [Adding AWS Outputs](docId\:CEKYAC7JI9gltBcPM40K3) - Add note that Elemental MediaStore is no longer an option ## 27 Mar 2026 ### New Documentation - Two new sections in our [Troubleshooting](docId:8fgk_ka5EQ71jMUusAZbS) guides - [Best Practices](docId\:zRsQrKVOELv4kA51Ezc0U) - [General Troubleshooting](docId:8G3vceiKZJsnPYLU1rQSH) ### Updated Documentation - Added section on Creating a Self-Signed Certificate to: - [Enabling DTLS](docId\:dPbwtfB1ic317na2uhnJD) - [General](docId\:R8yxxqXQ8e_YJM6M79TJG) ## 20 Mar 2026 ### New Documentation - [AWS SSM User Guide](docId\:SAhJY3H8uS6uNT2OkuNtR) - Guide to the AWS setup required to issue AWS SSM commands from ZEN Master ### Updated Documentation - [HTML Overlay Installation Guide](docId:6SNc7FcKnryvMtgzr06kB) - Updated for newer versions of Linux, with downloadable scripts to simplify the process ## 13 Mar 2026 ### New Documentation - [Broadcaster History CPU and Memory](docId\:a6UieNmy2eM-pMX373DOr) - An explanation of the how the CPU and Memory graphs are derived and their purpose - [Troubleshooting](docId:8fgk_ka5EQ71jMUusAZbS) - Errors and troubleshooting issues in Broadcaster and ZEN Master are now in their own section of the documentation - any bookmarks should automatically redirect to the new locations ## 17 Feb 2026 ### New Documentation - [SCTE-35 Modification Profiles](docId:-QYmFFVMc18NqpumZ7T3d) - [Changing the Default Port for the Broadcaster Web UI (4444)](docId\:aBAeNYnXICovaU6xcJQRj) ### Updated Documentation - [Requirements](docId:0l85jFgC5PWp6y-u23Y7q) (for DPDK in Broadcaster) - [Source Stream](docId\:dbcol69jr73U2Wy3SOFGw) - Added instructions for playing source inline - [Adding Transcoded Channels](docId\:xwF-mFNvRA5E3jQL2YMjU) - Updated for TAMS targets - [Adding HTTP Targets](docId\:Nth0upANEbiTHSEGzcKa3) - Updated for TAMS target - The following docs updated for SCTE-35 Modification Profiles - [Adding Zixi Push Targets](docId\:w7pgXYFK9SDyNQH_LRisd) - [Adding Zixi Pull Targets](docId:1tcWt65YZrnyWQiS7EAKA) - [Adding Zixi AWS MediaConnect Targets](docId\:E6rfLr5hPPecWd0nSWUOT) - [Adding RIST Targets](docId\:MrGwbni-X_Tm9L5upmkz8) - [Adding UDP/RTP Targets](docId\:UNZPMFAYf4TC32bChHPan) - [Adding SRT Targets](docId\:f0RaMeGFw8RacR47wYlUO) ## 13 Feb 2026 ### New Documentation - [Editing Input Settings or Duplicating Input Streams](docId\:pekHMXF2Mt4kk2-4u7Nr5) - Adding some missing documentation for Broadcaster ### Updated Documentation - The following docs were updated to clarify latency statistics and that changes to latency on a live source do not take effect until the stream is restarted - [Editing Output Settings or Duplicating Output Streams](docId\:uXGpRwAHHotL5Ldg-aeI5) - [Editing Input Settings or Duplicating Input Streams](docId:_ZqxXp21VJMOnYsF4Bx1b) - [Editing Input Settings or Duplicating Input Streams](docId:_ZqxXp21VJMOnYsF4Bx1b) - [Viewing Stream Statistics](docId\:aY59Yvq41rJthvDWmqVm-) ## 30 Jan 2026 ### New Documentation - [Comparison of Transcoders: Video Codec and Color Support](docId:0kUGUMogtknAKZY-UG6Qs) ### Updated Documentation - [Single PULL Transmission from Redundant Sources (Hot Redundancy)](docId\:HsaKQf4iH2RZSVnGIrglo) - [Dual PUSH Transmission to Single Target with High Priority Source (Warm Redundancy)](docId:2s71JLHHfdBPIkuTNyoaD) - [Dual PUSH Transmission to Redundant Targets (Hot Redundancy)](docId\:gyqKK5sYCIw-UM8kbLaeO) - [Adding SRT Streams](docId:9iaI4hwjF7HSzRj3izhjP) ## 16 Jan 2026 ### New Documentation - [Zixi Latency Negotiation](docId\:OT6ICc9DNdHiF9WQMpSoj) - [Understanding Transport Streams and IP Delivery Protocols](docId\:UreBRT0iD42_JulFzHhFe) - [TAMS and Zixi](docId\:Xb6n9zuNCcGOdDaBrvsba) ## 9 Jan 2026 ### New Documentation - [SCTE-35 Insertion - Broadcaster](docId\:QioGCWSbfgTfg5cZqN_Va) - [SCTE-35 Intsertion - ZEN Master](docId\:P41x2TyDYny_zgjl3-XXA) ### Updated Documentation - [Release Notes: Zixi Broadcaster Version 18](docId\:RadURZyqziy7DJ_BnSPqQ) - Added release notes for v18.9 - [Adding File Streams](docId:5JYwR6Abzyg5VT131sMEW) - Added explanation of the file path - [Zixi Transport Stream Protocol](docId\:jdVs1L_ZSEjBtnf2oKaV9) - [Viewing Existing Targets](docId\:PBUhNBoOCrnR9k0j1O0Zh) ## 12 Dec 2025 ### New Documentation - [Comparing Broadcaster and ZEC](docId\:iCJK7jRH5AwzyFcz9dLMh) ### Updated Documentation - [Requirements](docId:0l85jFgC5PWp6y-u23Y7q) (for DPDK) - [Source Info Pane](docId\:VybGOZcLBl0-3h-yfHP92) - [Viewing Existing Sources](docId\:DZbMC_Tk_K3MrDXvG7qP5) - [Adding an Elemental Link Source](docId\:DPvTZ8aJZ6HOBGDaYVY4A) - [Adding an AWS MediaConnect Source](docId\:PzkzjtdAIlmBOHGj4VMQA) - [Adding an ST 2110 JPEG XS MediaConnect Source](docId\:GFfqDw49NsAMTrq-yOVsu) - [Adding a CDI-protocol MediaConnect Source](docId:0Rppy-L7HX8jHvcsboDbj) - [Adding an SRT-protocol MediaConnect Source](docId\:X9Jogs03ZhS2YNPBDRba1) - [PID Mapping Profile Rules](docId:5C3YqIdkARIo_2fOHpXr8) ## 5 Dec 2025 ### New Documentation - [Comparing Broadcaster and ZEC](docId\:iCJK7jRH5AwzyFcz9dLMh) ## 21 Nov 2025 Documentation for the November 18th ZEN Master Release ### New Documentation - [ZEN Master 18 November 2025 Release Notes](docId:1nkcg7LUZ1XXWJofimd0A) - [Example: API keys with Roles and Tags](docId\:cYC8w6aCVnPbbl7z-lmTN) - [Unknown Status Missing Broadcaster Data](docId\:j-j_qCOhtHdpFcRW2eDJJ) - [Adding a Zixi Source – Broadcaster Pull](docId\:nQWathihsJwRWFWlB1086) - Pull and Push options separated into different docs - [Adding a Zixi Source – Broadcaster Push](docId\:vuNNBbUKYIyBi9EYCRX3C) - [Configuring API Keys](docId\:ZD3XPBLkFoO54qwF2_V4n) - [Paging Through the Events Log](docId\:IfjOdGL2igaBsLXz-1pLq) - [AWS and Zixi](docId\:B_CAPfgyTnyegRTtSssM1) ### Updated Documentation - [Configuring API Keys](docId\:y5VWL7q34grAoPRjlHzuI) - [Actions on Broadcasters](docId\:B1y6nShFZcUwCd0_GSPG-) - [Adding ZEN Master Sources](docId\:FUeKsDqQp0ltvQR-7oAna) - The majority of docs under this topic have been updated for new or changed fields - - [Adding Transcoded Channels](docId\:xwF-mFNvRA5E3jQL2YMjU) - [Targets](docId\:pv_76hSvp7_gsv7DbtamE) - The majority of docs under this topic have been updated for new or changed fields - - [Adding a Live Event](docId\:sFGlqBrA-439CjrUtdUvb) - [Live Event Management](docId\:JepWEEiTXpkrLz1X-YG5D) - [Viewing Thumbnail Grid Display](docId\:AlRDeKalu0zYp5IFvAayO) ## 31 Oct 2025 ### New Documentation - [Target redirected to Broadcaster but no connection - Verify firewall/network Error](docId\:cGUY460bBTkhODiQoh5yT) - Explains what to do in case of an issue with a source or a target that are on different Broadcasters and cannot reconnect after recovery or failover. ## 22 Oct 2025 ### Updated Documentation - [Release Notes: Zixi Broadcaster Version 18](docId\:RadURZyqziy7DJ_BnSPqQ) - Updated for 21 Oct 2025 (v18.8.46391) release - [Creating New Adaptive Groups](docId\:HMeOlyeDX4Lbfu2UFaFru) - Updated for options to positions WebVTT captions ## 17 Oct 2025 ### Updated Documentation - The following documents were updated to add new Error Concealment options (see [Improving Stream Resiliency: Error Correction and Concealment](docId:9_OLo1Argk_2aDoSHYFBb) for details on Error Concealment): - [Adding a Source - PID Mapping](docId\:goCKL3uPsD8V14Ia2an6g) - [Adding a Zixi Source – Broadcaster Push](docId\:vuNNBbUKYIyBi9EYCRX3C) - [Adding a Source – Inter-Cluster](docId\:pTwOaaSXb8HRqk1IcpsQM) - [Adding a Source - UDP/RTP](docId\:QQS-v7Ez6WxAM1NKCHPhS) - [Adding a Source - SRT](docId\:OH8D6MfKC_VxxY12acdYD) - [Adding a Source - RIST](docId\:inYRU5DuaFkA8PvnJQhb1) - [Adding a Source - RTMP](docId\:Nko_WzaJq2ugm9ZA82yOA) - [Adding a Source - HLS](docId\:wkIFT3FbZB62f-6S4Zhbw) - [Adding a Source - Demux](docId\:KXBLpiAlJdiVMwKO5irnW) - [Adding a Source - MPTS Multiplex](docId\:va5SMliAlWmbqxtrCuU99) - [Adding a Source - SPTS Multiplex](docId\:XFlBxEvjE2UD-0UVTnnx7) - The following documents have updates to input fields: - [Adding a Zixi Remote Access Profile](docId\:rtF7QZaDcLf4pFvd4adyb) - [Adding a Videon Remote Access Profile](docId:1k5OEvIUVlf_T19EnF3DL) - [Remote Access](docId\:M0TBH4rz07EDJ4ecnPr00) - [Target Details](docId\:n9nexWogVICzIYQkG6JtP) - [Target History](docId\:gfII56tGhkA_wmNr7n6y7) ## 10 Oct 2025 ### New Documentation - [Improving Stream Resiliency: Error Correction and Concealment](docId:9_OLo1Argk_2aDoSHYFBb) - Explanation of how Error Concealment prevents catastrophic failures downstream, how it is implemented in ZEN Master and Zixi Broadcaster, and how, for Zixi protocol sources, it works with FEC and ARQ to provide maximum stream resiliency ### Updated Documentation - [Adding a Source – Failover](docId\:FzrB10jKuzAinyT8gfNK0) - Added explanation of how to calculate an appropriate value for CBR padding ## 19 Sep 2025 ### New Documentation - [Paging Through the Events Log](docId\:IfjOdGL2igaBsLXz-1pLq) - How to page through the event log using the ZEN Master API ### Updated Documentation - The following docs were updated to provide a clearer explanation of Max Bitrate and advice on setting a value - [Adding SRT Streams](docId:9iaI4hwjF7HSzRj3izhjP) - [Adding RIST Streams](docId\:VCXoTypOgo8NUvTj_itHm) - [Adding RTMP Streams](docId\:oLyKwp4DlKs58dTdWqJSH) - [Adding a Source - SRT](docId\:OH8D6MfKC_VxxY12acdYD) - [Adding a Source - RIST](docId\:inYRU5DuaFkA8PvnJQhb1) ## 12 Sep 2025 ### Updated Documentation - [Release Notes: Zixi Broadcaster Version 18](docId\:RadURZyqziy7DJ_BnSPqQ) - Release notes for Broadcaster v18.7.46333 - [Using High Performance Networking](docId\:UMxCKfeISJluQZUbGEsNI) - All docs in the section updated with detailed explanations and instructions for setting up DPDK ## 29 Aug 2025 ### New Documentation - [ZEN Master 12 August 2025 Release Notes](docId\:NS7OEYQ0K_3ZNva_9GaU3) ### Updated Documentation - [Adding Transcoding Profiles](docId:3L1DNIo6v_15jzCFdhRKN) - Updated for logo insertion - [Adding ZEN Master Sources](docId\:FUeKsDqQp0ltvQR-7oAna) - Many Adding Source documents updated for a new Ignore Monitoring PIDS advanced field, and several to reflect that Frame Thinning is now a checkbox - [High Max Bitrate Configuration](docId\:IJrN4V8zGysjoKXEVCkHx) - Advice on configuring Max Bitrate values for ZEN Master sources or Broadcaster inputs ## 1 Aug 2025 ### New Docmentation - [The Zixi Customer Portal](docId\:xPQ8h_ANgNPKy1OWJORok) - New major section on using the Zixi Customer Portal - [Updating the Broadcaster API Password](docId\:ZLhH8f67VyaRBdiQpwRfg) - Overview of updating the Broadcaster password in the Broadcaster and ZEN Master, and instructions on resetting the Broadcaster password back to its original value if you have forgotten it - [Changing Broadcaster Password in ZEN Master](docId:-QWelOlQPM5YfObN00VFx) - How to update the password for a Broadcaster in Zen Master ### Updated Documentation - [Adding a Broadcaster to a Manual Cluster](docId\:xYscySO498lY77ZjQr-51) - Adding missing steps on entering the API user/password and selecting an SSH key - [Broadcaster V18](docId\:AD1Aw8R3QG7FrRPWAhS_A) - Updated required CUDA version ## 11 July 2025 ### New Documentation - [Creating a Failover Source](docId\:MHuREa_mcoKgXw1fGEd4Q) - Create a failover source using the ZEN Master API with Postman - [Release Notes: Zixi Broadcaster Version 18](docId\:RadURZyqziy7DJ_BnSPqQ) - New features and improvements for all v18 releases - [Release Notes: Zixi Broadcaster Version 17](docId\:IHwLuSOxOiGEgAe2eYemP) - New features and improvements for all v78 releases ## 4 July 2025 ### New Documentation - [Creating a Source, Channel, and Target](docId\:fCx7vkZ9lRRzW06WoKM-5) - Get started with the ZEN Master API by creating a source, channel, and target both by using Postman and using a Python script ### Updated Documentation - [Step 2 - Getting Started with Postman](https://docs.zixi.com/zen-master-api/step-2-getting-started-with-postman) - Updated steps to reflect best practices for saving Postman variables ## 27 June 2025 ### Updated Documentation - [Zixi Market Switching: ESAM Agent and ESNI Decisioning Service](docId\:caWN1TaxQsKVDi5jd757v) - Updated this section to include documentation for the [ESNI Decisioning User Guide](docId\:CCfonhvyBRYgOQUpZcPGX) - Added a [Zixi Market Switching: ESAM Agent and ESNI Decisioning Service](docId\:caWN1TaxQsKVDi5jd757v) ## 13 June 2025 ### New Documentation - [Zixi Documentation Center](docId:7jkqG2mAspDmKkS96SxFQ) - Steamlined and simplified the home page to make it easier to get to where you want to go. - [Zixi Product Updates](docId\:CEEsbcsNF9Wl90xSmMaJk) - Here we will list all Zixi product updates, with release notes. - [Zixi Documentation Updates](docId\:cZ5gyTJ3lI7X0ps4LGDAl) (this page) - Here we will list all updates to Zixi Documentation every week or two. - [ESNI Decisioning User Guide](docId:34bOG9SHeByXaZZJ846f0) - ESNI (Event Scheduling and Notification Interface) is a framework that manages and automates event-based switching and feed distribution across IP networks. Zixi utilizes ESNI coordinates when and where specific video feeds are delivered. The ESNI service is a paid add-on to ZEN Master. - [Zixi Market Switching: ESAM Agent and ESNI Decisioning Service](docId\:caWN1TaxQsKVDi5jd757v) - The Zixi ESAM Agent is an additional software installation on the server hosting a Zixi Broadcaster that adds two key feature sets: 1. The ability to interface with & act on an **externally hosted** scheduling service such as ESNI (SCTE 224) using SCTE 35 messages or based on wall clock time 2. The ability to interface with & act on an **externally hosted** POIS (SCTE 130 part 5) SCTE manipulation or conditioning service. - [Broadcaster - Errors and Troubleshooting](docId\:HUi-CQDzF218zY6PB1o9W) - Common Broadcaster errors explained, with guidance on how to resolve them. - [ZEN Master - Errors and Troubleshooting](docId\:CYHMfI_-M9ldX5aSfojSN) - Commone ZEN Master errors explained, with guidance on how to resolve them. ### Updated Documentation - [Appendix A - dockerfile\_zixi\_broadcaster.txt](docId\:YAQUfpaEkt86Hk7EUu-Df) - Updated the Docker file used to build the Docker image. - [Zixi Quick Start](docId:714kqnMSrshVBcXMJ6CZr) - Quick Start Guide updated to reflect current product features. [title] Zixi Documentation Center [path] / | :inlineImage[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/_792ueXBzuejrFoesjUGq_quick-start-smaller.png" alt caption}
[Zixi Quick Start](docId:714kqnMSrshVBcXMJ6CZr)
| :inlineImage[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/xJE0OfYO_Yl0fReLG6nex_product-features-smaller.png" alt caption}
[Product Features](docId\:z_dtgHik2QLXoazGTzwQh)
| :inlineImage[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/4632MSoFbbweknOXGCCzw_bx-smaller.png" alt caption}
[Zixi Broadcaster/ZEC](docId\:vqtUe3_40jdNjQL5ExR8c)
| | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | :inlineImage[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/pn7tAtjWQSh9y7i1RAyYq_zm-smaller.png" alt caption}
[ZEN Master](docId\:FG4D7DmllMvvFWAxtGNE2)
| :inlineImage[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/vPRZ3yl8_Q-LxrIfw1qA__zaas-smaller.png" alt caption}
[ZaaS (Zixi-as-a-Service)](docId\:S2xKLFIx_f00qC3f6v5Nn)
| :inlineImage[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/yKsRR2H-Kr1j6-usBsJpK_zms-smaller.png" alt caption}
[Zixi Market Switching](docId\:caWN1TaxQsKVDi5jd757v)
| | :inlineImage[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/le9sXdS7lxz8xnDRc69lh_how-to-smaller.png" alt caption}
[Zixi How To Guides](docId\:pfK0En_5IZ_fx41dRlMpX)
| :inlineImage[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/pn7tAtjWQSh9y7i1RAyYq_zm-smaller.png" alt caption}
[ZEN Master API](docId\:SafxBsM3wuvfg1NwpeAau) | :inlineImage[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/spYgWlSzkRDz8fyrTyUC1_troublehooting-smaller.png" alt caption}
[Troubleshooting](docId:8fgk_ka5EQ71jMUusAZbS) | | :inlineImage[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/gvGjBYWG3jC5XkwU4-FR5_portal-smaller.png" alt caption}
[The Zixi Customer Portal](docId\:xPQ8h_ANgNPKy1OWJORok) | :inlineImage[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/otFZAHWOIy-lznTTRnGin_doc-updates-smaller.png" alt caption}
[Zixi Product Updates](docId\:CEEsbcsNF9Wl90xSmMaJk) | :inlineImage[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/0tlFZau5F0YqGcFQ2vNJ4_zixi-doc-updates-smaller.png" alt caption}
[Documentation Updates](docId\:cZ5gyTJ3lI7X0ps4LGDAl) | *** [title] ZEN MASTER November 2021 RELEASE NOTES [path] Zixi Product Updates/Zixi ZEN Master Release Notes/ The following updates will be included in the ZEN Master November 30, 2021 release. Features The following new features were implemented in this release: • Added ability to define and view Incidents on Channels in ZEN Master. An Incident is defined by a user selected time range and includes time/user-stamped notes. The Incident view allows the user to select or “pin” multiple history graphs and event logs for objects in the Channel and view them together on a single page synchronized to the time range for the incident. The Channel diagram is displayed as well on the same page. An example is shown below. • Added diagrams to Sources, Feeders, and Receivers. Channels and Targets included diagrams previously. • Added ability to create MediaConnect Sources from Elemental Link encoder devices • Added support for failover based on TR-101 and CQA errors. Previously, the user could specify parameters for a rule for zero bitrate streams to trigger a switch to another Source in a good state. Now the rules for that failover are expanded to include TR-101 P1 transport errors, Frozen Video, Blank Picture, and Silent Audio. This feature applies to non-identical Sources merged hitless failover is not in being used. Broadcaster v15.0 is required. Additional Improvements The following additional improvements were implemented in this release: • Added support for Broadcaster v15 transcoding updates to NVIDIA CUDA 11.4 and driver version 470. • Added support for HRD buffer fractions in the transcoding profile • Improved DTLS redirection support • Added sticky multi-selection after an operation such as enable/disable or mute/unmute • Added UDP send errors to Target graphs for UDP, Zixi Pull, and Zixi Push • Added Disk usage column to Broadcaster list in Broadcaster cluster • Added a Broadcaster "restart required" confirmation when applying Broadcaster configuration that will require a restart that results in a stream interruption • Clarified status display of AWS Broadcasters terminated by AWS • Updated list of supported AWS regions to include recently added regions • Added disable checkbox for Source - Analysis - TR101 P2 in Event Profiles • Added an alert when a Source is connected to the wrong Broadcaster in the same cluster Bug Fixes The following issues were resolved: • Fixed RIST targets not configured correctly on Broadcasters • Fixed issue creating Broadcaster Sources with manual bonding • Fixed issue with Broadcaster losing virtual GPU after GCP maintenance event • Fixed an issue causing ZEN Master to try to create redundant Target configs on the same Broadcaster • Fixed intercluster Sources requiring a restart after an edit to apply the new configuration • Fixed ‘Sources Create’ API endpoint requiring that an Event Profile to be specified • Fixed AWS Broadcasters launching with no name • Fixed DNS redirect issue with SRT Targets • Fixed issue with being unable to disable MediaConnect Channels using Automation • Fixed issue with Broadcaster restarting unnecessarily when applying Broadcaster configuration • Fixed an issue preventing Broadcaster GPU usage from showing up in the Broadcasters table • Fixed issue with not reporting SCTE-35 messages with UPID 0 "Not Used" • Fixed issue with not cleaning up no longer required auto-pulls • Fixed issue incorrectly configuring PID Mapping in some edge cases • Fixed UI issues with PID Mapping Match PCR to Video PID [title] Release Notes: Zixi Broadcaster Version 19 [path] Zixi Product Updates/Zixi Broadcaster Release Notes/ # Zixi Platform V19 Release Notes Version 19 (v19.2.47061) of the Zixi Broadcaster and Zixi Edge Compute is now a Generally Available (GA) release and includes the following new capabilities, bug fixes, and security updates. :::BlockQuote **Note:** Not all features are available in Zixi Edge Compute. ::: ## V19.2.47061 Release Notes ### Improvements - Added #EXT-X-CUE-OUT-CONT tags to HLS adaptive output manifests on each segment during SCTE-35 ad breaks - Added a "Reject unencrypted stream" option for Zixi Push and Pull inputs with decryption enabled, so unencrypted streams are dropped and reported as an error instead of being passed through unencrypted - Removed the 60-segment limitation on HLS adaptive output playlists, enabling long sliding DVR windows - Fixed an issue where a Zixi Pull input with slow or failing DNS resolution caused receive errors and packet loss on other inputs; DNS resolution is now asynchronous ### Security - Fixed an issue where the connection handshake was sent unencrypted when a Zixi Pull input or Push output reconnected after being redirected to another node; the encryption key exchange is now repeated on every such reconnect - Hardened validation of SMPTE 2022-1 FEC and HEVC stream data, and of failover search window values supplied over the admin API, against malformed or malicious input ### Bug Fixes - Fixed an issue where the transcoder was stuck at 0 bitrate when the upstream source introduced additional PIDs, such as a failover to or from a slate - Fixed an issue in Error Concealment where audio PES packets were removed indefinitely after a switch - Fixed an issue where a spurious discontinuity tag was added to HLS output when a stream's timestamp was not yet initialized - Fixed an issue where SCTE-35 packets were dropped on Remux-enabled HLS inputs; the remuxer now drains SCTE-35 packets when a timeline jump is detected - Fixed an issue where a no-merge Failover Group reported continuity (CC) errors and packet loss that were not present on its component streams when the Broadcaster briefly stalled, for example on hosts with many offline Pull inputs (drafted - Jira text says TBD) - Reduced the startup delay of the Broadcaster monitoring agent from 30-60 seconds to 15-25 seconds, shortening the gap in ZEN Master statistics after the agent restarts and reducing false "missing broadcaster data" alerts - Fixed an issue where bonded input statistics read incorrectly after a stats reset - Fixed an issue where interlaced field order was lost when transcoding to MPEG-2 with a resolution change, which could cause combing or judder downstream - An MPEG-2 video profile set to interlaced output on a progressive source now fails the transcoded input with the error "Interlaced output from a progressive source is not supported", instead of silently ignoring the setting - Fixed an issue where SCTE-35 marker reporting stopped permanently on an input after a corrupted PMT followed by a stream discontinuity or reconnect - Fixed an issue where editing a component's priority in a no-merge Failover Group briefly dropped the group to a lower-priority input; priority edits are now applied seamlessly - Fixed an issue where SRT inputs and outputs offered an SRT version that was not installed, leaving the stream offline with a "Failed to load library" error - Fixed an issue where the Broadcaster did not exit on restart on older Linux distributions (CentOS/RHEL 7), preventing it from being relaunched automatically - Fixed thumbnail extraction for H.264 streams with I-frames only (no IDR) - Fixed an issue where transcoded audio went silent for the rest of the session when the AC-3 source changed its channel layout or sample rate mid-stream - Fixed corrupted, sheared video when transcoding vertical (9:16) sources with an HTML overlay ("Dynamic Overlay URL"), and corrected the overlay size when cropping is applied to the transcoded input - Fixed an issue where a SMPTE 2022-7 hitless Failover Group permanently lost one of its legs when the group's components were edited while both legs had no traffic, which left the group running unprotected while it still showed Connected - Fixed an issue where several CPU transcodes with an HTML overlay on the same input degraded (low frame rate, bitrate below target, transcoder resets) even though the server had spare CPU - Fixed an issue where a Zixi Push output stayed offline after a seamless redirect to another input made while the output was still connecting ### API Updates - **Inputs (Zixi Push/Pull):** new enforce\_decryption (0/1, default 0) on add\_stream.json / edit\_stream.json; returned by get\_stream\_settings.json; rejecting inputs report error\_code 35 "Encryption mismatch" in streams.json; config key \ - **Adaptive Outputs:** hls\_chunk\_count accepts values above 60 - **Adaptive Outputs:** scte\_type accepts new values for CUE-OUT-CONT tag variants - **Adaptive Outputs (manifest):** EXT-X-DATERANGE ad ranges now carry PLANNED-DURATION on CUE-OUT and END-DATE/DURATION on CUE-IN; #EXT-X-CUE-IN is emitted for auto-return breaks - **Error text:** "Data is encrypted" renamed to "Encryption mismatch" on inputs and outputs ## V19.1.46978 Release Notes ### Improvements - Updated SCTE-35 reporting to ZEN Master to report all SCTE PIDs, adding support for multiple SCTE PIDs per stream - Added support for multiple SRT Listener inputs on the same port - Added the capability to set the temporary directory used when executing a Broadcaster upgrade - Improved performance of HLS inputs by updating pacing strategy, preventing 0 kbps bitrate drops - Added "Time Left" value, measuring duration of data left in the buffer in milliseconds, to the Push and Pull stats graph and API ### Bug Fixes - Fixed an issue where the transcoder did not align GOP with the source when "Copy GOP from source" was selected (change in behavior since 18.9) - Fixed an Error Concealment edge case where a video splice was not detected but an audio splice was, when returning to the original source - Fixed an issue in Error Concealment where audio PES packets were removed indefinitely after a switch, causing audio corruption - Fixed an issue where HLS input CUE-to-SCTE-35 conversion did not log splice direction (In/Out of Network) in ZEN Master after upgrading to v19 - Fixed a condition that caused Error Concealment to continuously report false detections of timeline jumps (false splice detection) - Fixed an issue in Error Concealment where audio frames were dropped for 2 seconds during a switch when concatenating EC output to another EC input - Fixed SRT Listener ZEN Target creation via the Broadcaster API to default "Verify Stream ID" to disabled on the corresponding SRT Listener input and output - Fixed an issue where an injected clip played from a PCR-derived offset instead of from the start - Fixed an issue where input statistics counters latched to zero after a stats reset on bonded streams - Fixed Seamless Switch to wait for the current audio frame to complete before switching sources, so the last audio packet before a switch is no longer truncated ## V19.0.46942 Release Notes ### Security Update: SRT Library Vulnerabilities (July 2026) Zixi has identified and addressed two critical vulnerabilities in the open-source libSRT library used by the Zixi Broadcaster product. Patched versions are available now. **Affected Vulnerabilities**CVESeverityDescriptionCVE-2026-55869CriticalHeap-based buffer overflow in KMREQ handling, enabling denial of serviceCVE-2026-55868CriticalEncryption state machine downgrade, enabling remote encryption bypass | | | - | | | | | **Impact** These vulnerabilities exist in all previously released versions of the SRT library and affect the SRT protocol integration within Zixi Broadcaster. The Zixi protocol and all other protocols supported by the Zixi platform are not affected. **Resolution** Within 24 hours of the official libSRT patch (v1.5.6) released on July 20, 2026, Zixi shipped updated Broadcaster builds that incorporate the fix: - Zixi Broadcaster v19.0.46942 (re-release) **Required Action** - If you are running v19 of Zixi Broadcaster, download the latest v19 release from the customer portal, then upgrade via the Broadcaster UI. These vulnerabilities affect all prior versions of the libSRT library and may impact other vendor products that incorporate SRT capabilities. The Zixi protocol and other protocols supported by the Zixi platform are unaffected by these vulnerabilities. ## V19.0.46908 Release Notes ### Time Addressable Media Store (TAMS) Time Addressable Media Store. It enables broadcasters to store live streams as time-stamped segments, allowing precise access to any point in the content timeline. This capability supports real-time clipping, editing, compliance recording, and fast syndication without rendering or file transfers. Broadcaster v19 integrates with TAMS via APIs for segment upload and metadata handling, ensuring seamless workflows within the Zixi ecosystem. This architecture simplifies orchestration by using API-driven segment uploads and metadata, ensuring efficient and scalable workflows for live and near-live content. ### SPTS Multiplexing SPTS Multiplex (Single Program Transport Stream Multiplexing) allows combining selected PIDs from multiple SPTS sources into a single output stream. This feature enables flexible audio/video pairing and PID mapping without requiring external multiplexing hardware. Broadcaster v19 integrates this capability natively, with configuration via ZEN Master or API, supporting PID selection and remapping for precise stream control. By consolidating multiple feeds into one managed stream, SPTS Multiplex reduces infrastructure complexity and operational costs. ### Zero Latency Frame Thinning Zero Latency Frame Thinning is a feature in Broadcaster v19 that dynamically and gracefully reduces video frame rate under constrained network conditions without introducing additional latency or disrupting stream continuity. It selectively drops non-essential frames while preserving audio and key frames, ensuring uninterrupted delivery for critical live workflows. Broadcasters gain maximum resilience and cost efficiency by avoiding stream interruptions during extreme network fluctuations without deploying extra hardware or redundant paths when not feasible. ### NETINT VPU Support NETINT VPU (Video Processing Unit) integration in Broadcaster v19 enables ASIC-based hardware acceleration for high-density transcoding. These VPUs deliver ultra-efficient encoding for HEVC, H.264, supporting up to dozens of HD streams per card at a fraction of the power and cost of GPU or CPU-based solutions. Broadcaster v19 supports NETINT VPUs natively, allowing seamless deployment on-prem or in cloud environments. Broadcaster v19 with NETINT integration reduces CAPEX and OPEX significantly, lowering hardware footprint and energy consumption while scaling transcoding capacity for live workflows. ### HLS Normalization HLS Normalization in Broadcaster v19 ensures consistent, broadcast-grade transport streams from HLS inputs by repairing timeline irregularities (PCR, PTS, DTS), re-multiplexing segments, and cleaning SCTE-35 markers. This feature addresses issues introduced by upstream encoders or stitched HLS workflows, enabling predictable downstream delivery for contribution, distribution, and playout. This feature removes the need for costly preprocessing containers or third-party normalization tools, reducing infrastructure complexity and operational overhead. ### Protocol Updates Listed below are improvements and bug fixes to the various protocols supported by the Zixi Broadcaster. - **SRT:** Added SRT library version selection for SRT sources and targets, enabling operators to select between SRT library versions - **HLS:** Added #EXT-X-MEDIA tag for language metadata in HLS manifest output - **SCTE-35:** Added support for SCTE insertion on Failover Groups ### Transcoding Updates - Note the updates on the v19 Transcoding datasheet. - Updated Broadcaster to upscale CEF output beyond 1080 for up to 4K output - Updated Transcoder to support Software HEVC decode and encode of 422 10-bit content with CEF for HTML Overlays ### Additional Improvements Additional improvements to the Zixi Broadcaster are listed below. - Added the ability to individually enable logging on a per stream basis in the Broadcaster - Updated API of HLS Input to return the number of Continuity Counters within a segment - Added Frame Thinning with zero latency capability to HEVC streams - Added support for JPEGXS metadata into the TR101 Analyzer. - Added to TR101 Analyzer graphs of Frame Duration min/max/avg Elementary Stream values and deltas in the TR101 Dialog box - Added ability to validate JPEG-XS metadata to TR101 Analyzer - Optimized output flows to support higher bitrates without causing overflow errors - Increased the maximum allowable bitrate to 1Gbps in UDP and ASI inputs - Added support for Fastly Object Store as an HTTP Output and Recording Input target. - Added HLS Tag Metadata Passthrough, enabling end-to-end pass-through of #EXT-X-ASSET and #EXT-X-PROGRAM-DATE-TIME manifest tags through the HLS-to-TS-to-HLS pipeline - Improved Error Concealment to remove audio packets between splice point and first audio PES, preventing audio artifacts on stream switches ### API Updates Updates to API calls in the Zixi Broadcaster are listed below. **API Parameter Changes** - **SCTE-35:** Replaced keep\_scte\_null parameter with new support\_scte\_timeout timeout parameter for SCTE injection. Stream type is now auto-detected -- CBR inserts on null with timeout, VBR inserts immediately - **Failover Group:** Added assume\_identical parameter (\[0/1]) to Failover Group API to bypass stream comparison for Hitless Merge, improving performance **New Feature APIs** - **TAMS:** Added vuuid (video flow UUID) and auuid (audio flow UUID) parameters to /zixi/set\_adaptive\_channel\_with\_streams.json for TAMS integration. OAuth Token URL, Client ID, Client Secret, Grant Type, and Scope are configurable via API - **SPTS Multiplex:** New PID Interleaver source type with API parameters for primary\_source, PID selection and remapping via comma-separated source/target PID pairs. Configurable via API, UI, and ZEN Master - **SRT:** Added SRT library version selection parameter for SRT sources and targets, allowing operators to choose between SRT library versions **New API Response Fields** - **Stats:** Subtitle descriptors are now included in streams.json API response when present ## V19.1.46978 Release Notes ### Improvements • Updated SCTE-35 reporting to ZEN Master to report all SCTE PIDs, adding support for multiple SCTE PIDs per stream • Added support for multiple SRT Listener inputs on the same port • Added the capability to set the temporary directory used when executing a Broadcaster upgrade • Improved performance of HLS inputs by updating pacing strategy, preventing 0 kbps bitrate drops • Added “Time Left” value, measuring duration of data left in the buffer in milliseconds, to the Push and Pull stats graph and API ## V19.0 Release Notes # Time Addressable Media Store (TAMS) Time Addressable Media Store. It enables broadcasters to store live streams as time-stamped segments, allowing precise access to any point in the content timeline. This capability supports real-time clipping, editing, compliance recording, and fast syndication without rendering or file transfers. Broadcaster v19 integrates with TAMS via APIs for segment upload and metadata handling, ensuring seamless workflows within the Zixi ecosystem. This architecture simplifies orchestration by using API-driven segment uploads and metadata, ensuring efficient and scalable workflows for live and near-live content. # SPTS Multiplexing SPTS Multiplex (Single Program Transport Stream Multiplexing) allows combining selected PIDs from multiple SPTS sources into a single output stream. This feature enables flexible audio/video pairing and PID mapping without requiring external multiplexing hardware. Broadcaster v19 integrates this capability natively, with configuration via ZEN Master or API, supporting PID selection and remapping for precise stream control. By consolidating multiple feeds into one managed stream, SPTS Multiplex reduces infrastructure complexity and operational costs. # Zero Latency Frame Thinning Zero Latency Frame Thinning is a feature in Broadcaster v19 that dynamically and gracefully reduces video frame rate under constrained network conditions **without introducing additional latency or disrupting stream continuity**. It selectively drops non-essential frames while preserving audio and key frames, ensuring uninterrupted delivery for critical live workflows. Broadcasters gain maximum **resilience and cost efficiency** by avoiding stream interruptions during extreme network fluctuations without deploying extra hardware or redundant paths when not feasible. # NETINT VPU Support NETINT VPU (Video Processing Unit) integration in Broadcaster v19 enables **ASIC-based hardware acceleration for high-density transcoding**. These VPUs deliver ultra-efficient encoding for HEVC, H.264, supporting up to dozens of HD streams per card at a fraction of the power and cost of GPU or CPU-based solutions. Broadcaster v19 supports NETINT VPUs natively, allowing seamless deployment on-prem or in cloud environments. Broadcaster v19 with NETINT integration **reduces CAPEX and OPEX significantly**, lowering hardware footprint and energy consumption while scaling transcoding capacity for live workflows. # HLS Normalization HLS Normalization in Broadcaster v19 ensures consistent, broadcast-grade transport streams from HLS inputs by repairing timeline irregularities (PCR, PTS, DTS), re-multiplexing segments, and cleaning SCTE-35 markers. This feature addresses issues introduced by upstream encoders or stitched HLS workflows, enabling predictable downstream delivery for contribution, distribution, and playout. This feature removes the need for costly preprocessing containers or third-party normalization tools, reducing infrastructure complexity and operational overhead. # Protocol Updates Listed below are improvements and bug fixes to the various protocols supported by the Zixi Broadcaster. - SRT: Added SRT library version selection for SRT sources and targets, enabling operators to select between SRT library versions. - HLS: Added #EXT-X-MEDIA tag for language metadata in HLS manifest output. - SCTE-35: Added support for SCTE insertion on Failover Groups. # Transcoding Updates - Note the updates on the v19 Transcoding datasheet. - Updated Broadcaster to upscale CEF output beyond 1080 for up to 4K output. - Updated Transcoder to support Software HEVC decode and encode of 422 10-bit content with CEF for HTML Overlays. # Additional Improvements Additional improvements to the Zixi Broadcaster are listed below. - Added the ability to individually enable logging on a per stream basis in the Broadcaster. - Updated API of HLS Input to return the number of Continuity Counters within a segment. - Added Frame Thinning with zero latency capability to HEVC streams. - Added support for JPEGXS metadata into the TR101 Analyzer. - Added to TR101 Analyzer graphs of Frame Duration min/max/avg Elementary Stream values and deltas in the TR101 Dialog box. - Added “Time Left” value, measuring duration of data left in the buffer in milliseconds, to the Push and Pull stats graph and API. - Added ability to validate JPEG-XS metadata to TR101 Analyzer - Optimized output flows to support higher bitrates without causing overflow errors. - Increased the maximum allowable bitrate to 1Gbps in UDP and ASI inputs. - Improved Error Concealment to remove audio packets between splice point and first audio PES, preventing audio artifacts on stream switches. - Added support for Fastly Object Store as an HTTP Output and Recording Input target. # API Updates Updates to API calls in the Zixi Broadcaster are listed below. **API Parameter Changes** - SCTE-35: Replaced 'keep\_scte\_null' parameter with new 'support\_scte\_timeout' timeout parameter for SCTE injection. Stream type is now auto-detected -- CBR inserts on null with timeout, VBR inserts immediately. - Failover Group: Added 'assume\_identical' parameter (\[0/1]) to Failover Group API to bypass stream comparison for Hitless Merge, improving performance. **New Feature APIs** - TAMS: Added 'vuuid' (video flow UUID) and 'auuid' (audio flow UUID) parameters to /zixi/set\_adaptive\_channel\_with\_streams.json for TAMS integration. OAuth Token URL, Client ID, Client Secret, Grant Type, and Scope is configurable via API. - SPTS Multiplex: New PID Interleaver source type with API parameters for 'primary\_source', PID selection and remapping via comma-separated source/target PID pairs. Configurable via API, UI, and ZEN Master. - SRT: Added SRT library version selection parameter for SRT sources and targets, allowing operators to choose between SRT library versions. **New API Response Fields** - Stats: Subtitle descriptors are now included in streams.json API response when present [space] Announcements (/announcements) [title] Action required: API keys expire on 18 November 2026 [path] Untitled/ Some of the API keys on your ZEN Master account are due to expire at 16:29 UTC on 18 November 2026. Any script, dashboard or integration still using one of those keys will start getting authentication failures from that point, so please create replacement keys before the deadline. ### Why this is happening In November 2025 we introduced a maximum lifetime of one year for ZEN Master API keys. This limits how long a key remains usable if it is ever exposed, and it makes sure keys are reviewed and rotated on a regular basis rather than living indefinitely. Keys that already existed when the change went in were given an expiry date one year out, which is why a number of them land on the same date. ### How to check which of your keys are affected 1. Log in to ZEN Master as a user with admin rights. 2. Go to the API Keys page in your account settings. 3. Look at the expiry date for each key. Any key showing 18 November 2026 needs replacing. ### How to create a replacement key 1. On the API Keys page, choose the option to add a new API key. 2. Give it a name that identifies where it is used, for example "automation" or "scheduler". This matters later when you need to work out what a key belongs to. 3. Set the permissions to match what the integration actually needs. Choose read only where the integration only reads data, and assign a specific role and tag rather than full admin access wherever you can. 4. Set the expiry date. The maximum is one year from the date you create the key. 5. Save the key and copy the key value immediately. ZEN Master shows it once and cannot display it again afterwards. 6. Update your integration or script with the new key and confirm it works. 7. Once the new key is confirmed working, delete the old key. ### Points worth noting - Creating a new key has no effect on the existing one, so you can run both side by side while you cut over and there is no need for an outage. - An API key authenticates in its own right and is not tied to a user account, so it keeps working after the person who created it has left. Deleting the key is the only way to revoke that access. - Put a calendar reminder in place ahead of the new expiry date so the next renewal does not come as a surprise. If you are not sure where a key is being used, or you would like us to confirm which keys are affected on your account, please contact Zixi Support and we will help. [title] Announcements [path] / [space] Customer Portal (/customer-portal) [title] Documentation Section [path] The Zixi Customer Portal/ ![Documentation Section](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-KHkr_0iM4WHDPLpMw8FNW-20250722-191502.png) ## By Type The Documentation section is organized mainly by product - in some cases you will see links directing you back into other sections of the Zixi Documentation that you are currently looking at. In other cases there are PDF files that can be downloaded. There is also a sample transport stream you can use for testing. :::hint{type="info"} Note that your browser may be equipped or have an extension to display PDFs, in which case PDF documents will open in a new tab rather than download. In that case you can still download it from the new tab if you want a local copy. ![PDF Viewed in Browser](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-8gbvAhsNeVEUqWiBiQkO3-20250731-191903.png) ::: On the **By Type** tab, you can filter by product or documentation type, much as you can in the **Software** section. :::hint{type="info"} Note that what appears here will depend on what you subscribed to in the [Packages Section](docId\:FJ0-uTQaJnqAq9BxKUY3G). ::: ## Table ![Documentation Table View](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-ueob3tmRbw_K2kpQD5JTn-20250731-192852.png) You can also view the documentation in a more compact **Table **view**. **There is no filtering in this view, but you can select the number of rows to view on a page. [title] Partners Section [path] The Zixi Customer Portal/ ![Partners Section](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-wRnbHhwNCvl4yxTMPDKA2-20250728-194944.png) The Partners section provides information on Zixi partners that provide services and tools that can enhance your overall streaming video service by providing such things as encoders and decoders, ad insertion, and analytics beyond the scope of Zixi's services. [title] License Keys Section [path] The Zixi Customer Portal/ ![License Key Section](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-guCfZynj_jKWO2jrYUlbr-20250729-191339.png) The **License Keys** section of the the Portal allows to create or register the license keys that enable Zixi products like Zixi Broadcaster and ZEC, or Zixi-enabled products like AWS MediaConnect, to operate in a Zixi media topology. There are a limited number of license key types that you can create yourself - depending on how your account is set up - but you can also register keys created and given to you by someone at Zixi. Let's go through the options in the UI. At the very top you will see a button to **Register Keys** (one or more), which opens this dialog: ![Register License Keys](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-ZTfZeE8-Om16uKh6TNw32-20250729-134233.png) Here you can enter license keys given to you, followed by a label that will help you to identify them. You may not need to perform this step, as in many cases your contact at Zixi who creates the keys will go ahead and register them to your account. ## Registering Keys Moving down the page, you next come to the buttons that allow you to generate certain types of keys yourself. When you click one, the key will be generated immediately, and displayed to you in a notifcation that provides other information, such as the expiration date: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI--uydrLMrUSzxHg_gJsYmJ-20250729-135104.png" size="62" width="1004" height="688" position="center" alt="License Key Creation Notification" showCaption="false"} ## Viewing Keys and Editing Labels After keys are registered by you or someone at Zixi, they will appear in a table on the page: ![Table of License Keys](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-QSRV2awe0V85-54SWa1rh-20250729-143521.png) Note the **Update Labels** button above the table that allows you change the label to better remember what the key is used for. ![Edit License Key Labels](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-qXceMf4zjPu5rw4emJVyg-20250729-144919.png) Don't forget to click **Save Changes** after editing labels. ## Viewing License Key Details You can click the copy icon to the right of a license string to copy it to your clipboard and paste it into an activation dialog. Note the the license string is also a clickable link that will details about the license - essentially the same screen you see after creating a new license, but with more information if the license has been used: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-zsL_tk7xs4qQQdaFmYxou-20250729-182250.png" size="68" width="1080" height="934" position="center" alt="License Key Details - Info" showCaption="false"} ### Activations ![License Key Activations](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-XPu7lknhteiPcuiMklUGQ-20250729-182946.png) Note that you can click on or hover over any Host ID in the list to get information about the activated system: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-LjTmFUcmi1FbEDcgV2OOv-20250729-183555.png" size="64" width="956" height="694" position="center" alt="License Key Activated System Info" showCaption="false"} The **Active** tab shows you a similar table, but only showing systems active with the past 7 days. ### Features The **Features** tab shows which features are activated for the key: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-0jajCjYXnHTPfDdUJbG1f-20250729-190311.png" size="62" width="1066" height="1464" position="center" alt="License Key Features" showCaption="false"} ### Traffic Finally, the **Traffic** tab shows you data in and out of the systems using this license, with several options at the top for viewing the data in different ways: ![License Key Traffic](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-DvAnEeFVVanD_yWMoX9hU-20250729-191127.png) [title] Packages Section [path] The Zixi Customer Portal/ ![Packages Section](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-FMR2maXSnUqZiQ-jP7cjn-20250729-195046.png) In the **Packages** section, you can subscribe to (or unsubscribe from) software packages. This will control what items you see in the **Software** and **Documentation** sections. If you think packages should be available to you that are not available, contact your Account Manager, Technical Account Manager, or Customer Success contact. [title] Notifications Section [path] The Zixi Customer Portal/ ![Notifications Section](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-c0IGgV9_E8zH3UcYCvqco-20250729-201332.png) The **Notifications** section allows you to subscribe and time notifications on many crucial aspects of your Zixi account. Get notified when a license key is nearing expiration, when you're approaching maximum or projected usage of data transfer for the key, and many other things. Also note that you can choose to be auto-subscribed to new notifications when we add them. [title] My Settings Section [path] The Zixi Customer Portal/ ![My Settings Section](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-BpuX_wgr5kDosWt6qH31y-20250729-192415.png) In the **My Settings** section, you can view or update your user information in the Zixi Customer Portal. [title] File Sharing Section [path] The Zixi Customer Portal/ ![File Sharing Section](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-HI85x5lMGMazc-8YRaERQ-20250729-191800.png) In the **File Sharing** section, you can send files to or receive them from someone at Zixi. Note, however, that exchanging files through the Portal, typically used to resolve some issue, must be arranged by someone at Zixi. [title] Software Section [path] The Zixi Customer Portal/ ![Software Section](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-r2K3u4sNqi3Ad4kXrFYmV-20250721-191857.png) In the Software Section, you can find and download builds of various software, including Zixi products, plugins, and SDKs, and third-party tools like the VLC player and OBS broadcast studio with plugins to make them work seamlessly with Zixi. There are three different views of software offerings represented by the tabs at the top: - By Type/Product - New Builds - Table :::hint{type="info"} Note that the software that will appear depends on what you subscribe to in the [Packages Section](docId\:FJ0-uTQaJnqAq9BxKUY3G). If you think you should be able to see other packages that are not available for you to subscribe to, contact you Zixi Account Manager, Technical Account Manager, or a Customer Success contact. ::: ## By Type/Product ![Software by Type/Product](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-5TPZD3r1b_Qj_FaCgHOp2-20250731-173930.png) - The **By Type/Product** tab will show you builds for *supported* versions of software. - Where there are multiple releases available, the latest version is always listed at the top, with earlier releases listed in descending order by date. - Note that on the **By Type/Product** tab, you can click on the product filters at the top to only show releases for that one. ### Installers When you click on a release number, you will see a details screen where you can get an installer for different platforms: ![Software Download View](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-fKPtFprVvJNw8YqlRyq3I-20250722-134457.png) ### CLIs In addition to downloadable installers, there are also **CLIs** - commands that you can run from the command line to download the installer. These are intended mainly for cases where you only have SSH access to the system you want to install on. ![CLIs for Installation](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-c33nLzEF-PdFEWqi1LF7B-20250722-134745.png) ## New Builds ![New Builds](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-KATMJtMZa3WymvB4mVxk4-20250731-174449.png) The **New Builds** tab shows the same information and format as the **By Type/Product** tab, and with the same product filters at the top. However, it only shows those build released within the past 30 days. This view is offered as conveniene to those who like to keep their software up to date with the latest versions and features. :::hint{type="info"} If there are any new builds available, this tab will appear first when you go to the **Software** section. ::: ## Table ![Software Table View](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-23v301TdIDoaCFerCkeg--20250731-185114.png) In the **Table** view, you can find older builds in a more compact table. There is no filtering here, but you can choose how many rows to display at once. As in other views, clicking on the release number will take you to a details screen where you can download the installer or get the CLI. [title] The Zixi Customer Portal [path] / ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/gvGjBYWG3jC5XkwU4-FR5_portal-smaller.png) The Zixi Customer Portal is your entry way into Zixi. Here you can download software, manage license keys, set up email notifications, and much more. In these pages, we will look in detail at the different sections of the Portal, beginning with ones you first need to look at if you are new to Zixi. ## Logging In To login to the Customer Portal, go to [https://portal.zixi.com](https://portal.zixi.com): ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-lkqDHuFz4zgRNOB9kun5k-20250720-175837.png" size="50" width="790" height="942" position="center" alt="Portal Login" darkWidth="790" darkHeight="942" showCaption="false"} If you already have an account, enter your email address and password. If not, click **Create Account **to set one up. ## Getting Started If you are new to the Portal, probably these are the first things you want to do: - Go to the [Packages Section](docId\:FJ0-uTQaJnqAq9BxKUY3G) and subscribe to the packages relevant to you (otherwise, nothing will show up in the [Software Section](docId\:ygU6czPaPyNh2k_8fYjUm)) - Go to the [Notifications Section](docId\:prIkvyuI1nqwOErJ7BhLa) to set up email notifications for things like new software releases and expiring license keys ### Topics in this section - [Portal Dashboard](docId\:MSgiAqc6CJw5cAknJvODw) - [Software Section](docId\:ygU6czPaPyNh2k_8fYjUm) - [Documentation Section](docId\:nTui9htt9rAk0JEP7YmUh) - [Partners Section](docId:5-1SEz7XRL-UbS6GLhLS4) - [License Keys Section](docId\:xIskZzwNIZuWKhB966lvn) - [File Sharing Section](docId:-lolEjSrvRQi0H-khaP7d) - [My Settings Section](docId\:srT7IXNueD6SglYpGn0kj) - [Packages Section](docId\:FJ0-uTQaJnqAq9BxKUY3G) - [Notifications Section](docId\:prIkvyuI1nqwOErJ7BhLa) [title] Portal Dashboard [path] The Zixi Customer Portal/ ![Custom Portal Dashboard](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-HaqaMnN3M9dsY9vSF7Myx-20250721-150810.png) The Dashboad is the first page you will see when you login to the Portal (except the first time, when you will be invited to set up Notifications - which you can do then or later). There are four blocks of information on the Dashboard: 1. The lefthand navigation, persistent throughout the Portal, which allows you to quickly get to the section you want. 2. The same links appear in the main part of page, with brief descriptions explaining what you can do in each section. 3. Below the section descriptions is a scrollable list of messages about new software releases, EOL for old versions, recommended actions to improve security, and so forth. 4. Finally, there is a list of the most recent software releases for quick access (you can find all releases in the **Software** section). [space] How To Guides (/how-to-guides) [title] Video and Audio Codec Support Options [path] How to Monitor Streams Using WebRTC Home/ WebRTC stream delivery requires particular audio and video codecs. In case the streams you are transporting via Zixi Broadcaster do not match these requirements, additional transcoding will be necessary in order to re-encode the stream to become WebRTC compliant. The following are the requirements for a Zixi stream to be *WebRTC compliant*: - **Video** - H.264 codec with Baseline or Main profile and no B frames - **Audio** – Opus codec The following is a description of the possible methods for processing streams in Zixi for WebRTC viewing: - **Pass-Through** – if the stream is already fully compliant with WebRTC, then it can be passed through the Zixi Broadcaster to the WebRTC player for viewing. - **Transcoding **– if the incoming stream is not fully compliant, then you need to first transcode the stream in order to prepare it for delivery to the WebRTC player. There are two methods that can be used for transcoding a stream for WebRTC. **Single Version - Creating a single version of the monitor stream for all users** – in this option the stream will be encoded using Zixi Broadcaster's transcoder (with existing X264 or Nvidia for transcoding). This option allows many users to monitor the stream without encoding for each individual user, which saves CPU capacity. However, the option will still require additional output bandwidth for each user. 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. **Multiple Version - Creating a unique version of the monitor stream for each user **– in this option Zixi Broadcaster will transcode 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. In this option the stream will match the bitrate available for every particular user. Although this promises the best quality for users' specific network conditions, each re-encode consumes CPU, which could potentially max out the available CPU resources used to transport the streams. In this case, if the stream will be monitored by a large number of users, it is recommended to host a second Broadcaster and send the stream to the second Broadcaster and have all users monitor the stream from that second Broadcaster.  By doing so, there will be no impact on the primary Broadcaster. | **Input Codec** | **Passthrough** | **Single Version** | **Multiple Version** | | -------------------------------------------------- | ------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- | | **Video Codecs** |   |   |   | | **H.264 with no B-frames (profile Baseline/Main)** | Yes | Not Relevant | Not Relevant | | **H.264 with B-frames** | No | Transcode to WebRTC compliant profile (e.g. H.264 codec with Baseline or Main profile and no B frames). Needs transcoding on a server with Nvidia GPUs. | Transcode to a RAW  profile and specify a low resolution. | | **MPEG2** | No | Transcode to WebRTC compliant profile. Needs transcoding on a server with Nvidia GPUs. | Transcode to a RAW  profile and specify a low resolution. | | **HEVC** | No | Transcode to WebRTC compliant profile. Needs transcoding on a server with Nvidia GPUs. | Transcode to a RAW  profile and specify a low resolution. | | **Audio Codecs** |   |   |   | | **Opus** | Yes | Not Relevant | Not Relevant | | **AAC** | No | Transcode to Opus codec. | Transcode to RAW. | | **AC-3LC / HE v1 / HE v2** | No | Transcode to Opus codec. | Transcode to RAW. | | **MPEG-2 Audio Layer II** | No | Transcode to Opus codec. | Transcode to RAW. | | **MPEG-1 Audio Layer II** | No | Transcode to Opus codec. | Transcode to RAW. | | **E-AC-3 (and other unsupported codecs)** | Not supported. The stream will be passed through to WebRTC without audio. | Not relevant | Not relevant |     [title] Capturing a Live Stream [path] Zixi OnAir Guide (deprecated)/ The following instructions explain how to stream live video using the various protocols. The procedure does not include all the options that are available in the Settings screen. To learn more about all the configuration options, see the [OnAir Settings Screen](docId\:nLLBm2Jjkl5uu2blCJWAL) section. ## Capturing a live stream **To capture a live stream:** 1.In the target **Zixi Broadcaster**, do one of the following: - Create a **Push Input** which will be used to stream from the OnAir app. The details of this input stream will be entered into the OnAir Settings, as described below. - If you don't want to create the Push Input in advance, go to **Settings** **> Live Protocols** and select the **Allow Automatic HTTP Push input **for Zixi streams and** Allow Automatic RTMP Input **for RTMP streams. 2\. In the **Setting Screen**, in the **Protocol** field, select one of the following protocols: - Zixi - RTMP - RIST (iOS) 3\. Specify the target server details: - **For Zixi protocol** – specify the Zixi Broadcaster server name or URL in the **Broadcaster name** field, and **Port** number (default: 2088). - **For RTMP** – specify in the URL field, the Stream URL of the RTMP server. - **For RIST** - specify the Zixi Broadcaster IP address in the **Broadcast address** field, and **Port** number (default: 2088). 4\. Specify the stream details: - **For Zixi protocol** - in the **Channel Name** field, if you have already created a stream in Zixi Broadcaster, specify the stream name. If you enabled the "Allow automatic connection", you can specify any name. - **for RTMP** – specify the stream name in the Stream Name field. 5\. If the stream is protected by a username/password, specify the credentials in the appropriate field to connect to the server. 6\. If you have challenging network conditions, consider combining Wifi and Cellular links by selecting **Bonding** (Android) or **WiFi + Cellular Bonding (iOS).** 7\. Specify the camera that you want to use: - For the device's internal camera, select **Internal** in the **Camera Source** field. - For a USB-attached camera, select **External-USB** in the **Camera Source** field. 8\. Specify additional stream quality-related parameters. 9\. Tap **Save**. You are ready to capture the live video. 10\. On the main screen, tap the **Camera Flip** button to select the front/back camera. 11\. Tap the **Record** (green) button. The button will turn red and after a few seconds the Status bar will indicate the quality of the stream (e.g. Quality 100%). [title] Deployment Requirements [path] Zixi Multicast Deployment Guide/ ## Network and firewall settings The network and firewall settings on your network and on the machine/encoders should be configured to support the following: - Make sure UDP traffic coming to and from the Zixi components is not blocked. - The Zixi Broadcaster machine and external firewall should allow communication on UDP port 2077 (inbound & outbound) and the UDP port used for the multicast transmission (default port – 5000). - For Zixi Broadcaster remote web management, allow TCP 4444 (Zixi Broadcaster GUI) and TCP 22 (SSH remote access). - Make sure multicast is enabled on the network. Zixi supports IGMPv2 and IGMPv3. ## Licensing requirements Zixi Broadcaster should have the "File Transfer" license feature enabled. To ensure it has been enabled go to the Status screen and under License Information, check that the **File Transfer** field is set to "Enabled". ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/0kGuhIgz0sbFEdrN0Ou_k_image.png" size="90" width="995" height="591" position="center" showCaption="false"} [title] Configuring the Input Stream on VLC Player [path] Zixi Multicast Deployment Guide/Configuring the Consumption Segment for Multicast Streaming/ You can test the setup by connecting with another machine in the network using a VLC player that includes the Zixi Plugin. For detailed information about how to install and configure the Zixi VLC plug in, refer to [Installing the VLC Player and the Zixi VLC Plug-In](docId\:xCta6Jsvuk7v69VXPn-dU). **To configure the input stream on VLC Player:** ::::WorkflowBlock :::WorkflowBlockItem In a different computer inside the network install the Zixi VLC Plugin. ::: :::WorkflowBlockItem Open VLC Player. ::: :::WorkflowBlockItem On the **Main Menu**, click **Media**. Sub-menu options are displayed. ::: :::WorkflowBlockItem Click **Open Network Stream**. ::: :::WorkflowBlockItem In the **URL** field, enter a Zixi stream URL, which includes the Zixi Broadcaster details and channel name. You can reference your broadcaster IP or hostname in the Zixi URL. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/yqvbtURMLsreD2hinUydB_image.png" size="80" width="680" height="618" position="center" showCaption="false"} ::: :::WorkflowBlockItem Click **Play**. The stream will be played-back on the VLC player. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/lMxKUcgLE28yGsEflL4Vt_image.png" size="72" width="700" height="558" position="center" showCaption="false"} ::: :::WorkflowBlockItem To view the stream status on the Zixi Broadcaster, go to **Settings > Multicast Pool**. The stream should appear at the bottom of the page. If the multicast streaming was successful, the number of active multicast sessions should be greater than zero. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/StyBV2GdMvZJj1YKkuZW8_image.png" size="90" width="1002" height="494" position="center" showCaption="false"} ::: :::: [title] How to Use Zixi to Transport NDI Over the Public Internet: Introduction [path] How to Use Zixi to Transport NDI Over the Public Internet/ This guide describes how to transport NDI® content over the public internet with very low latency using high quality compression to reduce transport bandwidth requirements. NDI from NewTek lets you transmit and receive broadcast-quality video with very low latency over Gigabit Ethernet networks. With Zixi, NDI can be ingested on the LAN at one location and then compressed to high quality AVC/H.264 or HEVC/H.265 to be delivered to another location over the public internet to any distance, using the reliable, low latency Zixi protocol. Then at the receiving location the stream can be decoded and broadcasted on the local LAN as NDI. While a single 1920×1080\@30 fps NDI stream may require 125 Mbps of bandwidth on the local network, once it is compressed for delivery with Zixi it will only require 10 to 15Mbps using HEVC/H.265 and no perceptible quality loss, to move the stream over the public internet. ## About This Guide This guide demonstrates a basic use case for using Zixi to transport an NDI file over the internet. In this example, an NDI stream is ingested by the Zixi Broadcaster where it is compressed and delivered to another Zixi Broadcaster where the stream is decoded and then broadcasted with no perceptible quality loss. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/U53RpIRKA4EcLqYVrgUgd_image.png) [title] Using HTTPS/SSL for Zixi [path] Zixi Security Best Practices/Configuring the Security Settings after Installation/ Zixi enables secure encrypted communication using HTTPS among the Zixi resources (Feeder, Broadcaster and Receiver) as well as between the resources and oter end-points. In order to enable HTTPS communications, you first need to generate an SSL certificate and Private Key for your secure connections. - [Enabling HTTPS](docId\:qGDhqjs2lX0vJ1_P3Wp5T) [title] Enabling HTTPS [path] Zixi Security Best Practices/Configuring the Security Settings after Installation/Using HTTPS/SSL for Zixi/ :::hint{type="info"} The following procedure describes how to generate an SSL certificate and enable HTTPS for a Zixi Broadcaster. A similar procedure can be used for a Zixi Feeder and a Zixi Receiver.t ::: **To enable HTTPS and upload an SSL certificate:** :::::WorkflowBlock :::WorkflowBlockItem In the Zixi broadcaster navigation, click **Settings**. The Settings page opens showing the **General** tab. ::: :::WorkflowBlockItem In the **General** section, select the **Enable HTTPS administration checkbox**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Jfojed8E1RNdMs7FJCR0k_image.png" size="84" width="1167" height="608" position="center" showCaption="false"} ::: :::WorkflowBlockItem Next to the **HTTPS certificate uploaded** field, click **Upload**. ::: :::WorkflowBlockItem Navigate to your HTTPS certificate file, and click **Open**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/pCIAyCFk8dNUpQQwgro-U_image.png" size="84" width="1232" height="622" position="center" showCaption="false"} ::: :::WorkflowBlockItem Next to **HTTPS private key uploaded** field, click **Upload**. ::: :::WorkflowBlockItem Navigate to your private key file, and click **Open**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/6GJdi4SZdVFU1VZnDZvxC_image.png" size="84" width="1280" height="554" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **HTTPS private key passphrase** field, enter your passphrase, if one exists. ::: :::WorkflowBlockItem Verify that there is a green **Yes** next to both **Upload** buttons. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/fa3QeEhAYNVSZuTOtZZtw_image.png" size="40" width="186" height="76" position="center" showCaption="false"} ::: ::::WorkflowBlockItem Click **Apply**. A confirmation dialog is displayed: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/XznNPo4bojbPvILJ4zfKG_image.png" size="50" width="415" height="191" position="center" showCaption="false"} :::hint{type="info"} Any LIVE or ACTIVE streaming will be affected upon restarting the service. ::: :::: :::WorkflowBlockItem Click **Restart Now** or **Restart Later**. ::: ::::: :::hint{type="success"} If the Broadcaster is registered in ZEN Master, the certificates are managed by ZEN Master. - Locate the broadcaster within ZEN Master - Go to the "Details" tab - Click "Update Broadcaster Configuration" ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/OLwEbhAT3CrvVSTedWUSn_image.png) ::: [title] Zixi VLC Plugin Setup Guide [path] / Zixi offers a special plug-in for the popular VLC Media Player. The plug-in enables high-quality streaming of video/audio TS streams between a Zixi Broadcaster or Zixi Receiver and any PC, running VLC Media Player for error free, buffer free video delivery across any distance . The Zixi VLC Plug-in features Adaptive Bit Rate streaming which dynamically adjusts stream rate to adapt to changing network conditions, multi-format support, and high quality playback with no buffering, jitter, or dropouts. The **VLC Player** can be downloaded from [videolan.org](https://videolan.org) The **Zixi VLC plugin** can be downloaded from the **Software** section of the [Zixi Customer Portal](https://portal.zixi.com) The following setup guide provides instructions on how to install and configure Zixi VLC Plugin as well as operation instructions of VLC Media Player using the VLC Plugin: - [Installation and Setup](docId\:nEOmiNrwkUB0m1yxIoQxI) - [System Requirements](docId:0LrXm-lyEyRSRViagPjJW) - [Installing the VLC Player and the Zixi VLC Plug-In](docId\:xCta6Jsvuk7v69VXPn-dU) - [Zixi Plug-In Preferences Configuration](docId:4BmaH4pd2KPQnWSZqD46x) - [Operation](docId\:aa6up9rsSVRkWqpG_FPYq) - [Playing a Zixi-enabled Stream](docId\:DIr-demIIeWWYzY-uqSE1) - [Playing an Encrypted Zixi Stream](docId\:tCHhgswQT_xoS95FtxyMc) - [Recording a Stream Locally](docId\:EAkhWFigp-bxy0nVldC0n) - [Special Playback Controls for Monitoring Live Video](docId\:b_fvSTIu2tn9UcYn7Bei9) - [Stream Information and Metrics](docId\:j9LMEiE6nJyeRqg6DvOoT) - [Streaming a File to a Local Zixi Feeder or Broadcaster](docId\:x_kdNKw_cSmmdjfzE68VQ) - [Streaming Standard UDP from a Local Zixi Receiver](docId\:pzO4nbmwGsP7KRN2xBwtU) [title] Configuring the Broadcaster [path] Zixi OnAir Guide (deprecated)/Preparing for Use/ In order to stream content from the OnAir app to your broadcaster, you must first configure the broadcaster to receive the input from OnAir. There are two methods for doing this: - [Automatic Method](docId\:MjlT1d1EerFk51Y938QOo)** **- You can enable your broadcaster to automatically accept Push inputs from **any** device that tries accessing the broadcaster. OR - [Manual Method](docId\:UpHLb_U6SdfI9tOcOpdWO) – You can manually configure an Input specifically for your OnAir app. For this method, you will specify a *Stream ID* for the input which you will then enter into the OnAir app's settings (as the *Channel ID*) to identify the incoming stream. :::hint{type="info"} You must have access to a Zixi Broadcaster that is running. If you are activating your broadcaster for the first time, see [Installing Zixi Products](docId\:vr8wIZ4KSRwxSZ52Cx--w). ::: [title] Escalation Rule Example [path] Alert Escalation and Notification Management Guide/The Events Profile/ Consider a healthy Zixi Source that suddenly encounters intermittent packet loss over the course of several minutes, which eventually recovers. Notifications for packet loss, resulting in CC Errors, are controlled by the **“Source – Analysis – TR101 P1 Transport” Rule **of the Event Profile, which is configured as follows: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/IoZRu8OD_SyGpzzt-zyS__image.png) The escalation window is set to 10 minutes and an escalation count of 4 events. According to the rule, notification emails should be sent for both Error and OK states. The resulting behavior of the monitoring system is as follows: ### Scenario One 1. ZEN Master checks the source. The source is actively streaming, and packets are delivered. For each confirmation during the rolling escalation widow, the response is good. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/U1QDTfQJwY3IP2vO1kUMG_image.png) 2. A network error causes the source to lose packets. The following state check informs ZEN Master of CC Errors due to packet loss. As this is the first non-positive event during the window, ZEN Master places the source into a warning state. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/tJvx6gRIO3yeNyS1TNCdS_image.png) 3. The source has recovered, at the next check the response indicates the source is good. ZEN Master returns the source into a good state. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/s2RDinb9-07CTCbbrECTP_image.png) 4. Further packet loss occurs, and the following checks return a non-positive result of a source exhibiting CC Errors. ZEN Master has returned the source to a warning state. Note that the cumulative event total is now 2, and that concurrent non-positive results are considered a single ongoing event. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/r4nmwx0BA1To80lAeGrC9_image.png) 5. Monitoring of the source continues, returning several more CC Error results between to concurrent sets of good responses. The event count has reached 3, when the following check returns another non-positive result. The event count within the window is now 4, meeting the escalation requirement. ZEN Master now escalates the state of the source to an Error. Due to the notification settings, an Alert email is sent to users with notification privileges on the source. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/WzJRPSbbdGf2zOjaBwybt_image.png) 6. The next and subsequent confirmations return positive results, but the Source state has already met the Error criteria within the window and *remains in Error.* ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/0j77C4PLWPW9l8quUTxrH_image.png) 7. Once the Error criteria is met, further responses indicating CC Errors within the window will cause the Error state on the Source to persist. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/rS6YGb6_VzDsDmUOtarQz_image.png) 8. The source recovers, and subsequent checks return positive state. After a full de-escalation window of good responses ZEN Master returns the source to a Good status. Due to the notification settings, an Alert email is sent to all users with notification privileges on the source ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/T8Pp1458zGt9zlLGOdJd5_image.png) ### Scenario Two In scenario 2, the healthy source encounters *sustained* interruption before recovery. 1. The healthy source begins to return non-positive responses indicating CC Errors, and ZEN Master places the source in a warning state. The cumulative event count is 1. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/EQGor04ni1_ksLKPbl78T_image.png) 2. Packet loss in ongoing for almost the full duration of the escalation window, and the confirmations continue to return non-positive responses indicating CC Errors. The Event count remains 1 and the warning states persists. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/odnVBnjxxXnnP3WO7EsUr_image.png) 3. Upon another non-positive response, if the full duration of the escalation window is reached, ZEN Master escalates the state of the source to an Error. Note that in this scenario the event count did not exceed one, but continual non-positive events for the duration of the window result in an Error state. Due to the notification settings, an email Alert is generated to all users with notification privileges on the source. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/og4q-um4CzAyzwB9uiQ66_image.png) 4. The source recovers, and subsequent confirmations return a good state. After a full de-escalation window of good responses (i.e., 10 minutes and 4 event counts), ZEN Master finally returns the source to an OK state. ZEN Master generates an Alert email to all users with notification privileges on the source. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/if6OEyltTu3eHRzqP_x1d_image.png) [title] The Events Profile [path] Alert Escalation and Notification Management Guide/ The rules that determine an objects escalation path and notification email are configured in the **Events Profiles**, which are found under the **Configurations** menu. Event Profiles contain a set of rules that dictate how the system escalates the status of an object from each of the possible platform states: - Pending - Ok - Warn - Error And if needed, to send an alert notification. Note: Only ‘Error’ and ‘Ok’ Events can generate an alert and email notification. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/W8ivvAQhqSnCOiF8jijCF_image.png) The Event Profile rule table consists of various rules that will determine any alerting actions taken by ZEN Master depending upon the object type the profile is applied to. These profiles are not actually applied until they are associated with the various resources or streaming components within ZEN Master during the object's configuration. See [Applying Event Profiles](docId:2POfvPer-2w7HPKUnF0mi).   [title] Zen Master Monitoring [path] Alert Escalation and Notification Management Guide/ Every few minutes, ZEN Master polls data from the Zixi components in the deployment, including each system's current health check and system metrics and the current state of each source and target. These metrics are stored in the database and ZEN Master displays historic graphs that show changes over time in values such as CPU usage, or bitrate: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/IlzI7tISFvQU1CFVY5SnK_image.png) Other event data, changes, and user actions, are logged in the objects **Event Log**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/9yaSSF03RzUoX3wjKdYB8_image.png) ## Object Status Update and Alerting Mechanism ZEN Master compares the latest state metric with recent status and behavior. This updated account of the object’s behavior is then translated into an updated status and, where necessary, the object's status is escalated to ***warning*** or ***error*** states. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/q5iLPM9gW04SbDqbi_bsw_image.png) If an object is escalated to an ***error*** status, ZEN Master may also generate an alert notification, depending on the alerting configuration. [title] Creating a WebRTC Output [path] How to Monitor Streams Using WebRTC Home/ Zixi Broadcaster can transcode a TS stream Input into a WebRTC output using the relevant profiles, depending on the input video and audio, as described in the [Video and Audio Codec Support Options](docId\:ukYoKHP2ZOAmkoxxMvhG3) section. Before creating the WebRTC output, make sure you have configured the relevant transcoding profiles - see [Creating Transcoding Profiles for WebRTC](docId\:yLb7B8fu5t2p8xDMVqQ8u). When the input stream is transcoded, it becomes available to be pulled by the WebRTC player. **To Create a WebRTC Output:** ::::WorkflowBlock :::WorkflowBlockItem Create an input stream by following the instructions in the [Adding Input Streams](docId:5fAp4Zp7r44WbAJLxMgV1) section of the [Zixi Broadcaster User Guide](docId\:JGwIXYN936aeZmonZLERn). ::: :::WorkflowBlockItem Click the **Actions** button on the right end of the input stream row, and then click **Transcode**. The **Transcode \** window with the settings of the selected input stream is displayed. ::: :::WorkflowBlockItem Enter the unique **Stream ID**, which will correspond to the new transcoded input that will be added. ::: :::WorkflowBlockItem In the **Output Type** field, select **WebRTC**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/T7DkjRIdCOFKbe5Lxc86-_image.png" size="70" width="462" height="507" position="center" showCaption="false"} ::: :::WorkflowBlockItem Under **Stream Parameters**, in the **Video profile** field, select the desired video profile for the desired method. Only supported profiles are shown. If you would like to remove the video or audio stream completely, select **Remove stream**. - Pass-Through – select **Keep original stream** - Single Version Transcoding – select a profile that converts to H.264 with Main or Baseline profile and no B Frames - Multiple Version Transcoding – select a profile that converts to RAW video ::: :::WorkflowBlockItem In the **Audio profile** field, select the desired **audio profile** for the desired method. Only supported profiles are shown. If you would like to remove the video or audio stream completely, select **Remove stream**. - Pass-Through – select **Keep original stream** - Single Version Transcoding – select a profile that converts to Opus - Multiple Version Transcoding – select a profile that converts to RAW audio Only supported profiles are shown. ::: :::WorkflowBlockItem Configure additional parameters as required, see [Transcoding an Input Stream](docId\:Fxgz8rCaVCribHkZS_pGp) (in the [Zixi Broadcaster User Guide](docId\:JGwIXYN936aeZmonZLERn) ). ::: :::WorkflowBlockItem Click **OK**. The transcoded input stream is created and appears in an embedded window labeled Transcoded sources under the original input stream from which it was created. ::: :::: :::Iframe{code=""} ::: [title] Configuring Sources for WebRTC [path] How to Monitor Streams Using WebRTC Home/WebRTC for ZEN Master/ When creating/editing a Source in ZEN Master, you can activate WebRTC for that Source, enabling users to monitor that Source using WebRTC. :::hint{type="info"} WebRTC needs to be activated independently for **each** Source in ZEN Master (by default it is disabled). ::: **To configure a Source for WebRTC:** :::::WorkflowBlock :::WorkflowBlockItem In the ZEN Master UI, in the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add** (or click **Edit** for an existing Source). The **Create New Source** selection window is displayed. ::: :::WorkflowBlockItem Fill in the parameters as needed. ::: ::::WorkflowBlockItem In the **WebRTC Playback** section, select the desired playback method. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/7Dr6eoG0lFjpg25Rb0Q-J_image.png" size="80" width="467" height="515" position="center" showCaption="false"} 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 Click **Save**. ::: ::::: [title] WebRTC for ZEN Master [path] How to Monitor Streams Using WebRTC Home/ You can monitor streams in ZEN Master via web browsers and mobile applications with real-time communication (RTC) using WebRTC. For streams that are not using WebRTC compliant codecs, ZEN Master will need to transcode the stream to be WebRTC compliant. The following are the requirements for a Zixi stream to be compliant. - **Video** - H.264 codec with *Baseline* or *Main* profile and no B frames. - **Audio** - Opus Codec. - [Configuring Sources for WebRTC](docId:2Tx-aRSUgJWezWfK7I2tX) - [Viewing Sources with WebRTC](docId\:LqeoLr1YyJsBrvd2jxB1a) [title] Step 3 (option a) – Creating an RTMP output in Zixi Broadcaster [path] How to Send a Zixi Stream to YouTube/Streaming to YouTube/ To create an RTMP output in Zixi Broadcaster: ::::WorkflowBlock :::WorkflowBlockItem On **Zixi Broadcaster**, in the **Inputs** tab, click the drop-down menu keycap: \* button for the Input that you have created. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/zr3kgQq7r6Mnr9HPE4IFo_image.png) ::: :::WorkflowBlockItem Click **New Output**. The **Add new output** window is displayed with the info of your Input Stream in place. ::: :::WorkflowBlockItem Select **RTMP** for the output type. The window shows the fields that need to be configured for an RTMP output. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/L-0uxkfNTjh2570M6qrEB_image.png" size="80" width="2288" height="1438" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Output Name** field, enter a unique identifier for the output. ::: :::WorkflowBlockItem On YouTube, under **Stream Settings**, in the **Stream URL** field, click **Copy**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/0EYRhFvaSvN3x9Hk09VCd_image.png" size="80" width="2721" height="802" position="center" showCaption="false"} ::: :::WorkflowBlockItem On **Zixi Broadcaster**, paste the copied string into the **URL** field. ::: :::WorkflowBlockItem If you want to add a backup URL, on **YouTube**, in the **Backup server URL** field, click **Copy**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/NYMewejRcOp6tmtk2RSsF_image.png" size="80" width="2721" height="802" position="center" showCaption="false"} ::: :::WorkflowBlockItem On **Zixi Broadcaster**, paste the copied string into the **Backup URL** field. ::: :::WorkflowBlockItem On **YouTube**, in the **Stream key** field, click **Copy**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/9SxSKrE7PyLev4BYQKy-s_image.png" size="80" width="1440" height="424" position="center" showCaption="false"} ::: :::WorkflowBlockItem On **Zixi Broadcaster**, delete the existing text in the **Stream Name** field and paste the copied text, add additional stream settings as desired and click **OK**. If the stream connected successfully you should be able to see a preview of the stream. ::: :::: [title] Streaming to YouTube [path] How to Send a Zixi Stream to YouTube/ YouTube enables you to create an RTMP or HLS stream and begin streaming immediately or create the stream and schedule the streaming for a later time. The stream configuration involves configuring YouTube and Zixi Broadcaster in tandem, as described in the following sections. - [Step 1 - Creating an input stream in Zixi Broadcaster](docId\:wMbhYD8VJGWiPV-G83Z9r) - [Step 2 (option a) - Setting a scheduled (Later Date) live stream on YouTube](docId:-p42MIDVx5kHPi5zlvlg5) - [Step 2 (option b) – Setting an immediate (Right Now) live stream on YouTube](docId\:UwWKqKEROoRUcrjsku07Y) - [Step 3 (option a) – Creating an RTMP output in Zixi Broadcaster](docId:3pKXrRzCgV0a6Qzp1hV3L) - [Step 3 (option b) – Creating an HLS output in Zixi Broadcaster](docId\:lqUQliHwmZbQkXL02Ml0y) [title] How to Use Zixi to Transport NDI Over the Public Internet : Prerequisites [path] How to Use Zixi to Transport NDI Over the Public Internet/ This tutorial assumes that you have installed and activated two Zixi Broadcasters (a sending Zixi Broadcaster and a receiving Zixi Broadcaster) and that it they are connected to the internet. For an explanation of how to install and activate a Zixi Broadcaster see [Zixi v14 Installation Guide](https://zixidocumentation.atlassian.net/wiki/spaces/114/pages/949420464). You will also need to have an active NDI stream available on your LAN. In the sending side, you will need to install the mDNS (Bonjour / Zeroconf) discovery mechanism, which advertises sources on a local area network. ## Hardware Requirements Transcoding is required on both the sending and receiving side. The Zixi Broadcaster can make use of the following transcoding configurations: - X264 software for AVC/H.264 encode/decode - NVIDIA GPU for AVC/H.264 and HEVC/H.265 encode/decode. :::hint{type="info"} NVIDIA GPUs are available on AWS, GCP, and Azure, and for bare-metal installations they are available in the NVIDIA Quadra P2XXX and RTX XXXX family of PCIe cards. Zixi has a partnership with ScaleLogic to provide servers that include these NVIDIA cards but these cards and servers can be sourced from other sources as well. ::: ## Software Requirements NDI utilizes mDNS (multicast Domain Name System) to create a zero configuration environment for discovery of NDI streams available on the LAN. Through mDNS, devices such as the Zixi Broadcaster can discover available NDI streams for processing. The use of mDNS requires operating system support as follows: - **Windows** - Windows 10 has mDNS support built in, which is necessary for any NDI applications running on Windows. - **CentOS** - The recommended platform for the Zixi Broadcaster is CentOS 7. mDNS support is provided by the Avahi package which typically is not installed by default on CentOS 7. **To install Avahi, run the following commands on the server hosting the Zixi Broadcaster:** ```bash sudo yum install avahi sudo service avahi-daemon start ``` ## Network The mDNS Ethernet frame is a multicast UDP packet that broadcasts to: - MAC address 01:00:5E:00:00\:FB(for IPv4) - IPv4 address 224.0.0.251 - UDP port 5353 You need to verify that the LAN where NDI streams are present is multicast enabled and that all systems needing access to NDI streams, such as the Zixi Broadcaster, do not block mDNS via their firewall. [title] How to Use Zixi to Transport NDI Over the Public Internet [path] / ## Legal Notice This document contains proprietary and confidential material of Zixi LLC. Any unauthorized reproduction, use, or disclosure of this material, or any part thereof, is strictly prohibited. This document is solely for the use of Zixi employees and authorized Zixi customers. The material furnished in this document is believed to be accurate and reliable. However, no responsibility is assumed by Zixi LLC. for the use of this document or any material included herein. Zixi LLC. reserves the right to make changes to this document or any material included herein at any time and without notice. For more information visit: [www.zixi.com](http://www.zixi.com/). Copyright © Zixi 2021 Waltham, MA U.S.A. All Rights Reserved. - [How to Use Zixi to Transport NDI Over the Public Internet: Introduction](docId:3Y0eccrAoMQAXknQzEYQe) - [How to Use Zixi to Transport NDI Over the Public Internet : Prerequisites](docId\:SzTas9S1YyvGQFv8ndFUb) - [Creating NDI Streams](docId\:ynirFC2ic2FwUV32XDKoO) - [Creating Streams Using VLC](docId\:wYSge6F1H6Xo8TwlndoaO) - [Creating Streams Using NewTek Connect](docId\:kIW9CsA732C3ynGPyFuPe) - [Transporting NDI Stream Using Zixi](docId\:vhNrYUtcGCAhlTCNWc3dx) - [Configure Receiving Zixi Broadcaster to Output NDI Stream](docId:7NoXLSHTB0YbqzSgZmDs2) - [Configure Sending Zixi Broadcaster to Ingest NDI Stream](docId\:pov0QFytqzSyAr83hxH_e) [title] Event Profile Alert Rule Types [path] Alert Escalation and Notification Management Guide/The Events Profile/ All rules within the Event Profile fall under one of two rule types: - Boolean Rule Type - Threshold Rule Type ## Boolean Rule Type The "Boolean rule type" is used for static states, there is no meaningful scale of degradation, but the state is simply ‘OK’ or not. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/QIjKYMyBshqXoMtCJgxe4_image.png) For example, the ***Broadcaster Configuration Error*** rule is parsed when a broadcaster’s configuration does not match the configuration expected by ZEN Master. Historical data or previous confirmation results are not used in this case. When this error occurs, it must be addressed. This type of rule offers three options that can be enabled/disabled: - **Generate OK Notification** - If enabled, the system will generate an ‘Ok’ alert email and send it to the user and groups who have email privileges for this object. - **Generate Error Notification** - If enabled, the system will generate an ‘Error’ alert email and send it to the user and groups who have email privileges for this object. - **Ignore object state for notification generation** – ZEN Master objects can have multiple issues, e.g., a Broadcaster with high CPU and full hard drive. An object already in an error state may later have cause to error for a secondary reason. By default, the initial email notification is sufficient, but in cases where a specific issue warrants a secondary email, select this option to force a notification even if a previous email has been sent. ### Boolean Rules Type with Escalation Control Some Boolean rules provide further controls for how the system manages and alerts on errors states within a definable time window. These rules are designed to serve two purposes: - **To address flapping states** - Flapping states occur when a problem is intermittent. For example, when a monitored object jumps continually between good and bad states. Users can be overloaded and inundated with email. - **To address continuous warning states** - it guarantees that an object will not sit in a continual warning state, never escalating to an Error status or generating an alert email. The rule ensures operator are made aware the issue. The "Escalation Rule" provides additional controls under the **Event Type** toggle to tune ZEN Masters propensity to either subdue or escalate warnings to full Errors and send an email notification. When the **Event Type** toggle is set to **‘Error’** the rule will immediately escalate an issue to an **Error** status, bypassing any intermediate warning state. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/5qIaHePZ8vPch6Wm7Vff6_image.png) When it is set to ‘**Warning’**, the rule provides two additional controls: - **Event Escalation Count** – the number of events needed to occur within a window for the system to escalate to a full Error. - **Escalation/de-escalation window** – specifies the timeframe to escalate/De-Escalate in minutes. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/gbNd4QPjIb2PColNatsUP_image.png) If the event type configuration is set to **‘Warning’**, the following will occur: - The object status will elevate to a ‘Warning’ upon the first and any subsequent continuous occurrences of the event. - It will return to ‘Ok’ if the state recovers. - Subsequent events within the allotted a time window will again limit the escalation to a Warning status.   - The object will escalate to an Error status when the total number of Event occurrences within the time window configured first reaches the event count escalation based on number occurrences and time window. If the event does not occur again in the time window, then it will de-escalate back to an OK state. If the event type configuration is set to **‘Error’ **the following will occur: - It will be an error event upon the first occurrence of the event. When event type is set to Error there is no de-escalation process. - A notification is sent. The **‘Track only, do not update object state’** option specifies that any escalation event is to be registered in the event log only. This option is useful when the issue occurrence itself if not a primary reason to alert the operator, just useful information to log for a later time. If the event type configuration is set to **‘Track only’**, the following will occur: - ZEN Master alert system will obey the escalation settings, as described above. - The issue triggering the rule and any resulting escalation, will not escalate the object itself to a warning or error. ## The Threshold Rule Type The Threshold Rule provides controls for events where both thresholds are relevant, of which there are 2 categories. Some thresholds cannot be noisy, or flap above and below the defined threshold. For example, the broadcaster license expiration warning can be set to a specific number of days in advance of expiration. The number of days remain on the license can only decrease. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/FMrf1SYI0vKIM_QGnBaGM_image.png) In such a case the object is escalated to a warning status when the first threshold is met and escalated to an error with corresponding notification emails when the second threshold is met. The second category of Threshold Rules is used for volatile metrics and provides controls for events where both thresholds are relevant, and de-escalation can occur, such as CPU Usage. For this type of event, ZEN Master will again escalate the object to a Warning or Error status when the corresponding threshold is crossed. However, once the value falls back and stays below the threshold for the specified de-escalation window duration, the object will de-escalate back to the state of the most recent confirmation result. When user notifications are enabled, they will occur on ‘Error’ and / or ‘Ok’ events. [title] Automatic Method [path] Zixi OnAir Guide (deprecated)/Preparing for Use/Configuring the Broadcaster/ The following procedure applies to broadcasters for which authorization is not controlled by ZEN Master. If authorizations for your broadcaster are controlled by ZEN Master, then you can allow automatic Push Inputs by editing the Broadcaster Cluster authorization settings in ZEN Master. **To enable your broadcaster to allow automatic Push Inputs:** ::::WorkflowBlock :::WorkflowBlockItem In Zixi Broadcaster, go to **Settings > Live Protocols**. ::: :::WorkflowBlockItem Select **Allow automatic HTTP push input**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/w6SY7ksX66cq1eg9NVGxs_image.png" size="90" width="749" height="135" position="center" showCaption="false"} ::: :::WorkflowBlockItem Click **Apply**. Your Broadcaster is ready to receive input streams from OnAir. ::: :::: **To enable your broadcaster to allow automatic RTMP input:** ::::WorkflowBlock :::WorkflowBlockItem In Zixi Broadcaster, go to **Settings > Live Protocols**. ::: :::WorkflowBlockItem Under **RTMP Serve**r section, select **Enable RTMP** and **Allow automatic RTMP input**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/vtQgmFjz4fgCs-ZkBqr9j_image.png" size="90" width="848" height="165" position="center" showCaption="false"} ::: :::WorkflowBlockItem Click **Apply**. Your Broadcaster is ready to receive input streams from OnAir. ::: :::: [title] Zixi How To Guides [path] / ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/le9sXdS7lxz8xnDRc69lh_how-to-smaller.png) This section provides guides for cross-product things like security, related apps like VLC, OBS, and Wirecast, Zixi's OnAir Pro mobile app, etc. - [Network Port Settings](docId:_ZnPrTHruh2RZO8rhei2Z) - [Zixi Security Best Practices](docId:_7NFnXxN0AtAeV8lfV2Xc) - [Zixi Multicast Deployment Guide](docId\:zKHKA9Wzp-w8rt9qQo_ze) - [Zixi VLC Plugin Setup Guide](docId\:pG87liQ3B7evHxSiHC2NM) - [Zixi On Air Pro Guide](docId:8mmLXna1om5BAcjoA-oiC) - [Zixi OnAir Guide (deprecated)](docId\:eSgqBjx-RVmXHi6mA1lnr) - [Zixi Player Guide](docId:9fwVir8VQf5v7WoN-NwuM) - [Zixi Transcoder - Installation Guide](docId\:lgQ7l9Suyqop2EtaBv1uL) - [Alert Escalation and Notification Management Guide](docId\:tTIHguzlZsTUnWw0T4QOb) - [Deploying Zixi Products Using Docker Containers](docId\:KFs0sEhbIzmMBtK6iMoyr) - [DekTec ASI Installation Guide](docId\:a_hRYdkgt6eWyqWtBWyLI) - [How to Monitor Streams Using WebRTC](docId\:Ts6pRnbAIVBKBD5oq1L5z) - [How to Send a Zixi Stream to YouTube](docId\:j3RZ9A8DYRIqxV-Gxf2k3) - [How to Use Zixi to Transport NDI Over the Public Internet](docId\:xwHzUhPqzdZ6h0zXiwlcd) - [HTML Overlay Installation](docId:1svyta7P777nBTqPN8yt8) - [OBS Zixi Integration - Quick Start Guide Home](docId\:sf_jA_bS0yYVU9qKlOqCw) - [Using Terraform with OCI](docId:-lvOa8WBVisluh40f5TZa) - [Wirecast Zixi Integration - Quick Start Guide](docId\:D7DOOhVGk3IKnEKBwzujl) - [Wirecast Zixi ZEC Quick Start Guide Home](docId\:b1LkQuL21tIT8xSYf_8u_) [title] Network Port Settings [path] / For the Zixi Broadcaster operating as a streaming server, the following ports must be opened on your Firewall(s) as described below: # Network Settings for Zixi Broadcaster as Streaming Server | Port | Type | Direction | **Description** | Protocol | | --------------------- | --------------- | ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | | 2088/7088
\*\*\* | UDP | Inbound\* | Push input from a Zixi enabled feeding software \*\* | Zixi | | 2077/7077
\*\*\* | UDP | Inbound\* | Pull output by Zixi enabled receiving software \*\* | Zixi | | 2088/7088
\*\*\* | UDP | Outbound\* | Push output to a Zixi Broadcaster or AWS MediaConnect | Zixi | | 2077/7077
\*\*\* | UDP | Outbound\* | Pull input from a Zixi Broadcaster or AWS MediaConnect | Zixi | | 1935 | TCP | Inbound\* | Push input from RTMP enabled software | RTMP | | 1935 | TCP | Outbound\* | Push output to CDN origin server or RTMP enabled software | RTMP | | 7777 | TCP | Inbound\* | Pull output from HTML5 video player or CDN caching software | HLS or DASH | | 4444 | TCP | Inbound\* | Web management UI | HTTP | | 80/443 | TCP

| Outbound\* | Communication to Zixi License server -
For **all** Broadcaster versions:
****[license.zixi.com](http://license.zixi.com/), [license2.zixi.com](http://license.zixi.com/)
**For Broadcaster v19 and later: also add:**
[licensing.zixi.com](https://licensing.zixi.com)
* 52.72.218.41 * 34.195.97.223 * 3.140.62.221 * 3.137.16.26
ZEN Master Backend Servers
* 18.210.103.157 * 23.20.44.73 * 34.200.88.233 * 34.238.1.65 * 35.170.111.151 * 52.4.9.203 | HTTP/HTTPS | | 53 | TCP & UDP | Outbound\* | Communication to Domain Name Server |
| \* Return traffic must be enabled. \*\* The maximum recommended throughput per port is 1Gbps. If more throughput is expected through the Broadcaster, additional ports for the Zixi protocol can be defined on the [General](https://zixidocumentation.atlassian.net/wiki/spaces/116/pages/4775778220/General) page under the **Settings** tab. \*\*\* 7077 and 7088 use DTLS encryption For ZEC operating as a feeder device to a remote Zixi Broadcaster or AWS MediaConnect, the following ports must be opened on your Firewall(s) as described below: # Network Settings for ZEC as a Feeder Device | Port | Type | Direction | **Description** | Protocol | | --------------- | --------------- | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- | | 2088/7088\*\*\* | UDP | Outbound\* | Push output to a Zixi Broadcaster or AWS MediaConnect | Zixi | | 1935 | TCP | Inbound\* | Push input from RTMP enabled software | RTMP | | 4444 | TCP | Inbound \* | Web management UI | HTTP | | 80/443 | TCP

| Outbound\* | Communication to Zixi License server -
[license.zixi.com](http://license.zixi.com/), [license2.zixi.com](http://license.zixi.com/)
* 52.72.218.41 * 34.195.97.223 * 3.140.62.221 * 3.137.16.26
ZEN Master Backend Servers
* 18.210.103.157 * 23.20.44.73 * 34.200.88.233 * 34.238.1.65 * 35.170.111.151 * 52.4.9.203 | HTTP/HTTPS | | 53 | TCP & UDP | Outbound\* | Communication to Domain Name Server |
| \* Return traffic must be enabled. \*\* The maximum recommended throughput per port is 1Gbps. If more throughput is expected through the Broadcaster, additional ports for the Zixi protocol can be defined on the [General](https://zixidocumentation.atlassian.net/wiki/spaces/116/pages/4775778220/General) page under the **Settings** tab. \*\*\* 7077 and 7088 use DTLS encryption For the ZEC operating as a receiver device, the following ports must be opened on your Firewall(s) as described below: # Network Settings for ZEC as a Receiver Device | Port | Type | Direction | **Description** | Protocol | | --------------------- | --------------- | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | | 2077/7077
\*\*\* | UDP | Outbound\* | Pull input from a Zixi Broadcaster or AWS MediaConnect | Zixi | | 1935 | TCP | Inbound\* | Push output to CDN origin server or RTMP enabled software | RTMP | | 7777 | TCP | Inbound\* | Pull output from HTML5 video player or CDN caching software | HLS or DASH | | 4444 | TCP | Inbound\* | Web management UI | HTTP | | 80/443 | TCP

| Outbound\* | Communication to Zixi License server -
[license.zixi.com](http://license.zixi.com/), [license2.zixi.com](http://license.zixi.com/)
* 52.72.218.41 * 34.195.97.223 * 3.140.62.221 * 3.137.16.26
ZEN Master Backend Servers
* 18.210.103.157 * 23.20.44.73 * 34.200.88.233 * 34.238.1.65 * 35.170.111.151 * 52.4.9.203 | HTTP/HTTPS | | 53 | TCP & UDP | Outbound\* | Communication to Domain Name Server |
| | 22 | SSH | Outbound\* | ZEN Master to customer's io.zixi.com server
Note: This is an outbound-only, private key authenticated, SSH tunnel - no inbound rules are required | | \* Return traffic must be enabled. \*\* The maximum recommended throughput per port is 1Gbps. If more throughput is expected through the Broadcaster, additional ports for the Zixi protocol can be defined on the [General](https://zixidocumentation.atlassian.net/wiki/spaces/116/pages/4775778220/General) page under the **Settings** tab. \*\*\* 7077 and 7088 use DTLS encryption ## The two APIs use different paths | API | Protocol and port | Sign-in | Route | | ------------------- | ------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ | | **Broadcaster API** | HTTP on the Broadcaster's web port, TCP 4444 by default. HTTPS on the same port when "Use HTTPS interface for UI" is on. | A Broadcaster user account, sent as HTTP basic authentication | Straight to the Broadcaster. ZEN Master reaches it through the Broadcaster's reverse SSH tunnel. | | **ZEN Master API** | HTTPS | An API key, in the x-api-key header | Your ZEN Master address | [title] Changing the Default Root Folder Location [path] Zixi Security Best Practices/Configuring the Security Settings after Installation/ The root folder is used to store recordings and VOD content. Over time the size of the content in this folder may grow significantly. If this folder is in the same partition as the machine’s operating system and the capacity limit is reached, it may cause risks to the machine itself. It is therefore recommended to change Zixi’s root folder location to a separate partition (not the same partition as the OS). If the partition is filled it will not disrupt or harm the machine’s OS. **To change the default root folder location:** ::::WorkflowBlock :::WorkflowBlockItem Open the ‘broadcaster-info.xml’ file, which is located in the same folder as the Zixi executable file. The file includes the following content: ```xml d:\ts false false 0 1 ``` ::: :::WorkflowBlockItem Change the path settings, which is under `` and between `/` to a folder or to the root of a separate partition and save the file. ::: :::WorkflowBlockItem The folder location is displayed in **Settings > General** in the **Root Folder** field: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/8sIjqZTIDRvOSgvAoINAH_image.png" size="90" width="1280" height="486" position="center" showCaption="false"} ::: :::: [title] Enabling DTLS [path] Zixi Security Best Practices/Configuring the Security Settings after Installation/ ## Overview Datagram Transport Layer Security (DTLS) is a communications protocol that provides security for datagram-based applications by allowing them to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery. The DTLS protocol is based on the stream-oriented Transport Layer Security (TLS) protocol and is intended to provide similar security guarantees. Zixi supports DTLS encryption and identity authentication. This feature can be used in conjunction with static key AES scrambling for end-to-end encryption. DTLS encryption can be configured on any Input or Output UDP port on the Zixi Broadcaster. This feature is activated and configured in the Settings screen. A DTLS server is configured using certificate and private key files in X.509 PEM format, similar to the files used to enable an HTTPS server. ## To enable DTLS encryption: :::::WorkflowBlock :::WorkflowBlockItem In the Zixi Broadcaster navigation, click **Settings**. The Settings page opens showing the **General** tab. ::: :::WorkflowBlockItem Under the General section, click on the **HTTPS and DTLS Streaming Certificate** section heading to expand that section. The **HTTPS and DTLS Streaming Certificate** settings are shown. ::: :::WorkflowBlockItem Next to the **Certificate uploaded** field, click **Upload**. ![DTLS Settings](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Lgmj16rMq950trSPGI1wx-20260323-155122.png) ::: :::WorkflowBlockItem Browse to find your certificate file, select it and click **Open**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/yksj9wqY5olKeG-5QQxUX_image.png" size="90" width="986" height="498" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Private key uploaded** field, click **Upload**. ::: :::WorkflowBlockItem Browse to find your private key file, select it and click **Open**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/yX9LYR4blMIkZUgfinp_O_image.png" size="84" width="1156" height="500" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Private key passphrase** field, type a passphrase, if one exists. ::: ::::WorkflowBlockItem Verify that there is a green **Yes** next to both **Upload** buttons. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ZgCT6N_lbHCWiOBivNCVe_image.png" size="44" width="1280" height="445" position="center" showCaption="false"} :::hint{type="info"} Any LIVE or ACTIVE streaming will be affected upon restarting the service. ::: :::: :::WorkflowBlockItem Click **Restart Now** or **Restart Later**. ::: :::WorkflowBlockItem You can verify DTLS status on your streams in 2 ways: - There will be a gold lock on the green connected status icon - When you mouseover the green connected status icon, an informational popup will present the DTLS certificate issuance information including expiration. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/-74BM4qYa3KUHiU6raxTt_dtls.png) ::: ::::: ## Creating a Self-Signed Certificate There are various ways to obtain SSL/TLS certificates, but for a standalone Broadcaster, you can also create a self-signed certificate using OpenSSL. OpenSSL may already be installed on your system, but if not, you can see a list of av available binaries to install at [https://github.com/openssl/openssl/wiki/Binaries](https://github.com/openssl/openssl/wiki/Binaries). During the creation of your certificate, you will be prompted for the following information: - A passphrase for the certificate - be sure to remember what it is! - The two-letter code for your country (such as US or FR) - if you don't know the code, you can look it up at: [https://knowledge.digicert.com/general-information/ssl-certificate-country-codes](https://knowledge.digicert.com/general-information/ssl-certificate-country-codes) - The full state or province name within that country (such as Massachusetts) - The locality name, typically a city such as Boston - Organization name, such as Zixi - Organizational unit name, such as Documentation - Your name or a fully qualified domain name (FQDN), such as zixi.com - Your email address Once OpenSSL is installed, you can create a certificate by running a command like this: ```bash // sample command - see OpenSSL help for options // note that the pem files will be created in the directory where you run this command openssl req -x509 -newkey rsa:2048 -keyout selfsigned_key.pem -out selfsigned_cert.pem ``` After the PEM files are created, you can upload them and enter the passphrase in the Broadcaster settings as described above. [title] Stream Encryption [path] Zixi Security Best Practices/ Streams can be encrypted end-to-end, using fixed-key AES encryption. There are multiple options for encrypting the stream payload: - **Zixi Feeder (Legacy) output **– Zixi Feeder can encrypt outputs using a fixed key (AES 128, AES 192, AES 256) which can be entered into the output settings or automatically generated. - **Zixi Broadcaster input **– input streams can be encrypted by Zixi Broadcaster using a fixed key (AES 128, AES 192, AES 256), which can be entered into the input settings or automatically generated. Zixi Broadcaster can be configured to decrypt contribution streams using a matching key, or to securely forward encrypted streams to Receivers. This enables you to transmit the stream end-to-end with only the edge applications being able to see or analyze the traffic. **To encrypt an output stream in Zixi Feeder (Legacy):** ::::WorkflowBlock :::WorkflowBlockItem In the Zixi Feeder navigation, click **Outputs.** ::: :::WorkflowBlockItem Click **+ New Output**. ::: :::WorkflowBlockItem In the **Type** field select **Push to Broadcaster**. ::: :::WorkflowBlockItem Fill in the output details as needed. ::: :::WorkflowBlockItem At the bottom, select the **Show all Settings **checkbox. ::: :::WorkflowBlockItem Select the **Advanced Properties** checkbox. ::: :::WorkflowBlockItem In the **Encryption Type** field, select *AES 128*, *AES 192*, *AES 256* for fixed key or *Automatic* for automatically system-generated encryption. ::: :::WorkflowBlockItem If you have selected one of the fixed key encryptions, enter your own encryption key into the **Key** field or click **Generate** to have the system automatically generate a key. The identical key should be used to decrypt the stream on the other end. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/obRfwc_K5B1iRpeZnPZoe_image.png" size="84" width="954" height="665" position="center" showCaption="false"} ::: :::WorkflowBlockItem Click **OK**. ::: :::: **To encrypt an input stream in Zixi Broadcaster/ZEC:** ::::WorkflowBlock :::WorkflowBlockItem In the Zixi Broadcaster navigation, click **Inputs**. ::: :::WorkflowBlockItem Click **+ New Input**. ::: :::WorkflowBlockItem Select the desired input type (Push, Pull etc.). ::: :::WorkflowBlockItem Fill in the input details as needed. ::: :::WorkflowBlockItem At the bottom, select the **Enable Encryption **checkbox. ::: :::WorkflowBlockItem In the **Encryption Type** field, select *AES 128*, *AES 192 *or *AES 256* for fixed key encryption. ::: :::WorkflowBlockItem In the **Encryption Key** field, enter your own key or click **Generate** to have the system automatically generate a key. The identical key should be used to decrypt the stream on the other end. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/WxGz2BAS9P1EyC2vheeY6_image.png" size="84" width="887" height="905" position="center" showCaption="false"} ::: :::WorkflowBlockItem Click **OK**. ::: :::: **To decrypt an input stream in Zixi Broadcaster/ZEC:** :::::WorkflowBlock :::WorkflowBlockItem In the Zixi Broadcaster navigation, click **Inputs**. ::: :::WorkflowBlockItem Click **+ New Input**. ::: ::::WorkflowBlockItem Select the desired input type. :::hint{type="info"} Decryption is only supported for Zixi protocol Push or Pull inputs. ::: :::: :::WorkflowBlockItem Fill in the input details as needed. ::: :::WorkflowBlockItem At the bottom, in the **Decryption type** field, select from the drop-down list *AES 128*, *AES 192* or *AES 256* for fixed decryption or *None* if no decryption is needed. ::: :::WorkflowBlockItem In the **Decryption Type** field, select *AES 128*, *AES 192* or *AES 256* for fixed key decryption. ::: :::WorkflowBlockItem In the **Decryption key** field, enter the exact same key that was used to encrypt the stream. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Q2Emj1mbrYppMxvrKh_Bf_image.png" size="60" width="688" height="768" position="center" showCaption="false"} ::: :::WorkflowBlockItem Click **OK**. ::: ::::: **To decrypt a stream in Zixi Receiver:** ::::WorkflowBlock :::WorkflowBlockItem In the Zixi Receiver navigation, click **Inputs.** ::: :::WorkflowBlockItem Click **+ New Input**. ::: :::WorkflowBlockItem Select **Pull.** ::: :::WorkflowBlockItem Fill in the input details as needed. ::: :::WorkflowBlockItem At the bottom, in the **Decryption type** field, select from the drop-down list *AES 128*, *AES 192* or *AES 256* for fixed decryption or *None* if no decryption is needed. ::: :::WorkflowBlockItem In the **Decryption key** field, enter the exact same key that was used to encrypt the stream. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/0Qfp8UyHTd0pW0dGUxGod_image.png" size="50" width="653" height="717" position="center" showCaption="false"} ::: :::WorkflowBlockItem Click **OK**. ::: :::: [title] Zixi Security Best Practices [path] / The following documentation describes Zixi’s security features and mechanisms, while providing instructions on how to set them up. In addition, the document provides best practices on how to setup a secure environment. The document contains explanations and instructions on the following subjects: - [Password protection](docId:51rNJepV1smhq-tMR-7Eo) - [Using HTTPS/SSL for Zixi](docId\:z7tr0iyCoo46G5B5DvA2U) - [Enabling DTLS](docId\:dPbwtfB1ic317na2uhnJD) - [Stream Encryption](docId:8HiLlO6eyK1NKkaVqEmdp) - [Firewall Settings](docId\:HzEq6rhjndO4UangsyTtd) - [Remote SSH Connections](docId:5rL3ao1PN7jOSUctH0gkr) For additional details on the setup and configuration of the Zixi software components, refer to the [Zixi Core Documentation Current Version](docId:57HmWlQ-LhvAKOaEvSOvu) . [title] Remote SSH Connections [path] Zixi Security Best Practices/ For OS login, it is recommended to use passphrase protected SSH key pairs instead of passwords, and to not allow remote root login. To do this, take the following steps: - Generate a passphrase-protected SSH key for each system that needs to access the server. - Disable SSH password authentication. - Disable root login. Legacy Zixi Feeders & Receivers, ZEC and Zixi Broadcasters have a section under Settings that enables you to define reverse tunnels to a remote SSH server, in order to allow accessing the application through a secure SSH tunnel remotely. Make sure to stop/delete all tunnels if remote access is not desirable. **To configure an SSH Tunnel in Legacy Zixi Feeder/Receiver:** ::::WorkflowBlock :::WorkflowBlockItem Go to **Settings > SSH Tunnels**. ::: :::WorkflowBlockItem In the **Server Connection** section configure the server connection, as described in the table below. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/P1-3FPjtRbf45GKtSSVCq_image.png" size="80" width="1241" height="491" position="center" showCaption="false"} ::: :::WorkflowBlockItem Click **Apply**. ::: :::WorkflowBlockItem In the **Reverse tunnels** section, click **Add**. The **Tunnel details** dialog appears: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/7UJjvvtRH3mRvgO8rA90v_image.png" size="40" width="349" height="207" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Remote Source Port** field, type the Remote Source Port that will be used to connect. ::: :::WorkflowBlockItem In the **Local Destination IP** field, type the IP address of the Zixi Feeder/Receiver. ::: :::WorkflowBlockItem In the **Local Destination Port** field, type the port number in the Zixi Feeder/Receiver for the specific reverse SSH tunnel. ::: :::WorkflowBlockItem Click **OK**. ::: :::: **To configure an SSH Tunnel in Zixi Broadcaster:** ::::WorkflowBlock :::WorkflowBlockItem Go to **Settings > SSH Connections**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ARme6JKOn2vCWU8g634z9_image.png" size="90" width="1210" height="223" position="center" showCaption="false"} ::: :::WorkflowBlockItem Click **+ Add connection**. The **Add SSH connection** dialog appears. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/gPwbGilv8HP051SjM9JUN_image.png" size="40" width="271" height="197" position="center" showCaption="false"} ::: :::WorkflowBlockItem Configure the server connection, as described in the table below. ::: :::WorkflowBlockItem Click **Apply**. The configuration will be added to the **Defined Connections** section on the screen. ::: :::WorkflowBlockItem Click on the name of the new SSH connection ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/s12kRjrrdHWM5DZa3TO0x_image.png" size="80" width="1280" height="336" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Remote Source Port** field, specify the port that will be used to connect. ::: :::WorkflowBlockItem In the **Local Destination IP** field, specify the IP address of the Zixi Broadcaster. ::: :::WorkflowBlockItem In the **Local Destination Port** field, specify the port number in the Zixi Broadcaster for the specific reverse SSH tunnel. ::: :::WorkflowBlockItem Click **OK**. ::: :::: | ### Field | ### Description | | -------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | | ### Server connection | | | **Host** | Specify the Host name or IP address of the remote server for the SSH connection. | | **SSH Port** | Specify the port for the SSH connection.
Default: 22 | | **Username** | Specify the username required for SSH connection.
Default: the username on the remote computer is the same as that on the local one. | | **Key File** | Indicates if a key file has been uploaded.
Click Upload Key to upload a key to the server. | | ### Reverse tunnels | | | **Remote Source Port** | Specify the remote source port. | | **Local Destination IP** | Specify the IP address of the local destination. | | **Local Destination Port** | Specify the port number of the local destination. | | **Status** | Specify the status of the SSH tunnel. | [title] Configuring the Security Settings after Installation [path] Zixi Security Best Practices/ The following security procedure should be implemented following the installation and setup of all Zixi resources (Feeder, ZEC, Broadcaster and Receiver). - [title] Access Control and Authorization [path] Zixi Security Best Practices/ In general, every input and output needs to be pre-defined in the **Inputs** and **Outputs** screens of the Zixi software components before the connection/streaming. These settings include a variety of parameters for the stream, such as the Stream ID, and may include authentication parameters such as password. However, it is also possible to allow automatic connection of Push inputs and Pull outputs without defining them in advance. The streams will appear in the Inputs/Outputs screen automatically when the connection is established. The automatic connection settings include the following modes (in **Settings > Authorization** screen): - **Allow Automatic Push Inputs **- if this checkbox ***is selected***, the Zixi Broadcaster will automatically create an input stream each time it receives a push stream from a source. If the checkbox ***is NOT selected***, Push input streams must be pre-defined and the Zixi Feeders should match the defined Stream ID and password before connecting. - **Allow Automatic Pull Outputs **– if this checkbox ***is selected***, any Zixi Receiver that requests a Pull output will be granted access. If the checkbox ***is NOT selected****,* Pull-output entry must be pre-defined with Stream ID, Password, and the ID of the target receiver to allow each pull connection. - **Global Password **– another automatic connection option is through a “global password”. This is a single password that will be used for all access requests. Any Zixi Feeder or Zixi Player that passes this password can connect, without the need to pre-define the input/output. - **Linux Users **– this automatic connection option uses the built-in authorization of the operating system. In this case, Zixi Players will need to pass a valid username/password that is defined in the OS. - **HTTP Server – **this automatic connection uses an external HTTP web server to handle the authentication. On each connection attempt, HTTP request is sent to an external web server to handle the authentication, with stream ID, password, and requesting IP address. - **Users File - ** - **Text File -** this automatic connection uses a text file containing the connection configuration. For input streams, the file contains the stream name and password. For output streams, the file contains the stream name, user and password of the viewer. - **Stream access -** This automatic connection is for access authorization on the stream level. In this case, the password needs to be the same as the password to access the stream. - **Redirector auth -** NOT IN USE. The automatic connection settings should be used with caution. It shouldn’t be enabled unless you can ensure all connections originate from a trusted source. **To define automatic connection settings:** ::::WorkflowBlock :::WorkflowBlockItem In the Zixi Broadcaster navigation, click **Settings**. ::: :::WorkflowBlockItem In the **Settings** navigation, click **Authorization**. ::: :::WorkflowBlockItem If you would like to enable automatic Push inputs and/or automatic Pull outputs, select *None* from the dropdown list in the **Type **field, then do the following: 1. To enable **Automatic Push Inputs**, select the **Allow Automatic Push Inputs **checkbox. 2. To enable **Automatic Pull Outputs**, select the **Allow Automatic Pull Outputs **checkbox. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/C6tYejr8w_N-HSRZ0Fz_n_image.png" size="90" width="1178" height="530" position="center" showCaption="false"} ::: :::WorkflowBlockItem If you want to activate one of the available methods for automatic authorization (described above), select the desired method from the dropdown list in the **Type** field, then do the following: - In the **Parameter** field, enter the relevant parameter for the selected authorization type. - If you would like to allow access by user folders, click **Separate user folders**. ::: :::WorkflowBlockItem Click **Apply**. A confirmation dialog is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/PLI_jnVo8rBskIzpyndGj_image.png" size="58" width="560" height="163" position="center" showCaption="false"} ::: :::WorkflowBlockItem Click **OK**. ::: :::: [title] Replacing the Default Login Passwords [path] Zixi Security Best Practices/Configuring the Security Settings after Installation/ All Zixi resources come with a preconfigured admin account, which can perform all actions in the system. For Broadcaster you can add additional users with the following roles: - Operator - can perform read/write on all streams but cannot modify the configurations in the Settings screens. - User - can only perform read actions on streams and can switch between existing streams. - Observer - can perform only read actions on the streams. The default password for the "admin" account is "1234". Following the installation, it is strongly recommended to replace this with a "strong" password. Every organization has its own password policy, but generally, a strong password should include the following: - At least six characters - A combination of letters, numbers and symbols (@, #, $, %, etc.) - Both lowercase and uppercase letters. **To replace the default passwords in Zixi Broadcaster/ZEC:** ::::WorkflowBlock :::WorkflowBlockItem In the Zixi broadcaster navigation, click **Settings**. The Settings page opens showing the General tab. ::: :::WorkflowBlockItem In the **General** section, in the **Admin password** field, enter a "strong" password. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/puJBkKqtTn6icHK9gcOmu_image.png" size="90" width="1150" height="514" position="center" showCaption="false"} ::: :::WorkflowBlockItem If you have activated one or more additional accounts with the role of Operator, User, and/or Observer (by selecting the checkbox for Enable read/write user-except for settings screen…, **Enable read only user + ability to switch streams**… and/or Enable read only user) then replace each of the passwords with a “strong” password. ::: :::: [title] Defining “Non-Root User” [path] Zixi Security Best Practices/Configuring the Security Settings after Installation/ Zixi includes some settings that modify the operating system settings on the host machine (e.g. networking settings, etc.). Modifying these settings requires Zixi Broadcaster to have “Root user” (the highest) access privileges on the machine. However, once these settings have been defined, Zixi Broadcaster does not need these high level access privileges anymore and it is recommended to change the access privileges to a non-root user. The following settings cannot be modified after changing the access privileges. Make sure you do not need to modify any of these settings: - Settings > Network. - Settings > SSH Connections - Settings > ASI **To define non-root user privileges:** ::::WorkflowBlock :::WorkflowBlockItem Open the ‘cat /etc/systemd/system/zixibc.service’ startup script. ::: :::WorkflowBlockItem Modify the ‘`user=`’ to a non-root user. ::: :::: [title] Firewall Settings [path] Zixi Security Best Practices/ As a general security best practice, you should minimize the amount of ports that are opened on the Firewall. The initiating side can be behind an NAT, and doesn’t need to be publicly reachable. The Zixi Broadcaster should have a publicly reachable address. :::hint{type="info"} - Source IP address may be filtered to come only from certain allowed sources. - Make sure to open outgoing TCP 80 to license.zixi.com and UDP 53 to your DNS server. ::: # Network Settings for Zixi Broadcaster as Streaming Server | Port | Type | Direction | **Description** | Protocol | | --------------------- | --------------- | ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | | 2088/7088
\*\*\* | UDP | Inbound\* | Push input from a Zixi enabled feeding software \*\* | Zixi | | 2077/7077
\*\*\* | UDP | Inbound\* | Pull output by Zixi enabled receiving software \*\* | Zixi | | 2088/7088
\*\*\* | UDP | Outbound\* | Push output to a Zixi Broadcaster or AWS MediaConnect | Zixi | | 2077/7077
\*\*\* | UDP | Outbound\* | Pull input from a Zixi Broadcaster or AWS MediaConnect | Zixi | | 1935 | TCP | Inbound\* | Push input from RTMP enabled software | RTMP | | 1935 | TCP | Outbound\* | Push output to CDN origin server or RTMP enabled software | RTMP | | 7777 | TCP | Inbound\* | Pull output from HTML5 video player or CDN caching software | HLS or DASH | | 4444 | TCP | Inbound\* | Web management UI | HTTP | | 80/443 | TCP

| Outbound\* | Communication to Zixi License server -
For **all** Broadcaster versions:
****[license.zixi.com](http://license.zixi.com/), [license2.zixi.com](http://license.zixi.com/)
**For Broadcaster v19 and later: also add:**
[licensing.zixi.com](https://licensing.zixi.com)
* 52.72.218.41 * 34.195.97.223 * 3.140.62.221 * 3.137.16.26
ZEN Master Backend Servers
* 18.210.103.157 * 23.20.44.73 * 34.200.88.233 * 34.238.1.65 * 35.170.111.151 * 52.4.9.203 | HTTP/HTTPS | | 53 | TCP & UDP | Outbound\* | Communication to Domain Name Server |
| \* Return traffic must be enabled. \*\* The maximum recommended throughput per port is 1Gbps. If more throughput is expected through the Broadcaster, additional ports for the Zixi protocol can be defined on the [General](https://zixidocumentation.atlassian.net/wiki/spaces/116/pages/4775778220/General) page under the **Settings** tab. \*\*\* 7077 and 7088 use DTLS encryption For ZEC operating as a feeder device to a remote Zixi Broadcaster or AWS MediaConnect, the following ports must be opened on your Firewall(s) as described below: # Network Settings for ZEC as a Feeder Device | Port | Type | Direction | **Description** | Protocol | | --------------- | --------------- | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------- | | 2088/7088\*\*\* | UDP | Outbound\* | Push output to a Zixi Broadcaster or AWS MediaConnect | Zixi | | 1935 | TCP | Inbound\* | Push input from RTMP enabled software | RTMP | | 4444 | TCP | Inbound \* | Web management UI | HTTP | | 80/443 | TCP

| Outbound\* | Communication to Zixi License server -
[license.zixi.com](http://license.zixi.com/), [license2.zixi.com](http://license.zixi.com/)
* 52.72.218.41 * 34.195.97.223 * 3.140.62.221 * 3.137.16.26
ZEN Master Backend Servers
* 18.210.103.157 * 23.20.44.73 * 34.200.88.233 * 34.238.1.65 * 35.170.111.151 * 52.4.9.203 | HTTP/HTTPS | | 53 | TCP & UDP | Outbound\* | Communication to Domain Name Server |
| \* Return traffic must be enabled. \*\* The maximum recommended throughput per port is 1Gbps. If more throughput is expected through the Broadcaster, additional ports for the Zixi protocol can be defined on the [General](https://zixidocumentation.atlassian.net/wiki/spaces/116/pages/4775778220/General) page under the **Settings** tab. \*\*\* 7077 and 7088 use DTLS encryption For the ZEC operating as a receiver device, the following ports must be opened on your Firewall(s) as described below: # Network Settings for ZEC as a Receiver Device | Port | Type | Direction | **Description** | Protocol | | --------------------- | --------------- | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | | 2077/7077
\*\*\* | UDP | Outbound\* | Pull input from a Zixi Broadcaster or AWS MediaConnect | Zixi | | 1935 | TCP | Inbound\* | Push output to CDN origin server or RTMP enabled software | RTMP | | 7777 | TCP | Inbound\* | Pull output from HTML5 video player or CDN caching software | HLS or DASH | | 4444 | TCP | Inbound\* | Web management UI | HTTP | | 80/443 | TCP

| Outbound\* | Communication to Zixi License server -
[license.zixi.com](http://license.zixi.com/), [license2.zixi.com](http://license.zixi.com/)
* 52.72.218.41 * 34.195.97.223 * 3.140.62.221 * 3.137.16.26
ZEN Master Backend Servers
* 18.210.103.157 * 23.20.44.73 * 34.200.88.233 * 34.238.1.65 * 35.170.111.151 * 52.4.9.203 | HTTP/HTTPS | | 53 | TCP & UDP | Outbound\* | Communication to Domain Name Server |
| | 22 | SSH | Outbound\* | ZEN Master to customer's io.zixi.com server
Note: This is an outbound-only, private key authenticated, SSH tunnel - no inbound rules are required | | \* Return traffic must be enabled. \*\* The maximum recommended throughput per port is 1Gbps. If more throughput is expected through the Broadcaster, additional ports for the Zixi protocol can be defined on the [General](https://zixidocumentation.atlassian.net/wiki/spaces/116/pages/4775778220/General) page under the **Settings** tab. \*\*\* 7077 and 7088 use DTLS encryption **iptables example rules when the listening port is UDP 2088:** ```bash iptables -A INPUT -p udp --dport 2088 -j ACCEPT iptables -A OUTPUT -p udp --sport 2088 -m state --state ESTABLISHED -j ACCEPT ``` **iptables rules example, with target port 2088:** ```bash iptables -A OUTPUT -p udp --dport 2088 -j ACCEPT iptables -A INPUT -p udp --sport 2088 -m state --state ESTABLISHED -j ACCEPT ``` [title] Configuring an Input Stream with Multicast Transmission [path] Zixi Multicast Deployment Guide/ Multicast streams are pulled from the Zixi Broadcaster or ZEC by the various end-points/receivers. To allow the pulling of a specific channel, you need to configure the Input stream to enable transmission as multicast. The input stream (coming from the origin can be any of the supported stream types (e.g. Push, Pull, UDP, File, RTMP, HLS, TS over HTTP, RIST). In the consumption segment there are a variety of devices that can receive the Zixi-protected stream (e.g. ZEC). This receiving device will be configured to listen to the stream in order to pull it from the Zixi Broadcaster. Since the specific stream has been configured in the Zixi Broadcaster to *“Transmit as multicast”*, the stream will be automatically transmitted to the receiving device. The following instructions describe the process of configuring the input stream in Zixi Broadcaster, but they do not include all the relevant fields and steps to configure an input stream, just the ones that are specific for the configuration of a multicast input stream. For more information regarding additional settings, please refer to the [Zixi Broadcaster User Guide](docId\:JGwIXYN936aeZmonZLERn). **To configure an input stream with multicast transmission:** ::::WorkflowBlock :::WorkflowBlockItem In **Zixi Broadcaster**, go to **Inputs**. ::: :::WorkflowBlockItem Click the **+New Input** The **Add a new input stream **window is displayed. ::: :::WorkflowBlockItem In the **Stream ID** field, enter the unique name for the input stream (case-sensitive string). ::: :::WorkflowBlockItem In the **Max Outputs** field, enter the maximum concurrent connections to this stream. Default: Unlimited. ::: :::WorkflowBlockItem Select any of the stream types (radio buttons) – **Push**, **Pull**, **UDP**, **File**, **RTMP**, **HLS**,** TS over HTTP, RIST**, according to the incoming stream type. ::: :::WorkflowBlockItem Under **Stream Parameters**, enter the various parameters to configure the stream (see user guide for more details). ::: :::WorkflowBlockItem Select the **Transmit as multicast** ::: :::WorkflowBlockItem Do one of the following: 1. If you wish to enable full Unicast streaming as a fallback option when the multicast connection fails – DO NOT select the **Multicast Only **checkbox. 2. If you want to enable multicast only without the unicast fallback option, select the **Multicast Only** checkbox. The unicast error correction will be still enabled. ::: :::WorkflowBlockItem Configure additional parameters as necessary and click **OK**. The multicast stream is available for streaming. Since the stream will be pulled, you don't need to specify an output stream. ::: :::: [title] Enabling Multicast Settings [path] Zixi Multicast Deployment Guide/Configuring the Contribution/Distribution Segment for Multicast Streaming/ Multicast streaming is disabled by default and should be enabled. It is highly recommended to change the default multicast address to a different range that does not conflict with another Zixi Broadcaster, ZEC or Multicast Broadcaster range on your network. :::hint{type="warning"} Make sure your network supports multicast before enabling multicast settings in Zixi Broadcaster/ZEC ::: **To enable multicast settings:** :::::WorkflowBlock :::WorkflowBlockItem In **Zixi Broadcaster/ZEC**, go to **Settings > Multicast Pool.** The **Multicast Pool** screen is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/n-DvTyrdZYCzlO5IqM2Qi_image.png" size="80" width="995" height="467" position="center" showCaption="false"} ::: :::WorkflowBlockItem Under **Configuration**, select the **Enabled** ::: :::WorkflowBlockItem In the **Address** field, enter a multicast IP range in CIDR format. For example, type 225.5.0.0 / 16 configures the following multicast address range: 225.5.0.0 \~ 225.5.255.255. This is the multicast IP address range that the Zixi Broadcaster/ZEC will use to stream the various streams. Multicast addresses are not related to a specific stream in a static manner. Instead, each of these multicast addresses is dynamically allocated to the various input streams. All streams will use the same port (default: 5000) and use the consecutive IP within the range (e.g. 225.22.0.0, 225.22.0.1, etc.). ::: :::WorkflowBlockItem In the **Port **field, enter the port that will be shared by all the members of the multicast pool. Default: 5000. ::: :::WorkflowBlockItem In the **NIC** field, select the network card to use for the outgoing multicast traffic. ::: :::WorkflowBlockItem In the **TTL** field, enter the Time To Live. ::: :::WorkflowBlockItem Click **Apply**. The following dialog is displayed: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/szYxlZDcLyxKQyfiUlsv0_image.png" size="50" width="816" height="382" position="center" showCaption="false"} ::: ::::WorkflowBlockItem Click **Restart Now** or **Restart Later**. :::hint{type="warning"} **Warning** Schedule downtime before restarting if running other production streams on same Zixi Broadcaster or ZEC server. ::: :::: ::::: / [title] Configuring the Input Stream on Zixi Receiver [path] Zixi Multicast Deployment Guide/Configuring the Consumption Segment for Multicast Streaming/ Zixi Receiver will connect to the Zixi Broadcaster to pull the Input stream that has been configured in the Zixi Broadcaster. When this connection is established, the output stream will appear automatically in the Zixi Broadcaster. :::hint{type="info"} Stream names are case sensitive and must be identical. ::: The following instructions describe the process of configuring the input stream in Zixi Receiver, but they do not cover all the relevant fields and steps to configure an input stream. For more information regarding additional settings, please refer to the **Zixi Receiver User Guide**. **To configure an input stream on Zixi Receiver:** ::::WorkflowBlock :::WorkflowBlockItem In the Zixi Receiver Navigation menu, click the **Inputs** ::: :::WorkflowBlockItem In the Menu bar, click **New Input**. The **Stream details** screen is displayed: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/XhQ9DxfVv983I1sh4LgfC_image.png" size="50" width="410" height="447" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Input Name** field, type the *exact same stream name* (case sensitive) that was used during the configuration of the Input in the Zixi Broadcaster. ::: :::WorkflowBlockItem Select the **Pull** radio button. ::: :::WorkflowBlockItem In the **Host **field, type the host name or IP address of the Zixi Broadcaster. ::: :::WorkflowBlockItem In the **Port** field, type 2077 (default port). ::: :::WorkflowBlockItem Fill in additional parameters as needed. ::: :::WorkflowBlockItem Click **OK**. ::: :::: [title] Configuring the Contribution/Distribution Segment for Multicast Streaming [path] Zixi Multicast Deployment Guide/ This section provides instructions on how to configure Zixi Broadcaster/ZEC (which is located in the contribution/distribution segment) to enable Zixi-protected multicast streaming. - [Enabling Multicast Settings](docId\:y1_zPZMZSZvKO1ZA7nfcF) - [Enabling File Transfer & VOD Settings](docId\:rQbZ3WTXnR_mYW84i0ne8) - [Enabling Live Protocols Settings](docId\:Uo2RKedn6dZ2JI_Up5Ewr) [title] Enabling Live Protocols Settings [path] Zixi Multicast Deployment Guide/Configuring the Contribution/Distribution Segment for Multicast Streaming/ The relevant live protocols should be enabled. **To enable relevant Live Protocols settings:** :::::WorkflowBlock :::WorkflowBlockItem In **Zixi Broadcaster or ZEC**, go to **Settings > Live Protocols**. The **Live Protocols** screen is displayed: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/rcBACItY28DCA6ZC-Ss2B_image.png" size="80" width="1149" height="871" position="center" showCaption="false"} ::: :::WorkflowBlockItem Ensure the relevant protocol checkboxes are selected. For example, if you want to output HLS, select the **Enable HLS** ::: :::WorkflowBlockItem Click **Apply**. The following dialog is displayed: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/nJIBu0fu_jkMcNU2Y4K1W_image.png" size="50" width="816" height="382" position="center" showCaption="false"} ::: ::::WorkflowBlockItem Click **Restart Now** or **Restart Later**. :::hint{type="warning"} **Warning** Schedule downtime before restarting if running other production streams on same Zixi Broadcaster server. ::: :::: ::::: [title] Zixi Multicast Deployment Guide [path] / Zixi supports multicast streaming to a group of interested receivers in a single transmission. The solution enables either end-to-end protection of the stream using Zixi’s transport stream protocol or non-Zixi protected multicast streaming via HLS. This deployment guide focuses on end-to-end Zixi-protected multicast streaming.  ## Advantages of end-to-end Zixi protection The Zixi protocol is a content and network-aware protocol that dynamically adjusts to varying network conditions and employs error correction techniques for error-free video streaming over IP. This dynamic mechanism provides the following advantages in real-time video streaming: - Low end-to-end latency - Removes jitter - Recovers and re-orders packets - Smooths video delivery - Regenerates video to its original form ** ** ## Zixi-protected multicast streaming As part of the Zixi-protected multicast streaming the Zixi Broadcast sends the stream to multiple clients using a single multicast IP address. The interested clients pull the data from the multicast stream, while the error correction is performed for each client individually via unicast UDP. This allows for the best of both worlds, on one hand the ability to use the bandwidth-efficiency of the multicast streaming, while on the other hand you can enjoy the Zixi protection of the stream and all the advantages mentioned above. - [Deployment Architecture](docId\:vJOPK0h_relK15Qmq8vJr) - [Deployment Requirements](docId\:qdjpC3j_To6KvxtejxJ_2) - [Configuring the Contribution/Distribution Segment for Multicast Streaming](docId\:Rhe1AglHZfy-TZeO_vT9g) - [Configuring an Input Stream with Multicast Transmission](docId\:zPeviKXrr51P362Bsr-dD) - [Configuring the Consumption Segment for Multicast Streaming](docId\:aVWG8QJomUpKowvLHBMBs) - [Troubleshooting](docId:5n9kMykVcd9LS8FejUuEf) [title] Configuring the Consumption Segment for Multicast Streaming [path] Zixi Multicast Deployment Guide/ In the consumption segment the endpoints/receivers connect to the Zixi Broadcaster to pull the input stream. The configuration of the connection to the Zixi Broadcaster is exactly the same as a regular stream. The only difference is that since the stream has been configured as *“Transmit as multicast”, *the Zixi Broadcaster will redirect the request to a multicast address. If the multicast connection does not succeed and the input stream has NOT been marked as “multicast only”, the entire transmission of the stream will fall back to Unicast. In any case during multicast transmission If there are errors in the transmission, the error correction will be transmitted in UDP unicast directly to the specific device that suffered the error. This section provides instructions on how to configure a Zixi Receiver (which is located in the contribution/distribution segment) to pull the Zixi-protected multicast stream that has been configured in the previous section. In addition, this section also provides instructions on how to configure a VLC player, which includes the Zixi Plugin, to pull the Zixi-protected multicast stream that has been configured in the previous section. - [Configuring the Input Stream on Zixi Receiver](docId\:rzL-HX5Jo-uWFHPbJJ8xL) - [Configuring the Input Stream on VLC Player](docId\:d7hbmDLpG81EGw-zEuwL4) [title] Streaming a File to a Local Zixi Feeder or Broadcaster [path] Zixi VLC Plugin Setup Guide/Operation/ VLC can be used to stream an encapsulated MPEG Video file from a local disk to the Zixi transport platform. In order to stream a local file to a local Zixi Feeder, you must create an Input stream on the Zixi Feeder and then configure VLC Player to accept this stream. ## Zixi Feeder Configuration **To create an Input Stream on Zixi Feeder running on the local host:** 1. Access the local Zixi Feeder's management console through a web browser by entering the following URL: 127.0.0.1:4200 2. In the Main Navigation bar, click Inputs. 3. Click the **New Input** button. 4. In the** Input Name** field, enter a name for the input. 5. In the** Input Source** field, select **UDP**. 6. In the **NIC** field, select **127.0.0.1** (local host). 7. In the **Port** field, enter a non-conflicting network port. 8. Click OK. A new UDP input stream is created. ## VLC Player Configuration **To configure VLC Player:** ::::WorkflowBlock :::WorkflowBlockItem Open VLC Player ::: :::WorkflowBlockItem On the Main Menu, click **Media**. Sub-menu options are displayed. ::: :::WorkflowBlockItem Click **Stream**. The **Open Media** screen opens. ::: :::WorkflowBlockItem Under the **File** tab, click the **Add** button and select the file you wish to stream. ::: :::WorkflowBlockItem Select the "Show more options" checkbox at the bottom. ::: :::WorkflowBlockItem Click the **Stream** button. The **Stream Outpu**t wizard opens ::: :::WorkflowBlockItem Click **Next**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/btEr1EPhnk5KdGpx05vgj_image.png" size="80" width="741" height="397" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **New Destination** drop down list, select **UDP (legacy)**. ::: :::WorkflowBlockItem Click **Add** The UDP tab is added: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/lwgGHlIFAo-B9gPKCt5Pk_image.png" size="80" width="741" height="397" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Address** field, enter 127.0.0.1 (local host). ::: :::WorkflowBlockItem In the **Port** field, enter the port number matching the Zixi Feeder input port ::: :::WorkflowBlockItem Click **Next**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/jd10ieIm1bs-ZOBA8_4e1_image.png" size="80" width="741" height="397" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the Profile drop-down list, select **Video – H.264 + MP3 (TS)**. ::: :::WorkflowBlockItem If needed, you can further edit the codec parameters with the ‘**Edit Selected Profile**’ button. ::: :::WorkflowBlockItem Click **Next**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/MijBkWSYerFqC-sOBecU4_image.png" size="80" width="741" height="397" position="center" showCaption="false"} ::: :::WorkflowBlockItem Ensure the **Stream all elementary streams** checkbox is selected. ::: :::WorkflowBlockItem Click **Stream**. The VLC player begins streaming. ::: :::: Simultaneously you should see the stream connect and show positive bitrate in the Zixi Feeder Inputs list: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/aa4fsh2k0naGpzRGjvO9h_image.png" size="80" width="967" height="41" position="center" showCaption="false"} To play a UDP stream to a networked Feeder, replace the 127.0.0.1 output IP address with the IP or resolvable name of your target Feeder or Broadcaster. [title] Streaming Standard UDP from a Local Zixi Receiver [path] Zixi VLC Plugin Setup Guide/Operation/ To play a Zixi stream already being pulled to a broadcaster that is local to your machine, you must first push the stream from your local Zixi Receiver or Broadcaster to the local host network by configuring the following parameters: | Parameter | Value | | ------------------- | ------------------------------------------------------------------------------------------- | | Type | UDP | | Primary Source | Select the desired input | | Host | 127.0.0.1 | | Port | Enter an available port (do not to use a port that conflicts with other traffic), e.g. 6000 | | NIC | 127.0.0.1 | | TTL | 1 | | PCR Smoothing \[ms] | 0 | | RTP | Unchecked | Once you are streaming to the localhost, [Open VLC to play ](https://zixidocumentation.atlassian.net/wiki/spaces/ZVPSG/pages/7667747/Playing+a+Zixi-enabled+Stream)a standard UDP stream from the same local host and port. **To play a UDP stream:** 1. Open VLC Player 2. On the Main Menu, click **Media**. Sub-menu options are displayed. 3. Click **Open Network Stream**. 4. In the URL field, enter a UDP stream URL (e.g. udp\://@127.0.0.1\:your\_specified\_zixi\_port) 5. Click **Play**. [title] Installing the VLC Player and the Zixi VLC Plug-In [path] Zixi VLC Plugin Setup Guide/Installation and Setup/ To install Zixi VLC plug-in, you must first download and install the VLC player. **To download and install VLC Player:** 1. Download the VLC player version from the following URLs: - Windows - [http://www.videolan.org/vlc/download-windows.html](http://www.videolan.org/vlc/download-windows.html) - Mac - [http://www.videolan.org/vlc/download-macosx.html](http://www.videolan.org/vlc/download-macosx.html). 2. Run installer and follow the default Installation settings 3. Exit the VLC player. **To install the Zixi VLC Plug-in:** 1. Download the Zixi VLC Plug in from: - [https://portal.zixi.com/free/zixi\_vlc\_plugin-win-latest.zip](https://portal.zixi.com/free/zixi_vlc_plugin-win-latest.zip) - [https://portal.zixi.com/free/zixi\_vlc\_plugin-mac-latest.tar.gz](https://portal.zixi.com/free/zixi_vlc_plugin-mac-latest.tar.gz) 2. Ensure that VLC is not running before installing the Zixi VLC Plug-In. 3. Double click the Zixi VLC plug-In executable. The setup wizard automatically installs and configures the Zixi VLC Plug-In. 4. Click **Close** when the setup wizard completes. **Next Steps: ** [Zixi Plug-In Preferences Configuration](docId:4BmaH4pd2KPQnWSZqD46x) [title] Special Playback Controls for Monitoring Live Video [path] Zixi VLC Plugin Setup Guide/Operation/ While traditional video contains a single video track and a pair of stereo audio channels, VLC is also able to playback complex video containers carrying multi-camera video, multiple audio tracks and metadata elements such as closed captioning. The list below includes special VLC controls that are particularly useful for monitoring the individual audio and video elements of the source content itself, including artifacts and issues introduced at, or even prior to, the source video encoding. For example, missing metadata, inverted audio pairs, and more. ## Video Controls | Control | Details | | ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Video Track | Disable video or specify which embedded camera element to display at any time | | Full Screen | Toggle between window frame and full screen | | Zoom | A zoom setting of 1:1 ‘Original’ is advised for full image monitoring | | Aspect Ratio | The ‘Default’ setting displays the true aspect, and can highlight an incorrect setting in the source | | Crop | Ensure ‘Default’ is set, any local cropping is outside of the delivered stream | | DeInterlace | Set to ‘Off’ to view non-interlaced source, or to determine if the video channel is interlaced as expected. Once confirmed, Set ‘On’ or ‘Automatic’ for general monitoring of interlaced video on an LCD screen. | | DeInterlace Mode | When in ‘DeInterlace’ mode, a range of software post-processing methods are available. Note that any local post-processing effects are subjective and do not represent the source. | | Post Processing | Ensure ‘Disable’ is set, local post-processing can affect perception of the true source. | | Take Snapshot | This tool is useful for providing your support contact with a screenshot when describing a video artifact. | **** ## Audio Controls | Control | Details | | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Audio Track | Use this control to disable audio completely or specify which embedded audio element to play at any time. | | Audio Device | Default to the on-board sound system or select external audio monitoring equipment if available. | | Stereo Mode | Use this control to toggle the stereo and monitor left and right audio channels individually. | | Visualizations | VLC provides software visualizations that can help with audio monitoring such as the ‘Scope’ and ‘VU Meter’. Set to ‘disable’ or select a visualization to enable the visualization window. | | Volume | Ensure ‘Mute’ is turned off if you are monitoring audio. | **** ## Subtitle Controls | Control | Details | | ---------- | ----------------------------------------------------------------------------------------------------------- | | Sub Track | Use this setting to disable caption, or specify a specific closed captioning track to overlay on the video. | **** [title] Stream Information and Metrics [path] Zixi VLC Plugin Setup Guide/Operation/ VLC provides tools for viewing statistical information about a live stream. This includes both metadata and codec information within the source video itself, such as frames-per-second or audio codec specification, as well as details of the live stream fidelity, such as current video bitrate or the number of dropped frames. ## Video Codec Information Video codec information is created at the source and is not introduced or affected by the Zixi transport protocol. This information can help ensure the source content adheres to the desired video and audio specification. **To view video codec information:** - In VLC's Main Menu, click **Tools** menu and select **CODEC Information**. A window appears displaying a dropdown for each elementary stream and additional data by type: | Data Type | Details | | --------- | --------------------------------------------------------------------------------------------- | | Video | Original ID
Codec
Resolution (Source)
Resolution (Display)
Decoded Format | | Audio | Original ID
Codec
Language
Channels
Sample rate | | Subtitle | Codec
Description | ## Custom Metadata Zixi will pass through any metadata found in the source, including custom metadata that was injected into the source stream wrapper. **To view custom metadata:** - In VLC's Main Menu, click **Tools** menu and select **Media Information**. A window appears displaying current media information. - Click the **Metadata** tab. **** ## Video and Zixi Streaming Statistics VLC’s statistical information provides live data on end-to-end stream fidelity as well as the QoS between your VLC player and the Zixi broadcaster from which VLC is pulling the stream. **To view statistics:** - In VLC's Main Menu, click **Tools** menu and select **Media Information**. A window appears displaying current media information. - Click the **Statistics** tab. A live update panel displays the following information when a stream is active: | Data Type | Details | | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Audio | Decoded (blocks)
Played (buffers)
Lost (buffers) | | Video | Decoded (blocks)
Played (buffers)
Lost (buffers) | | Input/Read | Media Data Size (KiB)
Input bitrate (kb/s)
Demuxed data size (KiB)
Content bitrate (kb/s)
Discarded (corrupted)
Dropped (discontinued) | | Output/Written/Sent | Sent (packets)
Sent (KiB)
Upstream rate (kb/s) | [title] Installation and Setup [path] Zixi VLC Plugin Setup Guide/ - [System Requirements](docId:0LrXm-lyEyRSRViagPjJW) - [Installing the VLC Player and the Zixi VLC Plug-In](docId\:xCta6Jsvuk7v69VXPn-dU) - [Zixi Plug-In Preferences Configuration](docId:4BmaH4pd2KPQnWSZqD46x) [title] Playing an Encrypted Zixi Stream [path] Zixi VLC Plugin Setup Guide/Operation/ Zixi streams can be encrypted using 128, 192 or 256 Bit AES encryption keys. To play an encrypted Zixi stream in VLC, you must be provided with the appropriate decryption key (via your administrator) of the following format: 876e04a9f07b4b10iou4350943iu45656dsc56095ikjkjkre4207d3822e77dea Once added the VLC Zixi Plug-In Decryption Key is global to all streams, and must be change manually if the user pulls a Zixi stream from a different source or a stream encrypted with a different key. **To play an encrypted file:** 1. Access the [Zixi VLC plug-in preferences](https://zixidocumentation.atlassian.net/wiki/spaces/ZVPSG/pages/8159245/Zixi+Plug-In+Preferences+Configuration)**.** 2. In the **Decryption Key** field paste your decryption key. 3. Click **Save** and close the VLC player. 4. Restart VLC for your changes to take effect. 5. Play the encrypted Zixi stream as normal by following the [Playing a Zixi-enabled Stream](https://zixidocumentation.atlassian.net/wiki/spaces/ZVPSG/pages/7667747/Playing+a+Zixi-enabled+Stream) procedure. [title] Playing a Zixi-enabled Stream [path] Zixi VLC Plugin Setup Guide/Operation/ **To play a Zixi-enabled stream:** 1. Open VLC Player 2. On the Main Menu, click **Media**. Sub-menu options are displayed. 3. Click **Open Network Stream**. 4. In the URL field, enter a Zixi stream URL, which includes the following structure: - Zixi://\:\/\ For example: [zixi://demo.zixi.com:2077/sample1](#) - **Remote-ID configuration** - if you would like to use a specific username/session (password), for example, in case the broadcaster is configured with authorization or you already have a predefined output with specific remote-id, you can do so by adding username\:password to the zixi URI. for example: [zixi://user\:pass@host\:port/stream](#) 5. Click **Play**. [title] Downloading the App [path] Zixi On Air Pro Guide/ To begin streaming, download the Zixi On Air Pro app from the Apple App Store. ::::WorkflowBlock :::WorkflowBlockItem On your iPhone or iPad, open the App Store. ::: :::WorkflowBlockItem Search for **Zixi On Air Pro **app. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/b8C_EMFiXallNcuBdDs2G_.blob" size="50" width="388" height="777" position="center" darkWidth="388" darkHeight="777" showCaption="false"} ::: :::WorkflowBlockItem Tap the **GET** button. ::: :::WorkflowBlockItem Confirm the download, and open the app. ::: :::: :::hint{type="info"} During the installation, pop-up windows will ask you to allow Zixi On Air Pro to use your device's camera and audio input. You must allow access to run the app. ::: [title] On Air Pro Requirements [path] Zixi On Air Pro Guide/ This document applies to On Air Pro Version 1.0.0 or later. ## Device Requirements ### iOS iPhone requires iOS 15.3 or later. iPad requires iPadOS 15.3 or later. ### Android TBD ## Additional Requirements To stream video from your device using On Air Pro, you need the following: - A mobile device with either a cellular network or Wi-Fi connection, or both - Access to a Zixi Broadcaster or ZEN Master. :::hint{type="info"} If you have both Wi-Fi and cellular connections, you can enable Bonding to use both connections for video streaming. ::: [title] Streaming using ZEN Master [path] Zixi On Air Pro Guide/ Zixi On Air Pro is a mobile contribution solution that allows you to stream video from your Apple device (iPhone, iPad) or Android device (mobile phone, tablet) to a Zixi Broadcaster by creating a new **OnAir Source** in **ZEN Master** and linking it to your device. ## Workflow - Create an OnAir Source - Add a New Connection - Start Streaming ## Create an OnAir Source ::::WorkflowBlock :::WorkflowBlockItem In a web browser, navigate to [https://.zen.zixi.com](https://\{youraccount}.zen.zixi.com) ::: :::WorkflowBlockItem In the left navigation, select **Sources**. ::: :::WorkflowBlockItem Select **+Add**. ::: :::WorkflowBlockItem Select **Zixi**. ::: :::WorkflowBlockItem Enter the following: - **Name** – Enter a unique name for the Source - **Tags** - Add Tags to control access to this Source - **Mode** – Leave this as **Push** - **Application** – Select **OnAir** - **Ingest Cluster** – Select from the drop-down list one of the available Ingest Clusters as the destination for the Source. - **Target Broadcaster** – 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. - **Source Password** – Optional: Add a password to use with the On Air app ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/wuuZKAqsz_SYYqY4qCXAJ_.blob) ::: :::WorkflowBlockItem For information about the other fields for this Source, see [Adding a Zixi Source – OnAir](docId\:n4zdGFRpvVE3Kn4ek0z82). ::: :::WorkflowBlockItem Select **Save** to create the Source. ::: :::WorkflowBlockItem Once you have created the Source, find it in the display list select it and In the top right “kebab” icon, select **Config**. ::: :::WorkflowBlockItem ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/GWsMSRmMz4ccm8JXWkezc_.blob) ::: :::WorkflowBlockItem Enter an email address to send the Source configuration to your Apple or Android device. ::: :::WorkflowBlockItem Click outside the input area and click **Send**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/5G1zqeNJhvjSH2_1S4jnA_.blob) ::: :::WorkflowBlockItem Close the **Configuration** window. ::: :::: ## Add a New Connection ::::WorkflowBlock :::WorkflowBlockItem Return to your Apple or Android device. ::: :::WorkflowBlockItem Open the email from [mcr@zixi.com ](mailto\:mcr@zixi.com)or [notifications@zen.zixi.com](mailto\:notifications@zen.zixi.com) ::: :::WorkflowBlockItem In the email, click the **Open in OnAir Pro** button. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/GVLpfCG9MzqTpfAEHyNTW_image.png) ::: :::WorkflowBlockItem Once you tap the button, you will be directed to a Zixi landing page, where you can either open the OnAir Pro app or get the app from the App Store. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/CTfRG78SLRuQgj2UKgaah_image.png) ::: :::WorkflowBlockItem In the OnAir Pro app, go to **Settings > Connections,** tap **+** and fill in the following fields: - **Stream ID** - **Host** - **Port** – You can use either: - **2088** – Non-encrypted - **7088** – Protected by DTLS - **Password** (If you entered one) ::: :::WorkflowBlockItem Enter the following: - **Name** – Connection name - **Ignore DTLS Certificate Errors** – Turn on to enable - Required with port 7088 and a fully qualified domain name ::: :::WorkflowBlockItem Tap **Add**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/tyeUT_w1VzweNMwpZJWbZ_.blob) ::: :::: ## Start Streaming ::::WorkflowBlock :::WorkflowBlockItem In the On Air Pro app, navigate back to the camera. ::: :::WorkflowBlockItem Tap the red (record) button to start streaming. ::: :::: In ZEN Master, you should now see your stream details. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/RNvn3kiFAEV2KdDGlOfMB_.blob) [title] Camera Screen [path] Zixi On Air Pro Guide/ The application's Camera screen shows the device camera view and presents several controls for shooting video. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ViDYtAH2kajSroZKnuDGP_image.png) | **Icon** | **Description** | | --------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Mic: on/off** | Tap the microphone button to toggle it on and off. | | **Settings** | Tap the settings icon to configure:
* Connections * Video settings * Audio settings * Network settings
For details, see [On Air Pro Settings](docId\:cbonagrhNB4rIv7aWxSAm). | | **Connection name** | The current Connection name followed by the Stream ID. | | **Status** | The status bar shows when the video stream is online or offline. It also shows how long the stream has been active. | | **Camera flip** | Tap the camera flip button to switch between the front and back cameras. | | **Start/stop stream** | When in ‘Offline’ mode, tap the red circle to begin streaming. A red square will appear in the circle.
Tap the red square to stop streaming. | | **More options** | Tap the "More options" (meatball) menu to see additional options. Tap the flash icon to show lighting options:
* Turn flash on * Turn flash off * Turn on flash auto mode | | **Resolution** | The resolution bar shows the selected **Quality** **settings**, including the selected resolution and frame rate. The settings are configured in **Video Settings **(see [On Air Pro Settings](docId\:cbonagrhNB4rIv7aWxSAm)). | [title] Viewing your Video Feed with the Zixi VLC Plug-In [path] Zixi OnAir Guide (deprecated)/Viewing a Live Video Stream/ The outbound video stream can be viewed by pulling the stream directly from the target Zixi Broadcaster. To do this, you require both the VLC Media Player and the Zixi VLC Plug-In. **To play a Zixi-enabled stream:** 1. Download the VLC player from the following URL - [http://www.videolan.org/vlc/#download](http://www.videolan.org/vlc/#download). 2. Run installer and follow the default Installation settings. 3. Ensure that VLC is not running before installing the Zixi VLC Plug-In. 4. Double click the Zixi VLC plug-In executable (e.g. zixi\_vlc\_plugin-win32-1.9.0.21770.exe). The setup wizard automatically installs and configures the Zixi VLC Plug-In.      5. Click **Close** when the setup wizard completes. 6. Open VLC Player. 7. On the Main Menu, click **Media**.  Sub-menu options are displayed.  8. Click **Open Network Stream**. 9. In the **URL **field, enter a Zixi stream URL, which includes the Zixi Broadcaster details and channel name, provided by your administrator (e.g. zixi://demo.zixi.com/clocks). 10.  Click **Play**. Your video stream should begin after a short pause. See the *Zixi VLC Plugin Setup* *Guide* for more details.** ** [title] Capturing a "Store and Forward" stream [path] Zixi OnAir Guide (deprecated)/Capturing a Live Stream/ Store and Forward records the stream to the mobile device's storage and then uploads it to Zixi Broadcaster as a file (not as a live stream). This allows you to configure a higher bitrate stream and transmit it (while recording) to the Zixi Broadcaster. :::hint{type="info"} This feature is not supported in Android Lollipop (5.0 – 5.1.1) or higher. ::: **To capture a Store and Forward stream:** 1. In the target **Zixi Broadcaster**, do one of the following: - Create a **Push Input** which will be used to stream from the OnAir app. The details of this input stream will be entered into the OnAir Settings, as described below. - If you don't want to create the Push Input in advance, go to **Settings** **> Live Protocols** and select the **Allow Automatic HTTP Push input **for Zixi streams and** Allow Automatic RTMP Input **for RTMP streams.     2\. Specify the target server details as described in the [Capturing a live stream](https://zixidocumentation.atlassian.net/wiki/spaces/ZOAG/pages/1513947174/Capturing+a+Live+Stream) section. 3\. In the **Settings** screen, enable the **Store and Forward** setting. 4\. Specify additional settings as described in the [Settings Screen](https://zixidocumentation.atlassian.net/wiki/spaces/ZOAG/pages/1513947147/OnAir+Settings+Screen) section. 5\. On the main screen, click the **Store and Forward record** button. ::Image[6. If you have stopped the recoding while the stream is in progress of uploading, the **Uploads **screen will open and you will be able to see the upload progress.]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/j0PrKr25efBPziqQrlWBG_image.png" size="30" width="625" height="1080" position="center" showCaption="false"} The stream will be upload while it is recording. 6\. If you have stopped the recoding while the stream is in progress of uploading, the **Uploads **screen will open and you will be able to see the upload progress.   [title] Zixi OnAir: Downloading the App [path] Zixi OnAir Guide (deprecated)/Preparing for Use/ Download the appropriate app and install it on your device, as described below. ## iOS Zixi *OnAir* for iOS is available at the AppStore. You can download it from: [https://itunes.apple.com/us/app/zixi-onair/id859954998?mt=8](https://itunes.apple.com/us/app/zixi-onair/id859954998?mt=8) :::hint{type="info"} During the installation, pop-up windows will ask you to allow Zixi OnAir to use your device's camera and audio input. You must allow access in order for the app to run. ::: [title] Preparing for Use [path] Zixi OnAir Guide (deprecated)/ Before you can start using OnAir you need to configure your Zixi Broadcaster to receive an input stream from your OnAir app. Then, you must configure the app to send the stream to your broadcaster. :::hint{type="info"} It is possible to send the OnAir stream directly to an external RTMP server, in which case you don't need to set up a broadcaster. This chapter assumes that you intend to send the stream to a Zixi Broadcaster. ::: [title] Streaming a file from your device (iOS only) [path] Zixi OnAir Guide (deprecated)/Capturing a Live Stream/ You can stream a file (photo or video) from your device's gallery. **To stream a file:** ::::WorkflowBlock :::WorkflowBlockItem On the main screen, click the **Upload** button. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/B5gvo0J9PrBHV6K53HwHG_image.png" size="44" width="460" height="759" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Uploads** screen, click the **+ button**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/cD7ahqsZ7OZP74mSqR82v_image.png" size="80" width="2208" height="1242" position="center" showCaption="false"} ::: :::WorkflowBlockItem The file is upload immediately. You can pause the upload, by clicking the **Pause** button. ::: :::: [title] OnAir Settings Screen [path] Zixi OnAir Guide (deprecated)/ The application **Settings** screen provides entry fields for camera and streaming settings.  Tap each required row to enter a text value with the built-in keyboard or select from the scrollable list of available options provided. | **Setting** | **Description** | | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | ***Connection Settings*** |   | | **Protocol** | Select one of the following protocols:
* Zixi * RTMP * RIST (iOS) | | ***Zixi Protocol Settings*** |   | | **Broadcaster Name** | Specify the Zixi Broadcaster server name or URL. | | **Port** | Specify the destination port (to listen on for Push streams). Default: 2088. | | **Channel Name** | Specify the name of the channel, which will be displayed as an Input name in Zixi Broadcaster. If you have already specified the stream as an Input in Zixi Broadcaster, use the Input name as the Channel Name. | | **Password** | Optional. Specify a password string that can be used to authenticate that you are allowed to push this stream to the configured Zixi Broadcaster. | | **Latency** | Specify the maximum latency (delay) in milliseconds that is allowed. Larger values provide additional protection against network loss
Available options: 100, 200, 300, 500, 1000, 1500, 2000 (default), 3000, 4000, 6000, 8000 | | **WiFi + Cellular Bonding (iOS)** | - If disabled – the stream will be transmitted using one of the available methods (Wifi (preferred)/Cellular).  - If enabled – the stream will be transmitted using both Wifi and cellular. | | **Store and Forward (iOS)** | Enable this setting to record the stream to the mobile device and then upload it to Zixi Broadcaster as a file. This allows you to configure a higher bitrate and transmit it (while recording) to the Zixi Broadcaster. | | ***RTMP Protocol Settings*** |   | | **URL** | Specify the Stream URL of the RTMP server. | | **Stream Name** | Specify the unique name for the stream that the RTMP server expects at the other end of the connection. | | **Username** | Specify the username to authenticate on the RTMP server. | | **Password** | Specify the string that is used for authorization on the RTMP server. | | ***RIST Protocol Settings*** | * * | | **Broadcast Address** | Specify the Zixi Broadcaster IP address/URL. | | **Port** | Specify the destination port (to listen on for Push streams). Default: 2088. | | ***Video Settings*** | *** *** | | **Video Codec (iOS)** | **Select one of the following video codecs:**
**·         H.264**
**·         HEVC (appears on supported devices only - iPhone 7 and above)** | | **Camera Source** | Select one of the following camera options:
·         **Internal** – the mobile phone's internal camera.
·         **External – USB** - the camera is an external USB camera which is connected to the mobile device. | | **Frame Rate (Back)** | Select the frame rate in which video will be captured through the back camera of the device. The options labeled (varying) mean a range from 0 to the number indicated. For example, 30 FPS, is 30 frames per second, while 30 FPS (varying) is 0-30 frames per second. | | **Frame Rate (Front)** | Select the frame rate in which video will be captured through the front camera of the device. The options labeled (varying) mean a range from 0 to the number indicated. For example, 30 FPS, is 30 frames per second, while 30 FPS (varying) is 0-30 frames per second. | | **Quality** | The level of detail and video bitrate of recorded video.
Possible options:
·         240p 300kbps
·         360p 700kbps
·         480p 1300kbps
·         720p 3000kbps
·         1080p 5000kbps | | ***Store and Forward*** | *Enable this setting to record the stream to the mobile device and then upload it to Zixi Broadcaster as a file. This allows you to configure a higher bitrate and transmit it (while recording) to the Zixi Broadcaster.*
*Note: This feature is not supported in Android Lollipop (5.0 – 5.1.1) or higher.* | | **Bonding** | Select one of the following network bonding options:
·         No bonding – the stream will be transmitted using one of the available methods (Wifi (preferred)/Cellular). 
·         Bonding – the stream will be transmitted using both Wifi and cellular. | | ***Forward RTMP*** | This setting allows sending a Zixi-protected stream to Zixi Broadcaster and then Zixi Broadcaster automatically creates an RTMP output to the remote RTMP Server in the specified destination.
**Note:** Allow automatic RTMP option must be enabled on the Broadcaster. | | **URL** | Specify the Stream URL of the remote RTMP server. | | **Stream Name** | Specify the unique name for the stream that the RTMP server expects at the other end of the connection. | | **User Name** | Specify the username to authenticate on the remote RTMP server. | | **Password** | Specify the string that is used for authorization on the remote RTMP server. | | ***Advanced Settings*** | * * | | **Sampling Rate** | Specify the digital resolution of audio date sampled via the on-board microphone
Possible options:
·         48000 Hz
·         44100 Hz | | **Audio Bitrate** | Specify the maximum bitrate for the audio in kbps. The bitrate should be set after checking your available bandwidth.
Possible options:
·         256 kbps
·         160 kbps
·         128 kbps
·         96 kbps | | **Bitrate (kbps)** | Specify the maximum bitrate for the video in kbps. The bitrate should be set after checking your available bandwidth. | | **GOP Size (sec)** | Specify the GOP (Group of Pictures) length in seconds.
Possible options:
1-6 seconds. Default: 2 seconds. | | **Time Code Insertion** | Specify whether to insert a time code into the stream. |     [title] Viewing HLS Delivered by Zixi from a CDN Directly from the Target Broadcaster [path] Zixi OnAir Guide (deprecated)/Viewing a Live Video Stream/ If a CDN has been configured for large scale video distribution, your CDN provider or Administrator will present a standard HLS playback URL for testing or inserting into an app or web-based player. See the *Zixi Broadcaster User Guide* for more details on configuring your Broadcaster as a CDN origin server. [title] Viewing a Live Video Stream [path] Zixi OnAir Guide (deprecated)/ There are several ways to view the output of your Zixi On Air live video stream: - [Viewing your Video Feed with the Zixi VLC Plug-In](docId\:nZe1MFmOzuIEHjZpAVavO) - [Viewing Zixi HLS Directly from the Target Broadcaster](docId\:CjmzCsNH6eVWTaJQIEC2N) - [Viewing HLS Delivered by Zixi from a CDN Directly from the Target Broadcaster](docId:9NeG3Y3-9zDwVGaB-Rvt6) [title] Zixi OnAir Guide (deprecated) [path] / Zixi’s *OnAir* mobile app provides a mobile entry point to the Zixi Internet video transport architecture. The application allows users to stream live from an iOS or Android device (phone or tablet), while using the device's built-in camera to encapsulate the encoded video and audio and prepare them for transmission over standard Internet connections using Zixi’s UDP-based transmission protocol, RTMP, or RIST. The application works exclusively with a Zixi Broadcaster or ZEC, which enables high quality streaming and format conversion to HLS, HDS, MPEG-DASH, MPEG-TS and RTMP, and RIST so the live video can be watched on any device, decoded on professional decoder or published to a CDN. Zixi’s Transport Stream architecture deploys monitoring, control, and intelligence along the entire transmission path. It is uniquely designed to deliver the quality and reliability that enables live contribution from any device to a cloud or on premise version of Zixi Broadcaster. :::hint{type="info"} There is also an option to send the stream using RTMP or RIST protocol. You can also add an **additional** RTMP target while streaming to a Zixi Broadcaster with Zixi protocol. ::: *Zixi OnAir* can bond 3G/4G/5G and Wi-Fi connections to send the highest bit rate possible. Zixi’s software bonding capability delivers a high-quality stream even under degraded network conditions. *OnAir* has two modes of operation: - **Live Streaming** – streams content to the broadcaster in real time. The stream quality may be somewhat degraded based on the constraints of your network connection. - **Store and Forward** – records high quality video on your device and uploads it to the broadcaster without degrading the video quality. In this mode, the stream is not available for viewing in real time. The Zixi *OnAir* mobile app is ideal for live event producers and ENG workflows (sports/news) who would like to capture a breaking news story or alternative views of concerts, sports events, theater, or fan cutaways during live broadcast. ## Features - Uses internal mobile device camera - Full HD up to 1080p 6mbps (iOS), 1080p 5mbps (Android) - Aspect ratio selection - Fixed capture frame rate in SD resolutions - Multiple resolution options - up to 1920 x 1080 30fps (available options are device dependent) - Configurable video resolution, quality and transmission latency - In-camera video information and transmission statistics display - Transmit using Zixi Protected Transport Protocol, RTMP or RIST - WiFi + Cellular bonding (available on iOS) - Set transmission latency - Live Streaming and Store and Forward modes ## About this Guide This document explains the initial setup as well as operation of the OnAir app. The procedures described in [Configuring the Broadcaster](docId\:dTjnnaYl1vNxC-ualy-SX) are intended specifically for the administrator of the Zixi Broadcaster administrator. The other sections of the document are relevant also for the end user who will run OnAir on his/her mobile device. [title] Manual Method [path] Zixi OnAir Guide (deprecated)/Preparing for Use/Configuring the Broadcaster/ You can create either a Push input which uses Zixi protocol, or an RTMP input which uses RTMP protocol. **To add a Push Input to the Broadcaster:** ::::WorkflowBlock :::WorkflowBlockItem In Zixi Broadcaster, go to **Inputs**. ::: :::WorkflowBlockItem On the **Inputs** screen, click the **+ New Input** button. The **Add a new input stream** window is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/1LVgwJkcgpR9Mugzm04b__image.png" size="80" width="903" height="489" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Stream ID** field, enter a name that you will use to identify the stream sent from your OnAir app. (Make a note of the precise Stream ID (case sensitive). You will enter this as the *Channel ID* in the OnAir settings.) ::: :::WorkflowBlockItem In the stream type selection, select the **Push** radio button (default). ::: :::WorkflowBlockItem In the **Stream Parameters** section, if you would like to add a password in order to increase security, enter a password in the **Password** field. (*Make a note of the precise Password* (case sensitive). You will enter this as the *Password* in the OnAir settings.) ::: :::WorkflowBlockItem Configure additional settings as necessary. ::: :::WorkflowBlockItem Click **OK**. The “Input added” message appears on the top of the screen. ::: :::: The new Input is added to the Zixi Broadcaster and now appears in the list of streams available on the Inputs screen. The **Status** should be *Offline *(blue). ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/YU8VIOK_ryGxCAtN7MMyL_image.png" size="80" width="1167" height="324" position="center" showCaption="false"} **To add an RTMP Input to the Broadcaster:** ::::WorkflowBlock :::WorkflowBlockItem In Zixi Broadcaster, go to **Inputs**. ::: :::WorkflowBlockItem On the **Inputs** screen, click the **+ New** Input button. The **Add a new input stream** window is displayed. ::: :::WorkflowBlockItem In the **Stream ID** field, enter a name that you will use to identify the stream sent from your OnAir app. (Make a note of the precise Stream ID (case sensitive). You will enter this as the *Channel ID* in the OnAir settings.) ::: :::WorkflowBlockItem In the stream type selection, select the **RTMP** radio button. ::: :::WorkflowBlockItem In the **Type** field, select **Push**. ::: :::WorkflowBlockItem Configure additional settings as necessary. ::: :::WorkflowBlockItem Click **OK**. The new Input is added to the Zixi Broadcaster and now appears in the list of streams available on the Inputs screen. The **Status** should be *Offline* (blue). ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/g83yt49nCcEfcPpSOO6Zb_image.png" size="80" width="1168" height="286" position="center" showCaption="false"} ::: :::: [title] Zixi OnAir Guide: Requirements [path] Zixi OnAir Guide (deprecated)/ ## Device Requirements ### iOS iOS 8.1 or later. It is compatible with iPhone and iPad. This document is for running OnAir Version 13.1.35626 or later. ### ## Operational Requirements Zixi OnAir is designed to transmit live video to a pre-configured Zixi Broadcaster. In order to stream video from your device using OnAir, your device needs to have either a cellular network or Wi-Fi connection and you must have access to a Zixi Broadcaster that is running. :::hint{type="info"} If you have both a Wi-Fi and cellular connection, then you can use Bonding to use both connections for the stream transmission. ::: [title] Camera Screen [path] Zixi OnAir Guide (deprecated)/ The application Camera screen shows the view of the device camera, and presents several controls for shooting video. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/_ECTX3_hUFrvTG7nLBlfa_image.png" size="84" width="1017" height="414" position="center" showCaption="false"} **Zoom Control Slider (iOS only)** Slide the silver zoom circle up to zoom in, and down to zoom out. **Camera Flip Button** Tap the camera flip button to switch between the front and the back camera (if one is available). **Lightning Button (Torch Mode)** Tap the lighting icon to turn the cameras flash light on and off. **Record Button** When in ‘Ready’ mode, tap the green circle to enter ‘Shoot’ mode and begin streaming. The circle will turn red. Tap the red circle to stop shooting, the button will return to green. :::hint{type="info"} Ensure the target settings are correct before shooting. See [OnAir Settings Screen](docId\:nLLBm2Jjkl5uu2blCJWAL) ::: **Upload** The Upload button displays a list of files that have been uploaded, including Store and Forward streams.    **Status Bar** The status bar displays the following statistics and information when the device is in ‘Shoot’ mode - Current Stream uptime - Connection status - Current video Quality - Current Video Frame Rate - Zoom level (iOS only) - Current Video Bitrate :::hint{type="info"} When using a bonded connection (wifi + cellular), click on the Bit-rate label to view the stream statistics. ::: [title] Deleting and existing stream [path] Zixi Player Guide/ You can delete an existing stream. **To delete an existing stream:** ::::WorkflowBlock :::WorkflowBlockItem On the lower right-hand side, tap the **+** button. ::: :::WorkflowBlockItem Tap the **Edit** icon (top icon). ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/GNwpfsK_kx7M2sEx4EJWb_image.png" size="20" width="127" height="259" position="center" showCaption="false"} ::: :::WorkflowBlockItem Tap the trash icon next to the relevant stream. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/StWI4jVkF2tFmgGASYvYG_image.png" size="30" width="1080" height="996" position="center" showCaption="false"} ::: :::: [title] Zixi Player Guide [path] / The Zixi Player mobile app can play live video over IP in real-time with low latency. Zixi Player uses Zixi's own adaptive streaming protocol and is a first-ever adaptive bitrate player at sub-GOP latency. Zixi Player works exclusively with a Zixi Broadcaster. ## Features - Playback of Zixi Transport Protocol streams - Supports low-latency (sub-GOP latency) - Enables adaptive bitrate streaming - Enables opening streams directly from a browser - Prevents screen locking during playback - Enables decryption of encrypted streams ## Supported Codecs The player uses the existing hardware decoders on the device. Supported codecs for iOS: - Video: H264 and HEVC, progressive only - Audio: AAC, MP3, AC-3, Opus​ :::hint{type="info"} Interlaced video and MPEG1 Layer 2 audio are not supported. ::: Supported codecs for Android: - Video: H264; additional video codecs are dependent on the specific model. - Audio: AAC; additional video codecs are dependent on the specific model. **** [title] Zixi Player Guide: Downloading the App [path] Zixi Player Guide/ ## iOS Zixi Player for iOS is available on the AppStore You can download it from:  [https://apps.apple.com/us/app/zixi-player/id1338473787](https://apps.apple.com/us/app/zixi-player/id1338473787) ## Android Zixi Player for Android is available on Google Play You can download it from:  [https://play.google.com/store/apps/details?id=com.zixi.player\&hl=en](https://play.google.com/store/apps/details?id=com.zixi.player\&hl=en) Once downloaded, the Zixi Player Icon will appear on the device screen. Tap the  icon to open the application. [title] Editing an existing stream [path] Zixi Player Guide/ You can edit the settings of an existing stream. **To edit an existing stream:** ::::WorkflowBlock :::WorkflowBlockItem On the lower right-hand side, tap the **+** button. ::: :::WorkflowBlockItem Tap the **Edit** icon (top icon). ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/GNwpfsK_kx7M2sEx4EJWb_image.png" size="20" width="127" height="259" position="center" showCaption="false"} ::: :::: [title] Zixi Player Guide: Requirements [path] Zixi Player Guide/ ## Device Requirements ### iOS iOS 10.0 or later. Compatible with iPhone, iPad, and iPod touch. ### Android Android 4.3 (Jelly Bean) or later. [title] The Gathered Data from Zixi Platform Components [path] Alert Escalation and Notification Management Guide/ The Zixi Platform consists of software ZECs and Broadcasters and the streams that are transmitted between them using the Zixi protocol. Each system in the network maintains its current health statistics. In addition, streaming metrics are continually monitored by the Zixi Broadcaster. The following data is measured by the components and gathered by ZEN Master. ## System Health ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/fe2l1AAm2JfW2wceUDcQN_image.png) System Health metrics measure CPU and Memory usage and local disk and GPU statistics, wherever available. These measurements serve as an indicator for performance and to understand the available headroom. A CPU that becomes overworked, for example, could lead to issues that result in video degradation, but the Broadcaster itself will continue to stream per its configuration.   ## Stream Health Zixi Broadcaster monitors the health of active input and output streams. This includes gathering: - Connectivity data - Streaming protocol statistics - Transport Stream Analysis data - Content Analysis of the video and audio essence ## Connection Status Basic connectivity data is tracked for all connection regardless of protocol, this includes connection status, uptime, bitrate etc. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/oulSzwlgQfz8C9AibpgUt_image.png) ## Streaming Statistics Streaming statistics monitor the performance and health of the streaming. For example, if the stream is a Zixi protocol stream, it provides accurate metrics on packet delivery and network information such as Jitter, RTT. It also tracks FEC packet, ARQ requests, and tracks changes to network congestion etc. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/FPp89rgI9KXB1vE9n2m1N_image.png) ## The Stream Analyzer The Stream analysis component of the Broadcaster looks more closely at the transport stream, tracking transport and table errors that may have originated further upstream, such as a misconfigured encoder etc. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/JscpuYQ0mJEa_xRsIcM0__image.png) ## The Content Analyzer Finally, the content analyzer looks at the essence of the stream. Errors captured here are a property of the content itself, such as freeze-frames or audio dropout transmitted as part of a perfectly delivered video feed. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/SyzrJMIQMoyfr2YRC6NTn_image.png) [title] Alert Escalation and Notification Management Guide: Introduction [path] Alert Escalation and Notification Management Guide/ ZEN Master serves as an orchestration control-plane for Zixi Platform components (Zixi Broadcasters and ZECs) throughout the deployment. As a central orchestration solution, it gathers health data and statistics from the various Zixi Platform components and analyzes the data over time, measuring it through a wide variety of KPIs. Based on this analysis and a set of rules defined in the ***Events Rules Profile***, ZEN Master escalates the measured KPI from an "OK" state to a "Warning" state and to an "Error" state. The rules also define the conditions for when a notification should be generated.   In this guide we will: - take a closer look at the data that is gathered in the Zixi Platform components - understand how ZEN Master Event Rules work - learn how to create and deploy new Event Rules - use real-life scenarios to illustrate how the alert escalations and notifications work.   [title] Creating a new Event Profile [path] Alert Escalation and Notification Management Guide/The Events Profile/ Each new ZEN Master environment provides the ‘Default’ Event Profile, which cannot be edited, however the default profile can be cloned to create new editable profiles ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/yWXZyZq3lgWJQJgnqAmZA_image.png) The Event Profile table is split into sections based on object type, and within each type, rules are grouped into similar state issues. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/St5z4_5RR7HIVxh-CXbO2_image.png) With a new or cloned Event Profiles, each individual rule can be edited to re-configure the escalation policy that bests suit the needs of production and monitoring operations teams. Whenever you modify an event rule, be sure to click the Save button. You can also see the save status of the rule next too its title. The system will confirm “Not Saved” or “Modified” after saving. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ljgKZj48VHUDc_vurOTUj_image.png) After having modified an event rule, the rule can be set back to the default values by using the ‘Reset’ button. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/WqtEibv-cEDCQsh5IX2Ch_image.png) [title] Event Profile Tuning [path] Alert Escalation and Notification Management Guide/The Events Profile/ A common approach to alert tuning is to first use a clone of the ‘Default’ Event Profile when initially testing and configuring ZEN Master workflows. Observing streams within the production environment, with production encoders, real-world networks, and transport stream, can assist in the fine-tuning of the Event Profile. Specific changes are often subjective and can change from production to production based on different requirements. However, the following best practices may apply in many cases: - Increasing the escalation count or extending time windows where a continually flapping issue is known and understood, awaiting resolution at a later time. - Disabling rules where known states do not impact the final video playback in a particular environment or player, such as the Audio Clipping, or TR101 Table rules. - Disabling freeze frame alerts for live event workflows here slated content is expected. - Adjusting CPU or GPU thresholds to give more accurate headroom warnings based on workflow specific benchmarking tests [title] Alert Escalation and Notification Management Guide [path] / ZEN Master serves as an orchestration control-plane for Zixi Platform components (Zixi Broadcasters and ZECs) throughout the deployment. As a central orchestration solution, it gathers health data and statistics from the various Zixi Platform components and analyzes the data over time, measuring it through a wide variety of KPIs. Based on this analysis and a set of rules defined in the ***Events Rules Profile***, ZEN Master escalates the measured KPI from an "OK" state to a "Warning" state and to an "Error" state. The rules also define the conditions for when a notification should be generated. In this guide we will: - take a closer look at the data that is gathered in the Zixi Platform components - understand how ZEN Master Event Rules work - learn how to create and deploy new Event Rules - use real-life scenarios to illustrate how the alert escalations and notifications work.    [title] About WebRTC [path] How to Monitor Streams Using WebRTC Home/ WebRTC (Web Real-Time Communication) is a free, open-source project that provides web browsers and mobile applications with real-time communication (RTC) via simple application programming interfaces (APIs). It allows audio and video communication to work inside web pages by allowing direct peer-to-peer communication, eliminating the need to install plugins or download native apps. Supported by Apple, Google, Microsoft, Mozilla, and Opera, WebRTC is being standardized through the World Wide Web Consortium (W3C) and the Internet Engineering Task Force (IETF).  WebRTC advantages include: - As an HTTP protocol, WebRTC can traverse Firewalls, allowing the monitoring of streams, while the Zixi Broadcaster that is serving the stream sits behind a Firewall/NAT, all without the need to open specific Firewall ports or configure a public IP address.  - WebRTC is a low latency protocol that can achieve sub second latency (e.g. several hundreds of milliseconds. [title] Playing an Input Stream with WebRTC Player [path] How to Monitor Streams Using WebRTC Home/ WebRTC uses a regular browser to play the stream without the need to download and install an external plug in. **To Play Input Streams with WebRTC:** ::::WorkflowBlock :::WorkflowBlockItem In the Zixi Broadcaster **Inputs** page, click the desired WebRTC input stream that you want to play. ::: :::WorkflowBlockItem Click the **Actions** button on the right end of the selected row and then **Play WebRTC**. The **Link Description** window will open with the directory path for the desired file and a link to open a browser window to play the stream. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/EySVX7AFHcfxTXi3Ivwba_image.png" size="80" width="635" height="214" position="center" showCaption="false"} ::: :::WorkflowBlockItem Copy the link or click the **Open WebRTC player** link to view the stream. ::: :::: [title] Viewing Sources with WebRTC [path] How to Monitor Streams Using WebRTC Home/WebRTC for ZEN Master/ When viewing the Details pane for a Wource that has WebRTC enabled, a WebRTC “Play” icon is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/VlBcvJdfHWQVZyoQ8gf1g_image.png" size="90" width="605" height="271" position="center" showCaption="false"} Click the **Play** icon to open a new browser which plays the stream in WebRTC. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/VrAsEfgzCUyefhqLZkg_l_image.png" size="70" width="535" height="421" position="center" showCaption="false"} [title] How to Monitor Streams Using WebRTC [path] / Zixi supports using WebRTC to monitor streams. With WebRTC you can monitor your streams using popular browsers, such as Chrome, without installing any external plugins, such as the Zixi VLC plugin. This guide described the process of transcoding a stream to support WebRTC and how to monitor a stream using the WebRTC browser-integrated player.  - [About WebRTC](docId\:xhtHC_Wx7iMsXCQR09y4P) - [Video and Audio Codec Support Options](docId\:ukYoKHP2ZOAmkoxxMvhG3) - [Creating Transcoding Profiles for WebRTC](docId\:yLb7B8fu5t2p8xDMVqQ8u) - [Creating a WebRTC Output](docId\:LqxM3aIzqW-1r33dTruEz) - [Playing an Input Stream with WebRTC Player](docId:7n166mTsBrLc2exArGdAb) - [WebRTC for ZEN Master](docId:2zMBQirmWmQklBHI3tcTX) ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/pjfWKAmrfpkeO5R_WXe2n_image.png" size="70" width="520" height="97" position="center" alt="WebRTC" showCaption="false"} [title] Step 3 (option b) – Creating an HLS output in Zixi Broadcaster [path] How to Send a Zixi Stream to YouTube/Streaming to YouTube/ To create an HLS output in Zixi Broadcaster: ::::WorkflowBlock :::WorkflowBlockItem On **Zixi Broadcaster**, you will need to first create an Adaptive Group. If you have an adaptive group created, proceed to step 7. ::: :::WorkflowBlockItem In the **Adaptive** screen, click **+ Add group**. The following screen is displayed: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/s7VLULTWOpkvOPTygf71I_image.png" size="60" width="1211" height="1446" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Group name** field, enter a name for the group. ::: :::WorkflowBlockItem In the **stream ID** field, select the input stream that you would like to include in the adaptive group and specify its bitrate. ::: :::WorkflowBlockItem Click **+ Add stream** to add additional stream variants with different bitrates to the adaptive groups. ::: :::WorkflowBlockItem Click **OK**. ::: :::WorkflowBlockItem In the main menu click **Outputs**. ::: :::WorkflowBlockItem Click **+ New Output**. ::: :::WorkflowBlockItem Select the **HTTP Push** option. The following screen is displayed: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ruRwhWKpvZ5qz9VQqEOcZ_image.png" size="60" width="1946" height="1317" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Output Name** field, enter a name for the output. ::: :::WorkflowBlockItem In the **Input Adaptive Group**, select the adaptive group that you have created. ::: :::WorkflowBlockItem On **YouTube**, under **Stream Settings**, in the **Select stream key** drop-down menu, select the **HLS Stream (HLS, Variable)** option. ::: :::WorkflowBlockItem In the **Stream URL** field, click **Copy**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/_QdBexeiUjBQP3VkvLiRN_image.png" size="60" width="1726" height="1045" position="center" showCaption="false"} ::: :::WorkflowBlockItem On **Zixi Broadcaster**, paste the copied string into the **Target URL** field. ::: :::WorkflowBlockItem The string that was pasted includes the additional parameters, which belong in the **Additional URL parameters** field. From the Additional URL parameters field, Cut the string after the http\_upload\_hls (i.e. from the question mark to the end) and paste it into the **Additional URL parameters** field. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/kWSJ90ddNSGrRxpzUWGki_image.png" size="90" width="1440" height="278" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Additional URL parameters** field, at the end of the string add the following string - %PATH% - the final string should look like this: ```html ?cid=xum5-6stc-xbds-7bzg-955y©=0&file=%PATH% ``` ::: :::WorkflowBlockItem In the **Segment Path** field, select the **Path in parameters** option. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/urQZ15KT2Jokmzpc-DOWf_image.png" size="80" width="1440" height="231" position="center" showCaption="false"} ::: :::WorkflowBlockItem Click **OK**. If the stream connected successfully you should be able to see a preview of the stream. ::: :::: [title] How to Send a Zixi Stream to YouTube [path] / This is the procedure for setting up a stream in Zixi Broadcaster that will stream to YouTube. The procedure involves taking a source video in Zixi Broadcaster and then sending that stream to YouTube. ## Prerequisites This guide assumes you have already set up a YouTube Studio account on YouTube and that your account has been approved for live streaming (this process may take 24 hours). [title] Step 2 (option a) - Setting a scheduled (Later Date) live stream on YouTube [path] How to Send a Zixi Stream to YouTube/Streaming to YouTube/ In this option, the stream will be played later according to the specified schedule. **To set a scheduled live stream on YouTube:** ::::WorkflowBlock :::WorkflowBlockItem In **YouTube Studio**, at the top right corner, click the **Create **button and then click **Go Live**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Jmt7-RbfXAPaEdM1PpXof_image.png" size="60" width="392" height="217" position="center" showCaption="false"} The following welcome message is displayed: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/4bdpSCjienAnQUJOgKRAF_image.png) ::: :::WorkflowBlockItem In the **Later date** box, click **Start**. ::: :::WorkflowBlockItem Click the **Go** button in the **Streaming Software** box. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Aek0r-3YSjNRzbkwfRdyY_image.png" size="70" width="659" height="581" position="center" showCaption="false"} The following screen is displayed: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/n9gOMOLyeNAVlQPU6jNTs_image.png) ::: :::WorkflowBlockItem Click **Schedule Stream**. The following screen is displayed: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/4gxXh55KFkQ9wH679wFz8_image.png" size="80" width="559" height="815" position="center" showCaption="false"} ::: :::WorkflowBlockItem Enter the stream details, including the **Date** and **Time** in which the streaming event will be scheduled to. These details are internal in YouTube and not used by Zixi Broadcaster. ::: :::WorkflowBlockItem Click **Create Stream**. The following screen is displayed: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Tt63tDr-k8V_e_w4mEp_K_image.png) ::: :::WorkflowBlockItem At this point, you will need to create the output in Zixi Broadcaster, while using the stream key and stream URL. Leave the screen open while you setup the output in Zixi Broadcaster, as described in sections [Step 3 (option a) – Creating an RTMP output in Zixi Broadcaster](docId\:hLPhTLudT714TerigCya2) or [Step 3 (option b) – Creating an HLS output in Zixi Broadcaster](docId\:J_T1rO7jMQvmZc5dsRPss). ::: :::: [title] Enabling File Transfer & VOD Settings [path] Zixi Multicast Deployment Guide/Configuring the Contribution/Distribution Segment for Multicast Streaming/ Enabling File Transfer & VOD Settings File transfer and VOD settings should be also enabled. **To enable File Transfer & VOD settings:** :::::WorkflowBlock :::WorkflowBlockItem In **Zixi Broadcaster**, go to **Settings > File Transfer & VOD**. The **File Transfer & VOD** screen is displayed: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/M4irGgnzvWjT8eXkgfZ1a_image.png" size="80" width="1142" height="528" position="center" showCaption="false"} ::: :::WorkflowBlockItem Ensure the **Download**, **Upload** and **VOD** checkboxes are selected. ::: :::WorkflowBlockItem Click **Apply**. The following dialog is displayed: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/nJIBu0fu_jkMcNU2Y4K1W_image.png" size="50" width="816" height="382" position="center" showCaption="false"} ::: ::::WorkflowBlockItem Click **Restart Now** or **Restart Later**. :::hint{type="warning"} **Warning** Schedule downtime before restarting if running other production streams on same Zixi Broadcaster server. ::: :::: ::::: [title] On Air Pro Settings [path] Zixi On Air Pro Guide/ In the application **Settings** screen, you can manage Broadcaster connections and adjust video, audio, and network preferences. | **Setting** | **Description** | | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Connections*** |   | | **Name** | Connection name. | | **Stream ID** | Broadcaster input ID:
* Automatic mode (in ZEN Master or Broadcaster): leave this field blank * Manual mode: Enter the Broadcaster Input ID | | **Host** | Public IP address for the Broadcaster; Either:
* Use the email link from ZEN Master to populate this field * Manually enter the public IP address | | **Port** | Destination port (to listen to for Push streams):
* **2088** (default): Non-encrypted * **7088**: Protected with DTLS | | **Password** | Optional: Enter a password string to be used to authenticate Push streams to the Broadcaster. | | **Ignore DTLS Certificate** | Enable a Push input stream to establish an encrypted DTLS connection without validating the Broadcaster’s certificate. | | | | | ***Video Settings*** | | | **Codec** | Video codec:
* **H.264** * **H.265** | | **Profile** | Encoder compression profile:
* **Baseline** - Maximum compatibility, low latency * **Main** - Balance of quality and compatibility * **High** - Best quality at lowest bitrate | | **GOP (in seconds)** | Group of Pictures (GOP) length in seconds:
* .5 - 6 seconds; Default: 2 seconds | | **Resolution** | Video resolution, frame rate (fps), and bitrate (Kbps):
* **360p60, 1000Kbps** * **480p60, 1800Kbps** * **720p60, 4000Kbps** * **1080p60, 6000Kbps** * **2160p60, 18000Kbps** | | **Frame Rate** | Move the slider to change the frame rate (fps).
* 15 fps - 60 fps | | **Lock Exposure With Focus** | Enable focus and exposure lock when you tap to focus. | | **Adjust Bitrate** | Enable the app to adjust the bitrate based on network conditions and system constraints. | | | | | ***Audio Settings*** | | | **Codec** | Audio codec:
* **AAC** | | **Sampling Rate (Hz)** | Number of audio samples captured per second, measured in Hertz (Hz):
* **44100** * **48000** | | **Bitrate** | Number of bits per second allocated to audio after compression, expressed in kilobits per second (kbps):
* **96 kbps** * **128 kbps** * **160 kbps** * **256 kbps** | | **Stereo Mode** | Enable stereo mode. | | | | | ***Network Settings*** | | | **Latency (ms)** | Set the maximum latency (delay) in milliseconds. Larger values provide additional protection against network loss.
* 100 - 8000 ms | | **WiFi+Cellular Bonding** | Enable Wi‑Fi + Cellular Bonding:
* Packets are sent over both networks in parallel * The Broadcaster recombines them into one clean stream * If one network degrades or drops, the other keeps the stream alive |     [title] Viewing Zixi HLS Directly from the Target Broadcaster [path] Zixi OnAir Guide (deprecated)/Viewing a Live Video Stream/ If the target Broadcaster has been configured as an HLS Adaptive Group server and you have the HLS group name (provided by your administrator), you can pull the resulting HLS stream directly back you to a local device or system for live playback. An HLS capable player will be able to play the HLS using a URL of the following format: [http://broadacster\_details:7777/HLS\_group\_name.m3u8](http://broadacster_details:7777/HLS_group_name.m3u8) Example: zixi://mybxdemo.zixi.com:7777/livetest.m3u8 Recommended players include: - Apple’s Safari browser - A freely available online HLS player, such as [http://osmfhls.kutu.ru/](http://osmfhls.kutu.ru/) :::hint{type="warning"} This is intended for a test scenario, not for large-scale distribution, unless stated by your administrator. ::: [title] Playing back a video stream [path] Zixi Player Guide/ Zixi Player can playback Zixi Transport Protocol streams that have been added to the player (see - [Adding a video stream](docId\:wdoTO_dOhMQkwByvnMJZP) section). Video streams using Zixi-protocol will be protected by the Zixi protocol, a resilient congestion and network-aware protocol that adjusts to varying network conditions and employs patented, dynamic Forward Error Correction techniques for error-free video transport over IP with 99.9999% uptime at minimal latency. **To playback a video stream:** ::::WorkflowBlock :::WorkflowBlockItem From the Zixi Player home screen, tap the relevant stream. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/lFH5SiupLImgHG3AE_rVp_image.png" size="60" width="400" height="404" position="center" showCaption="false"} The stream is played back in the Zixi Player. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/_aeIq6svQqYaMchLuAzRG_image.png" size="80" width="407" height="520" position="center" showCaption="false"} ::: :::WorkflowBlockItem While in playback mode, you can view the stream statistics by taping the "i" icon at the top. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/WAv0wXtJj9mKhnTHXwjzZ_image.png" size="80" width="1080" height="1374" position="center" showCaption="false"} ::: :::: [title] Adding a video stream [path] Zixi Player Guide/ Before playing back a stream you will need to add the stream to the Zixi Player.  Encrypted and password protected streams can be decrypted/accessed using the Zixi Player. **To add a video stream:** ::::WorkflowBlock :::WorkflowBlockItem Open the **Zixi Player **app. ::: :::WorkflowBlockItem On the lower right-hand side, tap the **+** button. ::: :::WorkflowBlockItem Tap the **+** icon (middle icon). ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/upGglhv7P1G6CnahApDuU_image.png" size="18" width="125" height="259" position="center" showCaption="false"} The following screen is displayed: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Xf3D5tS86UV2rO8emY_qR_image.png" size="38" width="400" height="381" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Name** field, enter a name for the stream. This is an internal name for the application only, so it does not have to match the name of the stream in the Zixi Broadcaster. ::: :::WorkflowBlockItem In the **URL** field, enter the full URL path of the stream. The app will use the URL to pull the stream. ::: :::WorkflowBlockItem If the stream is password-protected, enter the password in the **Password** field. ::: :::WorkflowBlockItem If the stream is encrypted, enter the decryption key in the Decryption Key field. ::: :::WorkflowBlockItem In the **Latency** field, enter the desired latency in milliseconds. Latency creates a buffer for improved performance. Higher latency may be required when the network experiences high packet loss percentage and high jitter. This setting affects memory usage as higher levels of protection require more buffering. Default: 2000 ms. ::: :::WorkflowBlockItem Tap the **Save** icon at the top. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/qOQ9GBAmqoeNvZpuVI96U_image.png" size="40" width="402" height="396" position="center" showCaption="false"} The new stream is added to a list of streams. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/iE8m14QUQWj-u4MFThgSu_image.png" size="40" width="401" height="366" position="center" showCaption="false"} ::: :::WorkflowBlockItem Repeat the steps above to add additional streams ::: :::WorkflowBlockItem You can tap the mosaic icon at the top to view all the streams presented in a mosaic fashion. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/DuxMWFM5eQu4se1z8fQjt_image.png" size="40" width="1080" height="881" position="center" showCaption="false"} The streams are presented as a mosaic: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/t-CiQajmnoo-Y4QBmpJNm_image.png" size="40" width="1080" height="836" position="center" showCaption="false"} ::: :::: [title] Applying Event Profiles [path] Alert Escalation and Notification Management Guide/The Events Profile/ Once defined, an Event Profile can be applied individually to each resource such as Channels, Broadcasters, Sources, etc. in ZEN Master.  The “Events Configuration Profile” pull-down is shown when creating or editing an object in ZEN Master, where the appropriate event profile can be selected. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/9mzQMj2PNiXRCQ-1mI9pX_image.png) If an actively applied profile is edited and saved, the change will propagate to all objects using the event profile. If a new profile is created, it can be applied to many objects at a time, using the multi-select and edit capability on the list pages for sources broadcasters etc. In either case, changing and objects event profile will not cause a restart. In addition, the change will not affect any active escalations. i.e., if an object is in an ‘Error’ state, and its profile is edited to disable the actively triggered rule, the object will stay in Error until its resolved. [title] Deployment Architecture [path] Zixi Multicast Deployment Guide/ ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/JcoP3CMRfvoygUpFKeZtS_image.png" size="90" width="1429" height="717" position="center" showCaption="false"} Zixi-protected multicast deployments includes the following Zixi Components: - **Origin **– the origin of the stream can be either a ZEC, a file playing locally, or any device streaming remotely or locally in any of the following formats: - Zixi protected transport (PULL/PUSH) - MPEG-TS over UDP and/or RTP with SMPTE-2022 (Unicast/Multicast) - File - Transport stream files from local file system - RTMP pull from CDNs and/or other sources - RTMP push - RTMPS - RTSP input - HLS - TS over HTTP - RIST - **Contribution/distribution** – in the contribution/distribution segment there is a Zixi Broadcaster component that streams a Zixi protected transport stream to a multicast-supported network. - **Consumption **– in the consumption segment there are a variety of devices that can receive and playback a multicast Zixi-protected stream, including: - Mobile device running a Zixi player. - Mobile device running a customer application with Zixi Proxy embedded. - PC running VLC with Zixi embedded. - PC/Server running ZEC as a receiver The endpoints/receivers/ZEC connect to the Zixi Broadcaster to pull an input stream. The Zixi Broadcaster redirects them to a multicast address. If the multicast connection does not succeed and the input stream has **NOT** been marked as “**multicast only**”, the entire transmission of the stream will fall back to Unicast. However, enabling the multicast only flag will prevent the fallback to unicast. If the multicast connection is successful, but there are errors in the transmission, the error correction will be transmitted in UDP unicast directly to the specific device that suffered the error. [title] Recording a Stream Locally [path] Zixi VLC Plugin Setup Guide/Operation/ VLC is able to record a Zixi stream locally to disk. This is especially useful in the event that a copy of the pulled stream is required for further analysis by technical support. A local recording can be captured and the resulting file can be uploaded to Zixi Support. ## Recording a Stream **To record a stream:** ::::WorkflowBlock :::WorkflowBlockItem Open VLC Player ::: :::WorkflowBlockItem On the Main Menu, click **Media**. Sub-menu options are displayed. ::: :::WorkflowBlockItem Click **Open Network Stream**. ::: :::WorkflowBlockItem Enter network URL - `Zixi://:/` ::: :::WorkflowBlockItem At the bottom, click the down arrow next to the **Play** button and select **Convert**. The **Convert** window opens. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/yX2O0lYkqcKP4mBKtfAuh_image.png" size="60" width="1503" height="1224" position="center" showCaption="false"} ::: :::WorkflowBlockItem Select the **Dump Raw Input **checkbox. ::: :::WorkflowBlockItem Click **Browse** and select the destination folder. ::: :::WorkflowBlockItem Enter a relevant filename with a ‘.ts’ extension. ::: :::WorkflowBlockItem Click **Start**. ::: :::: ## Stopping the Recording **To stop the recording:** - Click the stop playback button in the VLC play control bar. ## Validating the Recording **To ensure the recording was successful:** 1. Open VLC Player 2. On the Main Menu, click **Media**. Sub-menu options are displayed. 3. Click Open File. 4. Set the file filter in the bottom right to **“All Files (\*)”**. 5. Browse to select your recorded file. 6. Click **Open**. Your recording will playback in VLC. [title] Zixi Plug-In Preferences Configuration [path] Zixi VLC Plugin Setup Guide/Installation and Setup/ You can configure the Zixi Plug-in settings, such as caching, latency, and more. **To access Zixi Plug-in preferences:** ::::WorkflowBlock :::WorkflowBlockItem In VLC's** Main Menu**, click the **Tools **menu and select **Preferences.** ::: :::WorkflowBlockItem At the bottom left of the **Preferences** window, under **Show Settings** select **All**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/DnCWq49zRofT6PyjdBg0T_image.png" size="80" width="2404" height="515" position="center" showCaption="false"} The **Advanced Preference** window opens displaying a tree with all the preferences. ::: :::WorkflowBlockItem Under I**nput / Codecs**, click **Access Modules > Zixi**. ::: :::WorkflowBlockItem Click **Input / Codecs** and then click **Access Modules**. The **Zixi VLC plug-in preferences** appear in the right pane. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/UiiO8oaU2tNI0jyPKZJa7_image.png" size="80" width="803" height="732" position="center" showCaption="false"} ::: :::WorkflowBlockItem Configure the following settings as required: | Setting | Description | | --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Allow Latency to Decrease** | ‘Off’ is recommended. Can dynamically lower latency when ‘On’ but may re-buffer if an increase is needed. | | **Decryption Key** | For playback of encrypted streams, enter the key provided by your administrator (see Playing an Encrypted Zixi Stream). | | **Drop Frames with Missing Data** | In the case of data loss, when this option is turned on, any partial frames are removed by the Zixi Plug-In prior to forwarding to the player. This option can improve VLC stability. | | **FEC Overhead \[%] and FEC Blocksize \[ms]** | **Do \*not\* alter**. FEC settings are set automatically. These entries will be removed in future versions. | | **Fixed end-to-end delay** | When selected, this setting guarantees synchronization of all players having the same latency settings, regardless of their location. The latency settings sets the duration of the buffer size. This means that when enabling fixed end-to-end delay, the buffer will be slightly shorter, taking into account the propagation delay from the source, because the latency is from source to destination, instead of a local delay at the destination | | **Fixed Latency** | ‘On’ is recommended. Uses Max Latency specified when off, dynamically increases to Max Latency when on. | | **Max Latency \[ms]** | The maximum latency in milliseconds of the Zixi stream over your local connection between the source Zixi Broadcaster and the VLC player. Increasing latency will add additional buffer space to compensate for network burst loss. | | **Player Caching \[ms]** | The length, in milliseconds, of the VLC player cache. Using skip controls may cause the player to re-buffer. | | **Zixi Log Mode** | This integer value sets the log entry level mode for Zixi stream messages. Available Options: Disabled (-1) Debug (0 or 1) Info (2) Warning (3) Error (4) Fatal (5). **Note: Set only as disable unless debugging. Additional disk writes can affect memory and performance.** | ::: :::WorkflowBlockItem Once you have updated the preferences, click Save and close the VLC player. Restart VLC for your changes to take effect. ::: :::: [title] Operation [path] Zixi VLC Plugin Setup Guide/ - [Playing a Zixi-enabled Stream](docId\:DIr-demIIeWWYzY-uqSE1) - [Playing an Encrypted Zixi Stream](docId\:tCHhgswQT_xoS95FtxyMc) - [Recording a Stream Locally](docId\:EAkhWFigp-bxy0nVldC0n) - [Special Playback Controls for Monitoring Live Video](docId\:b_fvSTIu2tn9UcYn7Bei9) - [Stream Information and Metrics](docId\:j9LMEiE6nJyeRqg6DvOoT) - [Streaming a File to a Local Zixi Feeder or Broadcaster](docId\:x_kdNKw_cSmmdjfzE68VQ) - [Streaming Standard UDP from a Local Zixi Receiver](docId\:pzO4nbmwGsP7KRN2xBwtU) [title] System Requirements [path] Zixi VLC Plugin Setup Guide/Installation and Setup/ The VLC Media Player is produced and maintained by The VideoLAN project and is compatible with VLC versions 1.0.x, 1.1.x, 2.0.x, 2.1.x, 2.2.x, 3.0, and later. This documentation covers the Zixi VLC Plug-In with VLC Version 3.0.10 and later. **Windows Version** - The Zixi VLC Plug-In for Windows should use the latest VLC version and is available for Windows versions 7 and later. **Mac Version** - The Zixi VLC Plug-In for Mac should use the latest VLC version and is available for macOS 10.9 and later. For live stream playback, the plug-in requires an active network connection to a pre-configured Zixi Broadcaster. Inbound UDP must be enabled from the remote broadcaster source port 2077 to a session based random local port. **** [title] Zixi On Air Pro Guide [path] / Zixi On Air Pro is a next-generation, professional live-video contribution app that turns your mobile device into a broadcast-quality video source, which integrates with the Zixi Platform. In addition to reliable live streaming using the Zixi protocol, the app is tightly integrated with ZEN Master for centralized provisioning, monitoring, permissions, and operational control. Zixi On Air Pro enables field teams to stream reliable, low-latency video directly into existing Zixi workflows. The app is intended for Zixi customers who require secure, scalable mobile contribution without a separate operational model. The On Air Pro supports enterprise workflows, enabling mobile sources to be managed like other Zixi Sources, with platform visibility, control, and orchestration. # Features - Next-generation mobile app - Deep integration with ZEN Master and Zixi Broadcaster - Configuration is centrally provisioned using ZEN Master - Platform-level monitoring, control, and orchestration - Enterprise, production-grade mobile workflows - Mobile treated as a first-class Zixi Source - Uses the internal mobile device camera - HEVC support for Full HD (1080p) and Ultra HD (2160p) - Configurable video resolution, quality, and transmission latency - Transmit using Zixi Protected Transport Protocol - WiFi + Cellular bonding - Audio selection for mono or stereo mode # App Comparison | **Area** | **Zixi OnAir (legacy)** | **Zixi On Air Pro** | | ---------------------- | ---------------------------------------- | ----------------------------------------------------- | | Status | Legacy mobile app | Next-generation mobile app | | Platform integration | Works with Zixi Broadcaster | Deep integration with ZEN Master and Zixi Broadcaster | | Configuration | Manual | Centrally provisioned using ZEN Master | | Monitoring and control | Limited, local to the app | Platform-level monitoring, control, and orchestration | | Target use | Basic mobile live contribution | Enterprise, production-grade mobile workflows | | Operational model | Mobile is viewed as a stand-alone source | Mobile is treated as a first-class Zixi Source | # Contents - [On Air Pro Requirements](docId\:LdbHJ6Og0UYUjMASRAjbg) - [Downloading the App](docId\:Hi2HKT54c9o_HcAoVa9Mg) - [Streaming using ZEN Master](docId\:IKoURGnTRFnzRLlqiYqUr) - [Camera Screen](docId:9upv5vqJORMUcm78GGZqS) - [On Air Pro Settings](docId\:cbonagrhNB4rIv7aWxSAm) - [Streaming with Broadcaster Only](docId\:q9eyY6y9Vd1G3nzrkwnOx) - [Monitor a Broadcaster Feed](docId\:xAVu8W0G0GPF5Lj5FTTPI) [title] Monitor a Broadcaster Feed [path] Zixi On Air Pro Guide/Streaming with Broadcaster Only/ If you have access to a ZEN Master, you can add the Broadcaster to a manual Cluster and monitor the input through a Monitor Only Source on the ZEN Master. ### Adding the Broadcaster to a Manual Cluster ::::WorkflowBlock :::WorkflowBlockItem In ZEN Master, download an SSH key by selecting an existing SSH key or creating a new one - See - [Configuring SSH Keys](docId\:qXuh0ckZbygbyCRZvjtwS). Store the SSH key, as you will need to upload it to your Broadcaster. ::: :::WorkflowBlockItem In ZEN Master, configure the Broadcaster on a Manual Cluster - See - [Adding a Broadcaster to a Manual Cluster](docId\:xYscySO498lY77ZjQr-51). In the SSH Key field select the SSH key that you have used or created in step 1. ::: :::WorkflowBlockItem Connect your Broadcaster to the Cluster by following these steps - [Connecting the Zixi Broadcaster (Zixi Broadcaster UI – For Manual)](docId\:OeXqmQgq_YZFbIi_OqjPO) ::: :::: ### Create a Monitor Only Source ::::WorkflowBlock :::WorkflowBlockItem In a web browser, navigate to [https://.zen.zixi.com](https://\{youraccount}.zen.zixi.com) ::: :::WorkflowBlockItem When you sign in, you should see the Zixi ZEN Master dashboard. ::: :::WorkflowBlockItem In the left navigation, select **Sources**. ::: :::WorkflowBlockItem Select **+Add**. ::: :::WorkflowBlockItem Select **Monitor Only**. ::: :::WorkflowBlockItem The **Name** will come from the Broadcaster Input ID. ::: :::WorkflowBlockItem Enter the following information: - **Tags** – Add Tags to control access to this Source - **Broadcaster** – Select your Broadcaster - **Broadcaster Inputs** – Select the Broadcaster Input associated with the On Air Pro app ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/G1Ykojsig0tiMK2bg68vl_.blob) ::: :::WorkflowBlockItem For information about the other fields for this Source, see the [Adding a Source – Monitor Only](https://docs.zixi.com/zen-master/adding-a-source-monitor-only) document. ::: :::WorkflowBlockItem Select **Save** to create the Source. ::: :::: With the Monitor-only Source, ZEN Master shows stream information details, including some historical data. [title] Streaming with Broadcaster Only [path] Zixi On Air Pro Guide/ To stream from Zixi On Air Pro to your Broadcaster, you must first enable the Broadcaster to receive the input by creating a Push Input. :::hint{type="info"} You must have access to a running Zixi Broadcaster. If you are activating your Broadcaster for the first time, see [Installing Zixi Products](docId\:vr8wIZ4KSRwxSZ52Cx--w). ::: There are two options to stream to a stand-alone Broadcaster (both options use the Zixi protocol): - **Manual connection** **option** - you can manually create a Push Input on your Broadcaster in advance and then configure a Connection with the Input's details. - **Automatic connection** **option** - you can create a connection on the On Air Pro app with the details of the Broadcaster. When you start streaming using this connection, a Push Input is automatically created on the Broadcaster and will disappear once the stream is disconnected. This option requires enabling the **Allow automatic HTTP push input **setting. ## Manual Connection Option ### Step 1 - Add a Push Input to your Broadcaster ::::WorkflowBlock :::WorkflowBlockItem Open your Zixi Broadcaster. ::: :::WorkflowBlockItem In the top navigation, select **Inputs**. ::: :::WorkflowBlockItem On the Inputs screen, select **+ New Input**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/K_3uCngtgxMM2gxzzT1Ms_bxpush.jpg) ::: :::WorkflowBlockItem In the **Stream ID** field, enter a name that you will use to identify the stream sent from your On Air Pro app. Make a note of the Stream ID (case sensitive), as you will enter this as the Stream ID in the app settings. ::: :::WorkflowBlockItem In the stream type selection, select the **Push** radio button (default). ::: :::WorkflowBlockItem In the **Stream Parameters** section, in the **Password** field, you can add a password for increased security. Make a note of the Password (case sensitive), as you will enter this as the Password in the app settings. ::: :::WorkflowBlockItem Configure additional settings as necessary. ::: :::WorkflowBlockItem Click **OK**. The new Input is added to the Zixi Broadcaster and now appears in the list of available streams on the **Inputs** screen. The **Status** should be Offline (blue). ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/k1jRR8e6g81MqXGPicWhj_bxpush2.jpg) ::: :::: ### Step 2 - Get the Broadcaster IP Address Get the public IP address for your Zixi Broadcaster, so you can use this to populate the **Host** field in the app, by doing one of the following: ::::WorkflowBlock :::WorkflowBlockItem If you are running the Zixi Broadcaster from your local machine, run the following command: For Linux - `curl -4 ip.me` For Windows - go to `ip.me`. ::: :::WorkflowBlockItem If you are using a Broadcaster connected to ZEN Master, the IP is show on the Broadcaster page in the ribbon at the top of the Broadcaster page. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/dERF6grOpkTlcdZ0kFuBZ_broadcasteripaddress.png" size="50" isUploading="false" position="center" width="390" height="137" darkWidth="390" darkHeight="137" showCaption="false"} ::: :::: ### Step 3 - Add a New Connection ::::WorkflowBlock :::WorkflowBlockItem On your Apple or Android device, open the **Zixi On Air Pro** app. ::: :::WorkflowBlockItem In the top left, tap the gear icon. ::: :::WorkflowBlockItem In **Settings**, tap **Connections**. ::: :::WorkflowBlockItem Tap the **+** icon to create a new connection. ::: :::WorkflowBlockItem Enter the following information: - **Name** – Give the connection a name - **Stream ID** – Enter the same Stream ID you have configured on the Zixi Broadcaster (case sensitive). - **Host** – Enter the Public IP address for the Broadcaster (e.g. 172.217.22.14) - **Port** – Leave the default, or set the Broadcaster server port which allows push inputs: - **2088** – Non-encrypted - **7088** – Protected by DTLS - **Password –** Optional: Enter the password set on the Broadcaster Input - **Ignore DTLS Certificate Errors** – Turn on to enable - Required with port 7088 and fully qualified domain name ::: :::WorkflowBlockItem Tap **Add** to create the connection. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/tyeUT_w1VzweNMwpZJWbZ_.blob) ::: :::WorkflowBlockItem In the **Connections **screen, if you have multiple connections, long tap the newly created connection to set it as the default connection. ::: :::WorkflowBlockItem In **Audio Settings**, you may want to toggle **Stereo Mode** on. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/DC-m9Psds3waauK6QYSgm_.blob) ::: :::: ### Step 4 - Start Streaming 1. In the On Air Pro app, navigate back to the camera. 2. Press the red button to start streaming. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/G05quHfu1loSB12ye6zNW_.blob) 3. In Zixi Broadcaster, you should now see your new input. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Yq-LBICroeTD8E07rWqT7_connectiontobx.png) ## Automatic Connection Option ### Step 1 - Enable the Allow automatic HTTP push input setting 1. On the Broadcaster, go to Settings > Live Protocols. 2. Enable the **Allow automatic HTTP push input **setting. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/5F8kakthKxQYrj2TEg7Z9_allowautopushinput.jpg" size="100" isUploading="false" position="center" width="1128" height="668" darkWidth="1128" darkHeight="668" showCaption="false" indent="1"} 3. Click **Apply**. ### Step 2 - Add a New Connection ::::WorkflowBlock :::WorkflowBlockItem On your Apple or Android device, open the **Zixi On Air Pro** app. ::: :::WorkflowBlockItem In the top left, tap the gear icon. ::: :::WorkflowBlockItem In **Settings**, tap **Connections**. ::: :::WorkflowBlockItem Tap the **+** icon to create a new connection. ::: :::WorkflowBlockItem Enter the following information: - **Name** – Give the connection a name - **Stream ID** – Give the stream ID a name. This will be used to create a temporary input on your Broadcaster. (e.g. onair-app) - **Host** – Enter the Public IP address for the Broadcaster (e.g. 172.217.22.14) you will use to stream. - **Port** – Leave the default, or set the Broadcaster server port which allows push inputs: - **2088** – Non-encrypted - **7088** – Protected by DTLS - **Ignore DTLS Certificate Errors** – Turn on to enable - Required with port 7088 and fully qualified domain name ::: :::WorkflowBlockItem Tap **Add** to create the connection. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/tyeUT_w1VzweNMwpZJWbZ_.blob) ::: :::WorkflowBlockItem In the **Connections **screen, if you have multiple connections, long tap the newly created connection to set it as the default connection. ::: :::WorkflowBlockItem In **Audio Settings**, you may want to toggle **Stereo Mode** on. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/DC-m9Psds3waauK6QYSgm_.blob) ::: :::: ### Step 3 - Start Streaming 1. In the On Air Pro app, navigate back to the camera. 2. Press the red button to start streaming. 3. In Zixi Broadcaster, you should now see your new input. This input will disappear once the stream will stop. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/FrIz5zv57r70Clkl2ASxZ_adhocpush.jpg" size="100" isUploading="false" position="center" width="1139" height="311" darkWidth="1139" darkHeight="311" showCaption="false" indent="1"} [title] Zixi OnAir: Quick Start [path] Zixi OnAir Guide (deprecated)/ This quick start provides basic instructions on how to stream a Zixi-protocol video using your device's camera. **To stream a video using your device's camera:** 1. Ensure you have a Wi-Fi/cellular connection to the internet. 2. Ensure you have created a **Push Input** in **Zixi Broadcaster**. 3. Open the Zixi OnAir app. 4. Tap **Allow** to allow Zixi OnAir to record audio and video. The **Settings** screen is displayed. 5. In the **Broadcaster Name **field, enter the Name or IP Address of the target Broadcaster. 6. In the **Channel Name **field, enter the name of the Input that you have setup on the target Broadcaster. 7. Tap **Save**. 8. Tap the **Green** circle (Shoot button) on the right-hand side to stream live video to your target Broadcaster. [title] Summary [path] Alert Escalation and Notification Management Guide/ The following are some of the main points covered in this guide: - For any object within the ZEN Master system, Warnings, Errors, and Alert Notification Emails, are controlled by the Event Profile. - An Event Profile contains a table of rules dictating how the ZEN Master alerting system reacts to each of the various state changes of resources and streaming objects. - These profiles are not actually applied until they are associated with the various resources or streaming components within ZEN Master during the object's configuration. - Each rule can be edited independently, depending on the rule type any issue being caught by the rule can be: - Completely ignored and disabled. - Entered in the Event Log without impact the status of the object or generating alerts. - Elevated to a warning based on the number of events within a time window or some defined threshold. - Escalated to a full error when the event count reaches a defined number, or an upper threshold is reached. - Editing a rule and saving will propagate the change to all objects actively using the profile. Applying a new profile will update the rule of all selected objects. Neither change will interrupt an active stream or cause a restart. - Email notifications are generated on Error or Ok Status changes. Each of which can be independently disabled in each rule of the Event Profile. - Alert notification emails are sent only to Users or Groups assigned to Roles with email receipt permissions (see Account Management documentation) on a given object. [title] Creating Transcoding Profiles for WebRTC [path] How to Monitor Streams Using WebRTC Home/ In order to enable transcoding of non-WebRTC compliant streams you need to first create the relevant Transcoding Profiles. You need to create separate video and audio profiles for use with Single Version and Multiple Version transcoding methods. You will then be able to apply those profiles to your streams as needed. ## Creating a Video Profile for “Single Version” Transcoding **To create a video profile for “Single Version” transcoding:** ::::WorkflowBlock :::WorkflowBlockItem On the **Transcoder** screen of the Broadcaster UI, click **New Profile**. The **Add New Profile** window opens. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/IL8D29lzY-GN9pJW58AgH_image.png" size="72" width="1014" height="789" position="center" showCaption="false"} ::: :::WorkflowBlockItem Under **Codec** **type**, select the **H.264** radio button (default). ::: :::WorkflowBlockItem In the **Name** field, enter a name that describes this profile (e.g. WebRTCSingleVersionVideo). ::: :::WorkflowBlockItem In the **Encoding Profile** field, select either *Baseline* or *Main*. ::: :::WorkflowBlockItem In the **Resolution** fields, enter a low resolution that can be viewed by all of your users. ::: :::WorkflowBlockItem Configure additional parameters as required, see [Creating New Transcoding Profiles](docId\:nnzH8CsjpFQlDlZCXGZ4c) (in the [Zixi Broadcaster User Guide](docId\:JGwIXYN936aeZmonZLERn)). ::: :::WorkflowBlockItem Click **Apply**. The new profile is created and it can be used to configure a “Single Version” WebRTC output. ::: :::: ## Creating an Audio Profile for “Single Version” Transcoding **To create an audio profile for “Single Version” transcoding:** ::::WorkflowBlock :::WorkflowBlockItem On the **Transcoder** screen of the Broadcaster UI, click **New Profile**. The **Add New Profile** window opens. ::: :::WorkflowBlockItem Under **Codec** **type**, select the **Opus** radio button (default). The Opus configuration options are shown. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/jo-vpsZdOyyU5vDiHMmLU_image.png" size="70" width="1013" height="418" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Name** field, enter a name that describes this profile (e.g. WebRTCSingleVersionAudio) ::: :::WorkflowBlockItem Configure additional parameters as required, see [Creating New Transcoding Profiles](docId\:nnzH8CsjpFQlDlZCXGZ4c) (in the [Zixi Broadcaster User Guide](docId\:JGwIXYN936aeZmonZLERn)). ::: :::WorkflowBlockItem Click **Apply**. The new profile is created and it can be used to configure a “Single Version” WebRTC output. ::: :::: ## Creating a Video Profile for “Multiple Version” Transcoding **To create a video profile for “Multiple Version” transcoding:** ::::WorkflowBlock :::WorkflowBlockItem On the **Transcoder** screen of the Broadcaster UI, click **New Profile**. The **Add New Profile** window opens. ::: :::WorkflowBlockItem Under **Codec** **type**, select **Raw Video** (default). The Raw Video configuration options are shown. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/rzpjPHnAocIquVKYzzBuN_image.png" size="70" width="1015" height="493" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Name** field, enter a name that describes this profile (e.g. WebRTCMutipleVersionVideo) ::: :::WorkflowBlockItem Configure additional parameters as required, see [Creating New Transcoding Profiles](docId\:nnzH8CsjpFQlDlZCXGZ4c) (in the [Zixi Broadcaster User Guide](docId\:JGwIXYN936aeZmonZLERn)). ::: :::WorkflowBlockItem Click **Apply**. The new profile is created and it can be used to configure a “Multiple Version” WebRTC output. ::: :::: ## Creating an Audio Profile for “Multiple Version” Transcoding **To create an audio profile for “Multiple Version” transcoding:** ::::WorkflowBlock :::WorkflowBlockItem On the **Transcoder** screen of the Broadcaster UI, click **New Profile**. The **Add New Profile** window opens. ::: :::WorkflowBlockItem Under **Codec** **type**, select **Raw Audio** (default). The Raw Audio configuration options are shown. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/In6wxCacnJKT8Ppth_6pm_image.png" size="70" width="1013" height="378" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Name** field, enter a name that describes this profile (e.g. WebRTCMutipleVersionAudio) ::: :::WorkflowBlockItem Configure additional parameters as required, see [Creating New Transcoding Profiles](docId\:nnzH8CsjpFQlDlZCXGZ4c) (in the [Zixi Broadcaster User Guide](docId\:JGwIXYN936aeZmonZLERn)). ::: :::WorkflowBlockItem Click **Apply**. The new profile is created and it can be used to configure a “Multiple Version” WebRTC output. ::: :::: [title] Step 2 (option b) – Setting an immediate (Right Now) live stream on YouTube [path] How to Send a Zixi Stream to YouTube/Streaming to YouTube/ In this option the stream will be played immediately after creating it in YouTube and creating the output in Zixi Broadcaster. To set an immediate live stream on YouTube: ::::WorkflowBlock :::WorkflowBlockItem In **YouTube Studio**, at the top right corner click the **Create** button and then click **Go Live**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/SBFiwr1TkApm4oQ2F2P55_image.png" size="60" width="392" height="217" position="center" showCaption="false"} The following welcome message is displayed: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/7rIY1FzEN4qIT7mj6LR8N_image.png) ::: :::WorkflowBlockItem In the **Right now** box, click **Start**. ::: :::WorkflowBlockItem Click the **Go** button in the **Streaming Software** box. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/3Tm8Rsj61FCEz6MYiuCaF_image.png" size="70" width="659" height="581" position="center" showCaption="false"} The following screen is displayed: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/TkHSDClKKpVNUvFweew0f_image.png) ::: :::WorkflowBlockItem At this point you will need to create the output in Zixi Broadcaster, while using the stream key and stream URL. Leave the screen open while you setup the output in Zixi Broadcaster, as described in sections: [Step 3 (option a) – Creating an RTMP output in Zixi Broadcaster](docId\:hLPhTLudT714TerigCya2) or [Step 3 (option b) – Creating an HLS output in Zixi Broadcaster](docId\:J_T1rO7jMQvmZc5dsRPss). ::: :::: [title] Step 1 - Creating an input stream in Zixi Broadcaster [path] How to Send a Zixi Stream to YouTube/Streaming to YouTube/ The Input in Zixi Broadcaster can be any of the supported inputs.  **To create an Input stream:** ::::WorkflowBlock :::WorkflowBlockItem Login to **Zixi Broadcaster.** ::: :::WorkflowBlockItem In the Main Navigation menu, click the **Inputs** tab. ::: :::WorkflowBlockItem In the Menu bar, click **New Input**. The **Add a new input stream** window is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/7zZTe7N3EJGqDpTRWC7hD_image.png" size="90" width="887" height="482" position="center" showCaption="false"} ::: :::WorkflowBlockItem Select the type of Input based on the source stream. ::: :::WorkflowBlockItem Fill in the fields with the relevant information, see [Zixi Broadcaster User Guide](docId\:JGwIXYN936aeZmonZLERn) . ::: :::WorkflowBlockItem Click **Ok**. The new Input is created. ::: :::: [title] Creating Streams Using NewTek Connect [path] How to Use Zixi to Transport NDI Over the Public Internet/Creating NDI Streams/ You can use the NewTek connect application to generate full motion NDI streams from a webcam source. **To create a stream using NewTek Connect:** ::::WorkflowBlock :::WorkflowBlockItem Go to [https://www.newtek.com/ndi/applications/connect/](https://www.newtek.com/ndi/applications/connect/) and download the application following the on-screen instructions. ::: :::WorkflowBlockItem Install and launch the NewTek Connect application. ::: :::WorkflowBlockItem In the default OUT 1 stream, click on the settings icon. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/9J5LxTlTsE_PE_orxKc4B_image.png" size="22" width="133" height="98" position="center" showCaption="false"} The configuration window is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/5U9I7eMA6ffRS0m08tJfo_image.png" size="70" width="480" height="466" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Input** tab, in the **Video Source** field, select from the drop-down list **Local (Integrated Camera)**. ::: :::WorkflowBlockItem In the Video Format field, select from the drop-down list the video quality and frame rate. ::: :::WorkflowBlockItem In the Output tab, in the Channel Name field, specify a name for the output stream. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/dmWWtKwzjkIJUTqd2Inpo_image.png" size="70" width="535" height="426" position="center" showCaption="false"} ::: :::WorkflowBlockItem Click **Close**. The NDI stream will now be published on the network. ::: :::: [title] Adding an Input in Zixi [path] OBS Zixi Integration - Quick Start Guide Home/ [title] OBS Studio Configuration [path] OBS Zixi Integration - Quick Start Guide Home/ Once installation is complete, there will be new Zixi Service available as a stream destination in OBS Studio. To configure OBS Studio to send a Zixi stream, click on Settings: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/5DZoEtAslaF_W9V8JRkam-20260513-171751.png" size="82" width="806" height="389" position="center" caption="OBS Menu" alt="OBS Menu" showCaption="true"} - Under the Stream menu on the left, select Zixi Broadcaster as the Service. You should see a form pop up below. (If you do not see the form, select a different Service and then select Zixi Broadcaster again to refresh the page.) - Configure the Zixi Broadcaster URL with the Broadcaster IP address, Ports, & Stream ID from the Broadcaster or ZEN Master configuration as show below. :::hint{type="info"} Port is only necessary if it is not the default 2088. zixi://\{hostname}/\{streamID}:\{port} ::: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/VnwtaoHa659znUalleNr7-20260513-165337.png) - Set the desired latency buffer and enable encoder feedback and bonding if desired. Encoder feedback will dynamically reduce the bitrate of the encoded stream based on upstream congestion measured during transmission of the Zixi protocol. - Bonding will send the Zixi stream spread out as evenly as possible across all available NICs. As long a one network connection to the Broadcaster remains with sufficient bandwidth for the stream, there will be no disruption in delivery. [title] OBS Zixi Integration - Quick Start Guide Home [path] / OBS Studio is a free, open source software tool for video recording and live streaming with the following key features: - High performance real-time video/audio capturing and mixing. You can create scenes made up of multiple sources including window captures, images, text, browser windows, webcams, capture cards and more. - Set up an unlimited number of scenes, which you can switch between seamlessly via custom transitions. - Intuitive audio mixer with per-source filters such as noise gate, noise suppression, and gain. Take full control with VST plugin support. - Powerful and easy to use configuration options. Add new sources, duplicate existing ones, and adjust their properties effortlessly. - Streamlined Settings panel gives you access to a wide array of configuration options to tweak every aspect of your broadcast or recording. - Modular ‘Dock’ UI allows you to rearrange the layout exactly as you like. You can even pop out each individual Dock to its own window. - OBS supports all your favorite streaming platforms and more. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/uxcR6BVqP2WyQr5DCOlHe_image.png" size="90" width="866" height="668" position="center" showCaption="false"} - [Installing OBS Studio for Zixi](docId\:yfM91-BtC5zRtO_uQaaqM) - [Adding an Input in Zixi](docId\:uAZtP_QPj75YSx1XNV3T0) - [Finding the Connection Details](docId\:pXBp_69Jri9jU_Bi7aJdd) - [OBS Studio Configuration](docId\:cAY9xg_4fm56_1zQFf52Q) [title] Adding an Input on Zixi Broadcaster [path] Wirecast Zixi Integration - Quick Start Guide/Adding an Input in Zixi/ **To add an input on Zixi Broadcaster:** ::::WorkflowBlock :::WorkflowBlockItem In Zixi Broadcaster, in the **Inputs** section, click **+ New Input**. The **Add new Input stream** window is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/QqG5MbD2wyl6qjyH_pPtK_image.png" size="80" width="1423" height="812" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Stream ID** field, enter a unique Stream ID that will be used to identify the stream that is sent from Wirecast. ::: :::WorkflowBlockItem Select the **Push** radio button. ::: :::WorkflowBlockItem Configure additional settings as required (see [Adding Input Streams](docId:5fAp4Zp7r44WbAJLxMgV1)). ::: :::WorkflowBlockItem Click **OK**. The Input stream is added and can be viewed in the list of Inputs. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/tSVyhPGi012uPCC-7F0rc_image.png" size="80" width="870" height="348" position="center" showCaption="false"} ::: :::: [title] Configure Sending Zixi Broadcaster to Ingest NDI Stream [path] How to Use Zixi to Transport NDI Over the Public Internet/Transporting NDI Stream Using Zixi/ ## Step 1 – Log in to Sending Zixi Broadcaster First, you need to log in to the Zixi Broadcaster that you will use to *send* the stream. :::hint{type="info"} When the Broadcaster is first installed, the default user name is **'admin'** and the default password is **‘1234’**. ::: **To log in to Zixi Broadcaster:** 1. In your web browser, navigate to [http://localhost:4444](http://localhost:4444/). A user authentication window opens. 2. In the **User Name** field, enter your user name. 3. In the **Password** field, enter your password. 4. Click **OK**. The Broadcaster UI opens on the **Status** page. ## Step 2 - Create a New Transcoding Profile Create a new transcoding profile that will be used to convert the NDI video to H.265. **To create a new Transcoding Profile:** ::::WorkflowBlock :::WorkflowBlockItem In the main navigation of the Broadcaster, click **Transcoder**. ::: :::WorkflowBlockItem Click **+ New Profile**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/uJXKqlgYCJfUytR6uErhS_image.png" size="90" width="553" height="85" position="center" showCaption="false"} The **Add New Profile** window is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Cd3-xS0z-CVbpj1Zuwcfp_image.png" size="54" width="460" height="537" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Codec Type** field, select **H.265**. ::: :::WorkflowBlockItem In the **Profile Configuration** section, in the Bitrate Mode, select *VBR* from the drop-down list. ::: :::WorkflowBlockItem In the **Average Bitrat**e field, enter *10000*. ::: :::WorkflowBlockItem In the **Max Bitrate** field, enter *15000*. ::: :::WorkflowBlockItem In the **Performance** field, select **High Quality** from the drop-down list. ::: :::WorkflowBlockItem In the **Advanced Options** section, verify that the **Copy GOP from Source** checkbox *is ****not*** selected. ::: :::WorkflowBlockItem In the **GOP** field, enter *30* ::: :::WorkflowBlockItem Fill in additional parameters as necessary, for more information about configuring Transcoding Profiles, see [Creating New Transcoding Profiles](docId\:nnzH8CsjpFQlDlZCXGZ4c). ::: :::WorkflowBlockItem Click **Apply**. ::: :::: ## Step 3 - Create a New Audio Encoding Profile Create a new audio encoding profile that will be used to convert the NDI audio to AAC. **To create a new Audio Encoding Profile:** ::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Transcoder**. ::: :::WorkflowBlockItem Click **+ New Profile**. The **Add New Profile** window is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/HY5cMzJyMy3d1ZwOJpg6k_image.png" size="60" width="526" height="247" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Codec Type** field, select *AAC*. ::: :::WorkflowBlockItem In the **Profile Configuration** section, in the Bitrate field, select *512* from the drop-down list. ::: :::WorkflowBlockItem Fill in additional parameters as necessary, for more information about configuring Transcoding Profiles, see [Creating New Transcoding Profiles](docId\:nnzH8CsjpFQlDlZCXGZ4c). ::: :::WorkflowBlockItem Click **Apply**. ::: :::: ## Step 4 - Create a New NDI Input Create an Input on the sending Broadcaster to ingest the NDI stream. **To create a new NDI input:** ::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Inputs**. ::: :::WorkflowBlockItem Click **+ New Input**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ixjrwIdViPpUBcwt3UTsM_image.png" size="70" width="553" height="85" position="center" showCaption="false"} The Add new input stream window is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/lhhCvpT0nVuG5gkBHyUDp_image.png" size="70" width="543" height="290" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Stream ID** field, enter a unique name to identify this Input on your Zixi Broadcaster, e.g. *NDI\_Intput*. ::: :::WorkflowBlockItem Select the **NDI** radio button for the type of input stream. ::: :::WorkflowBlockItem In the **Stream Parameters** section, in the **Stream** field, select from the drop-down list the desired NDI stream. ::: :::WorkflowBlockItem In the **Video profile** field, select from the drop-down list the Transcoding Profile you created in [step 2 above](docId\:pov0QFytqzSyAr83hxH_e). ::: :::WorkflowBlockItem In the **Audio profile** field, select from the drop-down list the Audio Encoding profile you created in [step 3 above](docId\:pov0QFytqzSyAr83hxH_e) . ::: :::WorkflowBlockItem In the **Audio Reference Level** field, select **AAC 512K** from the drop-down lis ::: :::WorkflowBlockItem In the **Transport stream bitrate** field, verify that the value is 0 (default). ::: :::WorkflowBlockItem Fill in additional parameters as necessary, for more information about configuring NDI inputs, see [Adding NDI Streams](docId\:O9Wl9OXPTcWjR6xRnAQD1). ::: :::WorkflowBlockItem Click **OK**. ::: :::: ## Step 5 - Create a New Zixi Pull Output For this tutorial we will send a Pull Output from the sending Broadcaster to the receiving Broadcaster using Zixi Protocol with the default settings. :::hint{type="info"} The following procedure describes how to manually create a Pull Output on the sending Broadcaster. You can configure your Broadcaster to automatically allow Pull Outputs. Once this feature is enabled, when you create a "Pull Input" on your receiving Broadcaster, the corresponding Pull Output is automatically created on the sending Broadcaster. To enable automatic Pull Outputs, see [Authorization](docId\:op1GiGovcUfEyffJHwYMP) in the [Zixi Broadcaster User Guide](docId\:JGwIXYN936aeZmonZLERn). ::: **To create a Pull Output on the Broadcaster:** ::::WorkflowBlock :::WorkflowBlockItem In the Zixi Broadcaster UI, in the Main Navigation, click **Outputs**. The Outputs page opens. ::: :::WorkflowBlockItem On the **Outputs** page, click the **+ New Output** button in the Menu bar. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/JdVYsmFL8M02IraKgS12O_image.png" size="70" width="1901" height="280" position="center" showCaption="false"} The **New output** window is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/vXlXGBHUN_7VoRZFA5nII_image.png" size="50" width="309" height="289" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Output Name** field, enter a unique identifier for this Output on the Broadcaster, e.g. *DemoOutput*. ::: :::WorkflowBlockItem In the **Input Stream** field, select from the dropdown list the Input that you created in [Step 4 above](docId\:pov0QFytqzSyAr83hxH_e) . ::: :::WorkflowBlockItem For the **stream type** selection, select the **Pull** radio button. ::: :::WorkflowBlockItem In the **Stream ID** field, enter a unique identifier that will be used by the receiving Broadcaster to identify this stream. It is recommended to use the identical name as the **Input Stream** name, e.g. NDI\_Input. Make a note of the precise Stream ID (case sensitive) that you assigned. You will enter this Stream ID when you configure the receiving Broadcaster to Pull this stream in the following section. ::: :::WorkflowBlockItem In the **Remote ID** field, enter the ID of the receiving Broadcaster that will pull this stream. The ID can be found on the Status page of the UI of the receiving Broadcaster. To learn about additional configuration options, see Adding Pull Outputs in the Zixi Broadcaster UG. ::: :::WorkflowBlockItem Click **OK**. The new Pull Output with its settings is created and now appears on the Outputs screen of your Zixi Broadcaster UI. The Status should be shown as Offline (blue), since the Output hasn’t yet been “pulled” by the Receiver. ::: :::: [title] Creating Streams Using VLC [path] How to Use Zixi to Transport NDI Over the Public Internet/Creating NDI Streams/ For full motion NDI test streams, the tools package includes a VLC plugin that will render any video played in VLC to an NDI stream instead of the display. To use the VLC plugin, make sure VLC is not open on your device and select *VLC Plugin* during the tools package installation. **To create a stream using VLC:** ::::WorkflowBlock :::WorkflowBlockItem Open VLC on your device. ::: :::WorkflowBlockItem In the main navigation, select **Tools** and then click on **Preferences**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Gpys5eYsFqTzTJ1eg7ctW_image.png" size="56" width="536" height="362" position="center" showCaption="false"} The Simple Preferences window is displayed. ::: :::WorkflowBlockItem In the navigation, click **Audio**. The **Audio Settings** are displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/7-xfh8nTB28N3lx0h9xy3_image.png" size="60" width="501" height="462" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Output Module** field, select **NDI audio output** from the drop-down list. ::: :::WorkflowBlockItem Click **Save**. ::: :::WorkflowBlockItem In the navigation, click **Video**. The **Video Settings** are displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Zy3qArtUnzxRD6sRFM56h_image.png" size="60" width="444" height="410" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Output** field, select **NDI video output** from the drop-down list. ::: :::WorkflowBlockItem Click **Save**. Close and reopen VLC. Any video played now in VLC will be rendered as and NDI stream and the VLC window will display a black screen. ::: :::: [title] Configure Receiving Zixi Broadcaster to Output NDI Stream [path] How to Use Zixi to Transport NDI Over the Public Internet/Transporting NDI Stream Using Zixi/ Now that we have a Zixi Broadcaster ingesting NDI and delivering a compressed Zixi stream, as described in the previous section, we can now set up another Broadcaster at another location to ingest the Zixi stream, decode it, and publish it to the network as an NDI stream. :::hint{type="info"} The Broadcaster can also ingest any other supported input type such as HLS, RIST, SRT, or others, and publish that as NDI to the network. ::: For this tutorial we are using the Zixi protocol to transport NDI content from a Broadcaster in one location to a Broadcaster in another location so we will be ingesting a Zixi protocol stream, via a Pull request. ## Step 1 – Log in to Receiving Zixi Broadcaster First, you need to log in to the Zixi Broadcaster that you will use to *receive* the stream. :::hint{type="info"} When the Broadcaster is first installed, the default user name is '**admin**' and the default password is ‘**1234**’. ::: **To log in to Zixi Broadcaster:** 1. In your web browser, navigate to [http://localhost:4444](http://localhost:4444/). A user authentication window opens. 2. In the **User Name** field, enter your user name. 3. In the **Password** field, enter your password. 4. Click **OK**. The Broadcaster UI opens on the **Status** page. ## Step 2 - Create a New Transcoding Profile Create a transcoding profile that will be used to convert the Zixi stream to Raw video that can be used for an NDI output. **To create a new Transcoding Profile:** ::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click Transcoder. ::: :::WorkflowBlockItem Click **+ New Profile**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/9SnVHb7N_I-xicPtTelYA_image.png" size="80" width="548" height="87" position="center" showCaption="false"} The **Add New Profile** window is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/TUZq5clqsBAhnUfZwL8T9_image.png" size="70" width="533" height="269" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Codec Type** field, select **Raw Video.** ::: :::WorkflowBlockItem In the **Profile Configuration** section, in the resolution field, enter *1920 x 1080*. ::: :::WorkflowBlockItem Fill in additional parameters as necessary, for more information about configuring Transcoding Profiles, see [Creating New Transcoding Profiles](docId\:nnzH8CsjpFQlDlZCXGZ4c). ::: :::WorkflowBlockItem Click **Apply**. ::: :::: ## Step 3 - Create a New Audio Encoding Profile Create an audio encoding profile that will be used to convert the Zixi stream to Raw audio that can be used for an NDI output. **To create a new Audio Encoding Profile:** ::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Transcoder**. ::: :::WorkflowBlockItem Click **+ New Profile**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/dK4LrJAhARoF0Ahfc8aKG_image.png" size="80" width="548" height="87" position="center" showCaption="false"} The **Add New Profile** window is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/wvk6yn9UGZEei0TIaLUmh_image.png" size="70" width="543" height="209" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Codec type** field, select **Raw Audio**. ::: :::WorkflowBlockItem In the **Profile configuration** section, in the **Sampling Rate** field, select **Copy from source** from the drop-down list. ::: :::WorkflowBlockItem Click **Apply**. ::: :::: ## Step 4 - Create a New Zixi Pull Input Create a Zixi Pull Input to bring the stream from the sending Broadcaster to the receiving Broadcaster. **To create a Zixi Pull Input:** ::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Inputs**. ::: :::WorkflowBlockItem Click **+ New Input**. The **Add new input stream** window is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Le7eKyw4sK1zwI6I9Im5M_image.png" size="80" width="539" height="276" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Stream ID** field, enter a unique identifier for this stream in the receiving Broadcaster, e.g. *ReceivedNDIInput*. ::: :::WorkflowBlockItem Select the **Pull** radio button for the stream type. ::: :::WorkflowBlockItem In the **Stream Parameters** section, in the Host field, enter the hostname or IP address of the sending Broadcaster (from which the stream is being pulled). ::: :::WorkflowBlockItem In the **Stream** field, enter the precise stream ID (case sensitive) that you assigned to this stream on the sending Broadcaster in the previous section, e.g. *NDI\_Input*. ::: :::WorkflowBlockItem Fill in additional parameters as necessary, for more information about configuring pull inputs, see [Adding Pull Streams](docId\:rJL8u4EAmTpF7ZVED99i2). ::: :::WorkflowBlockItem Click **OK**. ::: :::: ## Step 5 - Create a New NDI Transcoded Output Create an NDI Transcoded Output to publish the stream as NDI. **To create an NDI Transcoded Output:** ::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Inputs**. ::: :::WorkflowBlockItem Click on the Settings icon to the right of the Input you created in [step 4 above.](docId:7NoXLSHTB0YbqzSgZmDs2) ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/pvjg8bBTb3qzUfvlQxg6W_image.png" size="80" width="541" height="155" position="center" showCaption="false"} ::: :::WorkflowBlockItem Select **Transcode** from the drop-down list. The **Edit input stream** window is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/AZl1XDih9gMy-IoPadGrS_image.png" size="50" width="383" height="511" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Stream ID** field, enter a unique name to identify this Output on your Zixi Broadcaster, e.g. *NDI\_Output*. ::: :::WorkflowBlockItem In the **Video Profile** field, select from the drop-down list the raw video profile you created in [Step 2 above](docId:7NoXLSHTB0YbqzSgZmDs2) . ::: :::WorkflowBlockItem In the **Audio Profile** field, select from the drop-down list the raw audio profile you created in [Step 3 above.](docId:7NoXLSHTB0YbqzSgZmDs2) ::: :::WorkflowBlockItem In the **Output Typ**e field, select **NDI** from the drop-down list. ::: :::WorkflowBlockItem Fill in additional parameters as necessary. For more information about configuring NDI Outputs, see [Creating an NDI Output](docId\:TZDAsqITtN_mwxOOS9KF6). ::: :::WorkflowBlockItem Click **Ok**. ::: :::: ## Step 6 - Monitor the Stream You can monitor the stream using the NewTek Studio Monitor program included in the tools package from NewTek. This program can be used to verify that the Zixi Broadcaster is successfully publishing the NDI stream on the network. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/HgijK7-nXl2TWT0Tn1SoU_image.png" size="60" width="602" height="428" position="center" showCaption="false"} [title] Transporting NDI Stream Using Zixi [path] How to Use Zixi to Transport NDI Over the Public Internet/ The following sections explain how to send your stream end-to-end through the Zixi system. For our use case we will be streaming a 1080p video using HEVC/H.265 stream and NVIDIA GPU. The quality parameters are set to minimize quality loss and provide mezzanine quality video at 1/10th the original bitrate of the NDI stream. We will use a Zixi Pull Output to send the stream from the sending Broadcaster to the receiving Broadcaster. - [Configure Sending Zixi Broadcaster to Ingest NDI Stream](docId\:pov0QFytqzSyAr83hxH_e) - [Configure Receiving Zixi Broadcaster to Output NDI Stream](docId:7NoXLSHTB0YbqzSgZmDs2) [title] Creating NDI Streams [path] How to Use Zixi to Transport NDI Over the Public Internet/ A variety of tools from NewTek, downloadable at [https://ndi.tv/tools/](https://ndi.tv/tools/), are available to create and monitor NDI streams. The tools package is available for Windows and Mac. Inside the tools package is a Test Pattern program that will publish an NDI stream with various test patterns on the network. These test patterns are 1 FPS so they are not so useful for testing realistic video workflows, but the Test Pattern program is useful for verifying that mDNS is working on the network and on the Linux host where the Broadcaster is installed. Below is a description of some of the tools that can be installed as part of the tools package. - [Creating Streams Using VLC](docId\:wYSge6F1H6Xo8TwlndoaO) - [Creating Streams Using NewTek Connect](docId\:kIW9CsA732C3ynGPyFuPe) [title] Adding an Input on Zixi Broadcaster [path] OBS Zixi Integration - Quick Start Guide Home/Adding an Input in Zixi/ ## Zixi Configuration To contribute a stream from OBS Studio into the Zixi ecosystem, you first need to define an input stream on a Zixi Broadcaster. If you are managing a Broadcaster though its native UI, you will add a new input stream under the Inputs tab. Specify a Stream ID and select the “Push” radio button. The IP address that you will push the stream to from OBS Studio is the same IP used to view the Broadcaster UI and the port will be 2088, unless you changed the default on the Broadcaster. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/kd9Wy70Z_2AIY2yBE5fAB-20260513-170211.png) ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/DCzx1GH5VMUsAV0INTBb7-20260513-170213.png) [title] Adding an Input on ZEN Master [path] OBS Zixi Integration - Quick Start Guide Home/Adding an Input in Zixi/ If you are using ZEN Master, you will create a new Zixi type source and select the “Other” radio button. Provide a Source Name and fill in other details on the form. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/6aNZzeoli_3GmDA3Cl3Yo-20260513-170620.png" size="50" width="418" height="832" position="center" caption="ZEN Master source input configuration" alt="ZEN Master source input configuration" showCaption="true"} Once the Source is created, the IP address, Port, and Stream ID that you will use in OBS Studio are displayed in the Configuration panel. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Sl4NH6GfbxQnFRHTXe2d2-20260513-170736.png" size="60" width="448" height="195" position="center" caption="Configuration info for OBS" alt="Configuration info for OBS" showCaption="true"} If you are using AWS MediaConnect or a MediaConnect based service, you will need to use the IP address, Port, and Stream ID displayed for the Flow in the MediaConnect console. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/UAzyNN_K0vO2k8-9IiBWj-20260513-170843.png" size="80" width="808" height="196" position="center" caption="Mediaconnect configuration" alt="Mediaconnect configuration" showCaption="true"} ### [title] Installing OBS Studio for Zixi [path] OBS Zixi Integration - Quick Start Guide Home/ The OBS Studio integration consists of a fork of OBS Studio and a Zixi Feeder plug-in. Both are available for the Windows platform, and can be downloaded from the Zixi Customer Portal. To use OBS with Zixi as an option you are required to install both. :::hint{type="danger"} If you already have a version of OBS installed from a location outside of our portal you will need to uninstall this before following the steps below. ::: In addition, OBS studio requires the installation of Visual Studio Runtime.   **To install OBS Studio:** ::::WorkflowBlock :::WorkflowBlockItem Go to [https://portal.zixi.com/self-registration/OBS\_STUDIO\_ZIXI\_FEEDER](https://portal.zixi.com/self-registration/OBS_STUDIO_ZIXI_FEEDER). The **Create Account** window opens. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/t07V7IfgAPIr8VIq_zv9w_image.png" size="50" width="443" height="816" position="center" darkWidth="443" darkHeight="816" showCaption="false"} ::: :::WorkflowBlockItem Fill in your details and then click **Create Account**. The **Zixi Customer Portal** window is displayed. ::: :::WorkflowBlockItem In the main menu, click **Software**, and then click the links to download **OBS Studio with Zixi Integration** and **Zixi Feeder for OBS Studio**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/kecQQB2lwb19EsX7FXs1t_image.png" size="78" width="1031" height="396" position="center" darkWidth="1031" darkHeight="396" showCaption="false"} ::: :::WorkflowBlockItem On your desktop, first install **OBS Studio with Zixi Integration**. ::: :::WorkflowBlockItem Then, install the **Zixi Feeder for OBS Studio plug-in**. If you have already installed OBS Studio with Zixi integration but do not yet have the Zixi Feeder plug-in, you can install it through OBS Studio. Click on Help > Download Zixi Support. This will take you to the Customer portal mentioned above. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/PvJgEFiFmIRQVYmKFRZMw-20260513-171529.png" size="82" width="460" height="216" position="center" caption="Download zixi support from OBS" alt="Download zixi support from OBS" showCaption="true"} ::: :::WorkflowBlockItem Exit **OBS Studio** and restart **OBS Studio**. ::: :::WorkflowBlockItem If all has gone correctly you will see Zixi Broadcaster listed in Settings > Stream > Service. *See example.* ![Settings window showing Zixi Broadcaster service](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/VnwtaoHa659znUalleNr7-20260513-165337.png "Settings window showing Zixi Broadcaster service") ::: :::: :::hint{type="info"} When running OBS if you receive an error regarding the VC runtime not being found, install the Visual Studio runtime available at [https://obsproject.com/visual-studio-2017-runtimes](https://obsproject.com/visual-studio-2017-runtimes). ::: [title] Wirecast Zixi Integration - Quick Start Guide [path] / Wirecast allows you to stream using multiple live cameras, bring in remote guests and screenshares, and dynamically mix in other media-like movies, images, and sounds. Easily add production features such as stinger transitions, instant replay, playlists, built-in titles, chroma key, virtual sets, live scoreboards and clocks. Wirecast is ideal for broadcasting professional-looking live internet shows, news, online gaming, sporting events, concerts, church services, corporate meetings, lectures and much more. Telestream Wirecast integration with the Zixi video delivery platform, enables users to send Zixi transport streams to any Zixi on-premise platform or cloud-based service. Using the Zixi platform, Wirecast users can dramatically improve the quality of first mile ingest to popular CDNs and for contribution workflows regardless of distance. By centralizing the ingest point of presence (POP) using the Zixi platform, Wirecast users can have a simple contribution setup for global event ingest. Wirecast provides a variety of capture sources (screen, file, webcam, etc), baseband capture devices, and mezzanine quality NDI network sources. This guide provides information on how to configure Telestream Wirecast to contribute video feeds into the Zixi ecosystem. - [Installing Wirecast](docId\:kwk4QSB-HIp40S_21RmIQ) - [Adding an Input in Zixi](docId\:xCAbzl4cFNZXt6O0lVoBV) - [Finding the Connection Details](docId:1f_YWGanCwtNWBV-Nm5g_) - [Wirecast Configuration](docId\:f8oxDf6k0Go4005BtrT4e) [title] Adding an Input on ZEN Master [path] Wirecast Zixi Integration - Quick Start Guide/Adding an Input in Zixi/ If you are using ZEN Master, you add the input by creating a new Zixi type Source. **To add a source on ZEN Master:** ::::WorkflowBlock :::WorkflowBlockItem Go to the **Sources** screen. ::: :::WorkflowBlockItem Click **+Add**. ::: :::WorkflowBlockItem Select the **Zixi** Source type. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/fcsN65nBlqUz1xzZtoEce_image.png" size="60" width="825" height="267" position="center" showCaption="false"} The **Create Zixi Source** window opens. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/rs06QpDGZTbmUsGw55_5E_image.png" size="52" width="319" height="840" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Name** field enter a name for the Source. ::: :::WorkflowBlockItem Under **Mode**, select **Push**. ::: :::WorkflowBlockItem Under **Application**, select **Other**. ::: :::WorkflowBlockItem Fill in additional details for the Source (see ZEN Master User Guide for detailed instructions). ::: :::WorkflowBlockItem Click **Save**. The Source is created and appears in the list of Sources. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/HhWgm_Zxw0wiSG7lHrqes_image.png" size="88" width="579" height="168" position="center" showCaption="false"} ::: :::: [title] Finding Connection Details in Zixi Broadcaster [path] Wirecast Zixi Integration - Quick Start Guide/Finding the Connection Details/ **To find the connection details on Zixi Broadcaster:** ::::WorkflowBlock :::WorkflowBlockItem In Zixi Broadcaster go to the Inputs screen. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Cl31jtdnDOK6TjlJ5rJWG_image.png" size="88" width="1424" height="572" position="center" showCaption="false"} ::: :::WorkflowBlockItem For the *IP Address*, you will use the same IP that you used to access the Broadcaster UI. ::: :::WorkflowBlockItem The *Stream ID* is shown in the **ID** column for the Wirecast Input. ::: :::WorkflowBlockItem By default, the Port is set as **2088**. If you changed the Port configuration, then use the Port that you configured. ::: :::: [title] Finding Connection Details in MediaConnect [path] Wirecast Zixi Integration - Quick Start Guide/Finding the Connection Details/ If you are using AWS MediaConnect or a MediaConnect based service, you will need to use the IP address, Port, and Stream ID displayed for the **Flow** in the **MediaConnect Console**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/3Ptj39aGUWsDw5qEyETWt_image.png" size="90" width="1108" height="240" position="center" showCaption="false"} [title] Adding an Input in Zixi [path] Wirecast Zixi Integration - Quick Start Guide/ To contribute a stream from Wirecast into the Zixi ecosystem, you first need to define an input stream on the Zixi side through the Zixi Broadcaster or ZEN Master. - [Adding an Input on Zixi Broadcaster](docId\:KIO_bMDHgU3QIEdD_wwbV) - [Adding an Input on ZEN Master](docId:5lNjohhxUHFDUdEcwTf6F) [title] Finding Connection Details in ZEN Master [path] Wirecast Zixi Integration - Quick Start Guide/Finding the Connection Details/ The connection details are used in Wirecast to connect to Zixi. **To find the connection details on ZEN Master:** ::::WorkflowBlock :::WorkflowBlockItem Go to the **Sources** screen. ::: :::WorkflowBlockItem Click the Source that you have added. ::: :::WorkflowBlockItem croll down the Details pane (right-hand pane) until you reach the **Configuration** section. ::: :::WorkflowBlockItem The **Configuration** section includes the **IP Address**, **Port**, and **Stream ID** details that you will use in Wirecast. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ou1l2Ue1yRVu05YihBh_r_image.png" size="50" width="334" height="348" position="center" showCaption="false"} ::: :::: [title] Finding the Connection Details [path] Wirecast Zixi Integration - Quick Start Guide/ When you configure the stream in Wirecast, you will need the following information: - IP Address - Stream ID - Port The following steps will explain how to find this information for each of the different methods. - [Finding Connection Details in Zixi Broadcaster](docId\:OtTRF4xgr_vd34i7ztsY0) - [Finding Connection Details in ZEN Master](docId:3Bx01RbZ48FMPoRTv57N5) - [Finding Connection Details in MediaConnect](docId:2DIJylhLXxdL7ZwwVNAfd) [title] Installing Wirecast [path] Wirecast Zixi Integration - Quick Start Guide/ The Wirecast integration consists of a specially built Zixi Feeder application that is downloaded and installed on a Windows or Mac computer and runs as a service or background process on Mac. **To install Wirecast Feeder:** ::::WorkflowBlock :::WorkflowBlockItem Go to: [https://portal.zixi.com/self-registration/WIRECAST\_FEEDER](https://portal.zixi.com/self-registration/WIRECAST_FEEDER). ::: :::WorkflowBlockItem The **Create Account** window opens. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/NkcTzJKArSXDEq-L9CE9y_image.png" size="30" width="420" height="800" position="center" showCaption="false"} ::: :::WorkflowBlockItem Fill in your details and then click **Create Account**. ::: :::WorkflowBlockItem In the main menu, click **Software** and then under **Zixi Feeder for Wirecast**, click the link to download the Windows version or the Mac version. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/_j9_9FWGZYE05Rswh6S6H_image.png" size="70" width="1032" height="312" position="center" showCaption="false"} ::: :::WorkflowBlockItem On your desktop, install the Zixi Feeder for Wirecast plugin. ::: :::: [title] Wirecast Zixi ZEC Quick Start Guide: Introduction [path] Wirecast Zixi ZEC Quick Start Guide Home/ Wirecast allows you to stream using multiple live cameras, bring in remote guests and screenshares, and dynamically mix in other media-like movies, images, and sounds. Easily add production features such as stinger transitions, instant replay, playlists, built-in titles, chroma key, virtual sets, live scoreboards and clocks. Wirecast is ideal for broadcasting professional-looking live internet shows, news, online gaming, sporting events, concerts, church services, corporate meetings, lectures and much more. Telestream Wirecast integration with the Zixi video delivery platform, enables users to send Zixi transport streams to any Zixi on-premise platform or cloud-based service. Using the Zixi platform, Wirecast users can dramatically improve the quality of first mile ingest to popular CDNs and for contribution workflows regardless of distance. By centralizing the ingest point of presence (POP) using the Zixi platform, Wirecast users can have a simple contribution setup for global event ingest. Wirecast provides a variety of capture sources (screen, file, webcam, etc.), baseband capture devices, and mezzanine quality NDI network sources. This guide is an update to a previous guide titled “Wirecast Zixi Integration – Quick Start Guide” and provides updated information on how to configure Telestream Wirecast to contribute video feeds into the Zixi ecosystem using ZEC and replacing the legacy Wirecast Plug-in. [title] Wirecast Zixi ZEC Quick Start Guide Home [path] / Wirecast allows you to stream using multiple live cameras, bring in remote guests and screenshares, and dynamically mix in other media-like movies, images, and sounds. Easily add production features such as stinger transitions, instant replay, playlists, built-in titles, chroma key, virtual sets, live scoreboards and clocks. Wirecast is ideal for broadcasting professional-looking live internet shows, news, online gaming, sporting events, concerts, church services, corporate meetings, lectures and much more. Telestream Wirecast integration with the Zixi video delivery platform, enables users to send Zixi transport streams to any Zixi on-premise platform or cloud-based service. Using the Zixi platform, Wirecast users can dramatically improve the quality of first mile ingest to popular CDNs and for contribution workflows regardless of distance. By centralizing the ingest point of presence (POP) using the Zixi platform, Wirecast users can have a simple contribution setup for global event ingest. Wirecast provides a variety of capture sources (screen, file, webcam, etc.), baseband capture devices, and mezzanine quality NDI network sources. This guide is an update to a previous guide titled “Wirecast Zixi Integration – Quick Start Guide” and provides updated information on how to configure Telestream Wirecast to contribute video feeds into the Zixi ecosystem using ZEC and replacing the legacy Wirecast Plug-in. - [Wirecast Zixi ZEC Quick Start Guide: Introduction](docId\:fOPGOrI8wW12YCrc6J6ua) - [Step 1 - Downloading ZEC and Generating License Key](docId:47EfUSB4oCNHnhLv-9Zpu) - [Step 2 - Setting ZEC to receive RTMP](docId\:PJRfX0gY0NH_48Cw-Gu6b) - [Step 3 - Adding an input in ZEC](docId\:AvFbjVt1PU8tpvvpxcf9s) - [Step 4 - Wirecast Configuration](docId\:WQoAYMGpRevndnStBS1MU) - [Step 5 (optional) - Saving the Input Stream Configuration](docId\:mCNp0BXd9wKl13kEPzLEI) - [Step 6 - Pushing the stream to a Zixi Broadcaster or to a Media Connect](docId\:aao_QKJ_QB9YYp9Riqctq) [title] Step 3 - Adding an input in ZEC [path] Wirecast Zixi ZEC Quick Start Guide Home/ If you did *not* select the **Allow automatic RTMP input** setting, then to contribute a stream from Wirecast into the Zixi ecosystem, you will need to define an input stream on the Zixi side through ZEC. **To add an input on ZEC:** ::::WorkflowBlock :::WorkflowBlockItem On ZEC, in the **Inputs** section, click **+ New Input**. The **Add new Input stream** window is displayed. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/akJek6Llcd0Y0vgbS6CAS_image.png) ::: :::WorkflowBlockItem In the **Stream ID** field, enter a unique Stream ID that will be used to identify the stream that is sent from Wirecast. ::: :::WorkflowBlockItem Select the **RTMP** radio button. ::: :::WorkflowBlockItem Under **Stream Parameters** section select the **Push** radio button. ::: :::WorkflowBlockItem Click **OK**. ::: :::: [title] Step 6 - Pushing the stream to a Zixi Broadcaster or to a Media Connect [path] Wirecast Zixi ZEC Quick Start Guide Home/ We now have an RTMP stream from Wirecast being pushed into ZEC where it can be converted into a Zixi stream.  At this point we are ready to push this Zixi stream to a Broadcaster or to MediaConnect over the public Internet. ## Configuring the connection directly on ZEC We can configure the connection to Broadcaster directly on ZEC, by adding a Push Output on ZEC and then a Push Input on the Broadcaster. See the Broadcaster and ZEC User Manuals for details. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ZSE7GyDW27wThrFRlIbxw_image.png) ## Configuring the connection directly on ZEC We can also use ZEN Master to create this workflow.  First, we need to ensure that the ZEC device is added to ZEN Master under **Zixi Edge Devices**. Then we’ll create a **Zixi Push Source** with **ZEC** as the **Application** and select the **ZEC device** and the relevant **ZEC Input**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/kkmcD00D31_u5wuINEQzy_image.png) For detailed instructions, see the [ZEN Master User Guide](docId\:vzz5bE4XXIpP9wLuLps4N). [title] Step 5 (optional) - Saving the Input Stream Configuration [path] Wirecast Zixi ZEC Quick Start Guide Home/ When you start the Wirecast stream, **ZEC** will automatically add the RTMP stream to the **Input** and remove it once you stop the stream on Wirecast.  If you want you can save the input stream, so you can use the input stream configuration at a later time. **To save the stream configuration:** ::::WorkflowBlock :::WorkflowBlockItem In **ZEC**, go to **Inputs**. ::: :::WorkflowBlockItem Click the Gear icon on the right side of the Input that appears. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/-fgP_Q9fBqajum8TfRtd6_image.png) ::: :::WorkflowBlockItem Click **Save**. ::: :::: We can go ahead and configure ZEC to send this stream as a **Zixi Push output** to a **Broadcaster** or **MediaConnect** either on the **Broadcaster** and **ZEC** UI’s or through **ZEN Master**. [title] Step 4 - Wirecast Configuration [path] Wirecast Zixi ZEC Quick Start Guide Home/ Once the ZEC is installed and Wirecast is configured, the Wirecast encoder can send the encoded stream to ZEC via RTMP.  **To configure RTMP output on Wirecast:** ::::WorkflowBlock :::WorkflowBlockItem In **Wirecast**, go to **Output > Output Settings**. ::: :::WorkflowBlockItem Click **Add**. ::: :::WorkflowBlockItem Under **Select an Output Destination** choose **RTMP Server** and in the Destination field, click **More**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/vi5_UtbCEmKq5-0NQkb_l_image.png) ::: :::WorkflowBlockItem In the **Address** field, enter the IP address of the ZEC in the format displayed above. ::: :::WorkflowBlockItem Configure other properties in the dialog as needed. ::: :::: Wirecast is now ready to send an RTMP stream locally to ZEC.  [title] Using Terraform with OCI [path] / Terraform is a tool created by HashiCorp that lets you define, provision, and manage cloud infrastructure using code. Instead of writing manual deployment steps, you define the desired end state of your infrastructure, and Terraform determines how to build it. Terraform with Oracle Cloud Infrastructure (OCI) means using Infrastructure as Code to create and manage Oracle Cloud resources like VCNs, subnets, compute instances, databases, IAM, load balancers, and OKE clusters. While this guide focuses on OCI, you can apply the same approach to any cloud provider Terraform supports. To learn more about Terraform, see HashiCorp's documentation: [Automate Infrastructure on Any Cloud](https://developer.hashicorp.com/terraform). # Content - Create a Terraform-enabled Broadcaster Cluster - (Optional) Create a Broadcaster Placeholder - Complete Prerequisites - Create OCI Objects - Customize Terraform Variables - Run Terraform Script # Create a Terraform-enabled Broadcaster Cluster First, use ZEN Master to create a Zixi Broadcaster Cluster that is enabled for Terraform scripts. The Cluster ID and name will be passed in the Terraform script. :::::WorkflowBlock :::WorkflowBlockItem In a web browser, navigate to **https\://\{youraccount}.zen.zixi.com** ::: :::WorkflowBlockItem When you sign in, you should see the Zixi ZEN Master dashboard. ::: :::WorkflowBlockItem In the left navigation, select **Broadcasters**. ::: :::WorkflowBlockItem Click **+Add** to create a new Broadcaster Cluster. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/30mN7l9l1n5MXZV9DE6Du_image.png) ::: :::WorkflowBlockItem In the **Create New Broadcaster Cluster** dialog, provide a Cluster **Name** and one or more **Tags**. ::: :::WorkflowBlockItem For **Management Type**, select **Manual**. ::: :::WorkflowBlockItem Select the checkbox for **Terraform Deployment Support**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/vjWljUc8wcPGrryFXcFtE_image.png) ::: ::::WorkflowBlockItem For **Broadcaster Version**, select the desired Broadcaster version that you would like to run on your cloud service machines. :::hint{type="info"} - Broadcaster versions available for your account can be viewed and modified on the Customer Portal. - Select a Broadcaster version that supports the type of processing that will be done on this Cluster. ::: :::: :::WorkflowBlockItem For **Activation Key**, enter your Zixi Broadcaster license activation key. ::: :::WorkflowBlockItem For **SSH Key**, enter the SSH key pair used to establish a secure SSH tunnel and allow ZEN Master to access and manage the Broadcaster. ::: :::WorkflowBlockItem For **API User**, enter the username for ZEN Master to access the Broadcaster API. ::: :::WorkflowBlockItem For **API Password**, enter the password for ZEN Master to access the Broadcaster API. ::: :::WorkflowBlockItem Customize the other Cluster fields as needed. For details, see [Adding a Broadcaster Cluster – Manual](docId\:lUGqITvwdm0YIpL102_px). ::: ::::: # (Optional) Create a Broadcaster Placeholder When using Terraform, creating a Broadcaster in ZEN Master is optional. If you want to set the Broadcaster name and override some configuration fields, you can create a Broadcaster placeholder in ZEN Master that OCI will use. When OCI creates Broadcasters, it creates system-generated Broadcaster names. :::::WorkflowBlock :::WorkflowBlockItem Return to ZEN Master. ::: :::WorkflowBlockItem In the left navigation, select **Broadcasters**. ::: :::WorkflowBlockItem In the Broadcaster Cluster list, click on your Cluster name that is configured for Terraform Deployment Support. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/75zFTKjzvqo-GKXxwm9na_image.png) ::: :::WorkflowBlockItem In the Broadcaster Cluster details screen, click **+ Add Broadcaster**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/p-6Tu7spSREJCaxKyfx9y_image.png) ::: :::WorkflowBlockItem In the **Create New Broadcaster** dialog, provide a **Name.** ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/LChEHvprNBioeBaHwYA96_image.png) ::: :::WorkflowBlockItem For **API User**, enter the username for ZEN Master to access the Broadcaster API. ::: :::WorkflowBlockItem For **API Password**, enter the password for ZEN Master to access the Broadcaster API. ::: :::WorkflowBlockItem For **SSH Key**, enter the SSH key pair used to establish a secure SSH tunnel and allow ZEN Master to access and manage the Broadcaster. ::: :::WorkflowBlockItem Customize the other Broadcaster fields as needed. For details, see [Adding a Broadcaster to a Manual Cluster](docId\:xYscySO498lY77ZjQr-51). ::: ::::WorkflowBlockItem :::hint{type="info"} - Values that you set when creating a Broadcaster placeholder will override the values from the Cluster. - Creating a placeholder allows you to specify a custom Broadcaster name. Otherwise, the Terraform script creates system-generated Broadcaster names. ::: :::: ::::: # Complete Prerequisites Review the Zixi public repo for using Terraform with OCI and install the system requirements. ::::WorkflowBlock :::WorkflowBlockItem In a browser, navigate to the Zixi Customer Portal ([https://portal.zixi.com) ](https://portal.zixi.com)and log in with your credentials. ::: :::WorkflowBlockItem In the left navigation, select **Documentation**. ::: :::WorkflowBlockItem Select **BY TYPE** and then **ZEN Master**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/vHDqCqTgv5vFFVrfGCkSN_image.png) ::: :::WorkflowBlockItem Download the **TerraformOCIRepo.zip** file and unzip it. ::: :::WorkflowBlockItem In the **OCI-Broadcast-Cluster-TF** repo, open the **README.md** file. ::: :::WorkflowBlockItem Review the **Prerequisites** section and follow the steps: - Install Terraform CLI on your computer. - Create an OCI API Key. - Upload the public key file (public.pem) to the OCI console. - Copy the fingerprint shown after you upload the public key file. ::: :::: # Create OCI Objects Before running the Terraform script, the following OCI resources must exist. ::::WorkflowBlock :::WorkflowBlockItem Return to the **README.md** file in the **OCI-Broadcast-Cluster-TF** repo. ::: :::WorkflowBlockItem Review the **OCI Prerequisites** section to create OCI objects. ::: :::WorkflowBlockItem In a browser, navigate to and log in to the Oracle dashboard. ::: :::WorkflowBlockItem Using the Oracle dashboard, create the following objects: - **Compartment** - A fundamental logical container within Oracle Cloud Infrastructure used to organize, isolate, and secure cloud resources. - **VCN** - A Virtual Cloud Network (VCN) with a public subnet and an Internet Gateway (IGW) is the standard baseline setup for running public-facing cloud infrastructure. - **NSG** - Network Security Groups (NSGs) allow you to apply granular firewall rules directly to specific virtual network cards (VNICs). - **Vault** - Used to securely store your ZM API key (or any other media orchestration credentials) in OCI. - **Master Encryption Key** - Before you can save a secret, OCI requires a master key to encrypt the secret's contents. - **Secret** - Now that the vault structure and encryption framework are ready, you can create the actual secret. - **Dynamic Group** - This allows your compute instances to securely access cloud resources—like pulling that ZM API key from the OCI Vault you just created—without hardcoding user credentials on the server. - **IAM Policy** - Because you want this policy to apply to the tenancy level rather than just a single sub-compartment, the policy file itself must be attached to your Root compartment. ::: :::: # Customize Terraform Variables Review and customize the Terraform variables used by the script. :::::WorkflowBlock :::WorkflowBlockItem Return to the **OCI-Broadcast-Cluster-TF** repo. ::: ::::WorkflowBlockItem Open the **CUSTOMER\_INPUTS.md** file. Use this as a reference that defines all the variables you will configure. You will NOT update this file. :::hint{type="info"} What you will edit: - terraform.tfvars - Variable values What you will NOT edit: - Terraform resource structure - Cloud-init bootstrap logic ::: :::: :::WorkflowBlockItem Duplicate the **terraform.tfvars.example** file and rename it **terraform.tfvars** ::: :::WorkflowBlockItem Open the newly created **terraform.tfvars** file. This is the **only file** you will edit. Customize this file with your variable values. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/0eKmKJMCi2QfOnjIrdlaL_image.png) ::: ::::: # Run Terraform Script Running a Terraform script with OCI follows the standard "Init, Plan, Apply" workflow. Under the hood, it instructs Oracle's cloud API to build, modify, or destroy Oracle-specific resources. ::::WorkflowBlock :::WorkflowBlockItem In a terminal window on your computer, navigate to the **OCI-Broadcast-Cluster-TF** repo folder. ::: :::WorkflowBlockItem First, run the **init** command (Setup): This prepares your working directory and downloads plugins. - It reads your code, determines the cloud provider, and downloads the plugins needed to talk to those APIs. - It sets up the backend with your state file. ```bash terraform init ``` ::: :::WorkflowBlockItem Next, run the **plan** command (Preview): This lets you see what Terraform intends to do before making any changes to your cloud environment. - It checks the current state of your cloud infrastructure. - It generates a list of what will be created, modified, or destroyed. ```bash terraform plan ``` ::: :::WorkflowBlockItem Then, run the **apply** command (Execute): This takes your configuration and updates your cloud infrastructure. - It makes the API calls to your cloud provider to build, update, or delete resources. - Once the resources are built, Terraform records their IDs and metadata into your state file. ```bash terraform apply ``` ::: :::WorkflowBlockItem For more details about working with OCI, see Terraform's document: [Get Started - OCI](https://developer.hashicorp.com/terraform/tutorials/oci-get-started) ::: :::: :::hint{type="info"} Notes: - The script sets up an OCI vault and secret to securely store the ZEN Master API Key. No credentials are stored on the instances. - The cloud-init script makes calls to the ZEN Master API. - Cluster and Broadcaster management is still done within ZEN Master. - If you want another instance, modify the template, redeploy, and Terraform takes care of it. - If you want custom images (AMIs), add them to the script. ::: [title] Step 2 - Setting ZEC to receive RTMP [path] Wirecast Zixi ZEC Quick Start Guide Home/ Before adding streams, we need to configure ZEC to accept RTMP. It is possible to have RTMP inputs automatically connect by checking the **Allow automatic RTMP input** check box. In this case you could skip the adding an input section below. Once Wirecast is pushing the stream you can "Save" it on the ZEC inputs page to preserve the input even when Wirecast is not pushing the stream. To configure RTMP settings: ::::WorkflowBlock :::WorkflowBlockItem On the ZEC UI, go to **SETTINGS > Live Protocols**. ::: :::WorkflowBlockItem In the **RTMP Server** section, select the **Enable RTMP Server** checkbox. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/joV9KtkVrk7a1XlVcYOxs_image.png) ::: :::WorkflowBlockItem Ensure that the **RTMP server port** is set **1935**. Optionally check **Allow automatic RTMP input**. This allows RTMP inputs to automatically connect. In this case you will not need to manually add these inputs ::: :::: [title] Wirecast Configuration [path] Wirecast Zixi Integration - Quick Start Guide/ Once the Wirecast Feeder is installed and Wirecast is configured, the Wirecast encoder will configure the Feeder with the IP address, Port, Stream ID, etc. and will send the encoded stream to the Feeder via RTMP on the local computer. All of this happens behind the scenes. You only have to configure Wirecast just like any other stream destination in Wirecast. **To configure Wirecast:** ::::WorkflowBlock :::WorkflowBlockItem In Wirecast, go to **Output > Output Settings**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/zZX98CXhesUqmDDagMrOW_image.png" size="40" width="406" height="409" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Destination** field, click **More**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/iLlb1k3c05vejIlRTdIUl_image.png" size="64" width="729" height="233" position="center" showCaption="false"} ::: :::WorkflowBlockItem Scroll down and select the **Zixi** checkbox and click **OK**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/tZdaqSGTA5p45TZ7TVNmj_image.png" size="50" width="752" height="648" position="center" showCaption="false"} ::: :::WorkflowBlockItem Select **Zixi** as the **Output Destination**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/VEgcLaYMGYEbUpXBPYpZB_image.png" size="50" width="727" height="595" position="center" showCaption="false"} ::: :::WorkflowBlockItem Configure the Zixi destination with the **Broadcaster IP address**, **Ports**, and **Channel Name** (Stream ID) from the Broadcaster configuration above. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/IkZ-1_iowRcwK8KPqKoJO_image.png) ::: :::: At this point, your Zixi destination is configured and the Zixi protocol will be used to deliver your stream to your Broadcaster or AWS MediaConnect. Once you start streaming, you should see the input stream show up in the Broadcaster UI or in ZEN Master or in AWS MediaConnect. If you do not see the input stream, verify that your local firewall is not blocking outbound UDP traffic on the port specified above and that the firewall on your Broadcaster is not blocking inbound UDP traffic on that port or verify that your AWS MediaConnect Flow is active. [title] Step 1 - Downloading ZEC and Generating License Key [path] Wirecast Zixi ZEC Quick Start Guide Home/ Following a registration process, you can download the ZEC software and generate a license key for it. **To download ZEC and generate a license key:** ::::WorkflowBlock :::WorkflowBlockItem Go to the [Zixi Customer Portal ](https://portal.zixi.com/dashboard) and create a new account on or log into existing account. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/VwGDuudxyBcIGW8dBcseB_image.png" size="60" width="785" height="1267" position="center" showCaption="false"} ::: :::WorkflowBlockItem On the main menu, click **My Settings**. ::: :::WorkflowBlockItem Verify that you are subscribed to Zixi Edge Compute software. If not subscribed yet, under the **You can subscribe to the following packages** section, scroll down until you find **Zixi Edge Compute (ZEC)** and click **Subscribe**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/zrndFMHfDWD_LhRwIX2QF_image.png) ::: :::WorkflowBlockItem On the main menu, click **License Keys** and click **Generate a key** for Zixi Edge Compute. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/KFFTeZ2r6RhEmkqgqXfIt_image.png) ::: :::WorkflowBlockItem Copy the generated key. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/_yfJbmaOBujPBCCB_xYFm_image.png) ::: :::WorkflowBlockItem On the ZEC UI select **Options** and **Activate License**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Toi340JGJ6SjocGTAG25b_image.png) ::: :::WorkflowBlockItem Paste in the license key and click **Activate**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/QqbeM-kI5_wj37OTWmsJn_image.png" size="60" width="636" height="467" position="center" showCaption="false"} ::: :::: [space] Market Switching (/market-switching) [title] Appendix E: Glossary of ESAM Terms [path] Zixi Market Switching: ESAM Agent/Untitled/ | **Acronym/Name ** | **Description** | | ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **ESAM** | Event Scheduling and Metadata API – Cablelabs (v. I03) standard used for bridging communication between the Broadcaster and external SDS | | **ESNI** | Event Scheduling and Notification Interface – SCTE-224 standard used for scheduling content switches. This is an option for an SDS | | **POIS** | Placement Opportunity and Information Service – SCTE-130 standard with logic on how to create, modify, replace, delete, passthrough SCTE-35 messages | | **PSN** | Process Status Notification – message sent from the ESAM Agent to the SDS notifying the SDS of the status/progress of the Agent completing the instructions sent in the SPN | | **SAS** | Signal Acquisition Service – system that captures the SCTE-35 messages and is ESAM capable. The Broadcaster and ESAM Agent together make up Zixi’s SAS | | **SDS** | Signal Decision Service – external system with schedule or logic for handling SCTE-35 messages. Also, can send unsolicited commands to the Agent for immediate switches or SCTE creation | | **SPE** | Signal Processing Event – message sent from the ESAM Agent to the SDS requesting instructions | | **SPN** | Signal Processing Notification – message from the SDS to the ESAM Agent with instructions (solicited or unsolicited) | [title] How the Zixi ESAM Agent Works [path] Zixi Market Switching: ESAM Agent/Untitled/ ![Market Switching via ESAM](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-SZToBrUd6hiF_KvNNG3hC-20250602-150742.png) ## Content Switching The content switching component of the agent leverages the Broadcaster’s `redirect_client.json` API call to switch the input connected to an output regardless of input or output type. To adhere to scheduling requirements, Zixi employs multiple types of switches as follows: - When switching off the source that reported the SCTE message that triggered the switch, the broadcaster will search for the PTS within that stream before switching. - When switching from a different source to the source that reported the SCTE that triggered the switch (typical in a blackout workflow), the broadcaster will search the upcoming source for the PTS. - If neither situation is applicable, the broadcaster will attempt to search for PTS within the upcoming feed (assuming streams are synchronized in that circumstance). If PTS is not found, it will switch after the pre-defined timeout period. All switching is seamless, meaning the broadcaster will wait for an i-frame (which generally coincides with a SCTE message’s defined PTS regardless) ## SCTE Manipulation - The SCTE Manipulation component of the agent interfaces with an external POIS server. The agent sends all relevant SCTE messages to the external decisioning service as base64 and receives back an action to take on existing stream SCTE and updated SCTE payload in base64 if applicable. Actions are taken from the agent via the Broadcaster’s `add_stream_scte.json` API. :::hint{type="info"} For more information, on api calls, refer to Zixi Broadcaster API manual on the Customer Portal. ::: ## Special Operating Modes :::hint{type="info"} You should only use these modes if required by SDS. ::: ### SingleStreamMode In this mode, the ESAM Agent will create a SPE message for each ESAM enabled output regardless of what input that output is connected to. For output-based workflows, this allows for switching away from a looping file based on SCTE-35 messages seen on another input. The only outputs excluded from consideration are outputs without an ESAM ID and outputs that are connected to the input where the SCTE-35 was seen. Add to “sds” section: `“singleStreamMode”: true` ### ZoneIdentityInSPEMode Some SDS’s require ZoneIdentity as an added SPE parameter. This mode will evaluate all acquisitionPointIdentities against zoneIdentities when sending SPE. Only use this mode if required. Add to “sds” section: `“zoneIdentityInSpeMode”: true ` [title] Zixi ESAM Agent [path] Zixi Market Switching: ESAM Agent/ ## Overview The Zixi ESAM Agent is an additional software installation on the server hosting a Zixi Broadcaster that adds two key feature sets: 1. The ability to interface with & act on an externally hosted scheduling service such as **ESNI** (SCTE 224) using SCTE 35 messages or based on wall clock time 2. The ability to interface with & act on an externally hosted **POIS** (SCTE 130 part 5) SCTE manipulation or conditioning service. To do this, the agent sends a SCTE message as well as the source of that message to the external system and receive instructions back—whether to switch inputs to outputs or insert modified SCTE messaging or remove SCTE messaging altogether. You can use the agent to interact with either an ESNI or POIS service, or both. ESNI and POIS are collectively referred to as “Decisioning Services” in these documents. The Zixi ESAM Agent was designed around and adheres to the [Cablelabs I03 specification](https://www.cablelabs.com/specifications/CM-SP-CM-OSSIv4.0?v=I03). ## Use Cases - **Scheduling Control:** Zixi enables broadcasters to pre-schedule the delivery of specific feeds based on regional blackout rules, licensing agreements and live event timing. - **Dynamic Feed Switching:** ESNI Integration into the Zixi Software Platform facilitates real-time switching between feeds based on pre-set conditions or manual triggers. - **Resource Optimization:** By managing which feeds are sent to specific destinations, the Zixi Software Platform optimizes bandwidth usage and minimizes compute loads. - **Rights and Content Compliance:** The Zixi Software Platform with ESNI is central to enforcing content rights by limiting where and when feeds are accessible based on geographical or contractual restrictions. - **Enhanced Viewer Experience:** Broadcasters can use Zixi to ensure the delivery of region-specific content, branding, and messages like SCTE signals for ad markers. ## Requirements - Zixi Broadcaster 17.5 or later, running on Linux on an ARM 64-bit or X86 64-bit processor - If you are using ZEN Master, you will need to [Create a ZEN Master API Key](docId\:y5VWL7q34grAoPRjlHzuI) ## Section Contents - [ESAM Installation Guide](docId\:QOcjl5ScKXdp4FgeBKHGy) - [Agent Configuration](docId\:kmh8XYPqthZ9gVMGAik1G) - [How the Zixi ESAM Agent Works](docId\:jgm9F_cY9_ce8Ni9PEQ8Y) - [Monitoring and Troubleshooting](docId\:yO9BlSY79XSbn9tanvJrT) - [Appendix A: Example Use Cases](docId\:OkJGNsMWU4JLMOw9_LS-b) - [Appendix B: Example config.json file](docId\:o-74uavFiUqKsPw4umxrM) - [Appendix C: Example SPE and SPN XML](docId:4UThsV96vmuKyfsXpqpxi) - [Appendix D: Detailed Architectural Reference](docId\:DMMjur_Nd-AVMmVjMKjoa) - [Appendix E: Glossary of ESAM Terms](docId\:PKxdq2_F0q3XZzFsIfwLs) - [Appendix F: ESAM Agent Log Reference](docId\:XFH2a-L8VupGr90JoiP2Z) [title] Appendix C: Example SPE and SPN XML [path] Zixi Market Switching: ESAM Agent/Untitled/ ## SPE ```xml acquisitionSignalID="d02ecd86-a20f-4f35-90e3-b98265cd7c79" acquisitionTime="2024-12-14T01:21:17.296Z" /DBUAAAAAAAAAAEABQb+IXERUQA+Ah1DVUVJCXsIUH/OAAAAAAABCTEwMDEwMjY1MCEFAAIdQ1VFSQmEbfx//wAAaF7AAQkxMDAxMDI2NTAwAQD/aaic ``` ## ESNI SPN ```xml /DCSAAAAAAAAAAEABQb+auatQgB8Ah1DVUVJB+6chX//AAAAAAABC EwMDExMjQ4MjEBAAIdQ1VFSQe5igB/zgAAAAAAAQkxMDAxMTI0ODIRAQACHUNVRUkH8HSYf84 AAAAAAEJMTAwMTMwMTA4EAEAAh1DVUVJB/B0mX/OAAAAAAABCTEwMDEzMDEwOCABAJ+O1W8= ``` ## POIS SPN ```xml /DA1AAAAAAAAAAEABQb+NPDJPQAfAh1DVUVJB91lsH/OAAAAAAABCT EwMDEyOY4NAEAAF2GonA= ``` [title] ESNI Decisioning User Guide [path] Zixi Market Switching: ESAM Agent/ ## Overview ESNI (Event Scheduling and Notification Interface) is an XML-based standard used in broadcast and streaming workflows to enable real time, rights-aware, policy-driven control of content delivery allowing customers to adapt their distribution based on licensing constraints, user entitlements, and geographic restrictions. Using ESNI, Zixi’s ZEN Master can respond automatically to scheduling rules such as regional blackouts, alternate content substitution, and live event timing to map appropriate content to distributions from the Zixi platform ensuring compliant and personalized content playout across devices and regions. The Zixi ESNI decisioning service is designed around the ESNI/SCTE-224 standard. :::hint{type="info"} Notes: - The ESNI Decisioning service is a paid add-on to ZEN Master. - Currently there is no UI for the ESNI Decisioning service. It must be set up via API requests as explained in the documents that follow. A UI will be added in a future ZEN Master release. ::: ## Documents in this Section - [Setup and Using ESNI](docId\:Ig3-vBjQ1aXcAHAV-Zn7l) - [How ZEN Master Objects correspond to ESNI Schedule](docId\:PVDadxikeuguGHKmjTbvG) - [Sample Diagrams](docId:5sSJ8F45oYNWAV0kwZUcv) - [Content Switching](docId\:BqSnnipn1DMoXmnekPEfK) [title] How ZEN Master Objects correspond to ESNI Schedule [path] Zixi Market Switching: ESAM Agent/ESNI Decisioning User Guide/ ## ZEN Master Channel EXT ID These are **Advanced** options when editing a Channel in ZEN Master. ### Media - In the 224 Media element, the Channel EXT ID corresponds to the `source` parameter within the `` tag and/or `` tags. - In this context, the **Channel EXT ID** denotes the Channel that will be monitored for SCTE messages in a **matchSignal mediapoint**. - Example: ```xml ``` ### Viewingpolicy - In the 224 Viewingpolicy element, the Channel EXT ID corresponds to the `` tag value. - In this context, the **Channel EXT ID** denotes the source that will be switched to the desired audience when that **viewingpolicy** is active. - Example: ```xml esni-demo-main ``` ## ZEN Master Target EXT ID These are **Advanced** options when editing a Target in ZEN Master ### Audience - In the 224 Audience, the Target EXT ID corresponds to either (in priority order): - A **tag** (such as ``) with the `urn:scte:224:audience` namespace. - **If no namespace exists**, the `id` parameter within the `` tag. - This indicates the **Target** that will be switched when that audience is referenced. - Example: ```xml target-1 ``` :::hint{type="info"} *As Zixi delivers unicast, linear feeds, by default the ESNI Decisioning service does not make use of Zip or Homezip tags. Accordingly, overlapping audiences are out of scope. We recommend having an Audience per Target identified using the Audience ID or one of the designated Vird or DMA tags available per the schema. If tags other than Vird or DMA are required, contact your Zixi account rep.* ::: [title] Zixi Market Switching: ESAM Agent and ESNI Decisioning Service [path] / ![Zixi Market Switching](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-F8pWrNmmPwdFvoGDtCUku-20250530-140750.png) ## Overview Media providers often need to switch from one stream to another for purposes including: - Ad insertion - Providing regionalized content - Switching to alternate content in areas where the main stream is blacked out for contractual or regulatory reasons The telecommunications industry has created standards to allow content switching in a consistent way that avoids excess consumption of bandwidth by providing the correct content to each receiver. These standards are described below. ### ESAM (Event Stream Application Manifest) ESAM is a specification used in digital video advertising and content delivery. It defines how to insert advertisements and other events into video streams in a standardized way. ESAM provides: - A framework for describing when and where ads should be inserted in video content - Support for dynamic ad insertion (DAI) in live and on-demand streaming - Integration capabilities with ad servers and content delivery networks - Metadata handling for advertising events and content transitions The specification helps broadcasters and streaming services manage complex ad insertion workflows while maintaining stream quality and viewer experience. ### ESNI (Event Stream Network Interface) - SCTE-224 ESNI is part of the Event Scheduling and Notification Interface standard. SCTE-224 defines: - A framework for communicating scheduling information between different systems in the video delivery chain - Standardized messaging for ad insertion events, blackouts, and other program modifications - Real-time event notifications that can trigger actions across multiple network elements - Integration between traffic systems, ad servers, and playout equipment - Support for both linear TV and streaming workflows ESNI specifically handles the network interface aspects, enabling different systems to exchange event information in a standardized format. This allows for coordinated actions like simultaneous ad insertion across multiple distribution points or automated blackout enforcement. ### POIS (Placement Opportunity Information Service) In the context of video advertising and SCTE standards, POIS refers to: - Services that identify and communicate available advertising placement opportunities - Integration with SCTE-35 signaling to detect ad avails in content streams - Coordination between content providers and ad insertion systems - Real-time communication of when advertising slots are available - Support for both scheduled and dynamic advertising opportunities ESNI and POIS are separate services but can work together in modern video delivery ecosystems to enable sophisticated advertising workflows, event management, and automated content scheduling across broadcast and streaming platforms. ## Zixi's Market Switching Offerings Zixi provides two different services to handle content switching. ### The Zixi ESAM Agent The Zixi ESAM Agent is a paid add-on and an additional software installation on the server hosting a Zixi Broadcaster that adds two key feature sets: 1. The ability to interface with & act on an **externally hosted** ESNI (SCTE 224) scheduling service such as using SCTE 35 messages or based on wall clock time 2. The ability to interface with & act on an **externally hosted** POIS (SCTE 130 part 5) SCTE manipulation or conditioning service. For more information, see [Zixi ESAM Agent](docId\:OsyzVsQM3mNsyzO76AMBY). ### The Zixi ESNI Decisioning Service Zixi provides its own ESNI service as a paid add-on as an alternative to using an external service through the Zixi ESAM Agent. For more information, see [ESNI Decisioning User Guide](docId\:CCfonhvyBRYgOQUpZcPGX). ## Section Contents - [Zixi ESAM Agent](docId\:OsyzVsQM3mNsyzO76AMBY) - [ESNI Decisioning User Guide](docId\:CCfonhvyBRYgOQUpZcPGX) [title] ESAM Installation Guide [path] Zixi Market Switching: ESAM Agent/Untitled/ ## Installation To install the Zixi ESAM Agent, follow the steps below. :::::WorkflowBlock :::WorkflowBlockItem Login to the [Customer Portal](https://portal.zixi.com). ::: :::WorkflowBlockItem Go to the **Software** section > **BY TYPE/PRODUCT** tab. ::: :::WorkflowBlockItem Select **Zixi ESAM Agent:** ![](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-S9eiKWsedW7MkseX0eHtQ-20250521-192831.png) ::: :::WorkflowBlockItem Download the tar file for your processor (ARM or X86) and untar the files in the same `/zixi` directory where you installed Zixi Broadcaster. ::: :::WorkflowBlockItem Run the installer `./esam.service.install.sh` from within the same directory. ::: ::::WorkflowBlockItem Open `/zixi/esam-linux-x64/config.json` or `/zixi/esam-linux-arm64/config.json` and configure for desired operations (see [Agent Configuration](docId\:kmh8XYPqthZ9gVMGAik1G)). :::hint{type="warning"} Note: if you do not do this **before** starting the service (the next step), you will need to restart the service for the configuration changes to take effect. ::: :::: :::WorkflowBlockItem Once you have updated the `config.json` file, start the ESAM service using the command `esam-agent-service.service` ::: ::::: ## Updating the ESAM Agent When a new version of the Zixix ESAM Agent is released on the [Customer Portal](https://portal.zixi.com/dashboard), you can update your installation by following the steps below. :::::WorkflowBlock :::WorkflowBlockItem First, verify that you need the update by checking your installed version: `curl http://localhost:5555/version` ::: :::WorkflowBlockItem If the version on the portal is newer, download it and untar the file in the same` /zixi `directory where you installed Zixi Broadcaster. ::: ::::WorkflowBlockItem ***DO NOT*** run `./esam.service.install.sh` during update process. :::hint{type="warning"} Running the install script is ***NOT*** necessary to update the agent, and will overwrite the current `config.json` file. We strongly recommend that you keep a separate copy of the `config.json` file anyway, in case the install script is rerun by mistake. ::: :::: :::WorkflowBlockItem To restart the ESAM service, run the command `esam-agent-service.service` ::: :::WorkflowBlockItem Verify that the agent is updated by checking the version again: `curl http://localhost:5555/version` ::: ::::: [title] Monitoring and Troubleshooting [path] Zixi Market Switching: ESAM Agent/Untitled/ ## Monitoring ### Viewing Switches in ZEN Master When ZEN Master communication is configured, all switches will be reported to and reflected in ZEN master. The Target will show the proper channel and the switch will be reflected in the change log and event logs. ![ESAM Change Tracking Sample](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-ztido7fLZoE9ZbrnV3wh4-20250527-183503.png "ESAM Change Tracking Sample") ### Viewing Switches on the Broadcaster Logs for the Broadcaster can be found in the EVENT LOG tab by searching “switch” In the log files the Broadcaster produces, filtering for “switch” will also show the logs for switches requested. **Event Log Messages** | **Message** | **Description** | | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Switch source for output zen-push.oxwzpyvr.rpvyweyr to WBD-NBA-001-FO-WEST-sxxd1q5-pm requested\_pts=8288264131 timed out. switching anyway | The provided PTS was not found after the timeout, but the switch was done anyway. If seamless is configured, a seamless switch was tried , then an immediate switch | | Switch source for output zen-push.oxwzpyvr.rpvyweyr to WBD-NBA-FILE-001-FO-WEST-se21ryl-pm requested\_pts=7695381841 detected\_pts=7697004962 diff=1623121 | The provided PTS was found and a switch was done on that PTS | ### SCTE-35 Reporting When using the ESAM agent, all SCTE-35 messages seen on inputs on the Broadcaster are still forwarded to ZEN Master or any other external system. The Agent gets the URL to post the SCTE-35 messages to from the SCTE-35 Reports URL defined in the Broadcaster settings. For example: [https://zen.zixi.com/reporting/broadcasters/xrpkpnqo/scte35](https://zen.zixi.com/reporting/broadcasters/xrpkpnqo/scte35) The Agent updates the value on the broadcaster with a passthrough parameter that is the original reporting URL and passes all SCTE that it receives on to the SCTE logging platform. For example: [http://127.0.0.1:5555/signal?agentESAM=1\&passthrough=https%3A%2F%2Fzen.zixi.com%2Freporting%2Fbroadcasters%2Fxrpkpnqo%2Fscte35](http://127.0.0.1:5555/signal?agentESAM=1\&passthrough=https%3A%2F%2Fzen.zixi.com%2Freporting%2Fbroadcasters%2Fxrpkpnqo%2Fscte35) This process uses ZEN Master API key authentication with the Key in the headers: x-api-key: *api-key-from-zen-master-account* **SCTE-35 Reports Format** The SCTE-35 information is reported in an HTTP post and the data sent in the parameters: | **Parameter** | **Description** | | --------------- | -------------------------------------------------------------------- | | stream | StreamID of input | | scte\_cmd | Binary of SCTE-35 message | | Duration | Duration of break | | Eventid | ID of the message | | ProgramID | ID of the break | | PTS | PTS time of splice point | | OutOfNetwork | 1/0 if going in or out of network | | Autoreturn | 1/0 Should the break close automatically | | immideate | 1/0 if the break should be spliced immediately (it is spelled wrong) | | PTS\_Adjustment | Value the PTS should be adjusted by | | PID | The PID the SCTE-35 was captured on | | ReportTime | Timestamp when SCTE-35 message was captured | | wallClockTime | Splice time converted to timestamp based on wall clock time | | SendTime | Timestamp when SCTE-35 report was sent | To log SCTE in ZEN Master, enable logging in the Broadcaster Cluster & Source settings: 1. Broadcaster Clusters – SCTE-35 logging must be enabled if you wish to view SCTE-35 messages in ZEN Master on each source or in the general logging page 2. Individual Sources – SCTE-35 logging must be enabled on each Source if you wish to view SCTE-35 messages for each input on the Broadcaster ## Troubleshooting The ESAM Agent is very lightweight and stateless so restarts will not affect. There are also debug logs to assist in deep diving were problems to arise. When working through issues the best places to investigate are: - ESAM Agent logs – found in the directory configured by the ‘logger’ section within the config file. Full logging details: - Broadcaster logs – Event logs, system logs, or log files - ZEN Master Events – On the Target or general logs - SDS logs – The external SDS system [title] Appendix A: Example Use Cases [path] Zixi Market Switching: ESAM Agent/Untitled/ ## Signal based SCTE224 Scheduling based on source SCTE35 messages SCTE detected on any input with an External ID will trigger an SPE to the decisioning service. An SPN will be returned with all of the input to output switches that should occur based on that SCTE message detected on that source. ![ESAM Use Case: ESNI](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-WyG2wHgoiWIXHZ-Ebotbh-20250522-185703.png) ## SCTE manipulation/conditioning using external POIS service SCTE detected on an input or output will trigger an SPE to the POIS service. An SPN will be returned outlining any SCTE modifications and new SCTE payload if applicable. This is done per output and if defined on an input, will apply to all outputs connected to that input. ![](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-CU3Vc39TvWS4v51_uAfzO-20250522-185929.png) :::hint{type="info"} Note that ESNI and POIS can be used simultaneously. POIS insertion will still happen per output downstream of switches ::: [title] Appendix B: Example config.json file [path] Zixi Market Switching: ESAM Agent/Untitled/ Below is a sample config.json file, for reference only. ```json { "agent": { "port": 5555 }, "sds": [ { "mode": "esni", "baseUrl": "http://url.url.com/esniendpoint", "username": "", "password": "", "zoneIdentity": { "type": "output", "path": "user_data.zm_external_id" }, "acquisitionPointIdentity": { "type": "input", "path": "user_data.zm_external_id" }, "altContentIdentity": "user_data.zm_external_id", "singleStreamMode": false, "zoneIdentityInSpeMode": false, "retryDelay": 500, "maxRetries": 4 }, { "mode": "pois", "baseUrl": "http://url.url.com/poisendpoint", "username": "", "password": "", "zoneIdentity": { "type": "output", "path": "user_data.zm_external_id" }, "acquisitionPointIdentity": { "type": "output", "path": "user_data.zm_external_id" }, "altContentIdentity": "user_data.zm_external_id", "singleStreamMode": false, "zoneIdentityInSpeMode": false, "retryDelay": 500, "maxRetries": 4 } ], "redirect": { "abortOnTimeout": false, "seamless": true, "overwriteIfInProgress": false, "ptsDetectionTimeoutMS": 500 }, "broadcaster": { "port": 4444, "username": "admin", "password": "1234", "retryDelay": 500, "maxRetries": 2, "cacheMs": 1000 }, "logger": { "syslog": { "level": "debug", "host": "host-ip", "port": 514, "protocol": "udp4", "localhost": "desired-hostname" }, "console": { "silent": false, "level": "error" }, "file": { "level": "info", "filename": "EsamAgent-%DATE%.log", "dirname": "/zixi/zixi_broadcaster-linux64/files/logs/esam/", "datePattern": "YYYYMMDD", "maxSize": "1024m", "maxFiles": "7d" } }, "zenMaster": { "baseUrl": "https://zen.zixi.com", "apiKey": "zenmaster-api-key", "switch_target_path": "api/scte224/targets" } } ``` [title] Appendix F: ESAM Agent Log Reference [path] Zixi Market Switching: ESAM Agent/Untitled/ This guide is broken into sections where the log messages are found within the Agent. Not all logs are defined here as they’re triggered by the network or external systems. For messages in the log file that are not referenced here, consult ZEN Master engineering team. The log levels used are WARN, ERROR, INFO, DEBUG. ## General log navigation Every event will have an acquisitionSignalID generated with the signal processing event for solicited events and signal processing notification for unsolicited. This acquistionSignalID will appear on every subsequent log event until that event is complete. If you find any log line related to an action in question and ‘grep’ the log using the acquisitionSignalID, you will return the entire flow from SCTE Acquisition to source switch/POIS insertion and broadcaster response. ## Signal-handler (solicited) ### Variables - \{\{text}} = variable (listed below) - \ = info from another return in the Agent - Identifiers = acquisitionSignalID, streamId, output.id, zoneIdentity - Decision = acquisitionSignalID, zoneIdentity, acquisitionPointIdentity, altContent, altContentIdentity, utcPoint | **Level** | **Message** | **Description** | | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | | DEBUG | signalHandler - called with streamId: \ | Notification that a new SCTE-35 message came in on the provided streamID | | DEBUG | signalHandler - input is not ESAM relevant \ | The input where the SCTE-35 was captured does not have an ESAM ID | | DEBUG | signalHandler - no outputs found for streamId \ | There are no outputs connected to the input were the SCTE-35 was captured | | INFO | signalHandler - called with streamId: \ outputs: \{output.id, output.name, output.zoneIdentity} | All outputs attached to the input where the SCTE-35 was captured | | DEBUG | signalHandler - processing output (signalProcessingEvent) \{\{identifiers}} | Informative message about output that is being processed | | DEBUG | signalHandler - parsedDecision \{decision}, \{\{identifiers}} | SDS response for processed output | | ERROR | signalHandler - error requesting decision, \, \{\{identifiers}} | Error getting decision from SDS | | INFO | signalHandler - no altContent element in decision; no switch required \{\{identifiers}} | Error getting decision from SDS | | WARN | signalHandler - no matching input for altContentIdentity \ \{\{identifiers}} | The alternate identity provided in the SDS response does not exist on the Broadcaster | | ERROR | Invalid inputId | AltContentIdentity field in config set incorrectly | | DEBUG | signalHandler - skipping output on matching input \ \{\{identifiers}} | The output being processed is already connected to the alternate content input | | INFO | signalHandler - processing output (switching) \{\{identifiers}} \{
currentInputId: \,
newInputId: \,
\} | A switch command is being sent to the Broadcaster to switch the input connected to the output | | ERROR | signalHandler - Error processing event: \ \{\{identifiers}} | General error while processing the response from the SDS | ## Unsolicited-handler - \{\{text}} = variable (listed below) - \ = info from another return in the Agent - Identifiers = acquisitionSignalID, streamId, output.id, zoneIdentity - OutputIdentifiers = \{\{identifiers}}, outputId: output.id, outputName: output.name | **Level** | **Message** | **Description** | | --------- | ---------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | | INFO | unsolicitedHandler - called with \{\{identifier}} | Informative message that unsolicited message was received | | WARN | unsolicitedHandler - no switch required \{\{identifiers}} | Alternate content element of SDS message is missing or set to False | | WARN | unsolicitedHandler - no input found by altContentIdentity \{\{identifiers}} | No input was found on the Broadcaster with the ID provided in the altContentIdentity of the SDS message | | DEBUG | unsolicitedHandler - skipping output on matching input \ \{\{identifiers}} | The output and input in the SDS message are already connected | | WARN | unsolicitedHandler - no outputs found by zoneIdentity \{\{identifiers}} | The output provided in the SDS message is not available on the Broadcaster | | INFO | unsolicitedHandler - processing output (switching) \{\{outputIdentifiers}} | A switch command is being sent to the Broadcaster to switch the input connected to the output | | ERROR | unsolicitedHandler - error processing event: \{\{outputIdentifiers}}\ | General error while switching input and updating ZEN Master | ## Broadcaster-API/Client - \ = info from another return in the Agent | **Level** | **Message** | **Description** | | --------- | ---------------------------------------------------------------------------------- | --------------------------------------------------------------- | | ERROR | Timeout | Timeout interacting with the Broadcaster API | | ERROR | BroadcasterApi.get, error: \ | Error interacting with the Broadcaster API | | ERROR | Broadcaster API error2 \ | Error interacting with the Broadcaster API (JSON format) | | ERROR | BX error: \ | Error switching inputs on Broadcaster | | INFO | Broadcaster redirect response: \ | Response message from Broadcaster after input switch | | INFO | BroadcasterClient.enableScteReporting, SCTE reporting applied successfully | SCTE-35 Reporting URL is set to send messages to the ESAM Agent | | ERROR | BroadcasterClient.enableScteReporting, Error enabling SCTE reporting: \ | Problem updating the SCTE-35 Reporting URL on the Broadcaster | | ERROR | BroadcasterClient.getSettings, Error getting settings \ | Problem getting Broadcaster config file through the API | | ERROR | BroadcasterClient.getOutputs, No outputs found | No outputs on the Broadcaster | | ERROR | BroadcasterClient.getOutputs, No ESAM relevant outputs found | No outputs with ESAM IDs on the Broadcaster | | ERROR | No inputs found | No inputs on the Broadcaster | | ERROR | No ESAM supported inputs found | No inputs with ESAM IDs on the Broadcaster | ## SDS (Signal Decision Service) - \ = info from another return in the Agent | **Level** | **Message** | **Description** | | --------- | ------------------------------------------- | ----------------------------------------------- | | ERROR | Error sending acknowledgement: \ | Problem sending the response message to the SDS | | DEBUG | === signalProcessingEvent === | Header for next log | | DEBUG | \ | Unformatted message to SDS | | DEBUG | = signalProcessingNotification = | Header for next log | | DEBUG | \ | Formatted response from SDS | | ERROR | Error parsing decision: \ | Problem parsing message from SDS | | ERROR | Invalid SDS decision: \ | Problem parsing message from SDS | | DEBUG | SDSClient.acknowledgement \ | Unformatted message to SDS | | ERROR | Error sending acknowledgement: \ | Problem sending the status message to the SDS | ## Config Manager - \ = info from another return in the Agent | **Level** | **Message** | **Description** | | --------- | ------------------------------------------------------------------------------- | ----------------------------------------------------- | | ERROR | Config file ./config.json not found, see ./config-templage.json for an example. | The ESAM Agent is unable to find the config.json file | | ERROR | Error reading ./config.json \ | The ESAM Agent is unable to read the config file | | ERROR | Error parsing ./config.json \ | Validation error for XML | ## Helper functions - \{\{text}} = variable (listed below) - \ = info from another return in the Agent - PtsTime = pts time of the splice point in the SCTE-35 message - PreRoll = pre roll (if provided) in the SCTE-35 segmentation descriptors - AdjusterPtsTime = ptstime + preRoll | **Level** | **Message** | **Description** | | --------- | -------------------------------------------------------------------- | ----------------------------------------------------- | | ERROR | Invalid xml. Data type is not string | Validation error for XML | | ERROR | Failed to parse xml | Problem parsing the XML provided | | DEBUG | Parsed PTS \{ \{\{ptsTime}}, \{\{preRoll}}, \{\{adjustedPtsTime}} } | PtsTime, preRoll, and adjustedPtsTime from SCTE-35 | | ERROR | Error parsing PTS \ | Problem parsing PTS and PreRoll from SCTE-35 message | | ERROR | Invalid request: \ | Validation error for XML | ## HTTP-Client - \ = info from another return in the Agent | **Level** | **Message** | **Description** | | --------- | ---------------------------------------------------------------------- | --------------------------------------------- | | ERROR | requestHandler ERROR \
, \, \ | Problem requesting data from external system | | ERROR | Error fetching data \ | Problem requesting data from external system | | WARN | retryHandler, Attempt \ failed: \ | Problem, attempting another retry | ## Monitor - \ = info from another return in the Agent | **Level** | **Message** | **Description** | | --------- | ----------------------------------- | --------------------------------------------------------------- | | WARN | monitor, No broadcaster detected | No response from Broadcaster getSettings API call | | ERROR | monitor, SCTE messages not enabled | Broadcaster SCTE-35 Report URL not configured for ESAM Agent | | ERROR | Error in monito \ | Problem checking or configuring Broadcaster SCTE-35 Report URL | ## ZEN Master Client - \ = info from another return in the Agent | **Level** | **Message** | **Description** | | --------- | ------------------------------------------------------------------------- | --------------------------------------------------------------------- | | INFO | ZenMasterClient.updateZenMaster, Switching targets | ZEN Master will be notified of a input output switch | | INFO | ZenMasterClient.updateZenMaster, ZEN master has been updated successfully | ZEN Master successfully reassigned the Channel to the Target | | ERROR | Error updating ZEN master \ | ZEN Master was unsuccessful in reassigning the Channel to the Target | | INFO | reportScte35, SCTE35 posted to ZEN Master \ | Response message from ZEN Master after posting SCTE-35 message | | ERROR | reportScte35, Failed to post SCTE35 to ZEN Master: \ | Problem posting SCTE-35 message to ZEN Master | ## App (Main) - \ = info from another return in the Agent | **Level** | **Message** | **Description** | | --------- | ------------------------------------------------- | -------------------------------------------------------------- | | ERROR | Error processing unsolicited request \ | General error processing unsolicited message | | ERROR | Error processing signal \ | General error processing solicited message | | INFO | Server is running on localhost: \ | Startup message noting the TCP port the Agent is listening on | | ERROR | Failed to start server \ | General error starting ESAM Agent | [title] Appendix D: Detailed Architectural Reference [path] Zixi Market Switching: ESAM Agent/Untitled/ The diagram below describes the logic of what happens when you are using Zixi ESAM ESNI and/or POIS. ![ESAM Detailed Architectural Reference](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-gfyARxJHtdo-asW-0gBDC-20250522-184049.png) [title] Monitoring in ZEN Master [path] Zixi Market Switching: ESAM Agent/ESNI Decisioning User Guide/ ZEN Master includes monitoring tools for the ESNI Scheduling back-end. These tools will be available when the ESNI server module of ZEN Master is enabled and configured. ## Setting Up Access to ESNI Schedules User access to ESNI schedules is configured via Roles. :::::WorkflowBlock :::WorkflowBlockItem In the **Create** (and **Edit**) screen for **Roles**, go to the REGEX section: ![Role REGEX Section](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/o8S9GvegjWV9yVEnfYuvS-20251207-210016.png) ::: :::WorkflowBlockItem Users assigned this Role will match any SCTE224 Media, Policy, ViewingPolicy, or Audience ID’s **that match the provided regex(es).** ::: ::::WorkflowBlockItem Regex allows flexibility to allow global visibility to an entire subset of Media’s that have consistent IDs (i.e. sharing all schedules that start with “customer1”) or lock users down to a single schedule. Examplew: 1. To match all schedules starting with a certain string, use **^string -** (i.e. for “zixi”, use the regex *^zixi*) 2. To match schedules containing a string, use **.\*string.\*** (i.e. for “zixi”, use the regex *.\*zixi.\**) - note the periods! 3. To allow access to all schedules, use **.\*** :::hint{type="info"} Account Administrators will also have access to a “database” tab that will show all current SCTE224 files in ESNI database whether in active use by a Media or not. ::: :::: ::::: ## Schedule Tab The Schedule tab shows a practical representation of upcoming scheduled content switches, associated content that will be applied to various audiences, as well as timestamps of previously triggered switches. Hover actions also provide matchSignal effective windows and assert statements. ![ESNI Schedule Tab](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/CvIX-sCIUbHfJkbONw0fV-20251105-193956.png) ## Media Tab The **Media tab** shows various elements of the current media as well as as an active policy table displaying currently active policies to various audiences. Each tab will show selected relevant parameters of the ESNI elements as well as an option to see the RAW XML payload. ![ESNI Media Tab](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/VRyqeFbNSA4K2JsxIsnUS-20251105-193744.png) ### ViewingPolicy and Audience tabs The ViewingPolicy and Audience tabs for Media also provide a drop down showing all associated Channels and Targets respectively. ![Viewing Poli](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/5p0XZgSMSL7ntkKFqEpRU-20251207-212604.png) ![Audience](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/M7JfJzRYCUw8Mfc8G5saY-20251207-212741.png) :::hint{type="info"} Note that the ESNI section in ZEN Master currently is for monitoring only - there are no actions available. ::: [title] Setup and Using ESNI [path] Zixi Market Switching: ESAM Agent/ESNI Decisioning User Guide/ ## Setup ## The ESNI Server To leverage Zixi’s ESNI implementation, please request that ESNI be enabled for your account by your Zixi account team. Once done, valid ESNI/SCTE-224 element XML payloads can be added to the ESNI database via **HTTP PUT**. ### URL Endpoint The production URL is: [https://esni.zen.zixi.com/](https://esni.zen.zixi.com/)**\/** ### Authentication Per ESNI standard, use [Amazon Signature version 4 for API Requests](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_sigv.html). :::hint{type="info"} *Access Key and Secret Key can be rotated by request. Reach out to your Zixi account rep as required.* ::: ### HTTP Methods - **PUT** – Adding a new XML payload to the Database / Updating the XML payload in the database - **DELETE** – Removing an XML payload from the database - **GET** – Retrieving XML payloads from the database ### XML HTTP PUT ordering Within the XML payloads are hrefs that reference other media elements. Referenced XMLs must be added to the database prior to broadcasting the media that references these XMLs. 1. Audience  2. Viewingpolicy 3. Policy 4. Media ## Working with ESNI Elements **Media**, **Policy**, **ViewingPolicy**, and **Audience** all have **@lastUpdated** XML attributes. These **must** be updated each time a new ESNI element is posted. **If @lastUpdated is older than what is currently in the database, the XML will not update.** :::hint{type="success"} **Tip**: When using postman use this variable: `lastUpdated="{{$isoTimestamp}}"` to ensure current time stamp. ::: ## Adding an ESNI Element - **PUT**: https\://esni.zen.zixi.com/***\{customer-zenmaster-prefix}*/*\{element}****/*id/of/element - **BODY**: XML formatted Media - When creating the other ESNI elements, replace “\{element}” from the URL above with the ESNI element type – **media**, **policy**, **viewingpolicy**, **audience**. ## Modifying/Viewing an ESNI Element - **PUT/GET**: https\://esni.zen.zixi.com/***\{customer-zenmaster-prefix}/\{element}***/id/of/element - **BODY** for **PUT**: XML formatted Media with edits and updated **\** value. ## Deleting an ESNI Element - **DELETE: **https\://esni.zen.zixi.com/***\{customer-zenmaster-prefix}/\{element}***/id/of/element - **BODY**: empty ## Viewing all elements of a certain type in the database - **GET:** https\://esni.zen.zixi.com/***\{customer-zenmaster-prefix}***/?role=***\{element}*** - Replace “***\{element}***” from the URL above with a capitalized version of the ESNI element type – **Media**, **Policy**, **ViewingPolicy**, **Audience**. ## Validating ESNI element XML **PUT**: https\://esni.zen.zixi.com/***\{customer-zenmaster-prefix}***/\_\_validate **BODY: **XML formatted Media This request will return any errors in the XML preventing a successful upload ## Checking Zixi ESNI Decisioning service version **GET**: https\://esni.zen.zixi.com/***\{customer-zenmaster-prefix}***/\_\_status/about **BODY**: empty ### Configuration notes: 1. Audience tags. By default, the Zixi ESNI backend will only be aware of audience ID’s, Vird tags and DMA tags for associating ZEN Master Targets with Audience files for timing optimization purposes. Options can be added as needed. 2. UPID Formats. By default, SCTE-224 UPID asserts will match with SCTE-35 payloads presented in Hex, Base64, or Text. If your deployment requires this to be limited to a specific format, this can be arranged. 3. Schedule offset. Depending on upstream workflows, streaming latency can cause a timing disparity between UTC schedule timing and currently displayed content on the stream. An offset can be applied so that matchTime and SCTE-35 effective windows align with video stream. [title] Content Switching [path] Zixi Market Switching: ESAM Agent/ESNI Decisioning User Guide/ Zixi hosted ESNI leverages ZEN Master’s Channel Switching capabilities. All switches will be a seamless switch on an i-frame, ensuring no downstream disruptions or disconnects, as well as the option to create a continuous PTS timeline. ## Redundancy and Dual Redundancy Options The Zixi ESNI switching logic only works within a **ZEN Master Broadcaster cluster** and seeks out the nearest source to the target being switched. This means that if there are two channels within a cluster with the same External ID, the target will switch to the one on the same broadcaster first, and if none exist, search other broadcasters within the cluster. **It will not switch across clusters**. This means two things: 1. If a Channel is within a cluster but not on the same broadcaster, there will not be a seamless switch, but the show will go on. We recommend ensuring ESNI workflows are on single broadcasters, but have built this functionality for flexibility. 2. If an identical workflow is configured in two different ZEN Master broadcaster clusters using the same Channel/Target external IDs, both workflows will switch simultaneously, allowing for hot-hot redundancy from a single schedule. :::hint{type="warning"} If using a Channel External ID multiple times within a cluster*, be sure to specify the **Target Broadcaster **in the Channel configuration to ensure Targets switch to Channels on the same broadcaster.* ::: ### Notes - If a 224 element such as **Audience** is deleted, any element that references that specific element will no longer have that reference. Remember to add that element back to relevant **viewingpolicys/policys** if it’s been deleted and replaced. - **Precedence:** 1. **\ **works on a low to high scale with low priority taking precedence. 2. **\ **value matters and will prioritize higher numbers when multiple policies are simultaneously applied. If unsure, leave it out, and the schedule will implicitly auto-increment. 3. With no priority/order attributes defined, the most recent effective policy for an audience will be applied. - ZEN Master Targets must be set up to prefer **any** source in the channel being switched. If you pin a source, it will be unable to negotiate the seamless switch. - For **matchSignal**, Zixi’s default maximum value for allowed SCTE-35 pre-roll is 30s. If you expect a longer pre-roll, please let your Zixi account team know. [title] Sample Diagrams [path] Zixi Market Switching: ESAM Agent/ESNI Decisioning User Guide/ The below example is a simple demonstration of a channel associated with a 224 media file’s `` attribute that is also the channel identified in the ViewingPolicy’s `` value. Depending on the policy applied by a given SCTE35 message, one may switch to a separate designated blackout channel or to/from an alt content channel separate to the channel asserting the SCTE and triggering the switch through policy application. ![Content Switching via ESNI](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-bh94YHHjlyL3QaxbG4IDc-20250602-191144.png) ### ESNI Switching Components ![ESNI Switching Component](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/qyVUVgkf-2NCJmn5t8A4d-20250916-131717.png) ### ESNI Switching Components - Relationship to ZEN Master ![ESNI Switching Components - Relationship to ZEN Master](https://app.archbee.com/api/optimize/amUtKWPrNQCS-26DKyGuI-OIPovg74DtdwVAe51qmvC-20250910-182607.png) [title] Agent Configuration [path] Zixi Market Switching: ESAM Agent/Untitled/ After you have downloaded and untarred the Zixi ESAM Agent files, you can configure the agent by editing the `/zixi/esam-linux-x64/config.json` or `/zixi/esam-linux-arm64/config.json` file. The JSON configuration is made up of six arrays of key/value pairs, which are explained below. Also see: [Appendix B: Example config.json file](docId\:o-74uavFiUqKsPw4umxrM). ## Agent configuration ### agent array This array contains startup information: - `port` \[integer] - The TCP port the Agent is listening on. This port will be used for unsolicited messages and SCTE-35 messages coming from the Broadcaster. ### sds \[Signal Decision Service] There are two SDS services that can be used with ESAM: 1. **ESNI/SCTE-224** – Content switching 2. **POIS/SCTE-130** – SCTE-35 manipulation (See [SDS Terminology](docId\:kmh8XYPqthZ9gVMGAik1G) below for an explanation of terms used in this section.) ### sds configuration array - `mode` \[string] - “esni” or “pois” indicating desired service. Multiple services can be configured by adding an additional SDS json array \{ } within the sds section. - `baseURL` \[string] - URL to send Signal Processing Event messages to. **Note**: if using both pois and esni it is not recommended to use the same endpoint as each service sends its own signal processing event. - `username` \[string] - if the SDS requires authentication - `password` \[string] - if the SDS requires authentication - `zoneIdentity` – ID of output to be switched. Corresponds to Audience in SCTE-224. - `type` \[string] - generally “output” - `path` \[string] - Full [JSONPath](https://goessner.net/articles/JsonPath/index.html#e2) location of desired External ID key in output metadata. “user\_data.zm\_external\_id” is default. - `acquistionPointIdentity` – ID of an output or input to mark where the SCTE-35 messages were captured. Corresponds to source in SCTE-224. - `type` \[string] - options include \[“output”,”input”] - `path` \[string] - Full JSONPath location of desired External ID in input/output metadata. “user\_data.zm\_external\_id” is default. - `altContentIdentity` \[string] – ID of an input that the zoneIdentity will switch to. (destination input.) Generally, should match path of acquistionPointIdentity. Corresponds to content under *viewingpolicy* in SCTE-224. - `retryDelay` \[integer] - Wait time before retry after api timeout - `maxRetries` \[integer] - number of retries after timeout ### broadcaster array The ESAM agent gathers input and output info as well as triggers switches and inserts SCTE via the Broadcaster API. This section outlines communication preferences. - `port` \[integer] - TCP port hosting the broadcaster service - `username` \[string] - Broadcaster UI admin username - `password` \[string] - Broadcaster UI admin password - `retryDelay` \[integer] - Milliseconds the Agent should wait when interacting with the Broadcaster API. - `maxRetries` \[integer] - Number of attempts the Agent should make when interacting with the Broadcaster API. - `cachMs` \[integer] - How long the broadcaster input/output list is stored to optimize performance when conducting multiple switches at once. ### redirect array This array details switching options using the redirect\_client.json api: - `abortOnTimeout` \[boolean] - Allow redirect\_client API call to abort action if PTS detection time runs out. - `seamless` \[boolean] - Perform seamless switch if PTS detection times out. - `overwriteIfInProgress` \[boolean] - Cancel current API request in favor of new API request with same parameters. If False, multiple switches will be queued. - `ptsDetectionTimeoutMs` \[integer] - The amount of time in milliseconds the broadcaster should continue to search in real time for provided PTS. ### logger array There are three options to log—**console**, **syslog**, **file**. They can be used simultaneously. The library is the Winston library which has more config info found [here.](https://github.com/winstonjs/winston-daily-rotate-file?tab=readme-ov-file#options) - `console` – will post logs to stdout - `silent` \[boolean] - False will post logs to the stdout - `level` \[string] - Sets the log level that should be posted to the stdout. Options include: \[“debug”, “info”, “warning”, “error”] - `file` – will post logs to file - `level` \[string] - Sets the log level that should be posted to the file. Options include: \[“debug”, “info”, “warning”, “error”] - `filename` \[string] - Format of filename %DATE% will use the value assigned to datePattern - `dirname` \[string] - Directory to write logs to. It’s recommended to match the file path with that of the Zixi broadcaster logs so they can be accessed in a single place via ZEN Master tunnel without SSH access. - `datePattern` \[string] - format of datetime string. - `maxSize` \[string] - Max size each file should reach - `maxFiles` \[string] - The number for files to keep before cycling. - `syslog` - Will post logs to external syslog server. We passthrough parameters from the Winston syslog implementation: https\://www\.npmjs.com/package/winston-syslog. - `level` \[string] - log level \[“debug”, “info”, “warning”, “error”] - `host` \[string] - host ip of syslog server - `port` \[integer] - syslog communication port - `protocol` \[string] - syslog communication protocol. :::hint{type="info"} **Log Message Reference: **details of all log messages can be found in [Appendix F: ESAM Agent Log Reference](docId\:XFH2a-L8VupGr90JoiP2Z) ::: ### zenmaster array This array configures Agent to report to ZEN Master or other external system. - `baseUrl` \[string] – The URL where to post SCTE-35 messages and notifications of content switches. (If using ZEN Master, [https://zen.zixi.com](https://zen.zixi.com)) - `apiKey` \[string] - Key used for authentication to external system. Added as value to “x-api-key" in request headers. (If using ZEN Master, Configuration > API Keys in your ZEN Master account) - `switchTargetPath` \[string] - URI where the notifications can be sent in the baseUrl. (If using ZEN Master, “api/scte224/targets”) ## Input & Output configuration ### Parameters - **Acquisition Point Identity** – The ID associated with any SCTE 35 message sent to a decisioning service. Included in both SPEs and SPNs, this can correlate to a Zixi Broadcaster input or output depending on how the schedule is set up and will generally correspond to the `` attribute in an ESNI media or mediapoint. - **Zone Identity** – Part of the SPN for the switching component, this is the ID of the Zixi output or ESNI audience that will be switched. - **Alt Content Identity** – Part of the SPN for the switching component, this is the ID of the input that will be switched to a Zixi output or Zone Identity and corresponds to the `` in an ESNI schedule’s viewingPolicy. ### Basic configuration using ZEN Master **ESNI** ::::WorkflowBlock :::WorkflowBlockItem Mapping sources to schedule: - In ZEN Master, create a failover source containing desired source, and in the **Advanced** section, enter an External ID that corresponds with Source or Content IDs in the external schedule. *(failover source does not require two components. They are just used in this case as a variable element that is written to the broadcaster)* - Create a Passthrough channel for the source. - In the ESAM Agent config file, set **acquisitionPointIdentity** and **altContentIdentity** types to` input `and **paths** to `user_data.zm_external_id` ::: :::WorkflowBlockItem Mapping targets to schedule: - In ZEN Master, create a target and in the **Advanced** section, enter an External ID that corresponds to the Audience ID (or Zip/VIRD/etc) in the external schedule. - In the ESAM Agent config, set **zoneIdentity** type to `output` and **path** to `user_data.zm_external_id` ::: :::: **POIS** ::::WorkflowBlock :::WorkflowBlockItem In ZEN Master: - Create a failover source containing desired sources, and in the “Advanced” section, enter an External ID *(failover source does not require two components. In this case, it is just used as a variable element that is written to the Zixi Broadcaster)*. - Create a Passthrough channel for the source. - Create a target and in the “Advanced” section, choose an External ID and enter a POIS latency offset. This value can be zero, but it establishes that this output should receive POIS SCTE conditioning. If a value is entered, this will offset the POIS modification path to allow for api latency. *Note that the External ID is only required if doing POIS modification on the inputs.* ::: :::WorkflowBlockItem In the ESAM Agent config file, set **acquisitionPointIdentity** path to `user_data.zm_external_id` - If `acquisitionPointIdentity` is on the input, all POIS-enabled targets connected to the channel with matching External ID will receive POIS conditioning. - If `acquisitionPointIdentity` is on the output, only SCTE on targets with matching External ID will be conditioned. ::: :::: ### Broadcaster only deployments (no ZEN Master) The ESAM agent references input/output metadata to match unique identifiers. For the below instructions use the `/edit_stream.json` and `/edit_output.json` endpoints with parameter `userdata= {“zm_external_id”:”desired-id”}`. For more information on API, refer to Zixi Broadcaster API manual available on the Custom Portal. :::::WorkflowBlock ::::WorkflowBlockItem **acquisitionPointIdentity** - In the agent config.json, set **type** to either `input` or `output` depending on the external SDS set up. - For **path**, we recommend the default, `user_data.zm_external_id` :::hint{type="info"} This ID represents where the SCTE-35 messages were captured, or the output connected to the input that the SCTE-35 messages were captured on. This generally equates to the `` attribute in a 224 Schedule. For POIS this would be that input/output that will receive manipulation ::: - Using the Broadcaster API, update the user\_data.zm\_external\_id field to match the source IDs referenced by the SDS on desired inputs/outputs that should be referenced by the SDS. :::: :::WorkflowBlockItem **ZoneIdentity** - **zoneIdentity** is often on the output. In the config, set **type** to `output.` - For **path**, we recommend the default, `user_data.zm_external_id` - Using the Broadcaster API, set the `user_data.zm_external_id` field to match output/audience ID’s referenced by the SDS. ::: :::WorkflowBlockItem **altContentIdentity** - There is no ‘type’ for altContentIdentity as it will always be an input. In the config, set ‘path’ to use the same field as acquisitionPointIdentity. - Using the Broadcaster API, update the `user_data.zm_external_id` field to match the content IDs referenced by the SDS on desired inputs or outputs that should be referenced by the SDS (if there are some sources that are not included in `acquisitionPointIdentity` list) ::: ::::: ## SDS Terminology ### ESAM Terminology and how it relates to Zixi, scheduling and POIS - **Signal Processing Event (SPE)** – this is the XML message that is sent to the decisioning service when triggered by a relevant SCTE message. - **Signal Processing Notification (SPN)** – this is the XML message that is returned from a decisioning service outlining any stream switches or SCTE 35 manipulation that should occur. - **Unique components of the SPE/SPN:** - **>Acquisition Point Identity** – The ID associated with any SCTE 35 message sent to a decisioning service. Included in both SPEs and SPNs, this can correlate to a Zixi Broadcaster input or output depending on how the schedule is set up and will generally correspond to the `` attribute in an ESNI media or mediapoint. - **Zone Identity** – Part of the SPN for the switching component, this is the ID of the Zixi output or ESNI audience that will be switched. - **Alt Content Identity** – Part of the SPN for the switching component, this is the ID of the input that will be switched to a Zixi output or Zone Identity and corresponds to the `` in an ESNI schedule’s viewingPolicy. ### Authentication Authentication is handled in the config file as user and password parameters. The credentials are added to the SDS endpoint URL with [Apache basic authentication](https://developer.mozilla.org/en-US/docs/Web/HTTP/Authentication#access_using_credentials_in_the_url). ### Communication Methods There are two ways the ESAM agent communicates with an external SDS: ### Solicited – @matchSignal The ESAM Agent requests a notification message from the SDS on what to do. When the ESAM Agent is provided a SCTE-35 message from the Broadcaster. The ESAM Agent will make an HTTP Post to the SDS (at the URL provided in the config file) and await a response within the same HTTP connection. In ESNI/SCTE-224, this is called *matchSignal*. ### Unsolicited – @matchTime The SDS reaches out to the ESAM Agent without prompting from the Agent. As part of the setup with the SDS, the IP of the Broadcaster, the port hosting the ESAM Agent, and a list of input and output id’s must be provided to the SDS to allow them to send messages. In ESNI/SCTE-224, this is called *matchTime*. ### Special note: *notifying SDS of ESAM enabled inputs and outputs * To facilitate interaction with an SDS, Zixi has added an External ID metadata field. In general, the External ID that is used to identify esam enabled inputs and outputs should match the source, content, and audience IDs used in the SDS. If the SDS partner is planning to send unsolicited messages it is important to notify them of all the available input and output external id’s that can be switched (or manipulated). [space] Product Features (/product-features) [title] Implementing Transcoding [path] Untitled/ ZGuides to implementing transcoding, whether on sources or inputs or channels or adaptive groups, or creating reusable transcoding profiles or templates, are found in the ZEN Coder and Broadcaster documents. Here we provide a map of the implementation guides. ## Installation Transcoding, regardless of whether you are using a hardware trancoder or using Zixi's software encoder, goes on the server where the Broadcaster is installed. For detailed installation instructions, see [Zixi Transcoder - Installation Guide](docId\:EgXT1qsMiDGJM1FSC62c0). ## ZEN Master ### Sources [Adding a Source – Transcoded](docId\:lNauA-wKTttUl4xktBido) - You can create a transcoded Source based on an existing Source. The transcoding parameters are set by selecting one of the pre-configured transcoding profiles. ### Channels [Adding Transcoded Channels](docId\:xwF-mFNvRA5E3jQL2YMjU) - Transcoded channels transcode a single source into multiple bitrates for output to an HTTP or S3 target. ### Transcoding Profiles [Transcoding Profiles](docId\:kmselIGIGobBQMjZCI-YB) - Transcoding profiles are configuration settings for the transcoding of streams. They are used in the configuration of Transcoded Channels. ZEN Master supports H.264 (AVC) and H.265 (HEVC) transcoding formats. ## Broadcaster ### Inputs [Transcoding Broadcaster Input Streams](docId\:Mc8lVokobD_91PdoUU14E) - Zixi Broadcaster offers live transcoding, enabling users to create multiple bitrate streams from a single input stream. ### Transcoding Profiles and Templates [Creating New Transcoding Profiles](docId\:qiLLDDFkI54DNUg_XPSoZ) - In order for the Broadcaster to switch from one encoding to another, different transcoding profiles must be configured first. These transcoding profiles include the transcoding settings that can be used for the transcoding of streams. [Transcoding Broadcaster Templates](docId\:KUoh9IwRubdIf8UxDOgyh) - Instead of manually selecting input streams to be transcoded, you can define templates with rules for automatic transcoding of input streams according to the settings of a pre-defined Transcoding Template. Every time a new input stream, which matches the conditions of the template, is added, it will be automatically transcoded into the transcoded streams defined in the template's settings. [title] Zixi Transcoding [path] / Zixi Broadcaster’s live transcoding provides a single solution for the universal origination and distribution of high-quality, adaptive live broadcast content. It enables users to create multiple bitrate streams from a single input stream, converting video and audio live streams to a variety of profiles and bitrates for OTT workflows, digital MVPDs, MSOs, and other destinations. The transcoder is typically employed in the following use cases: - **Broadcast Backhaul:** Compress high-bitrate live mezzanine MPEG2 to lower-bitrate H.264 or H.265 at the same quality level to reduce bandwidth requirements for video uplink. - **Adaptive Bitrate (ABR):** Deliver live mezzanine video transcoded into multiple renditions of H.264 or H.265 and packaged into HLS or DASH formats to devices via Content Delivery Networks or similar services. - **Social Media Packaging:** Deliver live mezzanine video transcoded to lower-bitrate H.264 and packaged into RTMP or HLS for platforms such as Facebook Live, YouTube Live, and Twitch. - **Format Normalization:** Ingests legacy, obsolete, or incompatible formats and converts them into standardized, modern broadcast profiles for downstream IRDs and decoders. - **Storage Optimization:** Transcodes high-bitrate archive feeds into high-efficiency bitrates to reduce long-term file and cloud storage requirements. ## Transcoding Engine Options The transcoding feature in the Zixi Broadcaster is available using the following options: - **Software-based Transcoding:** Operates on any hardware configuration supported by Zixi Broadcaster (excluding macOS). It uses the AVCODEC library for video decode and the x264 library for video encode, offering the most hardware flexibility and support for advanced chroma subsampling (up to 4:4:4). - **NVIDIA GPU-based Transcoding:** Utilizes NVIDIA GPUs for hardware-accelerated video transcoding on-premise or via cloud providers. It leverages nvdec and nvenc libraries to offer high-density processing, decoding and encoding at resolutions up to 4K (2160p) at 60fps. - **NETINT VPU:** Utilizes NETINT VPUs for specialized hardware acceleration that provides fast transcoding with low memory overhead (Note: Framerate conversion is not supported). - **NDI Software Library:** Native processing for NDI format workflows. ## Advanced Processing Capabilities Beyond format conversion, the transcoder offers deep processing tools for professional broadcast pipelines: - **Ad Insertion:** - SCTE-35 passthrough to Zixi TS - SCTE-35 converted to CUE-OUT/CUE-IN in HLS - SCTE-35 converted to Splice Events in DASH - SCTE-35 converted to OnCuePoint in RTMP - API Injection with output to SCTE-35 (Zixi TS), CUE-OUT/CUE-IN (HLS), Splice Events (DASH), or OnCuePoint (RTMP) - **Captioning Options:** - ATSC 608/708 ES passthrough to Zixi TS, HLS, DASH, and RTMP - DVB track passthrough to Zixi TS - WebVTT generation from ATSC 708 Elementary Stream - **Audio Processing:** - Transcode up to 16 audio tracks - Passthrough of multiple audio tracks and unsupported codecs (e.g., E-AC-3) - Audio Sample Rate Conversion (44.1KHz to/from 48KHz) - PID mapping of audio tracks - **Video Processing:** - MPTS De-multiplexing and passthrough - 10-bit to 8-bit color downscaling - Smooth up/down framerate conversion with frame interpolation (NVIDIA) or frame duplication/removal (Software) - Deinterlacing and support for interlaced/progressive outputs (Software) or progressive outputs (NVIDIA) - Thumbnail extraction as an HLS playlist - Static image/logo insertion and dynamic HTML overlays - GOP synchronization, I-frame synchronization of outputs with different FPS, and I-frame injection at SCTE-35 markers ## Comparison of Transcoders Before deciding on a transcoder, you should consider its video codec and color support to see which one best suits your needs. Below is a comparison of the different options. ### NVIDIA Hardware Encoder Codec and Color Support | | ***Format*** | ***Chroma Subsampling*** | ***Color Depth*** | | ------------------ | ------------ | ------------------------ | ----------------- | | ***Video Decode*** | MPEG-2 | 4:2:0 | 8-bit | | | H.264/AVC | 4:2:0 | 8-bit | | | H.265/HEVC | 4:2:0 | 8-bit, 10-bit | | ***Video Encode*** | H.264/AVC | 4:2:0 | 8-bit | | | H.265/HEVC | 4:2:0 | 8-bit, 10-bit\* | *\*Input stream must be 10-bit* ### Software Encoder Codec and Color Support | | ***Format*** | ***Chroma Subsampling*** | ***Color Depth*** | | ------------------ | ------------ | ------------------------ | ----------------- | | ***Video Decode*** | MPEG-2 | 4:2:0 | 8-bit | | | H.264/AVC | 4:2:0, 4:2:2, 4:4:4 | 8-bit, 10-bit | | | H.265/HEVC | 4:2:0, 4:2:2, 4:4:4 | 8-bit, 10-bit | | ***Video Encode*** | MPEG-2 | 4:2:0 | 8-bit | | | H.264/AVC | 4:2:0, 4:2:2, 4:4:4 | 8-bit, 10-bit\* | *\* Input stream must be 10-bit* ### NETINT VPU Codec and Color Support :::hint{type="info"} Note: Framerate conversion is not supported. ::: | | ***Format*** | ***Chroma Subsampling*** | ***Color Depth*** | | ------------------ | ------------ | ------------------------ | ----------------- | | ***Video Decode*** | H.264/AVC | 4:2:0 | 8-bit, 10-bit | | | H.265/HEVC | 4:2:0 | 8-bit, 10-bit | | ***Video Encode*** | H.264/AVC | 4:2:0 | 8-bit, 10-bit\* | | | H.265/HEVC | 4:2:0 | 8-bit, 10-bit\* | ### NDI Software Library Codec and Color Support | | ***Format*** | ***Chroma Subsampling*** | ***Color Depth*** | | ------------------ | ------------ | ------------------------ | ----------------- | | ***Video Decode*** | NDI\* | 4:2:0, 4:2:2, 4:4:4 | 8-bit, 10-bit | | ***Video Encode*** | NDI\* | 4:2:0, 4:2:2, 4:4:4 | 8-bit, 10-bit\*\* | \**NDI v original format, not NDI | HX* ### Transcoding Templates Instead of manually selecting input streams to be transcoded, you can optionally define templates with rules for automatic transcoding of input streams according to the settings of a pre-defined Transcoding Template. **NDI Transcoding** For details about NDI transcoding, see the [Configuring NDI Streams](docId\:bXVItyeMQr6_XJH6J847Y) section. **WebRTC Transcoding** For details about WebRTC transcoding, see the [Configuring WebRTC Streams](docId\:p6-Q3-0XOTE6FecysHbxR) section. [title] Dual PULL Transmission from Single Source (Warm Redundancy) [path] Zixi Redundancy/Zixi Pull Transmission Redundancy/ ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/N6QDBPoulo3vxjdUU3rPX-20260216-105442.png) Zixi can be deployed to pull a stream to redundant targets. This topology shows a stream that is pulled from a single source node to a corresponding pair of redundant targets in a warm redundancy configuration. The stream is not pulled in parallel, only when the Main Zixi Receiver fails, the Backup Zixi Receiver will be able to pull the stream from the Zixi Broadcaster. A single Input is created at the source Zixi Broadcaster, which includes a **Max Outputs** limitation of 1 output. The same Pull input is created in both the Main ZEC and Backup ZEC. In runtime, the ZEC will connect to the Zixi Broadcaster and the output is created automatically "on the fly". If the Main Zixi Receiver becomes unavailable, the Zixi Broadcaster will grant the Backup ZEC with the permission to pull the stream. However, when the main ZEC becomes available again, Zixi Broadcaster will not grant a permission to pull the stream again (due to the max outputs limitation) until the Backup Zixi Receiver stops pulling the stream. ## Source Configuration **To configure the source node (e.g. Zixi Broadcaster):** 1. On the **Inputs** page of the primary Zixi Broadcaster, click **New Input** on the upper- right end corner of the screen. 2. In the **Stream ID** field, type a new name for the input stream. 3. Select the **a relevant connection type** option. 4. In the **Max Outputs** field, type "1". 5. Specify the stream parameters according to the relevant connection type selected. 6. Click **OK **to create the primary input. ## Target Configuration A Pull input should be configured in the primary and backup target nodes. **To configure the primary target node (e.g. ZEC):** 1. Click the **Inputs **tab at the top of the ZEC administrative screen. 2. Click **New Input **on the upper right hand side of the screen. 3. In the **Input Name** field, type a new name for the input. 4. Select the **Pull **option. 5. In the **Remote Host** field, enter the host name or IP of the Primary Broadcaster source. 6. In the **Remote Port** field, enter the connection port of the source host (primary Zixi Broadcaster). Default: 2077. 7. In the **Remote Stream** **ID** field, enter the stream ID used in the Primary Broadcaster source output. 8. Configure additional parameters as required. 9. Click **OK**. **To configure the secondary target node (e.g. ZEC):** - Repeat the same configuration steps as the ones in the primary target node. Make sure you use the same input name used in the primary target node. ## Cost Considerations This topology duplicates the source Zixi hardware and software components. It does not require doubling the uplink bandwidth as the backup connection stream is only active in the event that the primary fails. ## Latency Considerations For detailed recovery time details, please contact your Zixi representative. [title] Single PULL Transmission from Redundant Sources (Hot Redundancy) [path] Zixi Redundancy/Zixi Pull Transmission Redundancy/ ::Image[]{src="https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/1qdQt40xqUrmUefKkoTx3-20260128-174509.png" size="72" width="502" height="127" position="center" showCaption="false"} Zixi can be configured to PULL a stream from multiple sources to a single target. The topology includes a target node pulling identical input stream simultaneously from two live sources in a hot redundancy configuration. Two differently named inputs are created at the target pulling identical streams from two different sources nodes. The output in the target node should be configured to include two sources. A "Primary Source" and, in addition, either a second "Primary Source" or "Fallback Source". The consideration between the two options are: - **Second Primary Source **- one primary output is connected to the input that is pulling the stream from the Primary Broadcaster source. An additional source is defined as a primary output, which is connected to the input that is pulling the stream from the Secondary Broadcaster source. If the first output becomes unavailable ZEC will use the second primary output. However, when the first output becomes available again ***ZEC will not switch back to the first output*** ***until the second output becomes unavailable***. This means that if you want to switch back to the first primary source you will have to do it manually. - **Fallback Source **- one primary output is connected to the input that is pulling the stream from the Primary Broadcaster source. An additional source is defined as a fallback output, which is connected to the input that is pulling the stream from the Secondary Broadcaster source. If the first output becomes unavailable ZEC will use the second Fallback output. ***When the first output becomes available again ZEC will automatically switch back to the first output***. :::hint{type="info"} **Note** Multiple primary and fallback sources can be configured. In this case the IRD will pull the streams, while prioritizing the primary outputs first in a "top down" order. ::: ## Source Configuration Input and output streams are defined in the Primary and Secondary Broadcasters. The names of the inputs/outputs do not have to be the same. However, if the latency of the inputs is identical and the sources are synced, the streams will be frame synced at the target. ## Target Configuration ### Inputs Configuration Two inputs need to be configured on the target ZEC, one pulling the stream from the Primary Broadcaster source and the other from the Secondary Broadcaster source. **To configure the primary input on target node (e.g. ZEC):** 1. Click the **Inputs **tab at the top of the ZEC administrative screen. 2. Click **New Input **on the upper right hand side of the screen. 3. In the **Input Name** field, type a new name for the input. 4. Select the **Pull **option. 5. In the **Remote Host** field, enter the host name or IP of the Primary Broadcaster source. 6. In the **Remote Port** field, enter the connection port of the source host (primary Zixi Broadcaster). Default: 2077. 7. In the **Remote Stream ID** field, enter the stream ID used in the Primary Broadcaster source output. 8. Configure additional parameters as required. 9. Click **OK**. **To configure the secondary input on target node (e.g. ZEC):** 1. Click the **Inputs **tab at the top of the ZEC administrative screen. 2. Select the newly created primary input. 3. In the right hand drop down, select **Duplicate**. A new input is created with identical parameters 4. In the **Input Name** field, type a new name for the secondary input. The name should be different than the one used for the primary input. 5. Select the **Pull **option. 6. In the **Remote Host** field, enter the host name or IP of the secondary source (secondary Zixi Broadcaster). 7. In the **Remote Port** field, enter the connection port of the secondary source host (secondary Zixi Broadcaster). Default: 2077. 8. In the **Stream** field, enter the stream ID used in Secondary Broadcaster source output. 9. Configure additional parameters as required. 10. Click **OK**. ### Output Configuration The output in the target node can be configured to include an additional source that can be either a "Primary Source" or a "Fallback Source". **To configure the output to include an additional "Primary Source" or "Fallback Source" on the target node (e.g. ZEC):** 1. Click the **Outputs **tab at the top of the ZEC administrative screen. 2. Click **New Output **on the upper right hand side of the screen. 3. In the **Name** field, type a new name for the output. 4. Select the output type (UDP/File/ASI). 5. Under the **Primary Source** section, from the pull down menu select the input that is pulling the stream from the Primary Broadcaster source. 6. In the **Host** field, enter the host name or IP of the destination IRD. 7. In the **Port** field, enter the connection port on the IRD. 8. Configure additional parameters as required. 9. Click **OK**. The new output is created and appears in the Outputs list on the Outputs Screen. 10. On the **Outputs **screen, select the newly created output and click the drop-down button in the far-right column labeled Actions and select **Add Source**. The **Add output source** dialog is displayed. 11. Do one of the following: Select the **Primary Source** checkbox - to configure the redundant source as a primary source. Select the **Fallback Source** checkbox - to configure the redundant source as a fallback source. 12. From the pull down menu select the input that is pulling the stream from the Secondary Broadcaster source. 13. Click **Add**. The new primary source is created and will appear in the list of** Primary Sources **or **Fallback Sources** at the bottom of the screen. ## Cost Considerations This topology duplicates the target Zixi hardware and software components. The configuration also requires using double the up-link bandwidth. Allocation of twice the expected maximum bit-rate with head room is advised. ## Latency Considerations For detailed recovery time details, please contact your Zixi representative. [title] Dual NIC PUSH Redundancy (Hot Redundancy) [path] Zixi Redundancy/Dual NIC Redundancy/ ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/jlg8LA-OOIEnrpe63lfu9_image.png" size="74" width="1083" height="143" position="center" showCaption="false"} This topology includes two simultaneous streams delivered in parallel from a single source using two NICs to a single target in a hot redundancy configuration. If the latency of the outputs is identical, the streams will be frame synced, provided that the video is synced on entry. ## Source Configuration The following procedure describes how to configure a Zixi Feeder to push a redundant stream to a target host in a hot redundancy configuration. In order to configure a hot redundancy you will need to create two outputs in Zixi Feeder, each output will use a different NIC. Each NIC has a separate IP address. The procedure does not cover instructions on how to configure the Input into the Zixi Feeder. **To configure the first output in the source node (e.g. Zixi Feeder):** 1. On the **Outputs** page of Zixi Feeder, click the **New Output** button, located in the upper-right end corner of the screen. 2. In the **Name** field, type a new name for the output. 3. In the **Type** field select **Push to Broadcaster**. 4. In the** Input Name** field select the relevant the input stream. 5. In the **Program** field, if you have created a filter for the stream, select the relevant program. 6. In the **Stream ID** field, enter a stream ID (alphanumeric). The same Stream ID will be also configured in the target node (Push Input). 7. Optional - in the **Password** field, specify a string to be used at the destination to authenticate that the pushing Broadcaster is allowed to push this stream. 8. In the **Max Bitrate** field, specify the maximum bitrate of the stream. Default: 8000. This is used for internal memory allocation and will not affect the transmitted bitrate. Recommended: double the bitrate of the stream. 9. In the **Max Latency** field, specify the buffer size that Zixi Broadcaster will keep for error correction. For example, 6000 milliseconds would ensure that the stream is protected for six seconds of errors in the network. Default: 6000. 10. In the **Host** field, enter the host name or IP of the primary target. 11. In the **Port** field, specify the destination port to listen on for the Push stream (default: 2088). 12. In the **IP** field, select from the drop-down menu, the IP address of the NIC (Network Interface Card) in the Source through which the stream will be pushed. 13. Click **OK**. The output is added to the Outputs list. **To configure the second output in the source node (e.g. Zixi Feeder):** - Repeat the steps above to configure the second output, however In the **IP** field, select from the drop-down menu, the IP address of the secondary NIC in the Source through which the stream will be pushed. - The stream in the second NIC should have the same Stream ID as the first output. ## Target Configuration The following procedures describe how to configure the target Zixi Broadcaster in a hot redundancy configuration. The target should include two inputs that use the same Stream IDs, as configured in the first and second outputs in the source. **To configure the first target input (e.g. Zixi Broadcaster):** 1. Click the **Inputs **tab at the top of the primary Zixi Broadcaster administrative screen 2. Click **New Input **on the upper right hand side of the screen. 3. Select the **Push **option. 4. Create an input at the primary target, ensuring the “Stream ID” matches that of the first source output. 5. Configure additional parameters as required. 6. Click **OK**. **To configure the second target input (e.g. Zixi Broadcaster):** 1. Click the **Inputs **tab at the top of the secondary Zixi Broadcaster administrative screen 2. Click **New Input **on the upper right hand side of the screen. 3. Select the **Push **option. 4. Create an input at the secondary target, ensuring the “Stream ID” matches that of the first and second source output. 5. Configure additional parameters as required. 6. Click **OK**. ## Cost Considerations The configuration also requires using double the up-link bandwidth. Allocation of twice the expected maximum bit-rate with head room is advised. ## Latency Considerations For detailed recovery time details, please contact your Zixi representative. [title] Retry Timing [path] Zixi Redundancy/ ## PUSH Transmission Retry Timing When planning a high-availability Zixi deployment it is important to consider timing issues. The various types of redundancy configurations offer different retry timings, which are critical to calculating the overall video dropout at the target. Based on the latency settings that have been configured, Zixi Broadcaster acknowledges disconnection after a connection loss that exceeds the latency period and then retries to establish a connection. The cause of the connection loss also determines the time it takes for ZEC to acknowledge a drop. This can take up to 25 seconds in the worst case scenario. For more detailed retry timing data, please contact your Zixi representative. [title] Single PULL Transmission from Redundant Sources (Warm Redundancy) [path] Zixi Redundancy/Zixi Pull Transmission Redundancy/ ::Image[]{src="https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/rhse-jhaETy5NLhoMVHbM-20260128-165741.png" size="72" width="502" height="127" position="center" showCaption="false"} A Zixi PULL input can be configured with multiple, ordered, failover sources. The topology includes a target node pulling from a primary source. In the event that the primary source becomes unavailable, the target node will automatically switch to the secondary source. The target node will attempt to pull the primary sources again only in the event that the secondary source becomes unavailable. The configuration is performed on the target ZEC. There you will configure a Pull input from the primary Broadcaster, which includes an backup host (secondary broadcaster). The stream has to be defined in the primary and secondary Broadcasters as inputs with the same stream ID. In runtime, the ZEC will connect to the primary Zixi Broadcaster and the output will be created automatically "on the fly". If the primary source becomes unavailable the target will attempt to pull the same stream with the same stream ID from the secondary source (which has been defined as the Backup host). ## Source Configuration Configuring in advance the Pull output in the primary and secondary Broadcasters is not mandatory. If you configure outputs in the primary and secondary source Broadcasters, make sure both use the same stream ID. ## Target Configuration **To configure the target node (e.g. ZEC):** 1. Click the **Inputs **tab at the top of the ZEC administrative screen 2. Click **New Input **on the upper right hand side of the screen. 3. In the **Input Name** field, type a new name for the input. 4. Select the **Pull **option. 5. In the **Remote host** field, enter the host name or IP of the primary source (e.g., Primary Broadcaster) 6. Click the **"+"** button to add an alternative Remote host (e.g., Secondary Broadcaster). 7. In the second field enter the host name or IP of the Secondary Source Broadcaster. 8. In the **Port** field, enter the connection port of the host (ZEC). Default: 2077. 9. In the **Stream** field, enter the stream ID used in the primary and secondary source inputs. The same **Stream ID** should be used in the Inputs configured on the Primary and Secondary sources (Zixi Broadcasters). The output is created "on the fly" on the Zixi Broadcaster, so there is no need to configure it. 10. Configure additional parameters as required. 11. Click **OK**. ## Cost Considerations This topology duplicates the source Zixi hardware and software components. It does not require doubling the uplink bandwidth as the backup connection stream is only active in the event that the primary fails. ## Latency Considerations For detailed recovery time details, please contact your Zixi representative. [title] Single PUSH Transmission to Redundant Targets (Warm Redundancy) [path] Zixi Redundancy/Zixi Push Transmission Redundancy/ ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/s_4zUBtcbMv3F2jkZY-KV_zec-image.png) A Zixi PUSH output can be configured with multiple, ordered, fail-over targets. The topology includes a source node (in this case a ZEC) pushing a stream to a primary target (in this example the Primary Broadcaster). In the event that the primary target is not available, due to connection loss or hardware/software failure, the source node automatically switches to the secondary target. Additional targets can be configured with the same fail-over mechanism. The source node will attempt to connect to the primary again only in the event that the secondary connection is lost. ## Source Configuration The following procedure describes how to configure the ZEC to push a single stream to a primary host and an option to push the same stream to alternative hosts in the event that the primary host is unavailable. The procedure does not cover instructions on how to configure the Input into the ZEC. **To configure the source node (e.g. ZEC):** 1. On the **Outputs** page of ZEC, click the **New Output** button, located in the upper- right end corner of the screen. 2. In the **Name** field, type a new name for the output. 3. Select the **Push **radio button. 4. In the **Input Stream** field, select the relevant input stream. 5. In the **Output Name **field, enter a stream ID (alphanumeric) . The same Stream ID will be also configured in the target nodes (Push Inputs). 6. Optional - in the **Password** field, specify a string to be used at the destination to authenticate that the pushing Broadcaster is allowed to push this stream. 7. In the **Max Latency** field, specify the buffer size that Zixi Broadcaster will keep for error correction. For example, 6000 milliseconds would ensure that the stream is protected for six seconds of errors in the network. Default: 6000. 8. In the **Host** field, enter the host name or IP of the primary target. 9. In the **Port** field, specify the destination port to listen on for the Push stream (default: 2088). 10. In the **Local IP** field, select from the drop-down menu, the IP address of the NIC (Network Interface Card) in the Source through which the stream will be pushed. 11. Click the **"+"** button to add another (secondary) target. Another line is added with the properties of the secondary destination. 12. Fill out the secondary destination parameters. 13. To add additional destination(s), click the "+" and fill out the destination parameters. 14. Click **OK**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/8IOUNmpoLAq59ghGGGsDi_image.png) ## Target Configuration The following procedures describe how to configure the two or more target Zixi Broadcasters in a warm redundancy configuration. These targets must use the same Stream ID that was used to configure the Source in the ZEC. **To configure the primary target node (e.g. Zixi Broadcaster):** 1. Click the **Inputs **tab at the top of the primary Zixi Broadcaster administrative screen 2. Click **New Input **on the upper right hand side of the screen. 3. In the **Stream ID** field, enter the same “Stream ID” as the source output. 4. Select the **Push **radio button option. 5. In the **Password** field, if you have configured a password in the source (ZEC output), enter the same password. 6. Configure additional parameters as required. 7. Click **OK**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/WeXTIho7XHOwbKJOezizu_image.png) **To configure the secondary target node(s) (e.g. Zixi Broadcaster):** 1. Click the **Inputs **tab at the top of the secondary Zixi Broadcaster administrative screen 2. Click **New Input **on the upper right hand side of the screen. 3. In the **Stream ID** field, enter the same “Stream ID” as the source output. This is the same Stream ID that was also entered in the primary target. 4. Select the **Push **option. 5. Configure additional parameters as required. 6. Click **OK**. 7. Repeat the steps above to configure additional target nodes as necessary. Each target node needs to be configures in the Zixi Feeder (source) output. ## Cost Considerations This topology duplicates the target side Zixi node software and hardware components. However, it does not require doubling the up-link bandwidth, as the backup connection stream will be only active in the event that the primary stream fails. ## Latency Considerations For detailed recovery time details, please contact your Zixi representative. [title] Zixi Push Transmission Redundancy [path] Zixi Redundancy/ Zixi's push redundancy configurations includes an alternative host, which provides a secondary redundant target with automatic failover when the primary becomes unreachable. Once the failover has occurred, the system remains in the secondary target delivery state until a further interruption occurs, such as further connection loss or a stream being restarted by the user. ## PUSH Transmission Retry Timing When planning a high-availability Zixi deployment it is important to consider timing issues. The various types of redundancy configurations offer different retry timings, which are critical to calculating the overall video dropout at the target. Based on the latency settings that have been configured, Zixi Broadcaster acknowledges disconnection after a connection loss that exceeds the latency period and then retries to establish a connection. The cause of the connection loss also determines the time it takes for ZEC to acknowledge a drop. This can take up to 25 seconds in the worst case scenario. Zixi push transmission redundancy can be deployed through the following configuration options: - [Single PUSH Transmission to Redundant Targets (Warm Redundancy)](docId\:S_hPsGv-uGuKcCz64v7nr) - [Single PUSH Transmission to Redundant Targets (Hot Redundancy)](docId\:VcSHEgiEQNesobVL3T6co) - [Dual PUSH Transmission to Single Target (Warm Redundancy)](docId\:PG2Ao-0wHYcOXA3AN5fOJ) - [Dual PUSH Transmission to Single Target with High Priority Source (Warm Redundancy)](docId:2s71JLHHfdBPIkuTNyoaD) - [Dual PUSH Transmission to Redundant Targets (Hot Redundancy)](docId\:gyqKK5sYCIw-UM8kbLaeO) - [Dual PUSH Transmission to Redundant Targets (Full Cross Over)](docId\:hB6EPl2CdZ2S8jWiQUyJ7) [title] Dual NIC PULL Redundancy (Warm Redundancy) [path] Zixi Redundancy/Dual NIC Redundancy/ ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/2b71FoxR4mUOnwjv5-mGk_image.png" size="74" width="491" height="92" position="center" showCaption="false"} A Zixi PULL input should be configured, which pulls the stream from a single source with two redundant NICs. In the event that the primary NIC becomes unavailable, the target node will automatically switch to the secondary NIC. The target node will attempt to pull from the primary NIC again only in the event that the secondary NIC becomes unavailable. The input in the source is configured as usual and can use any available connection types (Push, Pull, UDP, etc.). On the target Zixi Receiver you will configure one Pull input. This input is connected to the Broadcaster and includes an Alternative Host, which is the IP of the secondary NIC. In run-time, the Zixi Receiver will connect to the primary NIC in the Zixi Broadcaster and the output will be created automatically "on the fly". If the primary source becomes unavailable the target will attempt to pull the same stream with the same stream ID from the secondary NIC (which has been defined as the Alternative Host). ## Source Configuration Configure an input, as described below. Configuring in advance the Pull output in the Broadcaster is not mandatory. **To configure the source node (e.g. Primary Zixi Broadcaster):** 1. On the **Inputs** page of the primary Zixi Broadcaster, click **New Input** on the upper-right corner of the screen. 2. In the **Stream ID** field, type a new name for the input stream. 3. Select the **a relevant connection type** option. 4. Specify the stream parameters according to the relevant connection type selected. 5. Click **OK **to create the primary input. ## Target Configuration **To configure the target node (e.g. Zixi Receiver):** 1. Click the **Inputs **tab at the top of the Zixi Receiver administrative screen 2. Click **New Input **on the upper right hand side of the screen. 3. In the **Input Name** field, type a new name for the input. 4. Select the **Pull **option. 5. In the **Host** field, enter the IP of the Primary NIC. 6. Click the **"+"** button to add an Alternative Host. 7. In the** Alt. Host** field, enter the IP of the Secondary NIC. 8. In the **Port** field, enter the connection port of the host (Zixi Receiver). Default: 2077. 9. In the **Stream** field, enter the stream ID used as configured in the source. The output is created "on the fly" on the Zixi Broadcaster, so there is no need to configure it. 10. Configure additional parameters as required. 11. Click **OK**. ## Cost Considerations This topology duplicates the network link. Allocation of the expected maximum bitrate with head room is advised on each network path. ## Latency Considerations For detailed recovery time details, please contact your Zixi representative. [title] Zixi Redundancy [path] / Zixi software and hardware can be deployed and configured for fault tolerant live streaming in a range of topology options across a wide range of use cases and workflows, including point-to-point streaming, transcoding, recording, and more. These topology options can be deployed in a clustered environment that supports reliability and scalability. In this Redundancy Guide we will cover the main redundancy options, while explaining the associated cost and performance/latency considerations, including instructions on how to configure Zixi's software components to deploy such architectures. - [Zixi Redundancy: Overview](docId\:xmiT0Gwd-CyObMGiwoU1o) - [Hitless Failover Configuration](docId\:dSnjjAPn3eZ-IfW-H4DqD) - [Retry Timing](docId\:cc522esXFN60uOHMkVOkO) - [Zixi Push Transmission Redundancy](docId\:daJVzmbssT42BZVZRdkLB) - [Zixi Pull Transmission Redundancy](docId\:SZx1wQR1rw2CQuzp3JXo-) - [Dual NIC Redundancy](docId\:Es8-dDF3ZMPvz6-tE23Ss) - [title] Dual NIC PUSH Redundancy (Warm Redundancy) [path] Zixi Redundancy/Dual NIC Redundancy/ ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/EePJ9tbzYKkJz9--H8YXM_image.png" size="74" width="887" height="134" position="center" showCaption="false"} A single source can be configured to PUSH two redundant stream to a single target using two NICs. Provided that the streams from both NICs include the same Stream ID, contention for the input is decided on a first-come first-served basis. If the primary NIC connection is lost, the target Input will automatically accept a new stream (coming from the secondary NIC). As a result, this topology provides source-side NIC redundancy with automated fail-over to a second identical stream. ## Source Configuration The following procedure describes how to configure a Zixi Feeder to push a stream through two NICs to a target hosts in a warm redundancy configuration. The procedure does not cover instructions on how to configure the Input into the Zixi Feeder. **To configure the primary source node (e.g. Zixi Feeder):** 1. On the **Outputs** page of Zixi Feeder, click the **New Output** button, located in the upper- right end corner of the screen. 2. In the **Name** field, type a new name for the output. 3. In the **Type** field, select **Push to Broadcaster**. 4. In the **Input Name** field, select the relevant input stream. 5. In the **Program** field, if you have created a filter for the stream, select the relevant program. 6. In the **Stream ID** field, enter a stream ID (alphanumeric). The same Stream ID will be also configured in the target node (Push Input). 7. Optional - in the **Password** field, specify a string to be used at the destination to authenticate that the pushing Broadcaster is allowed to push this stream. 8. In the **Max Bitrate** field, specify the maximum bitrate of the stream. Default: 8000. This is used for internal memory allocation and will not affect the transmitted bitrate. Recommended: double the bitrate of the stream. 9. In the **Max Latency** field, specify the buffer size that Zixi Broadcaster will keep for error correction. For example, 6000 milliseconds would ensure that the stream is protected for six seconds of errors in the network. Default: 6000. 10. Under Links, in the **Host** field, enter the host name or IP of the primary target. 11. In the **Port** field, specify the destination port to listen on for the Push stream (default: 2088). 12. In the **IP** field, select from the drop-down menu, the IP address of the **Primary NIC** (Network Interface Card) in the Source through which the stream will be pushed. 13. Click the** '+'** button to create a secondary link. 14. In the **Host** field, enter the host name or IP of the primary target. 15. In the **Port** field, specify the destination port to listen on for the Push stream (default: 2088). 16. In the **IP** field, select from the drop-down menu, the IP address of the **Secondary NIC** (Network Interface Card) in the Source through which the stream will be pushed. 17. Click **OK**. The output is added to the Outputs list and includes a primary and a secondary link. ## Target Configuration The following procedures describe how to configure the target Zixi Broadcaster in a warm redundancy configuration. The target is configured with a single input. If this input is unavailable the secondary input will be received. The input must use the same Stream ID that was used to configure the primary and secondary source NICs. **To configure the target node (e.g. Zixi Broadcaster):** 1. Click the **Inputs **tab at the top of the secondary Zixi Broadcaster administrative screen 2. Click **New Input **on the upper right hand side of the screen. 3. In the **Stream ID** field, enter the same “Stream ID” as the source outputs. 4. Select the **Push **option. 5. Configure additional parameters as required. 6. Click **OK**. ## Cost Considerations This topology duplicates the source side Zixi node software and hardware components. It does not require doubling the up-link bandwidth, as the backup connection stream is only active in the event that the primary stream fails. ## Latency Considerations For detailed recovery time details, please contact your Zixi representative. [title] Dual NIC PULL Redundancy (Hot Redundancy) [path] Zixi Redundancy/Dual NIC Redundancy/ ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/gvUPwyG_gSzmjj1bZVYm0_image.png" size="74" width="1120" height="167" position="center" showCaption="false"} Zixi can be configured to PULL a stream from a single source with multiple NICs to a single target. Each NIC has a different IP address. The topology includes a target node pulling identical input streams simultaneously from two live NIC sources in a hot redundancy configuration. Two differently named inputs are created at the target pulling identical streams from two different sources nodes. The output in the target node should be configured to include two sources. A primary source and, in addition, either a second "Primary Source" or "Fallback Source". The consideration between the two options are: - **Second Primary Source **- one primary output is connected to the input that is pulling the stream from the Primary Broadcaster source. An additional source is defined as a primary output, which is connected to the input that is pulling the stream from the Secondary Broadcaster source. If the first output becomes unavailable Zixi Receiver will use the second primary output. However, ***when the first output becomes available again Zixi Receiver will not switch back to the first output*** until the second output becomes unavailable. This means that if you want to switch back to the first primary source you will have to do it manually. - **Fallback Source **- one primary output is connected to the input that is pulling the stream from the Primary Broadcaster source. An additional source is defined as a fallback output, which is connected to the input that is pulling the stream from the Secondary Broadcaster source. If the first output becomes unavailable Zixi Receiver will use the second Fallback output. ***When the first output becomes available again Zixi Receiver will automatically switch back to the first output***. :::hint{type="info"} **Note** Multiple primary and fallback sources can be configured. In this case the IRD will pull the streams, while prioritizing the primary outputs first in a "top down" order. ::: ## Source Configuration The outputs can be automatically created during run time as they are pulled by the Zixi Receiver. Two outputs can be optionally configured in the Zixi Broadcaster, each output will be related to another NIC. The names of the inputs/outputs do not have to be the same. However, if the latency of the inputs is identical and the sources are synced, the streams will be frame synced at the target. ## Target Configuration ### Inputs Configuration Two inputs need to be configured on the target Zixi Receiver, one pulling the stream from the Primary Broadcaster NIC source and the other from the Secondary Broadcaster NIC source. **To configure the primary input on target node (e.g. Zixi Receiver):** 1. Click the **Inputs **tab at the top of the Zixi Receiver administrative screen. 2. Click **New Input **on the upper right hand side of the screen. 3. In the **Input Name** field, type a new name for the input. 4. Select the **Pull **option. 5. In the **Host** field, enter the IP address of the Primary NIC source. 6. In the **Port** field, enter the connection port of the source host (primary Zixi Broadcaster NIC). Default: 2077. 7. In the **Stream** field, enter the stream ID used in the Primary Broadcaster NIC source output. 8. Configure additional parameters as required. 9. Click **OK**. **To configure the secondary input on target node (e.g. Zixi Receiver):** 1. Click the **Inputs **tab at the top of the Zixi Receiver administrative screen. 2. Select the newly created primary input. 3. In the right hand drop down, select **Duplicate**. A new input is created with identical parameters 4. In the **Input Name** field, type a new name for the secondary input. The name should be different than the one used for the primary input. 5. Select the **Pull **option. 6. In the **Host** field, enter the IP address of the secondary source NIC. 7. In the **Port** field, enter the connection port of the secondary source host (secondary Zixi Broadcaster). Default: 2077. 8. In the **Stream** field, enter the stream ID used in Secondary Broadcaster source output. 9. Configure additional parameters as required. 10. Click **OK**. ### Output Configuration The output in the target node can be configured to include an additional source that can be either a "Primary Source" or a "Fallback Source". **To configure the output to include an additional "Primary Source" or "Fallback Source" on the target node (e.g. Zixi Receiver):** 1. Click the **Outputs **tab at the top of the Zixi Receiver administrative screen. 2. Click **New Output **on the upper right hand side of the screen. 3. In the **Name** field, type a new name for the output. 4. Select the output type (UDP/File/ASI). 5. Under the **Primary Source** section, from the pull down menu select the input that is pulling the stream from the Primary Broadcaster NIC source. 6. In the **Host** field, enter the host name or IP of the destination IRD. 7. In the **Port** field, enter the connection port on the IRD. 8. Configure additional parameters as required. 9. Click **OK**. The new output is created and appears in the Outputs list on the Outputs Screen. 10. 11. Click **Add Source**. The **Add output source** dialog is displayed 12. Do one of the following: Select the **Primary Source** checkbox - to configure the redundant source as a primary source. Select the **Fallback Source** checkbox - to configure the redundant source as a fallback source. 13. From the pull down menu select the input that is pulling the stream from the Secondary Broadcaster source. 14. Click **Add**. The new primary source is created and will appear in the list of** Primary Sources **or **Fallback Sources** at the bottom of the screen. ## Cost Considerations The configuration requires using double the up-link bandwidth. Allocation of twice the expected maximum bit-rate with head room is advised. [title] Improving Stream Resiliency: Error Correction and Concealment [path] / In transmitting media broadcasts, some packet loss is nearly inevitable. Depending on the network quality and congestion, the amount can vary considerably. Zixi first tries to replace the missing data, first through **Forward Error Correction** () and second, through **Automatic Repeat reQuest (**&#xNAN;**).** In extreme cases where lost data cannot be recovered, to prevent packet loss from corrupting the data stream to the point that the downstream decoder will throw errors or crash, Zixi provides **Error Concealment**, which addresses several common issues, such as timeline jumps, CC errors, VBR source streaming to decoders that require a constant bitrate, etc. Using Error Concealment is recommended if you anticipate significant bandwidth fluctuations in some or all parts of the network, and there are no downsides to using it aside from adding about one second for analyzing the stream and making necessary fixes. ## Error Concealment in ZEN Master Error Concealment can be applied to any source in ZEN Master when you create or edit it, except for the following: - Zixi Push - Monitor Only - Transcoded - File - NDI - Multiviewer There are multiple options under Error Concealment that can be used individually or together to address different issues: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/MRId8Qdzx8uydT9ZKQa-3_zm-error-concealment.png" size="90" isUploading="false" position="center" width="1418" height="1302" darkWidth="1418" darkHeight="1302" showCaption="false"} - **Continuous Timeline** - corrects errors that are related to timeline jumps in the source. This mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input. - **Replace Frames** - If there are frames with CC (Continuity Counter) errors, it replaces them with skip frames (inserts the last good frame received in place of missing ones). This solves issues such as an IRD that loses synchronization when it receives broken frames. This mechanism also creates a variant of the input (doubling the input). - **Renumber CC **- The **Continuity Counter** is part of the TS encapsulation. When there are CC errors in TR101 analysis, it means that the counter has a gap due to the lost frames. This mechanism can rewrite the CC counter for the downstream devices, so they will see a continuous increase in the counter. - **Delay (ms) **- The delay that the Error Concealment adds to the stream in milliseconds. Error Concealment needs to buffer the stream to analyze it. One second is a reasonable value, so the default value of 1000 ms should be adequate. Lower values may cause the Error Concealment to not be able to fix some of the issues. - **CBR Padding** - A value for the rate at which padding will be added to maintain a specific output transport bitrate. This is included because some decoders (or business models) require a constant bitrate, and CBR Padding ensures that in case of missing data or a VBR source. The value you enter should be approximately the overall maximum bitrate, including the video and audio stream. For example, if you have a video bitrate at 5000 kbps or that varies from 3000-5000 kbps and audio at 64 kbps, the total bitrate will be max 5064 kbps or min 3064 kbps. With CBR padding set at 6000 kbps, 6000 kbps is being delivered downstream at all times, ensuring a consistent bitrate. - **PCR Interval** - Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. This depends on the standard used by downstream encoders or decoders. ATSC encoders expect the PCR interval to be 100 ms, while DVB Euro decoders expect a 40 ms interval. - **Remux Buffer Size** - 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. Higher values allow more time for these fixes, but will add to latency. - **Smoothing** - The size of the buffer in Milliseconds. A larger buffer enables smoother entry, however, it may influence the latency rate. The Smoothing feature uses a buffer to time packets according to the stream's clock, by creating a queue in the buffer, allowing smoother entry into the Broadcaster. This is useful when there are bursts in the rate in which the stream arrives. All of the **Error Concealment** mechanisms are executed in the **Broadcaster**. Error Concealment messages will appear in the source details in ZEN Master: ![Sample Error Concealment Message](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/dRUNyXTuyPiWkWe20puKO-20251020-152059.png) :::hint{type="info"} Note that editing a source to enable or modify Error Concealment, or applying Fix to an input in Broadcaster (see the next section), will cause the stream to be restarted. ::: ## Error Concealment (Fix) in Broadcaster Error Concealment can also be applied to **inputs** in Broadcaster, but in a different way: ::::WorkflowBlock :::WorkflowBlockItem After you have created the source, find it in the sources list. ::: :::WorkflowBlockItem Expand the **Action Menu** and select **Fix**: ![Input Action Menu](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/FcK-rbn3eQnEkt2hgtUT4-20251010-170711.png) ::: :::WorkflowBlockItem In the dialog that opens, you will see the Error Concealment options under **Stream Parameters**: ::Image[]{src="https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/aHv9BwSVn8UhPL47eXxuf-20251010-171000.png" size="80" width="1364" height="964" position="center" alt="Error Concealment Option in Broadcaster" darkWidth="1364" darkHeight="964" showCaption="false"} ::: :::WorkflowBlockItem Select the options you want (refer to the previous section for explanations of the options) and click **OK**. ::: :::: After you have created the source, find it in the sources list. ## Maximizing Stream Resiliency While **Error Concealment** prevents almost all catastrophic stream issues at the viewer end (blank screen, pixelation, gaps in audio), using the **Zixi Protocol **(Zixi Push or Pull sources) provides additional stream resilience that will correct most cases of packet loss by adding the additional mechanisms of **Forward Error Correction** **(FEC)** and **Automatic Repeat reQuest (ARQ). **Together, these mechanisms provide three layers of defense against stream corruption. ::Image[]{src="https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/x1VgR2xXQQeAsdl6S2Ko3-20251010-182225.png" size="90" width="1000" height="740" position="center" alt="Maximizing Stream Resiliency" darkWidth="1000" darkHeight="740" showCaption="false"} [title] Single PUSH Transmission to Redundant Targets (Hot Redundancy) [path] Zixi Redundancy/Zixi Push Transmission Redundancy/ ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/D_higGbYweRQQ6JVC1-tF_image.png) A Zixi source can be configured to PUSH a single input stream to multiple output targets in parallel. The topology includes a source node receiving a single IP input, while simultaneously pushing the stream to two live targets. Two differently named outputs are created at the source using the same Input Stream. If the latency of the outputs is identical, the streams will be frame synced, provided that the video is synced during its entry. ## Source Configuration The following procedure describes how to configure the ZEC to push a single stream to two target hosts in a hot redundancy configuration. In order to configure a hot redundancy you will need to create two outputs containing the same Stream ID with the same latency configuration. The procedure does cover instructions on how to configure the Input into the Zixi Feeder. **To configure the first source output in the source node (e.g. ZEC):** 1. On the **Outputs** page of Zixi Feeder, click the **New Output** button, located in the upper- right end corner of the screen. 2. In the **Output Name** field, type a new name for the output. 3. In the **Type** field, select **Push **radio button. 4. In the **Input Stream** field, select the relevant input stream. 5. In the **Stream ID** field, enter a stream ID (alphanumeric). The same Stream ID will be also configured in the target nodes (Push Input). 6. Optional - in the **Password** field, specify a string to be used at the destination to authenticate that the pushing Broadcaster is allowed to push this stream. 7. In the **Max Latency** field, specify the buffer size that Zixi Broadcaster will keep for error correction. For example, 6000 milliseconds would ensure that the stream is protected for six seconds of errors in the network. Default: 6000. 8. In the **Host** field, enter the host name or IP of the primary target. 9. In the **Port** field, specify the destination port to listen on for the Push stream (default: 2088). 10. In the **Local** **IP** field, select from the drop-down menu, the IP address of the NIC (Network Interface Card) in the Source through which the stream will be pushed. 11. Click **OK**. The output is added to the Outputs list. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/h9ywf6yfC_Xn9V_k6k6St_image.png) **To configure the second source output in the source node (e.g. ZEC) repeat the same instructions.** The second output is added to the Outputs list. ## Target Configuration The following procedures describe how to configure the two target Zixi Broadcasters in a hot redundancy configuration. The two targets use different Stream IDs, as configured in the first and second sources. **To configure the first target node (e.g. Zixi Broadcaster):** 1. Click the **Inputs **tab at the top of the first Zixi Broadcaster administrative screen 2. Click **New Input **on the upper right hand side of the screen. 3. In the **Stream ID** field, enter the same “Stream ID” as the first source output. 4. Select the **Push** radio button option. 5. In the **Password** field, if you have configured a password in the source (Feeder output), enter the same password. 6. Configure additional parameters as required. 7. Click **OK**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/s8MGpBmbuoGEkxQkFJ4Ph_image.png) **To configure the second target node (e.g. Zixi Broadcaster) repeat the same instructions.** The second input is added to the Inputs list. ## Cost Considerations This topology duplicates the target side Zixi node software and hardware components. This configuration also requires doubling the up-link bandwidth. It is recommended to allocate more than twice the expected maximum bit-rate to ensure head room. ## Latency Considerations For detailed recovery time details, please contact your Zixi representative. [title] Product Features [path] / ![Product Features](https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/n26HVb3yMqwJcKpHLET0x_productfeature2.jpg) This section covers core concepts and cross-product features to help you get the most out of Zixi products. - [AWS SSM User Guide](docId\:SAhJY3H8uS6uNT2OkuNtR) - [Error Correction and Concealment](docId:9_OLo1Argk_2aDoSHYFBb) - [Inline/HTML5 Player](docId\:O_Yk6ekqB7ZYSmmGneFzo) - [Latency Negotiation](docId\:OT6ICc9DNdHiF9WQMpSoj) - [Zixi Transcoding](docId\:j17NBlQHLOjAAuCAaJCde) - [Redundancy](docId\:xmiT0Gwd-CyObMGiwoU1o) - [TAMS and Zixi](docId\:Xb6n9zuNCcGOdDaBrvsba) - [Transport Streams and IP Delivery Protocols](docId\:UreBRT0iD42_JulFzHhFe) [title] Dual PUSH Transmission to Single Target with High Priority Source (Warm Redundancy) [path] Zixi Redundancy/Zixi Push Transmission Redundancy/ ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/O4Zni5s1fnh08JlKySEMT_image.png) A Zixi PUSH input can be configured to switch to a designated hi-priority source. The topology includes redundant source nodes pushing to a primary target. In this configuration the sources DO NOT contend for the target Input. If the High-Priority Source connection is available it will take-over the Input. In the event the connection is lost, the secondary stream will assume the connection. However, if the primary connection returns, the target will drop the secondary connection and return to the primary stream. ## Source Configuration The following procedure describes how to configure two ZECs to push a single stream to a target hosts in a warm redundancy configuration. The procedure does not cover instructions on how to configure the Input into the ZEC. **To configure the primary source node (e.g. ZEC):** 1. On the **Outputs** page of ZEC, click the **New Output** button, located in the upper- right end corner of the screen. 2. In the **Output Name** field, type a new name for the output. 3. In the **Type** field select **Push **radio button option. 4. In the** Input Stream** field select the relevant the input stream. 5. In the **Stream ID** field, enter a stream ID (alphanumeric). The same Stream ID will be also configured in the target node (Push Input). 6. Optional - in the **Password** field, specify a string to be used at the destination to authenticate that the pushing Broadcaster is allowed to push this stream. 7. In the **Max Latency** field, specify the buffer size that Zixi Broadcaster will keep for error correction. For example, 6000 milliseconds would ensure that the stream is protected for six seconds of errors in the network. Default: 6000. 8. In the **Host** field, enter the host name or IP of the primary target. 9. In the **Port** field, specify the destination port to listen on for the Push stream (default: 2088). 10. In the **IP** field, select from the drop-down menu, the IP address of the NIC (Network Interface Card) in the Source through which the stream will be pushed. 11. Click **OK**. The output is added to the Outputs list. **To configure the secondary source node (e.g. ZEC) repeat the steps above.** ## Target Configuration The following procedures describe how to configure the target Zixi Broadcaster in a warm redundancy with high priority source configuration. The target is configured with a single input. If this input is unavailable the secondary input will be received. The input must use the same Stream ID that was used to configure the primary and secondary Source ZEC. Before you begin, you must obtain the ID of the ZEC that will be used as the high-priority source. **To obtain the High-Priority ZEC ID:** - Go to the **Status** page of the primary ZEC. - The ZEC ID is presented in the **ID** field under **Genral**. **To configure the target node (e.g. Zixi Broadcaster):** 1. Click the **Inputs **tab at the top of the secondary Zixi Broadcaster administrative screen 2. Click **New Input **on the upper right hand side of the screen. 3. In the **Stream ID** field, enter the same “Stream ID” as the source outputs (matches that of the primary and secondary sources output). 4. Select the **Push **option. 5. Under Stream Parameter, in the** ID of high priority source** field, enter the **ID **of the primary ZEC. 6. Configure additional parameters as required. 7. Click **OK**. ## Cost Considerations This topology duplicates the source side Zixi node software and hardware components. It does not require doubling the up-link bandwidth, as the backup connection stream is only active in the event that the primary stream fails. ## Latency Considerations For detailed recovery time details, please contact your Zixi representative. [title] Dual PULL Transmission from Single Source (Hot Redundancy) [path] Zixi Redundancy/Zixi Pull Transmission Redundancy/ ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ZApSYTlzqZMZAhRtcX1RR-20260216-142445.png) Zixi can be deployed to pull a stream to redundant targets. This topology shows a stream that is pulled from a single source node to a corresponding pair of redundant targets in a hot redundancy configuration. The stream is pulled in parallel by the two redundant targets, creating two redundant paths to the destination. Two distinctly named outputs are created at the source Zixi Broadcaster. Each output is configured to stream to one of the redundant ZECs. If the latency of the outputs is identical, the streams will be frame synced, provided that the video is synced on entry. A single Input is created at the source Zixi Broadcaster. This input may include Unlimited Max Outputs, which will enable multiple simultaneous Pull connections. If you want to limit the number of Pull connections, you can enter the desired number of Max Outputs (e.g. enter '2', if you have two ZECs pulling). In runtime, the two ZECs will connect to the Zixi Broadcaster and the two outputs are created automatically "on the fly". Additional connections will be denied. Alternatively, you can manually configure the two Pull outputs in the Zixi Broadcaster. ## Source Configuration **To configure the source node (e.g. Zixi Broadcaster):** 1. On the **Inputs** page of the primary Zixi Broadcaster, click **New Input** on the upper- right end corner of the screen. 2. In the **Stream ID** field, type a new name for the input stream. 3. Select the **a relevant connection type** option. 4. In the **Max Outputs **field, do one of the following: 1. Leave it as **Unlimited**. 2. Specify the maximal number of connections (e.g. type "2" to enable two Pull connections). 5. Specify the stream parameters according to the relevant connection type selected. 6. Click **OK **to create the primary input. ## Target Configuration A Pull input should be configured in the primary and backup target nodes. **To configure the primary target node (e.g. ZEC):** 1. Click the **Inputs **tab at the top of the ZEC administrative screen. 2. Click **New Input **on the upper right hand side of the screen. 3. In the **Input Name** field, type a new name for the input. 4. Select the **Pull **option. 5. In the **Remote** **Host** field, enter the host name or IP of the Primary Broadcaster source. 6. In the **Remote** **Port** field, enter the connection port of the source host (primary Zixi Broadcaster). Default: 2077. 7. In the **Remote** **Stream** **ID** field, enter the stream ID used in the Primary Broadcaster source input. 8. Configure additional parameters as required. 9. Click **OK**. **To configure the secondary target node (e.g. ZEC):** - Repeat the same configuration steps as the ones in the primary target node. Make sure you use the same input name used in the primary target node. ## Cost Considerations This topology duplicates the target Zixi hardware and software components. The configuration also requires using double the up-link bandwidth. Allocation of twice the expected maximum bit-rate with head room is advised. ## Latency Considerations For detailed recovery time details, please contact your Zixi representative. [title] Dual PUSH Transmission to Redundant Targets (Full Cross Over) [path] Zixi Redundancy/Zixi Push Transmission Redundancy/ ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/prPKjIm37PMz1YMYPySJq-20260126-113441.png) This topology includes source and target redundancy with additional cross-over redundancy capabilities. The topology includes two simultaneous streams delivered in parallel from two separate source nodes to a corresponding pair of redundant targets. If the latency of the outputs is identical, the streams will be frame synced, providing the video is synced on entry. In addition, in the unlikely event that a second loss occurs at the opposing connected end-point, the automated cross-over mechanism uses the resources of the opposite path, providing a stream with minimal disruption. ## Source Configuration The following procedure describes how to configure two ZECs to push a single stream to two target hosts (parallel streams), while adding an alternative target host to each source for additional redundancy. The procedure does not cover instructions on how to configure the Input into the ZECs. **To configure the primary source node (e.g. ZEC):** 1. On the **Outputs** page of ZEC, click the **New Output** button, located in the upper- right end corner of the screen. 2. In the **Name** field, type a new name for the output. 3. In the **Type** field select **Push **. 4. In the** Input Stream** field select the relevant the input stream. 5. In the **Host** field, enter the host name or IP of the primary target (e.g., the Primary Broadcaster). 6. In the **Port** field, specify the destination port to listen on for the Push stream (default: 2088). 7. In the **IP** field, select from the drop-down menu, the IP address of the NIC (Network Interface Card) in the Source through which the stream will be pushed. 8. Click the **"+"** button to add another (secondary) target. Another line is added with the properties of the secondary destination. 9. Fill out the secondary destination parameters (e.g., Secondary Broadcaster). 10. In the **Stream ID** field, enter a stream ID (alphanumeric). The same Stream ID will be also configured in the target node (Push Input). 11. Optional - in the **Password** field, specify a string to be used at the destination to authenticate that the pushing Broadcaster is allowed to push this stream. 12. In the **Max Latency** field, specify the buffer size that Zixi Broadcaster will keep for error correction. For example, 6000 milliseconds would ensure that the stream is protected for six seconds of errors in the network. Default: 6000. 13. Click **OK**. The output is added to the Outputs list. **To configure the secondary source node (e.g. ZEC):** - Repeat the steps above to configure the second source node, however in the **Host** field enter the host name or IP of the Secondary Broadcaster. - The stream in the second source must have the same Stream ID as the first source. - Make sure the latency is the same as on both ZECs. - Click the **"+"** button to add the first target (Primary Broadcaster). Another line is added with the properties of the first target. Fill in the details of the Primary Broadcaster. - Click **OK**. ## Target Configuration The following procedures describe how to configure the two target Zixi Broadcasters to accept the feed from their corresponding sources as well as a backup feed from the alternative source. The target is configured with two inputs. If this input is unavailable the secondary input will be received. **The input must use the same Stream ID** that was used to configure the primary and secondary Source ZECs. **To configure the primary target node (e.g. Zixi Broadcaster):** 1. Click the **Inputs **tab at the top of the Zixi Broadcaster administrative screen 2. Click **New Input **on the upper right hand side of the screen. 3. Select the **Push **option. 4. Create an input, while ensuring the “Stream ID” matches that of the primary and the secondary sources output. 5. Configure additional parameters as required. 6. Click **OK**. **To configure the secondary target node (e.g. Zixi Broadcaster):** - Repeat the steps used to configure the primary target node. ## Cost Considerations This topology duplicates the hardware and software components of both the source and the target. The configuration also requires using double the up-link bandwidth. Allocation of twice the expected maximum bitrate with head room is advised. ## Latency Considerations For detailed recovery time details, please contact your Zixi representative. [title] Dual PULL Transmission from Redundant Sources (Full Cross-Over) [path] Zixi Redundancy/Zixi Pull Transmission Redundancy/ ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/v2Z3Z-nUQltfzJ2Wmcp8H-20260527-084123.png" size="74" width="502" height="127" position="center" darkWidth="502" darkHeight="127" showCaption="false"} This topology includes source and target redundancy with additional cross-over redundancy capabilities. The topology includes two simultaneous streams delivered in parallel from two separate source nodes to a corresponding pair of redundant targets. If the latency of the outputs is identical, the streams will be frame synced, providing the video is synced on entry. In addition, in the unlikely event that a second loss occurs at the opposing connected end-point, the automated cross-over mechanism uses the resources of the opposite path, providing a stream with minimal disruption. The configuration is performed on the target ZECs. There you will configure a Pull input from the primary Broadcaster, which includes a backup host (secondary Zixi Broadcaster). The stream has to be defined in the primary and secondary Broadcasters as inputs with the same stream ID. In runtime, the Zixi Receiver will connect to the primary Zixi Broadcaster and the output is created automatically "on the fly". If the primary source becomes unavailable the target will attempt to pull the same stream with the same stream ID from the secondary source (which has been defined as the Backup host). A single Input is created at the source Zixi Broadcasters, which includes a **Max Outputs** limitation of 1 output. The same Pull input is created in both the Main ZEC and Backup ZEC. In runtime, the ZEC will connect to the Zixi Broadcaster and the output is created automatically "on the fly". If the Main Zixi Receiver becomes unavailable, the Zixi Broadcaster will grant the Backup Receiver with the permission to pull the stream. However, when the main Zixi Receiver becomes available again, Zixi Broadcaster will not grant a permission to pull the stream again (due to the max outputs limitation) until the Backup Zixi Receiver stops pulling the stream. ## Source Configuration **To configure the primary source node (e.g. Zixi Broadcaster):** 1. On the **Inputs** page of the primary Zixi Broadcaster, click **New Input** on the upper right-end corner of the screen. 2. In the **Stream ID** field, type a new name for the input stream. 3. In the** Max Outputs** field, type 1. 4. Select the **a relevant connection type** option. 5. Specify the stream parameters according to the relevant connection type selected. 6. Click **OK **to create the primary input. **To configure the secondary source node (e.g. Zixi Broadcaster):** - Repeat the steps above on the secondary Zixi Broadcaster. ## Target Configuration **To configure the primary target node (e.g. primary ZEC):** 1. Click the **Inputs **tab at the top of the primary ZEC administrative screen 2. Click **New Input **on the upper right hand side of the screen. 3. In the Input Name field, type a new name for the input. 4. Select the **Pull **option. 5. In the **Host** field, enter the host name or IP of the primary source. 6. In the **Backup** **Host** field, enter the host name or IP of the secondary source. 7. In the **Port** field, enter the connection port of the host (ZEC). Default: 2077. 8. In the **Stream** field, enter the stream ID used in the primary and secondary source inputs. The same stream ID should be used in the Inputs configured on the Primary and Secondary sources (Zixi Broadcasters). The output is created "on the fly" on the Zixi Broadcaster, so there is no need to configure it. 9. Configure additional parameters as required. 10. Click **OK**. **To configure the secondary target node (e.g. secondary ZEC):** 1. Click the **Inputs **tab at the top of the secondary ZEC administrative screen 2. Click **New Input **on the upper right hand side of the screen. 3. In the Input Name field, type a new name for the input. 4. Select the **Pull **option. 5. In the **Host** field, enter the host name or IP of the secondary source. 6. In the **Backup** **Host** field, enter the host name or IP of the primary source. 7. In the **Port** field, enter the connection port of the host (ZEC). Default: 2077. 8. In the **Stream** field, enter the stream ID used in the primary and secondary source inputs. The same stream ID should be used in the Inputs configured on the Primary and Secondary sources (Zixi Broadcasters). The output is created "on the fly" on the Zixi Broadcaster, so there is no need to configure it. 9. Configure additional parameters as required. 10. Click **OK**. ## Cost Considerations This topology duplicates the hardware and software components of both the source and the target. The configuration also requires using double the up-link bandwidth. Allocation of twice the expected maximum bit-rate with head room is advised. ## Latency Considerations For detailed recovery time details, please contact your Zixi representative. [title] Dual NIC Redundancy [path] Zixi Redundancy/ Dual NIC (Network Interface Card) redundancy configurations include redundant paths from a single source to a single target node. Each NIC has a different IP address. This means that, although there is a single source, the redundancy is configured in the same way as if there were two sources. Redundant streams can be delivered over multiple Network Interface Cards (NICs) in either a PUSH or PULL configuration. Dual NIC redundancy can be deployed through the following configuration options: - [Dual NIC PULL Redundancy (Warm Redundancy)](docId\:I83ggeXjRVlOdALAXZGnb) - [Dual NIC PUSH Redundancy (Warm Redundancy)](docId\:uaCc9BvfWi4_8UVdh7poA) - [Dual NIC PULL Redundancy (Hot Redundancy)](docId:-rbgAUqaGm0YdmJSsFZ7G) - [Dual NIC PUSH Redundancy (Hot Redundancy)](docId\:bi174gMuDnH5-HECQWCXY) [title] Dual PULL Transmission from Redundant Sources (Hot Redundancy) [path] Zixi Redundancy/Zixi Pull Transmission Redundancy/ ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/CYJNZT4PQF9aNRzKdHdtW-20260216-143935.png) Zixi can be deployed to pull parallel redundant sources to two targets. This topology includes two simultaneous streams pulled in parallel from two separate source nodes to a corresponding pair of redundant targets. The streams are pulled in parallel by the two redundant targets, creating two redundant paths to the destination. If a component in one of the paths fails, the alternative path can be used by the IRD. Two distinctly named inputs are created at the source Zixi Broadcasters. Each ZEC will be configured to Pull the stream from each of the Zixi Broadcasters. If the latency of the Inputs is identical, the streams will be frame synced providing they video is synced at the source. ## Source Configuration Configuring in advance the Pull output in the primary and secondary Broadcasters is not mandatory. **To configure the first source node (e.g. Primary Zixi Broadcaster):** 1. On the **Inputs** page of the primary Zixi Broadcaster, click **New Input** on the upper-right corner of the screen. 2. In the **Stream ID** field, type a new name for the input stream. 3. Select the **a relevant connection type** option. 4. In the **Max Outputs** field, do one of the following: 1. Leave it as Unlimited. 2. Specify the maximal number of connections (e.g. type "1" to enable a single Pull connection). 5. Specify the stream parameters according to the relevant connection type selected. 6. Click **OK **to create the primary input. **To configure the second source node (e.g. Secondary Zixi Broadcaster):** 1. On the **Inputs** page of the primary Zixi Broadcaster, click **New Input** on the upper-right corner of the screen. 2. In the **Stream ID** field, type a new name for the input stream. 3. Select the **a relevant connection type** option. 4. In the **Max Outputs** field, do one of the following: 1. Leave it as Unlimited. 2. Specify the maximal number of connections (e.g. type "1" to enable a single Pull connection). 5. Specify the stream parameters according to the relevant connection type selected. 6. Click **OK **to create the primary input. ## Target Configuration **To configure the primary target node (e.g. ZEC):** 1. Click the **Inputs **tab at the top of the ZEC administrative screen 2. Click **New Input **on the upper right hand side of the screen. 3. Select the **Pull **option. 4. In the **Remote Host** field, enter the name of the primary source host Zixi Broadcaster. 5. In the **Remote** **Port** field, enter the port number as configured in the primary Zixi Broadcaster. 6. In the **Remote** **Stream** **ID** field, enter the stream ID as configured in the primary Zixi Broadcaster. 7. Configure additional parameters as required. 8. Click **OK**. **To configure the secondary target node (e.g. ZEC):** 1. Click the **Inputs **tab at the top of the ZEC administrative screen 2. Click **New Input **on the upper right hand side of the screen. 3. Select the **Pull **option. 4. In the **Remote Host** field, enter the name of the secondary source host Zixi Broadcaster. 5. In the **Remote Port** field, enter the port number as configured in the secondary Zixi Broadcaster. 6. In the **Remote stream ID** field, enter the stream ID as configured in the secondary Zixi Broadcaster. 7. Configure additional parameters as required. 8. Click **OK**. ## Cost Considerations This topology duplicates the hardware and software components of both the source and the target. The configuration also requires using double the up-link bandwidth. Allocation of twice the expected maximum bit-rate with head room is advised. ## Latency Considerations For detailed recovery time details, please contact your Zixi representative. [title] Zixi Latency Negotiation [path] / # Overview Video latency refers to the time elapsed between the source capture and the player's rendering. Zixi’s software platform provides a flexible approach to latency management across origin, Broadcaster, and destination components. When setting latency values, consider the tradeoffs between low delay, error recovery, and network delivery. # Platform latency The following describes latency negotiation between client and server (Zixi Broadcaster). ## Push mode In push mode, the sender actively pushes a video stream to a destination. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/P8-QcmDoizNmSqxxp1iTm_image.png) Diagram: - The client can be associated with: - Feeder - ZEC as feeder - Broadcaster as feeder - Embedded feeder SDK - Latency is **required** for the client PUSH output. - Latency is **optional** for the Broadcaster (server). - Broadcaster negotiation: - If latency **is not set** in the Broadcaster, use the client latency. - If latency **is set** in the Broadcaster, override the client latency. ## Pull mode In Pull mode, the receiver initiates the connection and requests the stream from the Broadcaster. ::Image[]{src="https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/vZeKqmGk0rS_ciHtDgpWV_image.png" size="90" width="870" height="472" position="center" darkWidth="870" darkHeight="472" showCaption="false"} Diagram: - The client can be associated with: - Receiver - ZEC as receiver - Broadcaster as receiver - Embedded receiver SDK - Latency is **required** for the client PULL input. - Latency is **optional** for the Broadcaster (server). - Broadcaster negotiation: - If latency **is not set** in the Broadcaster, use the client latency. - If latency **is set** in the Broadcaster, override the client latency. ## Platform latency precedence For the PUSH and PULL mode scenarios above, the latency precedence can be summarized as follows: 1. Broadcaster latency, if set 2. Client latency # ZEN Master Cluster Redirection Rules In addition to the platform latency negotiation discussed above, Zixi provides a ZEN Master-only feature called Cluster Redirection Rules. This allows you to manage Inter-Cluster Sources, Auto-Pulls, and latency overrides. ## Pull mode Cluster Redirection Rules only apply to Pull mode. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/kuHpvZXAQiSyNiUCFHesH_image.png) Diagram: - The client can be associated with: - Receiver - ZEC as receiver - Broadcaster as receiver - Embedded receiver SDK - Latency is **required** for the client PULL input. - Latency is **optional** for Cluster Redirection Rules. - Latency is **optional** for the Broadcaster (server). - ZEN Master negotiation: - If latency **is set** for Cluster Redirection Rules, then override all other values. - Broadcaster negotiation: - If latency **is not set** in the Broadcaster, use the client latency. - If latency **is set** in the Broadcaster, override the client latency. ## Setting Cluster Redirection Rules To apply redirection rules to a Broadcaster Cluster, do the following: ::::WorkflowBlock :::WorkflowBlockItem In the left navigation, select **Broadcasters**. ::: :::WorkflowBlockItem From the **Broadcaster Clusters** list, select a Cluster. ::: :::WorkflowBlockItem Select **Redirection Rules** and then **+Add Rule**. ::Image[]{src="https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/GpTOGnNWnFWdXXBXtf1UU_.blob" size="90" width="936" height="300" position="center" darkWidth="936" darkHeight="300" showCaption="false"} ::: :::WorkflowBlockItem Complete the form and select **Save**. ::Image[]{src="https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/NaLJFjJyNNd842U_ECb9x_.blob" size="50" width="394" height="489" position="center" darkWidth="394" darkHeight="489" showCaption="false"} ::: :::: ## ZEN Master latency precedence With ZEN Master, latency has an additional consideration: 1. Cluster Redirection Rules, if set 2. Broadcaster latency, if set 3. Client latency # Dynamic latency In addition to setting latency values, you can also enable Zixi’s Dynamic Latency, which adjusts latency dynamically in response to changing network conditions. The latency values that you set become the upper bounds for dynamic adjustment. Note that Zixi limits the latency change rate to make clock frequency drift within specs of mpeg-ts. To enable Dynamic latency, do one of the following: - In the Broadcaster input settings, select **Minimize Latency**. ::Image[]{src="https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/kZ0YPYkC847ku6aWE5_h6_.blob" size="60" width="528" height="307" position="center" showCaption="false"} - In ZEN Master, when creating/updating a Source, select **Minimize Latency**. ::Image[]{src="https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/hrhEup0rYQ5bRWIAzHJ6S_.blob" size="90" width="936" height="399" position="center" showCaption="false"} For details about Dynamic Latency, see the [Latency Considerations](docId\:b5ijrtxUIcWxU7rCmdHza) document. # Trade-offs Zixi offers a three-way trade-off between: - Latency - Resiliency (error recovery) - Overhead (FEC/ARQ) Lower latency reduces recovery robustness. Higher latency improves resiliency. # Summary Latency can impact event success. Zixi provides a comprehensive solution that masters network dynamics to guarantee low-latency, reliable delivery at any scale. # Notes Here are some additional notes: - For sufficient error recovery, Zixi recommends setting the latency to at least 3 to 5 times larger than the \[RTT + Jitter]. You may need to adjust latency depending on the ISP network, as conditions can change due to network overload, a new network path, or additional hops. - Zixi telemetry displays actual latency, not just configured values. [title] Understanding Transport Streams and IP Delivery Protocols [path] / # Overview Modern broadcast and streaming workflows rely on **MPEG Transport Streams (TS)** for reliable delivery of video, audio, and metadata across diverse networks. This document explains: - How video and audio are encoded into transport streams. - How receivers extract and decode these streams. - How IP delivery protocols (SRT, RIST, Zixi) ensure resilience and quality. Here's a basic architectural diagram of the encoding - decoding flow: ::Image[]{src="https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/R7V9DspVG3WArdS4rN20c-20260107-144815.png" size="80" width="1536" height="1024" position="center" alt="Transport Stream Encoding/Decoding" showCaption="false"} We will look at a more complete diagram after looking at some of the details of the process. ## Encoding Pipeline ### Step-by-Step Process 1. **Compression** - Video: H.264/AVC, HEVC (H.265), or MPEG-2. - Audio: AAC, AC-3. 2. **Packetization** - Compressed streams become **Elementary Streams (ES)**. - ES wrapped into **Packetized Elementary Streams (PES)** with timing info ( /) - **Transport Stream Packetization** - PES split into **188-byte TS packets**. - Each packet includes: - **Sync byte (0x47)** for alignment. - &#xNAN;** (Packet Identifier)** for stream identification. - Optional **adaptation field** for timing ( \[Program Clock Reference]). 3. **Multiplexing** - Video, audio, and metadata interleaved into one TS. - &#xNAN;**/**&#xNAN;** tables** describe program structure. 4. **Metadata & Signaling** - SCTE-35 markers for ad insertion. - Timing references (PTS/DTS, PCR) for synchronization. ## Decoding Pipeline 1. **Demultiplexing** - Receiver uses PAT/PMT to identify PIDs. 2. **Depacketization** - TS packets → PES → ES. 3. **Decoding** - Video/audio are decoded using original codecs. 4. **Rendering** - Frames and audio are synchronized for playback. ## IP Delivery Protocols ### Why IP Delivery? Traditional satellite/cable links are being augmented or replaced by IP-based transport for flexibility and cost efficiency. However, IP introduces packet loss, jitter, and latency challenges. ### Protocols - **Zixi Protocol** - (Automatic Repeat reQuest) for packet recovery. - (Forward Error Correction) for proactive error handling. - Bonding across multiple paths for resilience. - AES-256 encryption and security. - Integrated orchestration via **ZEN Master**. - **SRT (Secure Reliable Transport)** - ARQ-based recovery. - AES encryption. - Designed for low-latency contribution feeds. - **RIST (Reliable Internet Stream Transport)** - Standards-based. - ARQ with optional FEC. - Ideal for broadcast-grade reliability. ### Error Correction Layers - **ARQ**: Retransmits lost packets based on NACKs. - **FEC (Forward Error Correction)**: Adds redundant data for recovery without retransmission. - **Bonding**: Distributes traffic across multiple links for hitless failover. - **Jitter Buffers**: Smooth out packet arrival variations. ## Timing & Signaling - **PTS/DTS**: Presentation and decoding timestamps. - **PCR**: Program Clock Reference for sync. - **SCTE-35**: Ad signaling for dynamic ad insertion. ## End-to-End Architecture **Source → Contribution → Core → Distribution → Affiliate** - Transport Stream encapsulated in IP packets. - Delivered via SRT, RIST, or Zixi with error correction. - Monitored via ZEN Master for SLA compliance. ### Diagram Here is a more complete diagram: ::Image[]{src="https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/mHJXG2KjpF8UlfG8PSGFs-20260112-155215.png" size="80" width="1536" height="1024" position="center" alt="Transport Stream Processing End-to-End" showCaption="false"} ## Key Benefits Zixi Provides - **Reliability**: >99.999% uptime with bonding and error correction. - **Security**: AES-256 encryption and DTLS. - **Flexibility**: Multi-protocol support for diverse workflows. - **Visibility**: Real-time telemetry and analytics via ZEN Master. ## Related Topics [Zixi Transport Stream Protocol](docId\:jdVs1L_ZSEjBtnf2oKaV9) [Improving Stream Resiliency: Error Correction and Concealment](docId:9_OLo1Argk_2aDoSHYFBb) [title] Zixi Pull Transmission Redundancy [path] Zixi Redundancy/ Zixi's pull redundancy configurations include either two parallel streams running across redundant paths or a target node that can automatically switch to a redundant source. The target node will attempt to pull the primary sources again only in the event that the secondary source becomes unavailable. Zixi pull transmission redundancy can be deployed through the following configuration options: - [Single PULL Transmission from Redundant Sources (Warm Redundancy)](docId\:bCS8GZFnrtZ-eoxVkwY3i) - [Single PULL Transmission from Redundant Sources (Hot Redundancy)](docId\:HsaKQf4iH2RZSVnGIrglo) - [Dual PULL Transmission from Single Source (Warm Redundancy)](docId\:OOsn4-7Y1p7OlauhrU8yC) - [Dual PULL Transmission from Single Source (Hot Redundancy)](docId\:I6Don4JJ0H8XFhXKmndR9) - [Dual PULL Transmission from Redundant Sources (Hot Redundancy)](docId\:LdjA5EkqM84XoKWgVy0-5) - [Dual PULL Transmission from Redundant Sources (Full Cross-Over)](docId\:WHNAMVHN5rj3HTfM23WRM) [title] AWS SSM User Guide [path] / # Overview Using AWS Systems Manager (SSM) command scripts, you can control and automate your AWS resources. In this guide, you will learn how to connect and run SSM commands from your Zixi Broadcaster. # Steps Follow these steps to initiate SSM commands from within ZEN Master. ## Step 1: Update AWS IAM Policy With the Feb 2026 release of ZEN Master, the AWS IAM policy has been updated to include authorization for SSM. 1. Sign in to ZEN Master. 2. In the left navigation, hover over **Configuration** and select **Amazon AWS**. 3. In the top tabs, select **Documentation**. 4. For the **policy document JSON file**, select the copy icon to the right of step 3. This latest set of permissions allows ZEN Master to trigger SSM documents. ![Create an IAM Role for ZEN Master](https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/hhcZsWaVzFwvMZl59NOCo_.blob) 5. Sign in to your AWS IAM console. 6. Select the **Policies** page. ::Image[]{src="https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/A7Yq9Tp97OJ29jeR7sGOr_.blob" size="40" width="349" height="538" position="center" alt="Select Policies Page" showCaption="false"} 7. Either update an existing policy or create a new policy using the copied permissions. 1. If you are creating a new policy and role, *follow the steps in the ZEN Master Documentation tab*. ## Step 2: Create a Role with SSM Agent Next, create a Role with the SSM Agent installed. 1. Return to your AWS IAM console. 2. Select **Roles** and then **Create Role**. 3. Select **EC2**. 4. In the **Add permissions** screen, search for **SSM**. 5. Select the SSM agent: **AmazonSSMManagedInstanceCore** 6. Click **Next**. 7. In the **Name, review, and create screen**, enter the following: 1. Role name 2. Description 3. Leave the default trust policy and permissions 8. Click **Create role**. 9. View your new role and copy the **Instance profile ARN**. ## Step 3: Apply the Role to your Cluster Now, you can apply the AWS Role to your ZEN Master Broadcaster Cluster. 1. Return to ZEN Master. 2. In the left navigation, select **Broadcasters**. 3. Select a Broadcaster Cluster and click **Edit**. ![Broadcaster Cluster](https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/7E1sMbkO6PDZujHTwRX9F_.blob) 4. Find the **Instance profile ARN** field and paste in your value from the new Role you created in AWS. ![Insert Instance Profile ARN](https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/jJjLGR1hsEFbpuH59hwZJ_.blob) 5. Click **Save**. You can now initiate an SSM document from a Broadcaster within this Cluster. ## Step 4: Create an SSM Document In the AWS IAM console, you will create an AWS Systems Manager (SSM) Command Document. 1. In AWS, go to the AWS Systems Manager. 2. In the left navigation, select **Documents**. 3. Expand the **Create document** button and select **Command or session**. 4. In the Document details screen, enter the following: 1. Name 2. Target type - **AWS: EC2 Instance** 3. Content JSON – Update with your script Here’s an example script that you can try. This example returns 'hello' whether the instance is running Linux or Windows. ```json { "schemaVersion": "2.2", "description": "A simple document to echo hello to the command line.", "mainSteps": [ { "action": "aws:runShellScript", "name": "echoHelloLinux", "precondition": { "StringEquals": [ "platformType", "Linux" ] }, "inputs": { "runCommand": [ "echo 'hello'" ] } }, { "action": "aws:runPowerShellScript", "name": "echoHelloWindows", "precondition": { "StringEquals": [ "platformType", "Windows" ] }, "inputs": { "runCommand": [ "Write-Output 'hello'" ] } } ] } ``` 5. Click **Create document**. ## Step 5: Initiate SSM Document from ZEN Master Your new SSM document will now appear as an option to select in ZEN Master. 1. Return to your Cluster in ZEN Master. 2. Edit a Broadcaster within the Cluster. 3. In the top right, select the kabob menu and select **Run SSM Command**. ![Run SSM Command Option](https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/UQ3YgLgLO1Cknt6A8kc95_.blob) 4. Expand **Available SSM Scripts**. You should see your new SSM document in the list. 5. Select your new SSM document. 6. Click **Run SSM Command**. ![Run SSM Command](https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/L2fxGjfjoLTJYAxuj2Zmx_.blob) In the **SSM Command Output** window, you will see the command-line output on the instance. *Note that only the last 10 lines of output are displayed in the output window.* ![SSM Command Output](https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/f6a-Lz3oBWVyFnCa6-mQD_image.png) If you want to write the output to an S3 bucket, you can do this in AWS within your SSM document. :::hint{type="info"} Coming soon, you will be able to write the output to an S3 bucket from ZEN Master. ::: [title] The Zixi Inline/HTML5 Player [path] / Whether you manage your streams as Sources in ZEN Master or Inputs in Broadcaster, Zixi provides an inline HTML5 player to let you see the stream playing without having to go to an external player. :::hint{type="warning"} Note that the HTML5 player does not support all video formats, so you won't be able to view all Sources/Inputs this way. ::: ## ZEN Master In ZEN Master, you can view the live stream for a source by going to Sources List and clicking on the source you want to see. The Source Details will open on the Stream tab, which includes in the inline player as well as other source information: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/iTDF0AwFeLCIc95N-WIXo_inline-player-source.png) ## Broadcaster In Broadcaster, the inline player is opened from that Actions Menu for an input: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/KCdIg9jM3cCKF4nY1mEw9_inline-html5-player.png" size="30" isUploading="false" position="center" width="310" height="630" darkWidth="310" darkHeight="630" showCaption="false"} [title] TAMS and Zixi [path] / ## What is TAMS? TAMS stands for **Time Addressable Media Storage**, a cloud-native platform designed to optimize how media content—especially live streams—is stored, accessed, and repurposed. Unlike traditional file-based workflows, TAMS organizes content into **time-stamped segments** rather than monolithic files. This architecture enables applications to retrieve only the exact time range needed, dramatically reducing latency and bandwidth consumption. Originally developed by the BBC, TAMS combines: - **Chunked media encoding** - **Cloud storage orchestration** - **Timecode-driven API interfaces** This makes TAMS ideal for both **Video on Demand (VOD)** and **live workflows**, supporting real-time clipping, compliance recording, and rapid syndication without rendering or file transfers. :::hint{type="info"} **Note: TAMS outputs require Zixi Broadcaster v19 or later. TAMS targets will also be available in ZEN Master in February 2026.** ::: ## Typical Use Cases 1. **Live Sports and News Clipping** Broadcasters can extract highlights from live events in seconds, enabling near-instant publishing to social platforms or OTT services. This is critical for monetizing live sports and breaking news. 2. **Compliance Recording** Regulatory environments often require long-term storage of live content. TAMS allows broadcasters to archive streams and retrieve specific time windows for audits without downloading entire files. 3. **Cloud Editing and Collaboration** Editors can pull precise segments directly into tools like Adobe Premiere via API, streamlining workflows for distributed teams. This eliminates the need for heavy file transfers and accelerates turnaround. 4. **Syndication to Partners** Instead of rendering and shipping files, TAMS enables partners to access content via secure links and time ranges, reducing operational overhead and speeding delivery. ### Sample TAMS Workflow ![Sample TAMS Workflow](https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/oPT3MfiG1V3LQ007BDqg--20251215-185355.png) ## How Zixi Works with TAMS Zixi integrates TAMS into its **Broadcaster v19** and **ZEN Master** platforms, creating a seamless ecosystem for live video contribution, processing, and delivery. Here’s how: - **Segmented Uploads via API** Zixi Broadcaster writes transport stream (TS) segments to TAMS using dedicated storage URLs and metadata exchange. This ensures time-indexed storage for frame-accurate retrieval. - **Rapid Turnaround Workflows** Integration supports real-time clipping and compliance workflows without leaving the Zixi environment. This “stickiness” reduces complexity and keeps customers within the Zixi ecosystem. - **Live and VOD Enablement** Applications can request segments via TAMS APIs or webhooks, enabling dynamic playout and cloud-based editing. Zixi’s orchestration layer ensures interoperability across IP-based workflows. [title] Target Configuration [path] Zixi Redundancy/Untitled/ The following procedure describes how to configure three inputs as a Hitless Failover group in Zixi Broadcaster. The configuration in ZEC is similar. The procedure does not cover instructions on how to configure the Zixi Feeder inputs and outputs. **To configure a Failover Group in Zixi Broadcaster:** ::::WorkflowBlock :::WorkflowBlockItem On the **Input **screen of Zixi Broadcaster, select the checkboxes of the relevant identical input streams. ::: :::WorkflowBlockItem At the top of the inputs list, click the **Marked **drop-down menu. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Xb_Qvz7Ea_tV5k-YU9X4I_image.png" size="84" width="1040" height="274" position="center" showCaption="false"} The Create a Failover Group window opens: ::: :::WorkflowBlockItem ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/SStlNc8ZoM648Q2rgutxP_image.png" size="62" width="517" height="607" position="center" showCaption="false"} In the **Stream ID** field, type a new name for Failover Group. This name will appear in the list of Inputs. ::: :::WorkflowBlockItem In the **Max Outputs** field, type the number of desired concurrent outputs that can use the Failover Group. Default: Unlimited. ::: :::WorkflowBlockItem In the **Search Window** field, type the timeframe in which the system can search for the relevant packets in a matching stream. If there is a latency difference between the streams in the group, the Search Window value should be higher than the latency difference between the streams. ::: :::WorkflowBlockItem In the **Max Bitrate** field, specify the maximum bitrate of the stream. Default: 8000. This is used for internal memory allocation and will not affect the transmitted bitrate. Recommended: double the bitrate of the highest bitrate stream. ::: :::WorkflowBlockItem In the **Max Latency** field, specify the buffer size that Zixi Broadcaster will keep for error correction. For example, 6000 milliseconds would ensure that the stream is protected for six seconds of errors in the network. Default: 6000 ::: :::WorkflowBlockItem Under **Candidates**, if you want to configure one or more of the streams as back up, select the checkbox next to the relevant stream. Backup streams will be used only when all the "Primary" streams are down. ::: :::WorkflowBlockItem Configure additional parameters as required. ::: :::WorkflowBlockItem Click **OK** The Hitless Failover Group is added to the list of inputs, listing the sub-streams that are part of the group. The system will automatically detect the offset between the sub-streams and display it in milliseconds under Offset (ms). ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/QnCzXS5UGHU1RN_xPJWhH_image.png" size="80" width="1013" height="202" position="center" showCaption="false"} ::: :::: [title] Zixi Redundancy: Overview [path] Zixi Redundancy/ In order to protect against device, link connectivity, or software failures, Zixi supports a variety of high-availability topologies by deploying redundant components. Zixi products feature failover mechanisms that utilize alternative components in the event of failure as well as redundant external encoder or decoder configurations. ## Types of Redundancy ### Hitless Failover Zixi features hitless failover for inputs, enabling undisrupted streaming when switching from one source to another. The hitless failover feature is based on the SMPTE 2022-7 standard, which specifies “seamless” or hitless failover between binary-identical streams with synchronized RTP headers. Zixi's patent-pending hitless failover technology works by comparing the transport stream payload, without relying on sequences being synchronized. Zixi then applies a proprietary sequencing algorithm to identify missing parts and fill-in missing packets. The Hitless Failover feature is supported in the inputs of Zixi Broadcaster and ZEC. ### Hot Redundancy Hot redundancy, represented in the diagrams by a solid non-dashed arrow, involves two parallel active streams. This enables seamless failover transition between the two streams. It requires two live feeds, doubling the overall bandwidth. ### Warm Redundancy Warm redundancy, represented in the diagrams by a dashed arrow, involves a primary active stream and a secondary backup stream that is ready to become active in the event of primary failure. ### Cold Redundancy In a cold redundancy configuration, a secondary path is available in a dormant state, requiring a manual switch over to activate in the event of a primary failure. [title] Dual PUSH Transmission to Redundant Targets (Hot Redundancy) [path] Zixi Redundancy/Zixi Push Transmission Redundancy/ ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/VYfzdQ3nmLDNyaD9RFp3U_image.png) Zixi can be deployed to provide source and target redundancy. This topology includes two simultaneous streams delivered in parallel from two separate source nodes to a corresponding pair of redundant targets. If the latency of the outputs is identical, the streams will be frame synced, provided that the video is synced on entry. ## Source Configuration The following procedure describes how to configure two ZECs to push the same stream to two target hosts in a hot redundancy configuration. In order to configure a hot redundancy you will need to create an output in each of the ZECs. The procedure does not cover instructions on how to configure the Input into the ZEC. **To configure the first source node (e.g. ZEC):** 1. On the **Outputs** page of Zixi Feeder, click the **New Output** button, located in the upper- right end corner of the screen. 2. In the **Output** **Name** field, type a new name for the output. 3. In the **Type** field select **Push **radio button option. 4. In the** Input Name** field select the relevant the input stream. 5. In the **Stream ID** field, enter a stream ID (alphanumeric). The same Stream ID will be also configured in the target node (Push Input). 6. Optional - in the **Password** field, specify a string to be used at the destination to authenticate that the pushing Broadcaster is allowed to push this stream. 7. In the **Max Latency** field, specify the buffer size that Zixi Broadcaster will keep for error correction. For example, 6000 milliseconds would ensure that the stream is protected for six seconds of errors in the network. Default: 6000. 8. In the **Host** field, enter the host name or IP of the primary target. 9. In the **Port** field, specify the destination port to listen on for the Push stream (default: 2088). 10. In the **IP** field, select from the drop-down menu, the IP address of the NIC (Network Interface Card) in the Source through which the stream will be pushed. 11. Click **OK**. The output is added to the Outputs list. **To configure the second source node (e.g. ZEC):** - Repeat the steps above to configure the second source node, however in the **Host** field enter the host name or IP of the second target. - The stream in the second source can have the same Stream ID as the first source or a different Stream ID. ## Target Configuration The following procedures describe how to configure the two target Zixi Broadcasters in a hot redundancy configuration. The two targets can use the same Stream IDs or use different Stream IDs, as configured in the first and second sources. **To configure the first target node (e.g. Zixi Broadcaster):** 1. Click the **Inputs **tab at the top of the primary Zixi Broadcaster administrative screen 2. Click **New Input **on the upper right hand side of the screen. 3. Select the **Push **option. 4. Create an input at the primary target, ensuring the “Stream ID” matches that of the first source output. 5. Configure additional parameters as required. 6. Click **OK**. **To configure the second target node (e.g. Zixi Broadcaster):** 1. Click the **Inputs **tab at the top of the secondary Zixi Broadcaster administrative screen 2. Click **New Input **on the upper right hand side of the screen. 3. Select the **Push **option. 4. Create an input at the secondary target, ensuring the “Stream ID” matches that of the second source output. 5. Configure additional parameters as required. 6. Click **OK**. ## Cost Considerations This topology duplicates the hardware and software components of both the source and the target. The configuration also requires using double the up-link bandwidth. Allocation of twice the expected maximum bit-rate with head room is advised. ## Latency Considerations For detailed recovery time details, please contact your Zixi representative. [title] Dual PUSH Transmission to Single Target (Warm Redundancy) [path] Zixi Redundancy/Zixi Push Transmission Redundancy/ ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/SnBW3hddmRRYwjteZ3XE0_image.png) Multiple source nodes can be configured to PUSH to a single Zixi target Input. Provided that the streams from both source nodes include the same Stream ID, contention for the input is decided on a first-come first-served basis. If the primary source connection is lost, the target Input will automatically accept a new stream (coming from the secondary source). As a result, this topology provides source-side redundancy with automated fail-over to a second identical stream. ## Source Configuration The following procedure describes how to configure two ZECs to push a single stream to a target hosts in a warm redundancy configuration. The procedure does not cover instructions on how to configure the Input into the ZEC. **To configure the primary source node (e.g. ZEC):** 1. On the **Outputs** page of ZEC, click the **New Output** button, located in the upper- right end corner of the screen. 2. In the **Output** **Name** field, type a new name for the output. 3. In the **Type** field, select **Push **radio button option. 4. In the **Input Stream** field, select the relevant input stream. 5. In the **Stream ID** field, enter a stream ID (alphanumeric). The same Stream ID will be also configured in the target node (Push Input). 6. Optional - in the **Password** field, specify a string to be used at the destination to authenticate that the pushing Broadcaster is allowed to push this stream. 7. In the **Max Latency** field, specify the buffer size that Zixi Broadcaster will keep for error correction. For example, 6000 milliseconds would ensure that the stream is protected for six seconds of errors in the network. Default: 6000. 8. In the **Host** field, enter the host name or IP of the primary target. 9. In the **Port** field, specify the destination port to listen on for the Push stream (default: 2088). 10. In the **IP** field, select from the drop-down menu, the IP address of the NIC (Network Interface Card) in the Source through which the stream will be pushed. 11. Click **OK**. The output is added to the Outputs list. **To configure the secondary source node repeat the same steps.** ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/JrpVtaSYdQlEKt8Myv68q_image.png) ## Target Configuration The following procedures describe how to configure the target Zixi Broadcaster in a warm redundancy configuration. The target is configured with a single input. If this input is unavailable the secondary input will be received. The input must use the same Stream ID that was used to configure the primary and secondary source nodes (ZECs). **To configure the target node (e.g. Zixi Broadcaster):** 1. Click the **Inputs **tab at the top of the secondary Zixi Broadcaster administrative screen 2. Click **New Input **on the upper right hand side of the screen. 3. In the **Stream ID** field, enter the same “Stream ID” as the source outputs. 4. Select the **Push **option. 5. Configure additional parameters as required. 6. Click **OK**. ## Cost Considerations This topology duplicates the source side Zixi node software and hardware components. It does not require doubling the up-link bandwidth, as the backup connection stream is only active in the event that the primary stream fails. ## Latency Considerations For detailed recovery time details, please contact your Zixi representative. [title] Hitless Failover Configuration [path] Zixi Redundancy/ ::Image[]{src="https://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/tgKjbLJKHFEIP-MscWY_I-20260116-161144.png" size="90" width="920" height="445" position="center" alt="hitless failover configuration" darkWidth="920" darkHeight="445" showCaption="false"} The hitless failover configuration involves grouping two inputs in a "Failover Group". If the two inputs are identical (i.e. two or more binary-identical streams with synchronized RTP headers), when one of them is disrupted or interrupted completely, Zixi Broadcaster will seamlessly use the packets of the other input without any disruptions. :::hint{type="info"} Note: - If the streams are not identical, the failover process will not be seamless and may take up to a second. - The **Inject Metadata **option for inputs/sources, though useful in other ways, will make the streams non-indentical and prevent seamless failover ::: A Failover Group can comprise two or more inputs. In a group of three or more, you can define one or more streams as a "Backup". In this case the system will always try to recover packets from "Primary" streams first and only if there are no available primary streams, it will use the backup streams. When one of the primary streams becomes available, the system will automatically jump to the primary stream. While the Broadcaster GUI only enables configuration of primary streams at a single priority level, through the Zixi Broadcaster API it is possible to assign different priorities as follows: - Priority 0 – means backup. It will be used only if all other streams are unavailable. - Priority greater than 0 - means primary. :::hint{type="info"} Failover between streams that have different priorities, even primary streams, will not be seamless and may take up to a second. ::: The Failover Group has its own Stream ID, just like an Input Stream, and will appear in the Inputs list. Although the topology above shows only one Zixi Broadcaster, it is also possible to have multiple targets (e.g. two or more Zixi Broadcasters), each with its own Failover Group of inputs to enable a more complete system-level redundancy. [space] Quick Start (/quick-start) [title] Using Zixi Documentation [path] / Before we get into the Quick Starts for ZEN Master and Broadcaster, here are a few tips on getting around in this documentation site and getting answers to your questions. ## Site Navigation Zixi documentation is divided into several major sections that appear in the site navigation on the left: ![Site Navigation](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/koqoJtnENTzRirG0G8gYQ_left-side-site-navigation.png) :::hint{type="info"} Note that on narrower displays, the site navigation may not appear automatically, but you can still access by clicking the icon in the upper-left corner: ![To Open the Site Navigation](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/SYtvXC-X2VswBYpOHL5Gb_click-to-open-global-navigation2.png) ::: ### The Major Sections Here is a brief description of what you'll find in the major sections: - **Zixi Documentation Home** - the home page, but also release notes for Broadcaster and ZEN Master, as well as a page that shows recent additions and updates to the documentation - **Quick Start **- the section you are in now, which also includes instructions for getting started quickly with ZEN Master and Broadcaster - **Product Features **- high-level overviews of some key Zixi features, such as Redundancy, Error Correction, working with TAMS, and so forth - **Broadcaster vXX Current Version** - documentation for the current version of Broadcaster and ZEC (when you go to that section, you will also find links to documentation for previous but still supported versions) - **ZEN Master **- documentation for ZEN Master - **ZaaS** - a one-page explanation of Zixi-as-a-Service, which is ZEN Master used with Broadcasters that Zixi sets up and maintains in the cloud for you - **Market Switching** - covers Zixi's tools for inserting SCTE messages into streams for purposes such as creating pre-rolls or ad breaks, providing regionalized content to different receivers, and switching to different content in situations where content is blacked out in particular areas for regulatory or contractual reasons. - **How To Guides** - Guides for cross-product things like security, related apps like VLC, OBS, and Wirecast, Zixi's OnAir Pro mobile app, etc. - **ZEN Master API** - **Not** the API Reference, which is found on the [Customer Portal](https://portal.zixi.com), but guides to some common basic API tasks, as well as configuring API Keys, setting up the API in Postman, and such - **Troubleshooting** - despite Zixi's elaborate array of tools to ensure that your video streams get to their destinations intact and on time, things happen. This section contains troubleshooting guides to help you fix or mitigate issues when they arise - **Customer Portal **- a guide to the portal where you can download Zixi software, get licenses, find additional documentation, and more ### Navigating the Sections When you click on any of the main sections, the section navigation will open up below the links to the main sections: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/KaN9QDxPYQXM46dvgrbyX_opening-section-navigation.png" size="40" isUploading="false" position="center" width="652" height="1254" darkWidth="652" darkHeight="1254" alt="Section Navigation" showCaption="false"} When you click on one of the subsections of the main section, it will expand to reveal links to the documents and subsections it contains: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/AVnxujBCly4NPunD1EJUU_drilling-down.png" size="40" isUploading="false" position="center" width="546" height="986" darkWidth="546" darkHeight="986" alt="Drilling Down into Subsections" showCaption="false"} :::hint{type="info"} Note that an arrow to the right of a link (as shown in the image above) indicates that there are additional documents and/or subsections contained in it. These will open up when you click the link. ::: ## Searching and Asking AI At the top of every page is a search bar, and beside it a button to Ask AI: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/KK4YEvXT72t5Jm_Db4hxK_search-and-ask-ai2.png) **Search**, like most search engines, will return a list relevant documents, with brief text highlighting where the search terms appear: ![Search Results](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/UGH4pEozwqWNG-wTV82gZ_search-results.png) :::hint{type="info"} Note that if you would rather see the AI response, you can click **Ask AI** in the search results. ::: **** **Ask AI**, on the other hand, provides a summary of the topic you searched on based on what it found within all the documents: ![Ask AI Response](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/JXLmc0hLE0tJCfh47Vmfe_ai-assistant-response.png) :::hint{type="info"} Note that you can click the icon highlighted in the image above to see a list of the documents that AI used to generate its summary. ::: ### Which Should I Use? If you are already fairly familiar with Zixi's documentation and simply want to get back to a document you know to check on a detail, **search** can be very effective. On the other hand, if you are looking for answer to a question, we recommend trying **Ask AI** instead. Here's why: Zixi provides many features that can be used across a variety of Broadcaster Inputs, Adaptive Groups, and Outputs, or ZEN Master Sources, Channels, and Targets. If you go to a document on adding a specific item, you will find a brief explanation of all the available fields. However, if you are trying to understand what the feature does, and in what cases you would want to use it, there are often higher-level documents with deeper explanations of features and how they work together. The AI summaries are often more effective in leading you to the high-level explanations. :::hint{type="info"} Also remember that AI responses are generally more useful when you ask questions, providing context for what you are trying to figure out, rather than just providing search terms. For example (referring to the images above), instead of prompting AI with "FEC", try asking something like "What is FEC, and how does it work with other mechanisms to fix errors in transmitting video streams? Do I just need one, or do they work together?" ::: [title] Step 2: Create a Broadcaster Cluster [path] Quick Start: ZEN Master/ :::hint{type="info"} **Note**: If you have already created a Broadcaster Cluster in ZEN Master, skip this step and proceed to the next one. ::: A Broadcaster Cluster is the logical grouping of one or more Broadcaster instances that ZEN Master uses to manage ingest and processing. You must create a cluster before you can register individual Broadcasters or configure Sources and Channels. ::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Broadcasters**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Swp1oDFUSeEbey_bWZ8xY_image.png" size="28" width="446" height="692" position="center" alt="ZEN Master Navigation" showCaption="false"} ::: :::WorkflowBlockItem Click **+ Add**. The Create New Broadcaster Cluster screen is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Lro9soadQEQtcmlRnva4Z_image.png" size="56" width="944" height="230" position="center" alt="Add Button" showCaption="false"} ![Create New Cluster](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/tB910g26TJvVmOS8qe1dU-20260414-143633.png) ::: :::WorkflowBlockItem In the **Name** field, enter a logical name for the Cluster. ![Cluster Name](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/qgIetQteXMDrBtXs_06ba-20260414-144023.png) ::: :::WorkflowBlockItem Select the **default** tag (or any other if you have created additional tags) from the **Tags** dropdown selector. ::: :::WorkflowBlockItem The required **DNS Prefix** will be automatically populated with a URL-encoded version of the Name you entered in step 3. ::: :::WorkflowBlockItem Ensure that the **Management Type** is *Manual:* ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/qF5mwfObSc4vmtvmw8xpi-20260414-151022.png) ::: :::WorkflowBlockItem For this exercise, you don't need to change any other fields, so click **Save** to create the cluster. The cluster details will be displayed: ![Cluster Details](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/B6MTlfVl5A_zO2XcPcloI-20260414-151339.png) ::: :::: [title] Step 4: Add a Broadcaster to the Cluster [path] Quick Start: ZEN Master/ :::hint{type="info"} **Note:** If you have already registered a Broadcaster in a cluster, you can skip Steps 4 and 5. ::: When the Cluster exists, you register individual Broadcaster instances within it. This is the first step. Once completed, we'll configure the SSH connection in the Broadcaster UI to complete the registration. :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Broadcasters**. ::: :::WorkflowBlockItem From the list of Broadcaster Clusters, select the Cluster you created in Step 2. The Cluster details are displayed on the right. ![Cluster Details](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/B6MTlfVl5A_zO2XcPcloI-20260414-151339.png) ::: :::WorkflowBlockItem In the **Broadcasters** section, click **+ Add Broadcaster**. The Create New Broadcaster window is displayed. ![Create New Broadcaster](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/YL8DvodMxkoS3GJCsf0ou-20260414-175444.png) ::: :::WorkflowBlockItem In the **Name** field, enter a logical name for this Broadcaster instance. ::: :::WorkflowBlockItem In the **API User** field, enter **admin**. ::: ::::WorkflowBlockItem In the **API Password** field, enter the admin password for logging into the Broadcaster. These credentials allow ZEN Master to access the Broadcaster API. :::hint{type="info"} Remember that the default password is `1234`. For security reasons, Zixi recommends changing the password in the Broadcaster UI Settings before you register it in ZEN Master. If you have changed it, enter the **new password **here. ::: :::: :::WorkflowBlockItem Select an **SSH Key** from the dropdown, either the one you created in Step 3, or one you created earlier. ::: :::WorkflowBlockItem For the **Broadcaster Type**, leave it as **Primary** (the default). ::: :::WorkflowBlockItem Click **Save**. ::: ::::: :::hint{type="info"} Remember: The Broadcaster is set up now, but not connected to ZEN Master. In the next step, we will configure the SSH connection in the Broadcaster UI to make the connection. ::: [title] Step 6: Register ZEC in ZEN Master [path] Quick Start: ZEN Master/ :::hint{type="info"} Note: If you are not using a ZEC on a separate system for this exercise, or if you have already set up your ZEC in ZEN Master, you can skip Steps 6 and 7. ::: If you are using a ZEC on a separate system as your target, register it in ZEN Master now before configuring the workflow. Unlike Broadcasters, ZECs are registered directly as individual edge devices and do not belong to a Cluster. :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Zixi Edge Devices**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/1vPO6z3_RhQjuz1S_eBbA-20260415-185226.png" size="56" width="974" height="1004" position="center" alt="Zixi Edge Devices" showCaption="false"} ::: :::WorkflowBlockItem Click **+ Add**, then click **ZEC**. The Create New ZEC screen is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/MCkY-K9_fG7xbSs2VNzNp-20260415-185446.png" size="88" width="1470" height="1732" position="center" alt="Create New ZEC" showCaption="false"} ::: :::WorkflowBlockItem In the **Name** field, enter a logical name for the ZEC. ::: :::WorkflowBlockItem In the **API User** field, enter admin (default). ::: ::::WorkflowBlockItem In the **API Password** field, enter the ZEC's admin password (default: `1234`). :::hint{type="info"} For security reasons, we recommend changing the default admin password in the ZEC UI before registering it in ZEN Master. If you have changed the password, enter the updated password here. ::: :::: :::WorkflowBlockItem In the **SSH Key** field, select the SSH key you created in Step 3. ::: :::WorkflowBlockItem Click **Save**. ::: ::::: The ZEC will display a **Pending **status until you complete the connection from the ZEC UI in Step 7. [title] Step 8: Create a Source [path] Quick Start: ZEN Master/ Sources are the input streams managed in ZEN Master. A Source can originate from any of the following: - ZEC - Broadcaster - An external source, such as an external encoder or an external ZEC not configured in ZEN Master - AWS MediaConnect Flow In this example, we will create a Source from a transport stream file sitting on a public URL. ::::WorkflowBlock :::WorkflowBlockItem Click **Sources** in the main ZEN Master navigation, and then click **+ Add**. ![Sources](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Tog-D3wEIQGmJzjwxEqJY-20260416-143158.png) ::: :::WorkflowBlockItem From the Source type options, select **File**: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/gBEDE-sRraZxqqIlEDgh4-20260416-164059.png" size="90" width="1350" height="1638" position="center" alt="Create New Source" showCaption="false"} ::: :::WorkflowBlockItem The **Create New File Source** screen appears: ![Create New File Source](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/8JuZplsAxRbHqpBMWqDpM-20260416-164207.png) ::: :::WorkflowBlockItem Enter a **Name** for your Source. ::: :::WorkflowBlockItem Select the *default* or some other tag from the **Tags** dropdown. ::: :::WorkflowBlockItem In the **Broadcaster** dropdown, select your Broadcaster. ::: :::WorkflowBlockItem For **Source**, select **URL**. ::: :::WorkflowBlockItem In the **URL** field, enter: [https://zixi-file-sources.s3.us-east-1.amazonaws.com/ts/clock\_AVC\_420\_8bit\_480p30.ts](https://zixi-file-sources.s3.us-east-1.amazonaws.com/ts/clock_AVC_420_8bit_480p30.ts) ::: :::WorkflowBlockItem Under **Public Output**, check **Allow**. ::: :::WorkflowBlockItem You don't need to change any other fields for this exercise, so click **Save**. ::: :::WorkflowBlockItem The **Source** details screen will open, and after a few seconds, you should see a thumbnail view of the stream, and after a minute or two, detailed Stream Information: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/n3kEZznBxyujVtCVpyE1S-20260416-165629.png" size="80" width="1250" height="2088" position="center" alt="Source Details" showCaption="false"} ::: :::: :::hint{type="info"} Note: You may see a Content Analysis warning or error about clipped audio. You can ignore this. ::: [title] Step 9: Create a Channel [path] Quick Start: ZEN Master/ Channels are essentially connectors between Sources and Targets. They allow for various processing of the source stream, including transcoding. In this exercise, we will create a simple Pass-Through channel, which passes the stream to its Target. ::::WorkflowBlock :::WorkflowBlockItem In the main ZEN Master navigation, select **Channels** and then click **+ Add**. ![Channels](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/PKIQFbOhRq1JS3rwgkCcP-20260416-173923.png) ::: :::WorkflowBlockItem In the **Create New Channel** screen that opens, select **Pass-Through.** ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/cK5VAULRYmBjx3JVJqGHE-20260416-174118.png" size="90" width="1352" height="1054" position="center" alt="Select Channel Type" showCaption="false"} ::: :::WorkflowBlockItem Enter a **Name** for your Channel. ::: :::WorkflowBlockItem Select *default* or some other tag from the **Tags** dropdown. ::: :::WorkflowBlockItem Select your Broadcaster Cluster from the **Processing Cluster** dropdown. ::: :::WorkflowBlockItem Select your Broadcaster from the **Target Broadcaster/s** dropdown. ::: :::WorkflowBlockItem Select the Source you created in Step 8 in the **Sources** selector. ::: :::WorkflowBlockItem You don't need to change any other fields, so click **Save**. ::: :::WorkflowBlockItem The **Channel Details** will appear, showing your Broadcaster and Source: ![Channel Details](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/RJrOlI8hsiYxARqxiRdyn-20260416-175518.png) ::: :::: :::hint{type="info"} Note: You may see a Content Analysis warning or error about clipped audio. You can ignore this. ::: [title] Step 3: Create an SSH Key [path] Quick Start: ZEN Master/ :::hint{type="info"} **Note**: If you have already created an SSH Key in ZEN Master, you can skip this step. ::: ZEN Master uses SSH keys to access the web UI of connected Zixi resources, such as Broadcasters. **You must have at least one SSH key configured before you can add a Broadcaster to a Cluster (which is the next step).** There are two methods for generating SSH keys: - **Generate in ZEN Master** (simplest) — ZEN Master generates the key pair; you download the private key and load it onto the Broadcaster. - **Import from the external device** (most secure) — You generate the key on the Broadcaster and import the public key into ZEN Master. To generate a new SSH key in ZEN Master: ::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Configuration > SSH Security & Keys**. The SSH Security & Keys screen is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/mgnY7uz3K_jz8OSRiMF3A-20260414-171555.png" size="74" width="1198" height="1402" position="center" alt="SSH Security & Keys" showCaption="false"} ::: :::WorkflowBlockItem Click **+ Add**. The Create New SSH Key screen appears. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/UD2uOq0far4278fNT4hU4-20260414-171709.png" size="82" width="1468" height="1074" position="center" alt="Create SSH Key" showCaption="false"} ::: :::WorkflowBlockItem In the **Name** field, enter a name for the key. ::: :::WorkflowBlockItem In the **Tags **field, select *default* or another tag to control which users have access to this key. ::: :::WorkflowBlockItem Under **SSH Key**, select **Generate**: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/GdUlG7AC11VtFBZnXi4OF-20260414-173611.png" size="84" width="1488" height="312" position="center" alt="Generate SSH Key" showCaption="false"} ::: :::WorkflowBlockItem Click **Save**. ::: :::: [title] Step 7: Connect the ZEC (ZEC UI) [path] Quick Start: ZEN Master/ As with the Broadcaster, you now need to complete the ZEC connection from the ZEC UI by configuring the SSH tunnel back to ZEN Master. **Keep both ZEN Master and the ZEC UI open in separate browser tabs**. ::::WorkflowBlock :::WorkflowBlockItem In ZEN Master, in the main navigation, click **Zixi Edge Devices**. ::: :::WorkflowBlockItem Click on the **ZEC** you added in Step 6. ::: :::WorkflowBlockItem As with the Broadcaster, click the ⋮ icon in the upper-right corner of the details panel and select **Config **to open a panel with instructions for setting up the connection in the ZEC UI **Settings**. Keep this panel open and follow the steps while you work in the ZEC UI. ::: :::WorkflowBlockItem In a separate tab, if the ZEC is running locally, navigate to `http://localhost:4444`or `http://127.0.0.1:4444` ; if remote, navigate to `http://:4444`. ::: :::WorkflowBlockItem Go to Settings, and click on **SSH Connections.** Follow the instructions in the Configuration panel in ZEN Master. ::: :::WorkflowBlockItem Follow the instructions in the Configuration panel in ZEN Master. When the setup is complete, the ZEC status in ZEN Master will change to **OK**. ::: :::: [title] Step 7: Creating a UDP Output on Zixi Broadcaster/ZEC [path] Quick Start: Broadcaster and ZEC/ Zixi Broadcaster and ZEC can output streams to various types of targets. The stream can be sent as unicast or multicast. It can also be stored as a file or transmitted as an IP-MPEG-TS stream. You can include multiple sources in your Output for high-availability. *For this tutorial we will send the stream to another Broadcaster/ZEC.* **To Create a UDP Output on Broadcaster/ZEC:** :::::WorkflowBlock :::WorkflowBlockItem In the Zixi Broadcaster/ZEC UI, in the Main Navigation, click **Outputs**. The Outputs page opens. ::: :::WorkflowBlockItem On the **Outputs** page, click the **+New Output** button in the Menu bar. ![New Output Button](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-ZSIcgAFJeSNzbThbpMrrD-20250614-195943.png) ::: :::WorkflowBlockItem The **New Output** screen is displayed. ![New Output screen](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-7OE0cUBV5vsXvOosMx6i4-20250614-200147.png) ::: :::WorkflowBlockItem In the Input type section, verify that **UDP** is selected (default). ::: :::WorkflowBlockItem In the **Name** field, enter a unique name to refer to this Output, e.g. *SampleTSFile/UDPOutput01*. ::: :::WorkflowBlockItem In the **Input Stream** field, select from the dropdown list the Input that you created to pull the stream from the Broadcaster. ::: :::WorkflowBlockItem In the **Host** field, enter the hostname or IP of the Broadcaster/ZEC you want to send the UDP stream to. ::: :::WorkflowBlockItem In the **Port** field, enter the port on your IRD that will receive the stream. ::: ::::WorkflowBlockItem In the **NIC** field, verify that *Any* is selected (default). :::hint{type="info"} To learn about additional configuration options, see [Adding UDP Outputs](docId\:VeW0Wh-eDBjRUcBaBSoaI). ::: :::: :::WorkflowBlockItem Click **OK**. The new Output is added to the Zixi Receiver and now appears on the **Outputs **screen. The status indicators for the Output should be green (Connected). ![Output Connected](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-woNOUrdK9sQDvTYgERhl3-20250615-155459.png) ::: ::::: Congratulations! You have successfully sent the stream from your TS file through the Zixi system and delivered it to another Broadcaster/ZEC. The following sections explain how to start and stop your stream and how to view the content of the stream. [title] Quick Start: Broadcaster and ZEC [path] / This quick start guide demonstrates a basic use case for transmitting a video file throughout Zixi Software components. In this example, an MPEG-TS file is streamed from a Zixi Edge Compute (ZEC) feeder to a Zixi Broadcaster and on to a ZEC receiver without applying any additional processing or advanced configuration options. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/i4ySSZ6O8f1YI8qwkNMBt_image.png) As part of the configuration of the components, you will use the following inputs/outputs types: - ZEC (Feeder) - Input: File - Output: Push - Zixi Broadcaster - Input: Push - Output: Pull - ZEC (Receiver) - Input: Pull - Output: UDP ### Contents of the Quick Start - [Prerequisites](docId\:tmGrz4u_MKCTuz3INy6L9) - [Step 1: Logging in to Zixi Resources](docId\:er8Z8JDrnroVvNjKIWKDB) - [Step 2: Creating a File Input on ZEC/Broadcaster](docId\:WfjJsEqkXo9j3HbLnXaPI) - [Step 3: Creating a Push Output in ZEC/Broadcaster](docId\:InuywLLm8SGo2xqxJh7J4) - [Step 4: Creating a Push Input on Zixi Broadcaster](docId\:Bj1WG6Olt4Gnw6nJMvH6_) - [Step 5: Creating a Pull Output on Zixi Broadcaster](docId\:DtlduATXsDvf1O0jK3cGy) - [Step 6: Creating a Pull Input on ZEC/Broadcaster](docId\:CDcxQDsF4GONxUu1rzD6V) - [Step 7: Creating a UDP Output on Zixi Broadcaster/ZEC](docId\:vPQ1nA2gxS3DeT_Uq4eMu) [title] Quick Start: ZEN Master [path] / ## Introduction This guide walks you through setting up an end-to-end live video stream using **ZEN Master** as your control plane. You will configure a Source (where the stream originates), a Channel (how it is routed), and a Target (where it is delivered) — entirely from the ZEN Master interface. If you are working without ZEN Master and configuring Broadcaster and ZEC directly, see the Quick Start - Broadcaster. ## Prerequisites Before starting, ensure you have the following in place: - **ZEN Master access** — You have a ZEN Master account and can log in. If you do not have access, contact your Zixi account manager. - **A Zixi Broadcaster instance** — installed, running, and connected to the internet. Broadcaster software and licenses are available to Zixi customers via the Zixi Customer Portal. - **A ZEC instance on a separate system** (recommended) — For the most realistic scenario, a ZEC installed on a separate system will serve as the target for the stream. This guide includes instructions for adding the ZEC to ZEN Master. If a separate system is not available, the Broadcaster can also be used as the target — this is not a realistic production scenario, but it allows you to complete the full workflow and become familiar with all the essential ZEN Master components. ZEC software can be downloaded from the Zixi Customer Portal by anyone, and license keys can be self-generated at no cost. - **A source stream** — We will use a sample MPEG-TS file hosted at a public URL, provided in Step 6 below. No additional setup is required. ## Overview of the Workflow In ZEN Master, an end-to-end stream is built from these steps: | **Step** | **What it does** | **Where** | | -------------------------------------------------------------------------------- | ----------------------------------------------------------- | -------------------------------------------------------- | | [Step 1: Login to ZEN Master](docId:1_GftIfM1VvuEmDjnM1wD) | Access ZEN Master | — | | [Step 2: Create a Broadcaster Cluster](docId\:H5WEZYHIdYMs9cFxsM9pB) | Groups one or more Broadcasters as a managed resource | **Broadcasters** → + Add | | [Step 3: Create an SSH Key](docId\:RHlJL-2F__umZT-SQkz3T) | Enables ZEN Master to access Broadcaster and ZEC resources | **Configuration** → SSH **Security & Keys **→ + Add | | [Step 4: Add a Broadcaster to the Cluster](docId\:o5nF_lb33zvrhMEFn-cxk) | Registers an individual Broadcaster instance in the Cluster | **Broadcasters** → select Cluster → + Add Broadcaster | | [Step 5: Connect the Broadcaster (Broadcaster UI)](docId:3tiP0Jyyr_7BnaobJhVIv) | Completes the SSH tunnel setup from the Broadcaster UI | **Broadcaster UI** → Settings → SSH Connections | | [Step 6: Register ZEC in ZEN Master](docId\:n1AdWX4tWkudr--Nr4mOw) | Registers the ZEC as an edge device in ZEN Master | **Zixi Edge Devices** → + Add → ZEC | | [Step 7: Connect the ZEC (ZEC UI)](docId:8LFOrJc3WAUHCwsBrvZXE) | Completes the SSH tunnel setup from the ZEC UI | **ZEC UI **→ Settings → SSH Connections | | [Step 8: Create a Source](docId\:uprZdOrLmAZsoOj_xxQ9P) | Defines where the stream originates | **Sources** → + Add | | [Step 9: Create a Channel](docId\:EHsalbua75N7YKcZADwNx) | Defines how the stream is routed | **Channels** → + Add | | [Step 10: Create a Target](docId\:jfTyLKl5I2vmCulvDP39G) | Defines where the stream is delivered | **Targets** → + Add | [title] Step 6: Creating a Pull Input on ZEC/Broadcaster [path] Quick Start: Broadcaster and ZEC/ ZEC/Broadcaster can receive streams from a variety of different sources such as Zixi Broadcasters, TS files etc. ZEC/Broadcaster can then transmit the stream to downstream targets such as Zixi enabled IRDs. While configuring an Input in ZEC/Broadcaster you can customize the stream configuration. *For this tutorial we will configure ZEC/Broadcaster to Pull your sample stream from your Zixi Broadcaster using Zixi Protocol using the default configuration.* **To Add a Pull Input to your Zixi ZEC/Broadcaster :** :::::WorkflowBlock :::WorkflowBlockItem In the ZEC/Broadcaster UI, in the Main Navigation, click **Inputs**. The Inputs page opens. ::: :::WorkflowBlockItem On the **Outputs** page, click the **+New Input** button in the Menu bar. ![New Input Button](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/bsgB81ai9JCZQjX6VLi5h_input.png) ::: :::WorkflowBlockItem The **Stream details **screen is displayed. ![Stream Detail](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/oCAkhJCpsMSPeapuOX350_image.png) ::: :::WorkflowBlockItem In the **Stream ID** field, enter a unique identifier for this stream in ZEC/Broadcaster, e.g. *SampleTSFileReceiverInput01*. ::: :::WorkflowBlockItem In the Input type section, verify that **Pull** is selected for the Input stream (default). ::: :::WorkflowBlockItem In the **Remote** **Host** field, enter the hostname or IP address of the Broadcaster from which the stream is being “pulled”. ::: :::WorkflowBlockItem Verify that the **Port** field is set as 2077 (default for pull). ::: ::::WorkflowBlockItem In the **Remote Stream ID** field, enter the precise Stream ID (case sensitive) that you assigned to the **Output** that you created on the Broadcaster in Step 5, e.g. *SampleTSStream01*. :::hint{type="info"} To learn about additional configuration options, see [Adding Pull Streams](docId\:rJL8u4EAmTpF7ZVED99i2) in the Zixi ZEC/Broadcaster UG. ::: :::: :::WorkflowBlockItem Click **OK**. The “Input added” message appears on the top of the screen. The Pull Stream is added to the ZEC/Broadcaster and is now displayed in the list of Input streams available. The Status should be Online (green). ![Input Status](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/INFt5Xv8tlACmP-DytaH6_image.png) ::: ::::: In the Zixi Broadcaster UI, on the **Outputs** page, the **Status** of this Output should now be Connected (green). ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/oamHoW_UAftAhGMFZAeJj_image.png" size="68" width="551" height="84" position="center" alt="Output Status" showCaption="false"} [title] Starting and Stopping Zixi Streams [path] / Once a stream is created from a TS file it automatically begins streaming. You can stop the streaming at any stage along the flow (i.e. on the Broadcaster or ZEC) either as an Input or an Output. From whatever point the streaming was stopped onward, the stream will be unavailable. You can resume the streaming at any time. ### To stop streaming: ::::WorkflowBlock :::WorkflowBlockItem In the UI of the resource on which you want to stop the stream (Broadcaster or ZEC), go to the **Inputs** or **Outputs** page as desired. ::: :::WorkflowBlockItem Select the desired stream and click on the Actions button. ::: :::WorkflowBlockItem Click **Stop**. ![Stop Stream](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-uIluImlr-Xn_hvelyDwoy-20250613-164407.png) The stream is stopped. ::: :::: ### To start a stream: ::::WorkflowBlock :::WorkflowBlockItem In the UI of the resource on which you want to start the stream (Broadcaster or ZEC), go to the Inputs or Outputs page as desired. ::: :::WorkflowBlockItem Select the desired stream and click on the Actions button. ::: :::WorkflowBlockItem Click **Start**. ![Start Stream](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-MekGQlx-s5HukhJJWzmsY-20250613-164600.png) The stream resumes streaming. ::: :::: [title] Step 1: Logging in to Zixi Resources [path] Quick Start: Broadcaster and ZEC/ First, you need to log in to all of your resources so that you will be able to access each of them as needed during the tutorial. ZEC and Broadcaster are the same software in functionality but your license determines what features & functions it has available for use. ## Logging in to ZEC/Broadcaster: **To log in to ZEC/Broadcaster:** :::::WorkflowBlock :::WorkflowBlockItem In your web browser, navigate to [http://localhost:4444](http://localhost:4400) A user authentication window opens. ::: :::WorkflowBlockItem In the **User Name** field, enter ‘**admin**’ ::: ::::WorkflowBlockItem In the **Password** field, enter ‘**1234**’. :::hint{type="info"} Note: 1234 is the default password. For security reasons, we strongly recommend that you change it to a more secure password. ::: :::: :::WorkflowBlockItem Click **OK**. The Broadcaster UI opens on the **Status** page. ::: :::WorkflowBlockItem If you have not already activated the license, click the "Options" dropdown and select **Activate License, **and enter the license number in the dialog that appears. ![Options Menu](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/6s9n1q5z5qiWjzirTqQMT_image.png) ::: ::::: [title] Step 10: Create a Target [path] Quick Start: ZEN Master/ A Target defines where a Source is delivered to (via a Channel). It might be the final destination or a transfer point for additional processing or distribution to multiple destinations. The Target type is largely determined by what will be on the receiving side and what kind of stream it expects (for example, some broadcast receivers need a constant bitrate (CBR) stream, while others can handle variable bitrate (VBR) streams). In this case, we are going to create a Zixi Pull Target to allow the ZEC you set up to pull the stream, or if you don't have a ZEC in place, use your Broadcaster (not a very realistic scenario, but it will serve here to give you the experience of creating the full Source to Channel to Target workflow). ::::WorkflowBlock :::WorkflowBlockItem In the ZEN Master main navigation, click **Targets** and then **+ Add:** ![Targets](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/E8NDWskwWQwQwp4h4-Yn6-20260417-142637.png) ::: :::WorkflowBlockItem The **Select Target Type** screen opens; select the **Zixi** type: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Z-r2qDxbgmZpcbSiM2dWs-20260417-142756.png" size="84" width="1326" height="2132" position="center" alt="Target Type" showCaption="false"} ::: :::WorkflowBlockItem The **Create New Zixi Target** screen opens: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/AkzNFdlXm0Au_cFKmD9og-20260417-143216.png" size="90" width="1502" height="3532" position="center" alt="Create Zixi Target" showCaption="false"} ::: :::WorkflowBlockItem Enter a **Name** for the Target. ::: :::WorkflowBlockItem Select *default* or some other tag from the **Tags** dropdown. ::: :::WorkflowBlockItem Set the **Type** to **Pull**. ::: :::WorkflowBlockItem Set the **Mode** to **Single**. ::: :::WorkflowBlockItem Set the **Channel Type** to **ZEN Master Channel**. ::: :::WorkflowBlockItem Select the Channel you created in Step 9 from the Channel dropdown. ::: :::WorkflowBlockItem Leave the **Source Preference** as **Any **(you can select the Source you created, but there is no need to since the Channel contains only one Source). ::: :::WorkflowBlockItem Set the **Device** to **ZEC** (or Broadcaster, if you are not using a ZEC). ::: :::WorkflowBlockItem Select your **ZEC** from the **ZEC** dropdown (or your Broadcaster from the Broadcaster dropdown). ::: :::WorkflowBlockItem You do not need to change any other settings, so click **Save**. The **Target Details** will be shown. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/yNUxuZOv49eBgd9fSPvjS-20260417-144817.png" size="80" width="1550" height="1846" position="center" showCaption="false"} ::: :::: [title] Step 5: Creating a Pull Output on Zixi Broadcaster [path] Quick Start: Broadcaster and ZEC/ Zixi Broadcaster can send Outputs to a variety of targets such as ZEC acting as a Receiver or Zixi enabled IRDs. The Outputs can be sent through “push” or “pull” interactions and can be delivered using a wide range of protocols. While configuring an Output in Broadcaster you can customize the stream configuration. *For this tutorial we will send a Pull Output from the Broadcaster to a ZEC using Zixi Protocol. In this case, the stream is available on the Broadcaster waiting for the ZEC to initiate the “Pull” of the stream. For this tutorial we will use the default settings.* :::hint{type="info"} The following procedure describes how to manually create a Pull Output on the Broadcaster. You can configure your Broadcaster to automatically allow Pull Outputs. Once this feature is enabled, when you create a "Pull" Output on your ZEC, the corresponding Pull Output is automatically created on the Broadcaster. To enable automatic Pull Outputs, see [Authorization](docId\:op1GiGovcUfEyffJHwYMP) in the [Zixi Broadcaster User Guide](docId\:JGwIXYN936aeZmonZLERn). ::: [title] Step 5: Connect the Broadcaster (Broadcaster UI) [path] Quick Start: ZEN Master/ :::hint{type="info"} Note: If you have already fully registered your Broadcaster in ZEN Master, you can skip this step and proceed to the next one. ::: After saving the Broadcaster in ZEN Master, its status will show as **Pending**. You now need to complete the connection from the Broadcaster UI by configuring the SSH tunnel back to ZEN Master. You will be working in both ZEN Master and the Broadcaster UI simultaneously, *so it is helpful to keep both open in separate browser tabs*. ::::WorkflowBlock :::WorkflowBlockItem In ZEN Master, in the main navigation, click **Broadcasters** and open the **Broadcasters** tab. ::: :::WorkflowBlockItem Click on the Broadcaster you set up in the previous step with **Pending** status to reveal its details. ::: :::WorkflowBlockItem Click the ⋮ icon in the upper-right corner of the details panel and select **Config**. ZEN Master displays step-by-step configuration instructions for this Broadcaster — including values to copy and paste into the Broadcaster UI, and a button to download the SSH certificate you will need. ![Get Broadcaster Config](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/_Hret21frGY1W3bzyQbEJ-20260414-183653.png) ![Broadcaster Configuration Instructions](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/sOd6pQM76kqipD9t6KXrT-20260414-183904.png) ::: :::WorkflowBlockItem **In a new browser tab**, open the Broadcaster UI. If the Broadcaster is running locally, navigate to `http://localhost:4444` or `http://127.0.0.1:4444`; if remote, navigate to `http://:4444`. ::: :::WorkflowBlockItem Log in as **admin** (default password: `1234` - if you changed the admin password, use the new value). ::: :::WorkflowBlockItem In the Broadcaster UI, go to **Settings** in the main navigation and click **SSH Connections**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/HeNUAzCyWxOJ---LcOGEl-20260414-190353.png) ::: :::WorkflowBlockItem Click **Add Connection **and follow the instructions in the ZEN Master Configuration. ::: :::WorkflowBlockItem When you are finished, check the Broadcaster details in ZEN Master again, and you should see that the connection is established: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/cXh3eHM9oK7hzvLWSWdwg-20260414-192901.png) ::: :::: [title] Prerequisites [path] Quick Start: Broadcaster and ZEC/ This tutorial assumes that you have installed and activated a ZEC device to use as a feeder, a Zixi Broadcaster and a ZEC device to use as a Receiver and that all of the above resources are connected to the internet. For an explanation of how to install and activate each of the resources see [Zixi Installation Guide](https://zixidocumentation.atlassian.net/wiki/spaces/ZIG). You will also need to have a sample MPEG TS file available. You can download a sample TS file (*clock.ts*) for use in this tutorial from the Zixi Customer Portal and save it on your ZEC/Broadcaster in the "files" folder within the install directory. Access the portal [here](https://portal.zixi.com/) and then, in the **Documentation **tab, download the “Sample Files”. ![Portal Sample Files](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-6kdoLH00jB1dy_kCUeIam-20250606-132515.png) :::hint{type="info"} If you haven’t done so previously, you need to first register for access to the portal and then subscribe to the “Sample Files” packages on the **Settings **tab. :::   [title] Step 4: Creating a Push Input on Zixi Broadcaster [path] Quick Start: Broadcaster and ZEC/ Zixi Broadcaster can receive Inputs from a variety of sources such as another Broadcaster, a ZEC acting as a feeder, or Zixi enabled encoders. The Inputs can be received through “push” or “pull” interactions and can be delivered using a wide range of protocols. While configuring an Input in Broadcaster you can customize the stream configuration. *For this tutorial, the Broadcaster is receiving a Push input from your ZEC using the Zixi Protocol. In this case, the stream is initiated by the ZEC while the Zixi Broadcaster remains in “listening mode” until the stream is initiated. We will create a Push Input in your Zixi Broadcaster using the default configuration settings.* :::hint{type="info"} The following procedure describes how to manually create a Push Input on the Broadcaster. You can configure your Broadcaster to automatically allow Push Inputs. Once this feature is enabled, when you create a Push Output on your ZEC, the corresponding Push Input is automatically created on the Broadcaster. To enable automatic Push Inputs, see [Authorization](docId\:op1GiGovcUfEyffJHwYMP) in the [Zixi Broadcaster User Guide](docId\:JGwIXYN936aeZmonZLERn). ::: ### To create a Push Input on the Broadcaster: :::::WorkflowBlock :::WorkflowBlockItem In the Zixi Broadcaster UI, in the Main Navigation, click **Inputs**. The Inputs page opens. ::: :::WorkflowBlockItem On the **Inputs** page, click the **+New Input** button in the Menu bar. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/CVZxkS-5N46ahnr4KeHkG_image.png" size="64" width="2560" height="371" position="center" alt="New Input Button" showCaption="false"} The **Add a new input stream** window is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/lz0SNT3XweUbxBvabmMOf_image.png" size="76" width="2560" height="1251" position="center" alt="New Input Screen" showCaption="false"} ::: :::WorkflowBlockItem In the **Stream ID** field, enter the precise Stream ID (case sensitive) that you assigned to the **Output** that you created on the ZEC in Step 3, e.g. *SampleTSStream01*. ::: ::::WorkflowBlockItem For the stream type selection, verify that the **Push** radio button is selected (default). :::hint{type="info"} To learn more about additional configuration options, see [Adding Push Streams](docId\:QBxQqH5asrn97jVSLwRgt) in the Zixi Broadcaster UG. ::: :::: :::WorkflowBlockItem Click **OK**. The “Input added” message appears on the top of the screen. The new Input is added to the Zixi Broadcaster and now appears in the list of streams available on the Inputs screen. After a few seconds the Input Status should be Connected (green). ![Input Status](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/_7qaGcbgHjOr53A0Wias-_image.png) ::: ::::: In the ZEC UI, on the **Outputs** page, the **Output Status** should now be *Connected* (green). [title] Step 2: Creating a File Input on ZEC/Broadcaster [path] Quick Start: Broadcaster and ZEC/ ZEC enables you to input streams into the Zixi system from various types of input sources (e.g. TS File, UDP, RTMP, ASI etc.). Once an Input has been created on the ZEC, you can configure ZEC to send the source to your Zixi Broadcaster for processing and transmission. *For this tutorial we will create an Input in ZEC for a TS file. You can use the file that you downloaded in *[Prerequisites](docId\:tmGrz4u_MKCTuz3INy6L9)* . You will then be able to configure the ZEC to transmit this file to the Broadcaster.* ### To create a File Input on the Feeder: ::::WorkflowBlock :::WorkflowBlockItem In the ZEC UI, in the Main Navigation, click **Inputs**. The Inputs page opens ::: :::WorkflowBlockItem On the **Inputs** page, click the **+New Input** button in the Menu bar. ![New Input Button](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/yrktG4ly8In7wwiF1ITSh_image.png) The** New Input** window is displayed: ![Add New Input Dialog](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/35L2Hhsa59g5tpvciIJxa_image.png) ::: :::WorkflowBlockItem In the **Stream ID** field, enter a unique name to identify this Input on your Zixi Feeder, e.g. *SampleTSFile01.* ::: :::WorkflowBlockItem In the **Input Source** section, select the **File** radio button. ::: :::WorkflowBlockItem In the **Path** field, enter the full path to the sample TS file "clock.ts" on the local machine OR click on the "…" button and navigate to the desired file. *If you cannot locate the file ensure it has been placed into the "files" folder in the install directory.* ::: :::WorkflowBlockItem Click **OK**. The “Input added” message appears on the top of the screen. The new Input is added to the Feeder and now appears in the list of streams available on the Inputs screen. After a few seconds the **Input Status** should be *Online* (green). ![Input Status](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/GPMkqE9-xh4DdvBGbVK97_image.png) ::: :::: [title] Step 3: Creating a Push Output in ZEC/Broadcaster [path] Quick Start: Broadcaster and ZEC/ Once you have configured an Input on the ZEC/Broadcaster, you can create an Output to send the Source to your Zixi Broadcaster/ZEC. This can be done either as a Push or Pull interaction. It can also be done in various formats (e.g. UDP, HTTP or Zixi Protocol). To use ZEC your Input has to be either Zixi push/pull OR your Output has to be Zixi push/pull. You can then select any format for the opposite input or output. *For this tutorial we will create a "Push to Broadcaster" Output, which uses Zixi Protocol to push the Source to your Broadcaster.* ### To create a "Push to Broadcaster" Output on the ZEC/Broadcaster: :::::WorkflowBlock :::WorkflowBlockItem In the ZEC/Broadcaster UI, in the Main Navigation, Click **Outputs**. The Outputs page opens. ::: :::WorkflowBlockItem On the **Outputs** page, click the **+New Output** button in the Menu bar. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/8tUi7bgZwZHREDGquq9nI_image.png) The **New Output** window is displayed: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/qFfOIKU9ns3R_uYLdKUI0_image.png" size="40" width="652" height="792" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Output Name** field, enter a unique name to refer to this Output on the ZEC/Broadcaster, e.g. *SampleFeederOutput01*. ::: :::WorkflowBlockItem In the **Type** section, select **Push **radio selection button. ::: :::WorkflowBlockItem In the **Input Stream **field, select from the dropdown list the Input that you created using the sample TS file. e.g. *SampleTSFileInput01* (The input is listed as follows "\{Input Name} – File:/\{file name}.ts"). ::: ::::WorkflowBlockItem In the **Stream ID** field, enter a unique name that will be used to identify this stream throughout the Zixi ecosystem. e.g. *SampleTSStream01.* *If you are sending this stream to ZEN Master - the configuration details, including the ****Stream ID****,**** Host ****and ****Port****, will be provided once you create a new source in ZEN Master.* :::hint{type="info"} Make a note of the precise Stream ID (case sensitive) that you assigned. You will enter this Stream ID when you configure the Broadcaster to receive this stream in *Step 4*. ::: :::: :::WorkflowBlockItem In the **Host** field, enter the **hostname** or **IP address** of your Zixi Broadcaster. ::: ::::WorkflowBlockItem Verify that the **Port** field is set as 2088 (default for push) and that the **IP** field is set as *Any* (default). :::hint{type="info"} To learn about additional configuration options see [Adding Push Outputs](docId\:nsqD917A5wh-XgGSccsrd) in the Zixi User Guide. ::: :::: :::WorkflowBlockItem Click **OK**. The “Output added” message appears on the top of the screen. The new Output is added to the ZEC/Broadcaster and now appears in the list of streams available on the Outputs screen. The **Status** should be *Connected* (green). ![Output Status](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/s6m3fUOyUB1BRhW_TyjZu_image.png "Output Status") ::: ::::: [title] Zixi Quick Start [path] / ![Zixi Quick Start](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/OOifjIc92uy11HXr4sDLN_quickstart.jpg) This Quick Start guide is designed to get you up and running with Zixi quickly by familiarizing you with key tasks and elements of the Zixi platform. There is first a document with tips on using this documentation site most effectively and then the main tutorial, which is offered in two versions: - **Quick Start focusing on ZEN Master **- we recommend using ZEN Master as it both simplifies the central tasks of ingesting video transport streams, processing them as needed, and delivering them to target destinations, while also providing extensive monitoring of each of those steps, which is invaluable in diagnosing and addressing issues when they arise. - **Quick Start focusing on Zixi Broadcaster and ZEC** - for those who choose to forego the ZEN Master control plane and just use the Broadcaster and ZEC as standalone apps, we offer a second version of the tutorial that uses only these apps. Before we get to the actual tutorials, though, here is a quick overview of the different parts of the Zixi Platform to help you understand what they do and how they relate to one another, and also a page on [Using Zixi Documentation](docId\:lSBEYruIz4H_LcGzcrQRr). ## Zixi Platform Overview Zixi's platform enables the delivery of broadcast-quality live video over the public internet — with low latency, high reliability, and flexible deployment options. Three core components work together to make this possible: **Zixi Broadcaster/ZEC**, **ZEN Master**, and **ZaaS**. ### Zixi Broadcaster / ZEC **Zixi Broadcaster **is the engine at the heart of the Zixi platform. It receives video streams, processes them (including transcoding, transmuxing, and recording), and distributes them to one or more destinations — across any network, at any distance, in real time. **Zixi Edge Compute (ZEC)** is a lightweight edge component that can function as a contribution endpoint (replacing a Zixi Feeder), a distribution endpoint (replacing a Zixi Receiver), or both. ZEC is installed on-premises and connects to Broadcaster in the network. Broadcaster and ZEC handle the actual movement and processing of your video. They are the workhorses of the Zixi network. ### ZEN Master **ZEN Master** is Zixi's orchestration and monitoring control plane. It provides a centralized web interface — and a REST API — for configuring, managing, and monitoring Broadcaster instances and the streams flowing through them. With ZEN Master, you can: - Configure Sources, Channels, and Targets for your streams - Monitor stream health and receive alerts in real time - Manage large-scale deployments of Broadcaster instances from a single interface - Automate workflows using the ZEN Master API ZEN Master does not move video itself — it tells Broadcaster how to move it. Think of Broadcaster as the infrastructure and ZEN Master as the control plane that sits above it. ### ZaaS (Zixi-as-a-Service) **ZaaS** is a fully managed deployment model for the Zixi platform. Rather than installing and maintaining your own Broadcaster infrastructure, Zixi provisions and manages Broadcaster clusters in the AWS cloud on your behalf — in two geographic regions for redundancy and failover. Once the infrastructure is in place, you interact with ZaaS exactly as you would with any other Zixi deployment: through ZEN Master. You configure your Sources, Channels, and Targets in ZEN Master; Zixi handles everything beneath that layer. ZaaS is the right choice if you want the capabilities of the Zixi platform without the overhead of managing the underlying infrastructure yourself. ## How the Three Components Relate | | **Broadcaster / ZEC** | **ZEN Master** | **ZaaS** | | ------------------ | ------------------------- | ------------------------- | ---------------------------------------- | | **What it does** | Moves and processes video | Orchestrates and monitors | Managed infrastructure | | **Where it runs** | On-premises or cloud | Cloud (SaaS) | Zixi's Cloud Vendors | | **Who manages it** | You | You | Infrastructure: Zixi
Workflows: You | | **Required?** | Yes | Recommended | Optional | In a typical self-managed deployment, you run one or more **Broadcaster** instances (on-premises, in your own cloud, or both) and use **ZEN Master** to configure and monitor them. With **ZaaS**, the Broadcaster infrastructure is provisioned and managed by Zixi — but you still use ZEN Master as your operational interface, exactly as in a self-managed deployment. In all cases, ZEN Master is the recommended primary interface for day-to-day operations. - [Using Zixi Documentation](docId\:lSBEYruIz4H_LcGzcrQRr) - [Quick Start: ZEN Master](docId\:Y-kn6UUQYEBqS5NOMp9Z1) - [Quick Start: Broadcaster and ZEC](docId\:qunjBjcj-QFPKGBaop14D) [title] Step 1: Login to ZEN Master [path] Quick Start: ZEN Master/ Navigate to your ZEN Master instance URL and log in with your credentials. :::hint{type="info"} If your organization uses SSO, follow your organization's login flow. See SSO Setup Guides for supported identity providers. ::: [space] Troubleshooting (/troubleshooting) [title] General Troubleshooting [path] Troubleshooting/ This section walks you through common issues step-by-step, helping you find and fix root causes quickly. For anything that can't be resolved quickly and requires Zixi assistance, escalation guidance is included, covering exactly what to provide when opening a case with Zixi Support. - [CC Error Troubleshooting Guide](docId:41TzO6gnW6ZkBJ7eoBgpC) - [Missing Captions Troubleshooting Guide](docId\:gLK1y0aHsgILe8w_bUYPO) - [PCR Clock Drift Troubleshooting Guide](docId:1fY2-LxjIbTP5wkuThnkE) - [Timeout error Troubleshooting Guide](docId\:BxgUNlKZYi2URd-hyU3gz) - [VLC Issue Troubleshooting Guide](docId\:oRUrn5WhmTRzXFs3YrTzJ) [title] Troubleshooting [path] / ![Troubleshooting](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/SkaT7kDx1AIW3WJSuf-Pj_troubleshooting.jpg) In this section, you will find guides to help you understand errors and to help you diagnose and correct them. ## Topics - [Best Practices](docId\:zRsQrKVOELv4kA51Ezc0U) - [General Troubleshooting](docId:8G3vceiKZJsnPYLU1rQSH) - [Broadcaster - Errors and Troubleshooting](docId\:HUi-CQDzF218zY6PB1o9W) - [ZEN Master - Errors and Troubleshooting](docId\:CYHMfI_-M9ldX5aSfojSN) [title] Error - Bitrate above configured maximum [path] Troubleshooting/ZEN Master - Errors and Troubleshooting/ ### ERROR Bitrate above configured maximum - Update source configuration with a higher value ZEN Master raises this warning when an input receives more packets than its Max Bitrate allows, not counting resent or FEC packets. On a Zixi input, Max Bitrate sizes the buffer used to recover lost packets. It is not a cap on the stream, but if it is set close to the feed rate, bursts and resent packets overflow that buffer and count as not recovered. Set the input's Max Bitrate to about 1.5 times the feed's average rate. See [Sizing latency, buffer and max bitrate](docId\:oj4srP9fTjhYtmGyv7xJA). ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/UcRPdtEOkBeUjYy8Dbl-Q_image.png) [title] Broadcaster - Errors and Troubleshooting [path] Troubleshooting/ Explanations of common errors and notes on how to resolve them are found in the following pages. - [Bitrate above configured maximum - Update source configuration with a higher value](docId:72pfNXrqL4wBYFSzANbYS) - [Broadcaster API Errors](docId\:iW55PKhoZZwh9-rJm9y12) - [Broadcaster Output error - Unsupported Encoding](docId:2SZM2Mj3aiwJmBCm_pAWI) - [Certificate Error](docId\:sLaHDvzTRWYZmRzUSuHLi) - [Change the UI Port for Broadcaster](docId:2Ud9zWCPT0lOA4KJIYUYU) - ["Compression Error"](docId\:g4-y60GhhPfxODmBs7Cn3) - [Configure linux to create core dumps on a crash](docId\:wVMJQpOhPks4yQFgj6W2S) - ["Failed to start program" Transcode error](docId\:R-vhfLmFOjgKFXWfwSNEa) - [Intermittent frozen video/silent audio errors](docId:6_Xgsh6LEaaX7QW2bEtpc) - ["INVALID CSRF TOKEN"](docId\:H1WRITLvCQxjbLx4-yG7Q) - ["Low Bitrate" Error](docId\:fQjRReVrTBql4kdkF9kJD) - ["NTP - Failed to Start Service"](docId\:wlbxf27RIVVLj41d4ToIW) - ["Not Supported" error on a PULL input](docId\:DH10CCWVEnS2E2uARjCtY) - ["Overflow" Error (Output)](docId:3LbvbeOXfKuPLmf44yxgx) - ["Reconnecting – Full" / "Reconnecting – Rejected" on a stream](docId\:FGdyD4cAeKk_zAX4zYeUc) - [Replacing Zixi Hardware in active cluster with Pinned Objects](docId\:OuQrgzXttmugnqS5hn6WM) - [RIST Simple Profile shows a Bitrate - status: not connected](docId\:M1w-3FELkMZgE9TRm6X2q) - [Source & Target States & Errors](docId\:XfUx_gIUJs8sdqC8cV1bi) - [SRT Library Reference](docId\:dGx0_IY4y6WDofkBXmvpO) - [Stream only connects using IP Address](docId\:KkNb2XcdCR1iDDD9QWoqD) - [Unsupported Encoding](docId:7h1aEAm5dHrUgMiZjhPPH) - [Updating time in the Broadcaster causes a Disconnection](docId\:I5tzO1LXI8IsZG8EZLFNa) - [Windows Broadcaster Will Not Connect to ZEN Master (SSH Tunnel / Key Permissions)](docId\:fUYtLeYtglmGat6Cs0FUF) - [Upgrading an Existing Broadcaster/ZEC](docId\:R3H7Mu4pHgbO5qQH8AcWs) [title] "Failed to start program" Transcode error [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/ ### ERROR "Failed to start program" error on transcode stream. ![Failed to Start Program Errors](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/XcqnWDa2Xh4vRlQWVZM3__image.png) ### ISSUE - Verify **libgomp1** dependency is installed on Ubuntu OS - You can run the following command `# dpkg -l | grep libgomp1` ![Check for Dependency](https://zixi.zendesk.com/attachments/token/yZD9WfZZYt44rAX4tirULic1u/?name=image.png) - If **libgomp1** is not installed, install it using the following command: ` # sudo apt-get install libgomp1` ### RESOLUTION The libgomp1 dependency was not installed, once it is installed the transcode streams should resolve. If you continue to experience issues please reach out to Support team. [title] Certificate Error [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/ ### ERROR You may find that you are having an issue with a Source output connecting to the destination Broadcaster, and see repeated "certificate error" events in the log. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/7DnFrhMT94yaYlnlrxBI-_certificate-error.png) ### CAUSE The receiving broadcaster (whether it be ZEC -> Broadcaster, or Broadcaster -> Broadcaster) is required to have a valid DTLS Certificate. If the certificate information is expired you may see the above mentioned error, and new sources which may have been configured to use port 7077/7088 (DTLS ports) may not connect. ### RESOLUTION - You can manually adjust the port on the sources to 2077/2088 instead of 7077/7088, to immediately connect without using DTLS. - If this certificate has expired, renew the certificate per instructions here [Enabling DTLS](docId\:dPbwtfB1ic317na2uhnJD) - If the certificate is valid, the ZEC may be holding onto stale DTLS certificate data, in this case restart the ZEC software to refresh. You can determine a stream is connected using DTLS by the gold lock icon on the green connected status icon, as well as by the data in the informational popup when you mouseover the icon. The popup will display certificate issuance and expiration dates ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/HZeZN_Z85-A51C3eK5fSn_dtls.png) ### [title] Replacing Zixi Hardware in active cluster with Pinned Objects [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/ **Procedure to replace a Zixi Broadcaster (Hardware) in a active Broadcaster Cluster that has “Pinned” Sources, Channels and Targets.** ### Pre-Requisites Within reason, execute the following: - Remove as many of the services as possible off of the Zixi Broadcaster that is to be replaced. - Take note and copy all the network, naming and password information from the Broadcaster that is to be replaced. - Export the Configuration file - Go to the Settings Tab - Export - Export Configuration File ::Image[]{src="https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/WQXak-Oswxq2tlXwmcFt6-20251121-181850.png" size="76" width="1145" height="517" position="center" caption="Export configuration file - screenshot" alt="Export configuration file - screenshot" showCaption="true"} ### Install hardware - If there is room in the data center or specific rack location, install your replacement server. - Prewire the server with the appropriate NICs and available switch ports preset to mirror the port configs of the server to be replaced. - Load your preferred OS and Zixi Bx software, using the same version as on the server to be replaced. ### Instructions for ZEN Master - Login to ZEN Master **TARGETS** - Go to the ‘Target’ tab, filter targets by the name of the Broadcaster that is to be replaced. ![Filter by broadcaster - screenshot](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/wdh2Alx-G5MofNwKt8qsx-20251121-181743.png "Filter by broadcaster - screenshot") - Enter broadcaster name into Broadcaster name filter box ::Image[]{src="https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/8Zgh5njdhMefpcOfy0c-T-20251121-182045.png" size="60" width="573" height="158" position="center" caption="Broadcaster name filter - Screenshot" alt="Broadcaster name filter - Screenshot" showCaption="true"} - Check the box next to name to highlight all entries ![Screenshot with Name checkbox checked](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/mGS09SwjbNDfSgsFueiEt-20260204-224358.png "Screenshot with Name checkbox checked") - Disable all targets ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/TaTShqhLDU9ytcKV0rHbC-20260204-224943.png) - Repeat the above process in the following order for: - Channels, then - Sources ### Instructions for Server to be Removed - Export and save the configuration file form the current broadcaster - Go to the Settings tab in the Broadcaster User interface - Click the "Export" button ![Screenshot Export configuration file button](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Ab_Qlg2xs9-e40-rD_e8C-20260204-225304.png "Screenshot Export configuration file button") - Power down and remove the server ### Instructions for New Server - Install New Server - If you were not able to prewire and configure the new server, at this point, wire in the server using the same cables that were previously used. - Install your OS - Install Zixi broadcaster software - Configure the Zixi broadcaster settings to mirror the settings of the previous server that has been removed from service - Copy/Transfer the saved config file from the previous machine - Import and load the saved configuration file - Go to the Settings tab in the new Broadcaster User Interface - Click the "Install" button and select the saved config file ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/zjUg4k1Z5luGUg1FGO6Ij-20260204-225326.png) ### Instructions in ZEN Master for restoring new server - In ZEN Master go to the page for the broadcaster - In the Broadcaster tab, locate the three dots/More Actions button and select "Config" from the drop-down menu ![Config option in drop down window screenshot](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/6YhI_3VouE2Ki7nKnLi0G-20260204-230144.png "Config option in drop down window screenshot") - Following the instructions on the Config window that pops up, copy and paste the Config into into the replacement broadcaster using the Broadcaster GUI - Wait for ZEN Master and the new broadcaster to establish a connection - this should take less than a minute. - Go to the "Details" tab on the broadcaster page - Install Agent Z ![Details page showing install agent z tab](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/U5p2Zzug14RNu2x2jmEGU-20260204-231518.png "Details page showing install agent z tab") - Once Agent Z is finished installing, click "Update Broadcaster Configuration" at the bottom of the details page ![Screenshot of Update broadcaster configuration buttton](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/b6fdug8cTStP1gMA5NaZc-20260204-231803.png "Screenshot of Update broadcaster configuration buttton") ### Bringing streams back online *We can now start to bring services back online, using the reverse of the disable procedure we performed at the start.* - Go to the **"Sources"** tab and filter Sources by broadcaster name - Check the "Name" box to select all of the sources pinned to this broadcaster - Click the "Enable" button - While monitoring in ZEN Master their connection status, wait until the alarms for all of the Sources clear (status goes from Red to Green) - Repeat the same process for all **"Channels"** pinned to the broadcaster - While monitoring in ZEN Master their connection status, wait until the alarms for all of the Channels clear - Repeat the same process for all **"Targets"** pinned to the broadcaster. - While monitoring in ZEN Master their connection status, wait until the alarms for all of the Targets clear - Validate that all Targets have reconnected via both ZEN Master Target tab ***AND*** the status indicators in the ‘Output’ tab of the direct Broadcaster GUI [title] CC Errors on Failover Source (No-Merge/Stream Switch) [path] Troubleshooting/Best Practices/ This applies to failover sources configured in **no merge mode.** In this mode, the source carries a single active source at a time and performs a hard cut when switching. CC errors on the failover output in this configuration are generally expected and fall into two distinct categories. ## Root Causes ### 1. Switch-Correlated CC Errors (Expected Behavior) In a no merge failover, any source switch adds a discontinuity in the MPEG-TS continuity counter. The outgoing stream transitions abruptly from one source's counter state to another. When this happens the counters will not be in sync, and a CC error will occur on each switch event. **Note:** You may see several CC errors as each PID has its own counter. This is **not a defect** it is the inherent nature of hard cut switching. There is no way to eliminate this without moving to a merge/redundancy (2022-7) configuration, which can stitch streams together at the packet level. :::hint{type="warning"} 2022-7 can only be used with binary identical RTP streams. ::: **Mitigation - Error Concealment (EC):** If the CC error at switch time is causing downstream issues (e.g. alerting systems, decoders), the following EC options can mask the problem: - **Make timeline continuous** - Makes the output stream appear as a single continuous timeline across switch events, reducing visible discontinuity to downstream equipment. - **Renumber CC** - Renumbers continuity counters on output to suppress CC error reporting. Effectively masks counter breaks induced by the switch. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ZHV7K1mLZh66XfqFFmYDO_zm-edit-failover-source.png) These are cosmetic fixes only, the underlying switch event still occurs - but downstream detection is suppressed. ### 2. Source P1 Errors Passing Through (Configuration Note) When the source is** not **configured to switch on P1 error events. This means if a CC error exists in the active source feed, it will be passed through to the failover output without triggering a switch. If the goal is to fail away from a source that is generating CC errors, enable P1-based switching. **Note: **This should only be used to switch when there are excessive CC errors which can be defined in the configuration options. *Be aware that the switch itself will also introduce a CC error (see above).* ![Options when Failover on p1 Error concealment configuration menuis switched on](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/OI2BXRjtU_GWtfJVaUPQj_zm-edit-failover-source2.png) ### 3. Jitter Introducing CC Errors (Transport Layer) Stream inputs can introduce packet timing jitter that does not manifest on the source monitoring points, but does appear after the failover source's processing path. This explains cases where CC errors appear on the failover output but **not** on the individual stream inputs. **Mitigation:** - Increase the **search window** (latency buffer) on the Failover source. It needs to be set at >50ms at all times, ideally be more in the 500ms-1s range unless latency is a major decision point. - A wider window gives the receiver more room to reorder and recover packets before they're passed downstream, which can reduce or eliminate jitter induced CC errors. ## Decision Tree **CC errors seen on failover source output** Do errors correlate with source switch events? **→** YES **→** Expected behavior for no merge failover - enable EC with Continuous Timeline + Renumber CC to suppress Are CC errors also present on the stream source inputs? **→** YES **→** Source feed issue. Consider enabling P1 error based switching to fail away from a bad source CC errors on failover output but not on stream Inputs? **→** YES **→** Likely jitter introduced in the failover path - increase the search window/latency buffer No clear cause found **→** Capture TR 101 290 data at both Stream input and failover output and escalate to Zixi Support ## Escalation Checklist When escalating to Zixi Support, include the following: - ZEN Master source link and Broadcaster version(s) involved - Source name and failover mode (confirm no-merge vs. 2022-7 merge) - Stream input names and connection details (listener/caller, latency settings, search window size) - Whether EC is enabled and which options are active (Make timeline continuous, Renumber CC) - Whether P1 error-based switching is enabled or disabled - Timestamp and Time zone of CC error events - TR 101 290 error counts at Stream inputs vs. failover output - Source Event Log export covering the error window - Any recent changes to failover source config, Stream settings, or source routing ## Configuration Summary | Setting | Current State | Recommendation | | -------------------- | --------------------- | ----------------------------------------------------------------------- | | Failover mode | No-merge (hard cut) | Acceptable; 2022-7 merge eliminates switch CC errors entirely | | Switch on P1 errors | Disabled | Enable if you want automatic failover on source CC errors | | Error Concealment | Not confirmed enabled | Enable with Continuous Timeline + Renumber CC to suppress switch errors | | Stream search window | Default/narrow | Widen if jitter-induced CC errors are suspected | ## Notes - Moving to **2022-7 merge mode** is the only way to fully eliminate switch-correlated CC errors. EC options suppress reporting but they do not prevent the underlying counter discontinuity. - If alerting thresholds are being hit by switch correlated CC errors, EC with Renumber CC is the fastest resolution to mitigate. - For jitter investigation, compare TR 101 290 P1 CC error timestamps on the source inputs versus the failover output to confirm possible Jitter causes before widening the search window. ## [title] Missing Captions Troubleshooting Guide [path] Troubleshooting/General Troubleshooting/ Missing captions can occur at several points in the signal chain. The fastest path to resolution is figuring out where captions disappear. ## Step 1. Isolate the Fault Point Before changing anything, capture and inspect the stream at each stage: - **Source (encoder output)** → **Zixi input** → **Zixi output** → **Decoder/IRD** Use a TS analyzer (Wireshark, a hardware analyzer, or VLC with stream info) to check whether captions are present at each stage. The point where they vanish is the fault point. ## Step 2. Check the Source Encoder If captions are absent from the start of the chain this is likely an issue at the encoder. **Things to check:** - Is closed caption passthrough enabled? This is a common miss after a firmware update, reconfiguration, or factory reset. - Is the encoder transcoding the video? Transcoding pipelines frequently strip CEA-608/708 data unless CC passthrough is configured. - Verify the source material is actually captioned. Live sports and news feeds typically are, but the caption insertion feed (e.g. a separate caption encoder) may have its own failure. - Are there frame drops in the encoder logs? CEA-608 data rides per-frame inside the video elementary stream dropped frames mean dropped caption bytes. **Fix:** Enable CC passthrough in the encoder settings. If transcoding, ensure the transcoder is configured to re-encode or pass through caption data. Refer to your encoder vendor's documentation for specific information. ## Step 3. Check the Zixi Path If captions are present at the Zixi input but missing at the output, something in the broadcaster/ZEC processing chain is removing them or an error is occurring. **What to check:** - Is any transcoding or remuxing being applied inside Zixi Broadcaster? This may be inadvertently stripping out the caption data. - On failover sources, did a source switch occur recently? The backup source may not be configured identically to the primary. Check that the failover source encoder has the same CC settings. - Review ZEN Master source/channel/target and Broadcaster logs around the time captions went missing. Look for source switch events, errors, or unexpected restarts. ## Step 4. Check the Decoder / IRD If captions are present in the Zixi output but still not displaying at the endpoint: **What to check:** - Is the decoder configured to decode the correct caption service? - CEA-608: CC1 or CC3 (field 1/field 2) - CEA-708: Service 1 (most common default) - Has the decoder been recently rebooted or reconfigured? Caption decode settings can reset to defaults. - Does the playout or monitoring system have a caption rendering/overlay setting that may be disabled? ## Troubleshooting Decision Tree Captions reported missing ZEN Master alert raised? → YES → Event Notification Profile has caption monitoring enabled — trace chain below to find fault point Captions absent from source TS? → YES → Encoder issue (Step 2) Captions present at Zixi input, missing at Zixi output? → YES → Distribution/processing issue (Step 3) Captions in Zixi output, not displaying at endpoint? → YES → Decoder / IRD issue (Step 4) A clear fault point found? → NO → Capture TS at input and output and escalate to Zixi Support ## ZEN Master Event Notification Alerts If you're using Zixi ZEN Master, it can be configured to actively alert on missing captions. If your **Event Notification Profile** has caption monitoring enabled, ZEN Master will raise an error any time captions are not detected in the stream. - A ZEN Master caption alert is a reliable signal that captions are absent, but it isn't able to tell you *why.* Use Steps 1–4 above to find the fault point. - If captions are intentionally not present on a channel (e.g. a non-captioned feed), disable the caption check in the Event Notification Profile for that channel to avoid false alarms. - Check your Event Notification Profile settings in ZEN Master under *Settings → Event Notifications *to confirm which event types are active and which channels they apply to. ## Escalation If captions are confirmed present in the Zixi output stream but a downstream device is still not displaying them, provide the following to support: - TS capture at the Zixi output (.ts or .pcap) - Encoder and Zixi Broadcaster logs covering the affected time window - Decoder model and firmware version - Whether the issue is constant or tied to specific events (e.g., source switches, time of day) [title] Upgrading Broadcaster from legacy versions [path] Troubleshooting/Best Practices/ ### Broadcaster Upgrade Preparation Reference Use this checklist before upgrading your Broadcaster from a legacy version. ### Before You Begin - **Back up your configuration file.** In the Broadcaster UI, go to **Settings > Export** and save the configuration before starting the upgrade. - **Confirm your license.** Depending on your upgrade path, the license may need to be reloaded or reactivated after the upgrade completes. - **Whitelist the license server.** Versions 16 to 18 use license2.zixi.com, and version 19 uses licensing.zixi.com. Allow outbound TCP 443 and 80 to the license server on your network before upgrading. - **Check the release notes.** Release notes are on portal.zixi.com, where you can also sign up to be told when a new version is released. ### Upgrade Paths by Platform **Recommended path:** upgrade one major version at a time, installing the last release of each in turn: 16.13, then 17.9, then the last 18 release, then 19. This applies to Linux and Windows. Version 18 can go straight to 19. The table below applies the same approach to specific platforms. | Current Version | Target | Path | | ------------------------ | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | v13/v14 | v16 | Upgrade through the last release of each major version: the last v15 release, then 16.13. This helps prevent potential issues during the jump. | | v15.3.44122+ (Linux x86) | v17 | Upgrade to 16.13 first, then to 17.9. | | Linux ARM | v17 | Upgrade to the last v16 release for ARM (v16.12.45243 or later) first, then to 17.9. | | AWS Graviton (ARM) | v17 | Requires **Amazon Linux 2023.** Amazon Linux 2 is not supported. | | Windows/Mac | All Versions | No in-place UI upgrade. Run the installer directly to upgrade. On Windows, the installer stops and restarts the Broadcaster service, and the host does not need a reboot. | For full OS compatibility details, refer to the System Requirements document. ### Network & Licensing Configuration Before configuring v16.x Broadcasters, make sure your port settings and licensing URL match the current requirements: - *Port Guide: *[https://docs.zixi.com/how-to-guides/network-port-settings](https://docs.zixi.com/how-to-guides/network-port-settings) ### After Upgrading: Migrating the Files Directory The upgrade installer does **not** automatically move files between the old and new install directories. Deleting the old directory without migrating it first can break existing workflows. **Once upgraded to v16, before you delete the old v15 directory:** 1. Locate the files directory under the old install path, e.g.: zixi\_broadcaster-centos7/files 2. Move its contents into the corresponding directory in the new install path: zixi\_broadcaster-linux64/files 3. Confirm dependent workflows still function correctly. 4. Only then delete the old v15 directory to reclaim disk space. [title] Intermittent frozen video/silent audio errors [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/ ### ERROR You are seeing intermittent frozen video & silent audio errors. You are not seeing any issues on the source itself at origin. ### ISSUE There could be several aspects here to investigate. - Initially see if the source is showing correlating network spikes or cc errrors at these times, if so this is related to network fluctuations. Raising the latency can help mitigate these fluctuations. - If the network is looking clean but you are still experiencing these hits, check the Max Bitrate and Dejitter Values on the stream as they may need increasing. See here for details regarding Max bitrate - [https://docs.zixi.com/zen-master/high-max-bitrate-configuration](https://docs.zixi.com/zen-master/high-max-bitrate-configuration) also check your Dejitter buffer settings. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/FT-yrIaKGU41bSgFkF-0p_image.png) ### RESOLUTION **Dejitter Buffer Impact** The broadcaster with the lower dejitter buffer setting doesn't have enough buffering capacity to smooth out network jitter spikes. When packets arrive late or out of order, the smaller buffer runs dry, causing the decoder to stall - hence frozen video. The "silent audio" suggests the audio decoder is also starving for packets during these events. **Max Bitrate Setting** If the actual source bitrate occasionally spikes above this configured maximum (common with variable bitrate encoding), the broadcaster may be dropping packets or throttling the input stream. This compounds the buffer underrun problem. [title] Upgrade from CentOS to Alma Linux [path] Troubleshooting/Best Practices/ - Take a back-up or snapshot prior to migration - Navigate to AlmaLinux OS - Forever-Free Enterprise-Grade Operating System - Click on the migrate (yellow) button - This will take you to the migration instructions page. Halfway down the page under “perform migration” the github repository link is listed. Click that link: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/WkYzNIIGlqu_-un7n9S5u_image-20250522-213357.png) - Navigate to the file almalinux-deploy.sh and click the “raw” button: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/N2DR_EYmmQT2mvHnH0raj_image-20250522-213333.png) - Choose all text (ctrl+a) and save (ctrl+s) as “almalinux-deploy.sh” in your downloads folder. - Open terminal and switch to the downloads directory. Run the script using the following command to migrate: sudo bash almalinux-deploy.sh - Once its complete, reboot and log into Almalinux [title] Broadcaster Authorization Configuration Error [path] Troubleshooting/ZEN Master - Errors and Troubleshooting/ ### ERROR "Broadcaster Authorization Configuration" error will affect a Broadcaster which has an authorization mode which is not correctly set to HTTP Server. In this mode ZEN Master is responsible for authorization of sources and targets. ### RESOLUTION In the Broadcaster view in ZEN Master navigate to the Details tab and click "Update Broadcaster Configuration". :::hint{type="danger"} Please Note: This does require a broadcaster restart during which the feeds running on it will be interrupted. ::: [title] "Overflow" Error (Output) [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/ ### ERROR "Offline - Overflow" error on an output stream ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/E2HOoZvX3XMFgjaTQCu9H_overflow.png) ### ISSUE Two different conditions inside the Broadcaster surface as the same "Overflow" error on an output. **1. The output's send queue is full.** This applies to SRT outputs, in both caller (push) and listener (pull) mode. Each SRT output holds a fixed send queue of 10,000 packets. For every packet handed to the output the Broadcaster checks how full that queue is; if it is full, the packet is dropped and the output is flagged Overflow. The flag clears automatically once the queue drains below half full. On its own this condition does not disconnect the target: the output keeps running, and packets are lost for as long as the queue stays saturated. **2. The output has stopped draining and is holding up the source.** Any output type can hit this one. If an output falls almost a full source buffer behind the stream, or the packet it has still not sent is more than 40 seconds old, the Broadcaster treats the output as stuck and disconnects it with reason overflow, so its status goes Offline. A few internal output types are re-added automatically a moment later instead of being disconnected. For failover and merged inputs, the input itself also raises Overflow for as long as any of its legs reports new overflows. In both cases the queue or buffer fills because data arrives faster than the output can send it out. The usual causes are: - Source bitrate spikes or bursts, for example from a VBR encoder on high-motion or cut-heavy content. - A max bitrate set far above the stream's real bitrate on the source. Max bitrate does not size the output's send queue. What it does is govern how large a burst the Broadcaster will admit and pass downstream, so an inflated value lets bursts through that the target link cannot drain in time. - Not enough sustained capacity on the path to the target, or, for SRT outputs, an SRT latency setting that is too low for the round trip time to that destination. Note that "Overflow" is also reported by HLS/DASH and recording outputs for an unrelated reason, where a segment or upload buffer could not take the data. Those cases are not the send queue condition described here. ### RESOLUTION - On the source, set the max bitrate to roughly 1.5 to 2 times the actual bitrate of the stream, measured against the peak rather than the nominal average. A max bitrate set well above the real rate allows bursts the target cannot drain in time, and values outside this range can cause the stream to experience issues. - Confirm the target's downstream network or link has enough sustained capacity for the stream's peak bitrate. - For SRT outputs, check the SRT latency against the measured round trip time to that specific destination. A latency below roughly 3 to 4 times the RTT is a frequent cause of overflow on longer paths. For a fuller walkthrough, including how to tell overflow apart from a network timeout, see "SRT Target overflow disconnects Troubleshooting guide". - To confirm overflow is really the trigger, check the Broadcaster system log around the event. At the default log level you will see the output being dropped for buffer pressure, logged as an `on_distributor_sink_stuck` entry for the affected output immediately before the reconnect. The raw per-packet overflow events, logged as `OnRealData OVERFLOW`, are written at debug level only, so raise the log level to debug if you need them. Related errors, not to be confused with this one: - "Max bitrate times latency too high" is a separate error, raised at connection setup rather than at runtime, when the max packet rate multiplied by the latency exceeds the internal buffer limit of 524,288 packets. If you see that specific wording, reduce the max bitrate and/or the latency. Note that for Zixi pull and push sources the max packet rate is inherited from the upstream feeder, so the setting that needs changing may be on the feeding object rather than on the one showing the error. - The ZEN Master "Performance warning" alert, "Performance related overflows detected - Validate Max Bitrate and Latency settings", is raised against the source when its distributor overflow counter increases. It points at the same underlying pressure, but it is a source-side signal and not the output error described on this page. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/oB7-k7rRFiD2jH7Bs9m3m_image.png) [title] "Reconnecting – Full" / "Reconnecting – Rejected" on a stream [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/ ### ERROR Error "Reconnecting - Full Full" on a stream input or output ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/bXaUMHzsWfCik6ju-fK5U_reconneting.png) ### ISSUE A stream (input or output) stays in a **Reconnecting** state with an error of **Full** or **Rejected**. These look similar but have different causes — the error field tells you which: **"Full"** — the remote Broadcaster refused the connection because it is **at capacity or has hit a configured limit** (e.g. server full, or a max sources / max outputs / object limit reached). The connecting side keeps retrying, so the stream cycles in *Reconnecting – Full*. **"Rejected"** — the stream is **already connected somewhere else**: another feeder/Broadcaster/decoder is using the same stream ID. The two ends repeatedly displace each other, so the output keeps disconnecting and reconnecting. ### RESOLUTION - **Full:** free up capacity on the target Broadcaster, raise the relevant limit (max sources/outputs), or connect to a different Broadcaster. - **Rejected:** find and stop the duplicate feeder/decoder using the same stream ID so only one end is connected. [title] "NTP - Failed to Start Service" [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/ ### ERROR "NTP - Failed to Start Service" Error ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/xYY25c--ykkC6Q8Rw6b3y_image.png" size="74" width="963" height="331" position="center" darkWidth="963" darkHeight="331" showCaption="false"} ### ISSUE NTP Service Failure in Zixi Broadcaster and Zixi Edge Device (ZEC) may encounter an issue when attempting to start the NTP (Network Time Protocol) service in Zixi Broadcaster or Zixi Edge Device (ZEC). The error message displayed is: *NTP – Failed to start service* The NTP service in Linux is a daemon responsible for synchronizing the system clock of a computer with a time source server. NTP enables devices to maintain accurate and coordinated time over a network, ensuring consistent and reliable operations. This error typically arises when the required NTP service is either not installed or not enabled on the Linux machine running the Zixi Broadcaster or ZEC. Below are steps to identify and resolve this issue on both Ubuntu 22.04 and CentOS 7.9 Linux distributions. :::hint{type="info"} Modern OS's no longer support the package `ntp` and the Broadcaster therefore cannot manage NTP on those machines. The modern equivalent is `chrony` and must be managed directly via the OS. ::: ### RESOLUTION ### For Linux Ubuntu 22.04: **Check if the NTP Service is Installed:** Open a Linux shell and run the following command to verify the status of the NTP service: *systemctl status ntp* This command will provide information on whether the NTP service is installed and currently running. **Install NTP (if not installed):** If the NTP service is not installed, install it by executing the following command: *sudo apt-get install ntp* This will download and install the necessary NTP package. **Start NTP Service in Zixi Broadcaster/ZEC:** Once the NTP package is installed, navigate to the Zixi Broadcaster or ZEC Management Console and attempt to start the NTP service. If the installation was successful, the service should start without issues. ### For Linux CentOS 7.9 **Check and Install NTP Service:** In CentOS 7.9, verify and install the NTP service by running: *yum install ntp* If the NTP service is already installed, this command will notify you. If not, it will install the required NTP package. **Start NTP Service in Zixi Broadcaster/ZEC:** After installing NTP on CentOS, revisit the Zixi Broadcaster or ZEC Management Console and try to start the service. The issue should be resolved at this point. ### Summary: The failure to start the NTP service in Zixi Broadcaster or Zixi Edge Device (ZEC) often stems from a missing or inactive NTP service on the Linux machine. By verifying the installation of the NTP package and installing it if necessary, users can resolve this issue and successfully synchronize the system clock for accurate and smooth operations.   [title] Error: Create transcoded input error, not found in response [path] Troubleshooting/ZEN Master - Errors and Troubleshooting/ ### ERROR "Create transcoded input error, not found in response" ### ISSUE The error "**Create transcoded input error, not found in response**" occurs when creating a **transcoded** input on a Broadcaster, for example when enabling an **NDI target**, or when creating any transcoded source/channel. ZEN Master asked the Broadcaster to create the transcoded input and the Broadcaster returned **no error**, but the newly-created input was **not present **in the Broadcaster's response, so ZEN Master cannot confirm it was created. ### RESOLUTION Try recreating the target/transcoded input. If it continues, contact Zixi support. [title] "Low Bitrate" Error [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/ ### ERROR Low Bitrate ### ISSUE The stream shows a bitrate problem: on the stream itself the error state reads "**Insufficient bitrate**" (or "**Zero bitrate**" if it is receiving nothing), while the corresponding alert/notification is labelled "**Low bitrate**". Check the bitrate for the stream and you will see it is receiving 0 or a very low bitrate. ### RESOLUTION - Verify the state of the stream on the sender side - is it active, does it have the correct bitrate, are there any errors with the encoder. - Restart the stream on the sender side - Verify the network status on the machine hosting the sending software and the receivers network. - Restart the machine on the sending side - Verify the network is set to allow traffic from the sending Address and Port on the receiving side with the Low Bitrate error [title] Broadcaster Output error - Unsupported Encoding [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/ ### ERROR Broadcaster Output Error - Unsupported Encoding ### ISSUE The "Unsupported encoding" error usually relates to a codec the target cannot accept; the error comes from the target itself. It is most often an unsupported audio type. For example, RTMP output supports only AAC or MP3 audio, and only H.264 or HEVC video, any other audio (e.g. MPEG-1 Layer 1/2, AC-3) or video codec will be rejected with this error. ### RESOLUTION - **Transcode** the stream and set the audio to **AAC** (MP3 is also accepted for RTMP), and video to H.264/HEVC; or - Go back to the provider and have the encoding adjusted to a supported type — e.g. change the RTMP audio from MPEG to AAC. [title] Configure linux to create core dumps on a crash [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/ Open SSH connection using PuTTy and running the following commands: 1. Create the target directory first: :::CodeblockTabs{indent="1"} ```bash sudo mkdir -p /zixi/cores # the path in core_pattern must exist, or no core file is written ``` ::: 2. `sudo nano /etc/security/limits.conf` 3. edit row with *"*`*  soft  core  unlimited`*"* 4. add line *sysctl kernel.core\_pattern="*`/zixi/cores/core.%p`*"* 5. Save changes  *Ctrl + O* 6. Exit from nano* Ctrl + X* 7. Check with the following command: `ulimit -c` 8. Check if it is unlimited after restart as well `cat /proc/sys/kernel/core_pattern` :::hint{type="info"} edit /etc/security/limits.conf - will make the core dumps creation persistent sysctl kernel.core\_pattern="/zixi/cores/core.%p" - will put the cores in the defined location ::: :::hint{type="danger"} The limits config is not persistent across reboots. To persist this config add `kernel.core_pattern = /zixi/cores/core.%p`to `/etc/sysctl.conf` ::: [title] CC Error Troubleshooting Guide [path] Troubleshooting/General Troubleshooting/ **Continuity Counter (CC) errors detected on incoming streams within Zixi Broadcaster / ZEN Master** **What Are CC Errors?** The **Continuity Counter (CC)** is a 4-bit sequence number (0–15, wrapping) embedded in the header of every MPEG-2 Transport Stream (TS) packet, unique per PID. Each successive packet on the same PID must increment the counter by exactly 1. A **CC error** is triggered when that sequence breaks, which indicates one of the following: | **Condition** | **Meaning** | | ---------------------- | --------------------------------- | | Counter value skipped | One or more packets were **lost** | | Counter out of order | Packets were **reordered** | | Counter repeated twice | Packets were **duplicated** | CC errors are a symptom of a problem, not a root cause. The troubleshooting goal is always to identify *where* in the signal chain the break is occurring. ## Troubleshooting Workflow Work through the following steps in order, from source along the stream towards the target. Diagrams within ZEN Master can provide a visual overview of the workflow. Resolve at the earliest point of failure before proceeding. **Situation:** The target customer advises they are seeing cc errors. Check content analysis within ZEN Master, starting at the source. Within the histogram you observe cc errors. Compare the Network histogram to see if drops/spikes align with the same time stamps as the cc errors. ![Screenshot comparing cc errors with network](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/fQM1WBmMTb0s3xobADEQp-20260318-190150.png "Screenshot comparing cc errors with network") The event log will have useful information relevant to the cc errors like a specific PID. ![Event log showing Continuity Count Errors](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/JspYWFZKaG2Zu_qeLwf3D-20260318-190328.png "Event log showing Continuity Count Errors") ### Step 1. Confirm the CC errors are originating from the source **What to check:** Before assuming a network or Zixi issue, verify whether CC errors are present *before* the stream even reaches Zixi. **How:** - If you have access to the encoder or upstream device, capture a local TS (e.g. via loop output or direct ASI/IP tap) and analyze it with a tool such as TSReader, Wireshark (MPEG plugin), or VLC. - In ZEN Master, navigate to the affected input object and check the TR101 histogram under “History” - If CC errors are visible immediately in the analysis for this source with no matching network anomalies (drops or spikes), the source is the likely culprit. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Dk22vJVyZ5k96P7kEX8Es-20260318-192153.png" size="60" width="1085" height="463" position="center" caption="CC errors on the Source Histogram" alt="CC errors on the Source Histogram" darkWidth="1085" darkHeight="463" showCaption="true"} - In Zixi Broadcaster, go to **Inputs → \[Select Stream] → Stream Analysis → CC Error Histogram** and note whether CC errors are present from the moment the stream connects or only appear intermittently. ![Stream analysis Icon](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/NkRGWktCgNJxytnN8cknX-20260318-193233.png "Stream analysis Icon") ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Y9vKdRv4mztEeKcPdfM-G-20260318-192618.png" size="82" width="1328" height="835" position="center" caption="CC error statistics in Broadcaster" alt="CC error statistics in Broadcaster" darkWidth="1328" darkHeight="835" showCaption="true"} **Root Cause:** CC errors present at source before any Zixi processing. **Advice:** Escalate to the source provider encoder/mux operator team. The issue lies upstream of Zixi and must be resolved at the encoding device. Provide them with a TS capture or CC error count with timestamps as evidence. ### Step 2. Check encoder configuration **What to check:** Even if the source appears healthy, incorrect encoder settings can produce malformed TS output. **Check the following on the encoder:** - **Restart the encoder - **Even a correctly configured encoder can begin generating CC errors after running for an extended period without a restart. This is not a network or Zixi issue it is an internal encoder process failure. Common causes include: - Internal mux scheduler corruption - Memory leak in the encoder process - PRC Clock drift accumulation - Thread deadlock in the mux pipeline - PID Counter wraparound bug - **Bitrate stability** - Is the encoder configured for CBR (Constant Bit Rate)? VBR streams with aggressive rate changes can cause buffer overflows in downstream muxers, leading to dropped packets and CC errors. - **PCR interval** - PCR should be injected every 40 (DVB minimum) – 100ms (ATSC minimum) per PCR PID. Misconfigured PCR spacing causes downstream sync issues that can manifest alongside CC errors. - **Mux rate overhead** - Ensure the encoder's configured mux rate includes sufficient null packet stuffing. A mux rate too close to the active content bitrate leaves no headroom and causes packet drops under load. - **Multiple audio PIDs** - Streams with many audio PIDs (e.g. multilingual feeds) are more susceptible to mux scheduling issues. Confirm that all PIDs are being correctly scheduled by the encoder's internal muxer. - **Encoder firmware/software version** - Known bugs in specific encoder firmware versions from manufacturers such as Sencore, Ateme, Elemental, and others can generate CC errors. Check the manufacturer's release notes for TS-related fixes. Update the firmware for the device for testing. **How to identify an encoder process issue:** - CC errors are present on a direct tap of the encoder output (before any network or Zixi involvement). - CC errors affect only specific PIDs, particularly lower-activity ones. - The issue began gradually or suddenly after the encoder had been running for an extended period (days/weeks) without a restart. - A cold restart of the encoder (full power cycle or process restart) resolves the CC errors immediately and cleanly. - Errors reappear after the same approximate uptime interval, confirming a runtime degradation pattern. **Root Cause:** Encoder misconfiguration or firmware bug producing CC errors at output. **Next Steps:** Correct the encoder settings (CBR, PCR interval, mux rate) or update firmware. If the errors appeared after a long runtime, perform a full encoder restart and monitor whether CC errors clear. If they do and then recur after extended uptime, document the interval and raise a firmware bug report with the encoder manufacturer. Request a clean TS capture directly from the encoder output port to confirm before and after. ### Step 3. Investigate the network path **What to check:** CC errors introduced during transit indicate packet loss, reordering, or duplication on the network between the source and the Zixi Broadcaster input. **How:** - In ZEN Master, check the **Network Quality** graph for the affected stream — high packet loss percentages directly correlate with CC errors. ![Not recovered packet loss ](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/SPZzEjh1-D-i-AkFSGI0--20260318-194244.png "Not recovered packet loss ") - In Zixi Broadcaster **Input Statistics **(select a stream in broadcaster and statistics will appear at the bottom of the Interface window) review: - **Packets Lost** - Any value above 0 that is not being recovered indicates network-level loss. - **ARQ/FEC Recovery Rate** - If recovery is failing to keep up, the network loss is exceeding what the Zixi protocol can correct. - **Jitter** - High or spiking jitter values suggest packet reordering or an unstable network path, both of which cause CC errors. ![Statistics showing Jitter, Packet Loss, FEC/ARQ](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/hcQIhn2pULIujcOoDjaMo-20260318-194807.png "Statistics showing Jitter, Packet Loss, FEC/ARQ") - Run a parallel path test — if possible, send a test stream over a different network path and compare CC error rates. - For streams transiting the public internet, check whether the issue is ISP-specific or time-of-day related (indicating congestion on a shared path). **Root Cause:** Network packet loss, jitter, or reordering in transit. **Next steps:** - Increase the Zixi Latency Buffer on the input — a higher latency setting gives the ARQ/FEC mechanism more time to recover lost packets before they are passed downstream. (We recommend a minimum of at least 1000 ms.) - If packet loss is severe, engage the customer's network team or ISP to investigate the transport path. - For persistent public internet issues, we recommend the customer consider a more stable transport option (dedicated circuit, managed IP transit, or bonded links). ### Step 4. Check Zixi Broadcaster input buffer and latency settings **What to check:** If the network appears healthy but CC errors are still present on the Zixi input, the Broadcaster's buffer configuration may not be correctly matched to the network conditions. **How:** In Zixi Broadcaster, navigate to **Inputs → \[Stream] → Edit** and review: - **Latency** - This defines the size of the jitter buffer and recovery window. If latency is set too low for the RTT of the connection, packets that arrive slightly late will be discarded rather than recovered, generating CC errors downstream. - Recommended starting point: set latency to at least **2–3× the measured RTT** between source and Broadcaster. - **Max Bitrate** - Ensure this is set high enough to accommodate the source stream's peak bitrate including TS overhead. An undersized max bitrate cap will cause the stream to drop incoming packets. - **FEC / ARQ settings** - Verify that the error correction mode configured on the input matches what the sending encoder supports. A mismatch disables recovery silently. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/RFb6CqFyksT56t-6X7BUP-20260318-195400.png" size="94" width="1737" height="427" position="center" caption="Input settings showing latency and max bitrate" alt="Input settings showing latency and max bitrate" darkWidth="1737" darkHeight="427" showCaption="true"} **Root Cause:** Latency buffer too small for network conditions, or input misconfiguration. **Advice:** Increase the latency value on the input. A conservative approach is to double the current value, observe CC error rate, and adjust from there. ### Step 5. Check server resources on the Broadcaster host **What to check:** On high-density Broadcaster deployments, resource exhaustion on the host server can cause the Broadcaster process to drop packets internally, generating CC errors that are not network-related. **How:** SSH into the Broadcaster host and check: \# CPU usage top The %Cpu(s) line at the top shows the breakdown of CPU usage (user, system, idle, etc.) To see usage per CPU core, press the 1 key while top is running. **top -H -o %CPU -b n1>top\_cpu.txt** This command shows the CPU usage only and writes it to a text document. \# Network interface errors and drops ip -s link show \ Provides detailed statistics for all network interfaces, including dedicated counters for errors and dropped packets. Also check the Broadcaster host's NIC receive buffer drops: ethtool -S \ Look for fields with names like rx\_dropped, rx\_queue\_0\_drops, rx\_discards, nic\_rx\_dropped, or similar driver-dependent counters. Any non-zero RX drop values indicate that packets are being discarded at the NIC level before Zixi even processes them. **Root Cause:** Server CPU overload, memory pressure, or NIC buffer exhaustion causing internal packet drops. **Next Steps:** - Reduce the number of streams on the affected Broadcaster or redistribute load across multiple instances. - Increase NIC ring buffer size. To increase the Network Interface Card (NIC) ring buffer size in Linux and reduce packet drops, use ethtool -G \ rx \ tx \ to set both Receive (RX) and Transmit (TX) buffers, typically to a maximum of 4096 or 8192. Run ethtool -g \ to view current and maximum supported ring buffer sizes. - For AWS deployments, verify that the instance type is appropriately sized for the number of streams and bitrates. Consider Elastic Network Adapter (ENA) optimized instance types for high-throughput workloads. - If using DPDK, validate DPDK configuration is applied correctly for the interface and kernel version in use. ### Step 6. Examine the output path and downstream decoder **What to check:** If no CC errors are reported on the Zixi input but the downstream IRD, decoder, or monitoring tool is reporting them, the issue may be introduced during Zixi output processing or on the Network segment between the Broadcaster and the decoder. **How:** - In Broadcaster **Outputs**, check the output statistics for the affected stream — compare CC error counts on input vs output. - If transcoding is active on the stream, CC errors can be introduced if the transcoder is dropping frames under load. Disable transcoding temporarily to isolate and test. - Capture the TS at the Broadcaster's output IP (e.g. via Wireshark on the LAN) and verify CC integrity at that point before it reaches the decoder OR send a duplicate test stream to a test target and verify. - For IRDs (e.g. Synamedia, Ericsson), be aware that some devices report CC errors for packets with the discontinuity indicator set, which Zixi may legitimately insert during stream reconnects or failover events. Confirm whether the CC errors correlate with connection events. **Root Cause:** CC errors introduced at output stage (transcoding, output misconfiguration) or falsely reported by decoder. **Advice:** - If transcoding is the cause, review transcoder resource allocation and reduce transcoding load. - If errors correlate with reconnects, these are expected transient events. Advise the customer that their decoder should tolerate the discontinuity indicator per MPEG-2 TS specification. - If false positives from the decoder are suspected, cross-reference with a second analysis tool (TSReader, VLC) to confirm whether CC errors are genuinely present in the TS. ### Troubleshooting Decision Tree CC errors reported on stream Present at encoder output? **→** YES **→** Encoder issue (Step 2) Network packet loss / jitter? **→** YES **→** Network / Latency issue (Steps 3–4) Server resources exhausted? **→** YES **→** Host resource issue (Step 5) Errors only at output / decoder? **→** YES **→** Output / Decoder issue (Step 6) No clear cause found **→** Capture full TS at input and output and escalate to Zixi Support ### Escalation Checklist When escalating to Zixi Support, you **must** include as much as possible of the following so that the team may investigate the issue: - Broadcaster version and OS - Stream name and connection type (Push/Pull, protocol used) - CC error count over time (input and output statistics screenshot) with time stamps. - Zixi Broadcaster log covering the period of errors (/var/zixi/broadcaster/log/) - Network path description (public internet, dedicated circuit, AWS region, etc.) - Latency and FEC/ARQ settings on the affected input - TS capture at Broadcaster input (Wireshark .pcap or TSReader analysis if available) - Notes on any recent changes to encoder, network, or Broadcaster configuration [title] Broadcaster on Windows: ZEN Master shows "authorization plugin error ... was not OK (60)" [path] Troubleshooting/ZEN Master - Errors and Troubleshooting/ ### ERROR In **ZEN Master**, the Broadcaster raises an authorization alert (you may see it as either an Error or a Warning - they are the same issue): ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/4em88J-NNCQtviVeP1FAk_image.png) ```none Broadcaster authorization plugin error: SSL peer certificate or SSH remote key was not OK (60) ``` In the **Broadcaster log** you will see the following line (logging set to Warning for HTTP Upload or higher): ```null curl_easy_perform failed (60): SSL peer certificate or SSH remote key was not OK (60) ``` ### ISSUE A ZEN Master–managed Broadcaster authorizes streams by making a secure (HTTPS) call back to ZEN Master. To trust that connection, the Broadcaster on Windows relies on the certificates in the **Windows Trusted Root Certification Authorities store**. ZEN Master's certificate is issued by Amazon and its trust chain requires the **Amazon Root CA 1** certificate. If that root is **not present** in the Windows root store, the Broadcaster cannot verify the connection and the authorization call fails with error **60** on every attempt. **Important:** A web browser or a PowerShell Invoke-WebRequest test to the same address will usually succeed even when the Broadcaster fails, because Windows and browsers validate certificates differently than the Broadcaster does. A successful browser test does **not** rule out this issue, trust the Broadcaster's own log. This issue is **not** caused by an expired certificate or an incorrect system clock. ### RESOLUTION Install the **Amazon Root CA 1 **certificate into the Windows root store, then restart the Broadcaster. Run all commands in an **elevated (Administrator) PowerShell **on the Broadcaster host. 1. **Confirm the root is missing** :::CodeblockTabs{indent="2"} ```powershell Get-ChildItem Cert:\LocalMachine\Root | Where-Object { $_.Subject -match "Amazon Root CA 1|Starfield Services" } | Select-Object Subject, Thumbprint ``` ::: :::Paragraph{indent="2"} If **Amazon Root CA 1 **is not listed (you may see only "Starfield Services Root Certificate Authority - G2"), continue. ::: :::Paragraph{indent="3"} ::: 2. **Install Amazon Root CA 1** :::Paragraph{indent="1"} **Option A: **Download the certificate from Amazon's official repository and import it ::: :::CodeblockTabs{indent="1"} ```powershell # Download: curl.exe -o AmazonRootCA1.cer https://www.amazontrust.com/repository/AmazonRootCA1.cer # Import into the Windows root store: Import-Certificate -FilePath .\AmazonRootCA1.cer -CertStoreLocation Cert:\LocalMachine\Root ``` ::: :::Paragraph{indent="1"} **Option B: **Capture the certificate directly from the ZEN Master connection and install it ::: :::CodeblockTabs{indent="1"} ```powershell $certs = @() $cb = [Net.Security.RemoteCertificateValidationCallback]{ param($s,$c,$chain,$e); $script:certs = @($chain.ChainElements | ForEach-Object { $_.Certificate }); $true } $tcp = New-Object Net.Sockets.TcpClient; $tcp.Connect("zen.zixi.com",443) $ssl = New-Object Net.Security.SslStream($tcp.GetStream(),$false,$cb) try { $ssl.AuthenticateAsClient("zen.zixi.com",$null,[Security.Authentication.SslProtocols]::Tls12,$false) } catch {} $ssl.Dispose(); $tcp.Close() $amazon = $script:certs | Where-Object { $_.Subject -match "CN=Amazon Root CA 1" } | Select-Object -First 1 $store = New-Object Security.Cryptography.X509Certificates.X509Store("Root","LocalMachine") $store.Open("ReadWrite") if ($amazon) { $store.Add($amazon) } $store.Close() ``` ::: :::Paragraph{indent="1"} ::: :::Paragraph{indent="1"} Confirm it is now present by re-running the Step 1 command — you should now see **Amazon Root CA 1 **listed. ::: :::Paragraph{indent="1"} ::: 3. **Restart the Broadcaster** **** The (60) errors should no longer appear, and the authorization alert in ZEN Master will clear within a few minutes. [title] Bitrate above configured maximum - Update source configuration with a higher value [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/ ### ERROR "Bitrate above configured maximum - Update source configuration with a higher value" ![Bitrate above configured maximum](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/Jd9xdsry-jCXQYlBZqHge_error-bitrate-above-config-max.png "Bitrate above configured maximum") ### ISSUE ZEN Master raises this warning when an input receives more packets than its Max Bitrate allows. Resent (ARQ) and FEC packets are not counted, so the stream itself is arriving faster than the setting. This usually happens when Max Bitrate is set close to the feed's average rate and the feed bursts above it. ### RESOLUTION On a Zixi input, Max Bitrate sizes the buffer the Broadcaster uses to recover lost packets: enough packets to cover the latency, or 1 second if the latency is shorter. It does not cap the stream. If the feed runs above it, that buffer overflows and the extra packets count as not recovered. Set the input's Max Bitrate to about 1.5 times the feed's average rate. For a 20 Mbps feed, set 30 Mbps. Max Bitrate is in the input's advanced settings: add `?advanced=1` to the Broadcaster URL. In the API the parameter is `maxbr`. See [Sizing latency, buffer and max bitrate](docId\:oj4srP9fTjhYtmGyv7xJA). Do not set it far higher than needed. If Max Bitrate multiplied by the latency needs more than 524,288 packets, about 5.5 Gbps for each second of latency, the input reports "Max bitrate times latency too high". If the stream shows no not-recovered packets while this warning fires, you can turn the warning off in the input's event profile. [title] Target and Output Status & Error Reference [path] Troubleshooting/ZEN Master - Errors and Troubleshooting/ A target or output reports a state and, when something is wrong, an error reason. ZEN Master also raises alarms of its own. The messages below are the ones that most often cause confusion. For sources, see [Source Status & Error Reference](docId\:HODONx74L3mVaP1b3g79Z). | Message | What it means | What to do | | --------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Broadcaster output error: None** | The output was not connected, or was sending no data, and the Broadcaster gave no reason. "None" is the Broadcaster's empty error value. It is not a cause, and it does not mean the output is healthy. | Check the output's extended error and the Broadcaster Event Log for the same time. | | **Encryption mismatch (earlier versions: "Data is encrypted")** | The stream is Zixi-encrypted and has no decryption key on this Broadcaster. The output cannot turn it into a plain transport stream, so it sends nothing. | Set the decryption key on the input. | | **Zero Bitrate** | At least one bitrate sample since ZEN Master's last check read zero. With the rule's threshold at 0%, the first zero raises it, after any escalation delay set on the rule. | Check the source bitrate for the same time. | | **Not recovered packets** | Packets that were lost and not replaced before the latency window closed, plus packets dropped because the recovery buffer was full. If the sender sent nothing, this count does not rise. If the network dropped while the sender kept sending, the whole gap is counted when traffic returns. | Raise the latency or the input's Max Bitrate, or look at the network path. See [Sizing latency, buffer and max bitrate](docId\:oj4srP9fTjhYtmGyv7xJA). | | **Segment or playlist upload failed (HLS, S3)** | The Broadcaster gave up on an upload. It retries a segment at least 3 times, 500 ms apart, for up to four segment lengths plus 4 seconds. It gives up at once on HTTP 400 or 403. The Event Log records the upload only when it gives up, but the output status can show an error on each failed attempt. | Check the Event Log for "upload failed". A 400 or 403 means the storage refused the path or the credentials. | | **Activation failed, Timeout was reached (28)** | The Broadcaster could not reach the Zixi license server within 5 seconds, over HTTPS and then over HTTP. This is a network or firewall problem, not a problem with the key. A bad key returns a message from the license server instead. | Allow outbound TCP 443 and 80 to licensing.zixi.com (version 19) or license2.zixi.com (versions 16 to 18), then activate again. | [title] Certificate Error [path] Troubleshooting/ZEN Master - Errors and Troubleshooting/ ### ERROR Broadcaster Input Error: Certificate Error ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/-xHkWwwCF8je3pNl5_V_0_image.png) ### ISSUE DTLS is not enabled on the source broadcaster or the certificate has expired ### WORKAROUND The quick workaround for this is go into bx on INPUTS - on each affected stream check box for “Ignore TLS certificate errors” ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/gvnxhxOk8NSm0DxZT_Dd4_image.png) ### RESOLUTION Replace expired DTLS certificate on the source Broadcaster with an active certificate. [title] SRT Library Reference [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/ Reference: Broadcaster versions and their associated SRT Library Version 19 - SRT Library 1.5.6 Version 18.13+ - SRT Library 1.5.6 Version 18 - SRT Library 1.5.4 Version 17 - SRT Library 1.5.3 Version 16 - SRT Library 1.4.4 :::hint{type="warning"} SRT \< 1.5.6 is not recommended due to critical vulnerabilities found. Click [here](https://zixi.com/news/libsrt-fix/) for more information. ::: [title] Zixi Port Guide - Reference [path] Troubleshooting/Best Practices/ - *Port Guide: *[https://docs.zixi.com/how-to-guides/network-port-settings](https://docs.zixi.com/how-to-guides/network-port-settings) [title] Best Practices [path] Troubleshooting/ ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/jis5wv9vubwoelFzrXFPj-20260327-171538.jpg" size="84" width="1920" height="1080" position="center" showCaption="false"} This section covers best practice configuration for your broadcast streams - helping you prevent issues before they start and keep your streams stable and best quality for your clients. - [CC Errors on Failover Source (No-Merge/Stream Switch)](docId\:BRbhgP85BUj3NxWuIJAhP) - [Upgrade from CentOS to Alma Linux](docId:1UVGkLBwtI7en33kC3NS2) [title] Updating time in the Broadcaster causes a Disconnection [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/ ### ISSUE Updating the time within the broadcaster resulted in a disconnection. ### RESOLUTION This will happen when trying to change the time backwards. There is a security feature which will make the license go into an error state, which can cause a disconnection. This is to prevent customers from trying to extend the life of their license by changing the time. [title] HLS master playlists are not supported [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/Broadcaster API Errors/ ### ISSUE "HLS master playlists are not supported" error when creating a HLS source. ### CAUSE The issue is that you are passing a master playlist, whereas the API expects a media playlist. When using the ZM UI, it validates the playlist and, if it’s a master playlist, allows the user to select the media playlist they are interested in. However, when using the API, it’s up to the user to provide a valid media playlist. A master playlist is an HLS playlist that includes all available bitrates, while a media playlist is a single-bitrate playlist that lists only the segments for playback. Note: Some provided URL's are signed, and such URLs typically expire. If that happens, the broadcaster won’t be able to pull the playlist or its segments. ### RESOLUTION Provide a media playlist instead of a master playlist. [title] URL or RTMP Stream parameter missing [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/Broadcaster API Errors/ ### ISSUE "error": "URL or RTMP Stream parameter missing" error can result when pushing to a video streaming platform online. ### RESOLUTION You need to url encode the "url" and "rtmp\_stream" parameters, so the command becomes: (Example for a facebook live stream) http\://admin:1234\@127.0.0.1:4444/zixi/add\_output.json?type=rtmp\&stream=StreamName8\&id=StreamName8Output\&name=StreamName8Output\&url=rtmps%3A%2F%2Flive-api-s.facebook.com%3A443%2Frtmp\&rtmp-stream=123456789098765%3Fs\_bl%3D1%26s\_ow%3D10%26s\_psm%3D1%26s\_pub%3D1%26s\_sw%3D0%26s\_tids%3D1%26s\_vt%3Dapi-s%26a%3DAb2qAbiGRdI1ne6ABPrWqJ6e [title] Target redirected to Broadcaster but no connection - Verify firewall/network Error [path] Troubleshooting/ZEN Master - Errors and Troubleshooting/ ### ERROR "Target redirected to Broadcaster but no connection - Verify firewall/network" ### ISSUE This can happen when there has been an issue with the source or the target and they are currently on different broadcasters. They need to align on the same broadcaster for connectivity. ### RESOLUTION The best solution to this is to disable and re-enable the channel - This will force the Target to reconnect to a different broadcaster within the cluster to meet up with the source. You could also manually configure a specific broadcaster within the target configuration. [title] Broadcaster Authorization plugin error [path] Troubleshooting/ZEN Master - Errors and Troubleshooting/ ### ERROR The "Broadcaster Authorization Plugin" error means that either someone has changed the authentication settings on the broadcaster or something is preventing the Broadcaster from being able to do authentication calls against ZEN Master. The Broadcaster does a health check on the authorization server periodically - if that fails but it's still connected to ZEN Master via the tunnel ZEN will catch that and report an error.' ### RESOLUTION The issue will always be related to network or DNS. Ports below for ZEN Master must be open and IPs whitelisted. | 80/443 | TCP
  | Outbound\* | Communication to Zixi License server - 
* license.zixi.com * license2.zixi.com * 52.72.218.41 * 34.195.97.223 * 3.140.62.221 * 3.137.16.26
ZEN Master Backend Servers
* 18.210.103.157 * 23.20.44.73 * 34.200.88.233 * 34.238.1.65 * 35.170.111.151 * 52.4.9.203 | | ------ | ---------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | [title] Upgrade a broadcaster through ZEN Master [path] Troubleshooting/ZEN Master - Errors and Troubleshooting/ - Locate your broadcaster within ZEN Master - Select the dropdown from the "More Actions" menu (three dots) - Select "Install version" ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Go8-mlAbTGZHYjW2Zc5WF-20260211-232354.png) - Select the version you wish to upgrade to in the "New Broadcaster Version" selection box - Click "Install" ![Upgrade configuration window screenshot](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Pk2nUJbyaqHeuphI8O4yd-20260211-232639.png "Upgrade configuration window screenshot") :::hint{type="warning"} Please note: this process includes an automatic restart of the broadcaster ::: - ZEN Master will go ahead and install the new version of the broadcaster, reload your configuratio and restart the braodcaster. [title] Unable to Allocate processing broadcaster(s) Error [path] Troubleshooting/ZEN Master - Errors and Troubleshooting/ ### ERROR The error "Unable to Allocate processing Broadcaster(s)" The issue is caused by the target configuration, on the source preference it had a specific source from the current channel selected. When switching channels, that source doesn’t exist on the new channel and prompts the error. ### WORKAROUND As a work around change the target’s Source Preference to “Any” before making any channel changes. [title] Source not found in cluster - Verify Broadcasters Status [path] Troubleshooting/ZEN Master - Errors and Troubleshooting/ ### ERROR "Error - Source not found in cluster - Verify Broadcasters status" ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/77YDx3l40-WRZ7-zLsoFv_image.png) ### ISSUE ### RESOLUTION Restart the Source and/or Channel to clear the error to force all stream targets & sources to sync up. If the error reoccurs after a minute or two Check the stream count is not over your stream limit for that broadcaster. [title] Broadcaster Authorization Configuration Error - Update via ZEN Master to correct [path] Troubleshooting/ZEN Master - Errors and Troubleshooting/ ### ERROR The "Broadcaster Authorization Configuration Error - Update via ZEN Master to Correct" error. ![Update Broadcaster Configuration window. Update Authorizatoin, DTLS and Ports configuration on the Broadcaster.](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/1AYaXpmWAGImIXxG87CBl_screen-shot-2022-07-19-at-54042-pm.png "Update Broadcaster Configuration window") ### RESOLUTION To solve this click on the Broadcaster in ZEN Master, scroll down to find the link for “Update Broadcaster Configuration,” and click it. This will resolve the issue. In the Broadcaster UI, under Settings > Authorization, when the Broadcaster is in error, this setting will be “None.” After you update the configuration in ZEN Master, it will be changed to “HTTP Server” and have the relevant ZEN Master URL in the field. [title] Content Analysis error: Video is not changing for more than 30 seconds [path] Troubleshooting/ZEN Master - Errors and Troubleshooting/ ### ERROR "Content Analysis error: Video is not changing for more than 30 seconds" ### ISSUE This Content Analysis (CQA) error is raised when a source's video stops changing for longer than the configured freeze threshold. The full message identifies the affected PID, e.g. "*Video is not changing for more than 30 seconds on PID \*". 30 seconds is the default, not a fixed value. The threshold is the source's Frozen Video Minimal Duration setting (`freeze_detection_timeout_sec`) and can be changed per source in ZEN Master, if that source has a different value, the message and detection time reflect it. It is most commonly seen when a **slate/static image** is used as a source, or when the video genuinely **freezes**. When the picture is frozen you will typically also see the companion Content Analysis errors for the source (e.g. "*Frozen Frames detected in Source*" and, if audio has also stopped, "*Silent Audio detected in Source*"). ### RESOLUTION - Confirm whether the source is intentionally a slate/static feed (expected) or genuinely frozen upstream. - If it's a false alarm for a deliberately static feed, raise the source's **Frozen Video Minimal Duration** or exclude the PID from CQA (Source > Advanced > ignored CQA PIDs). - If the video is genuinely frozen, investigate the upstream encoder/source path. [title] Decryption Error - Verify or configure decryption key Error [path] Troubleshooting/ZEN Master - Errors and Troubleshooting/ ### ERROR "Error - Decryption Error - Verify or configure decryption key" Error. ### ISSUE The decryption key entered is incorrect ### RESOLUTION Check the correct spelling & re-enter the correct decryption key info, or create a new decryption key. [title] 502 Bad Gateway Error [path] Troubleshooting/ZEN Master - Errors and Troubleshooting/ ### ERROR 502 Bad Gateway Error within ZEN Master while attempting to access a Broadcaster ### CAUSE 502 Bad Gateway means that the tunnel is not connected or that it's not pointing at the correct port - potential DNS issue. ### RESOLUTION - Check for any issues on the machine hosting the Broadcaster, that it has not crashed and is running all services as per normal operation - Check your internet is working from the machine hosting the Broadcaster - Check your DNS configuration - Restart the host machine - Consult with your local network team [title] RIST Simple Profile shows a Bitrate - status: not connected [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/ ### ERROR RIST Simple Profile shows a Bitrate, status is not connected. Stream stays "Offline" Shows a bitrate in Broadcaster Stats, but does not connect (Stays Offline) and shows no bitrate at the stream level. ### RESOLUTION The problem is the the firewall blocking the RTCP port in the receiving side. The RIST simple profile requires a configuration change to open both P and P+1 ports. If you add a RIST target, you should: - Run RIST stream on an EVEN-numbered port. - Open both the EVEN-numbered port and its incremental neighboring port. i.e. 50002,50003. [title] Request failed with status code 500 [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/Broadcaster API Errors/ ### ISSUE Receiving generic Error: Request failed with status code 500 for specific commands This would indicate there is something wrong in the API Request. ### RESOLUTION The easiest way to troubleshoot syntax issues with API is to create the Source via the ZM UI and have Developer Tools running in the browser. This will show you the syntax that is being used in the backend via API during your requested command. [title] Encoder Bitrate Spike Troubleshooting Guide [path] Troubleshooting/General Troubleshooting/ # 1. What Is an Encoder Bitrate Spike? A bitrate spike is a short-duration burst where the encoder's output bitrate significantly exceeds its configured target or nominal rate. Spikes are distinct from a general bitrate increase — they are transient, typically lasting from one to several seconds, and the instantaneous rate during the spike can be several times higher than the average bitrate. Spikes are a normal characteristic of many encoding modes. The problem arises when the downstream transport path, multiplexer, or receiving device cannot absorb the burst — at which point the consequences range from packet loss and buffer overflow to complete stream failure. When a customer reports downstream errors, start by establishing a bitrate profile over time in ZEN Master or Zixi Broadcaster to confirm whether spikes are occurring and correlate them with the timing of reported errors. ![An example of spikes - audio clipping](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/uWn72XTw6W3KGO3gHL2zO-20260527-184648.png "An example of spikes - audio clipping") # 2. Why Encoders Produce Bitrate Spikes Understanding the cause of the spike determines the correct fix. The most common sources are: •       **VBR and Constrained VBR encoding** — VBR allocates bits based on scene complexity. Scene changes, fast motion, and cuts to detailed frames cause large I-frames or high-complexity P-frames that temporarily exceed the average bitrate target by a significant margin. This is the most common cause. •       **I-frame size at scene changes and cuts** — I-frames are self-contained and significantly larger than P-frames or B-frames. Frequent cuts, graphics overlays, and lower thirds all force I-frames. Sports, news, and live events with heavy graphics are more susceptible than static content. •       **CBR with insufficient VBV buffer** — True CBR uses a buffer model (VBV/HRD) to constrain output. If the VBV buffer size is set too large relative to the target bitrate, the encoder is permitted to emit large bursts and pay them back over a long window. At the physical output this looks like spikes even though the encoder considers itself CBR. •       **Encoder rate control instability** — Software encoders or hardware encoders under high CPU/processing load can exhibit rate control instability, producing oscillating spikes at regular intervals, particularly at scene changes. •       **GOP structure and keyframe interval** — A long GOP accumulates a large debt of predicted frames between I-frames. When the I-frame is finally emitted it can be disproportionately large. Shorter GOPs produce smaller, more frequent I-frames and a flatter bitrate profile. •       **Audio encoding** — Some audio codecs (AC-3/Dolby Digital and certain AAC implementations) can create brief spikes on loud transients or complex multichannel audio. Usually small relative to video, but proportionally significant on low-bitrate streams. # Step 1 . Establish a Bitrate Profile Over Time ### What to check Before diagnosing the cause or fix, confirm that spikes are actually occurring and characterize their pattern. ### How •       In ZEN Master, navigate to the affected source and review the **TR101 histogram** and bitrate graph over an extended period. •       In Zixi Broadcaster, go to **Inputs → \[Stream] → Statistics** and review the bitrate graph. Look for: :::Paragraph{indent="1"} ◦      Peak-to-average ratio — if peaks are more than 1.5–2× the average, spikes are likely causing downstream issues. ::: :::Paragraph{indent="1"} ◦      Whether spikes correlate with visible content events (scene changes, fast motion, graphics). ::: :::Paragraph{indent="1"} ◦      Whether spikes occur at regular intervals (GOP boundary issue) or randomly (rate control instability). ::: Compare the bitrate graph against the timestamps of any downstream errors. If spikes and errors align, the spike is the root cause of the downstream symptom. :::hint{type="success"} **Root cause confirmed if: **Spike peaks exceed 1.5–2× average bitrate and timing aligns with downstream error events. ::: # Step 2. Check Encoder Rate Control Mode and VBV Settings ### What to check Incorrect encoder configuration is the most common cause of spikes that affect downstream infrastructure. Even a correctly configured encoder can develop issues after extended runtime. ### How On the encoder, confirm the following: •       **Rate control mode** — Is the encoder in CBR, VBR, CVBR, or CQ/CRF mode? VBR with no peak constraint and a loose VBV buffer will spike freely regardless of the average bitrate setting. •       **VBV buffer size** — For CBR contribution workflows, the VBV buffer should be sized at 1–2 seconds of the target bitrate or less. A large VBV buffer permits the encoder to emit bursts and recover them over a long window, which looks like spikes at the output. •       **Peak bitrate limit** — For CVBR or limited VBR, confirm a hard peak limit is set. The peak should be no more than 120–130% of the average target, and the VBV buffer must be sized to match the peak, not the average. •       **GOP size and keyframe interval** — Long GOPs (e.g. 250–300 frames) produce disproportionately large I-frames. For contribution workflows, GOPs of 1–2 seconds are standard. For satellite delivery, check the downstream decoder’s preferred keyframe interval. •       **Restart the encoder** — If rate control instability is suspected or errors appeared after extended uptime, perform a full encoder restart. Rate control feedback loop corruption can develop over time and is resolved by a clean restart. :::hint{type="success"} **Root cause: **Encoder in VBR/CVBR mode with no peak constraint, oversized VBV buffer, long GOP, or rate control instability. ::: Switch to CBR with a VBV buffer of 1 second or less for contribution workflows with a fixed bandwidth envelope. If VBR is required, set a hard peak bitrate limit at no more than 120–130% of the average target. Reduce GOP size to 1–2 seconds for contribution. If issues appeared after extended encoder uptime, restart the encoder and monitor for recurrence. # Step 3. Compare Encoder Output Bitrate vs. Transport Path Capacity ### What to check Confirm that the transport path is sized for the spike peak, not just the average bitrate. ### How •       Identify the hard ceiling of the downstream path. For a satellite workflow, this is the modulator’s maximum input rate. For a Zixi contribution link, this is the available bandwidth between the encoder and Broadcaster plus any configured bitrate limits. •       In Zixi Broadcaster, review **Inputs → \[Stream] → Statistics** and compare the peak bitrate observed in Step 1 against the configured max\_bitrate on the input. If the spike peak exceeds max\_bitrate, the Broadcaster’s internal ARQ/FEC buffers will be overrun during spikes. ![stream statistics ](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/croWb2HHKK3MqP9A0rK32-20260527-183937.png "Stream statistics") •       For satellite workflows, check the modulator’s input buffer alarm log. CC errors, PCR discontinuities, or input overflow alarms that correlate with spike timing confirm the modulator ceiling is being exceeded. •       For MPTS mux workflows, check the per-program allocated bitrate. A spike on one component stream can overflow that stream’s buffer in the mux, causing CC errors that affect all programs in the multiplex. :::hint{type="success"} **Root cause: **Spike peak exceeds transport path capacity, modulator input ceiling, or Zixi max\_bitrate allocation. ::: Set** max\_bitrate** on the Zixi input and Failover Group to 1.5–2× the highest expected peak bitrate to ensure adequate ARQ/FEC buffer headroom. For satellite workflows, switch the encoder to CBR with a hard peak at or below the modulator’s maximum input rate. For MPTS workflows, confirm per-program allocated bitrate accommodates the encoder peak, not the average. :::hint{type="warning"} ZEN Master has notifications on by default to raise an alert when the Max Bitrate is set outside of the recommended range. ::: ![Max bitrate warning in ZEN Master](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/RNNRhnIIKhb2I4pNaCPZk-20260527-190828.png "Max bitrate warning in ZEN Master") ![Stream configuration with max bitrate](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/2zcelC5JOeBJmreXcAo8a-20260527-183422.png "Stream configuration with max bitrate") # Step 4. Correlate Spikes with Content Events ### What to check The pattern of spikes identifies the specific fix required. ### How •       Review the bitrate graph alongside the content or event log. Note whether spikes occur at predictable moments. •       **Spikes at scene changes, cuts, or lower thirds** — I-frame size at cut points is the cause. Fix: tighten VBV buffer, switch to CBR, or reduce GOP size. •       **Spikes on fast-motion or high-complexity content** — VBR/CVBR peak exceeding transport ceiling. Fix: set a hard peak bitrate limit at or below downstream capacity. •       **Spikes at regular fixed intervals regardless of content** — GOP boundary I-frame overrun. Fix: shorten GOP interval and tighten VBV buffer. •       **Random spikes with no content correlation** — Rate control instability. Check encoder CPU load, thermal state, and rate control firmware version. Restart the encoder. •       **Spikes only during graphics or lower thirds** — Scene complexity on cut. Fix: shorter GOP, tighter VBV, consider CBR. :::hint{type="success"} **Root cause: **Pattern of spikes identifies encoder rate control mode, VBV/GOP configuration, or encoder process instability as the specific cause. ::: # Step 5. Check for Cascading Downstream Effects ### What to check Confirm that the bitrate spike is the direct cause of the downstream error events and not a coincidental overlap with a separate issue. ### How •       Review downstream device error logs (modulator, mux, IRD) and compare error timestamps against the spike timestamps captured in Step 1. •       CC errors, PCR accuracy alarms, or decoder resets that occur at the same time as peak bitrate events confirm the spike is the root cause. •       In Zixi Broadcaster, check **ARQ/FEC recovery rate** during spike periods. If recovery is failing to keep up during spikes, the spike is exceeding the retransmission buffer capacity. •       For IRDs and decoders, check whether the device logs show input buffer overflow or a decoder reset at the time of the spike. •       For MPTS workflows, check whether CC errors appear across multiple programs in the multiplex or are isolated to one — cross-program errors indicate a mux-level buffer overflow rather than a single-stream issue. :::hint{type="success"} **Root cause confirmed if: **Downstream error timestamps align with spike timestamps from the bitrate graph. ::: If cascading effects are confirmed, apply the encoder-side fix identified in Steps 2–4. If the encoder cannot be reconfigured, insert a CBR rate smoother between the encoder and the transport path to absorb spikes before they reach downstream infrastructure. Size the transport path bandwidth to the peak rate, not the average, and increase Zixi latency to provide additional ARQ recovery headroom during spike events. # 6. Summary Decision Tree Downstream errors suspected to be caused by encoder bitrate spikes Bitrate peaks more than 1.5–2× average in ZEN Master / Broadcaster graph? -> YES -> Spikes confirmed — continue below Spikes correlate with scene changes, cuts, or graphics? -> YES -> I-frame spike - tighten VBV buffer, switch to CBR, reduce GOP size **(Step 2) ** Spikes correlate with fast-motion or high-complexity content? -> YES -> VBR/CVBR peak exceeding transport ceiling - set hard peak limit **(Step 2)** Spikes occur at regular fixed intervals regardless of content? -> YES -> GOP boundary I-frame overrun - reduce GOP, tighten VBV** (Step 2)** Spikes random with no content correlation? -> YES -> Rate control instability - check CPU/thermal, restart encoder **(Step 2)** Spike peak exceeds modulator maximum input rate? -> YES -> Switch encoder to CBR at or below modulator ceiling** (Step 3)** Spike peak exceeds Zixi max\_bitrate on input or Failover Group? -> YES -> Set max\_bitrate to 1.5–2× highest expected peak, increase Zixi latency** (Step 3)** CC errors or PCR alarms at mux during spike events? -> YES -> MPTS buffer overflow - confirm per-program bitrate covers peak** (Step 3)** Encoder in CBR mode but spikes still visible? -> YES -> VBV buffer too large - reduce to 1 second of target bitrate or less **(Step 2)** Encoder config cannot be changed? -> Insert CBR rate smoother between encoder and transport path, size transport path bandwidth to peak rate with margin # 7. Escalation Checklist When escalating to Zixi Support, include as much of the following as possible: | **Item** | **Details / Location** | | -------------------------------------- | ------------------------------------------------------------------------------------- | | Broadcaster version and OS | Shown in Broadcaster UI header or /etc/zixi/version | | Stream name and connection type | Push/Pull, protocol used (Zixi, SRT, UDP, etc.) | | Bitrate graph over time | ZEN Master TR101 histogram or Broadcaster input statistics screenshot with timestamps | | Encoder rate control mode and settings | CBR/VBR/CVBR, VBV buffer size, peak bitrate limit, GOP size | | Downstream device error log | Modulator, mux, or IRD error log covering the period of errors with timestamps | | Broadcaster log file | /var/zixi/broadcaster/log/ — covering the period of errors | | max\_bitrate setting on affected input | From Inputs → \[Stream] → Edit | | Network path description | Public internet, dedicated circuit, satellite uplink, AWS region, etc. | | Recent configuration changes | Encoder, network, or Broadcaster changes prior to errors beginning | [title] SRT Target Shows "Failed to Connect" After Disabling Encryption or Upgrading Broadcaster [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/ ## SRT Target Shows "Failed to Connect" After Disabling Encryption or Upgrading Broadcaster If your SRT target is showing **"Failed to Connect" **error and a passphrase is (or was) configured, the issue is likely a passphrase mismatch between ZEN Master, the Broadcaster, and the receiving end. This article explains the two most common causes and how to resolve them. ![Failed to connect error in broadcaster](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/BRA6NxUbb2S714PXv8_7u_failed-to-connect.png) ![Failed to connect image in ZEN Master](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/AxUU-biuTxHDag9IIhllT_failed-to-disconnect.png) *Failed to connect error in both Broadcaster & ZEN Master* ### Symptoms - SRT target status shows **Failed to Connect** - A passphrase is saved in ZEN Master, but encryption is currently **disabled** on the target - Issue appeared after **disabling encryption** on the target, or after a **Broadcaster upgrade** - The target receiver still has a passphrase configured # Root Cause **1. Passphrase saved in ZEN Master with encryption disabled** When encryption is disabled on an SRT target in ZEN Master, any passphrase saved in the configuration is **not pushed to the Broadcaster**. If the receiving end still expects an encrypted stream with a passphrase, the connection fails due to a mismatch. **2. Broadcaster upgrade wiped the passphrase** A Broadcaster upgrade can sometimes clear the passphrase from the Broadcaster's local target config. If ZEN Master still shows a passphrase saved (with encryption disabled), the Broadcaster has no passphrase, but the receiver is still expecting one, again causing a mismatch. :::hint{type="warning"} **Key rule: **The passphrase configuration must be consistent across ZEN Master, the Broadcaster and the target receiver. Encryption must be "enabled" for a passphrase to propagate from ZEN Master to the Broadcaster. ::: # Resolution ### Option 1: Enable Encryption (Recommended if the receiver is expecting it) If the target receiver is configured with encryption enabled: 1. In ZEN Master locate the SRT target. 2. Enable **Encryption** on the target. 3. Confirm the correct passphrase is entered. 4. Save the configuration. ### Option 2: Fully Remove the Passphrase (If encryption is not required) If you want to run without encryption: 1. In ZEN Master, navigate to the SRT target. 2. **Remove the passphrase** from the target configuration (the field must be empty — not just disabled). 3. Save the configuration. 4. On the **target receiver**, also clear the passphrase from its configuration. 5. Confirm both ends have no passphrase and encryption is disabled 6. Confirm stream connects successfully. [title] Windows Broadcaster Will Not Connect to ZEN Master (SSH Tunnel / Key Permissions) [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/ ## What This Covers A Zixi Broadcaster installed on Windows shows as **Pending** or **offline** in ZEN Master even though the Broadcaster itself is running and its web UI (port 4444) is reachable. The cause is that the reverse-SSH tunnel the Broadcaster opens back to ZEN Master fails to start, almost always because of file ownership or permissions on the SSH private key or the `.ssh` directory used by the Windows service account. This is specific to Windows. Linux hosts are not affected in the same way. ## Symptoms - In ZEN Master, the Broadcaster never leaves **Pending**, or it flips to **offline** shortly after you complete *Step 5: Connect the Broadcaster*. - The Broadcaster service is running and the local UI at `http://localhost:4444` works. - The Broadcaster log / Windows Event log shows an SSH error referencing the `.ssh` path under the service profile, for example: ```powershell C:\Windows\System32\config\systemprofile\.ssh\... bad permissions Permissions for '...id_rsa' are too open. It is required that your private key files are NOT accessible by others. Load key "...": bad permissions ``` - The error appears immediately at tunnel start, not after a period of streaming. ## Root Cause The Broadcaster runs as a Windows service under the **LocalSystem** account. To reach ZEN Master it launches the bundled OpenSSH client (`ssh.exe`) and opens a reverse tunnel, supplying the private key downloaded from ZEN Master. Because the service uses the LocalSystem profile, SSH looks for its key material under: ```powershell C:\Windows\System32\config\systemprofile\.ssh ``` Modern OpenSSH on Windows 10/11 and Windows Server **strictly enforces ownership and ACLs** on the private key file and the `.ssh` directory. If the key file is owned by the wrong account, is readable/writable by groups such as *Users* or *Everyone*, or the `.ssh` directory does not exist or is not writable by the service account, OpenSSH refuses to use the key and aborts. The tunnel never comes up, so ZEN Master never sees the Broadcaster as connected. :::BlockQuote Note: the 64-bit Broadcaster installer ships its OpenSSH client as `ssh.exe` (the 64-bit build); the Feeder / 32-bit package ships a 32-bit `ssh.exe`. This matters only for workaround 5 below. ::: ## Step-by-Step Resolution Work through these in order. Steps 1–2 resolve the large majority of cases. ### 1. Pre-create and permission the `.ssh` directory Confirm the directory exists and is writable by the account the Broadcaster service runs as (LocalSystem by default): ```powershell C:\Windows\System32\config\systemprofile\.ssh ``` If it is missing, create it. Grant the Broadcaster service account (LocalSystem, or the dedicated service account if you changed it) **Full Control** of this directory, and remove broad inherited permissions for *Users* / *Everyone*. ### 2. Fix the private key file ownership and ACLs The private key must be owned by the service account and **not** readable or writable by any group or other user. In an elevated PowerShell, for the key file in that `.ssh` directory: ```powershell icacls "C:\Windows\System32\config\systemprofile\.ssh\" /inheritance:r icacls "C:\Windows\System32\config\systemprofile\.ssh\" /grant:r "SYSTEM:F" icacls "C:\Windows\System32\config\systemprofile\.ssh\" /remove "Users" "Authenticated Users" "Everyone" ``` (If the service runs under a named account rather than LocalSystem, grant that account in place of `SYSTEM`.) Restart the Broadcaster service and recheck status in ZEN Master. ### 3. Run the install / service with Administrator privileges If the directory and key cannot be created or re-permissioned, the installer or service may not have had sufficient rights. Reinstall or start the Broadcaster service as **Administrator** so it can create and lock down the `.ssh` directory correctly. ### 4. Verify the Remote Source Port matches ZEN Master A wrong tunnel port produces the same "offline in ZEN" symptom even when the key is fine. In the Broadcaster UI under **Settings → SSH Connections**, confirm the **Remote Source Port** (and Local Destination IP/Port) exactly match the values shown in the Broadcaster's **Config** instructions in ZEN Master. See [SSH Connections](https://docs.zixi.com/zixi-broadcaster-zec-current-version/ssh-connections) and [Step 5: Connect the Broadcaster](https://docs.zixi.com/quick-start/step-5-connect-the-broadcaster-broadcaster-ui). ### 5. (Last resort) Swap in the 32-bit `ssh.exe` In rare environments where the bundled 64-bit `ssh.exe` still fails the key check, replacing it with the 32-bit `ssh.exe` from the Zixi Feeder package (placed in the Broadcaster install directory in place of `ssh.exe`) has resolved the tunnel for some sites. Treat this as a workaround of last resort and note the change for support. ### 6. Re-download a fresh SSH key If the key may be corrupt or mismatched, generate/download a fresh key from ZEN Master (see [Step 3: Create an SSH Key](https://docs.zixi.com/quick-start/step-3-create-an-ssh-key)), re-apply it in the Broadcaster's SSH Connection, and re-apply the ownership/ACL fix from Step 2. ## Decision Tree - Broadcaster stuck Pending/offline in ZEN but local UI (4444) works? → continue. - Log references `.ssh` path / "bad permissions" / "too open"? → **YES** → key/directory permissions issue → **Steps 1–3**. - No permissions error, but still offline? → check **Remote Source Port** vs ZEN config → **Step 4**. - Permissions correct and port correct, still failing? → try 32-bit `ssh.exe` (**Step 5**) and/or a fresh key (**Step 6**). - Still failing after all of the above? → collect logs and escalate. ## Escalation Checklist Open a Zixi Support ticket and include: | Item | Details / Location | | --------------------------------------------------------- | --------------------------------------------------------------------------------- | | Broadcaster version and Windows OS/build | Broadcaster UI header; Windows version (10/11 / Server 2016/2019), 32- or 64-bit | | Broadcaster log / Windows Event log excerpt | The SSH error showing the `.ssh` path and the "bad permissions" / "too open" text | | Service account the Broadcaster runs as | LocalSystem or a named service account | | Current ACLs on the key file and `.ssh` directory | Output of `icacls` for both | | Remote Source Port configured vs. ZEN Master Config value | Broadcaster Settings → SSH Connections, and ZEN Master Broadcaster → Config | | Whether 32-bit `ssh.exe` swap was attempted | Yes/No | [title] Timeout error Troubleshooting Guide [path] Troubleshooting/General Troubleshooting/ A **Timeout** error in Zixi Broadcaster indicates that the connection attempt to a target destination has never received a response. This is almost always a network or firewall issue. The stream is being sent, but something between the sender and receiver is blocking or dropping it before it arrives. In the Broadcaster the stream status will display **"Timeout" **(full message: *"Timeout error, check network and firewall configuration"*) and the stream will fail to connect. ## Step-by-Step Resolution ### 1. Verify Destination Address and Port Check the configuration on the broadcaster side: - **Destination Address -** Confirm the IP address or hostname is correct and matches the configuration of the target/endpoint. - **Destination Port -** Confirm the port number matches the configuration on the receiver. Incorrect information here will cause a timeout. Confirm the correct values directly with the receiving party. ### 2. Check Firewall Rules on Both Sides Timeouts are most commonly caused by a firewall dropping traffic. You'll need to verify with the network team on both ends that the relevant port is open **in both directions.** - **Sending side -** Outbound traffic on the destination port must be open and permitted. - **Receiving side -** Inbound traffic on that same port must be open and permitted. :::hint{type="warning"} Many firewalls allow outbound traffic broadly but for security reasons inbound is restricted. Make sure that both INBOUND and **OUTBOUND **have been checked - not just one. ::: If you're using Zixi protocol (default ports **2077 **& **2088**) or a custom port, ensure both TCP and/or UDP rules are in place as appropriate for your transport type. ### 3. Test General Network Connectivity Before escalating, rule out any broader network issues on the host machine: - Can the machine reach the internet? - Can it reach the destination IP directly (e.g., via ping or traceroute)? - Is there any VPN, proxy, or routing policy that might be interfering? A successful ping doesn't guarantee the port is open, but a failed ping indicates a possible connectivity problem. ### 4. Escalate to Your Network Team If the above steps haven't resolved the issue, this is likely a network infrastructure problem outside the scope of your Zixi Software. Provide your network team with the following: - The **destination IP address and port** you're trying to reach - The **protocol** in use (Zixi, SRT, UDP, etc.) - The **direction** of the connection (push vs. pull) - Any firewall rule changes that may have been made recently Your network team will be best positioned to trace where the traffic is being blocked. ## Troubleshooting Decision Tree Destination Address correct? **→** NO **→** Verify IP/hostname with the receiving client & retry. Destination Port Correct? **→** NO **→ **Confirm port matches the config on the receiver & retry. Firewall - sending side is open? **→** NO **→ **Add Outbound rule open for the destination port Firewall - receiving side is open? **→** NO **→ **Add Inbound rule open for the destination port Host machine has internet & network connectivity? **→** NO **→ **Ping/traceroute from host to destination. Test machine can load internet webpages. Escalated to your local network team? **→** NO **→ **Provide team with IP, port, protocol, and direction. ## Escalation Checklist If all checks passed and the timeout persists then please open a Zixi support ticket. When escalating to Zixi Support, you **must** include as much as possible of the following so that the team may investigate the issue: Open a support ticket with Zixi and include: - Broadcaster version - A screenshot or log excerpt showing the timeout error - The destination address and port (or confirm they've been verified) - Any relevant firewall rule screenshots or network topology details [title] PCR Clock Drift Troubleshooting Guide [path] Troubleshooting/General Troubleshooting/ # What Is PCR? PCR (Program Clock Reference) keeps time for broadcast streams, similar to a metronome built into your video stream. The encoder taps out a beat as it creates the stream, and every device downstream relies on this timing to stay in sync. Technically, the PCR is a timestamp embedded inside specific packets in the MPEG-TS stream. The industry standard (ETSI TR 101 290) determines that these timestamps must arrive at least every 100ms (ideally every 40ms or less). **Why does it matter?** If that beat strays off time or out of sync, downstream devices get confused about how fast to play back the stream. Even if every single packet arrives perfectly with zero data loss, a bad PCR can still cause freeze frames, audio dropouts, macroblocking, or a decoder that gives up and resets. ## What Is PCR Clock Drift? PCR drift is what happens when the metronome is no longer keeping steady time. Instead of ticking at a stable rate, it speeds up/slows down/hiccups/jumps unpredictably. The key measurements to be aware of from TR 101 290 are: | Metric | Priority Level | What It Means | | ----------------- | -------------- | ----------------------------------------------------------------------------- | | PCR interval | P2 | Timestamps must arrive at least every 100ms | | PCR accuracy | P2 | Each timestamp must be within ±500ns of when it was actually sent | | PCR jitter | P2 | Timestamps shouldn't vary wildly from one packet to the next | | PCR discontinuity | P2 | Sudden jumps in the timestamp must be flagged so decoders know to expect them | **Drift vs. discontinuity:** A discontinuity is a deliberate, flagged jump e.g. at a splice point. Drift is a slow, unflagged creep away from the correct clock rate. Decoders aren't warned about drift, which is what makes it harmful. ## Common Causes ### 1.1 The Encoder's Clock Isn't Locked to a Stable Reference This is the most common cause. An encoder needs a reliable external time reference such as GPS, PTP/IEEE 1588, or house sync to keep its internal clock accurate. Without it, the clock will wander. This is especially common with: - **Software encoders** running on regular computers, where other processes competing for CPU time can throw off timing precision - **Hardware encoders** that have lost their external reference signal - **Any encoder** that has been running for a long time without a reference. Even good internal clocks drift over hours ### 1.2 Network Jitter Being Mistaken for Clock Drift PCR timestamps are written at the encoder, but they have to travel across a network to reach the decoder. If the network introduces variable delay (jitter), those timestamp-carrying packets arrive at irregular times. The decoder sees the timestamps arriving unevenly and registers PCR errors even though the encoder's clock was perfectly fine. There is an important distinction with PCR Packets: - **Network jitter** → PCR packets arrive unevenly - **Encoder clock issues** → the PCR *values themselves* are wrong Both look identical in a stream analyzer as TR 101 P2 errors, so you need deeper analysis to find which one you're dealing with. ### 1.3 Remultiplexing or Transcoding Without Updating the Timestamps When a device re-multiplexes a stream (changing PIDs, adding or removing streams, or adjusting the bitrate) it needs to regenerate the PCR timestamps to reflect the new stream timing. If it just passes the original timestamps through unchanged, they'll no longer be accurate for the modified stream. This is a common problem in multi-hop contribution chains. ### 1.4 CBR Stuffing Done Incorrectly When a variable bitrate stream is shaped to a fixed (CBR - Constant Bitrate) output, the device adds null packets to fill the gaps. If this process doesn't also correctly pace the PCR timestamps, the output clock will be wrong even if the bitrate looks right. ### 1.5 Buffering Without Restamping Any device that buffers the stream (a gateway, a time-shift server, a cloud ingest point) delays delivery of the packets. If it doesn't update the PCR timestamps on the way out, the downstream device receives timestamps that describe the past rather than the present. Well implemented gateways (including Zixi Broadcaster) handle this correctly, but not all devices do. ### 1.6 Multi-Hop Encode/Decode Chains Every time a stream is decoded and re-encoded, there's a chance timing accuracy is degraded. In chains with multiple transcode hops, these small errors can compound. The further downstream you go from the original encoder, the more likely PCR accuracy has drifted. ## How It Shows Up Downstream The impact depends on how bad the drift is and how tolerant the receiving device is. | Drift Severity | What You'll Typically See | | ---------------------------------- | ------------------------------------------------------------------------------------- | | Minor (within P2 limits) | No visible picture issues; P2 warnings in a stream analyzer only | | Moderate (exceeds P2, within P1) | Occasional freeze frames, audio glitches, or brief stalls | | Severe (exceeds P1 or large jumps) | Repeated decode failures; IRDs reset or re-acquire; audio or video drops out entirely | | Unflagged discontinuity | Decoder locks up or produces garbled output until it re-syncs | :::hint{type="warning"} Different devices have very different tolerances. VLC on a laptop might play back a drifting stream without any visible issues, while a professional IRD on the same stream will throw alarms and attempt to relock. A stream that looks fine on a preview monitor may still be causing problems further down the chain. ::: ## How to Diagnose & Troubleshoot PCR Clock Drift ### Step 1. Capture and Analyze the Stream Use a stream analyzer (TSReader, Wireshark, Elecard StreamEye, Tektronix Sentry, Pixelmetrix DVStation etc). Check for: - **PCR interval violations** - gaps of more than 100ms between PCR packets (P1 error) - **PCR accuracy errors -** timestamp values deviating beyond ±500ns (P2 error) - **PCR jitter** - large swings between consecutive timestamps - **Unflagged discontinuities** - sudden PCR jumps with no discontinuity indicator set ### Step 2. Work Out Where It's Coming From Capture at two points - **as close to the encoder as possible**, and at the** receiving end**. Compare: - Errors **at the encoder output** → the encoder clock is the problem - Errors **absent at the encoder but present at the receiving end** → network jitter, or an intermediate device is introducing drift - Errors **appearing after a specific device** → that device is the likely culprit ### Step 3. Check the Encoder's Reference Clock On the encoder, check and confirm: - Is it locked to an external reference (GPS, PTP, house sync)? - What does the reference lock indicator say? - Has it been running for a long time without a reference? - For software encoders: was CPU load high around the time errors appeared? ### Step 4. Check Whether Intermediate Devices Are Restamping PCR For each device after the encoder (multiplexers, gateways, transcoders) confirm whether it regenerates PCR timestamps on output. Any device that is known to pass timestamps through unchanged is a risk point if it modifies the stream in any way. ### Step 5. Look at the Error Trend Over Time A single snapshot of P2 errors can provide misleading information. Check how error counts change over time: - **Errors gradually accumulating over hours** → slow oscillator drift; check reference lock - **Errors appearing in bursts at regular intervals** → likely a scheduling or processing issue - **Errors correlated with network events** → jitter-induced PCR arrival problems, not encoder clock issues ## Common Fixes | Root Cause | Fix | | ------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | | Encoder not locked to a reference | Lock to GPS, PTP (IEEE 1588), or house sync | | Software encoder on a busy CPU | Reduce CPU load; use a dedicated encoding host; consider hardware encoding for critical paths | | Multiplexer not regenerating PCR | Enable PCR restamping in the mux configuration, or replace it with a device that does | | Network jitter causing timestamp arrival problems | Apply QoS or use a dedicated path; add a jitter buffer or PCR smoother at the receive end | | Transcoder passing through old timestamps | Enable PCR regeneration on the transcoder output | | Too many encode/decode hops | Reduce transcode hops; use baseband or lossless contribution for upstream legs where possible | | Unflagged discontinuity from an upstream source | Fix flagging at the encoder or mux; if the source is out of your control, insert a PCR restamper at ingest | ## PCR Drift in Zixi Workflows Zixi Broadcaster transports the stream exactly as it receives it, it does not modify PCR values in transit. This means: - **Zixi is not a source of PCR drift.** It carries whatever is in the stream, good or bad. - If errors are present on the input, they will be present on the output. - For passthrough outputs (UDP, Zixi push/pull), the stream is delivered as received. - For HLS and adaptive outputs, Zixi will regenerate timing. :::hint{type="warning"} If TR 101 PCR errors are showing up on a source in ZEN Master, start your investigation at the encoder feeding that source, **not** at the Broadcaster or ZEN Master itself. ::: ## Troubleshooting Decision Tree PCR errors reported on stream The first best step is to restart the encoder and check if the issue is still occurring. If it is then work through the following Troubleshooting steps. P1 error: PCR interval >100ms? **→** YES **→** Capture at encoder output and check every mux in the chain P2 error: PCR accuracy violation? **→** YES **→ **Capture at encoder output to determine encoder-side vs. network-side Errors correlated with network events? **→** YES **→** PCR arrival jitter — check path quality and jitter metrics Errors appearing after a specific device? **→** YES **→** That device is not regenerating PCR correctly - check PCR restamp settings Encoder reference lock indicator showing a fault? **→** YES **→** Lock encoder to GPS, PTP, or house sync Errors on a software encoder under load? **→** YES **→** Reduce CPU load or move to hardware encoding Errors accumulating gradually over hours? **→** YES **→** Oscillator drift - check and restore encoder reference lock Unflagged PCR discontinuity jumps? **→** YES **→** Fix at encoder or insert a PCR restamper at ingest No clear cause found **→** Capture TS at encoder output and at receive point and escalate to Zixi Support ## Escalation Checklist When escalating to Zixi Support, include the following: - Broadcaster version and OS - Stream name and connection type (Push/Pull, protocol used) - TR 101 290 error type (P1/P2) and error counts over time - Stream analyzer output or screenshots showing PCR metrics - Network path description (public internet, dedicated circuit, cloud region, etc.) - Encoder make, model, and firmware version - Encoder reference clock source and current lock status - Whether errors are present at encoder output or only at receive point - Any recent changes to encoder, mux, network, or Broadcaster configuration - TS capture at encoder output and/or Broadcaster input (Wireshark .pcap or TSReader analysis) [title] Source Status & Error Reference [path] Troubleshooting/ZEN Master - Errors and Troubleshooting/ A source (input) reports a **connection state** plus, when something goes wrong, an **error reason**. The states and error reasons below are the full set a source can display. ## Connection States | Status | Meaning | | ---------------- | ------------------------------------------------------------------------ | | **Offline** | The source is not active. It is stopped or has not started yet. | | **Connecting** | The source is attempting to establish its connection for the first time. | | **Reconnecting** | The source lost its connection and is trying to re-establish it. | | **Connected** | The source is connected and receiving data normally. | ## Error Reasons ### Network & Connection | Status | Why it happens | | ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | | **Resolve** | The hostname of the remote source could not be resolved via DNS. Usually a bad address or a DNS problem. | | **Timeout** | No response or no data was received within the allowed time. The remote end is unreachable, too slow, or has gone away. | | **Network** | A general network failure, or the network subsystem could not be started. | | **TCP connect failed** | A TCP connection to the remote source could not be established (wrong address/port, blocked by firewall, or remote not listening). | | **Connection closed** | The remote end closed the TCP connection. | | **Failed to connect** | The connection attempt failed. | | **Failed to bind** | The local socket could not be bound to the requested address/port. | | **Failed to enter listening state** | The source could not start listening for incoming connections. | | **Port in use** | The port the source needs is already being used by something else. | | **Failed to open port** | The required port could not be opened (the source is busy or the port is unavailable). | | **Socket open error** | A network socket could not be created or opened. | | **Too large MTU** | The configured packet size (MTU) exceeds what is allowed. | | **Redirected** | The server redirected the source to a different host (normally handled automatically). | ### Protocol & Stream Negotiation | Status | Why it happens | | ----------------------------------- | -------------------------------------------------------------------------------------- | | **Protocol** | A protocol-level message could not be parsed, or the remote reported a protocol error. | | **Full** | The remote server is at capacity and cannot accept the connection. | | **Rejected** | The connection was refused. Usually this stream is already connected elsewhere. | | **Reconnected** | The source was replaced by a newer connection (e.g. during failover). | | **Remote stream closed** | The remote side closed the stream. | | **Stopped** | The source was stopped manually. | | **Limit** | A configured limit was reached. | | **Not Supported** | A requested feature or operation is not supported. | | **Illegal name** | The stream name is invalid or improperly formatted. | | **Double RTP header** | A packet arrived with a malformed (double) RTP header. | | **Payload is not transport stream** | The incoming data is not valid MPEG transport stream. | ### Source Availability | Status | Why it happens | | ---------------------------------- | --------------------------------------------------------------------------------------------- | | **No Source** | The requested stream was not found on the remote server, or no stream is currently available. | | **Over max outputs configuration** | The source has reached its configured maximum number of outputs/connections. | | **Multiple sources detected** | More than one source is broadcasting to the same stream simultaneously (a collision). | | **No multicast data** | The source could not join the multicast group, or no multicast data is being received. | | **NDI Stream not found** | The specified NDI stream could not be located on the network. | ### Authentication, Licensing & Security | Status | Why it happens | | --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | | **Authentication** | Authentication with the remote source failed (bad credentials). | | **Licensing** | The connection failed due to a licensing restriction on the remote. | | **Certificate error** | The security certificate presented during a secure (DTLS) handshake was invalid. | | **DTLS handshake error** | The encrypted (DTLS) handshake failed, or encryption was unexpectedly disabled. | | **Wrong DTLS-SRP username or password** | The DTLS-SRP credentials supplied were incorrect. | | **Data is encrypted** | The data is encrypted and cannot be processed (a key mismatch, missing key, or an attempt to re-encrypt already-encrypted data). | ### Bitrate & Quality | Status | Why it happens | | ----------------------------------------------- | ------------------------------------------------------------------------------------ | | **Zero bitrate** | The source stream is reporting no data flow (zero bitrate). | | **Insufficient bitrate** | The source bitrate is too low for what is required. | | **Remote version doesn't support high bitrate** | The remote device's software version cannot handle the required high bitrate. | | **Max bitrate times latency too high** | The combination of maximum bitrate and configured latency exceeds the allowed limit. | | **Performance** | A performance threshold was exceeded (the system could not keep up). | ### Data Integrity | Status | Why it happens | | --------------------------------- | -------------------------------------------------------------------- | | **Overflow** | A buffer overflowed: data arrived faster than it could be processed. | | **Compression error** | An incoming packet could not be decompressed. | | **Muxing error** | The stream could not be re-muxed/combined correctly. | | **Multiplex error** | A multiplexing operation failed. | | **Bad PID mapping configuration** | The PID remapping configuration is invalid. | | **Error concealer** | The error-concealment subsystem encountered a problem. | | **CBR Padder error** | The constant-bitrate padding subsystem failed. | | **PID interleaver error** | The PID interleaver subsystem failed. | | **Frame thinner error** | The frame-thinning subsystem failed. | ### RTMP Sources | Status | Why it happens | | ----------------------------- | ------------------------------------------------------------------------------- | | **RTMP connect failed** | The RTMP connection could not be established. | | **RTMP handshake failed** | The RTMP handshake negotiation failed. | | **RTMP stream failed** | The RTMP stream operation failed. | | **RTMP publish failed** | The RTMP publish operation failed. | | **RTMP play failed** | The RTMP play operation failed. | | **RTMP protocol malfunction** | The RTMP protocol could not be parsed or handled correctly. | | **Timeout, Bad stream data** | RTMP stream analysis timed out because the incoming data was bad or incomplete. | | **Unsupported encoding** | The RTMP stream uses an encoding that is not supported. | | **Akamai authentication** | Authentication to Akamai failed. | ### Adaptive / HLS / DASH | Status | Why it happens | | ------------------------------------- | ------------------------------------------------------------------------------------ | | **Adaptive stream** | An adaptive stream was received but no adaptive handler is configured to process it. | | **Source not adaptive** | The source does not support adaptive bitrate. | | **Unaligned timestamps** | The adaptive stream has timestamps that are not aligned, preventing segmentation. | | **Failed to create segment** | A timeout occurred while creating an adaptive stream segment. | | **No valid segmentation point found** | No suitable point was found to split the stream into segments. | | **HLS/DASH failed to upload** | An HLS or DASH segment failed to upload to its destination. | | **HLS disabled** | HLS output is disabled. | | **MDP disabled** | DASH (MPD) output is disabled. | | **Head request failed** | An HTTP HEAD request (used to probe an adaptive source) failed. | ### RIST | Status | Why it happens | | ---------------------------------------------- | ----------------------------------------------------------------------------------------------------- | | **Didn't receive RTCP packets for 10 seconds** | A RIST Simple Profile source stopped receiving the expected RTCP control packets for over 10 seconds. | ### Files & Storage | Status | Why it happens | | ------------------------- | -------------------------------------------------- | | **End of file** | A file-based source reached the end of the file. | | **Local file error** | An error occurred accessing the local file system. | | **Remote file error** | An error occurred accessing a remote file system. | | **Invalid file** | The source file is invalid or corrupt. | | **file not found** | The source file could not be found. | | **can not open file** | The source file could not be opened. | | **Not enough disk space** | The disk ran out of space. | ### System & Hardware | Status | Why it happens | | ----------------------------- | --------------------------------------------------------- | | **Out of memory** | A memory allocation failed. | | **Failed to create sink** | An output (sink) for the source could not be created. | | **Transcoder** | The transcoding subsystem encountered an error. | | **Failed to start program** | An external helper program could not be started. | | **Failed to access program** | Communication with an external helper program failed. | | **Failed to load library** | A required software library could not be loaded. | | **Driver not up to date** | The hardware driver is too old. | | **Cuda not up to date** | The CUDA (GPU) version is too old. | | **P2P error** | A peer-to-peer connection was aborted. | | **Destination address error** | The destination address could not be found or is invalid. | ### DRM | Status | Why it happens | | ----------------------------- | --------------------------------------------------- | | **DRM license or cpix error** | A DRM license or CPIX configuration error occurred. | | **DRM encryptor init error** | The DRM encryptor failed to initialize. | | **DRM encrypt error** | A DRM encryption operation failed. | | **DRM wrong flow** | DRM operations were performed in an invalid order. | | **DRM missing buffer** | A required buffer for DRM was missing. | | **DRM not supported feature** | A requested DRM feature is not supported. | ### Licensing (License Manager) | Status | Why it happens | | ----------------------------------------------------- | --------------------------------------------------------------------- | | **License file not found** | The license file is missing. | | **License file wrong version** | The license file is the wrong version. | | **License file wrong format** | The license file is malformed. | | **License file sign** / **License file verification** | The license file's signature could not be verified. | | **License expired** | The license has expired. | | **License limit** | A licensed limit has been reached. | | **License value out of range** | A license value is outside its allowed range. | | **Unknown license name** | The license name is not recognized. | | **The license is not present in the license file** | The required license entry is missing from the file. | | **License hostname and hostname mismatch** | The license is tied to a different hostname than the current machine. | | **System clock has been set back** | The system clock was moved backward (license tamper protection). | | **VM is not allowed** | The license does not permit running in a virtual machine. | | **Expired** | The item has expired. | | **Billing code** | A billing-code related error occurred. | ### Failover | Status | Why it happens | | ------------------------- | -------------------------------------------------------------------------------------- | | **Streams not identical** | Sources in a failover group could not be merged because the streams are not identical. | ### Generic / Fallback | Status | Why it happens | | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Error** | A generic, unclassified error occurred. | | **Unknown** | The cause of the error could not be determined. | | **None** | No error reason is reported. On a Connected source this is the normal state. On any other state it means no reason was given, so check the Broadcaster Event Log. | [title] Proxy Not Detected [path] Troubleshooting/ZEN Master - Errors and Troubleshooting/ ### ERROR Within the broadcaster software you get a "proxy not detected" error when clicking "New Upload" ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/QKJC_cU63yHMdqBj0Hdjj-20260305-202313.png) ### ISSUE Zixi Video Accelerator Proxy is not installed. ### RESOLUTION :::hint{type="warning"} This option is only accessible by accessing the broadcaster UI directly (by IP Address) in Firefox. This option is not accessible when accessing the broadcaster through ZEN Master. ::: Install to your local machine from the Zixi Portal at [https://portal.zixi.com/](https://portal.zixi.com/) See more information here [https://docs.zixi.com/zixi-broadcaster-zec-current-version/installing-the-zixi-video-acceleration-proxy](https://docs.zixi.com/zixi-broadcaster-zec-current-version/installing-the-zixi-video-acceleration-proxy) Also enable the following in the **Settings **tab (file-transfer/downloads section): **Download**, **HTTP input**, and **Upload**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/JCwLpIvetWeVK03DYKqwb-20260305-210322.png) [title] Unsupported Encoding [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/ ### ERROR Broadcaster Output Error - Unsupported Encoding ![Unsupported Encoding Error](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/MmgoWSpcVVyfpp3-2HP8s_unsupported-encoding.png) ### ISSUE The "Unsupported encoding" error usually relates to a codec the target cannot accept, the error comes from the target itself. It is most often an unsupported audio type. For example, RTMP output supports only AAC or MP3 audio, and only H.264 or HEVC video, any other audio (e.g. MPEG-1 Layer 1/2, AC-3) or video codec will be rejected with this error. ### RESOLUTION - **Transcode** the stream and set the audio to **AAC** (MP3 is also accepted for RTMP), and video to H.264/HEVC; or - Go back to the provider and have the encoding adjusted to a supported type — e.g. change the RTMP audio from MPEG to AAC. [title] SRT Target overflow disconnects Troubleshooting guide [path] Troubleshooting/General Troubleshooting/ # What is an SRT Target Overflow Disconnect? An SRT target overflow disconnect is a condition where a Zixi Broadcaster detect that an output buffer for an SRT pull target has exceeded its capacity, causing the broadcaster to terminate and immediately re-establish the connection. Overflow on an SRT output is distinct from a general network drop or timeout. The Broadcaster is actively cutting the connection in response to buffer pressure - the underlying transport path may be healthy. Because the broadcaster reconnects automatically and quickly, the events can be easy to overlook - the stream appears to recover on its own. In practice, each disconnect-reconnect cycle causes a brief output interruption, and if the underlying cause it not resolved, the disconnects may continue to recur, often at increasing frequency under sustained load or high-motion content. # Why SRT Targets Overflow and Disconnect Understanding which of the following causes applies is the first step in selecting the correct fix. :::Heading{depth="3" indent="1"} Encoder sending excessive UDP packets (Packet Flooding) ::: The most common cause of overflow on a Zixi Broadcaster is an encoder sending 1 MPEG-TS packet per UDP packet instead of the recommended 7. This results in a packet rate 7x higher than expected, which overwhelms the broadcaster's SRT output buffer regardless of the stream bitrate. *Expected vs. actual packet rate for a 27 Mbps stream:* - *Expected: 27,000,000 ÷ 8 ÷ 1316 ≈ 2,565 packets/sec* - *Flooding: ~18,000 packets/sec (approx. 7× too high)* If the observed packet rate is significantly higher than the expected value packet flooding is the cause. :::hint{type="success"} Fix: Configure the encoder to send 7 MPEG-TS packets per UDP packet. This eliminates the packet flod and removes the overflow condition. ::: :::Heading{depth="3" indent="1"} Network Path Differences Causing Output Buffer Overflow ::: When some SRT targets on the same source are stable while others are not, the cause is typically a difference in the different network path to each destination. The SRT latency buffer must be sized to accommodate the Round Trip Time (RTT) of the specific path. A latency setting this is adequate for a low-RTT destination (eg. a nearby data centre) will be sufficient for a high-RTT destination (eg. a distant cloud region), causing buffer overflow on the longer path while the shorter path targets remain stable. Recommendation: set SRT latency to at least 3-4x the measured RTT to the destination. Too low a latency setting is a frequent cause of SRT overflow on long distance paths. :::Heading{depth="3" indent="1"} Broadcaster Migration - Host Configuration Differences ::: Overflow issues that occur immediately after migration to a new Broadcaster instance are often caused by differences in the host environment rather than the stream itself. The stream and network may be identical, but the new host might be less capable of handling the same load. Contributing factors include: - OS-level socket buffer sizes smaller than the previous host - NIC settings or driver configuration that limit throughput or increase latency - Firewall rules on the new host that asymmetrically rate-limit traffic to specific target destinations - Software version differences between old/new broadcaster :::Heading{depth="3" indent="1"} Encoder Bitrate Spikes Exceeding SRT Buffer Headroom ::: Even with correctly configured packet rates and adequate SRT headroom latency, a VBR encoder that produces large bitrate spikes (ie. scene changes, fast motion or cut heavy content) can momentarily exceed the SRT output buffer's capacity. The spike saturates the buffer faster than it can drain to the target destination - triggering an overflow disconnect. This cause is particularly common on long destination paths where the drain rate is constrained by the bandwidth or RTT. :::hint{type="success"} See [Encoder Bitrate Spike Troubleshooting Guide](docId:9ci3Oqw8sz_lqibokrQoO) for diagnosis and fixes specific to this cause. ::: :::Heading{depth="3" indent="1"} Insufficient max\_bitrate Configuration in Zixi ::: The *max\_bitrate* parameter on Zixi Broadcaster inputs and Failover Groups controls internal buffer allocation. If *max\_bitrate *is set correctly within the 1.5-2x the stream's bitrate recommended value, the allocated buffer has no headroom to absorb short bursts - including retransmission overhead, bitrate spikes or congestion. When the actual bitrate (incl. overhead) exceeds the allocated ceiling, overflow results. # How Overflow Disconnects cause Problems Downstream ### Stream Instability and Viewer Impact Each disconnect/reconnect causes a brief interruption in the output stream delivered to the SRT pull target. This will be viewed as a black screen, audio dropout or momentary freeze at the receiving end. Even if the reconnect is fast, the interruption is visible and disruptive for live content. ### Cascading Failures in redundant Architectures In Failover configurations where multiple SRT targets are receiving from the same source, an overflow condition on one target does not always stay isolated. The processing overhead generated by the repeat disconnect/reconnect cycles on affected targets can increase load on the Broadcaster, degrading performance for stable targets on the same instance. In high-density deployments, a single flooding encoder or misconfigured target can trigger overflow events across multiple unrelated streams on the same host. ### Masking of Upstream Issues Because the Broadcaster reconnects automatically and quickly, repeated overflow disconnects can mask a more serious upstream problem. If overflow is caused by encoder packet flooding, the actual stream quality issue (malformed TS packaging, excessive PID rate, or encoder misconfiguration) goes unaddressed while the symptom (brief drops) appears to self-resolve. Without checking the system log, the overflow trigger may never be identified. ### Impact During Broadcaster Migration Host configuration differences can cause overflow disconnects and incorrectly be attributed to the migration process itself. Underlying socket buffer or NIC configuration difference then persists and continue to cause overflows on the new host indefinitely. # What to check :::Heading{depth="3" indent="1"} Confirm overflow is the trigger ::: ### What to Check Before investigating possible causes, confirm that overflow is the actual reason for the disconnect rather than a network timeout, authentication failure, or unrelated error. ### How - Check the broadcaster system log around the disconnect timestamps. At the default logging level you will see the output being dropped for buffer pressure, look for a `on_distributor_sink_stuck` entry for the affected sink immediately before the reconnect. To see the raw per-packet overflow events (log lines containing `OnRealData OVERFLOW`), raise the broadcaster log level to debug, since those lines are logged at debug level and are not shown at info. - Confirm the reconnect occurs immediately - a brief disconnect followed by instant reconnect is characteristic of an overflow-triggered cut rather than a network timeout, which typically has a longer reconnect delay. - In ZEN Master, check the event log for the affected target and note the exact timestamps of disconnect events. Cross-reference these against the Broadcaster log to confirm overflow entries at the same timestamps. :::hint{type="success"} **Root cause confirmed if: ** Overflow event is logged immediately before each disconnect, and reconnect is near-instantaneous. ::: :::Heading{depth="3" indent="1"} Calculate and Compare Packet Rate ::: ### What to check Determine whether the encoder is flooding the Broadcaster with an excessive number of UDP packets. ### How On the encoder or using a stream analyzer, measure the actual UDP packet rate on the source stream. Then calculate the expected packet rate: :::hint{type="warning"} *Expected packet rate = Bitrate (bps) ÷ 8 ÷ 1316* *Example: 27 Mbps stream* *27,000,000 ÷ 8 ÷ 1316 = 2,565 packets/sec expected* *If observed rate is 7x higher (e.g. 18,000 packets/sec)* ::: You can also capture a short packet trace on the Broadcaster's inbound interface using tcpdump and count UDP packets per second from the encoder source IP to confirm: :::hint{type="warning"} *tcpdump -i \ -n udp src \ -c 10000 2>/dev/null | wc -l* ::: :::hint{type="success"} **Root cause: ** Observed packet rate is 7× higher than the calculated expected rate — encoder is sending 1 MPEG-TS packet per UDP packet. ::: Configure the encoder to encapsulate 7 MPEG-TS packets per UDP packet. This is a standard setting on most broadcast encoders and is the correct configuration for MPEG-TS over UDP/IP delivery to Zixi. Confirm the packet rate drops to expected levels after the change. :::Heading{depth="3" indent="1"} Compare Stable vs Affected Targets ::: ### What to check If some targets on the same source are stable while others are overflowing, the cause is a network path difference between destinations. ### How - Identify which targets on the same source are stable and which are overflowing. If stable targets route to one destination and affected targets route to another, proceed with path comparison. - Measure RTT to both destinations from the Broadcaster host and compare. A significantly higher RTT to the affected destination confirms the path is the differentiating factor. - Check the SRT latency setting on both sets of targets. If the affected targets have the same latency setting as the stable targets but a longer path RTT, the latency is insufficient. **Latency should be at least 3–4× the measured RTT to that specific destination.** - Check for any firewall rules, QoS policies, or routing differences that apply to the affected destination path but not the stable one. - If all targets on the source are affected, path difference is not the cause - proceed to Steps 4 and 5. :::hint{type="success"} **Root cause: ** SRT latency setting is insufficient for the RTT of the affected destination path. ::: Increase the SRT latency on the affected targets to at least 3–4× the measured RTT. For example, a path with 80ms RTT requires a minimum SRT latency of 320ms. Apply the change and monitor for recurrence. Do not apply the increased latency to stable targets on shorter paths - unnecessarily high latency increases buffer size and end-to-end delay without benefit. :::Heading{depth="3" indent="1"} Check SRT Latency Configuration ::: ### What to check Even when all targets appear to be on similar paths, an undersized SRT latency setting is a common and easily overlooked cause of overflow on any destination with non-trivial RTT. ### How - On the affected targets in Zixi Broadcaster, navigate to **Outputs -> \[Target] -> Edit** and review the SRT latency setting. - Measure the current RTT to the destination from the Broadcaster host using ping or mtr. Confirm the latency setting meets the **3–4× RTT** minimum. If the latency is set to a default value (commonly 120ms or 200ms) and the actual RTT is above 50ms, the buffer is likely undersized for the path. - Also check whether the latency setting on the receiving end (if it is a Zixi device or SRT-capable decoder) matches or is compatible with the Broadcaster's output latency setting. A mismatch can cause silent buffer underruns at the receiver that feed back as pressure on the Broadcaster output buffer. :::hint{type="success"} **Root cause: ** SRT latency set to a generic default that does not reflect the actual path RTT to the destination. ::: Increase SRT latency on the affected output to **4× RTT** as a conservative starting point. Monitor overflow events in the Broadcaster log after the change. Reduce incrementally if the overflow resolves and lower latency is desired, keeping 3× RTT as the minimum floor. :::Heading{depth="3" indent="1"} Check Max Bitrate ::: ### What to check Confirm that *max\_bitrate* on the affected input and Failover Group is set high enough to provide adequate buffer headroom for the stream's peak bitrate. ### How - In Zixi Broadcaster, navigate to **Inputs -> \[Stream] -> Edit** and check the *max\_bitrate* value. Also check *max\_bitrate* on the associated Failover Group if one is in use. - Compare *max\_bitrate* against the stream's observed peak bitrate from the ZEN Master bitrate graph or Broadcaster input statistics - not just the nominal average. If *max\_bitrate* is at or close to the average bitrate, the buffer has no headroom for retransmission overhead, bitrate spikes, or burst events. - The recommended value is **1.5–2× the highest expected peak bitrate**. Eg. For a 20 Mbps average stream that peaks at 30 Mbps, *max\_bitrate *should be set to at least 45–60 Mbps. :::hint{type="success"} **Root cause: ** max\_bitrate set incorrectly, leaving no internal buffer headroom for peak traffic. ::: Set *max\_bitrate* to 1.5–2× the highest expected peak bitrate on both the input and Failover Group. Restart the affected input after the change if required for the new setting to take effect. :::Heading{depth="3" indent="1"} Check for Host Level Issues After Migration ::: ### What to check If overflow appeared after migrating to a new Broadcaster host, compare the host environment against the previous instance to identify configuration differences that reduce the new host's ability to handle the same load. ### How SSH into the new Broadcaster host and check the following: OS socket buffer sizes: *sysctl net.core.rmem\_max* *sysctl net.core.wmem\_max* *# Compare against values from the previous host.* *# Low values (\< 8MB) can cause SRT buffer pressure under high-bitrate conditions.* ** *# To increase (non-persistent — test first):* *sysctl -w net.core.rmem\_max=16777216* *sysctl -w net.core.wmem\_max=16777216* ** *# To persist across reboots, add to /etc/sysctl.conf:* *# net.core.rmem\_max = 16777216* *# net.core.wmem\_max = 16777216* ** NIC settings and driver version: *ethtool -i \ # Check driver version* *ethtool -g \ # Check ring buffer sizes* *ethtool -S \ # Check for RX drops* *# Look for: rx\_dropped, rx\_queue\_0\_drops, nic\_rx\_dropped* *# Non-zero RX drops indicate packets being discarded at the NIC level.* ** Software version and firewall: •       Confirm the Broadcaster software version on the new host matches the previous host, or review the release notes for any SRT-related changes between versions. •       Check firewall rules on the new host for any asymmetric rate-limiting or egress rules that target specific destination IPs or ports and were not present on the previous host. :::hint{type="success"} **Root cause: ** New Broadcaster host has smaller socket buffers, different NIC configuration, or additional firewall rules compared to the previous host. ::: Align the new host's OS socket buffer sizes, NIC ring buffer settings, and firewall rules with the previous host configuration. If the Broadcaster software version differs, review the release notes for SRT changes and test after aligning the version. # Summary Decision Tree SRT target(s) disconnecting and reconnecting repeatedly Overflow event logged immediately before disconnect? -> NO -> Not an overflow disconnect. Check for network timeouts or auth issues. YES - Continue below Observed packet rate >> (Bitrate ÷ 8 ÷ 1316)? -> YES -> Encoder flooding BX with 1 MPEG-TS per UDP packet. **Fix:** configure encoder to send 7 MPEG-TS packets per UDP packet **(Step 2)** **** Some targets on same source stable; others overflowing? -> YES -> Network path difference between destinations. **Check:** RTT to each destination; SRT latency on affected targets. **Fix:** increase SRT latency to ≥4× RTT on affected targets **(Step 3).** **** Issue appeared after migrating to a new Broadcaster host? -> YES -> Host configuration difference. **Check:** OS socket buffers, NIC settings, firewall rules, software version. **Fix: **align new host config with previous host **(Step 6).** **** Max Bitrate set at or close to nominal average bitrate? -> YES -> Insufficient internal buffer headroom. **Fix:** set max\_bitrate to 1.5–2× highest expected peak bitrate **(Step 5).** Overflow only during high-motion content or scene changes? -> YES -> Encoder bitrate spike exceeding SRT buffer headroom **Fix: **see [Encoder Bitrate Spike Troubleshooting Guide](docId:9ci3Oqw8sz_lqibokrQoO) increase max\_bitrate and review encoder VBV/CBR settings. Cause unconfirmed after above steps? -> YES -> **Action:** enable debug-level logging on the affected broadcaster (the raw `OnRealData OVERFLOW` lines are logged at debug; info level only shows the `sink_stuck`/`disconnect` entries). Collect logs and packet capture, and open a support ticket with RTT data and overflow event timestamps. # Escalation Checklist If disconnects continue after applying the fixes above, escalate to Zixi Support with the following: | Item | Details / Location | | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Broadcaster version and OS | Shown in Broadcaster UI header or /etc/zixi/version | | Stream name and affected target name | Push/Pull, protocol, SRT mode (caller/listener) | | System log with overflow events visible | Broadcaster log set to debug level (to capture `OnRealData OVERFLOW` lines) covering the period of disconnects; note that info level shows only the `on_distributor_sink_stuck`/`disconnect` entries | | Measured RTT to affected and stable destinations | From the Broadcaster host using ping or mtr | | Encoder packet rate and MPEG-TS-per-UDP configuration | From stream analyser or tcpdump capture on the inbound interface | | SRT latency settings for affected vs. stable targets | From Outputs → \[Target] → Edit | | max\_bitrate configuration for the affected input and Failover Group | From Inputs → \[Stream] → Edit | | OS socket buffer sizes and NIC settings on Broadcaster host | sysctl net.core.rmem\_max / wmem\_max; ethtool -g and -S | | Packet capture on the Broadcaster's inbound interface | .pcap covering the overflow period (tcpdump on the interface) | | | | [title] Finding where a stream fault is [path] Troubleshooting/General Troubleshooting/ A stream fault sits in one of four places: the source, the Broadcaster, the network path, or the target. Work through these checks in order. Each one rules a place in or out, so stop at the first clear answer. 1. **Compare the source with the Broadcaster input.** Look at the TR 101 290 errors, including CC (continuity counter) errors, on the source feed and on the same stream on the Broadcaster. If the source already has the errors, they arrived with the stream. Check the encoder or the provider that feeds it. 2. **Check whether both paths failed at the same moment.** If a main and a backup path show errors within the same second, look at what they share. That is usually the common source or a shared network exit. 3. **Check the input's Max Bitrate.** On a Zixi input, Max Bitrate sizes the buffer that holds packets for recovery. If it is close to the real feed rate, bursts and resent packets overflow that buffer and show as not recovered. ZEN Master warns with "Bitrate above configured maximum" when the input receives more than its Max Bitrate allows. Raise it before you look at the network. See [Sizing latency, buffer and max bitrate](docId\:oj4srP9fTjhYtmGyv7xJA). 4. **Check every output on the Broadcaster.** If all outputs on one Broadcaster show loss and its input is clean, the fault is on its outbound path. To confirm, stop one output. If loss on the others drops, the outbound link is short of capacity. 5. **Check the target on its own.** If one target disconnects again and again while its source and Broadcaster are clean, the fault is on the target's network or the receiving device. 6. **Check the other objects on the same Broadcaster.** If every source and target on it changed state at the same moment, the cause is the Broadcaster host or its network, not one stream. 7. **Check for "Unknown" before you call it an outage.** "Unknown status, missing broadcaster data" means ZEN Master received no status report from the Broadcaster for more than 70 seconds. If the Broadcaster, input and output uptimes carry on without a reset, the stream was not interrupted. If the checks do not give a clear answer, send Support the source name, the target name and the time window in UTC. [title] Error requesting Azure Authorization Token [path] Troubleshooting/ZEN Master - Errors and Troubleshooting/ ### ISSUE ZEN Master is displaying "Error - Error requesting Azure Authorization token" You may be experiencing an error "Error - Request failed with status code 401" also when attempting to create new sources/targets/broadcasters within ZEN Master. ### CAUSE Azure credentials for the application that is configured to communicate with ZEN Master have expired. ![Error - Expired Credentials](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/sOY5GzO2NRdz-lKvwxwNj_image.png) *Example of error when trying to create new elements in ZEN Master:* ![Error screenshot Status Code 401](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/XiPnAUwQKeiFygY2zXGBm_image.png "Error screenshot Status Code 401") ### RESOLUTION - In Azure, Access your Azure keys under "Storage Account" ![Access Azure Keys](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/o2A4vOkDw16O735CResG1_image.png) - Update the configuration for Azure - Resume operation within ZEN Master [title] High Max Bitrate Configuration [path] Troubleshooting/ZEN Master - Errors and Troubleshooting/ "**Warning: High Max Bitrate Configuration Detected - A value of 2x the actual bitrate is recommended**" - For informational purposes only It is best practice to optimize max bitrate for any source that does not have the max bitrate configured correctly. An incorrect max bitrate value can create issues with the stream and, in certain situations, result in poor-quality stream errors such as cc errors, packet loss, etc. :::hint{type="info"} Max Bitrate is used by the Broadcaster to determine buffer size when processing the transport stream - **it does not cap the bitrate**. We recommend setting it to 2x the actual bitrate. ::: **For SRT, RTMP, and RIST, you can manually adjust the max bitrate within the Broadcaster or ZEN Master. For all other protocols, please contact your source provider to make this adjustment.** To adjust the max bitrate for SRT, RTMP, and RIST: ### IN THE BROADCASTER - Log in to the Broadcaster - Select the souce/input for the adjustment - Click the Settings dropdown and select Edit ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/wQGej4Xq48o_4tP6a6D-e_image.png) - Adjust the Max Bitrate to be 1.5-2x the actual bitrate of the stream - ie. If the stream bitrate is approx 12,000mbps, the max bitrate should be 18,000-24,000mbps. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/lW4UwPymfLCQEkzveAiGa_image.png) - Select Ok :::hint{type="success"} **This will NOT disrupt the stream and does NOT require it to be restarted.** ::: ### In ZEN Master When creating or editing an SRT or RIST Source, use the "Max Bitrate" field within the configuration settings - setting it to approximately 2x the actual (average) bitrate, unless you know the max bitrate. :::hint{type="info"} The max bitrate for RTMP sources cannot be set or changed in ZEN Master. If you need to adjust it, you will need to do so in the Broadcaster. ::: *Example below for SRT* ![Source configuration window showing max bitrate setting](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ruD-EYGY57gAWRD68j47I_image.png "Source configuration window showing max bitrate setting") ### ERROR Notification within ZEN Master - The error will automatically clear from ZEN Master within 15 minutes. *This notification is enabled for the default notification profile within ZEN Master. * If you prefer not to receive this notification, you can duplicate the default notification profile or create a new custom profile and disable this notification. ZenMaster > Configure > Event Profile > Search for “Max” > Disable “Max bitrate set too high”. :::hint{type="info"} We do **not** recommend disabling the Max Bitrate notifications. Instead you should set the Max Bitrate as close as possible to 2x the maximum bitrate of the stream. ::: [title] Encryption Error (Error 35) [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/Broadcaster API Errors/ ### ERROR Encryption Error (Error 35) can happen in two cases: On input: "Double encryption" error - source is enrypted Zixi push/pull, and there is encryption configuration on the input On output: "No decryption key" error - input is encrypted Zixi push/pull, output expects clear data (UDP/RTP/RIST/SRT/ASI/RTMP/TCP...), and there is no decryption key defined. Note: Mismatch in keys will not generate this error, payload will simply be corrupted. Since the is no assumption on payload structure, a mismatch on encryption key simply shows up as corrupted data. ### RESOLUTION In order to detect decryption key mismatch we recommend adding 3 counters on outputs: 1. Number of corrupted compressed packets (a.k.a null-packet-optimization, although the name is misleading) 2. Number of total compressed packets 3. Number of non-TS packets, post-decryption If counters 1 or 3 increase, and there is a decryption key defined - this is a strong indication of a wrong key. Corrupted compressed packets are a clear giveaway, especially if it happens to a high proportion of the compressed packets (counter 1 out of counter 2). Although compression is the default - it is not always enabled. In that case, when counters 1 and 2 are not growing, counter 3 can play a role. Counter 3 can still increase when using non-TS payload, with compression disabled, and a correct static-key decryption, although this combination is a less likely scenario than simply a mismatch in keys.   [title] Post Upgrade Verification Checklist [path] Troubleshooting/Best Practices/ **Complete these checks within 10 minutes of the Broadcaster restarting.** Use this checklist immediately after every Broadcaster or ZEN Master upgrade to confirm that streams, outputs, and reporting have all recovered correctly. ## Streams and Connectivity •        **All sources reconnected. **In ZEN Master, verify all expected sources show as Active with normal bitrates. Sources that remain in Connecting state more than 3 minutes after restart need investigation. •        **All targets reconnected. **Verify all outputs are Connected in ZEN Master. Check each failover group is on the correct primary leg. •        **No unexpected stream errors. **Check the ZEN Master event log for any new error events generated after the restart. A small number of reconnection events is normal. Sustained errors or packet loss events are not. •        **Bitrates at expected levels. **Spot-check bitrates on key sources and targets. A bitrate significantly lower than normal after reconnection can indicate a source issue unrelated to the upgrade. ## Transcoding and Adaptive Outputs •        **Transcoded channels are online. **In ZEN Master or the Broadcaster UI, check all transcoded outputs. Any output showing as Offline after the restart with a codec or encoding error may indicate a regression in the new build. •        **Adaptive bitrate outputs reconnected. **Verify each adaptive output is Online and shows the correct profile ladder. An adaptive output showing "Offline: Unsupported Encoding" after an upgrade is a known regression pattern. See the companion Upgrade Checklist guide for steps. •        **Audio codec outputs are functioning. **If any transcoded outputs use HE-AACv2, verify that the audio bitrate is present and correct. Multi-channel audio sources can surface transcoding issues after an upgrade. See the Multi-Channel Audio Downmix Troubleshooting Guide if affected. ## ZEN Master Reporting •        **Stream statistics are populating. **Verify that bitrate graphs, packet loss stats, and content analysis data are appearing for active streams. If ZEN Master shows charts with no data, wait 5 minutes. Chart data can take time to populate after a restart. •        **Alert configuration is intact. **Go to Settings, then Alerts, and confirm all alert rules are present. •        **Historical charts are accessible. **Check that historical charts from before the upgrade are still visible. If history is missing, try a hard browser refresh first (Ctrl+Shift+R). If still missing after 30 minutes reach out to Support. ## Bonding ** Skip this section if bonding is not configured on this Broadcaster.** •        **Bonding statistics are populating. **Verify that bonding stats including link utilization and packet distribution are showing correctly in ZEN Master or the Broadcaster UI. If bonding stats to display as zero after upgrade, restart the bonding group and refresh the browser before escalating. •        **All bonding group members are active. **Confirm all links in each bonding group are active and contributing traffic. ## Recording and Storage ** Skip this section if recording is not configured on this Broadcaster.** •        **S3 recording settings are intact. **Go to Settings, then Recording, and verify the S3 URL and credentials are saved correctly. S3 URLs can appear to save but silently revert to disk-only after an upgrade. After saving, navigate away and return to confirm the URL is still present. •        **TS recording is capturing. **If scheduled TS recording is active, verify a capture is running or completed successfully after the restart. ## Post Upgrade Decision Tree Broadcaster restarted and streams not recovering as expected? Streams still Connecting after 5 minutes? -> Check upstream source/encoder is online -> Force Reconnect from ZEN Master -> Still offline after 10 min -> Initiate rollback Adaptive output shows "Offline – Unsupported Encoding"? -> Note target version -> contact Zixi Support with version and output config Bonding stats showing zero? -> Wait 5 min -> Refresh browser -> Restart bonding group -> Still zero after 10 min -> Escalate with version ZEN Master charts missing history? -> Hard refresh browser -> Wait 15 min -> Still missing - Open support ticket with ZEN Master links and details S3 recording not saving to S3? -> Re-enter and save S3 URL -> Verify credentials -> Navigate away and back to confirm persistence Transcoding output offline with audio or codec error? -> See Multi-Channel Audio Downmix guide or confirm codec settings match source PID Broadcaster not starting at all? -> Check systemctl status for error -> Review /var/zixi/broadcaster/log/ -> reinstall Multiple failures across multiple streams 10+ minutes post-restart? -> Collect Broadcaster logs -> Initiate rollback: reinstall previous build from backup, restore config, restart service No clear cause and streams still offline -> Collect Broadcaster logs, version details, and stream list and escalate to Zixi Support ## Rollback Procedure Initiate rollback if streams are not recovering within the agreed threshold (recommend 10 minutes) - Rollback restores the previous Broadcaster build and configuration. - Stop the Broadcaster service: sudo systemctl stop zixi-broadcaster - Reinstall the previous build: Use the previous installer - Run the installer to overwrite the new build. - Restore the configuration backup: Copy the backed-up config directory back to /var/zixi/broadcaster/config/ (Linux) or \[install dir]\config\ (Windows). - Restore the license file: Copy the backed-up license to /var/zixi/broadcaster/conf/broadcaster.lic. - Start the Broadcaster: sudo systemctl start zixi-broadcaster - Verify version is the previous build: Check Help -> About in the Broadcaster UI. - Notify Zixi Support: Open a support ticket describing what failed during the upgrade and that rollback was performed. Include the target version and the failure symptoms. Zixi Support will advise on a safe path forward. ## Escalation Checklist When escalating to Zixi Support after an upgrade failure, include as much of the following as possible: - Broadcaster version before upgrade (e.g. 17.9.45910) - Broadcaster version after upgrade (e.g. 18.10.46622) - Host OS and version (e.g. AlmaLinux 9, Ubuntu 22.04, Windows Server 2022) - Deployment type: On-premises / AWS / ZaaS / other cloud - List of affected streams/outputs with their current status and any error messages shown in ZEN Master or the Broadcaster UI. Provide ZEN Master links where possible. - Broadcaster logs post-upgrade from /var/zixi/broadcaster/log/ (Linux) or \[install dir]\log\ (Windows) include at minimum the log file covering the restart and the 10 minutes following - ZEN Master event log exported for the period around the upgrade - Description of which Section 3 checks failed and what was observed - Whether rollback was performed and what the outcome was - Time of the upgrade restart and time issues were first observed [title] "Compression Error" [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/ ### ERROR A **"Compression error"** means the receiving side **failed to decompress a packet**. (If the compressed size of a packet is greater than or equal to the original, the sender transmits the original uncompressed packet instead.) A common upstream cause is a **decryption/key mismatch,** if a packet can't be decrypted correctly, the following decompression step fails, but corruption, spiky traffic, or too-tight max-bitrate headroom can also trigger it. ### RESOLUTION - If the stream is encrypted, check/troubleshoot the **encryption (key) settings** on both ends. Some known cases were resolved in **v16.0 and later** — test on a current stable version. - **UDP source:** open advanced settings (add ?advanced=1 to the Broadcaster URL) and toggle **compression** off/on, restarting the stream after each toggle. - **UDP/SRT input:** check the **max bitrate** on the input (in Broadcaster or ZEN Master) and increase headroom if traffic is spiky. Max bitrate should be **1.5–2× the stream bitrate** — e.g. for a 9 Mbps stream, at least 13.5 Mbps, ideally 18 Mbps. ![UDP/SRT Input Advanced Settings](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/t0kEk4-yMeIEBauIuFj-V_image.png) [title] Intermittent frozen video/silent audio errors (cloned) [path] Troubleshooting/ZEN Master - Errors and Troubleshooting/ ### ERROR You are seeing intermittent frozen video & silent audio errors. You are not seeing any issues on the source itself at origin. ### ISSUE There could be several aspects here to investigate. - Initially see if the source is showing correlating network spikes or cc errrors at these times, if so this is related to network fluctuations. Raising the latency can help mitigate these fluctuations. - If the network is looking clean but you are still experiencing these hits, check the Max Bitrate and Dejitter Values on the stream as they may need increasing. See here for details regarding Max bitrate - [https://docs.zixi.com/zen-master/high-max-bitrate-configuration](https://docs.zixi.com/zen-master/high-max-bitrate-configuration) also check your Dejitter buffer settings. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/FT-yrIaKGU41bSgFkF-0p_image.png) ### RESOLUTION **Dejitter Buffer Impact** The broadcaster with the lower dejitter buffer setting doesn't have enough buffering capacity to smooth out network jitter spikes. When packets arrive late or out of order, the smaller buffer runs dry, causing the decoder to stall - hence frozen video. The "silent audio" suggests the audio decoder is also starving for packets during these events. **Max Bitrate Setting** If the actual source bitrate occasionally spikes above this configured maximum (common with variable bitrate encoding), the broadcaster may be dropping packets or throttling the input stream. This compounds the buffer underrun problem. [title] Disabling Ubuntu Unattended Upgrades on Zixi Broadcaster Hosts [path] Troubleshooting/Best Practices/ :::hint{type="warning"} **Disclaimer: ** Whether unattended upgrades should remain enabled is a decision for your network and IT security teams, not a Zixi recommendation. Automatic security patching reduces exposure to unpatched vulnerabilities, but as this ticket shows, it can also restart the Broadcaster process (or the host itself) without warning and interrupt live outgoing streams. The steps below let you keep OS security updates flowing while controlling when the restart happens please make sure to review them against your own security policy before applying. ::: Broadcaster instances running on customer-managed Ubuntu hosts can restart unexpectedly when the OS applies an unattended (automatic) security update that includes a kernel or systemd package update requiring a reboot, or that triggers a service restart via needrestart. This is an OS-level behavior, separate from Zixi. **There is no Zixi-side auto update mechanism - Broadcaster software upgrades only occur when explicitly initiated through ZEN Master’s Install Version screen or manually on the box, and every such event is logged.** This guide covers how to convert unattended-upgrades from a surprise reboot into planned maintenance, on Ubuntu hosts you manage yourself (AWS, on prem or otherwise). :::hint{type="info"} **Root cause: ** Ubuntu's unattended upgrades package runs its scheduled apt-daily-upgrade.service, installs an update and triggers an automatic reboot / service restart. This in turn restarts the zixibc service (and the host machine if a reboot required package was involved) and interrupts streams. ::: # Resolution There are two independent settings to change. You can apply either one on its own but applying both is a good option. **Option A: **Stop unattended-upgrades from automatically rebooting the host. **Option B: **Tell needrestart not to restart the zixibc service when packages are updated, even without a reboot. Applying both means package security updates can still install in the background (recommended: don’t fully disable security patching) but neither the host or the Zixi service can then restart without your confirmation. You can then restart the service yourself during a planned maintenance window. ## Step by Step: ### Step 1: Disable Automatic Reboot First check: whether unattended-upgrades is configured to reboot the host automatically after installing updates. - Edit the unattended-upgrades config file and set Automatic-Reboot to false. | sudo nano /etc/apt/apt.conf.d/50unattended-upgrades | | --------------------------------------------------- | - **Find** or **add** the following line and set it to *"false"*: | Unattended-Upgrade\::Automatic-Reboot "false"; | | ---------------------------------------------- | - **Save and exit. ** This stops the automatic reboot from occurring. The host will flag that a reboot is pending (visible via /var/run/reboot-required) instead of rebooting itself, so you can schedule it at a convenient time. ### Step 2: Ubuntu Configuration Check if needrestart is configured to automatically restart the zixibc service when its dependent packages are updated. This can restart the Broadcaster even without a host reboot. - **Edit** the needrestart config and add an override so zixibc is left unaffected. | sudo nano /etc/needrestart/needrestart.conf | | ------------------------------------------- | - Under the $nrconf\{override\_rc} section, **add:** | # Zixi Service — exclude from automatic restart
qr(^zixibc\\.service$) => 0, | | ------------------------------------------------------------------------------------- | - **Save and exit.** ### Step 3: (Optional - not recommended) Fully disable unattended upgrades **Check with your IT and Security teams before taking these steps **to confirm if they would prefer to control all OS patching manually rather than let security updates install automatically in the background. - Reconfigure the package outright. | sudo dpkg-reconfigure -plow unattended-upgrades | | ----------------------------------------------- | - Select “No” when prompted. Note this stops automatic security patching entirely. You will need a separate process to keep the host patched. Most customers prefer Steps 1 and 2 over this option, since it keeps security updates flowing while removing the disruptive restart. ### Step 4: Verify the change - Verify the settings are in place after editing both files: | grep Automatic-Reboot /etc/apt/apt.conf.d/50unattended-upgrades
grep -A2 override\_rc /etc/needrestart/needrestart.conf | | ---------------------------------------------------------------------------------------------------------------------------- | - Check the first command returns false. - Check the second command shows the zixibc.service exclusion line inside the override\_rc block. ## Quick reference | **File** | **Setting** | **Effect** | | ----------------------------------------- | ----------------------------------------------- | --------------------------------------------------- | | /etc/apt/apt.conf.d/50unattended-upgrades | Unattended-Upgrade\::Automatic-Reboot "false"; | Host no longer reboots itself after updates | | /etc/needrestart/needrestart.conf | qr(^zixibc\\.service$) => 0, under override\_rc | zixibc service is not auto-restarted by needrestart | | N/A (package-level) | dpkg-reconfigure -plow unattended-upgrades → No | Unattended-upgrades disabled entirely (optional) | | | | | ## Decision Tree If the Broadcaster restarts continue after applying the fix, work through this before opening a new support ticket: Restart correlates with apt-daily-upgrade.service in syslog? -> YES -> Recheck Steps 1 & 2 were saved correctlyl confirm with the verification commands in Section 4 No apt-daily-upgrade entry, but restart still occurs on a schedule? -> YES -> Check for AWS-side events (ie. schedule maintenance, instance retirement, auto scaling) via CloudTrail / the EC2 console for the affected instance ID No OS level or AWS level event found? -> Escalate to Zixi support using the checklist below. ## Escalation Checklist When escalating to Zixi Support, include the following: - Broadcaster instance name(s) affected (e.g. zb-distrib-aws-ire1) - Exact restart timestamp(s), in UTC - Confirmation of whether Steps 1–2 (Section 3) have already been applied - Syslog excerpt covering the restart window (look for apt-daily-upgrade.service entries) - AWS instance ID and region, plus CloudTrail/EC2 console findings if checked - Broadcaster version involved - Whether the restart caused an outgoing stream interruption and for how long [title] Stream only connects using IP Address [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/ ### ISSUE Client is having DNS issues - can connect by IP but not Full IO URL provided by ZEN Master. When a system connects to a service using a hostname (for example zaas-la-kekbz.cstest.io.zixi.com), it must first perform a DNS lookup. DNS (Domain Name System) translates the human readable hostname into a numerical IP address that computers actually use to communicate. The process is: 1. The client asks a DNS resolver to resolve the hostname 2. The resolver returns an IP address (or multiple IPs) 3. The client then connects to that IP address If DNS resolution fails, the connection attempt never reaches the service, because the client does not know which IP address to use. ### Why connecting by IP can still work When you connect directly to an IP address, DNS is completely bypassed. That means: · No hostname resolution is required · No DNS servers are queried · No DNS cache or TTL behaviour is involved As long as: · the service is running on that IP, and · the network path to that IP is reachable the connection will succeed, even if DNS is broken. We have not made any DNS changes. But it could have been a cache in a DNS that was stale. On the encoder network you could test the following: nslookup \[insert ZEN Master io URL here] 8.8.8.8 nslookup \[insert ZEN Master io URL here] 1.1.1.1 I expect to see: · The hostname resolves · One or more IP addresses are returned · No errors That confirms DNS is working for that resolver. If DNS is not working it will look something like this: \*\* server can't find hostname: NXDOMAIN ### RESOLUTION - Investigate your DNS configuration for the host host machine. - Configure DNS settings permanently using the appropriate configuration method for your respective OS, such as editing Netplan YAML files or using the NetworkManager. - Check your Network & DNS Settings within the Zixi Broadcaster - As the team the Network Configuration tab within the Broadcaster UI has been deprecated as of Version 17 and should not be used with newer OS that use NetworkManager or NetPlan (as in the case of Ubuntu).   [title] Removing a PID using a PID mapping profile [path] Troubleshooting/ZEN Master - Errors and Troubleshooting/ In the situation that you need to remove PID's you can do this using a PID Mapping Profile. You may need to do this in the case that there are unused PID's causing CC errors, targets have requested specific PIDs removed. In the Menu in ZEN Master go to "Transformations" > PID Mapping Profiles ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/wE5BWn9AaNWssJm-xUATy-20260212-184657.png" size="62" width="783" height="568" position="center" caption="Menu - PID mapping profiles screenshot" alt="Menu - PID mapping profiles screenshot" darkWidth="783" darkHeight="568" showCaption="true"} - Click Add+ to create a new PID Mapping Profile - Enter a Name for the profile - Any required tags - You can choose to Pass, Set Null or Remove the PID data - Select type either SPTS (Single Program Transport Stream) or MPTS (Multiple Program Transport Stream). - For CBR (Constant Bitrate) feeds use "Set Null" to maintain PCR accuracy - For VBR (Variable Bitrate) feeds use "Remove" as VBR feeds do not contain NULL packets and do not measure PCR accuracy :::hint{type="warning"} For editing/removal of PIDs 17-20 please ensure your Broadcaster is Version 18.4 or above. ::: ![edit PID mapping profile window screenshot](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/VOOJxslkLLoId5MElrBdL-20260211-235224.png "edit PID mapping profile window screenshot") - Click Save. [title] VLC Issue Troubleshooting Guide [path] Troubleshooting/General Troubleshooting/ # VLC Troubleshooting Guide This guide walks through the most common causes of VLC playback failure when using Zixi, along with step-by-step checks and recommended actions for each. Work through the steps in order. ### Step 1. Verify the Zixi Plugin is installed **Root Cause:** VLC cannot play Zixi streams without the Zixi plugin present and correctly placed. **What to Check:** - Confirm the Zixi VLC plugin has been downloaded and installed. - **Windows users:** The plugin file must be located in the VLC plugins folder. If VLC was installed to the default path, this is typically: - C:\Program Files\VideoLAN\VLC\Plugins If the plugin is missing from this folder, manually move it there and restart VLC. - **macOS users:** Ensure you are using the **Universal version** of VLC (not the Intel-only or Apple Silicon-specific build). The Universal build is required for plugin compatibility on Mac. - **macOS Venture Uusers**: On upgrading to MacOS Ventura, you may find that your existing VLC installation my stop working and/or show up as damaged on launch. If so please jump down to Step 7 for more information: **Action:** Reinstall or relocate the plugin, then relaunch VLC and attempt playback again. ### Step 2. Verify you are running the correct VLC Version **Root Cause:** Using an incompatible or unsupported VLC version can prevent the plugin from loading or functioning correctly. (Known stable versions 3.0.16 & 3.0.17) **What to Check:** - **macOS:** Confirm you are running the latest available **Universal** version of VLC. - **Windows:** Confirm your VLC version is current and matches the plugin version requirements. - If you are on a very recent VLC release and experiencing issues, see **Step 6** for version rollback guidance. **Action:** Download the latest Universal VLC release from videolan.org and reinstall if necessary. ### Step 3. Confirm required Network Ports are open. **Root Cause:** Firewall or network policy blocking Zixi traffic will prevent VLC from establishing the stream playback. **What to Check:** - Port **2077** must be open for both** INBOUND **and** OUTBOUND **TCP/UDP traffic. - This must be permitted across all relevant subnets including any intermediate network segments between the VLC client and the Zixi Broadcaster/ZEN Master host. - Check both host level firewalls (e.g., Windows Firewall, iptables) and network level firewalls or security groups. **AWS-Specific Checks:** If the Zixi Broadcaster is hosted on AWS, verify the following: - The** EC2 Security Group** associated with the Broadcaster instance allows inbound and outbound TCP/UDP on port **2077** from the appropriate source CIDR ranges. - **Network ACLs (NACLs)** at the subnet level also permit port 2077 traffic in both directions - NACLs are stateless and require explicit rules for both directions. - No **VPC routing** issues are preventing traffic from reaching the instance. **Diagnostic tip:** Use curl or telnet from the VLC client machine to test reachability on port 2077: curl -v telnet://\:2077 A successful TCP handshake confirms the port is reachable. **Action:** Work with your network or cloud infrastructure team to open port 2077 for inbound/outbound traffic across all relevant network levels. ### Step 4. Confirm Zixi Pull Egress is enabled on your Zixi license **Root Cause:** The Zixi license may not have the **Pull Egress** feature enabled, which is required for VLC pull-based playback. **What to Check:** - In **ZEN Master** or **Zixi Broadcaster**, navigate to your license details and verify that Pull Egress is listed as an active/licensed feature. - If Pull Egress is not listed or is marked as inactive, the stream cannot be pulled by VLC regardless of other settings. **Action:** Contact your **Zixi Sales representative** to request that Pull Egress be added to your license entitlement. Once the license has been updated: 1. In Broadcaster or ZEN Master, **reload the** **license** to apply the update without requiring a full service restart. 2. Retry playback in VLC after the reload completes. ### Step 5. Reload the License **Root Cause:** Even if Pull Egress is licensed, the running service may be holding a cached version of an older or more limited license. **What to Check:** - Confirm the license was recently updated or re-issued. - Verify the active license in the UI reflects the correct entitlements **Action:** **Reload the license** through the **Broadcaster** or **ZEN Master** interface. After reloading, confirm the updated license is reflected and retry VLC playback. ### Step 6. Rollback VLC to a known good versions **Root Cause:** Newer VLC releases occasionally introduce compatibility regressions with third-party plugins. **What to Check:** - If all previous steps have been verified and playback still fails, the active VLC version may have a compatibility issue with the current Zixi plugin build. **Action:** Roll back VLC to **3.0.16** or **3.0.17**, which is a confirmed working stable version with the Zixi plugin. Older VLC releases can be obtained from the VideoLAN archive: https\://download.videolan.org/pub/videolan/vlc/ After installing: 1. Reinstall/confirm the Zixi plugin is in the correct plugins folder. 2. Retry playback. ### Step 7. macOS Ventura - VLC shows as Damaged or Fails to Launch **Root Cause:** Upgrading to macOS Ventura can break existing VLC installations. VLC may refuse to launch or display a "damaged" warning due to Gatekeeper and library compatibility changes introduced in Ventura. A full reinstall of both VLC and the Zixi plugin is required. **Which VLC Binary Should I Use?** Two builds of VLC 3.0.17.3 are available for macOS. Try the **Intel64 binary first** — it is the simpler path. Only install the Universal binary if the Intel build fails after the plugin is installed. | Build | When to Use | | ------------- | ---------------------------------------------------------------- | | **Intel64** | Try this first on all Macs (including Apple Silicon via Rosetta) | | **Universal** | Use only if Intel64 does not work after plugin install | **Reinstallation Steps** 1. **Download and install VLC:** - **Intel64 (try first):** https\://get.videolan.org/vlc/3.0.17.3/macosx/vlc-3.0.17.3-intel64.dmg - **Universal (only if Intel64 fails):** https\://get.videolan.org/vlc/3.0.17.3/macosx/vlc-3.0.17.3-universal.dmg Double-click the downloaded .dmg to mount it, then drag VLC to your **Applications** folder. 1. **Universal binary only — enable Rosetta before first launch:** Skip this step if you installed the Intel64 binary. After dragging VLC to Applications but **before opening it for the first time:** 1. Right-click VLC in Applications and select **Get Info**. 2. In the Get Info panel, check the box labeled **"Open in Rosetta"**. 3. Close Get Info. 4. **Open VLC and leave it running** while you complete the plugin installation in the next step. 5. **Install the Zixi VLC plugin:** 6. Download the latest Mac plugin from the Zixi Customer Portal: https\://portal.zixi.com 7. Untar the downloaded archive to extract the installer package. 8. Launch and run the installer. 9. Once the installer completes, **close VLC and reopen it**. 10. **Verify playback** by connecting to your Zixi stream. If playback fails after following these steps with the Intel64 build, uninstall and repeat from Step 1 using the Universal binary with Rosetta enabled. ### Troubleshooting Decision Tree VLC will not playback stream, VLC opens but does not load stream Zixi Plugin installed and in correct folder? → NO → Reinstall / move plugin Are you using correct / Universal VLC Version? → NO → Re/Install latest Universal VLC Is port 2077 open for inbound & outbound traffic (all subnets / AWS)? → NO → Open port in firewall / security group Is Pull Egress enabled on your license? → NO → Contact Zixi Sales Has your license been reloaded after any changes? → NO → Reload license via ZM or UI Is your VLC version compatible with plugin? → NO → Rollback to VLC 3.0.16 or 3.0.17 MacOS Ventura – VLC damaged or won't launch? → YES → Reinstall VLC 3.0.17.3 (Intel64 first, Universal + Rosetta if needed) + plugin ### Escalation Checklist If you have worked through all steps above and playback is still failing, please open a support ticket (Email: support\@zixi.com). Include as much as possible of the following so that the team may investigate the issue: - VLC version in use - Operating system and version - Zixi plugin version - Screenshot or details of your Broadcaster/ZEC license details - Evidence that port 2077 is open for inbound & outbound traffic on your Firewall (& AWS if relevant) - Output of a port 2077 connectivity test from the affected machine - Any error messages displayed in VLC (Tools > Messages, set verbosity to 2) [title] Source & Target States & Errors [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/ ## Source Unknown "Unknown" typically means ZEN Master has no prior connection record for that source, in that it has never successfully established a session. :::hint{type="success"} Unknown points to a configuration or provisioning issue. ::: ## Source Offline "Offline" means the source has connected before but is currently not reachable but ZEN Master has a history of it. :::hint{type="success"} Offline points to a connectivity or encoder issue on a previously working path. ::: ## No Response from Target The target was configured and ZEN Master is attempting delivery, but the downstream endpoint is not acknowledging. This is usually a receiving-end issue either firewall, service not running, or the target system is down. :::hint{type="success"} Check the destination host first. ::: ## Being Concealed / Error Concealment This indicates that ZEN Master (or the underlying Broadcaster) has Error Concealment enabled on that stream. The signal is experiencing packet loss or corruption, and the system is actively substituting/filling to mask the artifacts. This is not a fatal error — it means the stream is degraded but being held together. :::hint{type="success"} Treat this as an early warning to investigate source signal health or network path quality. ::: ## Version/Configuration Mismatch This error surfaces when there's a discrepancy between what ZEN Master expects for a device or stream configuration versus what it's actually seeing. In practice, this may comes up when Broadcasters are on vastly different software versions across a workflow, or when a channel configuration was pushed before a device fully updated. :::hint{type="success"} Check Broadcaster version consistency across the affected path and compare the ZEN Master channel config against the actual device settings. ::: [title] Best Practices: Naming Conventions in Zixi [path] Troubleshooting/Best Practices/ Zixi component names including channels, inputs, outputs, targets, adaptive groups, and ZEN Master resources, are used internally in configuration files, API calls, log entries, and URL-based endpoints. Using special characters in these names can cause unexpected failures that are difficult to diagnose, particularly in automation workflows, REST API integrations, and scripted monitoring pipelines. :::hint{type="warning"} Use only alphanumeric characters, hyphens, underscores and periods for naming conventions ::: ## What to Avoid Avoid all characters outside the safe set described above. Common problem characters include: | Character | Example | Why It's Problematic | | ------------- | ------------ | ----------------------------------------------------------------------------------------------------- | | Spaces | My Channel | Breaks URL parsing; must be percent-encoded as %20, which causes issues in API calls and log searches | | Forward slash | BBC/HD | Interpreted as a path separator in URLs and file systems | | Backslash | BBC\HD | Causes parsing failures in JSON and config files | | Ampersand | Sport\&News | Reserved in URLs; interpreted as a query string delimiter | | Hash | Channel#1 | Interpreted as a URL fragment identifier; truncates API requests | | Question mark | Test?HD | Interpreted as the start of a URL query string | | Percent | 50%Feed | Triggers percent-encoding interpretation in URLs | | At sign | feed\@site | Confused with authentication syntax in URLs | | Brackets | \[HD]Feed | Can break shell scripts, JSON parsing, and regex-based log filters | | Parentheses | Feed(Backup) | Can interfere with scripting, CLI tools, and API parsing | | Quotes | "Primary" | Breaks JSON serialization and command-line argument handling | | Colons | BBC\:HD | Reserved in URIs and can interfere with host\:port parsing | | Commas | CH1,CH2 | Often used as delimiters in API parameters; can split values unexpectedly | ## Safe Characters | Character type | Allowed | Notes | | -------------- | -------- | -------------------------------------------------- | | Letters | A–Z, a–z | Both upper and lower case | | Numbers | 0–9 | | | Hyphen | - | Good for word separation: bbc-hd-primary | | Underscore | \_ | Good for grouping segments: bbc\_hd\_primary | | Period | . | Useful for versioning or hierarchy: bbc.hd.primary | ## Recommended Naming Patterns Use a consistent naming convention across your deployment. A structured pattern makes names predictable, searchable and automation friendly. **Suggested format:** :::BlockQuote \\_\\_\\_\ ::: **Examples:** :::BlockQuote nyc\_espn\_hd\_primarynyc\_espn\_hd\_failover lon\_bbc1\_sd\_input aws-eu\_sport24\_1080p\_output ::: Keep names concise and machine-readable. ## Renaming Existing Components If you have existing resources with non-compliant names, plan renames carefully: 1. **Audit first:** Check your lists in ZEN Master or Broadcaster and identify all non-compliant names. 2. **Check dependencies:** Before renaming, verify whether the resource name is referenced in API integrations, monitoring scripts, or external systems (encoders, decoders, automation). 3. **Rename during a maintenance window:** Renaming an active channel or output will interrupt the stream. Always rename during scheduled downtime. [title] "Not Supported" error on a PULL input [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/ ### ERROR “Not Supported” error entry, on an PULL Input. This is a very basic message that could be caused by various reasons. ### RESOLUTION: Items to check if you see this error: **Version of the application (for example: Zixi Broadcaster) affected: **An older version of a Zixi application can be affected by a bug(s), which can trigger this issue. **Protocol enabled:** For example, a protocol not declared in the activation key at the license level, can also caused this issue. Please reapply your license or reach out to Support at [support@zixi.com](mailto\:support@zixi.com) **Incorrect stream information:** A wrong source hostname/IP, and/or an incorrect port can caused a malformed request, which could possibly generate this message. For example, if the source stream (coming from the source provider) was originally configured in ZEN Master, using the host IP address this can cause some issues. Instead, is recommended to obtain the PULL input information, from the Target configuration tab, in ZEN Master which will use a dynamic link to the Zixi IO Server for the specified account. [title] Broadcaster API Errors [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/ Explanations for Broadcaster API errors: - [Unauthorized](docId\:jw-AEEwpWKyPl7-VjW--v) - [Invalid CSRF token](docId\:POrY4Eh4jNGbsqdeMWk5T) - [HLS master playlists are not supported](docId\:BfMoC-q-ilp53otO5SlDt) - [Request failed with status code 500](docId\:wjywdXtEjKLL6JUpPIRza) - [URL or RTMP Stream parameter missing](docId\:okncq4qjWiXmPnV06V2M4) - [Encryption Error (Error 35)](docId\:VIlxiix5ND0v_s1QGxGr4) [title] Invalid CSRF token [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/Broadcaster API Errors/ ### ISSUE Invalid CSRF Token ### CAUSE All ZM API requests use a base URL [https://api.zen.zixi.com/v2](https://api.zen.zixi.com/v2) please verify the base URL. [title] Ubuntu Broadcaster Host ID changes after OS Upgrade [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/ **Broadcaster unlicensed after Ubuntu OS upgrade** ### CAUSE The Zixi license Host ID is a machine fingerprint built from virtual hardware parameters, including the vNIC's MAC address. Ubuntu OS upgrades touch the kernel, drivers, and the systemd/udev network stack that identifies that vNIC and can also trigger the hypervisor to reassign it. Any of that can shift the fingerprint, changing the Host ID and then the old license key no longer matches. This affects Ubuntu and not Rocky, as Rocky is RHEL-based, while Ubuntu is Debian-based with different kernels, different udev/network-naming behavior. This is an Ubuntu/Debian-specific quirk, and not related to the Zixi Software. ### RESOLUTION After the upgrade reboot, if the Broadcaster comes up unlicensed, get the new Host ID and re-apply the license key in the portal. **Before you upgrade a production box have your licensing information ready to reactivate the broadcaster.** [title] ZEN Master - Errors and Troubleshooting [path] Troubleshooting/ In this section you will find explanations for ZEN Master error messages and advice on how to diagnose and resolve the issue. ## General Note - Error/Warning History Error and Warning messages now show a two-hour history that will give you an immediate sense of whether this is a permanent (or long-term) or intermittent issue: ![Error with Two-Hour History](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/OyYlscCZlxCvO085sgr8K_image.png) - [502 Bad Gateway Error](docId\:kTvu5Ox1R-PapUWX_6WeE) - [Broadcaster API error: timeout of 12000ms exceeded](docId\:qgH6shz0MRs6fBGctB3nF) - [Broadcaster Authorization Configuration Error](docId\:bBFDjHFLe5gKwtUgXT70z) - [Broadcaster Authorization plugin error](docId\:FGTzbolu792Dv4A9kGqog) - [Broadcaster Authorization Configuration Error - Update via ZEN Master to correct](docId\:enaW67KY3cQFBsnmM8-eA) - [Certificate Error](docId\:qgHgwTcuO2TgjrfbnLaot) - [Content Analysis error: Video is not changing for more than 30 seconds](docId\:HR6FdiNNWUm8jFSoWkNcE) - [Decryption Error - Verify or configure decryption key Error](docId\:k1S5npvhrLlZOROnKl1Ut) - [Error - Bitrate above configured maximum](docId:1Q5StpPL_ngx0iGtjaca2) - [Error: Create transcoded input error, not found in response](docId\:n4_XmVP9dlV8MdoLRJvMe) - [Error requesting Azure Authorization Token](docId:7zLrK5CxE4-NWZOlXmuOw) - [High Max Bitrate Configuration](docId\:IJrN4V8zGysjoKXEVCkHx) - [Intermittent frozen video/silent audio errors (cloned)](docId\:Uzc-ouyLvxyF7XseyB9UO) - [Proxy Not Detected](docId\:p5hm7RuldpwYSbeveXzL2) - [Removing a PID using a PID mapping profile](docId\:j08lXgPzOegc5gh9fGtID) - [Source not found in cluster - Verify Broadcasters Status](docId\:E4eNcy4bbxGw1Az6VWiRI) - [Source Status & Error Reference](docId\:HODONx74L3mVaP1b3g79Z) - [Target redirected to Broadcaster but no connection - Verify firewall/network Error](docId\:cGUY460bBTkhODiQoh5yT) - [Unable to Allocate processing broadcaster(s) Error](docId\:cnchVeGskfKXFZYcxMVAA) - [Unknown Status Missing Broadcaster Data](docId\:j-j_qCOhtHdpFcRW2eDJJ) - [Upgrade a broadcaster through ZEN Master](docId:-3ww9dB3efm60ch9B0obx) [title] Sizing latency, buffer and max bitrate [path] Troubleshooting/Best Practices/ Two settings decide whether a Zixi stream can recover lost packets: latency and Max Bitrate. Loss that looks like a network fault often comes from one of them being set too tight. ## Latency is the recovery window A lost packet can be replaced only if the resend arrives before the latency runs out. A longer latency survives longer drops and longer round-trip times, at the cost of delay. Set it to at least 4 times the round-trip time between the two ends. ## Max Bitrate sizes the recovery buffer On a Zixi input, the Broadcaster keeps enough packets to cover the latency, or 1 second if the latency is shorter, at the Max Bitrate. It does not cap the stream. If Max Bitrate is close to the feed rate, bursts and resent packets overflow the buffer and count as not recovered. Set it to about 1.5 times the feed's average rate: for a 20 Mbps feed, 30 Mbps. At 0, the Broadcaster uses the rate the sender reports. Max Bitrate is in the input's advanced settings: add `?advanced=1` to the Broadcaster URL. In the API the parameter is `maxbr`. ## Keep latency at or below 65,000 ms A value above 65,535 ms does not work as entered. HLS inputs accept at most 60,000 ms. ## SRT latency SRT latency defaults to 1000 ms. The Broadcaster uses the value as entered and does not adjust it to the round-trip time, so set it to at least 4 times the round-trip time yourself. ## UDP outputs have no latency setting A UDP output sends packets as they arrive and has no recovery. It never connects, so it never needs to reconnect after a network drop: packets lost on the way are simply lost. If a UDP output goes offline, look at its input, the destination address, the network interface or the license. ## "Max bitrate times latency too high" This error means the recovery buffer would need more than 524,288 packets. That is about 5.5 Gbps for each second of latency. Lower one of the two. [title] Change the UI Port for Broadcaster [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/ If for any reason you require the Broadcaster User Interface to be changed from port 4444 there is a few ways to make this adjustment. 1. **Within the User Interface directly** :::Paragraph{indent="2"} Go to the Settings Tab and in "Web Server Port" enter the new port number. ::: :::Paragraph{indent="2"} Hit Apply ::: :::Paragraph{indent="2"} Restart the broadcaster ::: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/NlnW26zyIRoOZusCqyUMn-20260218-220534.png) 2. **Using sed or Linux commands** :::Paragraph{indent="1"} After installing the Broadcaster, use sed or similar Linux command to update the port in the broadcaster-config.xml file. ::: :::Paragraph{indent="2"} Stop the Broadcaster process ::: :::Paragraph{indent="2"} Run the sed command: ::: :::BlockQuote sed -i 's/4444/5555/g' /zixi/zixi-broadcaster\_linux64/broadcaster-config.xml ::: :::Paragraph{indent="2"} Or Update in the config file: ::: :::Paragraph{indent="2"} Change* \ \4444\ \* to *\ \5555\ \ *for example. ::: :::Paragraph{indent="1"} Restart the Broadcaster process. ::: 3. **Using API commands** :::Paragraph{indent="1"} Install the Broadcaster ::: :::Paragraph{indent="1"} Make an API call on the local machine like the following: curl -i --user "admin:1234" http\://127.0.0.1:4444/apply\_settings.json?gui\_web\_port=5555 ::: [title] Unauthorized [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/Broadcaster API Errors/ ### ISSUE Getting "Unauthorized" error when making API calls. ### CAUSE No API key set up in ZEN Master ### RESOLUTION Set API key in ZEN Master - Log into ZEN Master account - In the Menu go to Administration > API Keys ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/PJJ9d2nIm4bR9sVudcnGR_image.png" size="36" width="468" height="911" position="center" caption="ZEN Master menu" alt="ZEN Master Menu " showCaption="true"} - Click the "+ Add Key" button ![Add key screenshot](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/bsVT0Vg6JaheOOxPID4VK_image.png "Add key screenshot") - Create New API Key ![Create New API Key screenshot](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/1_h3g1O-JOmu2AMC608Z0_image.png "Create New API Key screenshot") - Hit Save [title] "INVALID CSRF TOKEN" [path] Troubleshooting/Broadcaster - Errors and Troubleshooting/ ### ERROR Invalid CSRF Token on Source ### RESOLUTION Clear your browser cache. [title] Broadcaster API error: timeout of 12000ms exceeded [path] Troubleshooting/ZEN Master - Errors and Troubleshooting/ ### ISSUE Error "Broadcaster API error: timeout of 12000ms exceeded" displaying in ZEN Master and the data is not updating in the graphs during this error. ### CAUSE There is a disruption or issue with your network and the broadcaster/ZEC has not been able to communicate with ZEN Master to provide a monitoring update. ### RESOLUTION Once the network is connected and stable, the broadcaster/ZEC will update ZEN Master the next time it polls and the monitoring will resume and the error will clear. [space] ZaaS (/zaas) [title] ZaaS (Zixi-as-a-Service) [path] / ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/vPRZ3yl8_Q-LxrIfw1qA__zaas-smaller.png) ZaaS allows you to take advantage of Zixi's ability to deliver your video content with broadcast quality and ultra-low latency to the destinations you choose without you having to install, manage, and monitor the software. ## How it works To see if ZaaS is a good fit for your organization, [contact Sales](https://zixi.com/contact/contact-zixi-sales/). When you purchase ZaaS, Zixi will work with you to determine your needs, and then set up Zixi Broadcaster clusters in the cloud in two different geographical regions (for redundancy and failover in case of issues). We will also work out a [redundancy](docId\:k9mukecY4pzgeowUJDrHH) strategy to minimize the risk of delivery failure to your target destinations. ![Sample Redundancy Configuration](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-bFT6NMc6VTcfRboCdHopB-20250430-163855.svg "Sample Redundancy Configuration") Once the infrastructure setup is complete, you can set up your source stream(s), channel(s), and targets in [ZEN Master](docId\:vzz5bE4XXIpP9wLuLps4N). Zixi will also provide assistance with this if you need it. The most relevant parts of the ZEN Master documentation can be found under: - [Sources](docId\:WrXQ4NJAqG_e7h-u3v0de) - [Channels](docId\:sBYG_3vKUBrdtFVjV1X0K) - [Targets](docId\:pv_76hSvp7_gsv7DbtamE) :::hint{type="info"} There are other configuration options you may want to take advantage of in ZEN Master, such as SSO, PID Mapping, and Transcoding profiles. You will find all options explained in the ZEN Master documentation and the Zixi team will provide assistance wherever you need it. ::: As your streams flow through ZaaS toward their targets, we will monitor the ZaaS infrastructure set up for you and inform you of any issues or scheduled maintenance so that you can let your clients downstream know. [space] ZEN Master (/zen-master) [title] Adding a New ZEC [path] ZEN Master/ZEN Master User Guide/Zixi Edge Devices/Adding a ZEC/ **To add a ZEC:** :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click the **Zixi Edge Devices**. ::: :::WorkflowBlockItem Click **+Add.** ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/XfkkxWnvS_oeLb0d0xIkN_image.png" size="90" width="1095" height="452" position="center" alt="Create Edge Device Dialog" showCaption="false"} ::: :::WorkflowBlockItem Click **ZEC**. The **Create New ZEC** screen is displayed: ![Create New ZEC screen](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/j6wgTp4k4iIgj8DejCiLV_image.png) ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, type a logical name for the ZEC. ::: :::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 ZEC 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 ZEC. 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 ZEC’s location is used to represent it in the proper position in the Map display (see MAPS). By default, the location is determined automatically based on the ZEC’s IP. If you would like to manually set the location of the ZEC (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, in the **API User **field, enter the username for accessing the ZEC instance. This enables ZEN Master to use the API to monitor and manage the ZEC instance. (Default value: **admin**) ::: ::::WorkflowBlockItem In the **API Password** field, enter the password for accessing the ZEC - the password **must** match the password used to login to the ZEC UI in order for ZEN Master to communicate successfully with the ZEC. The default password is 1234. Unless you have changed the password for this ZEC, enter 1234 in this field. :::hint{type="warning"} For security reasons, we recommend that you change the default admin password in the ZEC UI before adding it to ZEN Master. ::: :::: ::::WorkflowBlockItem In the **SSH Key** field, select from the drop-down list one of the existing remote access keys to be used for SSH tunneling between the Zixi Feeder and ZEN Master. :::hint{type="info"} If you would like to configure a new SSH Key, see [Configuring SSH Keys](docId\:qXuh0ckZbygbyCRZvjtwS). ::: :::: :::WorkflowBlockItem Select the **Termination protection** checkbox if you want to prevent deletion of the ZEC. ::: :::WorkflowBlockItem In the **Initial State **section, select the Disabled checkbox if you would like to disable this Feeder upon initial configuration. ::: ::::WorkflowBlockItem Select the **Muted** checkbox if you would like to disable error/recovery notifications for this Feeder upon initial configuration. :::hint{type="info"} You can Enable/Unmute the Feeder at any time. ::: :::: :::WorkflowBlockItem Click **Save**. The ZEC is configured and will remain in Pending state until you configure the initial connection to the ZEC, see [Connecting the ZEC (ZEC UI)](docId\:DfXSrrQpRXKAzXK2aJQ7f). ::: ::::: ## ZEC Configuration Parameters Table | Parameter | Description | | ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Info** | | | Name | Specify the name of the ZEC 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 ZEC 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 Feeder. 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 ZEC’s location is used to represent it in the proper position in the Map display (see ). By default, the location is determined automatically based on the Feeder’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** | | | API User | Enter the username for accessing the ZEC instance. This enables ZEN Master to use the API to monitor and manage the ZEC instance. The default username on Zixi Feeders is admin. Unless you have changed the username for this Feeder, verify that “admin” is entered in this field (default). | | API Password | Enter the password for accessing the ZEC. The default password on Zixi Feeders is 1234. Unless you have changed the password for this Feeder, enter 1234 in this field. | | SSH Key | Select from the drop-down list one of the existing remote access keys to be used for SSH tunneling between the ZEC and ZEN Master. If you would like to configure a new SSH Key, see . | | Termination protection | Select this checkbox if you want to prevent deletion of the ZEC. To delete it you will have to first disable the termination protection. | | **Initial State** | | | Disabled | Select this checkbox if you would like to disable this ZEC upon initial configuration. | | Muted | Select this checkbox if you would like to disable error/recovery notifications for this ZEC upon initial configuration. | [title] Logging in to ZEN Master [path] ZEN Master/ZEN Master User Guide/ **To login to ZEN Master:** :::::WorkflowBlock ::::WorkflowBlockItem In your web browser, navigate to: https\://\.zen.zixi.com. A user authentication window opens. If your account is configured for SSO, then the Sign-in screen offers the option to either sign in through your SSO account or using ZEN Master credentials. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Qgt7jqfRQS_e5aGNcpby2_image.png" size="46" width="355" height="185" position="center" alt="Login Window" showCaption="false"} :::hint{type="info"} Once your email has been associated with an SSO account you are no longer able to login to that account using ZEN Master credential. ::: :::: ::::WorkflowBlockItem To sign in using an SSO provider, click on the blue bar for the desired provider and follow the procedures for signing in using that service. :::hint{type="info"} The first time that you sign in using an SSO provider you will need to activate the account using your existing credentials for that provider. ::: :::: :::WorkflowBlockItem To sign in using ZEN Master credentials, - Click **Sign In with ZEN Master credentials**. The ZEN Master sign in window is displayed ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/3F8oae9nJWZ07Tf8ka_m-_image.png" size="36" width="356" height="352" position="flex-start" showCaption="false"} - In the **Email** field, enter your email address. - In the **Password** field, enter the password that you received from your Zixi representative. ::: ::::WorkflowBlockItem Click **Login**. :::hint{type="info"} If you forgot your password, you can generate a new password by clicking **Forgot Password? > Send Email**. ::: :::: ::::: [title] Broadcaster Cluster Configuration Parameters Table (for Manual and Managed Clusters) [path] ZEN Master/ZEN Master User Guide/Broadcasters/Creating a Broadcaster Cluster/Creating a New Broadcaster Cluster/ ***Configuration (for Manual and Managed Clusters)*** | **Parameter** | **Description** | | ---------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify the name of the Broadcaster Cluster 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 Broadcaster Cluster 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 Cluster. 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. | | DNS Prefix | Specify a unique domain name for sending Sources to this cluster. | | IP Whitelist | Select this checkbox if you would like to control access to this cluster by limiting access to Push inputs and Pull outputs to specific IP address (for an AWS cluster this will enable you to control the AWS security groups).
Note: If you select **IP Whitelist**, then you must use ZEN Authorization mode for this cluster.
Note: If you selected **IP Whitelist** then after configuring the Broadcaster Cluster you must input the IPs that will have access to this cluster, see [Adding IPs to the Whitelist](docId\:RicoDzjUvWVliz6i2QTgX) . | | DTLS | Select this checkbox if you would like to encrypt the stream dynamically using DTLS. (This feature is supported for v12.2+ Broadcasters) | | Ignore DTLS certificate when not supported (for DTLS) | Select this checkbox if you would like to enable resources using older versions of Zixi software (\* **Minimize the number of broadcasters** (default) – transfers excess load to other broadcasters only when the allotted capacity on the host broadcaster is filled. * **Uniform distribution** – distributes the load equally between all available broadcasters under all circumstances. | | Log SCTE-35 | Select this checkbox if you would like to log SCTE-35 markers for streams in this cluster.
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. | | RTMP Servers | Select this checkbox if you need to receive RTMP push inputs. | | RTMP Server Port | Specify the port in the Broadcaster that will be used to receive the RTMP push inputs. | | Inject Metadata on Inputs | Allows Zixi create a PID that carries information about what hops a feed has travelled through on the way to its destination, it includes things like CC errors and IAT at each hop. The information is useful for debugging issues with streams. | | ***Configuration (for Manual)*** | | | Management Type | Select **Manual. **After creating a manual Broadcaster cluster, you must configure each Broadcaster instance for use in the cluster. To do this, see [Adding a Broadcaster to a Manual Cluster](docId\:xYscySO498lY77ZjQr-51) . | | Authorization Mode | Select one of the following options:
* **ZEN Master** – ZEN Master automatically verifies the authorization for each ZEN entity (e.g. Sources, Channels and Targets) that accesses the Broadcaster cluster. If you would like to allow access to inputs/outputs that are not configured in ZEN Master, then in the **Allow access…** section, select the **Push Inputs** and/or **Pull Outputs** * **Global Password **– Broadcasters are automatically configured to authorize all connections using a single global password. The global password will be used in the Source Password field when you configure a Source. In the **Password** field, enter the password OR click **Random **to generate a random password. * **Free for All **– Broadcasters will be automatically configured to allow all inputs/outputs to connect. Select **Inputs** and/or **Outputs** to automatically allow them to connect. * **Manual** – ZEN will not authorize connections. You will need to authorize each connection independently.
Note: All authorization modes other than *Manual* will override the authorization configured on your Broadcasters. Therefore, if you have streams on your Broadcasters that are not configured on ZEN Master, then any mode other than *Manual* or *Free for All* may interrupt those streams. | | Allow access to inputs not configured in ZEN Master (for ZEN Master Authorization) | Select the **Push Inputs** checkbox if you would like to automatically allow access to Push Inputs. Select the **Pull Outputs** checkbox if you would like to automatically allow access to Pull Outputs. | | Termination Protection | Select the **Deletion protection** checkbox if you want to prevent deletion of the Broadcaster Cluster. | ## Managed Clusters ### Configuration for Managed Clusters | Parameter | Description | | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Management Type | Select one of the AWS, Azure or GCP accounts configured in ZEN Master from the list shown under AWS, Azure or GCP in the drop-down menu. To create a new cloud service account see [Linking an AWS Account](docId\:erygXkCUfmmZ8BaKidJz4), [Linking an Azure Account](docId\:jSST1KXHRRRFCdyc1lENl) or[Linking a Google GCP Account](docId\:JBuzi2tJvSpS3o_VzVXxH) . | ### AWS Clusters | **Parameter** | **Description** | | --------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Region | Select from the drop-down list the AWS region. | | Key Pair | Select from the drop-down list one of the available Key Pairs to access the cluster. If no Key Pair is displayed, then go to your Amazon account to setup your Key Pair. | | VPC | Select from the drop-down list one of the available VPC (Virtual Private Cloud) networks to which the cluster will be connected. | | Subnets | Select from the drop-down list one or more of the subnets that are available in this VPC. | | Security Groups | Select from the drop-down list one or more of the security groups associated with this VPC. If no Security Group is displayed then go to your Amazon Account to configure your security groups (for guidance in setting up your Security Groups see Amazon Security Groups) or use the ZEN IP Whitelist to manage your AWS security (see the following step). | | Manage security groups via ZEN Master IP Whitelist (for IP Whitelist) | Select this checkbox to use the IP Whitelist to manage your AWS security. | | Instance Type | Select from the drop-down list one of the available AWS instance types that will be used in this cluster. | | Root Device Size \[GiB] | Specify the capacity of the hard drive (in GiB). | ### Azure Clusters | **Parameter** | **Description** | | ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Region | Select from the drop-down list the location of the account to be used for this cluster. | | Virtual Network | Select from the drop-down list a VN in your Azure account.
Note: You need to have a Virtual Network in your Azure account in order to be able to create a Broadcaster Cluster in ZEN Master. If you don’t have a VN in your account, you can create one via the Azure portal. | | Subnet | Select from the drop-down list a subnet that is available in the specified VN. | | Network Security Group | Select from the drop-down list a network security group for this cluster. | ### GCP Managed Clusters | **Parameter** | **Description** | | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------- | | Region | Select from the drop-down list the region of the GCP account. | | Zones | Select from the drop-down list one or more zones in the specified region. | | Network | Select from the drop-down list one or more of the subnets that are available in the specified region. | | Machine Type | Select from the drop-down list the type of machine to be used for the cluster.
Note: Both n1 and n2 machine types are supported. | | GPU Type | Select from the drop-down list the type of GPU to be used for the cluster. | | Root Device Size | Specify the size of the root device in GiB. | ### All Managed Clusters | **Parameter** | **Description** | | ---------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Activation Key | Enter the activation key for your Zixi Broadcaster license. | | API User | Enter the username for accessing the Zixi Broadcaster via API. | | API Password | Enter the password for accessing the Zixi Broadcaster via API. | | Broadcaster Version | Select from the drop-down list the Zixi Broadcaster version that you want to install. | | Authorization Mode | Select one of the following options:
* **ZEN Master** – ZEN Master automatically verifies the authorization for each ZEN entity (e.g. Sources, Channels and Targets) that accesses the Broadcaster cluster. If you would like to allow access to inputs/outputs that are not configured in ZEN Master, then in the **Allow access…** section, select the **Push Inputs** and/or **Pull Outputs** * **External Server **– the request for content is relayed to an Authorization Server. In the **Authorization Server** field, enter the URL of the external server. * **Global Password **– Broadcasters are automatically configured to authorize all connections using a single global password. The global password will be used in the Source Password field when you configure a Source. In the **Password** field, enter the password OR click **Random **to generate a random password. * **Free for All **– Broadcasters will be automatically configured to allow all inputs/outputs to connect. Select **Inputs** and/or **Outputs** to automatically allow them to connect. * **Manual** – ZEN will not authorize connections. You will need to authorize each connection independently.
Note: All authorization modes other than *Manual* will override the authorization configured on your Broadcasters. Therefore, if you have streams on your Broadcasters that are not configured on ZEN Master, then any mode other than *Manual* or *Free for All* may interrupt those streams. | | Allow Access to inputs not configured in ZEN Master (for ZEN Master Authorization) | Select the **Push Inputs** checkbox if you would like to automatically allow access to Push Inputs. Select the **Pull Outputs** checkbox if you would like to automatically allow access to Pull Outputs. | | Termination protection | Select the **Deletion protection** checkbox if you want to prevent deletion of the Broadcaster Cluster. | ### Advanced Parameters | **Parameter** | **Description** | | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | HTTP Streaming Port | You can change the HTTP streaming port from the default (7777) to a custom port. The custom port should match the configuration on the Zixi Broadcaster. | | Elastic IP Allocation IDs (for Managed) | Enter comma separated Elastic IP Allocation IDs. | | Bandwidth Limits Input/Output | Specify the bandwidth limits in Mbps. | | Default HLS/ DASH segment configuration (for Managed) | Specify the Count and Duration parameters for HLS and DASH segments on this Broadcaster Cluster. | | ***Transcode Thresholds*** | These are used by ZEN Master to determine whether an additional transcoded Channel can be added to the broadcaster. Adjust the following thresholds as desired: | | CPU Threshold \[%] | Specify the percentage of CPU being used. | | Memory Threshold \[%] | Specify the percentage of memory being used. | | GPU Threshold \[%] | Specify the percentage of GPU being used. | | GPU Memory Threshold \[%] | Specify the percentage of GPU memory being used. | | GPU Decoder Threshold \[%] | Specify the percentage of GPU decoder pipeline being used. | | GPU Encoder Threshold \[%] | Specify the percentage of GPU encoder pipeline being used. | | Process Priority (for Managed clusters) | This setting determines the process priority of your Broadcasters. | | Enable Real-time Broadcasters process priority | This setting is deselected by default. You can increase the Broadcaster's process priority by selecting it. This may be beneficial for sending streams to highly sensitive IRDs. However, this should not be done without consulting with your customer success agent. | | Billing Codes | If you would like to track usage for this Broadcaster, enter your **Billing Code** details, see . (Supported for Broadcasters v14.8+) | | Install AgentZ automatically | Select this checkbox to install AgentZ automatically. Agent Z is a Sidecar tool that sits on a Zixi Broadcaster, it acquires the system health data and other statistics locally and pushes it to ZEN Master. By enabling this option, ZEN Master will automatically install AgentZ on any existing and future Broadcasters connected to the Cluster. The feature is off by default. Due to AgentZ installation requiring a restart, ZEN Master will not auto-install AgentZ on a Broadcaster that already contains any inputs to avoid disturbing active streams. | [title] Billing Codes [path] ZEN Master/ZEN Master User Guide/Introduction to ZEN Master/ Billing codes are used to identify and differentiate traffic. A billing code can be defined on Sources, which represent inputs to a Broadcaster, and on Targets, which represent outputs from a Broadcaster. A billing code can also be applied to an entire Broadcaster Cluster. When a billing code is defined on 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 can be assigned to standard traffic related to the Source or Target or specifically to auto-pull events (i.e. when a ZEN Master object is automatically transferred to a different Broadcaster to increase efficiency). Billing codes are created by Zixi personnel on the Zixi Customer Portal for a particular organization. Zixi can create multiple Billing codes for an organization, enabling them to apply different codes to different traffic. Billing codes are password protected and ZEN Master validates each billing code that is used. If you would like to use billing codes in your workflows, please discuss it with your Zixi representative. ## Use Cases ### Differentiating Between Clients If you are receiving video content from different contributing clients or sending video content to multiple external organizations, you can designate distinct billing codes for each of your clients. You can then assign the client’s billing code to each Source or Target associated with that client. Your organization will then be able to bill each of their clients according to their usage. ### Charging only for Billable Usage When Zixi traffic is sent between distinct organizations, situations may arise in which the usage of only one of those organizations is billable. For example, if the contributor is using a Zixi Broadcaster to send outputs as if it were a Zixi Feeder, then only the receiving organization should be billed for that traffic. In that case, the receiving organization can request a billing code and assign it to their Targets. They can then ask the contributor to assign the identical billing code to each of the Sources that they are sending. In this way, Zixi will know to bill only the organization that is receiving the traffic. [title] Linking a Google GCP Account [path] ZEN Master/ZEN Master User Guide/Configuration/Configuring Google GCP Account Credentials/ To create a GCP account and connect it to ZEN follow the procedure shown in the **Documentation** tab, as described below: ::::WorkflowBlock :::WorkflowBlockItem Login to your GCP service accounts console at [https://console.cloud.google.com/iam-admin/serviceaccounts](https://console.cloud.google.com/iam-admin/serviceaccounts). ::: :::WorkflowBlockItem Click **Select a project**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Xbxa9axd1nHogxWTN9w6j_image.png" size="90" width="962" height="241" position="center" alt="GCP Account List" showCaption="false"} A window opens showing your projects. ::: :::WorkflowBlockItem Select a project. ::: :::WorkflowBlockItem Click on + **Create Service Account**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/2YF8pCgGhZmNIi9hBhPuJ_image.png" size="90" width="1350" height="386" position="center" alt="Create service account" showCaption="false"} A Create service account window opens. ::: :::WorkflowBlockItem In the **Name** field, enter a name for the account e.g. 'ZEN Master'. ::: :::WorkflowBlockItem Click **Create.** ::: :::WorkflowBlockItem In the **Role** field, select from the dropdown list **Service Account > Service Account User**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/XeE10J0yTLu9Mtgzao5i4_image.png" size="80" width="678" height="484" position="flex-start" alt="Service Account User Role" showCaption="false"} ::: :::WorkflowBlockItem Click **+Add Another Role**. ::: :::WorkflowBlockItem In the additional Role field, select from the dropdown list **Compute Engine > Compute Admin**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/uCMM5qRB1SuvtqbEeElfc_image.png" size="80" width="698" height="557" position="flex-start" alt="compute admin Role" showCaption="false"} ::: :::WorkflowBlockItem Click **Continue**. ::: :::WorkflowBlockItem Click **+ Create Key**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/MCzI6AB_iBLwB6i6q2BbG_image.png" size="58" width="573" height="388" position="flex-start" alt="Choose Key Type" showCaption="false"} ::: :::WorkflowBlockItem Select the **JSON** radio button (default). ::: :::WorkflowBlockItem Click **Create**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/MCzI6AB_iBLwB6i6q2BbG_image.png" size="58" width="573" height="388" position="flex-start" showCaption="false"} ::: :::WorkflowBlockItem Navigate to the folder where you would like to save the download file and click **Save**. ::: :::WorkflowBlockItem In the pop-up notification window, click **Close**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/iO7il9yXReS5k-YqlFCjJ_image.png" size="56" width="810" height="240" position="flex-start" alt="Key Saved" showCaption="false"} ::: :::WorkflowBlockItem In ZEN Master, go to **Configuration > Google GCP**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/qFsB869pdTvL1BnCfwz5E_image.png" size="90" width="1259" height="299" position="flex-start" alt="GCP Accounts" showCaption="false"} ::: :::WorkflowBlockItem Click **+ Add Account**. The **Add New GCP Account** window is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/jHwVkb7JZr8rp0dnV80MY_image.png" size="80" width="843" height="380" position="flex-start" alt="Add New GCP Account window" showCaption="false"} ::: :::WorkflowBlockItem In the **Name** field, enter a name for the account. ::: :::WorkflowBlockItem Click **Choose File**. ::: :::WorkflowBlockItem Navigate to the Key file that you saved from your GCP account and click **Open**. ::: :::WorkflowBlockItem The JSON key is added to the New Account window. ::: :::WorkflowBlockItem Click **Save**. Your GCP account is now linked to ZEN Master. You can now launch Broadcaster Clusters on this GCP account. ::: :::: [title] Overview [path] ZEN Master/ZEN Master User Guide/Introduction to ZEN Master/ ZEN Master is a cloud-based live video orchestration and monitoring control plane that provides a centralized view of the entire Zixi Platform deployment. With ZEN Master your entire global video delivery network, from acquisition to delivery, is managed from a single pane of glass. You can configure, orchestrate, manage and monitor live broadcast channels at scale across industry protocols, covering an entire supply chain of integrated services and devices. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/WmUc_wBaMdJuYv4TSnuGZ_image.png" size="90" width="580" height="305" position="center" alt="ZEN Master Architecture" showCaption="false"} - **Simple Task Oriented Management** - Instead of configuring inputs and outputs on each individual component throughout the entire deployment, ZEN Master abstracts the underlying infrastructure into simple task-oriented processes. For example, instead of configuring input and output streams on independent components for acquisition/aggregation, processing, and distribution, you can simply define a live linear channel, and the entire configuration is setup automatically, including redundant components for ultimate resiliency. - **End-to-end Orchestration** - Once all the resources have been configured, ZEN Master orchestrates all the resources along the path to create an end-to-end live streaming delivery platform. By managing the entire supply chain in one place, ZEN Master enables ongoing monitoring of the channels and the underlying resources. This includes their status, resource consumption levels (e.g. CPU and Memory consumption levels), all the events and errors, and more. - **High availability** – instead of manually configuring redundant components and ensuring a comprehensive end-to-end high-availability setup, ZEN Master automatically takes care of the high-availability of its streaming channels. All you have to do is set up channels and ZEN Master takes care of the rest, enabling automatic failover in case of unavailability, including multi-region deployment architectures. - **Advanced security **- ZEN Master offers advanced security features that ensure privacy and security for multi-tenant deployments. In addition to the security solutions offered by the underlying cloud hosting providers, ZEN Master offers robust yet simple access and permissions management based on Tags. This type of permissions scheme provides granular control on the resource, object (e.g. channels), and action levels (e.g. receive notifications). In addition, the communications between the Zixi Feeder and the ZEN Master service is secured by SSH tunnels. [title] Redundancy in ZEN Master [path] ZEN Master/ZEN Master User Guide/Introduction to ZEN Master/ ZEN master supports multi-level redundancy to ensure availability of the content delivery. Your deployment may include multiple redundant Target hosts. You can configure both the Channel (which outputs the content from ZEN Master) and the Target (which receives the content) for redundancy. Redundancy of sources can be configured in Pass-Through Channels and redundancy of hosts can be configured in Push or RTMP Targets. This feature is relevant for single bitrate push outputs only. Pull outputs enable any host to access the stream. ZEN manages the various configurations as follows: - **1 Source → 1 host** - if there is one Source in the Channel and one host in the Target then the content is sent directly from the Source to the host and the content is available as long as both elements are active. In this case, you don't need to configure a Secondary Source in the Channel nor an Alt. Target. - **1 Source → 2 hosts **- if there is a single Source in the Channel and there are two hosts in the Target, the content is sent from the Source to the primary host as long as it is available. If the primary host becomes unavailable then the Source is sent to the alternate Target host. In this case, you don’t need to configure a Secondary Source, but will need to configure an Alt. Target. - **2 Sources → 1 host** – if there are two Sources in the Channel and one host in the Target then two outputs are created (one on each Broadcaster) and both are pushed to the same Target host. The host receives the output from the primary Source as long as it is available. If the primary Source becomes unavailable, then the host receives output from the secondary Source. Some services such as Akamai do not support output of multiple Sources to a single host. In this case, you need to configure a Secondary Source, but will not need to configure an Alt. Target. - **2 Sources → 2 hosts** – if there are two Sources in the Channel and two hosts in the Target then two outputs are created (one on each Broadcaster) and each is pushed to a different host. As long as all elements are active the content is available on both hosts. If one path fails, then the other path remains available. For this configuration, the Channel status remains OK as long as one of the paths is active. In this case, you need to configure a Secondary Source and configure an Alt. Target. If you would like to monitor the status of each path separately, you must create two separate Channels and send each one to a different Target. Then you will have two completely independent pathways for delivering identical content. :::hint{type="info"} When configuring redundant Sources, make sure that each Source is located on a separate Broadcaster within the same Broadcaster Cluster so that one of the Sources will remain active if the other is disabled. ::: [title] Time Zone Selection [path] ZEN Master/ZEN Master User Guide/Management Console UI Elements/ For teams and environments spanning multiple time zones, ZEN Master provides the ability for users to set a global time zone to assist with coordinating support and incident management. The time zone can be set via the time zone picker at the top right of the console. When changed, all Date/Time data updates to the corresponding time in the selected time zone. :::hint{type="info"} The setting is stored in your account, so it is maintained even if you switch to another browser. ::: **To change the time zone: ** ::::WorkflowBlock :::WorkflowBlockItem At the top-right of the console, click the **Select Time Zone** drop-down menu. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/L9x8iKIfSMyjCErV1epWp_image.png" size="58" width="1186" height="438" position="center" alt="Timezone Selector" showCaption="false"} ::: :::WorkflowBlockItem Select the desired time zone. All the times displayed on the UI, including events, graphs, etc. will use the selected time zone. ::: :::WorkflowBlockItem You can also choose to use the US or EU date/time format. ::: :::: [title] Adding a New Events Profile [path] ZEN Master/ZEN Master User Guide/Configuration/Configuring Events Profiles/ You can create new Events Profiles (based on the default profile) in which you adjust the settings for each individual rule that you would like to change from the default behavior. **To create a new Events Profile:** ::::WorkflowBlock :::WorkflowBlockItem In the Main Navigation, click **Configuration > Events Profiles.** The **Events Profiles** screen opens. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Events Profile** window is displayed. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-5myj42CvC8zs874xL-3S4-20250825-111448.png) ::: :::WorkflowBlockItem In the **Name** field, enter a name for the new Events Profile. Choose a name that is representative of the set of rules that you plan to apply to your objects. ::: :::WorkflowBlockItem Edit the Events Profile rules by following the instructions in the [Editing Events Profile Rules](docId\:WJHCXAbqATmvsezByH8z7) page. ::: :::: [title] Working with Graphs [path] ZEN Master/ZEN Master User Guide/Management Console UI Elements/ ZEN Master features a wide variety of graphs that allow you to monitor the resources, objects, and networks over time. In most cases, the data is gathered from the underlying resource/object (e.g., Broadcaster, ZEC, etc.) and displayed in the relevant graph format and units/scales. # Understanding the legends Most graphs display multiple measurements in a single graph to provide multiple perspectives and help in the troubleshooting process. Each measurement and its related color appears in the legend, which is located underneath the corresponding Y-axis. The Y-axis adjusts to accommodate the min and max values of the entire displayed graph, expanding or contracting to show as much detail as possible for the given range. For example, the following graph measures the CPU (green) and Memory (yellow) utilization. Both legends are located underneath the Y-axis on the left as they share the same unit scale, which in this case is the percentage.  The X-axis refers to the timescale of the graph, with the right-hand edge being the current point in time, left of which the data progresses further into the past. ![Sample graph](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ObgevHo7BbMZx9Q-0ss22_image.png) # Viewing the measurement details To view the exact measurement details of a graph at any point in time, hover your mouse over the graph at the desired point in time. ![Getting details for point on the graph](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/H1OiQXmKjWruN_Msmhv9J_image.png) # Changing the time range There are multiple ways to change the timescale displayed on the graph: - Entering an absolute time range - Selecting a relative time range  - Navigating back/forward across the time range - Zooming in to a selected range - Zooming out ## Changing the time range by entering an absolute time range To change the time range by entering an absolute time range: ::::WorkflowBlock :::WorkflowBlockItem Click the **Time Range** field. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/W1s-UaPbk1Pv2ul7iqzX9_image.png" size="32" width="329" height="91" position="flex-start" showCaption="false"} ::: :::WorkflowBlockItem Under the **Absolute time range** section click the **From** field or enter an exact date and time in the following format – YYYY-MM-DD HH. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/zPOxU5fM0cVaEIBPb4Mo7_image.png" size="68" width="690" height="513" position="center" alt="Setting the From date/time" showCaption="false"} ::: :::WorkflowBlockItem Select the beginning of the time range, by double-clicking the desired day in the calendar. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/s76xGFLaju15tpvRsNVsy_image.png" size="80" width="948" height="490" position="center" alt="Selecting a day on the calendar" showCaption="false"} ::: :::WorkflowBlockItem Optionally edit the time in the following format - HH\:MM. ::: :::WorkflowBlockItem Click the **To** field and repeat the process. ::: :::WorkflowBlockItem Click **Apply time range**. The graphs will be updated with graphs from the selected time range. ::: :::: ## Selecting a relative time range **To select a relative time range:** ::::WorkflowBlock :::WorkflowBlockItem Click the **Time Range** field. ::: :::WorkflowBlockItem Under the **Relative time range** section, click on one of the relative time ranges from the list. The graphs will be updated with graphs from the selected time range. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/cQNc3Yr4AdsZPBeJpBekd_image.png" size="64" width="606" height="484" position="center" alt="Relative time range options" showCaption="false"} ::: :::: ## Navigating back/forth across the time range **To navigate back and forth in time:** ::::WorkflowBlock :::WorkflowBlockItem Click the **Time Range Zoom Out** button. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/IVQ4-vWQPa1e7mk07JKkA_image.png" size="46" width="351" height="219" position="flex-start" alt="Time Range Zoom Out button" showCaption="false"} ::: :::WorkflowBlockItem Click the right/left arrow to move forward/backward in time at the same time interval as the selected time range. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/D3gODMdsEMVC7oDBvmATW_image.png" size="80" width="602" height="217" position="center" alt="Adjust the time interval for the graph" showCaption="false"} ::: :::: ## Zooming in to a selected range To focus on a specific time range within the graph, select the time range using your mouse. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/nQjaM3OWoB-VlgLntitKt_image.png" size="80" width="497" height="353" position="center" alt="Selecting time range with mouse" showCaption="false"} The graph displays the selected time range and the specific time range is displayed in the time range filter. ## Zooming out To zoom out in the time range, click the **Time Range Zoom Out** button. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ikOjKW9HtIltBq7mE8_pO_image.png" size="38" width="306" height="98" position="center" alt="Zoom out button" showCaption="false"} # Changing the time zone By default, the graph uses your browser’s local time zone, however it is possible to change the timezone. The time zone is indicated in the **Browser Time** field. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/GR2HQX340FLfUGo3b8ZlQ_image.png" size="80" width="695" height="494" position="center" alt="Time zone selector" showCaption="false"} **To change the timezone:** ::::WorkflowBlock :::WorkflowBlockItem Click the **Time Range** field. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/5R6nmdKRsDBpyPq_sYBnv_image.png" size="36" width="329" height="91" position="center" alt="Time range field" showCaption="false"} ::: :::WorkflowBlockItem Click **Change Time Zone**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/OJY0w4IUKtV6aJCCheokz_image.png" size="80" width="663" height="497" position="center" alt="Change time zone button" showCaption="false"} ::: :::WorkflowBlockItem Select the relevant timezone from the drop-down list. You can search it by typing the name of the country, city, or the timezone abbreviation. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/kVJnsSL7RS6nU4Y8lnUJY_image.png" size="80" width="638" height="685" position="center" alt="Select/Search for timezone" showCaption="false"} ::: :::: # Refreshing the graph The data presented in the graphs does not refresh on its own (i.e., it displays data up to the moment the graph has been displayed). It is possible to refresh the data manually or automatically at predefined time intervals. **To manually refresh the graph:** - Click the **Refresh** button. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/f8VCnlLLbjePW4vx10IYg_image.png" size="26" width="302" height="87" position="center" alt="Refresh button" showCaption="false"} **To set an automatic refresh time interval:** ::::WorkflowBlock :::WorkflowBlockItem Click the dropdown menu next to the **Refresh** button. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/3DUu_CbPPszqGhD9_dYos_image.png" size="34" width="305" height="81" position="center" alt="Dropdown menu" showCaption="false"} ::: :::WorkflowBlockItem Select the relevant refresh time interval from the list. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/zoYt0CV1u0vGWD1iRXThY_image.png" size="38" width="308" height="321" position="center" alt="Refresh time interval selector" showCaption="false"} ::: :::: [title] Linking an Azure Account [path] ZEN Master/ZEN Master User Guide/Configuration/Configuring Microsoft Azure Account Credentials/ To Link an Azure account to ZEN Master, follow the procedure described in the **Documentation** tab. The configuration process involves the following steps: 1. **Create an Azure Subscription** – create a subscription for Microsoft Azure and copy your Subscription ID to the clipboard. 2. In ZEN Master go to** Configuration **> **Microsoft Azure**. 3. In **Documentation **tab, in the **Subscription ID** field, enter you Azure subscription ID. 4. Verify that the **New Account** radio button is selected (default). 5. **Run PowerShell script **– run the PowerShell script shown in the instructions section. Once you have entered your Subscription ID, this is automatically embedded in the script. 6. **Nvidia license **– run the PowerShell commands to access the Nvidia license and accept its terms. 7. **Create AD app and service principal** – follow the steps described in the linked article to create an AD application and service principal. This will generate the following parameters which will be used to link ZEN Master to your Azure account. - Directory/Tenant ID - Application ID - Authentication Key 8. **Link ZEN Master account **- to link your ZEN Master account to Azure: 1. Click **+ Add Account** at the top of the page. 2. Fill in the fields using the parameters that you generated in your Azure account. 3. Click **Save**. Your Azure Account is now linked to ZEN Master and can be used for managed Broadcaster clusters. 9. **Create a Virtual Network** – in order to be able to create an Azure cluster on ZEN Master, you need to first create a virtual network in your Azure account via the Azure portal. [title] Viewing Existing Zixi Receivers [path] ZEN Master/ZEN Master User Guide/Zixi Edge Devices/ After the Receiver resource is created, it is added to the list of Zixi Edge Devices. The list includes all types of Edge Devices, the type is indicated in the Type column. It is possible to filter the list by selecting **Add Filter** and **Type**. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX--FnuZDiSZAJA6GwKrteYS-20250316-132321.png) The list shows the following data: | **Parameter** | **Description** | | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Name | The name of the Receiver as configured in ZEN Master. | | Status | The connection status of the ZEC. Possible values:
* Green – OK * Red – error state * Gray – pending/disabled (waiting for initial connection) The 🔕 icon next to a ZEC indicates that the Receiver is muted, disabling notifications for error/recovery events. | | IP | The remote Zixi Receiver IP address as seen by ZEN Master. | | Type | | | RAM | The RAM utilization on the Receiver source machine. | | CPU | The CPU utilization on the Zixi Receiver source machine. | | Uptime | The time period that the Zixi Receiver has been online. | | Version | The Zixi Receiver software version. | | Link | | When a Receiver is selected, the list pane is minimized and detailed info about the selected Receiver is shown on the right side of the screen. The top of the **Info** pane includes buttons for taking the following actions on the selected Receiver: | **Parameter** | **Description** | | ----------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Selection Checkbox | Select one or more ZECs and perform batch actions on all selected ZEC. Available actions are:
* Mute All - disables notification for error/recovery events for the selected ZECs. * Unmute All – enables notification for error/recovery events for the selected ZECs. * Enable All – re-activates all active streams for the selected ZECs. * Disable All - stops all active streams for the selected Feeders without deleting the configuration of the ZECs. * Delete All – deletes the configuration for the selected ZECs. * Refresh | The info can be shown in Tabs view or Widgets, see [Info Pages](docId:6TlIS3dZX2OvWgel0k3Il). ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-yD9p6hCgY8A0WlbqFpKNj-20250316-133113.png) The **Info Pane** includes the following details: | **Parameter** | **Description** | | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | CPU  | The CPU utilization rate. | | RAM | The memory utilization rate. | | Uptime | The time period that the Broadcaster has been online. | | Type | The type of object. | | Tags | You can edit the tag/s as follows: click the **Edit** icon. Then, delete the current tag by clicking the "X" next to the tag. Add a new tag/s by selecting one or more tags from the dropdown list. | | Open | Click to access the ZEC Broadcaster UI. | | Source IP | The Source IP of the ZEC. | | Version | The software version of the Broadcaster. Click the copy icon to copy the details. | | Location | The location of the Broadcaster. By default, the location is determined automatically based on the Broadcaster's IP. However it is possible to specify another location during configuration. | | Network | The Network in which the Broadcaster is located. The Networks are discovered automatically by ZEN Master using IP-to-location method. A network is defined as an ASN from a specific country and region/state. | | Events Configuration Profile | All the related events that have been generated by the system, such as connections, errors, warnings and disconnections. To learn about the data that is displayed in the Events tab see [Events](docId\:BgoWcWCc5rMvqDKmLBTtQ) . Click **Quick Report** to generate a report of events related to this Source and download the .xls file. | :::hint{type="info"} It is possible to add more [columns](docId\:yOUqETI1_pIOYyvKAaSxp) to the list. If you want to view resources that were marked as **Priority**, add the **Priority** column and sort by it. ::: ## Receiver List The following is a brief description of the sections that are shown: When one of the ZECs in the list is selected, the details of the ZEC, divided into tabs, appear at the right side of the screen. The list display shows following data: ### Details Tab | **Parameter** | **Description** | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Type | The type of Zixi Edge Device. | | API Credentials | The username and password used to access the Receiver through the Zixi API in order to communicate between ZEN Master and the Receiver.
* Click **Show** to display the credentials. * Click **Copy Password** to copy the password. | | Open | Click the link to access the Receiver console. | | Source IP | The IP of the Receiver's input resource. Transcoded – means that the source is transcoded. | | Host ID | | | Platform | The OS platform on the Receiver. | | Location | The location of the Receiver. | | Network | The ISP/ network of the Receiver. | | Version | The software version of the Receiver. | | SSH Key | The SSH key file used to connect the Receiver to ZEN Master. Click to download the SSH key file. | | Activation Key | Click on **License Details** to show the license details of this resource. | | Events Configuration Profile | The Events Profile that is applied to this ZEC. Click the link to view the profile in the [Events Profile Rules](docId\:AgUE5_LD2Sz1HLysiWPsi) screen. | | Deletion Protection | Indicates whether the deletion protection is enabled or disabled. The deletion protection prevents deleting the ZEC. To delete it, you will need to first disable the Termination Protection. | ### Diagram Tab (open by deafult) This section shows a schematic diagram that displays theReceiver and its related objects, as well as the system objects (Sources, Channels, Targets) that relate to this Receiver and the relationships between the various elements. ### History Tab This sections shows a graphical display of the Receiver's CPU consumption over time. ### Outputs Tab Shows a list of all Outputs available in the ZEC, including information about their Status, Type, Source and Bitrate. ### Events Tab This section shows all the related events that have been generated by the system, such as connections, errors, warnings and disconnections. To learn about the data that is displayed in the Events tab see [Events](docId\:BgoWcWCc5rMvqDKmLBTtQ) . Click **Quick Report** to generate a report of events related to this Source and download the .xls file. ### Changes Tab A list if changes to the configuration throughout time. Expand each line to view the details of the change. Select **Revert **to discard this change or **Revert All** to discard all changes. ### Notes Tab This ections shows free-form text that can be added with pertinent information about this Receiver. - [Cloning a Zixi Receiver](docId\:c3qhrSAHVIIFvF8PmvyvT) [title] Types of Rules [path] ZEN Master/ZEN Master User Guide/Configuration/Configuring Events Profiles/ There are a series of settings that can be configured for each rule. Different configuration options are available for different types of rules. - For all rules you can configure the actions taken when a rule violation occurs. This includes specifying whether or not notifications will be sent out and whether or not the state of the object will change. - **Threshold Rules** - For rules that relate to thresholds, there are two types of thresholds: - **Value thresholds** - These thresholds determine the specific value that will escalate from to a "Warning" and "Error" state. - **Threshold** - The threshold fiels defines the condition for escalating to a "Warning" and "Error" state and also the condition to de-escalate from "Error" state to "Warning" state and to "OK" state. For example, a CPU Usage rule can determine that if the CPU utilization reaches of above the 50% threshold, it will escalate to a "Warning" state and if the value is above the 80% threshold, it will escalate to an "Error" state. - **Trigger warning after x minutes above threshold **- to protect against "flapping", the rule also includes de-escalation and escalation delays that require the object to spend the configured time (in minutes) in the higher/lower state to actually escalate/de-escalate the state. For example, the CPU has to be in under 80% for a period of 15 minutes in order to de-escalate from "Error" to "Warning" state. - **Clear error after** x minutes below threshold - the amount of time that the state (error/warning) is maintained before it is cleared. - ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-w745VUTSHG4Ye-cgUN9VO-20250825-140524.png) - **State-Over-Time Thresholds** - For alerts that are based on a "Boolean" state, whether it is Boolean (e.g., Source Offline) or because the exact value is not important (e.g., CC errors or not recovered packets). - **Threshold x% of a y minute window** - the threshold is defined by a time window and a percentage of time in which that window spent in the relevant state. For example, 50% out of 6 minutes is an error threshold, so if a source reports a blank picture for 3 minutes out of the 6 min window, ZM will put it into an error state. However, if the warning threshold is 5% out of 60 minutes, if a source reports a blank picture for 3 minutes out of the 60 min window, ZM will put it into a warning state. - **Trigger warning after x minutes above threshold** - To protect against "flapping", the rule also includes de-escalation and escalation delays that require the object to spend the configured time (in minutes) in the higher/lower state to actually escalate/de-escalate the state. - **Clear error after** - The rule also includes the amount of time that the state (error/warning) is maintained before it is cleared. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-q2x_NxdEp5HLi2VPie67A-20250825-144101.png) [title] Actions on a ZEC [path] ZEN Master/ZEN Master User Guide/Zixi Edge Devices/Viewing Existing ZEC/ When one of the ZECs in the list is selected, information about the ZEC is shown in the Info pane. The **Info pane** has buttons for taking the following actions for the selected ZEC. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/0P5Du9Dtv3pdt5h4a8Drs-20250914-093506.png) - **Acknowledge/Clear Acknowledgment **(for ZECs in disconnected status) – mark/clear the status of this ZEC as acknowledged. - **Mute/Unmute** – disables/activates notification for error/recovery events. - **Disable/Enable** – Disabling a ZEC stops all active streams for that ZEC without deleting the configuration of the ZEC. - **Edit** – enables you to edit the ZEC configuration. - **Refresh **– refreshes the page. When hovering over the three dots, a new menu of options appear: - **Mute until **– set the date and time when the mute will automatically be cleared by clicking on the down arrow and selecting **mute until.** - **Open **– click to access the ZEC UI. - **Clone** – create an additional ZEC based on the settings of the selected ZEC. - **Config**.– click to view instructions on how to configure the ZEC to connect to ZEN Master. - **Delete** – deletes the ZEC configuration. [title] Health Monitoring [path] ZEN Master/ZEN Master User Guide/Introduction to ZEN Master/ ZEN Master offers the ability to monitor the entire operation, while quickly drilling down to specific network segments, at the stream and device levels. Users can easily manage system health by quickly verifying that all sources are connected and streaming content, as well as view in-depth network and transport (TR101) visualization and history. Health monitoring can be viewed through the screens of the various resources (e.g. Broadcasters, ZECs, Sources, Targets) and through the following views: - **Dashboard** –provides a centralized view of the open issues across all the deployment components, their statuses, and event logs. - **Maps** – provides a geographical view of the deployment using maps. The maps display the location of your physical devices and logical entities, the direction of signal flow, and the operational status of each device and connection. - **Grids** – provides a thumbnail view of the live and a color-coded status of each source, while displaying content quality warnings such as audio clipping, frozen video, and more. - **Channel view** – provides an abstract view of the relationship between Contribution devices (Zixi Feeders or Feeder SDKs integrated into encoders), Zixi Broadcasters, and Zixi-enabled endpoints (e.g., ZECs or IRDs with integrated Zixi SDK). - **Source view** – provides history graphs showing network performance from the Source device to the Broadcaster. - **Broadcaster view **– provides history graphs showing server performance - **Target view **– provides history graphs showing network performance from the Broadcaster to the Target device. - **Preview with VLC/WebRTC **- offers the ability to monitor the stream by previewing it using a local VLC player or using webRTC for playback in the browser. - **Alerts and notifications **- instant alarms and email alerts across contribution or delivery. [title] Configuring AWS Account Credentials [path] ZEN Master/ZEN Master User Guide/Configuration/ You can link one or more AWS accounts to ZEN Master. This enables you to launch managed Broadcaster clusters on AWS (including broadcasters that use Nvidia GPU for transcoding). You can also use S3 Bucket storage as publishing targets for storing HLS and DASH manifests and segments. In addition, you can integrate AWS MediaConnect "Flows" into your ZEN Master workflow as Sources or Targets and you can also create new Flows in ZEN Master. :::hint{type="info"} **ZEN Master’s AWS IAM policy update** ZEN Master’s AWS IAM policy has been updated and is **REQUIRED**. The policy change allows ZEN Master to support changes to the AWS instance launch system that will come into effect at the beginning of 2024. Updating the IAM Policy of the AWS account will be required ahead of the Dec. 31st 2023 AWS cutoff date. ::: The **Accounts** tab in the** AWS Accounts** screen shows your existing AWS accounts that are linked to ZEN Master. For each existing configuration, icons at the end of the row enable the following actions: *Edit configuration, Delete configuration.* ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/YORVep8rOHjGVoRJ1a5aZ_image.png" size="80" width="1348" height="416" position="center" alt="AWS accounts list" showCaption="false"} The **Documentation** tab shows the procedure used for linking an AWS account to ZEN Master. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/7sjV7YC1ejSRyrOOvOagI_image.png" size="80" width="1125" height="485" position="center" alt="Instructions for linking AWS account" showCaption="false"} - [Creating an AWS IAM Role for ZEN Master](docId\:eJonw9BptBfHQf4iR7QNR) - [Linking an AWS Account](docId\:erygXkCUfmmZ8BaKidJz4) - [Editing an AWS Account](docId\:SlLbT8E2ZuN_RAFmviIzp) [title] ZEN Master [path] / ![ZEN Master](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/zzTwlhEPN6sAdqIUn5x0Q_zm.jpg) ZEN Master is the live video orchestration and telemetry control plane that enables Zixi users to manage large-scale configurations. ZEN Master provides centralized configuration, monitoring, automation, and troubleshooting for Broadcaster deployments across any network, cloud, or hybrid environment. With ZEN Master, media organizations can extend their reach, increase production speed, and dramatically reduce operational costs. - [ZEN Master User Guide](docId\:vzz5bE4XXIpP9wLuLps4N) - [SSO Setup Guides](docId\:EaNdUW7SZCOeZKPgwGteF) - [How to Videos](docId\:A9-EHZYG4xt_V27GeYpu2) *** Software Version 25.08.12 Copyright © Zixi 2025 All Rights Reserved ## Legal Notice This document contains proprietary and confidential material of Zixi LLC. Any unauthorized reproduction, use, or disclosure of this material, or any part thereof, is strictly prohibited. This document is solely for the use of Zixi employees and authorized Zixi customers. The material furnished in this document is believed to be accurate and reliable. However, no responsibility is assumed by Zixi LLC. for the use of this document or any material included herein. Zixi LLC. reserves the right to make changes to this document or any material included herein at any time and without notice. [title] Access Control [path] ZEN Master/ZEN Master User Guide/Introduction to ZEN Master/ ZEN Master features a multi-tier access control mechanism that enables granular control of the access privileges down to the object level. It manages access to all system objects, including Resources (i.e. Feeders, Broadcaster Clusters, Receivers and Licenses), Sources (i.e. input streams), Adaptive Channels and Pass-Through Channels. The access control is managed through the following entities: - **Tags **– Each object (Resource, Source, Adaptive Channel, Delivery Channel and SSH Key) is assigned one or more Tags. The assignment of the Tag/s is performed during the creation/configuration of the object. The same Tag can be assigned to multiple objects and several Tags can be assigned to the same object. - **Roles **– A role defines a set of privileges in the system. A role is associated with one particular Tag, enabling access to objects associated with that Tag. The role also designates what actions can be performed on each object type (i.e. Resources, Sources, Adaptive Channels and Pass-Through Channels). Actions include: - **View** - the ability to view data from the object. - **Edit** - the ability to edit the object’s configuration - **Notifications** - the ability to receive email notifications/alerts regarding the object. A Tag can be associated with one or multiple roles. - **Users **– A user receives privileges in the system by being assigned one or multiple roles. To learn more about access control see [Account Management](docId\:t49XhHyZCGfR2Rz2GtnRm). [title] Management Console UI Elements [path] ZEN Master/ZEN Master User Guide/ The Management Console UI provides easy access to all ZEN Master resources and system objects. You can configure ZEN Master to manage your resources (Feeders, Broadcaster and Receivers). You can also manage content throughout your network using ZEN Master’s abstraction layer of Sources, Channels and Targets. The UI also enables you to monitor system performance both on a macro as well as a granular level. This chapter gives a brief overview of the UI elements. Details about specific UI functionality are provided in the following chapters. - [Main Screens](docId\:AYwchxSDm3O2T6Et6A1Cw) - [Working with Lists](docId:2khXolkndYqeWQzV8Wpe9) - [Working with Data Forms](docId\:ev-H8NAIDcBskZoXLptTb) - [Working with Graphs](docId\:Vg27sunrozFOjPgZ1WvQY) - [Global Search](docId\:gpucGGvKr30AmC6QgFuzB) - [Change Tracking](docId\:hc-KMARjxkvIaZ69v6IVv) - [Dark Mode](docId\:cGux3Hwip0qtmTTXlOU0Q) - [Help](docId:23bZC5JVf9a28uyogSRhU) - [Customizing the Info Panel (Layout)](docId:3JrhHkACBegQy_tt-djvG) - [Using Widgets](docId\:dZGxObIfFLOncAnSfwY4d) - [Collapsing and restoring the details and resources panes](docId\:zgbklrmHmsSu6c7uJ_Q-5) [title] Working with Lists [path] ZEN Master/ZEN Master User Guide/Management Console UI Elements/ ZEN Master uses a standardized format for displaying lists of resources and other system objects on their designated screens. The following sections explain some general guidelines for viewing information and taking actions on the list screens. - [Info Pages](docId:6TlIS3dZX2OvWgel0k3Il) - [Search Filter](docId\:VOMYD859XVlwEtLQq158o) - [Sort](docId\:bcsB5HQhqmV4FaIuDqk11) - [Show/Hide Columns](docId\:yOUqETI1_pIOYyvKAaSxp) - [Batch Processes (multi-select)](docId:1e5zGEyH-YjRfNma0Fawn) - [Expand/Collapse Tables](docId\:dgHNQDzOJ7IXMG65_g8G1) - [Download Quick Report](docId\:QjtzX0P1q6xIwUGnxGS7o) [title] Creating a New Broadcaster Cluster [path] ZEN Master/ZEN Master User Guide/Broadcasters/Creating a Broadcaster Cluster/ There are two management options available for the Broadcaster clusters: - **Manual** – this option requires manual set up and configuration of each Zixi Broadcaster instance. You can then create a Manual cluster and add your specific broadcaster instances to the cluster. - **Managed** – this option enables ZEN Master to spin up new broadcaster instances in your cloud account and manage them automatically. For this option there is no need to manually set up the actual Zixi Broadcaster instances. All you need to do is create a Managed cluster and then add the desired number of primary and secondary broadcasters to the cluster. This option is only available once you have configured your Amazon AWS, Microsoft Azure or Google GCP account in ZEN Master. To configure your credentials, see [Configuring AWS Account Credentials](docId\:sKdBivurRY3pDLduJMB7I)**, **[Configuring Microsoft Azure Account Credentials](docId\:YS05F6_tIl6nSkE_XF9nE), or [Configuring Google GCP Account Credentials](docId\:F6m6HMz75NsLktENfKrSU). The following procedure describes how to add a Broadcaster cluster in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. - [Adding a Broadcaster Cluster – Manual](docId\:lUGqITvwdm0YIpL102_px) - [Adding a Broadcaster Cluster - Managed](docId:6sLx4TD__ZKr2XFhO8qZ6) - [Broadcaster Cluster Configuration Parameters Table (for Manual and Managed Clusters)](docId\:ISKTTeET_CQkw1tbMNoHL) [title] Centralized Management [path] ZEN Master/ZEN Master User Guide/Introduction to ZEN Master/ ZEN Master makes it easy to manage hundreds of live streams, while supporting any signal paths, including point-to-point, one-to-many, multi-cloud or multi-CDN using a variety of wide variety of industry protocols (e.g., Zixi, RIST, SRT, HLS, RTMP, and others). Physical resources, such as Zixi Feeders, Zixi Broadcasters, and Zixi Receivers are centrally managed along with the following logical entities: - **Broadcaster Cluster** – a logical entity comprising one or more Zixi Broadcasters for load balancing purposes. - **Sources** – a logical entity that represents a single video content stream coming from a Zixi Feeder or another contribution device. A Source may also consist of multiple physical streams with the same video content, which are combined together for failover purposes. - **Channels – **a logical entity that represents the type of processing, if any, to perform on the video content. The Channel is connected to one or more Sources in a Primary/Backup configuration and, on the other end to one or more Targets. - **Targets** – a logical entity that represents a single video stream from a Channel being distributed to a Zixi Receiver or another endpoint device. A Target can be connected to a single Channel only. Together these physical and logical entities help create new live channels and spin up required streams on the fly. [title] Configuring Google GCP Account Credentials [path] ZEN Master/ZEN Master User Guide/Configuration/ You can link a GCP account to ZEN Master. This enables you to launch managed Broadcaster clusters on GCP (including broadcasters that use Nvidia GPU for transcoding). You can also use GCP storage as publishing targets for storing HLS and DASH manifests and segments. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/6Lf7C_O7Zyh1LiBBCyqhw_image.png" size="90" width="1259" height="299" position="center" alt="GCP Account List" showCaption="false"} The **Documentation** tab shows the procedure used for linking a GCP account to ZEN Master. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/6B8XP6imIRfrCpPn7L8v4_image.png" size="70" width="1078" height="662" position="center" alt="Instructions for GCP and Zixi" showCaption="false"} - [Linking a Google GCP Account](docId\:JBuzi2tJvSpS3o_VzVXxH) - [Editing a GCP Account](docId\:YWoBWplAOR5doHq5E-O0y) [title] Using Widgets [path] ZEN Master/ZEN Master User Guide/Management Console UI Elements/ The Widgets view can display all the information that was previously available throughout the different tabs, all in one screen. The screen with the widgets is customizable, both in terms of the content that is displayed and also its appearance. ## Enabling Widgets View To enable the Widgets view, click the Widgets icon. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/oX4wA46tythZAk4ZzF7_F_image.png" size="12" width="107" height="73" position="flex-start" alt="Widgets icon" showCaption="false"} ## Hiding/showing widgets To hide/show a widget, click on the corresponding tab. The tab is highlighted when the widget is shown and not highlighted when hidden. For example, in the following image the Broadcasters widget is hidden. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/XnG5w7gA4xnypNyiPV4c5_image.png" size="62" width="562" height="193" position="center" alt="Hidden widget example" showCaption="false"} ## Moving widgets around To move a widget around, simply drag it to the desired position on the screen. ## Resizing widgets It is possible to resize the widget like a Window object by hovering the mouse on the desired edge and when it turns into an arrow, move it in the desired direction. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/EY-4rJpFSUxePBuVtrNWd_image.png" size="52" width="492" height="226" position="center" alt="Resizing widget" showCaption="false"} ## Saving and locking the layout After making all the changes, click **Save **to save the changes of the layout and click **Lock** to freeze the layout. Clicking **Revert **will revert to the previous layout or **Reset** to go back to the initial layout. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Ih--tkupXk0IpUEC0QJuM_image.png" size="38" width="329" height="123" position="center" alt="Save layout button" showCaption="false"} [title] Example: API keys with Roles and Tags [path] ZEN Master/ZEN Master User Guide/Configuration/Untitled/ ## Control User Permissions with Roles and Tags In this example, we'll create an API key that allows read-only access privileges to a specific group of Sources. ### Step 1: Create a Tag First, we'll create a Tag that can be assigned to ZEN Master objects. ::::WorkflowBlock :::WorkflowBlockItem In the left navigation, select **Configuration** > **Tags**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/bZgiqXMpFTqSXDJcDdrHk_image.png) ::: :::WorkflowBlockItem Select **+Add** to create a new Tag. ::Image[]{src="https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/yDZjd_QUCy4EXyrjp8xbc_image.png" size="50" width="370" height="104" position="center" showCaption="false"} ::: :::WorkflowBlockItem Give the Tag a name and select **Save**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/VRUWf7KOb-hsAg9xRMM9B_image.png) ::: :::: ### Step 2: Create an API key Next, we'll create an API key. :::::WorkflowBlock :::WorkflowBlockItem In the left navigation, select **Configuration** > **API Keys**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/PXW3-E2NHobqvbgamviRy_image.png) ::: :::WorkflowBlockItem Select **+Add Key** to create a new API key. ::: ::::WorkflowBlockItem In the **Create New API Key** page: - Enter a name for the API key. - Set the expiration date or leave the default. - Leave the other options unchecked/unselected. :::hint{type="info"} Since the **Read only**, **Account Administrator**, and **Administrator** options override the Roles persmissions, leave them unchecked. ::: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/gUqA9aQRbKthZ9WKdfOk1_image.png) :::: :::WorkflowBlockItem Click **Save** to create the API key. ::: ::::: ### Step 3: Create a Role With a Role, we can select user permissions for object types. ::::WorkflowBlock :::WorkflowBlockItem In the left navigation, select **Account Management** > **Roles**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/MMkjXew3wYjCjgJNoMQqe_image.png) ::: :::WorkflowBlockItem Select **+Add** to create a new Role. ::: :::WorkflowBlockItem In the **Create New Role** page: - Enter a name for the Role. - Select the Tag that we created in Step 1. - For **Permissions**, select the checkbox for Source. - Select the API key that we created in Step 2. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/mqtABnEtKNlklVyg2Ua5j_image.png) ::: :::WorkflowBlockItem Click **Save** to create the Role. ::: :::: ### Step 4: Add Tag to Sources Now, we can add our Tag to the Sources that we want to give read access to for our API key. ::::WorkflowBlock :::WorkflowBlockItem In the left navigation, select **Sources**. ::: :::WorkflowBlockItem Select the Sources that you want to grant read access for the API key, and click **Edit**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/1FIpCTnpeHHIc5QLmoLup_image.png) ::: :::WorkflowBlockItem In the **Edit Sources** page: - Select the checkbox to update Tags. - Select Add to add our new Tag without overwriting or removing any existing Tags. - From the dropdown menu, select our new Tag. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/BD92gWX546-67yBF-WqLv_image.png) ::: :::WorkflowBlockItem Click Save. The multi-edit dialog should confirm that each selected Source has been updated. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/KFLYtRqmFdZ6z29AHKsI5_image.png) ::: :::: ### Step 5: Using the API key Let's test our API key persmissions by making a request to the ZEN Master API. The new API key grants the API Caller read permission only for the Sources that share the key's assigned Tag and Role. ::::WorkflowBlock :::WorkflowBlockItem Send a GET API request to list all Sources. ```curl curl --location 'https://api.zen.zixi.com/v2/sources' \ --header 'x-api-key: ' \ --header 'Accept: application/json' ``` ::: :::WorkflowBlockItem The API response should only contain the two Sources that we tagged. ```javascript { "success": true, "result": [ { "id": 12345, "name": "api_docs_zixi_other_push", ... }, { "id": 12346, "name": "api_docs_zixi_other_push_api", ... } ] } ``` ::: :::WorkflowBlockItem Since we only have read access to two Sources, we will not be able to read other objects. Send a GET API request to list all ZECs. ```curl curl --location 'https://api.zen.zixi.com/v2/zecs' \ --header 'x-api-key: ' \ --header 'Accept: application/json' ``` ::: :::WorkflowBlockItem The API response will be **200 OK**, but the result will be empty. ```javascript { "success": true, "result": [] } ``` ::: :::WorkflowBlockItem With only read access, we will **not** be able to **create**, **update**, or **delete** any objects. Send a POST API request to create a new Source. ```curl curl --location 'https://api.zen.zixi.com/v2/sources' \ --header 'x-api-key: ' \ --header 'Content-Type: application/json' \ --header 'Accept: application/json' \ --data '{ "name": "api_docs_zixi_other_push", "broadcaster_cluster_id": 4444, "target_broadcaster_id": -1, "resource_tag_ids": [ 11 ], "autopull_latency": 1000 }' ``` ::: :::WorkflowBlockItem The API response will be an Unauthorized error. ```javascript { "success": false, "error": "Unauthorized" } ``` ::: :::: [title] Viewing Existing Events Profiles [path] ZEN Master/ZEN Master User Guide/Configuration/Configuring Events Profiles/ The Events Profiles screen displays all existing Events Profiles, and shows which Events Profile is set as the default profile. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-nVoxYbJfZ63xVFRizAWXF-20250901-130853.png) The main display includes the following data for each Events Profile: | **Parameter** | **Description** | | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Selection Checkbox | Select one or more Events Profiles and perform actions on all selected Events Profiles. Available actions are:
* **Delete Selected **– deletes the selected Events Profiles. | | Name | The name of the Events Profile. | | Default | Indicates (by a checkmark) which Events Profile is applied to objects by default. | When an Events Profile is selected, the list pane is minimized and detailed info about the selected Events Profile is shown on the right side of the screen. The following sections are shown in the Info pane: - **Details** - configuration details of the selected Events Profile. - **Rules** - the rules for the selected Events Profile with their associated settings. - [Actions on an Events Profile](docId\:ShhSyz5Jcs9xm8Z93go-1) - [Events Profile Details](docId\:yLO6-te3p4u9-fwaJbSlM) - [Events Profile Rules](docId\:AgUE5_LD2Sz1HLysiWPsi) [title] Viewing Existing Zixi Feeders [path] ZEN Master/ZEN Master User Guide/Zixi Edge Devices/ After the Feeder resource is created, it is added to the list of Zixi Edge Devices. The list includes all types of Edge Devices, the type is indicated in the Type column. It is possible to filter the list by selecting the type with the checkboxes at the top. ![Edge Device List](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/rBIM9F86OcprUiEFfCWY__image.png) When a Feeder is selected, the list pane is minimized and detailed info about the selected Feeder is shown on the right side of the screen. The info can be shown in Tab view or Accordion view, see [Info Pages](docId:6TlIS3dZX2OvWgel0k3Il). ![Feeder Details](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/l3jp5C-NYIjJ7tTcsSPyl_image.png) The following sections are shown in the info pane: - **Details** – configuration details of the Feeder. - **Status/Performance **– shows the main performance metrics for the Feeder. - **Inputs** - shows a list of available inputs on the Feeder. - **History** – a graphical display the Feeder's resource consumption over time. - **Events** - all the related events that have been generated by the system, such as connections, errors, warnings and disconnections. To learn about the data that is displayed in the Events tab see [Events](https://zixidocumentation.atlassian.net/wiki/spaces/ZMUG/pages/483688494/Events). Click **Quick Report** to generate a report of events related to this Source and download the .xls file. - **Notes **– free-form text can be added with pertinent information about this Feeder. - **Configuration **– configuration procedures for manually connecting the Feeder to ZEN Master, including specific settings for this particular Feeder. The main display shows following data: | **Parameter** | **Description** | | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Selection Checkbox** | Select one or more Feeders and perform batch actions on all selected Feeders. Available actions are:
* **Mute All** - disables notification for error/recovery events for the selected Feeders. * **Unmute All **– enables notification for error/recovery events for the selected Feeders. * **Enable All **– re-activates all active streams for the selected Feeders. * **Disable All **- stops all active streams for the selected Feeders without deleting the configuration of the Feeders. * **Delete All **– deletes the configuration for the selected Feeders. | | **Name** | The name of the Zixi Feeder as configured in ZEN Master. | | **Status** | The connection status of the Zixi Feeder. Possible values:
* Green – OK * Red – error state * Gray – pending/disabled (waiting for initial connection)
The 🔕 icon next to a Feeder indicates that the Feeder is muted, disabling notifications for error/recovery events. | | **IP** | The remote Zixi Feeder IP address as seen by ZEN Master. | | **CPU** | The CPU utilization on the Zixi Feeder source machine. | | **RAM** | The RAM utilization on the Zixi Feeder source machine. | | **Uptime** | The time period that the Zixi Feeder has been online. | | **Version** | The Zixi Feeder software version. | | **Actions** |
| | **Open** | Provides access to the Zixi Feeder UI (applicable to both cloud-based Zixi Feeders and on premise Zixi Feeders). | :::hint{type="info"} It is possible to add more [columns](docId\:yOUqETI1_pIOYyvKAaSxp) to the list. If you want to view resources that were marked as Priority, add the Priority column and sort by it. ::: When one of the Feeders in the list is selected, the details of the Feeder, divided into tabs, appear at the right side of the screen. | **Parameter** | **Description** | | -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Details Tab** |
| | **Name** | The name of the Zixi Feeder as configured in ZEN Master. | | **Type** |
| | **Tag** | The Tag/s that is associated with this Feeder.
You can edit the tag/s as follows: click the **Edit** icon. Then, delete the current tag by clicking the "X" next to the tag. Add a new tag/s by selecting one or more tags from the dropdown list. | | **Events Configuration Profile** | The Events Profile that is applied to this Feeder. | | **API User** | The username used to access the Zixi Feeder through the Zixi API in order to communicate between ZEN Master and the Zixi Feeder. | | **API Password** | The password used to access the Zixi Feeder through the Zixi API. Click **Show** to display the password. | | **SSH Key** | The name of the SSH key file. | | **Termination Protection** | Indicates whether the termination protection is enabled or disabled. The termination protection prevents deleting the Zixi Feeder. To delete it, you will need to first disable the Termination Protection. | | **Platform** | The OS platform on the Feeder. | | **Source IP** | The Source IP of the Feeder. | | **Uptime** | The time period that the Zixi Feeder has been online. | | **Host ID** | The Host ID of the Feeder. | | **Activation Key** | Click on **License Details** to show the license details of this resource. | | **Version** | The software version of the Zixi Feeder. | | **Open** | A link to the Feeder UI. | | ***Status/Performance*** | Shows the current CPU and RAM usage of the Feeder. | | ***Inputs*** | Shows a list of all Inputs available in the Feeder, including information about their Status, Type, Source and Bitrate. | | ***History*** | A graphical representation of the CPU and RAM utilization of the selected Feeder, displayed over time. | | ***Events*** | A list of the events that were generated in ZEN Master in relation to the selected Zixi Feeder. To learn about viewing event logs in ZEN Master, see [Events](https://zixidocumentation.atlassian.net/wiki/spaces/ZMUG/pages/483688494/Events). Click **Quick Report** to generate a report of events related to this feeder and download the .xls file. | | ***Configuration*** | Shows an explanation of how to connect the selected Feeder to ZEN Master. This tab includes your personal connection configuration settings which are used to make the connection. See section [Connecting the Zixi Feeder (Zixi Feeder UI)](https://zixidocumentation.atlassian.net/wiki/spaces/ZMUG/pages/388104215/Connecting+the+Zixi+Feeder+Zixi+Feeder+UI). | | ***Notes*** | Shows free-form notes relevant to the Feeder. | - [Actions on a Feeder](docId\:sMINcDxKZkn5xi8Fm7PyM) [title] Documentation [path] ZEN Master/ZEN Master User Guide/Management Console UI Elements/Help/ The Documentation section of the Help menu gives links to relevant documentation. The link to the User Guide home page is shown at all times. In addition, for each screen, links to relevant articles are shown. [title] Collapsing and restoring the details and resources panes [path] ZEN Master/ZEN Master User Guide/Management Console UI Elements/ It is possible to collapse and restore the details and resources pane. **To collapse the main menu and resources pane:** ::::WorkflowBlock :::WorkflowBlockItem Hover your mouse on the edge between the resources pane and the details pane. The following markings appear. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/w2YNQIA9Zk-EZSrvYN5YS_image.png" size="46" width="364" height="291" position="flex-start" alt="Resizing panes" showCaption="false"} ::: :::WorkflowBlockItem Do one of the following: - Click the left arrow to collapse the resources pane. This will allow the details pane to occupy more space on the screen. - Click the right arrow to collapse the details pane. This will allow the resources pane to occupy more space on the screen. ::: :::WorkflowBlockItem Click the opposite arrow to restore/expand the pane. ::: :::: ## Saving and locking the layout After making all the changes, click **Save **to save the changes of the layout and click **Lock** to freeze the layout. Clicking **Revert **will revert to the previous layout or **Reset** to go back to the initial layout. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Xqr71HjhOKmuVJQol46YX_image.png" size="44" width="329" height="123" position="center" alt="Save layout button" showCaption="false"} [title] Adding a Broadcaster Cluster - Managed [path] ZEN Master/ZEN Master User Guide/Broadcasters/Creating a Broadcaster Cluster/Creating a New Broadcaster Cluster/ When creating a ZEN Master managed Broadcaster cluster, you specify the AWS, Azure or GCP instance type that will be used for this cluster. Make sure to select an instance type that supports the type of processing that will be done on this cluster. ZEN Master supports both standard CPU instances as well as Nvidia GPU instances on AWS, Azure and GCP (including Tesla V100 and T4, which support both HEVC decoding and encoding). In addition, ZEN Master supports 5G Contribution and Distribution using the AWS Wavelength Zone. Before launching a wavelength zone instance, opt into the wavelength zone service, by enabling the feature via your AWS console. Due to instant type and public IP differences, wavelength zone and non-wavelength zone subnets are not interchangeable, and clusters can only choose one. For more information, see - [https://docs.aws.amazon.com/wavelength/latest/developerguide/what-is-wavelength.html](https://docs.aws.amazon.com/wavelength/latest/developerguide/what-is-wavelength.html) **To add a managed Broadcaster Cluster:** :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Broadcasters**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Broadcaster Cluste**r screen is displayed. ![Create Managed Cluster](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/rAduFlw6L99gyvS3Q3R0S-20251030-171905.png) ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, type a logical name for the Zixi Cluster resource. ::: :::WorkflowBlockItem In the **Tags** field, select one or more of the predefined Tags from the drop-down menu. Tags are used for access control. By selecting a Tag you are relating this Cluster to an 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 cluster. By default, the Defaultprofile 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 In the **DNS Prefix** field, enter a unique domain name for sending the streams to/from this cluster. ::: :::WorkflowBlockItem Select the **DTLS** checkbox if you would like to activate DTLS encryption and authentication. (This feature is only supported for Broadcasters running v12.2+.) ::: :::WorkflowBlockItem If you selected the **DTLS** checkbox then the **Ignore DTLS certificate when not supported** checkbox appears. Select this checkbox if you would like to enable resources using older versions of Zixi software (\**Parameter** | **Description** | | ----------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Selection Checkbox | Select one or more ZECs and perform batch actions on all selected ZEC. Available actions are:
* Mute All - disables notification for error/recovery events for the selected ZECs. * Unmute All – enables notification for error/recovery events for the selected ZECs. * Enable All – re-activates all active streams for the selected ZECs. * Disable All - stops all active streams for the selected Feeders without deleting the configuration of the ZECs. * Delete All – deletes the configuration for the selected ZECs. * Refresh | The info can be shown in Tabs view or Widgets view, see [Info Pages](docId:6TlIS3dZX2OvWgel0k3Il). ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-_IQi9KsvFYz3kLr0CCQ7m-20250316-091737.png) The **Info Pane** includes the following details: | **Parameter** | **Description** | | --------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | CPU  | The CPU utilization rate. | | RAM | The memory utilization rate. | | Uptime | The time period that the Broadcaster has been online. | | Type | The type of object. | | Tags | The Tag/s that is associated with this ZEC.
You can edit the tag/s as follows: click the **Edit** icon. Then, delete the current tag by clicking the "X" next to the tag. Add a new tag/s by selecting one or more tags from the dropdown list. | | Open | Click to access the ZEC UI. | | Public IP | The IP address of the of the ZEC instance. | | Version | The software version of the ZEC. Click the copy icon to copy the details. | | Location | The location of the ZEC. By default, the location is determined automatically based on the Broadcaster's IP. However it is possible to specify another location during configuration. | | Network | The Network in which the ZEC is located. The Networks are discovered automatically by ZEN Master using IP-to-location method. A network is defined as an ASN from a specific country and region/state. | | Events Configuration Profile | All the related events that have been generated by the system, such as connections, errors, warnings and disconnections. To learn about the data that is displayed in the Events tab see [Events](docId\:BgoWcWCc5rMvqDKmLBTtQ) . Click **Quick Report** to generate a report of events related to this Source and download the .xls file. | :::hint{type="info"} It is possible to add more [columns](docId\:yOUqETI1_pIOYyvKAaSxp) to the list. If you want to view resources that were marked as **Priority**, add the **Priority** column and sort by it. ::: ZEC List The list display shows following data: | **Parameter** | **Description** | | ------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Name** | The name of the ZEC as configured in ZEN Master. | | **Status** | The connection status of the ZEC. Possible values:
* Green – OK * Red – error state * Gray – pending/disabled (waiting for initial connection)
The 🔕 icon next to a ZEC indicates that the Feeder is muted, disabling notifications for error/recovery events. | | **IP** | The IP address of the of the ZEC instance. | | **Type** | The type of Zixi Edge Device. In this case - ZEC. | | **RAM** | The RAM utilization on the ZEC source machine. | | **CPU** | The CPU utilization on the ZEC source machine. | | **Uptime** | The time period that the ZEC has been online. | | **Version** | The ZEC software version. | | **Link** | Click **Open** to access the ZEC UI. | The following is a brief description of the sections that are shown: When one of the ZECs in the list is selected, the details of the ZEC, divided into tabs, appear at the right side of the screen. The list display shows following data: ### Details Tab | **Parameter** | **Description** | | -------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Type** | The type of Zixi Edge Device. | | **API Credentials** | The username and password used to access the ZEC through the Zixi API in order to communicate between ZEN Master and the ZEC.
* Click **Show** to display the credentials. * Click **Copy Password** to copy the password. | | **Open** | Click the link to access the ZEC console. | | **Public IP** | The IP address of the of the ZEC instance. | | **Platform** | The OS platform on the ZEC machine. | | **Location** | The location of the ZEC. | | **Network** | The ISP/ network of the ZEC. | | **Version** | The software version of the ZEC. | | **SSH Key** | The SSH key file used to connect the ZEC to ZEN Master. Click to download the SSH key file. | | **Activation Key** | Click on **License Details** to show the license details of this resource. | | **Events Configuration Profile** | The Events Profile that is applied to this ZEC. Click the link to view the profile in the [Events Profile Rules](docId\:AgUE5_LD2Sz1HLysiWPsi) screen. | | **SSH Key** | The name of the SSH key file. Click to download the key. | | **Platform** | The OS platform on the ZEC. | | **Deletion Protection** | Indicates whether the deletion protection is enabled or disabled. The deletion protection prevents deleting the ZEC. To delete it, you will need to first disable the Termination Protection. | ### Inputs Tab Shows a list of all Inputs available in the ZEC, including information about their Status, Type, Source and Bitrate. ### Outputs Tab Shows a list of all Outputs available in the ZEC, including information about their Status, Type, Source and Bitrate. ### History Tab A graphical representation of the CPU and RAM utilization of the selected ZEC, displayed over time. Click Open Incident to add a new or edit an existing incidents, see [Creating an Incident Manually](docId\:aomjabSyzYLzY3GQ4zH8o) for more details. ### Diagram Tab (open by deafult) This section shows a schematic diagram that displays the ZEC and its related objects, as well as the system objects (Sources, Channels, Targets) that relate to this ZEC and the relationships between the various elements. ### Events Tab A list of the events that were generated in ZEN Master in relation to the selected ZEC. To learn about viewing event logs in ZEN Master, see . Click **Quick Report** to generate a report of events related to this ZEC and download the .xls file. ### Changes Tab A list if changes to the configuration throughout time. Expand each line to view the details of the change. Select **Revert **to discard this change or **Revert All** to discard all changes. ### Notes Tab Shows free-form notes relevant to the ZEC. - [Actions on a ZEC](docId\:kZOKgXSWgR9jyL3q8jwPO) [title] Cloning a Zixi Feeder [path] ZEN Master/ZEN Master User Guide/Zixi Edge Devices/Adding a Zixi Feeder/ If you would like to create a new Feeder with properties similar to those of an existing Feeder, you can use the Clone feature to simplify the process. **To Clone a Zixi Feeder:** ::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Zixi Edge Devices**. ::: :::WorkflowBlockItem Select the Feeder that you would like to Clone (i.e. the Feeder already configured in ZEN Master which has setting similar to those that you would like to set for the new Feeder that you are creating). ::: :::WorkflowBlockItem Click on the **Clone** button. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/gnVoHnkvXEUX9zt6saBLF_image.png" size="60" width="838" height="331" position="flex-start" showCaption="false"} The **Feeder** window is displayed with all fields other than **Name** populated with the configuration data of the original Feeder. ::: :::WorkflowBlockItem In the **Name** field, enter the name of the new Feeder. ::: :::WorkflowBlockItem Change any of the fields that you would like to configure differently than the original Feeder. See section [Adding a New Zixi Feeder](docId\:mftOot18o5bbnbOfX-uhO). ::: :::WorkflowBlockItem Click **Save**. The Feeder is configured and will remain in Pending state until you configure the initial connection to the Zixi Feeder, see the following section [Connecting the Zixi Feeder (Zixi Feeder UI)](docId\:g1cbMtTJT9HfhCxKN20Ld). ::: :::: [title] Adding a New Zixi Receiver [path] ZEN Master/ZEN Master User Guide/Zixi Edge Devices/Adding a Zixi Receiver/ **To add a Zixi Receiver:** :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, select **Zixi Edge Devices**. ::: :::WorkflowBlockItem Click **+ Add**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/djSX-KOZsUXguRljC9dYX_image.png" size="68" width="963" height="422" position="flex-start" alt="Create New Edge Device" showCaption="false"} ::: :::WorkflowBlockItem Click **Receiver**. The **Create New Receiver** screen is displayed: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/HbGI75V8YitqebFWzjw_i_image.png" size="70" width="864" height="1484" position="flex-start" alt="Create new receiver" showCaption="false"} ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, enter a logical name for the Zixi Receiver. ::: :::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 Receiver 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 Receiver. 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 Receiver's location is used to represent it in the proper position in the Map display (see Maps). By default, the location is determined automatically based on the Receiver's IP. If you would like to manually set the location of the Receiver (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, in the **API User** field, enter the username for accessing the Zixi Receiver instance. This enables ZEN Master to use the API to monitor and manage the Zixi Receiver instance. (Default value: *admin*) ::: :::WorkflowBlockItem In the **API Password** field, enter the password for accessing the Zixi Receiver. The default password on Zixi Receivers is *1234*. Unless you have changed the password for this Receiver, enter *1234* in this field. ::: ::::WorkflowBlockItem In the **SSH Key** field, select from the drop-down list one of the existing remote access keys to be used for SSH tunneling between the Zixi Broadcaster and ZEN Master. :::hint{type="info"} If you would like to configure a new SSH Key, see [Configuring SSH Keys](docId\:qXuh0ckZbygbyCRZvjtwS). ::: :::: :::WorkflowBlockItem In the **Initial State** section, select the **Disabled** checkbox if you would like to disable this Receiver upon initial configuration. ::: :::WorkflowBlockItem Select the **Muted** checkbox if you would like to disable error/recovery notifications for this Receiver upon initial configuration. ::: :::WorkflowBlockItem Click **Save**. After configuring the Receiver in ZEN Master you must make the actual connection between the Receiver and ZEN Master using the procedure described in [Connecting the Zixi Feeder (Zixi Feeder UI)](docId\:g1cbMtTJT9HfhCxKN20Ld) . ::: ::::: [title] Configuration [path] ZEN Master/ZEN Master User Guide/ The **Configurations** menu includes the following elements: - **Tags** – Tags are used to control access to various system objects. - **Event Profiles** - manage Events Profiles, which determine rules for Event logging and Event notifications. - **Notifications **– configure the settings for sending out email notifications for alerts generated by the system. - **API Keys** – API keys are used to access Zixi functions via API. - **SSH Security & Keys** – SSH Keys are used in ZEN Master to authorize an SSH tunnel when connecting a Zixi component to ZEN Master. - **Amazon AWS **– configure your AWS account credentials to enable managed Broadcaster clusters and HLS/DASH storage. - **Microsoft Azure** - configure your Microsoft Azure account credentials to enable managed Broadcaster clusters and HLS/DASH storage. - **Google GCP **– configure your GCP account credentials to enable managed Broadcaster cluster and HLS/DASH storage. - [Configuring Tags](docId\:vPSZIytS_uzxdb-zvrAcX) - [Configuring Events Profiles](docId\:CWshWpVMDch_ryL86IMTS) - [Configuring Notifications](docId\:pU-7pgb7mA00zrZ1MGVdn) - [Configuring API Keys](docId\:y5VWL7q34grAoPRjlHzuI) - [Configuring SSH Keys](docId\:qXuh0ckZbygbyCRZvjtwS) - [Configuring AWS Account Credentials](docId\:sKdBivurRY3pDLduJMB7I) - [Configuring Microsoft Azure Account Credentials](docId\:YS05F6_tIl6nSkE_XF9nE) - [Configuring Google GCP Account Credentials](docId\:F6m6HMz75NsLktENfKrSU) - [title] Configuring Events Profiles [path] ZEN Master/ZEN Master User Guide/Configuration/ *EventsProfiles* are used to customize the way that *Events* are handled in ZEN Master. :::hint{type="info"} ZEN Master logs Events that occur in your system. This includes both warning and error Events (e.g. offline, low bitrate, TR101 error) as well as OK Events, when objects return to an OK state. All Events are shown on the **Logs > Events** screen. In addition, Events can trigger the affected objects changing state in ZEN Master (warning, error, ok) as well as email notifications being sent to relevant stakeholders. ::: :::hint{type="info"} This feature replaces the "Notifications" configuration for errors and warnings that was used previously in ZEN Master. ::: *Events Profiles* enable you to create a series of customized rules that determine precisely how Events are logged and what results they trigger. Each rule governs a specific type of event (e.g. offline, low bitrate, TR101 error). For each rule you specify the following details: - **Enabled/Disabled** - Specify whether or not this rule is enabled for generating Events. - **Thresholds** - For rules that are governed by thresholds (e.g. CPU usage, low bitrate), specify the thresholds for generating warning and error Events. - **Escalation** – Specify the number of events that cause escalation from “warning” to “error” Events and the window of time that is considered for escalation. - **Actions **– Specify what actions are triggered by this rule. Specify whether or not these Events cause the state of the object to change in ZEN Master, and whether or not email notifications will be sent to relevant stakeholders. :::hint{type="info"} The Events Profile does not determine which recipients will receive the notifications. When notifications are activated for a rule and that rule generates an Event for a particular object, notifications will be sent to all users who have roles associated with that object (via Tags) that include receiving notifications. ::: ZEN Master comes with a “Default” Events Profile that defines the default rules for Events. By default, that profile is applied to all objects in the system. You can create new custom profiles in which you adjust the settings for each individual rule that you would like to change from the default behavior. Events Profiles are applied on an object-by-object basis, enabling you to apply different sets of rules to different objects. The rules are grouped into the following categories, which represent different objects in the system: - **Adaptive Channel** - set of rules for events related to adaptive channels. - **Broadcaster** - set of rules for events related to Broadcasters that are managed by ZEN Master. - **MediaConnect Flow - **set of rules for events related to MediaConnect Flows. - **Publishing Target** - set of rules for events related to HLS Targets. - **Remote access** - set of rules for events related to Remote Access. - **Source** - set of rules for events related to all Source types. - **Target** - set of rules for events related to all Target types. - **ZEC **- set of rules for events related to ZEC that are managed by ZEN Master. - **Pull **- set of rules for events related to pull objects. - [Events Profiles Configuration Workflow](docId\:L6AalogbA04v70DlPK-oZ) - [Use Case Examples](docId:3f_hKlXVuXI25PxllUnNQ) - [Types of Rules](docId\:jZQSKQI-G-uxZoJaFDe8f) - [Adding a New Events Profile](docId:4rOwY-AvfVCI37-shEUjY) - [Editing Events Profile Rules](docId\:WJHCXAbqATmvsezByH8z7) - [Viewing Existing Events Profiles](docId\:w_Bwv1az6r_iiQZnMCkx4) [title] Configuring SSH Keys [path] ZEN Master/ZEN Master User Guide/Configuration/ SSH Keys are used in ZEN Master to enable ZEN Master to access the web UI of a connected Zixi resource (e.g. Broadcaster, ZEC or other Zixi enabled device). When you configure resources in ZEN Master you will assign an SSH key to each resource. You can use a single SSH key for several resources or use a separate key for each resource. Each SSH key is associated with one or more Tags which control which users have access to that key. There are two methods for generating SSH keys: - Generate the key in ZEN Master and then download the private part of the key and load it into the external device. (simplest method) OR - Generate the key on the external device and then *Import* the public part of the key into ZEN Master. (most secure method) :::hint{type="info"} * If you are importing a public key, it must be a "strong" key in order for it to be accepted in ZEN Master. * If an SSH Key was imported from an external device (not generated in ZEN Master) then you will need to use the manual method to connect the device to ZEN Master and not the automatic method (i.e. v12 method). ::: The **SSH Security & Keys** screen **(Configuration > SSH Security & Keys)** shows a list of the SSH keys available in your system as well as the tag/s associated with each key. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/rpcSHQIccc9IwtWcbHDHY_image.png" size="90" width="1618" height="800" position="center" alt="SSH Key list" darkWidth="1618" darkHeight="800" showCaption="false"} You can perform the following action for each SSH key. - **Edit** – Edit the name and/or Tag for that key. - **Download** – Download the private part of the key onto your local machine (for keys generated in ZEN Master). - **Delete** – Delete the key. The **Tunnels/IO Server** tab shows the Hostname used for SSH tunnels and includes a link to download the Public Key used to sign the SSH server's unique ID. **To generate a new SSH key:** ::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Configuration > SSH Security & Keys**. The **SSH Security & Key**s screen is displayed. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New SSH Key** screen appears. ![Create New SSH Key](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/pCKS1__-5DF0oE-79OBhz_image.png) ::: :::WorkflowBlockItem In the **Name** field, type a name for the new key using any alphanumeric characters. ::: :::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 SSH Key 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 **SSH Public Key** field, enter the public key that was generated on the external device. ::: :::WorkflowBlockItem Click **Save**. The new SSH key is added to the list of SSH keys. ::: :::: [title] Search Filter [path] ZEN Master/ZEN Master User Guide/Management Console UI Elements/Working with Lists/ The Search Filter feature shows results that match the search text for any data element on that screen (as opposed to the global site Search at the top of the navigation pane which searches the entire site). This includes the data shown in each column as well as the **Tags** associated with the element. So, for example, if you enter the search text *“Demo”* on the **Sources** screen, results are shown for Sources that have *“Demo”* as part of the Source Name, Ingest Cluster, Input etc. You can use Boolean operators "AND", "OR", and "NOT" and grouping characters "()\[]" to create complex search filters. :::hint{type="info"} The operators **must** be capitalized. When the words "and", "or", and "not" are not capitalized, they are treated as regular search text. Also, the operators must be preceded and followed by a space in order to be recognized as operators. ::: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/JqZkLbD83RkKezrqNgHF0-20260129-131515.jpg) ## Preset Filters The are preset filters to make filtering easier. You can also save your own filters for either personal or global use ("global" here means across this ZEN Master instance - they are not propagated to other ZEN Master instances). ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/F22kmDMNC95pnq3Ox0eWH_table-search.png) ## Column-specific filter options In addition to the search filter, it is possible to use additive column-specific filter options that are specific to the column types of the correspond table. This allows you to set more fine-grained filter parameters such as searching for text in specific columns, filtering with relational operators on numerical columns, or filtering for specifying time ranges etc. **To create a column-specific filter:** ::::WorkflowBlock :::WorkflowBlockItem Click **Add Filter**. A list of columns is displayed. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/-7cmEE8tVWUXDKlOHLz98-20260129-131701.jpg) ::: :::WorkflowBlockItem Select the relevant column to apply the filter. The filter configuration is displayed. ::: :::WorkflowBlockItem Select the relevant operator and enter the value. The filter is added. ::: :::WorkflowBlockItem Repeat the steps to configure additional filters. Filters are additive, so a sources search with a filter for uptime > 2 days, and a second for uptime \< 3 days, will yield a result of all sources with uptimes between 2 and 3 days. ::: :::: [title] Info Pages [path] ZEN Master/ZEN Master User Guide/Management Console UI Elements/Working with Lists/ When you navigate to a list screen the list of instances is shown in full view. In this view, a column is shown for each relevant parameter and a checkbox is shown next to each instance, enabling you to perform batch processes, see [Batch Processes (multi-select)](docId:1e5zGEyH-YjRfNma0Fawn). ![Sources List](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/TyAuULs0E7AP2peV_Fhgj_image.png) You can adjust the pagination by specifying the number of **Rows** displayed per page. The default setting is *Auto, *which displays the optimal number of rows for your screen. When you select an object instance the list becomes narrow, showing only the element name. Detailed info about the selected instance is shown in the Info pane to the right of the list. The Info pane can be shown either in ***tab view*** or in ***accordion view*** (with collapsible sections). You can return to the full list view by clicking on the "**x**" at the top of the info pane. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/5DD8IUCadU_OmsMcyqqgz_image.png" size="90" width="1396" height="530" position="center" alt="Source Settings" showCaption="false"} In tab view, selectable in the top right-hand corner, information is organized by tabs. The information in each tab is displayed responsively to adjust for browser width. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/3VJfbgFJY88W-WjPEguDj_image.png" size="90" width="1160" height="845" position="center" alt="Tab View" showCaption="false"} **Accordion View** In accordion view, selectable in the top right-hand corner, there are two columns of information panels, if browser width allows. The UI is responsive and the two columns will become a single column on narrow browser windows or mobile devices. Each information panel can be minimized and maximized with the ^ and ⌄ buttons on the top left of the panel. The min/max state of panels remains persistent while viewing other objects of the same type, Sources for instance. It will reset once you view other object types. ![Accordion View](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ICzeHDod7o6olmtOXBYdu_image.png) [title] Disaster Recovery (Alternative Path) [path] ZEN Master/ZEN Master User Guide/Introduction to ZEN Master/ ZEN Master features a disaster recovery feature that enables reverting an entire path after the Source (i.e., Channel/Broadcaster to the Target) to go through an alternative path, which is usually hosted on an alternative cloud/region. The redirection to the alternative path is manual. So, in case of a fault, if there is no time to troubleshoot a problem, this mechanism allows the user to select the feed that has an issue, click a button and revert the stream to go through a pre-configured alternative path.  For example, if you have a Channel and a Broadcaster on GCP and a secondary Channel and Broadcaster on Azure. If something goes wrong with the GCP path, you can click the **Go to Alternative** button and failover everything to Azure.  ## Setting an Alternative Channel/Broadcaster Cluster You can configure as an alternative entity, the Channel or the Broadcaster Cluster, but it is not recommended to do both at the same time. This is done by selecting the alternative entity in the **Alternative Cluster (Disaster Recovery)** field (for Broadcaster Clusters) or the **Alternative Channel (Disaster Recovery)** field for (Channels). ## Switching to the Alternative Path The switch to the alternative path can be done from the Channel details screen or from the Target details screen, as explained in the following instructions: - [Attaching a Channel to an Alternative Path](docId\:lVsDrpAXquoKEyy_mCY8y) - [Attaching a Target to an Alternative Path](docId\:Cf1NmnbVZxuSnsMEaEmkr) [title] Events Profile Details [path] ZEN Master/ZEN Master User Guide/Configuration/Configuring Events Profiles/Viewing Existing Events Profiles/ The Details section shows the following information: | **Parameter** | **Description** | | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Default | - **Yes** - indicates that this Events Profile is used to define the default rules for newly created Events Profiles. - **No** - indicates that this Events Profile is not used to define the default rules for newly created Events Profiles. | | Name | The name of the Events Profile. | [title] Editing an AWS Account [path] ZEN Master/ZEN Master User Guide/Configuration/Configuring AWS Account Credentials/ You can edit the configuration of an AWS account to update the Role ARN. :::hint{type="info"} You can't change the account that ZEN Master is linked to, you can only update the Role ARN to apply a different role for the original account. ::: **To edit an AWS Account**: ::::WorkflowBlock :::WorkflowBlockItem In AWS generate a new Role ARN with the desired permissions. ::: :::WorkflowBlockItem In ZEN Master, on the **Configuration > Amazon AWS** screen, click on the **Edit** icon for the desired account. The **Edit AWS Account** window opens. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/022dRLA58DegsOKQU7_6u_image.png" size="66" width="832" height="388" position="flex-start" showCaption="false"} ::: :::WorkflowBlockItem Edit the **Name** and/or **Role ARN** as desired. ::: :::WorkflowBlockItem Click **Save**. The new settings are applied. ::: :::: [title] Linking an AWS Account [path] ZEN Master/ZEN Master User Guide/Configuration/Configuring AWS Account Credentials/ ZEN Master uses its own AWS Role ARN credentials to access AWS and manage Broadcaster clusters. As part of this configuration, you will grant access to ZEN in order to manage your resources in your AWS account. To configure an AWS account in ZEN Master, follow the procedure described in the **Documentation** tab. The configuration process involves the following steps: - **Generate a Role ARN** - on AWS you will need to generate a Role ARN for ZEN. Under **Configuration **>** Amazon AWS**, in the **Documentation** tab, you will find instructions on how to configure the **AWS role for ZEN**. The instructions contain information that is unique to your account. Keep this browser open while you configure your Amazon AWS account so that you can use the dynamically generated credentials as you configure these settings. - **Enter the Role ARN in ZEN** – the ARN code that was generated should be entered into your Amazon AWS account configuration in ZEN Master (by clicking **+ Add Account**). [title] Adding a New Zixi Feeder [path] ZEN Master/ZEN Master User Guide/Zixi Edge Devices/Adding a Zixi Feeder/ The following procedure describes how to add a Zixi Feeder in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. **To add a Zixi Feeder:** :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Zixi Edge Devices**. ::: :::WorkflowBlockItem Click **+ Add**. ::: :::WorkflowBlockItem Click **Feeder**. The **Create New Feeder** screen is displayed: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/MpwC_mOBK7TIfrlZUcffd_image.png" size="90" width="1092" height="1483" position="center" alt="Create New Feeder Screen" showCaption="false"} ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, type a logical name for the Zixi Feeder. ::: :::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 Feeder 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 Feeder. By default, the *Default* profile is selected. :::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 Feeder's location is used to represent it in the proper position in the Map display (see [Maps](https://zixidocumentation.atlassian.net/wiki/spaces/ZMUG/pages/1546125324/Maps)). By default, the location is determined automatically based on the Feeder's IP. If you would like to manually set the location of the Feeder (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, in the **API User** field, enter the username for accessing the Zixi Feeder instance. This enables ZEN Master to use the API to monitor and manage the Zixi Feeder instance. (Default value: *admin*) ::: ::::WorkflowBlockItem In the **API Password** field, enter the password for accessing the Zixi Feeder. The default password on Zixi Feeders is *1234*. Unless you have changed the password for this Feeder, enter **1234** in this field. :::hint{type="info"} For security reasons, we recommend that you change the admin password on the Feeder. ::: :::: ::::WorkflowBlockItem In the **SSH Key** field, select from the drop-down list one of the existing remote access keys to be used for SSH tunneling between the Zixi Feeder and ZEN Master. :::hint{type="info"} If you would like to configure a new SSH Key, see [Configuring SSH Keys](docId\:qXuh0ckZbygbyCRZvjtwS). ::: :::: :::WorkflowBlockItem Select the **Termination protection** checkbox if you would like to prevent deletion of the Zixi Feeder. ::: :::WorkflowBlockItem In the **Initial State** section, select the **Disabled** checkbox if you would like to disable this Feeder upon initial configuration. ::: ::::WorkflowBlockItem Select the **Muted** checkbox if you would like to disable error/recovery notifications for this Feeder upon initial configuration. :::hint{type="info"} You can Enable/Unmute the Feeder at any time. ::: :::: :::WorkflowBlockItem Click **Save**. The Feeder is configured and will remain in Pending state until you configure the initial connection to the Zixi Feeder, see [Connecting the Zixi Feeder (Zixi Feeder UI)](docId\:g1cbMtTJT9HfhCxKN20Ld) . ::: ::::: ## Zixi Feeder Configuration Parameters Table | **Parameter** | **Description** | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | ***Info*** |
| | Name | Specify the name of the Zixi Feeder in ZEN Master. | | Tags | Select one or more of the predefined Access Tags from the drop-down list.
Tags are used for access control. By selecting a Tag, you are relating this Feeder 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](https://zixidocumentation.atlassian.net/wiki/spaces/ZMUG/pages/828014604/Creating+a+Tag). | | Events Configuration Profile | Select from the dropdown list the profile that you would like to apply to this Feeder. By default, the *Default* profile is selected.
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 Feeder's location is used to represent it in the proper position in the Map display (see ). By default, the location is determined automatically based on the Feeder'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*** |
| | API User | Enter the username for accessing the Zixi Feeder instance. This enables ZEN Master to use the API to monitor and manage the Zixi Feeder instance. The default username on Zixi Feeders is admin. Unless you have changed the username for this Feeder, verify that "admin" is entered in this field (default). | | API Password | Enter the password for accessing the Zixi Feeder. The default password on Zixi Feeders is 1234. Unless you have changed the password for this Feeder, enter 1234 in this field. | | SSH Key | Select from the drop-down list one of the existing remote access keys to be used for SSH tunneling between the Zixi Feeder and ZEN Master. If you would like to configure a new SSH Key, see . | | Termination protection | Select this checkbox if you want to prevent deletion of the Zixi Feeder. To delete it you will have to first disable the termination protection. | | ***Initial State*** |
| | Disabled | Select this checkbox if you would like to disable this Feeder upon initial configuration. | | Muted | Select this checkbox if you would like to disable error/recovery notifications for this Feeder upon initial configuration. | [title] ZEN Master User Guide [path] ZEN Master/ ![ZEN Master User Guide](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-AgA1FUcgzz3re13LK8msz-20250531-183743.png) ZEN Master makes it easy to manage inputs and outputs for hundreds of live video and Zixi streams at scale. With just a few clicks, and with automatic configuration details for network resources and distribution targets, this video management software allows users to create new live channels and spin up required streams on the fly. Zixi simplifies management of broadcast streams across industry protocols whether signal paths are point-to-point, one-to-many, multicloud or multi-CDN. Software Version 25.05.01 Copyright © Zixi 2026 All Rights Reserved ## Legal Notice This document contains proprietary and confidential material of Zixi LLC. Any unauthorized reproduction, use, or disclosure of this material, or any part thereof, is strictly prohibited. This document is solely for the use of Zixi employees and authorized Zixi customers. The material furnished in this document is believed to be accurate and reliable. However, no responsibility is assumed by Zixi LLC. for the use of this document or any material included herein. Zixi LLC. reserves the right to make changes to this document or any material included herein at any time and without notice. [title] PID Mapping Options in ZEN Master [path] ZEN Master/ZEN Master User Guide/Introduction to ZEN Master/ The Zixi Platform offers two primary map options: 1. **Designated PID Map Input**: Visible on the broadcaster as a PID Map input. 2. **Source-Level PID Map**: Embedded in the source and hidden within the broadcaster input. ZEN Master orchestration provides multiple methods to handle PID mapping, each utilizing these options differently: - **PID Map Source**: Creates a visible PID Map input parallel to the original Broadcaster input. Functions like a standard ZEN Master source and can be added to Sources/Channels for use. - **Broadcaster Push**: Generates a PID Map on the receive side, embedded within the Broadcaster input and not visible. Bandwidth at the receive side reflects the full payload for billing and processing. *\[Not appropriate for customers trying to save intercluster bandwidth with PID Map.]* - **Intercluster Pull**: PID Map is created on the receive side. The PID Mapy is built into Broadcaster input and not visible. Bandwidth at receive side will still show full for billing/processing purposes even though PID Map is happening. *\[Not appropriate for customers trying to save intercluster bandwidth with PID Map.]* - **Failover Source**: Produces a visible Broadcaster PID Map input parallel to the failover source on the Broadcaster. This input is automatically used by ZEN Master for all Targets connected to that source through a Passthrough Channel. - **ZEN Master Targets**: Will create a visible broadcaster PID Map input parallel to the requested Source when a Target is actively requested or delivered. The same PID Map will be automatically used by any future target created with that PID Mapping Profile applied delivering that Source. - **ZEN Master Sources with PID Map Support**: PID Map is built into broadcaster input and not visible. Input bandwidth will reflect total payload of source entering broadcaster and not PID Mapped bitrate. [title] How To Videos [path] ZEN Master/ The videos below will walk you through some of the essential tasks in ZEN Master. :::Iframe{iframeHeight="500" code=""} ::: [title] Cloning a ZEC [path] ZEN Master/ZEN Master User Guide/Zixi Edge Devices/Adding a ZEC/ If you would like to create a new ZEC with properties similar to those of an existing ZEC, you can use the Clone feature to simplify the process. **To Clone a ZEC:** 1. In the main navigation, click **Zixi Edge Device**. 2. Select the ZEC that you would like to Clone (i.e. the ZEC already configured in ZEN Master which has setting similar to those that you would like to set for the new ZEC that you are creating). The ZEC full details are displayed. 3. Click **Clone** button, located at the top. The **Clone ZEC** window is displayed with all fields other than Name populated with the configuration data of the original ZEC. 4. In the **Name** field, enter the name of the new ZEC. 5. Change any of the fields that you would like to configure differently than the original Feeder. See section [Adding a New ZEC](docId\:wmL-jeWi-y7QpberrnAa4). 6. Click **Save**. The ZEC is configured and will remain in Pending state until you configure the initial connection to the ZEC, see the following section [Connecting the ZEC (ZEC UI)](docId\:DfXSrrQpRXKAzXK2aJQ7f). [title] Zixi Edge Devices [path] ZEN Master/ZEN Master User Guide/ ZEN Master manages three types of Zixi Edge Devices: - **ZEC - **Zixi Edge Compute (ZEC) software that can be used as a contribution endpoint (like a Zixi Feeder) or as a receiver endpoint (like Zixi Receiver). - **Zixi Feeders** – Zixi Feeder resides at the point of acquisition and is either embedded inside Zixi EcoZystem partner encoder HW or SW, inside a camera (no back pack or field pack required) or can be installed on a pc that will be operated with any non-Zixi enabled encoder or camera. Zixi Feeder accepts and prepares the encoded video for transmission over standard internet connections using Zixi's UDP based transport stream protocol. Although Zixi Feeders are installed on premise, they can be added to the ZEN Master and managed through the ZEN Master’s management console. ZEN Master can manage multiple Zixi Feeder’s located in multiple points of acquisition. - **Zixi Receiver** - Zixi Receiver is a lightweight software tool that runs on standard PC hardware or can be embedded into a wide variety of professional decoders and mobile devices as part of the growing Zixi EcoZystem. Zixi Receiver accepts input from Zixi Feeder or Broadcaster via standard IP networks (including the public Internet) and outputs professional-quality video to a broad range of Integrated Receiver-Decoders (IRDs), and to file systems. :::hint{type="info"} The preferred edge device is now **ZEC** ::: As part of the management and configuration process, ZECs, Zixi Feeders, Broadcasters Clusters and Receivers are added to the system as described below. - [Adding a ZEC](docId\:kyJ2x8oYy-ahvhHVbOL37) - [Connecting the ZEC (ZEC UI)](docId\:DfXSrrQpRXKAzXK2aJQ7f) - [Viewing Existing ZEC](docId\:XbgDSwopbimlP9hvvWbcH) - [Adding a Zixi Feeder](docId:0SxfruZ8ET1qrqADL_PVH) - [Connecting the Zixi Feeder (Zixi Feeder UI)](docId\:g1cbMtTJT9HfhCxKN20Ld) - [Viewing Existing Zixi Feeders](docId\:uNyV9JnPZoSS1u2xfBL2B) - [Adding a Zixi Receiver](docId\:FLncsNrhtgTwT8PfT3gQx) - [Viewing Existing Zixi Receivers](docId\:V5rdeOHULD7ukhyAD3Hxm) - [Editing the Tags and Configuration Profiles of Multiple Zixi Edge Devices](docId:0D-vrusn7RmE25JCz72RZ) [title] Creating a Tag [path] ZEN Master/ZEN Master User Guide/Configuration/Configuring Tags/ **To create an Access Tag:** ::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Configuration > Tags**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Tag **window is displayed. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/KXWvISIBX0tbZbbLl6e0u_image.png) ::: :::WorkflowBlockItem In the **Name** field, enter a name that will enable you to identify the type of permissions that will be associated with this Tag, e.g. *EastCoast, CustomerA, QA*. ::: :::WorkflowBlockItem Select the **Priority** checkbox if you want to mark the object as a "Priority" object, so that it can be quickly found in the list of objects. This is helpful if you want to find easily find these objects by sorting and filtering the list. ::: :::WorkflowBlockItem Click **Save**. The Tag is created and it is shown on the list of Tags on the Tags screen. The Tag can now be assigned to roles and system objects. ::: :::: [title] Broadcasters [path] ZEN Master/ZEN Master User Guide/ - **Zixi Broadcasters **- The Zixi Broadcaster serves as a central hub for management, processing, and distribution of content in various formats. The Zixi Broadcaster platform enables live linear and live event broadcast-quality video delivery over standard broadband Internet. Zixi Broadcaster can also transcode and deliver RTMP or HLS in various bit rates and protocols. - **Broadcaster Clusters** are groups of Zixi Broadcasters that perform a certain task or tasks. A cluster can be configured to scale automatically or manually, enabling you to maximize the use of your resources. - [Creating a Broadcaster Cluster](docId\:H7vXp5B_aD2N0Qrtl7xQl) - [Viewing Existing Clusters](docId\:GutCxxQU1v-mBMsXtL7Rd) [title] Use Case Examples [path] ZEN Master/ZEN Master User Guide/Configuration/Configuring Events Profiles/ - If you are interested in tracking TR101 P2 errors for Sources of a specific client but not for others, you can create two different Events Profiles, one with TR101 P2 tracking enabled and the other with it disabled. You can then apply the appropriate Events Profile to each of your Sources. - If you want to set different GPU thresholds for broadcasters hosted on different types of machines, you can create different Events Profiles with different thresholds for broadcaster GPU usage. - If you don’t want to send any notifications for errors on a specific group of resources, you can create an Events Profile in which Notifications are disabled for all rules and apply that profile to the desired resources. [title] Editing the Tags and Configuration Profiles of Multiple Zixi Edge Devices [path] ZEN Master/ZEN Master User Guide/Zixi Edge Devices/ You can edit the Tags and Configuration Profiles of multiple Zixi Edge Devices at once. For more information, see [Configuring Tags](docId\:vPSZIytS_uzxdb-zvrAcX) and [Configuring Events Profiles](docId\:CWshWpVMDch_ryL86IMTS). **To edit the tags and configuration profiles:** ::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Zixi Edge Device**. ::: :::WorkflowBlockItem Click the checkboxes to select multiple objects. ::: :::WorkflowBlockItem Click **Edit**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/VvS8M6rcXAi-0q8oRnYVw_image.png" size="90" width="1592" height="713" position="flex-start" alt="Edit multiple edge devices" showCaption="false"} The **Edit Zixi Edge Devices** screen is displayed. ::: :::WorkflowBlockItem To edit the tags, under the **Tags** section, click **Update**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/pvGW5tbo6BWqL3v24aEbU_image.png" size="50" width="1086" height="665" position="flex-start" alt="Update Tags" showCaption="false"} ::: :::WorkflowBlockItem Select the action that you want to perform – **Overwrite**, **Add**, or **Remove**. ::: :::WorkflowBlockItem Click the drop-down menu and select the tag. It is possible to select multiple tags. ::: :::WorkflowBlockItem To edit the Events Configuration Profile of the objects, under **Events Configuration Profile**, click **Update**. ::: :::WorkflowBlockItem Click the drop-down menu and select the desired Events Configuration Profile. ::: :::WorkflowBlockItem Click **Save**. ::: :::: [title] ZEN Master Authorization [path] ZEN Master/ZEN Master User Guide/Introduction to ZEN Master/ ZEN Master features an automatic authorization mode in which it automatically verifies the authorization for each ZEN entity (e.g. sources, channels and targets) that accesses a Broadcaster cluster. You can activate this mode by simply selecting the ZEN authorization mode while configuring your Broadcaster clusters. This feature is optional, which means that streams can be authorized using other methods, however this method provides optimal security for your system without requiring configuration of specific authorization credentials for each individual stream. [title] Adding a ZEC [path] ZEN Master/ZEN Master User Guide/Zixi Edge Devices/ The ZEC is accessed by ZEN Master through an API. As part of the configuration process, you are required to specify the API credentials for access and select one of the preconfigured remote access keys to enable SSH tunneling between ZEC and ZEN Master. Access management and user permissions are managed through Tags. You can create a new ZEC with similar configuration to an existing ZEC by using the Clone feature. After adding a ZEC to ZEN Master, you will need to connect the ZEC using the procedure described in CONNECTING THE ZEC (ZEC UI). The following procedure describes how to add a ZEC in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. - [Adding a New ZEC](docId\:wmL-jeWi-y7QpberrnAa4) - [Cloning a ZEC](docId\:tZWPF7g-YBTjO-8PqoqYI) [title] Actions on a Feeder [path] ZEN Master/ZEN Master User Guide/Zixi Edge Devices/Viewing Existing Zixi Feeders/ Click on one of the Feeders to display information about the Feeder in the Info pane on the right side of the screen. The **Info** pane contains buttons for taking the following actions on the selected Feeder: - **Acknowledge/Clear Acknowledgment **(for Feeders in disconnected status) – mark/clear the status of this Feeder as acknowledged. - **Report **– - **Mute/Unmute** – disables/activates notification for error/recovery events. Set the date and time when the mute will automatically be cleared by clicking on the down arrow and selecting **mute until.** - **Edit** – enables you to edit the Feeder configuration. - **Clone** – create an additional Feeder based on the settings of the selected Feeder. - **Disable/Enable** – Disabling a Feeder stops all active streams for that Feeder without deleting the configuration of the Feeder. - **Delete** – deletes the Feeder configuration. - **Accordions/Tabs **– view. [title] Deep Data Analytics [path] ZEN Master/ZEN Master User Guide/Introduction to ZEN Master/ ZEN Master offers in-depth data analytics for monitoring issues. In addition to the basic monitoring parameters, such as Jitter, RTT, total packet loss, and total unrecovered packets, ZEN Master offers the following in-depth data analytics with a historical view of up to a year: - **Content Quality Analysis (CQA) - **Detects frozen video, blank pictures, silent audio and audio clipping. - **TR101 Analysis** - Detects TR 101 priority 1 and priority 2 issues within the stream. - **Perceptual Quality Analysis** - Provides perceptual quality analysis of the video content with **estimated PSNR (ePSNR) **and **estimated** **VMAF**. [title] Events Profiles Configuration Workflow [path] ZEN Master/ZEN Master User Guide/Configuration/Configuring Events Profiles/ 1. Create custom profiles for each of your specific needs. 2. Edit the settings for each object in your system to apply the desired Events Profile. 3. If necessary, adjust the role configurations and Tags as needed, to ensure that notifications are sent only to the relevant stakeholders. [title] Adding a Zixi Feeder [path] ZEN Master/ZEN Master User Guide/Zixi Edge Devices/ The Zixi Feeders are accessed by ZEN Master through an API. As part of the configuration process, you are required to specify the API credentials for access and select one of the preconfigured remote access keys to enable SSH tunneling between the Zixi Feeder and ZEN Master. Access management and user permissions are managed through Tags. You can create a new Feeder with similar configuration to an existing Feeder by using the *Clone* feature. After adding a Zixi Feeder to ZEN Master, you will need to connect the Feeder using the procedure described in [Connecting the Zixi Feeder (Zixi Feeder UI)](docId\:g1cbMtTJT9HfhCxKN20Ld) . - [Adding a New Zixi Feeder](docId\:mftOot18o5bbnbOfX-uhO) - [Cloning a Zixi Feeder](docId\:IPCN3ehbAvWupZu3dlnzS) [title] Adding a Zixi Receiver [path] ZEN Master/ZEN Master User Guide/Zixi Edge Devices/ The Zixi Receivers are accessed by ZEN Master through an API. As part of the configuration process, you need to specify the API credentials for access and select one of the preconfigured remote access keys to enable SSH tunneling between the Zixi Receiver and ZEN Master. Access management and user permissions are managed through Tags. After adding a Zixi Receiver to ZEN Master, you will need to follow the procedure described in [Connecting the Zixi Receiver (Zixi Receiver UI)](docId\:BesxROFc46eFKXhgWKFQ7) . - [Adding a New Zixi Receiver](docId\:V7hlpmDXf2UcaTLlehpws) - [Connecting the Zixi Receiver (Zixi Receiver UI)](docId\:BesxROFc46eFKXhgWKFQ7) [title] Expand/Collapse Tables [path] ZEN Master/ZEN Master User Guide/Management Console UI Elements/Working with Lists/ Tables are optimized for viewing on standard 16:9 screens. When viewing on a mobile device or other narrow screen, not all data on the log tables is visible. You can click on the **Expand Table **button to eliminate the fixed width limitations and enable access to all data using a horizontal scroll bar at the bottom of the screen. You can revert back to standard viewing mode by clicking on the **Collapse Table **button. [title] Configuring Notifications [path] ZEN Master/ZEN Master User Guide/Configuration/ Zen Master automatically sends email notifications about errors that occur in the system to all relevant parties. The settings for which error Events trigger notifications are determined by the Event Profiles under **Configuration > Events**, see [Configuring Events Profiles](https://zixidocumentation.atlassian.net/wiki/spaces/ZMUG/pages/2207350792/Configuring+Events+Profiles). The **Configuration > Notifications **screens enable you to configure the "Flapping Detection" thresholds and to configure a Kafka server to receive logs for ZEN Master Events. - [Configuring Flapping Detection](docId\:WvIXdwrF-FWsRX1Z0mLR0) - [Configuring Kafka Servers](docId:6Txdo_VGCzHiPdiL912-g) [title] Editing a GCP Account [path] ZEN Master/ZEN Master User Guide/Configuration/Configuring Google GCP Account Credentials/ You can edit the configuration of a GCP account to update the Role ARN. :::hint{type="info"} You can't change the account that ZEN Master is linked to, you can only update the permissions that apply to the original account. ::: **To edit a GCP Account**: ::::WorkflowBlock :::WorkflowBlockItem In GCP, adjust the permissions for ZEN Master and generate a new *Service Account Key File*. ::: :::WorkflowBlockItem In ZEN Master, on the **Configuration > Google GCP** screen, click on the **Edit** icon for the desired account. The Edit GCP Account window opens. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/hMnySdtrgr3zxuGuSdnUC_image.png" size="62" width="851" height="346" position="flex-start" showCaption="false"} ::: :::WorkflowBlockItem You can edit the **Name** if you would like. ::: :::WorkflowBlockItem Click Choose File and navigate to the new *Service Account Key File*. ::: :::WorkflowBlockItem Click **Save**. The new settings are applied. ::: :::: [title] Support Tickets [path] ZEN Master/ZEN Master User Guide/Management Console UI Elements/Help/ You can submit a Zendesk support ticket directly from the ZEN Master Help menu. **To submit a support ticket**: ::::WorkflowBlock :::WorkflowBlockItem Click on **Help** in the header bar and then click on **Report an Issue**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/T4pz9iuHIoQvXRi-CVzw9_image.png" size="70" width="600" height="336" position="center" alt="Report an Issue Option" showCaption="false"} ::: :::WorkflowBlockItem Sign in the Zendesk using account credentials or an SSO. ::: :::WorkflowBlockItem Fill in the support ticket fields as needed, and then click **Submit**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/2jJkbcaRuEUpUWnUAnD2X_image.png" size="70" width="856" height="1428" position="center" showCaption="false"} ::: :::: [title] Acquisition and Delivery [path] ZEN Master/ZEN Master User Guide/Introduction to ZEN Master/ Live-stream workflows are easily created using a set of tools for configuring and orchestrating the delivery across an entire video content creation and distribution network. ZEN Master manages inputs from 3rd party source devices and Zixi-embedded encoding systems and delivers to destinations such as the following: - Deliver HLS and MPEG DASH to AWS S3 and HTTP File Storage targets - Deliver RTMP to CDNs and DMVPDs/OVDs - Deliver MPEG TS to Zixi Receivers and IRDs - Deliver to multiple CDN targets [title] Editing an Azure Account [path] ZEN Master/ZEN Master User Guide/Configuration/Configuring Microsoft Azure Account Credentials/ You can edit the configuration of an Azure account to update the permissions. :::hint{type="info"} You can't change the account that ZEN Master is linked to, you can only update the permissions that are configured in that account. ::: **To edit an Azure Account**: ::::WorkflowBlock :::WorkflowBlockItem In Azure, adjust the permissions for ZEN Master and generate a new *Application ID* and *Authentication Key*. ::: :::WorkflowBlockItem In ZEN Master, on the **Configuration > Microsoft Azure** screen, click on the **Edit** icon for the desired account. The **Edit Azure Account** window is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/UPeN3AjM37XpO6Ii4ZkCu_image.png" size="66" width="843" height="635" position="flex-start" alt="Edit Azure Account" showCaption="false"} ::: :::WorkflowBlockItem Edit the **Name, Application ID** and **Authentication Key** fields as desired. ::: :::WorkflowBlockItem Click **Save**. The new settings are applied. ::: :::: [title] Creating a Broadcaster Cluster [path] ZEN Master/ZEN Master User Guide/Broadcasters/ Broadcaster clusters are groups of Zixi Broadcasters that perform one or more tasks. This allows efficient management of resources and ensures performance and availability of resources. Each Broadcaster cluster can be used to perform multiple tasks of various types. - [Creating a New Broadcaster Cluster](docId\:NJaOz_85Pcy2-QxgUYjSO) - [Adding Broadcasters to a Cluster](docId\:iIvjIF17ieMQlgBjoBxxZ) - [Adding IPs to the Whitelist](docId\:RicoDzjUvWVliz6i2QTgX) - [Creating a New Redirection Rule](docId\:nqC0LM3YLayDgVzssJPJx) [title] Connecting the Zixi Receiver (Zixi Receiver UI) [path] ZEN Master/ZEN Master User Guide/Zixi Edge Devices/Adding a Zixi Receiver/ For each Zixi Receiver component that has been configured in ZEN Master, you will need to configure the connection of the Zixi Receiver (using its Zixi Receiver UI) to ZEN Master. This will enable the actual connection, using the configured SSH keys. This can either be done manually by entering the configuration settings into the Zixi Receiver UI, or automatically using the ZEN tab in the Zixi Receiver UI (for v12 Receivers). :::hint{type="info"} If you are using an SSH Key that was imported from the Receiver (not generated in ZEN Master) then you will need to use the manual method to connect the Receiver to ZEN Master and not the automatic method. ::: **To connect the Zixi Receiver Manually (for v11 and below):** :::::WorkflowBlock :::WorkflowBlockItem In the ZEN Master UI, in the main navigation, click **Receivers**. The Receivers screen opens. ::: :::WorkflowBlockItem Select the Receiver that you would like to connect. ::: :::WorkflowBlockItem In the **Details** tab at the right side of the screen, click on the download link for the SSH Key. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/PrIwEpSyXoK1oPYlHzX0C_image.png" size="66" width="520" height="288" position="center" alt="Download SSH Key" showCaption="false"} ::: ::::WorkflowBlockItem In the **Configuration** section you will find your personal connection configuration settings for use with Receivers *Version 1.11 and older*. You will be using these settings to connect the Zixi Receiver (host, username, and remote source port), so you should write them down or keep this browser tab open while you configure the Zixi Receiver. :::hint{type="info"} In **tab** view, you need to select the **Configuration** tab. In **accordion** view, scroll down to the Configuration section. ::: :::: :::WorkflowBlockItem Login to the **Zixi Receiver UI** (it could be a locally installed Zixi Receiver, e.g. [http://localhost:4200](http://localhost:4200/) or a remote Zixi Receiver). ::: :::WorkflowBlockItem Go to **Settings > SSH Tunnels**. ::: :::WorkflowBlockItem In the **Key File** field, click Upload Key and select the downloaded SSH key file. ::: :::WorkflowBlockItem In the **Host** field, enter the host name that appeared in the **Configuration Help**. ::: :::WorkflowBlockItem In the **Username** field, enter the username name that appeared in the **Configuration Help.** ::: :::WorkflowBlockItem Click **Apply**. ::: :::WorkflowBlockItem In the **Reverse Tunnels** section (at the bottom) click **Add**. The **Tunnel Details** dialog opens: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/q9tY2bG2BHSFQ3IglKKoF_image.png" size="50" width="565" height="305" position="flex-start" alt="Tunnel Details" showCaption="false"} ::: :::WorkflowBlockItem In the **Remote Source Port** field, enter the Remote Source Port that appeared in the **Configuration Help**. ::: :::WorkflowBlockItem Click **OK**. ::: :::WorkflowBlockItem In ZEN Master, in the main navigation, click **Receivers**. Verify that the status of the newly connected Zixi Receiver has changed from *Pending to OK*. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/PO9EO7Felx0OUl3EikXJo_image.png" size="76" width="551" height="173" position="flex-start" alt="Receiver OK" showCaption="false"} ::: ::::: **To connect the Zixi Receiver Automatically (for v12 and above):** ::::WorkflowBlock :::WorkflowBlockItem Login to the **Zixi Receiver UI** (it could be a locally installed Zixi Receiver, e.g. [http://localhost:4200](http://localhost:4200/) or a remote Zixi Receiver). ::: :::WorkflowBlockItem Click the **ZEN** tab. The **ZEN login** screen is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/N1Ow4z6SE28E18oPdzJvi_image.png" size="80" width="560" height="301" position="flex-start" alt="ZEN Master login screen" showCaption="false"} ::: :::WorkflowBlockItem In the **Account ID** field, enter the customer domain of your ZEN Master account (e.g. if you login to ZEN at [demo.zen.zixi.com](http://zen.zixi.com/) then your Account ID is '*demo*'). ::: :::WorkflowBlockItem In the **Email** field, enter the username for your ZEN Master account. ::: :::WorkflowBlockItem In the **Password** field, enter the password for your ZEN Master account. ::: :::WorkflowBlockItem Click **Login**. A list of Receivers configured in ZEN Master is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/3CTg9WMyp_Ru26icdZXe6_image.png" size="82" width="1075" height="392" position="flex-start" alt="List of Receivers" showCaption="false"} ::: :::WorkflowBlockItem For the Receiver that you are adding, which should currently be in **Pending** mode, click **Select**. Details about the Feeder are shown in the Status section. ::: :::WorkflowBlockItem Click **Refresh**. The connection is configured automatically. ::: :::WorkflowBlockItem Verify that the Status is shown as **On:** ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/xbDIqFMzFvMZKK_GHun1V_image.png" size="70" width="540" height="87" position="center" alt="Status On" showCaption="false"} ::: :::WorkflowBlockItem In ZEN Master, in the main navigation, click **Receivers** and check that the status of the newly connected Zixi Receiver has changed from *Pending* to *OK*. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/EBiddIihGjtLkA4EE_5QW_image.png" size="80" width="551" height="173" position="center" alt="Receiver OK" showCaption="false"} ::: :::: [title] AWS and Zixi [path] ZEN Master/ZEN Master User Guide/Introduction to ZEN Master/ ZEN Master integrates with Amazon Web Services (AWS) to enable cloud-based contribution, processing, and distribution of live video workflows. Through this integration, ZEN Master provides centralized orchestration, monitoring, and control of AWS Media Services alongside Zixi-managed streams. AWS services are commonly used as part of hybrid or fully cloud-based workflows, where ZEN Master acts as the operational control layer while AWS provides scalable media infrastructure. AWS offers the following video streaming services that are integrated with Zixi: - **AWS MediaConnect** - MediaConnect is an AWS service that enables customers to reliably contribute and distribute live streams to/from the cloud using a wide variety of protocols. Zixi ZEN Master integrates with MediaConnect Flows to provide customers a powerful tool build, operate, and visualize contribution and distribution Flows at a global scale. - **AWS Elemental MediaLive** – MediaLive is a cloud-based live video encoding service from Amazon Web Services used to process and transcode live video streams. Zixi ZEN Master integrates with AWS Elemental MediaLive to enable reliable ingestion, orchestration, and monitoring of live channels, supporting scalable cloud-based distribution encoding workflows. - **AWS Elemental Link** – a hardware-based contribution encoder that delivers live video from remote locations directly into AWS. AWS Elemental Link uses Zixi technology to provide secure, low-latency, and resilient transport, allowing customers to reliably contribute live feeds into AWS-based workflows. ## AWS MediaConnect Integration Workflow AWS MediaConnect is a native cloud service designed for the transport of live video. It provides features such as encryption, entitlements for stream sharing, and integration with other AWS Media Services. MediaConnect supports protocols including Zixi, SRT, RTP, and RTMP, offering flexibility for different broadcast and streaming use cases. Because AWS MediaConnect has integrated the Zixi Protocol, customers can easily onboard streams originating or being delivered to Zixi-enabled encoders, decoders, and other software solutions. Here’s how the integration typically works: 1. **Source Ingestion:** The live video source is encoded using a device or software supporting the Zixi protocol. Customers can then direct their streams to an AWS MediaConnect Flow. 2. **Secure Transport:** MediaConnect receives the Zixi stream and securely transports it within AWS infrastructure or to external destinations. If the customer requires it, they can apply encryption, entitlements, or change protocols. 3. **Distribution:** Customers configure their MediaConnect Flows to distribute the stream to multiple endpoints, such as broadcast facilities, cloud-based video processing services, or other Zixi-enabled receivers. MediaConnect enables scalable, one-to-many distribution. 4. **Monitoring and Management:** Both Zixi ZEN Master and AWS MediaConnect provide monitoring tools to track stream health, latency, and error rates. Users can manage flows, entitlements, and destinations through the AWS Management Console or APIs. ### Benefits of Using ZEN Master with AWS MediaConnect - **Reliability**: Zixi’s error correction and adaptive transport ensure high-quality video even over unpredictable networks. - **Scalability**: MediaConnect makes it easy to scale distribution to global endpoints. - **Security**: Encryption and entitlements in MediaConnect protect content and control access. - **Flexibility**: Support for many protocols enables simple integration with a wide range of broadcast workflows. - **Operational Efficiency**: Cloud-based workflows reduce the need for on-premises hardware and simplify management. ZEN Master supports on-premises, cloud, and hybrid workflows to simplify management and control for customers in any deployment scenario. ## Disaster Recovery ZEN Master stores all source and target information, enabling confidence of business continuity through infrastructure updates. Customers who require high availability must be able to quickly restore their streams in the event of an underlying infrastructure issue. By building with ZEN Master, customers are ensuring faster recovery times when issues occur. For example, if an underlying cloud instance were to have an error or require an internal update, ZEN Master would be able to gracefully handle the transition to a new instance as quickly as possible. ## Related Documents - [Adding AWS Media Sources](docId\:v9xGBuOfembDGDPQSS_uG) - [Adding MediaConnect Flow Channels](docId\:VGHKldpL2Bb4KpPWwQZLq) - [Adding a AWS MediaLive Channel](docId:1RM8mcDM_28pYF0cG82dY) - [Adding Zixi AWS MediaConnect Targets](docId\:E6rfLr5hPPecWd0nSWUOT) [title] Configuring API Keys [path] ZEN Master/ZEN Master User Guide/Configuration/ Using an API key and endpoint requests, you can integrate ZEN Master's streaming features into your applications. ZEN Master Administrators can create API keys that control access to specific objects using ZEN Master Tags and Roles. :::hint{type="info"} Starting with the 18 Nov 2025 release, all ZEN Master API keys will have an expiration date: - Existing API keys will expire on 18 Nov 2026. - All new API keys will be set by default to expire one year after the creation date. You can set the expiration to an earlier date when needed. ::: On the API Keys screen, you will see the following: - A list of existing API keys - A **Documentation** link where you can download the latest ZEN Master OpenAPI file - Admin users will see an **Add Key** button to create new API keys ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/-FGCgVMM3d5umCcW0Jf_n-20251119-172319.jpg) The API Keys screen shows a list of API Keys available in the system. - Click **Show** next to a key to show the string of characters for that key. - Click **Copy** next to a key to copy the string of characters for that key. - Click **Delete **next to a key to delete that key. ## To generate a new API key: :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Configuration > API Keys**. The **API Keys** screen is displayed. ::: :::WorkflowBlockItem Click + **Add Key**. The **Create New API Key** screen appears: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/OMSp-F7hpBdCoUXoIBDiy-20251119-172801.jpg) ::: :::WorkflowBlockItem In the **Name** field, enter a name for the new key using any alphanumeric characters. ::: :::WorkflowBlockItem If you wish to set the expiration date to less than one year, change the **Expiration Date**. ::: ::::WorkflowBlockItem Check **Read only **to limit the use of the API key to GET methods. :::hint{type="warning"} Check **Read only** to limit users to GET (only) all objects. Do NOT check **Read only** if you want to control user permissions by Role and Tag. ::: :::: ::::WorkflowBlockItem Check **Account Administrator **to allow API key users to read and write all objects, including account management objects (Users, User Groups, Roles). :::hint{type="warning"} Do NOT check **Account Administrator** if you want to control user permissions by Role and Tag. Account Administrator permissions override Role permissions. ::: :::: ::::WorkflowBlockItem Check **Administrator** to allow API key users to read and write all objects, except for account management objects (Users, User Groups, Roles). :::hint{type="warning"} Do NOT check **Administrator** if you want to control user permissions by Role and Tag. Administrator permissions override Role permissions. ::: :::: :::WorkflowBlockItem Select a **Role** - the role will work the same way as roles in the ZEN Master UI, giving the user to GET and/or create/edit Sources, Channels, Targets, etc. See [Adding Roles](docId:268Rk_Tt-vJbIwFUYl71S). ::: :::WorkflowBlockItem Click **Save**. The new API key is added to the list of API keys. ::: :::WorkflowBlockItem You can view the new API Key by clicking **Show** next to the relevant key. ::: ::::: ## Control User Permissions by Role and Tag Learn how to configure Roles and Tags to control user permissions for an API key. For details, see [Example: API keys with Roles and Tags](docId\:cYC8w6aCVnPbbl7z-lmTN). ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/wQdEAd9sMuX8e1pv4C4-o-20251119-173118.jpeg) ## Notes for using Roles with API keys Setting a **Role** for the API key gives you granular control over which API requests the user will be able to make successfully. If the Role allows **viewing** a particular type of object (like **Sources**), the user will be able to make **GET** requests for that type of object. If the Role allows **editing** a particular type of object, then the user will be able to make **POST**, **PUT**, **PATCH**, and **DELETE** requests on objects of that type. When the Role does **not** allow viewing objects of a certain type, **GET** requests on that type of object will return a `success: true` message, but with no results: ```json { "success": true, "result": [] } ``` When the Role does **not** allow editing objects of a certain type, requests that attempt to create, update, or delete an object of that type will return a `success: false` message: ```json { "success": false, "error": "Unauthorized: POST /api/v2/tags" } ``` ## Additional Notes Here are some additional notes to keep in mind: - Live Events are only available to Administrator-level users. So, permissions on Roles will not give access to Live Events - Settings for Account Administrator, Administrator, and Read only take precedence over Roles permissions. - Roles are cumulative. So, permissions apply for all Roles associated with an object. ## Known Issues There are a few known issues around Roles: - Live Events are only available to Administrator-level users. Even though you can select Role permissions for Live Events in the ZEN Master UI, they will be ignored. - When a Role permission is set to read for an object, you will not be able to create, update, or delete the object. - For create and delete, you will receive a Forbidden response. - For update, you will get a 200 response, but no fields will be updated. [title] Actions on an Events Profile [path] ZEN Master/ZEN Master User Guide/Configuration/Configuring Events Profiles/Viewing Existing Events Profiles/ When one of the Events Profiles in the list is selected, information about the Events Profile is shown in the Info pane. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-m0eCxeA_xbnuy7Y_tYK9r-20250901-131123.png) The **Info** pane has buttons for taking the following actions for the selected Events Profile. - **Edit** - Edit the Events Profile Configuration (change the name of the profile). - **Clone** - Create an additional Events Profile based on the settings of the selected Events Profile. - **Delete** - Delete the Events Profile configuration. [title] Editing Events Profile Rules [path] ZEN Master/ZEN Master User Guide/Configuration/Configuring Events Profiles/ It is possible to create new Event Profiles to be applied on the various objects and/or edit existing event profiles. The options available to edit within a rule depend on the individual rule. Rules are grouped first by resource type (e.g. Adaptive Channel, Broadcaster, Source, etc.), then by error group (e.g. Usage, Configuration, etc.), and then by the error name (Low Bitrate, Low Audio Level, etc.). Rules that have already been modified are shown in the **Modified** list in alphabetical order, and rules in the **Default** list have default settings. ## To add/edit an Events Profile Rule: :::::WorkflowBlock :::WorkflowBlockItem Go to **Configuration > Events Profiles** and select the Events Profile for which you would like to edit the rules, or [Add a new Events Profile](docId:4rOwY-AvfVCI37-shEUjY). If you are editing an existing rule, details of the selected Events Profile are shown at the right side pane. ::: :::WorkflowBlockItem If you are editing the rules of an existing profile, click **Edit. ** ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-4t4zGPzyHmOQrRvlrB0V2-20250826-122023.png) ::: ::::WorkflowBlockItem Scroll through the list and click on the desired rule. :::hint{type="info"} Alternatively, you can use the search box at the top of the page to search for the desired rule. ::: ![events profile ule](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/KtdCpX1Pq0Xmiol-tErTi-20260617-200323.png) The Rule tab expands, showing the settings for that rule. (The options available to edit within a rule depend on the individual rule, see table below.) :::: :::WorkflowBlockItem Edit the settings as desired. When you modify the settings, the rule is marked as "Not Saved" (indicated at the end of the rule's title). ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-v_Fz8RTLaad-alBChZrX_-20250826-124503.png) ::: :::WorkflowBlockItem To save the changes, do the following: 1. Click **Save** at the top of the rule's tab. The modified rule is indicated by **\***. 2. Click **Save** at the top or bottom of the **Edit Rules** screen. The modified rules are indicated by the** YES **value under the **Modified **column. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-mZqxMWKOwLHiTbVm8f1wy-20250826-130135.png) ::: ::::: ### To restore an Events Profile Rule to its default settings: :::::WorkflowBlock :::WorkflowBlockItem Go to **Configuration > Events Profiles** and select the Events Profile for which you would like to edit the rules. Details of the selected Events Profile are shown on the right pane. ::: :::WorkflowBlockItem In the **Rules** tab, click **Edit**. The rules for your chosen Events Profile are shown. Rules that have been modified are indicated by a \*. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-6Pi3NANz0d_mayJy00WJV-20250826-133218.png) ::: :::WorkflowBlockItem Scroll through the list and click on the desired rule. The Rule tab expands, showing the settings for the r ::: ::::WorkflowBlockItem Click the **Reset** button at the top of the rule's tab. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-QjViSw94N7EiNSC0sUv2L-20250826-134101.png) The rule is reset to its default settings. :::hint{type="info"} When you click on the "Reset" button, the rule's settings are instantly reverted to their default settings and saved. You cannot undo this action. ::: :::: ::::: ## Parameters Table The table below lists all of the potential parameters from all of the rules. There is also the option to reset rules to their default settings. | **Parameter** | **Description** | | ----------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Track only, do not update object state | Select this option if you want the escalation event to be registered in the event log only. In this case, the issue triggering the rule and any resulting escalation, will not escalate the object itself to a warning or error state. | | Disable | Select this option to disable the rule entirely, so that no Events will be logged for this rule. (If checked, the other rule options are no longer shown.) | | Generate OK email notification | Select this checkbox if you would like email notifications to be sent to relevant stakeholders when the object returns to an **OK** state. | | Generate Error email notification | Select this checkbox if you would like notifications to be sent to relevant stakeholders when the object enters an **error** state. | | Ignore object state for notification generation | Select this checkbox if you would like notifications to be sent to relevant stakeholders for all error events regardless of whether the object was already in an error state. (When not selected, notifications are only sent when an object first enters into an error state.) | | Threshold | **For Value Thresholds:**
The threshold fiels defines the condition for escalating to a "Warning" and "Error" state and also the condition to de-escalate from "Error" state to "Warning" state and to "OK" state. For example, a CPU Usage rule can determine that if the CPU utilization reaches of above the 50% threshold, it will escalate to a "Warning" state and if the value is above the 80% threshold, it will escalate to an "Error" state.
**Note: **for** Video and Audio Bitrate, **you can enter any number (in KBPS) between **0** and **999999** - the number you want to enter depends on the average bitrate of the stream, and how far below that average you want to flag with a warning or error.
**For** **State-Over-Time Thresholds**
The threshold is defined by a time window and a percentage of time in which that window spent in the relevant state. For example, 50% out of 6 minutes is an error threshold, so if a source reports a blank picture for 3 minutes out of the 6 min window, ZM will put it into an error state. However, if the warning threshold is 5% out of 60 minutes, if a source reports a blank picture for 3 minutes out of the 60 min window, ZM will put it into a warning state. . | | Escalation/De-escalation Timing | To protect against "flapping", the rule also includes de-escalation and escalation delays that require the object to spend the configured time (in minutes) in the higher/lower state to actually escalate/de-escalate the state.
* **Warning De-escalation Delay** - specify the time in minutes in which the object should spend to de-escalate from "Warning "to "OK" state. * **Warning Escalation Delay** - specify the time in minutes in which the object should spend to de-escalate from "Warning "to "Error" state. * **Error De-escalation Delay** - specify the time in minutes in which the object should spend to de-escalate from "Error "to "Warning" state. * **Error Escalation Delay** - specify the time in minutes in which the object should spend to de-escalate from "Warning" to "Error" state. | | Clear error after | Specify the time in minutes that the state (error/warning) is maintained before it is cleared. | [title] Events Profile Rules [path] ZEN Master/ZEN Master User Guide/Configuration/Configuring Events Profiles/Viewing Existing Events Profiles/ ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-GggpPdnCm8JzQ8veLyjzU-20250903-130928.png) The Rules section shows options for all of the rules for the selected Events Profile. The following information is shown: | **Parameter** | **Description** | | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Type | The type of rule, which defines the component that it relates to. Types include:
* Broadcaster * Adaptive Channel * MediaConnect Flow * Publishing Target * Pull * Remote Access * Source * Target * ZEC | | Group | Rules are grouped into the following groups:
* Usage * Adaptive group * Offline * Rendition error * API * Configuration * License * Status * Usage * Validation * Failover * Connection * Analysis * Transcoding | | Rule | The name of the rule | | Modified | - **Yes **- indicated that the rule has been modified from its default settings. - **No **- indicates that the rile was not modified. | | Disabled | * **Yes** – indicates that the rule is disabled, so that no Events will be logged for this rule. * **No or \{blank} **– indicates that the rule is enabled. | ## Filtering the Rules The list of rules can be filtered in one of the following manners: - Type the string or part of the string into the **Filter **field. The filter applies to all the columns. - Click **+ Add Filter** and select the column to filter by. - For boolean values select/deselect the relevant values. - For string values type the string and select one of the following: - Contains - Equals - Begins With [title] Global Visibility and Health [path] ZEN Master/ZEN Master User Guide/Introduction to ZEN Master/ ZEN Master's control plane collects and analyzes telemetry data across the entire stream workflow — from contribution through processing to delivery — giving operators the visibility they need to quickly identify and resolve issues. Analysis results surface in the Incidents and Insights modules, where users can visualize stream health at a glance. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/DQWrSICRhvFnBxrtAK9yx_zm-diagram.png" size="70" isUploading="false" position="center" width="1360" height="2216" darkWidth="1360" darkHeight="2216" alt="Flow Diagram" showCaption="false"} Visual diagrams of sources, channels, and targets make it easy to spot problems, and users can drill down into real-time data on streams, devices, and networks for deeper diagnosis. Searchable event logs and customizable alerts keep operators informed and help them resolve issues fast. ## Graphs ZEN Master provides a set of graphs in ZEN Master that enable you to identify and diagnose areas of instability in your system. Brief descriptions are below; follow the links for more detailed explanations. ### [Broadcaster History](docId\:D75iFW_FOZXfd-Pptvxdw) ![Broadcaster History](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Hj1-x9OmQPh9sfjgzYEkL_zm-bx-history.png) The [Broadcaster History](docId\:D75iFW_FOZXfd-Pptvxdw) graphs provide a visual history of various aspects of the Broadcaster and the server or VM that it runs on. These are useful for diagnosing problems that might be related to issues with Broadcaster itself or the underlying system. ### [Source History](docId:7zapE3l6cY_1Z0vz9mxC-) ![Source Graph Sample](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/LDD7zORy0U2dgm2NrmEiQ-20260317-001318.png) [Source History](docId:7zapE3l6cY_1Z0vz9mxC-) graphs depend on the kind of source, whether you have enabled stream analysis, and so forth. In all cases there will be a Network graph showing the bitrate history. ### [Target History](docId\:gfII56tGhkA_wmNr7n6y7) ![Target History Graph Sample](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/YpGjCt6G-MS8iknenhpgD-20260317-150243.png) As with sources, ZEN Master provides [Target History](docId\:gfII56tGhkA_wmNr7n6y7) graphs. All targets will show a Network graph that shows recovered and unrecovered missing packets, reconnections, and send errors. For some target types, there is an additional Bitrate history graph. ### [Events](docId\:BgoWcWCc5rMvqDKmLBTtQ) and [Incidents](docId\:KM0I5TNPzuO-ygFv6QcVq) Events and Incidents tables in the details for sources, channels, and targets provide a list of changes that occurred to help you identify and fix problems. ### Events (what *happened*, on a specific object) In **ZEN Master**, an **Event** is a **single, atomic occurrence** generated when an individual object changes state or violates a rule. Examples include a source going offline, bitrate dropping below threshold, audio clipping, or CPU utilization crossing a limit. Key characteristics: - Events are generated **per object** (Source, Target, Broadcaster, Media Connect flow, etc.). - They are triggered by **event rules** defined in an **Event Profile**. - Events represent **state transitions** (OK → Warning/Error, or back to OK). - Events are logged immediately and appear in the **Events view**. - Some events may trigger **notifications** (for example, email alerts). ### Incidents (what *broke*, across multiple objects) An **Incident** is a **higher‑level construct** that **groups related events** together in order to surface a likely **common root cause**. According to the ZEN Master User Guide: - Incidents group together **related errors** to simplify troubleshooting. - They can be **automatically generated** by the system or **manually created** by an operator. - Automatic incidents are created when **multiple objects** (Sources, Targets, or Broadcasters) experience error events **around the same time** and **share a common resource**. - The system uses correlation logic (time window, shared resource, and proportion of affected objects) to decide when to create an incident. - An incident has a **date range**, **impact summary**, and a **root cause notice** (for auto‑generated incidents). [title] Connecting the ZEC (ZEC UI) [path] ZEN Master/ZEN Master User Guide/Zixi Edge Devices/ For each ZEC component that has been configured in ZEN Master, you will need to configure the connection of the ZEC (using its ZEC UI) to ZEN Master. This will use the configured SSH keys to enable the actual connection. For the initial setup of the ZEC in ZEN Master - see [Adding a New ZEC](docId\:wmL-jeWi-y7QpberrnAa4). **To connect the ZEC Manually:** ::::WorkflowBlock :::WorkflowBlockItem In the ZEN Master UI, in the main navigation, click **Zixi Edge Devices**. ::: :::WorkflowBlockItem Select the **ZEC** that you would like to connect. ::: :::WorkflowBlockItem In the **Details** tab at the bottom of the screen, click on the download link for the **SSH Key**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/xyXPqXOAt_17GKvMiPDKV_image.png" size="60" width="687" height="623" position="center" alt="Download SSH Key" showCaption="false"} ::: :::WorkflowBlockItem On the ZEC Details screen, click on the three dots in the upper right corner to reveal the dropdown menu, and choose Config to open the Configuration section. In the Configuration section, you will find your personal connection configuration settings for use with ZEC. You will use these settings to connect the ZEC (host, username, and remote source port), so you should write them down or keep this browser tab open while you configure the ZEC. ![Open ZEC Configuration](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/91YaUQZcTR-wCoBbzll4k_image.png) ::: :::WorkflowBlockItem Login to the ZEC UI (it could be a locally installed ZEC, e.g. [http://localhost:4444](http://localhost:4444/) or a remote ZEC). ::: :::WorkflowBlockItem Go to **Settings > SSH Connections**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/TGtHL43a4PYXezmg261yj_image.png" size="90" width="1018" height="658" position="center" alt="ZEC SSH Connections" showCaption="false"} ::: :::WorkflowBlockItem Click **Add** connections. ::: :::WorkflowBlockItem In the **Host** field, enter the host name that appeared in ZEN Master's Configuration section. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/brPK3SO6VDxLCSNFpy2RG_image.png" size="70" width="670" height="266" position="center" alt="Host Name" showCaption="false"} ::: :::WorkflowBlockItem Click Apply. The new connection is added to the list of **SSH connections** in ZEC. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/y3Ha47PwdbsWor1K1HrgI_image.png" size="90" width="811" height="505" position="center" alt="SSH Connections List" showCaption="false"} ::: :::WorkflowBlockItem Click **+** to expand. ::: :::WorkflowBlockItem Click **Edit Credentials**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/5gRCshbR6rkx4uECpYLXO_image.png" size="90" width="1076" height="187" position="center" alt="Edit Credentials Button" showCaption="false"} ::: :::WorkflowBlockItem In the **User** field, enter the **username** that appeared ZEN Master's Configuration section. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/p5wmX4YO8l4kVkp2XIONl_image.png" size="80" width="813" height="352" position="center" alt="User field" showCaption="false"} ::: :::WorkflowBlockItem In ZEC, in the **Private Key** field, click Upload Key and select the key that you have downloaded. ::: :::WorkflowBlockItem Click **Apply**. The **Key** field will indicate OK. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/NplaTPpmQzaFRyrnzkO0W_image.png" size="80" width="581" height="109" position="center" alt="Key OK" showCaption="false"} ::: :::WorkflowBlockItem In ZEC, in click the **Add** button next to Remote Source Port. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/QAczkTYGhrh09r1O425-D_image.png" size="80" width="797" height="136" position="center" alt="Add Remote Source Port" showCaption="false"} ::: :::WorkflowBlockItem In the **Remote Source Port** field, enter the Remote Source Port that appeared ZEN Master's Configuration section. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/wcrx5qquNrCYBQ_jMJGAg_image.png" size="80" width="931" height="359" position="center" alt="Port Field" showCaption="false"} ::: :::WorkflowBlockItem In ZEC, click **OK**. ::: :::WorkflowBlockItem In ZEN Master, in the main navigation, click **Zixi Edge Devices** and check that the status of the newly connected ZEC has changed from Pending to OK. ::: :::: [title] Sort [path] ZEN Master/ZEN Master User Guide/Management Console UI Elements/Working with Lists/ You can sort all lists by the data elements shown in each of the columns. When the full list screen is shown, click on the desired column headings. You can reverse the order by clicking the heading a second time. **To sort a column:** ::::WorkflowBlock :::WorkflowBlockItem Hover over the column name. An arrow is displayed indicating the sort direction (ascending/descending). ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Hb-NP7hB5fyI1uIRoho8V-20260201-175825.png" size="84" width="521" height="127" position="center" showCaption="false"} ::: :::WorkflowBlockItem Click the arrow to sort the list based on. ::: :::WorkflowBlockItem Click again to change the sort direction. ::: :::: [title] Live Events Management [path] ZEN Master/ZEN Master User Guide/Introduction to ZEN Master/ Zen Master Live Events feature provides users with the ability to schedule, run, and manage, workflows for occasional-use deliveries such as sporting events, press conference, news events, live production, and other real-time events. For more information, see [Live Events](docId\:tGt1QO5H-JHLJYI9bXd2x). ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/gte4tskY3vt0RHrEiujGJ-20260129-104852.jpg) [title] Download Quick Report [path] ZEN Master/ZEN Master User Guide/Management Console UI Elements/Working with Lists/ On the Resources/System objects main list screens, you can download a quick report about the items in the list. You can have the report include only relevant information by filtering the contents of the list before downloading the report. To learn more about reports, see [Reports](docId\:g5o2hv68aRXDvBcDL9SVG). ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/KCbzRGGrWeW5obcJBXPUr-20260129-140038.jpg) [title] Batch Processes (multi-select) [path] ZEN Master/ZEN Master User Guide/Management Console UI Elements/Working with Lists/ When a list screen (e.g. Sources, Targets etc.) is shown in full view (i.e. you haven’t clicked on a specific object), a checkbox is shown next to each object. When you select one or more checkboxes a series of buttons for performing batch processes is shown at the top of the screen. The available batch process options are different for each screen. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/iiS7Dddm_Q6QeaqBUVNia-20251208-120040.png) When you click on a batch process button, the following dialog is displayed: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/fO65f7Xkn9yA458JQKvIv-20251208-123018.png) The dialog displays the list of objects on which the action will be performed. Select Keep sources selected on close to maintain them selected after clicking **Close**. Confirm the action by clicking the the action button (e.g., Mute (4)). The action is applied on the objects and the following dialog is displayed confirming the updates made on each object: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Z5FxgtiTeMwG_vNK3Zczh-20251208-125014.png) [title] Show/Hide Columns [path] ZEN Master/ZEN Master User Guide/Management Console UI Elements/Working with Lists/ On list screens, you can select which columns to show/hide. The column settings persist whenever you return to the page, even after logging out of ZEN Master and returning. The settings are stored on a per browser basis, such that the browser on your tablet can be set to show different columns than those shown on your laptop browser. **To show/hide columns: ** ::::WorkflowBlock :::WorkflowBlockItem Click on the **column selection** button. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/fQDNzxd9LfJWu0mECRZtj-20260129-134350.jpg) The column selection drop-down list opens. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Ck8uBndMwr5w2MAdTF560-20260129-134527.jpg) ::: :::WorkflowBlockItem Select/deselect the checkbox for each column that you would like to show/hide. Only the selected columns are displayed. ::: :::: [title] Working with Data Forms [path] ZEN Master/ZEN Master User Guide/Management Console UI Elements/ Data forms are used to create new instances of Resources (Feeder, Receiver, Broadcaster), system Objects (Source, Channel, Target) and other system elements (e.g. Grid, Automation, etc.). When a form is opened, the browser navigates to a new page. For forms that are especially long, navigation links at the top of the page will take you directly to the desired section of the form. Also, some sections of the form, such as the “Advanced” section, will start out collapsed and can then be expanded by the user. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/zxKMorpTQjyZee5j9hghm-20260129-140622.jpg) [title] Change Tracking [path] ZEN Master/ZEN Master User Guide/Management Console UI Elements/ Change Tracking displays the history of changes that were made to the object configuration. The feature is available for ZECs, Broadcasters/Clusters, Sources, Channels, and most Target types. ## What change tracking records - Changes made in ZEN Master, through the web interface or the API, are recorded. - Changes made directly in the Broadcaster's web interface are not recorded in ZEN Master. - A change made from a Diagram View is recorded against the object that changed, not the object whose diagram you had open. For example, disabling a target from a source's diagram is recorded on the target. - Each target keeps its own history, including changes to its channel. A channel's history does not show changes made to its targets. ## To view the change tracking: ::::WorkflowBlock :::WorkflowBlockItem After selecting the relevant object, click the **Change Tracking** tab. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/EpBDwQ-BfX4Y_tOj53pwF_image.png) ::: :::WorkflowBlockItem The list includes entries for all the changes that were made by a user. If multiple changes were made at once, these will appear as a list: - **Modified by**: the user that made the change. - **Date/Time**: the date and time of the change. - **Change**: the name of the setting that was modified. - **Previous Value**: the value of the setting before the change. - **Updated Value** - the value of the setting after the change. ::: :::: ## To revert a specific change: - Click **Revert** on the specific change. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/pmvEb3GARoKFL9XaVLCK__image.png" size="100" isUploading="false" width="1723" height="597" darkWidth="1723" darkHeight="597" showCaption="false" indent="2"} ## To revert a batch of changes: - Click **Revert All **on the specific batch of changes. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ng34eBQwDR8XK9u-FQjAy_image.png" size="90" width="1378" height="597" position="center" darkWidth="1378" darkHeight="597" showCaption="false"} The revert itself is added as a change in the Change Tracking. ## Initial State For any objects created after the 18 November 2025 release of ZEN Master, the change log will record the initial creation of the object, so that you always have to way to view the initial configuration of the object: ![Initial State of Object](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/ZLnqEluoip3VrZJ2PEb-q-20251110-191041.png) [title] ZEN Master Egress IPs [path] ZEN Master/ZEN Master User Guide/Introduction to ZEN Master/ Whenever ZEN Master makes a call to the rest of the world (when sending Kafka messages, for example), it uses one of the following static IP addresses: - 3.210.250.62 - 54.144.111.182 This information is provided in case you need to whitelist these IPs for incoming data. [title] Introduction to ZEN Master [path] ZEN Master/ZEN Master User Guide/ ZEN Master is the live video orchestration and telemetry control plane that enables Zixi users to manage large-scale configuration and monitoring of the Zixi Enabled Network, Zixi's live streaming platform, devices and appliances. With ZEN Master, media organizations can extend their reach, increase production speed and dramatically reduce operational costs. [How To Videos](docId\:A9-EHZYG4xt_V27GeYpu2) - [Overview](docId\:z3EbEG7LyRVYapKJcnhdd) - [Centralized Management](docId\:PIfM-hcU0c65ene-F9MTz) - [Acquisition and Delivery](docId\:R_pY6kDAN4ov6pfUanev8) - [Health Monitoring](docId:16lMt-Vw08a7c2FzmlhzP) - [PID Mapping Options in ZEN Master](docId\:EAV0R1Up2eZocHPbN4Luo) - [Adding HTML Overlays - ZEN Master](docId\:fHnebEFhWM0psrzv52tDo) - [Deep Data Analytics](docId\:ruitfOmFtDfosqpNAXMoa) - [Global Visibility and Health](docId\:db0vLNelSzs5A-l908XHy) - [ZEN Master Egress IPs](docId\:zWDaK6BRL9-HEDtaBH_9b) - [ZEN Master Authorization](docId\:P0Ca6G5B8dMnrW1mqQCTP) - [Access Control](docId\:zV-r8F50gKOQzlviVFGgf) - [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ) - [Understanding Licensing](docId\:zff-plXnoyw6dEgKwSHvU) - [Improving Stream Resiliency: Error Correction and Concealment](docId:9_OLo1Argk_2aDoSHYFBb) - [Live Events Management](docId:__mKjT4nRjWbP07CSkwWc) - [Disaster Recovery (Alternative Path)](docId\:poo4ZS1-ZjRa1snDylqE0) - [Redundancy in ZEN Master](docId\:k9mukecY4pzgeowUJDrHH) [title] Configuring a transcode profile in ZEN Master [path] ZEN Master/ZEN Master User Guide/Configuration/ A transcode profile is a reusable set of encoding settings (codec, resolution, bitrate, audio). You create it once, then apply it to any transcoded source or channel. Changing a profile later affects every source that uses it. ## Before you start - You need a ZEN Master user with permission to manage transcoding profiles. - Know your target output: codec, resolution, frame rate and bitrate. - Transcoding needs a Broadcaster with transcoding enabled in its license. ## Create a profile 1. Log in to ZEN Master. 2. In the left menu, go to **Transformation > Transcoding Profiles**. 3. Click **Add** (or **New Profile**). 4. Enter a **Name** that describes the output, for example 1080p30-h264-6M. The name is how you will find the profile when you build a source. ### Video 1. Leave **Transcode Video** on to re-encode, or turn it off to pass the original video through. 2. Choose the **Video Codec**: H.264 or H.265. 3. Choose the **Encoding Profile**. For H.264 this is Baseline, Main, High or High 10. Use High unless a downstream device needs something simpler. 4. Set the **Resolution** (width and height) and **Frame Rate**. Keep the source aspect ratio unless you need to change it. 5. Set the **Bitrate**. Choose **CBR** for a steady rate, or **VBR** with an average and a maximum. 6. Set the **GOP** (keyframe interval). A common choice is one keyframe every 1 to 2 seconds, for example 60 at 30 fps. Use closed GOP if the output feeds HLS or DASH packaging. ### Audio 1. Leave **Transcode Audio** on to re-encode, or turn it off to pass the original audio through. 2. Choose the **Audio Codec** (for example AAC), **Bitrate** and **Sample Rate**. ### Optional 1. To burn in a logo, enable **Logo Insertion**, upload the image and set its position, size and transparency. 2. Click **Save**. ## Use the profile 1. Go to **Sources** and create or edit a source. 2. Set the source type to **Transcoded**. 3. Choose the input (parent) source and select your profile in **Transcoding Profile**. 4. Save, then add the source to a channel or target as normal. ## Check it works Open the new source and confirm it is **Running**. In the stream details, check that the output codec, resolution and bitrate match the profile. ## Tips - Build one profile per rendition (for example 1080p, 720p, 480p) and reuse them across channels. - A profile that is in use cannot be deleted. Remove it from the sources first. - Editing a profile restarts the transcode on every source using it. Make changes during a quiet period. - Hardware acceleration (GPU) needs a Broadcaster with a supported GPU. If you are unsure, leave it off. ## API You can also manage profiles with the ZEN Master API (/transcoding\_profiles). See the ZEN Master API reference on the Zixi Customer Portal under Downloads. [title] Adding HTML Overlays - ZEN Master [path] ZEN Master/ZEN Master User Guide/Introduction to ZEN Master/ ## Overview HTML overlays, which might be static images or dynamic widgets showing such things as news headlines, stock prices, sports scores, or local weather, can be added as overlays on streaming videos during transcoding. Zixi uses the **Chromium Embedded Framework (CEF) **to embed the HTML overlay into each frame of the video. Note that this process is separate from the processing of the video frames, and depending on the CPU load, might run more slowly. That means that while a snapshot from the HTML overlay will be added to every frame, some images may repeat. For a static overlay this makes no difference, but for a dynamic overlay, there might be small discrepancies between what is seen in the video stream and what is seen in overlay viewed separately. ## Requirements - The Broadcaster must have a license key that enables transcoding as well as a [transcoder (software, GPU, or VPU) installed](docId\:lgQ7l9Suyqop2EtaBv1uL). - The [HTML Overlay Plugin](docId:1svyta7P777nBTqPN8yt8) must also be installed. ## Adding the Overlay to a Transcoded Source In ZEN Master, HTML Overlays can only be added to [Transcoded Source](docId\:lNauA-wKTttUl4xktBido). The process is very simple: 1. Put the HTML Overlay on public URL. 2. Add the URL to the **HTML Overlay URL** field, which appears in the **Advanced** section of the screen for creating a Transcoded Source: ![HTML Overlay URL Field](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/2oX5nTJ6NeWXnX2_ohihD-20260525-160008.png) Note that there is an option to use the audio track from the HTML Overlay for the video audio track, which requires entering the audio PID number. ## Creating HTML Overlays HTML overlays can be created as static content that sits on top of other content, such as a logo or an ad banner. They can also be dynamic, pulling content such as current weather conditions or news headlines in from another source via JavaScript. :::hint{type="info"} Before looking at the details of creating overlays, it's worth pointing out that there are several platforms there are several platforms available that will help you do so easily. The one we find best for video overlays is [Singular.live](https://singular.live). ::: ### Creating Static HTML Overlays Creating a static overlay is straightforward. ::::WorkflowBlock :::WorkflowBlockItem Add a basic overlay element to your HTML: ```html
Place whatever content you want here.
``` ::: :::WorkflowBlockItem Style it with CSS so it covers the whole viewport and sits on top of the page: ::: :::: You can drop that into a bare HTML file and see it work, then adapt the CSS (color, opacity, z‑index) and what you place inside `#overlay` for your use case (logo, tutorial, modal, etc.). ### Creating Dynamic HTML Overlays You can treat the overlay as a floating “info panel” that your JavaScript keeps updating with live data (weather, headlines, or both). **Basic Idea** You create a fixed-position overlay element, style it so it sits on top of the page (but not full‑screen, unless you want that), and use`fetch` on an interval to pull in JSON from whatever API you like. Then you render that data into the overlay. **Example: dynamic overlay with weather + headlines ** ```html Dynamic Overlay: Weather & News

Weather

Loading weather…

Headlines

Loading news…
``` This gives you a small, dismissible overlay in the top‑right that keeps pulling in fresh weather and headlines. You can easily adapt it to a bottom bar or a ticker‑style strip by changing the CSS. If you prefer not to deal with APIs at all, you can also embed existing widgets inside an overlay container like this—for example a news ticker widget for \[headlines]  ([https://www.commoninja.com/widgets/news-ticker](https://www.commoninja.com/widgets/news-ticker)) or a configurable \[weather widget panel for current conditions and forecast] ⁠ ([https://weatherwidget.io/](https://weatherwidget.io/))—and let them handle the live data while your overlay just positions them. [title] Understanding Licensing [path] ZEN Master/ZEN Master User Guide/Introduction to ZEN Master/ # Licensing Portability, Evaluation and Expiry Zixi broadcaster and ZEC licenses govern what connection modes a device can use, how the license validates itself over time, and how that license behaves when hardware changes. This article covers the areas that prompts the most questions: license portability during hardware migration, license expiry and validation behavior, and connection mode limits by license tier. ## License Types: Metered vs Perpetual Every Broadcaster or ZEC license is issued as one of two types, and the type determines how the license validates itself while the device is running. **Perpetual license: **issued for the life of the hardware or a defined term, with no recurring validation requirement against Zixi's licensing servers. **Metered license: **requires the device to check in with Zixi's licensing servers on a recurring basis to remain valid. ## 72 Hour License Server Check-in Requirement A metered license must successfully check in at least once every 72 hours. If the device cannot reach the licensing server (due to network outage, firewall change, DNS failure) within that window, the license enters a failed validation state and will de-activate. The connections relying on that license will be rejected, even though the license itself is still good and the portal-listed expiry date is unaffected. The device will require the license to be re-activated to restart connections. ## License Portability & New Machine Detection Licenses are tied to a hardware fingerprint (host ID), not just a license key. Certain hardware changes are treated as a new machine and require re-activation. ### What triggers a new machine detection •      A NIC change on the host, since the primary network interface is part of the fingerprint used for activation. •      An IP address change alone does not typically trigger new machine detection on its own, but is often accompanied by a NIC change during migrations which does trigger one. •      Moving the license to genuinely new hardware (new VM, new physical host, cloned image with a new interface). ### How license activation works Each license has a fixed number of activation availability slots. Activating on a new machine consumes one slot. Decommissioning the old server does not automatically return its slot to the pool. Slot recovery after decommissioning, and re-activation on replacement hardware, both require Zixi to release and reissue an activation. Your sales team or solutions engineer can assist you with additional activation slots for Broadcaster. For ZEC you can issue additional activation slots yourself within the Zixi portal. ## Migrating a license to new infrastructure **1. Confirm the license type and current activation count: **In the license portal before starting the migration. **2. Provision the new hardware: **and retrieve its host fingerprint (host ID) from the Broadcaster or ZEC installer. **3. Submit the new host ID to Zixi: **along with the license key and a request to release the old activation slot, if the old server is being decommissioned. **4. Apply a new activation slot: **to the new machine once Zixi confirms the activation slot has been added to your account. **5. Decommission the old server: **once you confirm the new machine is up and active. :::hint{type="info"} *Steps 1, 2, and 4 are self-service. Step 3, releasing or reassigning an activation slot, requires Zixi involvement and is not available directly in the Zixi portal. Prepare ahead when scheduling your migration.* ::: ### Connection Modes by License Feature License features determine which input and output connection modes a Broadcaster or how ZEC is permitted to run, independent of whether the physical hardware can support them. All of these may have specific limits. **Push input: **the license permits the device to receive a stream initiated by the sending encoder. **Listener input: **the license permits the device to open a port and wait for a third-party encoder to connect to it. **Push output: **the license permits the device to initiate an outbound connection to a receiver. **Listener output: **the license permits the device to wait for a downstream receiver to connect. Third-party encoders vary in which mode they support. When integrating a third-party device, confirm both that the Broadcaster/ZEC license permits the required mode and that the third-party encoder itself supports initiating or listening for a connection accordingly. Mismatches here are a common source of connections that appear licensed at the device level but fail to establish. ![License comparisons for ZEC, Broadcaster, Feeder & Receiver](https://zixi.wpenginepowered.com/wp-content/uploads/2022/10/Zixi-Master-Pitch-Deck-Sep-2022-1024x576.png) :::hint{type="warning"} ZEC has specific limitation which requires using Zixi protocol as either the Input or an Output for each stream. ::: ### Troubleshooting: License failed before expiry A license failed error appearing before the portal-listed expiry date is not an expiry issue. It typically points to one of two causes. - Check-in failure on a metered license (see the 72-hour requirement above) - Server-side recognition failure following a license push or update In the second case, a corrected or reissued license push from Zixi resolves the failure. This can affect both the Zixi Broadcaster and third-party licensed devices connected to it, so a license failure on a downstream third-party device does not rule out a licensing issue on the upstream Broadcaster. ## Immediate remediation steps **1. Confirm the expiry date listed in the Zixi portal: **to rule out an actual license expiration. **2. Check network connectivity: **from the device to Zixi's licensing servers if the license is metered. See the [Network Port Settings](docId:_ZnPrTHruh2RZO8rhei2Z) **3. Contact Zixi support: **with the license key, the affected device's host ID, and the timestamp the failure began. [title] Customizing the Info Panel (Layout) [path] ZEN Master/ZEN Master User Guide/Management Console UI Elements/ It is possible to customize the Info Panel. The available customizations include: - Drag individual tiles left and right on the two rows. - Add new tiles from the tiles list. - Delete tiles from the second row. - Pin/Unpin each row. # Unlocking the layout Before you can customize the Info Panel, you need to unlock its layout. **To unlock the layout:** ::::WorkflowBlock :::WorkflowBlockItem Click the kebab icon in the upper right corner of the info panel. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/TXL0WPEYCwcNDKRKYo4l1_layout-controls.png) ::: :::WorkflowBlockItem Make the changes, as described below and reopen the Layout menu and click **Save** when done. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/oLVTdSEMlNJXCIa1hX_yu_save-layout-changes.png" size="60" isUploading="false" position="center" width="794" height="514" darkWidth="794" darkHeight="514" showCaption="false"} ::: :::WorkflowBlockItem You can click **Revert** to undo the last change or click **Reset** to undo all the changes. ::: :::: # Moving tiles **To move tiles:** 1. [Unlock the Info Panel](docId:3JrhHkACBegQy_tt-djvG). 2. Drag and drop the tile to the desired location on the Info Panel within the same row. # Adding new tiles Additional tiles can be added to the second row. **To add new tiles:** ::::WorkflowBlock :::WorkflowBlockItem [Unlock the Info Panel](docId:3JrhHkACBegQy_tt-djvG). ::: :::WorkflowBlockItem On the second row click the **Edit** button. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/k5Yl6iFH9Byhc9VchOAol_image.png" size="58" width="450" height="92" position="flex-start" alt="Edit button for layout" darkWidth="450" darkHeight="92" showCaption="false"} ::: :::WorkflowBlockItem Select the tiles that you want to add. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/5hWGJ7uIMUdwcfZ0uasUi_image.png" size="38" width="329" height="302" position="flex-start" alt="Adding tiles to a layout" darkWidth="329" darkHeight="302" showCaption="false"} ::: :::: # Deleting tiles Tiles can be removed from the second row. **To delete a tile:** 1. [Unlock the Info Panel](docId:3JrhHkACBegQy_tt-djvG). 2. Hover your mouse on the tile and click the **Remove** button. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/9Kt_9fHvqGLFBKSg7pUtd_image.png" size="46" width="291" height="112" position="flex-start" darkWidth="291" darkHeight="112" showCaption="false" indent="2"} # Pinning/unpinning a row **To pin/unpin a row:** 1. [Unlock the Info Panel](docId:3JrhHkACBegQy_tt-djvG). 2. Hover your mouse on the row and click the Pin/Unpin icon. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/kj4IbUUkU8E3O-u-_iWKt_image.png" size="22" width="158" height="81" position="flex-start" darkWidth="158" darkHeight="81" showCaption="false" indent="2"} [title] Adding a Broadcaster Cluster – Manual [path] ZEN Master/ZEN Master User Guide/Broadcasters/Creating a Broadcaster Cluster/Creating a New Broadcaster Cluster/ **To add a Manual Broadcaster Cluster:** :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, select **Broadcasters**. ::: :::WorkflowBlockItem Click **+ Add.** The **Create New Broadcaster Cluster** screen is displayed: ![Create new Cluster](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/qOYE_O1m49eCJCKmxubQ0_image.png) ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, type a logical name for the Zixi Broadcaster Cluster resource. ::: :::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 Cluster 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 cluster. 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 In the **DNS Prefix** field, enter a unique domain name for sending the streams to/from this cluster. ::: :::WorkflowBlockItem DTLS is session based encryption over the connection, establish on the network link when the connection is made, using the broadcasters web certificate. Under **DTLS**, select one of the following: - **Clear Only** - select this option if you do not wish to use DTLS, only clear ports (2077+2088) - **Dual Mode** - Select this option to support both DTLS encrypted and non-DTLS/clear ports (2077/2088 + 7077+7088) - **DTLS Only** - Select this option to support DTLS encrypted Zixi connections only. This means that ZEN Master won't create non-DTLS Zixi connections on the cluster, i.e., no clear traffic on port 2077+2088 (7077+7088 only). ::: :::WorkflowBlockItem If you selected the **DTLS Mode** or **DTLS Dual Mode options**, then the **Ignore DTLS certificate when not supported** checkbox appears. Select this checkbox if you would like to enable resources using older versions of Zixi software (\Amazon AWS:** ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-g9Xl-_o0j0jkacKm-t-sq-20250505-181623.png" size="64" width="882" height="854" position="center" alt="Configuration - Amazon AWS" showCaption="false"} ::: :::WorkflowBlockItem Click on the **Documentation **tab and follow the instructions there: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-GQcFpTjsyuPSnm51rPZ4j-20250505-181917.png" size="88" width="1218" height="376" position="center" alt="AWS Documentation Tab" showCaption="false"} ::: :::: :::hint{type="info"} **Note: **the **policy document** is divided into sections - see the `Sid` value to see what the section refers to. If some sections are not relevant to your account, you can remove them. You can also remove selected items from the `Action` list in a section if they are not relevant or you do not wish to allow users to perform those actions. ::: [title] Connecting the Zixi Feeder (Zixi Feeder UI) [path] ZEN Master/ZEN Master User Guide/Zixi Edge Devices/ For each Zixi Feeder component that has been configured in ZEN Master, you will need to configure the connection of the Zixi Feeder (using its Zixi Feeder UI) to ZEN Master. This will use the configured SSH keys to enable the actual connection. This can either be done manually by entering the configuration settings into the Zixi Feeder UI, or automatically using the ZEN tab in the Zixi Feeder UI (for v12 Feeders). :::hint{type="info"} If you are using an SSH Key that was imported from the Feeder (not generated in ZEN Master) then you will need to use the manual method to connect the Feeder to ZEN Master and not the automatic metho ::: **To connect the Zixi Feeder Manually (for v11 and below):** ::::WorkflowBlock :::WorkflowBlockItem In the ZEN Master UI, in the main navigation, click **Zixi Edge Devices**. ::: :::WorkflowBlockItem Select the Feeder that you would like to connect ::: :::WorkflowBlockItem In the Details tab at the bottom of the screen, click on the download link for the **SSH Key**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Uh2TGO63d1mrB_Y5EPvQN_image.png" size="46" width="292" height="146" position="flex-start" alt="Download SSH Key" showCaption="false"} ::: :::WorkflowBlockItem In the **Configuration** section, you will find your personal connection configuration settings for use with Feeders *Version 1.11 and older* . You will use these settings to connect the Zixi Feeder (host, username, and remote source port), so you should write them down or keep this browser tab open while you configure the Zixi Feeder. ::: :::WorkflowBlockItem Login to the **Zixi Feeder UI** (it could be a locally installed Zixi Feeder, e.g. [http://localhost:4200](http://localhost:4200) or a remote Zixi Feeder). ::: :::WorkflowBlockItem Go to **Settings > SSH Tunnels**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/8obxDrKR_cL3zjuPQrF_p_image.png" size="82" width="1199" height="384" position="flex-start" alt="SSH Settings" showCaption="false"} ::: :::WorkflowBlockItem In the **Key File** field, click **Upload Key** and select the downloaded SSH key file. ::: :::WorkflowBlockItem In the **Host** field, enter the host name that appeared in the *Configuration Help*. ::: :::WorkflowBlockItem In the **Username** field, enter the username that appeared in the *Configuration Help*. ::: :::WorkflowBlockItem Click **Apply**. ::: :::WorkflowBlockItem In the **Reverse Tunnels** section (at the bottom) click **Add**. The **Tunnel Details **dialog opens: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/_hkbBJUnMhPCi3ZvN7g7N_image.png" size="48" width="565" height="305" position="flex-start" alt="Tunnel Details" showCaption="false"} ::: :::WorkflowBlockItem In the **Remote Source Port **field, enter the Remote Source Port that appeared in the *Configuration Help*. ::: :::WorkflowBlockItem Click **OK.** ::: :::WorkflowBlockItem In ZEN Master, in the main navigation, click **Feeders** and check that the status of the newly connected Zixi Feeder has changed from Pending to OK. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/d_um_HVFBwdJNEz7iy6tm_image.png" size="90" width="932" height="299" position="flex-start" alt="Feeders List" showCaption="false"} ::: :::: **To connect the Zixi Feeder Automatically (for v12 and above):** ::::WorkflowBlock :::WorkflowBlockItem Login to the **Zixi Feeder UI** (it could be a locally installed Zixi Feeder, e.g. [http://localhost:4200](http://localhost:4200/) or a remote Zixi Feeder). ::: :::WorkflowBlockItem Click the **ZEN** tab. The ZEN login fields are displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/xSUkr9kkDvBWDkLhU5Q62_image.png" size="90" width="1049" height="565" position="flex-start" alt="ZEN Master login" showCaption="false"} ::: :::WorkflowBlockItem In the **Account ID** field, enter the customer domain of your ZEN Master account (e.g. if you login to ZEN at **demo.zen.zixi.com** then your Account ID is 'demo'). ::: :::WorkflowBlockItem In the **Email** field, enter the username for your ZEN Master account. ::: :::WorkflowBlockItem In the **Password **field, enter the password for your ZEN Master account. ::: :::WorkflowBlockItem Click **Login**. A list of Feeders configured in ZEN Master is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/9MQbtUjVqDWr17-OGZGdp_image.png" size="80" width="562" height="203" position="flex-start" alt="Feeders list in ZEN Master" showCaption="false"} ::: :::WorkflowBlockItem For the Feeder that you are adding, which should currently be in **Pending** mode, click **Select**. Details about the Feeder are shown in the **Status** section. ::: :::WorkflowBlockItem Click **Refresh**. The connection is configured automatically. ::: :::WorkflowBlockItem Verify that the Status is shown as **On**. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/lE58ldrrT3c8yZAxeXAyb_image.png" size="80" width="549" height="94" position="flex-start" alt="Feeder status" showCaption="false"} ::: :::WorkflowBlockItem In the ZEN Master UI, in the main navigation, click **Feeders** and check that the status of the newly connected Zixi Feeder has changed from *Pending* to *OK*. ::: :::: [title] Configuring Microsoft Azure Account Credentials [path] ZEN Master/ZEN Master User Guide/Configuration/ You can link one or more Microsoft Azure accounts to ZEN Master. This enables you to launch managed Broadcaster clusters on Azure (including broadcasters that use Nvidia GPU for transcoding). You can also use Azure Blob storage as publishing targets for storing HLS and DASH manifests and segments. The **Accounts **tab in the **Azure Accounts** screen shows your existing Azure accounts that are linked to ZEN Master. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/dcR8Irz3XzsRbb7XKH0bJ_image.png" size="90" width="1319" height="317" position="center" alt="Azure Account List" showCaption="false"} The **Documentation** tab in the screen shows the procedure used for linking an Azure account to ZEN Master. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/45eYefE531oFvSxajgJNf_image.png" size="90" width="1600" height="530" position="center" alt="Documentation for Azure Accounts" showCaption="false"} To link your Azure account to ZEN Master, first you need to create an Azure Active Directory application with a service principal (identity). Then you can enter your Azure account parameters into ZEN Master to link your Azure account to ZEN Master. - [Linking an Azure Account](docId\:jSST1KXHRRRFCdyc1lENl) - [Editing an Azure Account](docId\:QlqbJdV3uSeEzbNOgkDTm) - [Adding Blob Storage to an Azure Account](docId\:FlsoX9FAA-6mbUA2736oa) [title] Configuring Tags [path] ZEN Master/ZEN Master User Guide/Configuration/ Tags are used to control access to ZEN Master Resources as well as other system objects such as Sources, Channels, Targets, Automation Task Sets, Reports etc. Each object instance is assigned a Tag. User Roles allow access to objects based on the related Tags. Only users who are assigned Roles that allow access to a particular Tag can access objects associated with that Tag. To learn more about User Management in ZEN Master, see [Account Management](docId\:t49XhHyZCGfR2Rz2GtnRm). Tags are created on the **Configuration** > **Tags** screen[\[1\]](docId\:vPSZIytS_uzxdb-zvrAcX) . They are then assigned to Roles on the **Account Management** > **Roles **screen, see [Managing Roles](docId\:yEXZ8AiX--tjAjZsol3Ns). The Tags screen shows a list of all Tags that have been created in the system. ![Tag list](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/pDjE97PYHelXHeI-qCMmK_image.png) The following table describes the information shown on this screen and the actions which can be taken. | **Parameter** | **Description** | | ------------- | --------------------------------------------------------------------------------------------------------------------- | | Name | The name of the Tag | | ***Actions*** |
| | Edit | Enables you to edit the name of the Tag. | | Delete | Deletes the Tag.
Note: You can only delete an Tag that is not currently assigned to any Roles or system objects. | ### Notes 1. Alternatively, it is possible to create new Tags within the flow of creating a Role. [title] Configuring Flapping Detection [path] ZEN Master/ZEN Master User Guide/Configuration/Configuring Notifications/ ZEN Master uses Flapping Detection to stop the system from flooding users with multiple notifications for a particular object in the system that undergoes frequent state changes. Once the threshold frequency of recurrence is reached, the system automatically mutes the notifications for that object until it becomes stabilized. Users can configure the settings for what degree of frequency causes the notifications to be muted and how long the system must remain stable before notifications for that object are reactivated, see [Flapping Detection](docId\:Sha6sanwt1OKG_Z9VdxdD). ![Flapping Detection Notificsations](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/kUCYT1pnfWmQPLOgv5czp_image.png) The following table describes the information shown in this section: | **Parameter** | **Description** | | ------------------- | ----------------------------------------------------------------------------------------------------------------------- | | Window \[minutes] | The number of minutes in which the specified number of state changes must occur to trigger the Flapping Detection. | | State Changes | The number of state changes that must occur in the specified window of time in order to trigger the Flapping Detection. | | Cooldown \[minutes] | The number of minutes that the object must remain stable in order to resume sending notifications for that object. | | Update button | Activates changes made to the configuration. | [title] Configuring Kafka Servers [path] ZEN Master/ZEN Master User Guide/Configuration/Configuring Notifications/ ZEN Master can export event notifications and SCTE 35 messages to an Apache Kafka server. Kafka is a data streaming platform that allows you to publish and subscribe to streams of data, store them, and process them. ZEN Master is a “publisher” that uses the Kafka Producer API to send event data to a Kafka server. Once the event data from ZEN Master is streaming to a Kafka server, connectors are available to pull data from the Kafka server into third party applications and services including Elasticsearch, Splunk, Azure Event Hubs, AWS CloudWatch, AWS S3, and more. To configure a Kafka server to receive event notifications from ZEN Master, see [Sending Notifications to a Kafka server](docId\:Hsg1B8UgD18xjh3RR3OPl) . The following table describes the information shown in this section: | **Parameter** | **Description** | | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Name | The name of the Kafka server configuration. | | Topic | The Topic created in the Kafka server where the notifications will go. | | Servers | Kafka broker/host combination delimited by comma, e.g. [kafka-1.us-east-1.myapp.com](http://kafka-1.us-east-1.myapp.com/):9093,[kafka-2.us-east-1.myapp.com](http://kafka-2.us-east-1.myapp.com/):9093 | | Events | Shows if the server is configured to receive event notifications. | | SCTE-35 | Shows if the server is configured to receive SCTE-35 messages. | | ***Actions*** |
| | Test | Enables you to verify the connection between ZEN Master and Kafka. | | Edit | Enables you to edit the Kafka configuration. | | Delete | Deletes the Kafka configuration. | [title] Global Search [path] ZEN Master/ZEN Master User Guide/Management Console UI Elements/ The global search feature enables you to search all objects (i.e. Feeders, Broadcasters, Receivers, Sources, Channels, Targets, and Networks) in the system. This makes it simple to access data about objects in the system. The search results screen includes a link to view each object on the main screen for that type of object (i.e. view feeders on the **Feeders** screen). For example, if you want to find out about the status and usage of resources in the United States you could type in "US" and all objects that have US in their names are displayed. You can then view data about each relevant resource. :::hint{type="info"} The global search only shows results for names of system objects, as opposed to the local search box on specific screens which shows results for all relevant parameters. ::: **To search for objects in the system.** ::::WorkflowBlock :::WorkflowBlockItem Enter the search character string in the search box (above the main navigation). ::: :::WorkflowBlockItem Click the search button 🔎. The search results are shown on the Search screen. The results include a list of objects with the search string in their names. The search results are grouped by object type. For each resource and system object, the current status is shown as well as a link to view detailed info for that object on the main screen for that object type. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Fdy1ZQSLol9zpjjhwdhCC_global-search.png) ::: :::WorkflowBlockItem Click **View** next to an object to view detailed data about that object. ::: :::WorkflowBlockItem If you would like to adjust the search string, edit the string shown in the search box at the top of the screen and click **Search**. ::: :::: [title] Dark Mode [path] ZEN Master/ZEN Master User Guide/Management Console UI Elements/ ZEN Master features a dark mode of the UI as well as a light mode. The dark mode is enabled by default, click the moon icon at the top to toggle between the dark and light modes. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/-nYzH3z7sAJ9QayUpeX85_image.png" size="80" width="1346" height="213" position="center" showCaption="false"} [title] Help [path] ZEN Master/ZEN Master User Guide/Management Console UI Elements/ The ZEN Master Help menu (in the header bar) enables you to access relevant documents on the ZEN Master online documentations portal or to submit a support ticket. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/N7L4rFJRdnBMSaf4xpyf-_image.png" size="90" width="1428" height="355" position="center" showCaption="false"} - [Documentation](docId\:yyU_bd_44oHCyPVitOpi4) - [Support Tickets](docId\:ONQmWvheMVOnCGbqQQXss) [title] Source History Encoding Quality ePSNR [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/Source History/ This graph displays the **estimated Peak Signal-to-Noise Ratio (ePSNR) **over time, representing the video encoding quality. Each vertical orange box plot corresponds to a timestamp and shows the distribution of ePSNR values during that interval. **Y-axis (ePSNR Value): **Indicates the estimated PSNR, which is a measure of video quality — higher values typically represent better encoding quality. **Box plot elements:** - Top whisker: Maximum ePSNR - Top of box: 75th percentile - Bottom of box: 25th percentile - Bottom whisker: Minimum ePSNR :::hint{type="info"} ePSNR analysis is supported for MPEG2 or H.264 content, but not for most types of HEVC/H.265 content. Also, Sources must be 8-bit (not HDR) and Progressive (not Interlaced). ::: ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-b1yxWZ1_kj9L-tI-jaiAG-20250414-140159.png) [title] Adding a Source - RTMP [path] ZEN Master/ZEN Master User Guide/Sources/Adding ZEN Master Sources/ ZEN Master can receive a Source directly from an RTMP input. :::hint{type="info"} When this method is used, the stream is not protected by the Zixi protocol. ::: ZEN Master can receive RTMP streams that are sent using either *Push *or *Pull* method. The following procedure describes how to add an RTMP Source in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. ## To add an RTMP Source: :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Source selection** window is displayed. ![Create Source Options](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-3mXDQJHXUppSRZJSBYBnR-20250805-132303.png) ::: :::WorkflowBlockItem Click on **RTMP**. The **Create New RTMP Source** window opens. ![Create New RTMP Source](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/fu4i4B8QtP3kgdseQLZ0--20251105-145412.png) ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, enter a unique name to identify this Source in the system. ::: :::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 **RTMP Configuration **section, under **Mode**, select the mode used to send the stream. Options are: *Push* or *Pull*. ::: :::WorkflowBlockItem If you selected *Pull (Caller)* mode: - In the **URL **field, enter the URL of the RTMP server (e.g. rtmp\://server/live). - In the **Stream **field, enter the RTMP stream name as defined in the RTMP server. - In the **Username** field, enter the RTMP stream access credentials - Username. - In the **Password **field, enter the RTMP stream access credentials - Password. - Select the **Ignore TLS certificate errors **checkbox if you are sending the stream to a trusted server which does not have a valid certificate. When this option is selected, the Zixi Broadcaster will ignore TLS certificate errors and send the stream to its destination. ::: :::WorkflowBlockItem Both for Push and Pull Mode: If you would like to disconnect the stream when the bitrate drops very low, verify that the **Disconnect idle stream **checkbox is selected. (Default: selected) ::: :::WorkflowBlockItem In the **Source Configuration** section, 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 preference. 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 Onlly For Pull Mode: In the **Input NIC** 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 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 [Adding PID Mapping Profiles](docId\:gFTCaYurPL7DInoUyd14z). ::: :::: :::WorkflowBlockItem Select the **Alert on PID changes** checkbox if you would like to generate email notifications whenever a PID change is detected. ::: ::::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 closed captions, select **Monitor CEA-608 **checkbox**.** :::hint{type="info"} Monitoring CEA-608/ Closed Captions requires using a version 14.4 or newer Broadcaster. ::: If you would like to monitor CEA-708 closed captions, select **Monitor CEA-708 **checkbox**.** :::hint{type="info"} Monitoring CEA-708 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: :::: ::::WorkflowBlockItem If you would like to disable auto-pull, select the **Disable Auto-Pull** 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. (Default: 1000 ms) ::: ::::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 Only for Pull: Additional SCTE-35 options are available when you expand the **SCTE-35 Manipulation** section: ![SCTE-35 Manipulation](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/FxvVWM-bhpg9ZdVYW_LCl-20251104-153319.png) Here you can: - Enable SCTE-35 Manipulation - Specify the length of a search window for a NULL packet for SCTE-35 intertion - Set the SCTE-35 PID - Remove any existing SCTE-35 messages from the stream See the **Parameters Table** below for an explanation of these options. ::: ::::WorkflowBlockItem Also** for Pull Mode**: In the **Initial State **section, select the **Disabled **checkbox if you would like to disable this Source upon initial configuration. :::hint{type="info"} You can Enable/Unmute the Source at any time. ::: :::: :::WorkflowBlockItem Select the **Muted** checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. ::: :::WorkflowBlockItem In the **Initial State** section, select the **Disabled** checkbox if you would like to disable this Source upon initial configuration. ::: ::::WorkflowBlockItem Under **Error Concealment,** click the Enable Error Concealment checkbox to enable the following error concealment mechanisms that can correct transaport stream for downstream IRDs: :::Paragraph{indent="1"} 1\. **Continuous Timeline** - corrects errors that are related to timeline jumps in the source. This mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input. ::: :::Paragraph{indent="1"} 2\. **Replace Frames** - If there are frames with CC errors, it replaces them with skip frames (inserts the last good frame received in place of missing ones). This solves issues such as an IRD that lost synchronization when it received broken frames. This mechanism also creates a variant of the input (doubling the input). ::: :::Paragraph{indent="1"} 3\. **Renumber CC **- The Continuity Counter is part of the TS encapsulation. When there are CC errors in TR101 analysis it means that the counter has a gap due to the lost frames. This mechanism can re-write the CC counter for the downstream devices, so they will see a continuous increase of the counter. ::: :::Paragraph{indent="1"} 4\. **Delay (ms) **- Enter the delay that the Error Concealment adds to the stream in miliseconds. Error Concealment needs to buffer the stream to analyze it. One second is a reasonable value. Lower values may cause the Error Concealment to not be able to fix some of the frames. ::: :::Paragraph{indent="1"} 5\. **CBR Padding** - enter a value for the rate at which padding will be added to maintain a specific output transport bitrate. For example, if you have a video bitrate at 5000 kbps or that varies from 3000-5000 kbps and audio at 64 kbps, total bitrate will be max 5064 kbps or min 3064 kbps. With CBR padding set at 6000 kbps, 6000 kbps is being delivered downstream at all times, ensuring a consistent bitrate. ::: :::Paragraph{indent="1"} 6.** PCR Interval** - Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. This depends on standard used by downstream encoders or decoders. Options include: ::: :::Paragraph{listStyleType="disc" indent="2"} ATSC standard - 100 ms ::: :::Paragraph{listStyleType="disc" indent="2"} DVB standard - 40 ms ::: 7. **Remux Buffer Size** - Specify the time added for remuxing the stream (default: 2500 ms). 8. **Smoothing** - Time added for smoothing a bursty stream - adds to latency, but produces a smoother output. See [Improving Stream Resiliency: Error Correction and Concealment](docId:9_OLo1Argk_2aDoSHYFBb) for more information. ![Error Concealment Options](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/jEyT42FS_YflpTNxqCc9Q_zm-error-concealment-options.png) :::: :::WorkflowBlockItem If you would like to adjust the advanced settings, click **Advanced**. The **Advanced** settings fields are displayed: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/AyscX6G1T-mk7fPny8xza_rtmp-source-advanced.png) ::: :::WorkflowBlockItem If you would like to track usage for this Source, enter your **Billing Code** details. See [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ). ::: :::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 apply Input NIC selection to the network device, select the **Apply Input NIC selection to network device** checkbox. ::: :::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 Click **Save**. ::: ::::: ### RTMP Source Parameters Table | **Parameter** | **Description** | | ----------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the RTMP 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. | | ***RTMP Configuration*** | | | Mode | To create an RTMP Source, select the mode used for sending the stream. Options are: *Push* or *Pull*. | | URL (for Pull) | Enter the URL of the RTMP server (e.g. rtmp\://server/live). | | Stream (for Pull) | Enter the RTMP stream name as defined in the RTMP server. | | Username (for Pull) | Enter the RTMP stream access credentials – Username. | | Password (for Pull) | Enter the RTMP stream access credentials – Password. | | Ignore TLS certificate errors (for Pull) | Select this checkbox if you are sending the stream to a trusted server which does not have a valid certificate. When this option is selected, the Zixi Broadcaster will ignore TLS certificate errors and send the stream to its destination. | | Disconnect idle stream (for both Push and Pull) | Verify that this checkbox is selected if you would like to disconnect the stream when the bitrate drops very low. (Default: selected) | | ***Source Configuration (for both Push and Pull)*** | | | Ingest Cluster (for both Push and Pull) | Select from the drop-down list one of the available Ingest Clusters as the destination for the Source. | | Target Broadcaster/s (for both Push and Pull) | 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.*
**Note:** For managed clusters, it is not recommended to select a specific Broadcaster, as the Broadcaster’s availability may not remain stable. | | Input NIC (for Pull) | If you have selected a specific Target Broadcaster, you can select a specific input NIC from the drop-down list or select **Any**. | | 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. | | Alert on PID changes (for both Push and Pull) | If you would like to generate email notifications whenever a PID change is detected, select this checkbox. | | Log SCTE-35 (for both Push and Pull)
| 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 (for both Push and Pull) | If you would like to allow access to the stream directly through a supported player, select the **Allow** checkbox. | | 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 | Disables the Source thumbnail from appearing in the Sources list and other places. Disabling thumbnail may improve system performance. | | Monitor CEA-608 Closed Captions
| If you would like to monitor CEA-608 closed captions, select this checkbox.
Note: Monitoring CEA-708 Closed Captions requires using a version 14.4 or newer Broadcaster. | | Monitor CEA-708 Closed Captions | If you would like to monitor CEA-708 closed captions, select this checkbox.
Note: Monitoring 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. | | *WebRTC Playback*
*Disabled (for both Push and Pull)*


| 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. | | *SCTE-35 Manipulation (For Pull)* | | | Enable SCTE-35 Insertion | Select checkbox to enable SCTE-35 Insertion. | | SCTE-35 PID | Set the SCTE-35 PID in which the messages will be inserted. | | Remove Existing SCTE-35 | Remove any existing SCTE-35 messages from the stream. | | Replace with NULL | Replace any existing SCTE-35 messages with NULL. | | Auto-Pull Latency \[ms] | Specify the desired latency for auto-pull actions. (Default: 1,000 ms) | | *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/recovery notifications for this Source upon initial configuration. | | ***Error Concealment*** | | | Enable Error Concealment | Select this checkbox to enable the error concealment mechanisms listed below to correct transport stream for downstream IRDs. | | Continuous Timeline | Corrects errors that are related to timeline jumps in the source. This mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input. | | Replace Frames | If there are frames with CC errors, it replaces them with skip frames (inserts the last good frame received in place of missing ones). This solves issues such as an IRD that lost synchronization when it received broken frames. This mechanism also creates a variant of the input (doubling the input). | | Renumber CC | encapsulation. When there are CC errors in TR101 analysis it means that the counter has a gap due to the lost frames. This mechanism can re-write the CC counter for the downstream devices, so they will see a continuous increase of the counter. | | Delay (ms) | Enter the delay that the Error Concealment adds to the stream in miliseconds. Error Concealment needs to buffer the stream to analyze it. One second is a reasonable value. Lower values may cause the Error Concealment to not be able to fix some of the frames. | | CBR Padding (kbps) | Enter a value for the rate at which padding will be added to maintain a specific output transport bitrate. For example, if you have a video bitrate at 5000 kbps or that varies from 3000-5000 kbps and audio at 64 kbps, total bitrate will be max 5064 kbps or min 3064 kbps. With CBR padding set at 6000 kbps, 6000 kbps is being delivered downstream at all times, ensuring a consistent bitrate. | | PCR Interval (ms) | Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. Options include:
* ATSC standard - 100 ms * DVB standard - 40 ms | | ***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+) | | 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 | Specify the maximum transmission unit (largest data packet that a network-connected device will accept) in bytes for the Auto Pull. | | Auto-Pull Billing Password
| Enter the password that corresponds to this auto-pull billing code. | | 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. | | Apply Input NIC selection to network device | Select this checkbox to apply Input NIC selection to the network device. | | 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 for empty audio streams to prevent false warnings - enter a comma-delimited list of PID numbers that should not be monitored for null content. | [title] Adding a Source – Failover [path] ZEN Master/ZEN Master User Guide/Sources/Adding ZEN Master Sources/ You can combine two or more Sources to create a unified* Failover* Source. Whenever one of the Sources is disrupted (or interrupted completely), ZEN Master will seamlessly merge the streams, retrieving the missing packets from the alternate Source. The streams can be merged using one of the following methods: - **Stream Switch - **ZEN Master treats the streams as different and does not try to merge them. If packets are missing from one stream, ZEN Master will switch to the alternate stream. - **Content Hitless Merge **- if the Sources do not have RTP headers, Zixi will merge the streams using the MPEG-TS payload content itself. This method uses Zixi's patented DNA like sequencing algorithm to fill in the missing packets. - **SMPTE 2022-7 Hitless **- if the Sources use RTP, and the RTP headers were maintained, Zixi can use the SMPTE 2022-7 to compare and merge the two streams. This option uses the sequence and the timestamp in the packets to compare which packets are missing, providing optimal results. :::hint{type="info"} * If the streams are not identical, the failover process will not be seamless and may take up to a second. * You can manually select one of the streams to be active by clicking on the *Lock* button in the *Sources* tab of the *Source Details* page. The Source designated as Locked will be used whenever it is available until you click *Unlock*. ::: Zero Bitrate and Offline events always trigger failover. For v15+ Broadcasters, you can configure additional rules to failover for other content quality errors (e.g. P1 Transport Events, Frozen Video etc.) that occur beyond a specified threshold. The following procedure describes how to add a Failover Source in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. ### To add a Failover Source: :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Source selection** window is displayed. ![Failover Source Settings](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-xUm7I3JF9NhYlS_84YssJ-20250805-174701.png) ::: :::WorkflowBlockItem Click on **Failover**. The **Create New Failover** window opens. ![Failover Source Settings](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-xUm7I3JF9NhYlS_84YssJ-20250805-174701.png) ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, enter a unique name to identify this Source in the system. ::: :::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 **Input** section, in the **Sources **field, select two or more Sources that you would like to include in the failover group. :::hint{type="info"} If the selected Sources are not binary identical then there will be a one second delay in the failover to the backup source. ::: As you select sources, they will appear in the table below the selector: ![Selected Sources](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-MvdoEAvnavwHkEcSMrwGU-20250805-181617.png) :::: ::::WorkflowBlockItem For each source, configure the following: - Under **Priority** - to designate a Source as a preferred Source, select the **Preferred** checkbox or to to designate a Source as a Slate, select the **Slate** checkbox. Preferred source take precedence over non-preferred source (i.e., sources that were not marked as preferred). Slate sources are sources that stream slate content, which is content that can be served when there are gaps in a live stream ad break that cannot be filled with a dynamically-served ad. - Under **Min Bitrate (Kbps) - **specify the bitrate threshold level in Kbps to perform the failover (i.e., if the bitrate drops under the threshold the failover will take place). :::hint{type="info"} If you would like to remove a selected Source, click on the **-** button next to the Source. ::: :::: :::WorkflowBlockItem In the **Max Bitrate** selector, leave the selection at Auto to let ZEN Master calculate the max bitrate for the failover source using the bitrates of the component sources. Or you can choose a max bitrate from the available options if you prefer. ::: :::WorkflowBlockItem For **Failover Mode**, select the desired mode for failing over/merging the streams. Options are: - **Stream Switch** – ZEN Master treats the streams as different and does not try to merge them. If packets are missing from one stream, ZEN Master will switch to the alternate stream. If the payload is not binary identical it will fall back to Stream Switch. - **Content Hitless** - if the Sources do not have RTP headers, Zixi will merge the streams using the MPEG-TS payload content itself. This method uses Zixi's patented DNA like sequencing algorithm to fill in the missing packets. - **SMPTE 2022-7 Hitless **- if the Sources use RTP, and the RTP headers were maintained, Zixi can use the SMPTE 2022-7 to compare and merge the two streams. This option uses the sequence and the timestamp in the packets to compare which packets are missing, providing optimal results. ::: ::::WorkflowBlockItem If you have selected the **Content Hitless** or the **SMPTE-2022-7 Hitless** option, in the **Merge Search Window \[ms] **field, enter the time frame for which the system will search for the relevant packets in a matching stream. (Default: 1000) :::hint{type="info"} - If there is a latency difference between the streams, the *Search Window* value should be higher than the latency difference between the streams. - If *Merge Mode* is Disabled, the time period specified in the *Search Window* field defines how long the stream will wait for packet before attempting to switch between streams. ::: :::: :::WorkflowBlockItem If you have selected the **Stream Switch** option, in the **Zero Bitrate/Offline Detection Window \[ms]** field, enter the time frame with zero bitrate or offline state after which the system will perform the failover ::: ::::WorkflowBlockItem **Failover Rules **allow you to set rules for what type of error and how often they occur to change to the failover stream. If you would like to change the rules, use the following procedure (supported for Broadcasters v15+): 1. Select the Checkbox next to the error for which you would like to change the error rules. Options are: *P1 Transport Errors, Frozen Video, Blank Picture,* *Silent Audio, and Low Bitrate*. (*Zero Bitrate/Offline* is set as selected on a fixed basis.) 2. Set the parameters for: - **Sample Duration** - the duration (in seconds) of the window of each sample. - **Samples** - the number of samples that you check in each sampling. - **Samples Threshold** - the number of error results (within a sampling) that trigger the failover. - **PID** - scopes the rule to a specific PID in the transport stream (e.g., if you have multiple audio programs it will only apply the rule to the specified one) :::hint{type="info"} For example, if you set Sample Duration=10, Samples=6, Samples Threshold=2: then if during a 60 second time period an error occurs during 2 out of the 6 ten-second windows, failover will be triggered. ::: :::: :::WorkflowBlockItem In the **Configuration** section, in the **Ingest Cluster** field, select from the drop-down list the Ingest Cluster on which the Sources that you would like to group together are located. ::: :::WorkflowBlockItem In the **Target Broadcaster/s** field, specify which Broadcaster/s within the cluster on which ZEN Master can deploy the source. Either select a specific broadcaster (for Manual clusters) 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*. ::: :::WorkflowBlockItem Select the **Alert on PID changes** checkbox if you would like to generate email notifications whenever a PID change is detected. ::: ::::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 Additional SCTE-35 options are available when you expand the **SCTE-35 Manipulation** section: ![SCTE-35 Manipulation](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/FxvVWM-bhpg9ZdVYW_LCl-20251104-153319.png) Here you can: - Enable SCTE-35 Manipulation - Specify the length of a search window for a NULL packet for SCTE-35 intertion - Set the SCTE-35 PID - Remove any existing SCTE-35 messages from the stream See the **Parameters Table** below for an explanation of these options. ::: :::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 closed captions, select **Monitor CEA-608 **checkbox**.** :::hint{type="info"} Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: If you would like to monitor CEA-708 closed captions, select **Monitor CEA-708 **checkbox**.** :::hint{type="info"} Monitoring CEA-708 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: :::: ::::WorkflowBlockItem If you would like to disable auto-pull, select the **Disable Auto-Pull** 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 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 Under **Error Concealment,** click the Enable Error Concealment checkbox to enable the following error concealment mechanisms that can correct transaport stream for downstream IRDs: :::Paragraph{indent="1"} 1\. **Continuous Timeline** - corrects errors that are related to timeline jumps in the source. This mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input. ::: :::Paragraph{indent="1"} 2\. **Replace Frames** - If there are frames with CC errors, it replaces them with skip frames (inserts the last good frame received in place of missing ones). This solves issues such as an IRD that lost synchronization when it received broken frames. This mechanism also creates a variant of the input (doubling the input). ::: :::Paragraph{indent="1"} 3\. **Renumber CC **- The Continuity Counter is part of the TS encapsulation. When there are CC errors in TR101 analysis it means that the counter has a gap due to the lost frames. This mechanism can re-write the CC counter for the downstream devices, so they will see a continuous increase of the counter. ::: :::Paragraph{indent="1"} 4\. **Delay (ms) **- Enter the delay that the Error Concealment adds to the stream in miliseconds. Error Concealment needs to buffer the stream to analyze it. One second is a reasonable value. Lower values may cause the Error Concealment to not be able to fix some of the frames. ::: :::Paragraph{indent="1"} 5\. **CBR Padding** - enter a value for the rate at which padding will be added to maintain a specific output transport bitrate. For example, if you have a video bitrate at 5000 kbps or that varies from 3000-5000 kbps and audio at 64 kbps, total bitrate will be max 5064 kbps or min 3064 kbps. With CBR padding set at 6000 kbps, 6000 kbps is being delivered downstream at all times, ensuring a consistent bitrate. ::: :::Paragraph{indent="1"} 6.** PCR Interval** - Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. This depends on standard used by downstream encoders or decoders. Options include: ::: :::Paragraph{listStyleType="disc" indent="2"} ATSC standard - 100 ms ::: :::Paragraph{listStyleType="disc" indent="2"} DVB standard - 40 ms ::: 7. **Remux Buffer Size** - Specify the time added for remuxing the stream (default: 2500 ms). 8. **Smoothing** - Time added for smoothing a bursty stream - adds to latency, but produces a smoother output. See [Improving Stream Resiliency: Error Correction and Concealment](docId:9_OLo1Argk_2aDoSHYFBb) for more information. ![Error Concealment Options](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/jEyT42FS_YflpTNxqCc9Q_zm-error-concealment-options.png) :::: :::WorkflowBlockItem If you would like to adjust the advanced settings, click **Advanced**. The Advanced settings fields are displayed: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/icL6v2i58Cjt6FFvidUg6_fo-source-advanced.png) ::: :::WorkflowBlockItem If you would like to track usage for this Source, enter your **Billing Code** details. See [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ) . ::: :::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 Click **Save**. ::: ::::: ### Hitless Failover Source Configuration Parameters Table | **Parameter** | **Description** | | ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | ***Info*** | | | Name | Specify a name for the Failover 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*** | | | Sources | Select from the drop-down list two or more binary identical Sources that you would like to include in the failover group.
If the selected Sources are not binary identical then there will be a one second delay in the failover to the backup Source.
If you would like to designate a Source as a preferred Source, select the **Preferred** checkbox.
If you would like to designate a Source as part of the Slate, select the **Slate** checkbox.
In the **Min. Bitrate\[kbps]** field, specify the bitrate threshold level in Kbps to perform the failover (i.e., if the bitrate drops under the threshold the failover will take place).
**Note: **If you would like to remove a selected Source, click on the button next to the Source. | | Failover Mode | Select the desired mode for failing over/merging the streams. Options are:
* **Stream Switch – **ZEN Master treats the streams as different and does not try to merge them. If packets are missing from one stream, ZEN Master will switch to the alternate stream. If the payload is not binary identical it will fall back to Stream Switch. * **Content Hitless** - if the Sources do not have RTP headers, Zixi will merge the streams using the MPEG-TS payload content itself. This method uses Zixi's patented DNA like sequencing algorithm to fill in the missing packets. * **SMPTE 2022-7 Hitless **- if the Sources use RTP, and the RTP headers were maintained, Zixi can use the SMPTE 2022-7 to compare and merge the two streams. This option uses the sequence and the timestamp in the packets to compare which packets are missing, providing optimal results. | | Merge Search Window \[ms] | Specify the time frame for which the system will search for the relevant packets in a matching stream. (Default: 1000)
Note: If there is a latency difference between the streams, the Search Window value should be higher than the latency difference between the streams. | | Zero Bitrate/Offline Detection Window \[ms] (for Stream Switch option) | Enter the time frame with zero bitrate or offline state after which the system will perform the failover. | | Failover Rules | **Failover Rules** allow you to set rules for what type of error and how often they occur to change to the failover stream. If you would like to change the rules, use the following procedure (supported for Broadcasters v15+):
1) Select the checkbox next to the error for which you would like to change the error rules. Options are: *P1 Transport Errors*, *Frozen Video*, *Blank Picture,* *Silent Audio, and Low Bitrate*. 2) Set the parameters for: - **Sample Duration** – the duration (in seconds) of the window of each sample. - **Samples** – the number of samples that you check in each sampling. - **Samples Threshold **– the number of error results (within a sampling) that trigger the failover. - **PID** - scopes the rule to a specific PID in the transport stream (e.g., if you have multiple audio programs it will only apply the rule to the specified one)
Note: For example, if you set Sample Duration=10, Samples=6, Samples Threshold=2: then if during a 60 second time period an error occurs during 2 out of the 6 ten-second windows, failover will be triggered. | | ***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. | | Alert on PID changes | If you would like to generate email notifications whenever a PID change is detected, select this checkbox. | | Preserve RTP Headers | Select this checkbox to preserve the RTP headers (which include the timestamps and sequences) and propagate them the output. | | Log SCTE-35 | If you would like to log SCTE-35 markers for this stream, select this checkbox.
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. | | 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 desired latency for auto-pull actions. (Default: 1,000 ms) | | 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. | | ***SCTE-35 Manipulation *** | | | Enable SCTE-35 Manipulation | Select checkbox to enable SCTE-35 Manipulation. | | SCTE-35 PID | Set the SCTE-35 PID in which the messages will be inserted. | | Remove Existing SCTE-35 | Remove any existing SCTE-35 messages from the stream. | | NULL Packet Search Window (ms) | Look for a NULL packet 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 | | *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/recovery notifications for this Source upon initial configuration. | | ***Error Concealment*** | | | Enable Error Concealment | Select this checkbox to enable the error concealment mechanisms listed below to correct transport stream for downstream IRDs. | | Continuous Timeline | Corrects errors that are related to timeline jumps in the source. This mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input. | | Replace Frames | If there are frames with CC errors, it replaces them with skip frames (inserts the last good frame received in place of missing ones). This solves issues such as an IRD that lost synchronization when it received broken frames. This mechanism also creates a variant of the input (doubling the input). | | Renumber CC | encapsulation. When there are CC errors in TR101 analysis it means that the counter has a gap due to the lost frames. This mechanism can re-write the CC counter for the downstream devices, so they will see a continuous increase of the counter. | | Delay (ms) | Enter the delay that the Error Concealment adds to the stream in miliseconds. Error Concealment needs to buffer the stream to analyze it. One second is a reasonable value. Lower values may cause the Error Concealment to not be able to fix some of the frames. | | CBR Padding (kbps) | Enter a value for the rate at which padding will be added to maintain a specific output transport bitrate. For example, if you have a video bitrate at 5000 kbps or that varies from 3000-5000 kbps and audio at 64 kbps, total bitrate will be max 5064 kbps or min 3064 kbps. With CBR padding set at 6000 kbps, 6000 kbps is being delivered downstream at all times, ensuring a consistent bitrate. | | PCR Interval (ms) | Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. Options include:
* ATSC standard - 100 ms * DVB standard - 40 ms | | ***Advanced*** | | | Billing Codes | If you would like to track usage for this Source, enter you **Billing Code** details, see . (Supported for Broadcasters v14.8+) | | 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 | Specify the maximum transmission unit (largest data packet that a network-connected device will accept) in bytes for the Auto Pull. | | Auto- Pull Billing Password | Enter the password that corresponds to this auto-pull billing code. | | 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. | | 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 (sec) | 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 for empty audio streams to prevent false warnings - enter a comma-delimited list of PID numbers that should not be monitored for null content. | [title] Broadcaster History [path] ZEN Master/ZEN Master User Guide/Broadcasters/Viewing Existing Clusters/Viewing Existing Broadcasters/ The History section shows a graphic display of the Broadcaster's activity and performance over time. You can create an **Incident** to group together related network failures and see network data for the relevant time period. This is done by selecting a time range on a graph and clicking the **Open Incident** button. For more information about Incidents, see [Incidents](docId\:KM0I5TNPzuO-ygFv6QcVq) . ![Broadcaster History](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/xOy3eQ9nN8DC7bFR0l1ZD_image.png) Data is shown on separate line graphs for each topic that is relevant for the selected Broadcaster. Click on the section headings to expand/collapse the graph display. Each graph shows color coded lines indicating the events that occurred over time. A key indicating the colors used to represent various types of data is shown below each graph. The graphs have the following functionality: - Set the time range of the display either by selecting one of the preset time ranges or by entering a custom time range. (Default: *Last 6 hr*) - Manually refresh graph data or set the automatic refresh frequency. - Hover over a point on the graph to show the total values for that time. - Click and drag the cursor over a time range to zoom in on that time range. - Double click on the graph to zoom out on the graph (i.e. expand the time range). - Click on the title of a data element in the key to display only that element. :::hint{type="info"} * The granularity of the graph depends on the zoom level. Most graphs can zoom in to a resolution of one datapoint per minute. * For broadcasters v14.1+, data is gathered at 5 second intervals. This enables ZEN Master to show min. and max. values for RTT, jitter and bitrates based on 5 second intervals within a given data point. ::: The following sections describe the various graphs that are shown in the History tab. - [Broadcaster History System](docId\:ApXSmLPMsJh0WpLzvcMuX) - [Broadcaster History Network](docId\:P7NS43OoqdX9cU38pY0K9) - [Broadcaster History UDP](docId\:sPyXQm_w2_bxkHYSTIDPf) [title] Adding a Source - PID Mapping [path] ZEN Master/ZEN Master User Guide/Sources/Adding ZEN Master Sources/ You can apply mapping to Sources in ZEN Master (for v14+ Broadcasters). This enables you to ensure that the PIDs will have the desired values when they arrive downstream at the Target. This is done by first creating a PID Mapping profile which specifies which PIDs will be processed and defining how they will be handled. Once you have created a PID Mapping profile you can apply it to a Source in ZEN Master. This section explains how to create a new PID Mapping Source *from an existing Source*. This enables you to maintain the original Source with the original PID values. You can then set up multiple Sources with different PID mappings so that you can send differently mapped streams to different Targets. Alternatively, you can apply PID Mapping to a standard Source in ZEN Master (Zixi, UDP/RTP, SRT or RIST) by selecting the PID Mapping profile during the Source configuration. This causes the same mapped stream to be sent to all Targets that receive that Source. The following procedure describes how to add a PID Mapping Source in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. ## To add a PID Mapping Source: :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Source selection** window is displayed. ![Create Source Options](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-3mXDQJHXUppSRZJSBYBnR-20250805-132303.png) ::: :::WorkflowBlockItem Click on **Zixi**. The **Create New PID Mapping** window opens. ![New PID Mapping Source](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/pNkLUaGKJQ3BX57n0ZB59-20251104-154631.png) ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, enter a unique name to identify this Source in the system. ::: :::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 **Input** section, in the **Source** field, select from the drop-down list the existing Source from which you want to create the new PID Mapping Source. ::: :::WorkflowBlockItem In the **Configuration** section, 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** PID Mapping Profile** field, select from the drop-down list the PID Mapping profile you would like to use. ::: :::WorkflowBlockItem If you would like to generate email notifications whenever a PID change is detected, select the **Alert on PID changes **checkbox. ::: ::::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 closed captions, select **Monitor CEA-608 **checkbox**.** :::hint{type="info"} Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: If you would like to monitor CEA-708 closed captions, select **Monitor CEA-708 **checkbox**.** :::hint{type="info"} Monitoring CEA-708 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: :::: ::::WorkflowBlockItem If you would like to disable auto-pull, select the **Disable Auto-Pull** 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. (Default: 1000 ms) ::: ::::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 Additional SCTE-35 options are available when you expand the **SCTE-35 Manipulation** section: ![SCTE-35 Manipulations](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/FxvVWM-bhpg9ZdVYW_LCl-20251104-153319.png) **Here you can:** - Enable SCTE-35 Manipulation - Specify the length of a search window for a NULL packet for SCTE-35 intertion - Set the SCTE-35 PID - Remove any existing SCTE-35 messages from the stream See the **Parameters Table** below for an explanation of these options. ::: :::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 Under **Error Concealment,** click the Enable Error Concealment checkbox to enable the following error concealment mechanisms that can correct transaport stream for downstream IRDs: :::Paragraph{indent="1"} 1\. **Continuous Timeline** - corrects errors that are related to timeline jumps in the source. This mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input. ::: :::Paragraph{indent="1"} 2\. **Replace Frames** - If there are frames with CC errors, it replaces them with skip frames (inserts the last good frame received in place of missing ones). This solves issues such as an IRD that lost synchronization when it received broken frames. This mechanism also creates a variant of the input (doubling the input). ::: :::Paragraph{indent="1"} 3\. **Renumber CC **- The Continuity Counter is part of the TS encapsulation. When there are CC errors in TR101 analysis it means that the counter has a gap due to the lost frames. This mechanism can re-write the CC counter for the downstream devices, so they will see a continuous increase of the counter. ::: :::Paragraph{indent="1"} 4\. **Delay (ms) **- Enter the delay that the Error Concealment adds to the stream in miliseconds. Error Concealment needs to buffer the stream to analyze it. One second is a reasonable value. Lower values may cause the Error Concealment to not be able to fix some of the frames. ::: :::Paragraph{indent="1"} 5\. **CBR Padding** - enter a value for the rate at which padding will be added to maintain a specific output transport bitrate. For example, if you have a video bitrate at 5000 kbps or that varies from 3000-5000 kbps and audio at 64 kbps, total bitrate will be max 5064 kbps or min 3064 kbps. With CBR padding set at 6000 kbps, 6000 kbps is being delivered downstream at all times, ensuring a consistent bitrate. ::: :::Paragraph{indent="1"} 6.** PCR Interval** - Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. This depends on standard used by downstream encoders or decoders. Options include: ::: :::Paragraph{listStyleType="disc" indent="2"} ATSC standard - 100 ms ::: :::Paragraph{listStyleType="disc" indent="2"} DVB standard - 40 ms ::: 7. **Remux Buffer Size** - Specify the time added for remuxing the stream (default: 2500 ms). 8. **Smoothing** - Time added for smoothing a bursty stream - adds to latency, but produces a smoother output. See [Improving Stream Resiliency: Error Correction and Concealment](docId:9_OLo1Argk_2aDoSHYFBb) for more information. ![Error Concealment Options](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/jEyT42FS_YflpTNxqCc9Q_zm-error-concealment-options.png) :::: :::WorkflowBlockItem If you would like to adjust the advanced settings, click **Advanced**. The **Advanced** settings fields are displayed: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/GSBU0rggYHfO7PFAPoPUg_pif-mapping-source-advanced.png) ::: :::WorkflowBlockItem If you would like to track usage for this Source, enter your **Billing Code** details. See [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ). ::: :::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 apply Input NIC selection to the network device, select the **Apply Input NIC selection to network device** checkbox. ::: :::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 Click **Save**. ::: ::::: - ATSC standard - 100 ms - DVB standard - 40 ms ## PID Mapping Source Configuration Parameters Table | **Parameter** | **Description** | | ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** |
| | Name | Specify a name for the PID Mapping 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*** |
| | Source | Select from the drop-down list the Source that the PID Mapping Source is based on. | | ***Configuration*** |
| | Ingest Cluster | Select from the drop-down list one of the available Ingest Clusters as the destination for the Source. | | Target Broadcaster/s | 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.*
Note: For managed clusters, it is not recommended to select a specific Broadcaster, as the Broadcaster’s availability may not remain stable. | | Input NIC | If you have selected a specific Target Broadcaster, you can select a specific input NIC from the drop-down list or select **Any**. | | PID Mapping Profile | Select the desired PID Mapping profile from the drop-down list.
To create a new PID Mapping Profile, see [Adding PID Mapping Profiles](docId\:gFTCaYurPL7DInoUyd14z) . | | Alert on PID changes | If you would like to generate email notifications whenever a PID change is detected, select this checkbox. | | 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 | Disables the Source thumbnail from appearing in the Sources list and other places. Disabling thumbnail may improve system performance. | | Monitor CEA-608 Closed Captions
| If you would like to monitor CEA-608 closed captions, select this checkbox.
Note**:** Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. | | Monitor CEA-708 Closed Captions | If you would like to monitor CEA-708 closed captions, select this checkbox.
Note**:** Monitoring 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 desired latency for auto-pull actions. (Default: 1,000 ms) | | 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 passsed 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. | | ***SCTE-35 Manipulation *** | | | Enable SCTE-35 Manipulation | Select checkbox to enable SCTE-35 Manipulation. | | SCTE-35 PID | Set the SCTE-35 PID in which the messages will be inserted. | | Remove Existing SCTE-35 | Remove any existing SCTE-35 messages from the stream. | | NULL Packet Search Window (ms) | Look for a NULL packet 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 | | ***Error Concealment*** | | | Enable Error Concealment | Select this checkbox to enable the error concealment mechanisms listed below to correct transport stream for downstream IRDs. | | Continuous Timeline | Corrects errors that are related to timeline jumps in the source. This mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input. | | Replace Frames | If there are frames with CC errors, it replaces them with skip frames (inserts the last good frame received in place of missing ones). This solves issues such as an IRD that lost synchronization when it received broken frames. This mechanism also creates a variant of the input (doubling the input). | | Renumber CC | encapsulation. When there are CC errors in TR101 analysis it means that the counter has a gap due to the lost frames. This mechanism can re-write the CC counter for the downstream devices, so they will see a continuous increase of the counter. | | Delay (ms) | Enter the delay that the Error Concealment adds to the stream in miliseconds. Error Concealment needs to buffer the stream to analyze it. One second is a reasonable value. Lower values may cause the Error Concealment to not be able to fix some of the frames. | | CBR Padding (kbps) | Enter a value for the rate at which padding will be added to maintain a specific output transport bitrate. For example, if you have a video bitrate at 5000 kbps or that varies from 3000-5000 kbps and audio at 64 kbps, total bitrate will be max 5064 kbps or min 3064 kbps. With CBR padding set at 6000 kbps, 6000 kbps is being delivered downstream at all times, ensuring a consistent bitrate. | | PCR Interval (ms) | Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. Options include:
* ATSC standard - 100 ms * DVB standard - 40 ms | | ***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/recovery 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 . (Supported for Broadcasters v14.8+) | | 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
| Specify the maximum transmission unit (largest data packet that a network-connected device will accept) in bytes for the Auto Pull. | | 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. | | Apply Input NIC selection to network device | Select this checkbox to apply Input NIC selection to the network device. | | 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 for empty audio streams to prevent false warnings - enter a comma-delimited list of PID numbers that should not be monitored for null content. | [title] Adding a RIST-protocol MediaConnect Source [path] ZEN Master/ZEN Master User Guide/Sources/Adding AWS Media Sources/Adding an AWS MediaConnect Source/ **To create a RIST MediaConnect Source:** ::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The Create New Source window is displayed. ![Create New Source window](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/AxSEVtTg03J7Up0wQFdjQ_image.png) ::: :::WorkflowBlockItem Under **AWS Media**, click on **AWS MediaConnect**. The Create New AWS Media Source window opens. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-z4gk_F6RpooN7ZEEF2Fy5-20250706-130410.png) ::: :::WorkflowBlockItem In the **Info **section, in the **Name** field, type a logical name for the 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. *Events Profiles* consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. ::: :::WorkflowBlockItem In the **Input** section, under **Protocol**, select the **RIST** radio button.  ::: :::WorkflowBlockItem In the **Ingest Port** field, enter the port that the Flow will listen on for incoming content. ::: :::WorkflowBlockItem In the **Max Bitrate** field, enter the maximum bitrate to be used on this NIC. ::: :::WorkflowBlockItem In the **Latency **\[ms] field, select the latency time for the stream (default 4000). ::: :::WorkflowBlockItem You are required by MediaConnect to enter a valid **Whitelist CIDR block**. The whitelist CIDR block is a range of IP addresses that should be allowed to contribute content to your source. These IP addresses must be in the form of a Classless Inter-Domain Routing block. For example, 10.0.0.0/16. Through source needs to be in the range covered by this CIDR block. Any IP address with this range is allowed to send content to this flow. ::: :::WorkflowBlockItem In the **Initial State** section, select the **Muted** checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. You can Unmute the Source at any time. ::: :::WorkflowBlockItem Click **Save**. ::: :::: **Parameters Table** | **Parameter** | **Description** | | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the AWS Media 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. | | ***Input*** | | | Protocol | To create a RIST protocol Input AWS Media Source, verify that RIST is selected. | | Ingest Port | Enter the port that the Flow will listen on for incoming content. | | Max Bitrate | Select from the drop-down list the maximum bitrate for this Source.
Make sure that the value is greater than the max bitrate for the input. The default is set automatically based on the current bitrate of the input. | | Latency (ms) | Select the latency time for the stream (default 4000). | | Whitelist CIDR Block | Specify the CIDR for the range of IPs that you would like to allow to contribute content to this Source.
You are required by MediaConnect to enter a valid Whitelist CIDR block. | | ***Initial State*** | | | Muted | Select this checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. | [title] Broadcaster Details [path] ZEN Master/ZEN Master User Guide/Broadcasters/Viewing Existing Clusters/Viewing Existing Broadcasters/ The **Details Pane** includes the following details (explanations are included in the table below): ![Broadcaster Details Pane](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/fLP5bP5Rf_N281Imf87gH-20251107-151925.png) | Parameter | Description | | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | API Credentials | Click Show to display the API credentials between the ZEN Master and the Broadcaster. Click Copy Password to copy the password. | | Open | Click to access the Zixi Broadcaster UI. | | Public IP | The public IP address of the Broadcaster. | | Private IP | The public IP address of the Broadcaster. | | Hostname | The name of the Host. | | Host ID | The Host ID of the Broadcaster. | | Instance Id | The cloud instance type. | | Instance Type | The cloud instance type. | | Primary | Specifies whether the Broadcaster is a Primary Broadcaster or not. | | Version | The software version of the Broadcaster. | | Activation Key | Click License Details to view the license status. | | System Logs | Click Download Logs to download Broadcaster system logs. | | Created At | The date and time in which the Broadcaster object was defined in ZEN Master. | | Location | The location of the Broadcaster. By default, the location is determined automatically based on the Broadcaster's IP. However, it is possible to specify another location during configuration. | | Network | The Network in which the Broadcaster is located. The Networks are discovered automatically by ZEN Master using IP-to-location method. A network is defined as an ASN from a specific country and region/state. | | AgentZ | Indicates whether AgentZ has been installed for this Broadcaster. Agent Z is a Sidecar tool that sits on a Zixi Broadcaster, it acquires the system health data and other statistics locally and pushes it to ZEN Master. By enabling this option, ZEN Master will automatically install AgentZ on any existing and future Broadcasters connected to the Cluster. The feature is off by default. Due to AgentZ installation requiring a restart, ZEN Master will not auto-install AgentZ on a Broadcaster that already contains any inputs to avoid disturbing active streams. | | Protocol | Indicates the Protocols used on this Broadcaster, the ports used for each protocol and their status:
* Green - OK * Red- missing * Gray - not used by Zen Master | | DTLS Certificate | Indicates whether the DTLS certificate has been installed and its expiration date. | | Update Broadcaster Configuration | Click to update Authorization, DTLS and Ports configuration on the Broadcaster. | [title] Source History [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/ The History section shows a graphic display of the Source's activity and performance over time. You can create an **Incident** to group together related network failures and see network data for the relevant time period. This is done by selecting a time range on a graph and clicking the **Open Incident** button. For more information about Incidents, see [Incidents](docId\:KM0I5TNPzuO-ygFv6QcVq) . ![Source History Graphs](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/fJlblyiOncl1wgruCvyUc_image.png) Data is shown on separate line graphs for each topic that is relevant for the selected Source. Click on the section headings to expand/collapse the graph display. Each graph shows color coded lines indicating the events that occurred over time. A key indicating the colors used to represent various types of data is shown below each graph. The graphs have the following functionality: - Set the time range of the display either by selecting one of the preset time ranges or by entering a custom time range. (Default: *Last 6 hr*) :::hint{type="info"} One year of history is saved in the ZEN Master database even though the graphs show larger timeframes. Contact Zixi if you require more than one year of history. ::: - Manually refresh graph data or set the automatic refresh frequency. - Hover over a point on the graph to show the total values for that time. - Click and drag the cursor over a time range to zoom in on that time range. - Double click on the graph to zoom out on the graph (i.e. expand the time range). - Click on the title of a data element in the key to display only that element. :::hint{type="info"} * ZEN Master treats all graphs as a single component so that the zoom time range set for one graph is automatically applied to all graphs on that screen. Similarly, when you hover over a point on one graph, the tool-tip values are shown for the same point in time on all of the graphs. * The granularity of the graph depends on the zoom level. Most graphs can zoom in to a resolution of one datapoint per minute. * For broadcasters v14.1+, data is gathered at 5 second intervals. This enables ZEN Master to show min. and max. values for RTT, jitter and bitrates based on 5 second intervals within a given datapoint. ::: The following sections describe the various graphs that are shown in the History tab. - [Source History Content Analysis](docId\:PVW9iCpg49eu99XFyYwR9) - [Source History SCTE-35](docId:-jHt7KXDb6sgzZoGrJBx6) - [Source History Network](docId\:lZHvDL4YY6lrVaWTZxIXZ) - [Source History Failover](docId:_aahwGkV-snVZt_BcFTo0) - [Source History Network Bitrate](docId\:zkdlj0o42fLGoP4SaOxZh) - [Source History Elementary Stream Bitrates](docId\:hRLyMz9PPexP8sZ8eMAvs) - [Source History Frame Delivery %](docId\:Fl3UJtwawPGBeTwCIqj0E) - [Source History Encoding Quality ePSNR](docId\:USjyWgfUK7rbD0hVqd0ZA) - [Source History Packet Timing](docId\:QYUvH4qRp2xmnyJY_k81J) - [Source History Bonding (for Network Bonding Sources)](docId\:rPApl0NvWWqgFZrRs3vY3) - [Source History Traceroute](docId\:A3FAy5SZOHg7D_ApiMJLb) - [Source History Encoding Quality eVAMF](docId:6-849Y__KOzqGDGr74Egn) [title] Cloning a Source [path] ZEN Master/ZEN Master User Guide/Sources/ If you would like to create a new Source with properties similar to those of an existing Source, you can use the *Clone* feature to simplify the process. **To Clone a Source:** ::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Select the Source that you would like to Clone (i.e. the Source that is already configured in ZEN Master which has settings similar to those that you would like to set for the new Source that you are creating). ::: :::WorkflowBlockItem Click on the three dots on the **More **Menu. Click **Clone**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/3Pu05EPV-bYvlHp4oKAmV-20260129-101116.jpg) The **Clone Source **window is displayed with all fields other than **Name** populated with the configuration data of the original Source. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/4foY1RY536yYYIHVetgXx-20260129-101335.jpg) ::: :::WorkflowBlockItem In the **Name** field, enter the name of the new Source. ::: :::WorkflowBlockItem Change any of the fields that you would like to configure differently than the original Source. See the above sections that describe how to create new Sources of various types. ::: :::WorkflowBlockItem Click **Save**. The Source is created. ::: :::: [title] Sharing a Source [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/Actions on a Source/ The share feature allows you to share a link to a source object thumbnail page by sending a URL link. The link can be accessed by external users, without requiring them to have a ZEN Master account. This feature can be used to share visibility into a source with users that need to view a source, such as live event producers, service customers, external department, 3rd parties, and others. The link is temporary and can be configured to begin and end at specified times. After creating the link, its details will appear in the **Shared** tab of the source. **To Share a Source:** ::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Select the Source that you would like to share. ::: :::WorkflowBlockItem When hovering on the three dots, select **Share**. The **Share Source** window is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/BtLMjT1j12gTIgnJGUnY6_image.png" size="60" width="448" height="319" position="flex-start" alt="Share Source window" darkWidth="448" darkHeight="319" showCaption="false"} ::: :::WorkflowBlockItem In the **Name** field, enter the name for the link. ::: :::WorkflowBlockItem Specify a **Start /End Time**. ::: :::WorkflowBlockItem Click **Create Link**. The link and password details are displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/C19rVBE93F311c30HsfDS_image.png" size="54" width="448" height="419" position="flex-start" alt=" link and password details" darkWidth="448" darkHeight="419" showCaption="false"} ::: :::WorkflowBlockItem Click the **copy** button on the link and password and send them to the recipients. Anyone with this link and password can view the shared page until it expires. This is the only time that the shared page link can be copied, If you lose the link, create a new one and make the old inactive. ::: :::: **To Regenerate a Shared Source Password:** ::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Select the Source that you have shared. ::: :::WorkflowBlockItem In the **Shared** tab, under **Actions**, click the **Regenerate Password** icon. When generating a new password, the active users will be logged out and required to enter the new password. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-xutIYMRYcYUDwYQcykY03-20250429-143327.png) ::: :::WorkflowBlockItem Click the **Regenerate password** button. ::: :::WorkflowBlockItem Click the **Copy** button to copy the regenerated password. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-NLR-rsQNq111U5lGGhcn0-20250429-143509.png" size="56" width="449" height="213" position="center" showCaption="false"} ::: :::: [title] Connecting the Zixi Broadcaster (Zixi Broadcaster UI – For Manual) [path] ZEN Master/ZEN Master User Guide/Broadcasters/Creating a Broadcaster Cluster/Adding Broadcasters to a Cluster/Adding a Broadcaster to a Manual Cluster/ For each Zixi Broadcaster instance that has been added to the cluster (for manual management), you will need to configure the connection of the Zixi Broadcaster (using its Zixi Broadcaster UI). This includes configuring the SSH tunnel. You will need an SSH key, which you can create in ZEN Master - see [Configuring SSH Keys](docId\:qXuh0ckZbygbyCRZvjtwS). :::hint{type="info"} Note: for the steps below, you will need to work in both in ZEN Master and in the Broadcaster settings, so it will be useful keep both open in separate browser tabs. ::: **To connect the Zixi Broadcaster:** :::::WorkflowBlock :::WorkflowBlockItem In ZEN Master, in the main navigation, click **Broadcasters **and open the **Broadcasters** tab: ![Broadcasters List](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-ET-rSWnVAgU3C39F28Xqi-20250609-184556.png "Broadcasters List") ::: :::WorkflowBlockItem Click on the Broadcaster that has a **Pending **status to reveal the details: ![Broadcaster Details](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-H5HDwR5PIXAW3pY97JeDR-20250609-184843.png "Broadcaster Details") ::: :::WorkflowBlockItem Click the :FontAwesome[]{icon="fa-solid fa-ellipsis-vertical"} icon in the upper-right corner of the details to reveal the **More Actions** menu: ![3 Dots Icon](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-XzZikx6r7XjorXMB64Zbu-20250609-185807.png) ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-DI6NyqPeqjipjHuddlPpy-20250609-185852.png" size="20" width="420" height="582" position="center" caption="More Actions Menu" alt="More Actions Menu" showCaption="true"} ::: :::WorkflowBlockItem Click :FontAwesome[]{icon="fa-solid fa-gear"} **Config** to open these configuration instructions for the Broadcaster: ![Broadcaster Configuration InStructions](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-ZA2PotRzDTPtCNyNB2So0-20250609-191055.png "Broadcaster Configuration InStructions") ::: :::WorkflowBlockItem At this point, you can simply follow the instructions provided in ZEN Master*. *Also note the :FontAwesome[]{icon="fa-solid fa-clipboard"} icons beside items that you will need to copy and paste items into the Broadcaster settings, and Click the :FontAwesome[]{icon="fa-solid fa-download"} icon to download the SSH certificate you will need later to upload to the Broadcaster. The additional steps below simply add more detail in case you need it. ::: ::::WorkflowBlockItem Open a new browser tab and open the Broadcaster UI (if it is on the machine you are using, you can go to http\://localhost:4444, or if it is remote, to http\://(ip address):4444 (for example: http\://108.225.51.7:4444). Login as **admin.** :::hint{type="info"} The default password is 1234 - for security reasons, you should change this to something more secure. If you do that now, remember that you will need to update the password in the ZEN Master settings for the Broadcaster as well. ::: :::: :::WorkflowBlockItem Go to **Settings** in the main Broadcaster navigation, and click on **SSH Connections**: ![SSH Connection Settings](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-FYI0exS7vpD8I40jwikp3-20250609-193938.png "SSH Connection Settings") ::: :::WorkflowBlockItem Click :FontAwesome[]{icon="fa-solid fa-plus"} **Add Connection **and in the dialog that opens, enter **zixieast.io.zixi.com** in the **Host** field: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-oRrY6i2h-KsaCvWvtKqpS-20250609-194347.png" size="32" width="472" height="344" position="center" caption="Add SSH Connection" alt="Add SSH Connection" showCaption="true"} ::: :::WorkflowBlockItem Click **Edit Credentials** to open the dialog to add your SSH credentials from ZEN Master ::: :::WorkflowBlockItem For the **User**, copy and paste the **User name in Step 4 of the Configuration Instructions in ZEN Master:** ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-e1w6PB9yqmdXaI6V8D0eq-20250609-195438.png" size="38" width="528" height="410" position="center" caption="Connection Credentials" alt="Connection Credentials" showCaption="true"} ::: :::WorkflowBlockItem Click the **Upload Key** button and upload the private key file that you downloaded in Step 5 above. ::: :::WorkflowBlockItem Repeat steps 8-11 for **zixiwest.io.zixi.com** ::: :::WorkflowBlockItem Verify in ZEN Master that the status of the newly configured Broadcaster cluster is *OK*. ![Broadcaster Ok](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-MZHHn2ot3MPx_4TbVogY6-20250610-120152.png "Broadcaster Ok") ::: ::::: Select the new Broadcaster cluster. In the Broadcaster section, verify that the status of the Broadcaster that was added to the cluster has changed from *Pending* to *OK*. [title] Adding a CDI-protocol MediaConnect Source [path] ZEN Master/ZEN Master User Guide/Sources/Adding AWS Media Sources/Adding an AWS MediaConnect Source/ This Source is configured on an **AWS MediaConnect** that serves as the **Ingest Object**. The stream originates from any non-Zixi device or AWS service, which serves as the **Origin**. The stream uses the CDI protocol. The Origin is not managed by ZEN Master. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-JOAWO2Ut8Bg1EsL44EB-E-20250812-143709.png) The following procedure describes how to create a CDI MediaConnect Source. In addition, an explanation of each of the configuration parameters is given in the table below. **To create a CDI MediaConnect Source:** ::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The Create New Source window is displayed. ![Create New Source window](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/AxSEVtTg03J7Up0wQFdjQ_image.png) ::: :::WorkflowBlockItem Under **AWS Media**, click on **AWS MediaConnect**. The Create New AWS Media Source window opens. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-SpaXOvc1mEvyIvxEgU6w1-20250713-113148.png) ::: :::WorkflowBlockItem In the **Info **section, in the **Name** field, type a logical name for the 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. *Events Profiles* consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. ::: :::WorkflowBlockItem In the **Input** section, under **Protocol**, select the **CDI** radio button.  ::: :::WorkflowBlockItem In the **Ingest Port** field, enter the port in the MediaConnect that the Flow will listen on for incoming content. ::: :::WorkflowBlockItem In the **Max sync buffer** field, specify the size of the buffer that will be used to synchronize incoming source data. This value is measured in milliseconds (ms). ::: :::WorkflowBlockItem In the **Initial State** section, select the **Muted** checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. You can Unmute the Source at any time. ::: :::WorkflowBlockItem Click **Save**. ::: :::: **Parameters Table** | **Parameter** | **Description** | | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the AWS Media 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. | | ***Input*** | | | Protocol | To create a CDI protocol Input AWS Media Source, verify that CDI is selected. | | Ingest Port | Enter the port in the MediaConnect that the Flow will listen on for incoming content. | | Max sync buffer | Specify the size of the buffer that will be used to synchronize incoming source data. This value is measured in milliseconds (ms). Default - 200 | | ***Initial State*** | | | Muted | Select this checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. | [title] Broadcaster History CPU and Memory [path] ZEN Master/ZEN Master User Guide/Broadcasters/Viewing Existing Clusters/Viewing Existing Broadcasters/Broadcaster History/ ![CPU and Memory Usage Graphs](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/9f4IEDWRagBzeFmHr7vLY-20260311-212549.png) The Broadcaster CPU and Memory usage graphs are derived by querying the server or VM for the top processes and threads consuming CPU and Memory in the system. These are not graphs that need to be monitored, but rather are provided to help with troubleshooting when problems arise. The items shown in the graphs and list below them are taken from the raw data provided by the system the Broadcaster is running on - longer titles are truncated (indicated by a **+** sign) for the display. If you are troubleshooting an issue and see anamolies in the graphs, you should query the system directly or via SSH using commands similar to the following: ```shell top -H -o %MEM -b -n1 >top_mem.txt top -H -o %CPU -b n1>top_cpu.txt ``` :::hint{type="info"} Note that these are just examples - the exact syntax of the commands will depend on the plaform you are running the Broadcaster on. ::: [title] Adding a Zixi Source – ZEC Push [path] ZEN Master/ZEN Master User Guide/Sources/Adding ZEN Master Sources/ You can add an input from a ZEC to a Broadcaster cluster to be managed as a Source in ZEN. This is done by selecting **Zixi** in the **New Source** menu. In this case, the ZEC is referred to as the **Origin ZEC** which streams to the **Ingest Broadcaster**. ![Zixi Source Diagram](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/2bf6RUZj2k4StF7J9Gawf_image.png) - **Network bonding** -when configuring a Source using a Push stream from a ZEC to 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 Zixi Broadcaster. If you enable Bonding, you need to specify which ZEC Output NICs will used for Bonding. The following procedure describes how to add a ZEC Source in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. ## To add a Zixi Push Source from ZEC: :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The **New Source** selection window is displayed. ![Create Source Options](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-3mXDQJHXUppSRZJSBYBnR-20250805-132303.png) ::: :::WorkflowBlockItem Click on **Zixi**. The **Create Zixi Source** window opens. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/6muW59h10oCowjW-LmwRc_image.png" size="70" width="1408" height="4848" position="center" alt="Create New Zixi Source" darkWidth="1408" darkHeight="4848" showCaption="false"} ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, type a logical name for the ZEC 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). 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** 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.** ::: :::WorkflowBlockItem In the **Input** section, verify under **Mode** that **Push** is selected (default) and not **Pull**, and under **Application** that the **ZEC** radio button is selected (default). ::: :::WorkflowBlockItem In the **ZEC** field, select from the drop-down list one of the available ZECs to be the ZEC that will be the **Origin ZEC.** ::: :::WorkflowBlockItem In the **ZEC Input** field, select the desired input that will be part of the Source from the **Origin ZEC.** ::: :::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 **ZEC Output NIC**s 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: 1. Select the **Bonding** checkbox. 2. 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). 3. For each NIC that is selected you can adjust the following parameters: 1. In the **Max Bitrate** field, enter the maximum bitrate to be used on this NIC. 2. 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 In the **Configuration** section, in the **Ingest Cluster** field, select from the drop-down list one of the available Ingest Clusters as the destination for the Source (i.e., the **Ingest Broadcaster Cluster**). ::: ::::WorkflowBlockItem In the **Target Broadcaster/s** field, specify which Broadcaster/s within the **Ingest Broadcaster 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.* :::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 If you would like to apply a **PID Mapping** profile to this Source, then in the **PID Mapping** 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.** ::: ::::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 in 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.** ::: :::WorkflowBlockItem In the **Public Output** field, if you would like to allow access to the stream directly through a supported player, select **Allow.** ::: :::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](http://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 disable the Source thumbnail from appearing in the Sources list and other places, select the **Hide Thumbnail** option. Disabling thumbnail may improve system performance. ::: ::::WorkflowBlockItem If you would like to monitor CEA-608 or CEA-708 closed captions, select the **Monitor CEA-608 **and/or the** Monitor 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-Pull **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 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 I**nitial 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: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/CKSVt6zXGewuyUjg3Ht0L_zec-push-source-advanced.png) ::: ::::WorkflowBlockItem If you would like to track usage for this Source, enter your **Billing Code** and the **Billing Code** **Password**. See [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ) :::hint{type="warning"} Note that billing codes are **not** supported for **Push Sources** until Broadcaster **v19+**. ::: :::: :::WorkflowBlockItem Click the **Validate Billing Code** button if you want to verify that the information you entered is correct. ::: :::WorkflowBlockItem If you wish to use a different billing code for auto-pull, enter the **Auto-Pull Billing Code** and **Password** ::: :::WorkflowBlockItem Click the **Validate Billing Code** button if you want to verify that the information you entered is correct. ::: :::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 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 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 See the **Parameters Table** below for additional fields. ::: :::WorkflowBlockItem Click **Save**. ::: ::::: ### 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 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). | | 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). 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 ZEC Source, verify that **Push** is selected (default). | | Application | To create a ZEC Source, verify that the **ZEC** radio button is selected (default). | | ZEC | Select from the drop-down list one of the available ZECs to be the ZEC that will be the **Origin ZEC**. | | ZEC Input | Select the relevant ZEC Input that will be part of the Source from the **Origin ZEC**. | | Bonding | Select the checkbox if you would like to user bonding. | | ZEC Output NIC/s (for None and Manual bonding) | 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 *Manual* for **Bonding**, then click the (plus) 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 (minus) 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 (i.e., the **Ingest Broadcaster Cluster**). | | Target Broadcaster/s | Specify which Broadcaster/s within the **Ingest Broadcaster 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. | | 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. | | Password
(Optional) | If you would like to set a password to authenticate the stream from the Feeder, enter the password or generate a random password by clicking on **Random**. You need to enter the identical password on the Feeder. | | PID Mapping Profile
(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 | If enabled, Zixi adjusts the latency dynamically to optimize it for network conditions. | | 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. | | Monitor CEA-608 Closed Captions | If you would like to monitor CEA-608 closed captions, select this checkbox.
Note: Broadcasters/ZECs older than version 18 will not distinguish between 608 and 708 captions. | | Monitor CEA-708 Closed Captions | If you would like to monitor CEA-708 closed captions, select this checkbox.
Note: Broadcasters/ZECs older than version 18 will not distinguish between 608 and 708 captions. | | 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) | | 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/recovery 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: 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 Passwords | 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. | | 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) | | Max FEC Overhead | Allows you to limit the additional data added for FEC (Forward Error Correction).
**Note: **this option is only for sources for Zixi Broadcaster **18.2 **or later. | | Frame Thinning | Allow non-critical frames to be dropped to reduce latency. **Note:** this option is available for Push sources only coming for Broadcaster 18.2 or later. | | Auto Pull MTU | Specify the maximum transmission unit (largest data packet that a network-connected device will accept) in bytes for the Auto Pull. | | Frozen Video Minimal Duration | 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 | 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. | [title] Viewing Broadcaster Active Objects [path] ZEN Master/ZEN Master User Guide/Broadcasters/Viewing Existing Clusters/Viewing Existing Broadcasters/ ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/3oGV3lc6ipeMgUTMbrTat_image.png) The Active Objects tab displays a list of objects (e.g., sources, target etc.) that are related to the selected Broadcaster with their statuses. Click on the object’s name to view the object’s details. The Details tab includes the following data for the selected network: | **Parameter** | **Description** | | -------------- | --------------------------------------------------------------------------------------------- | | **Name ** | The name of the object. | | **Status** | The object status:
Green – OK
Red – error
Orange – warning
Gray - unknown | | **Type** | The type of object | [title] Creating a New AWS MediaConnect Flow Channel [path] ZEN Master/ZEN Master User Guide/Channels/Adding MediaConnect Flow Channels/ **To create a new MediaConnect Flow Channel:** :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click** Channels**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Channel** selection menu is displayed. ![Create New Channel selection menu](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/9qvMY-FsApjKFyZ_GIVGQ_image.png) ::: :::WorkflowBlockItem Click on **AWS MediaConnect Flow**. The **Create MediaConnect Flow** window is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/_WK0vg5_HT58OLb0nynmU_image.png" size="80" width="1452" height="2778" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Info** section, in the** Name** field, enter a logical name for the Channel. ::: :::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 an Tag, you are relating this Channel 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 Channel. 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 In the **Configuration** section, verify that **Create New** is selected (default). ::: ::::WorkflowBlockItem In the **AWS Account** field, select from the drop-down list the AWS MediaConnect account that you would like to use for this Flow. :::hint{type="info"} If the Source does not exist in the cluster, then the cluster will pull the Source automatically. ::: :::: :::WorkflowBlockItem In the **Region** field, select from the drop-down list the AWS region that you would like to use for this Flow. ::: :::WorkflowBlockItem In the **Availability Zone** field, select from the drop-down list the Availability Zone that you would like to use for this Flow. ::: ::::WorkflowBlockItem In the **Source** field, select from the drop-down list the AWS MediaConnect type Source that you would like to assign to this Channel. :::hint{type="info"} Specifying a **Source** is optional. You can create a Channel without assigning a Source, although it won’t be activated until you assign a Source at a later time. You can also switch to a different Source at a later time. To learn about creating a MediaConnect Source, see [Adding an AWS MediaConnect Source – Creating a ZEN Master Managed Flow](docId\:ynOP9bIsiol7ZUVi6KLMz) . ::: :::: :::WorkflowBlockItem Under **Monitoring Configuration, **select the **Enable Thumbnails** checkbox, which allow thumbnails to update in the AWS Media Source Stream tab. ::: :::WorkflowBlockItem Under **VPC Interfaces**, if you want to stream content between your Virtual Private Cloud (VPC) and MediaConnect, without going over the public internet, click **Add VPC Interface**. ![New VPC Interface](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/3-b3nObBfFKGXop3X0FCg_image.png) ::: :::WorkflowBlockItem In the **Name** field, enter a name for the VPC interface. ::: :::WorkflowBlockItem In the **Type** field, select the type of network adapter that you want MediaConnect to use on this interface. ::: :::WorkflowBlockItem In the **Role ARN **field, select the Role ARN of the IAM role that you have created when you set up MediaConnect as a trusted device. ::: :::WorkflowBlockItem In the **Subnet** field, select the VPC subnet that you want MediaConnect to use to set up your VPC configuration. ::: :::WorkflowBlockItem In the **Security Groups** field, select the relevant security groups and the inbound and outbound rules. ::: :::WorkflowBlockItem To add additional VPC interface, click **Add VPC Interface**. ::: :::WorkflowBlockItem Under the **Media Streams** section, click **Add Media Stream** to add a media stream to represent each component (e.g. video, audio, etc.) of the flow. Media streams can only be added to a flow if the Source uses the ST 2110-22 JPEG-XS or CDI protocols. ![Add Media Stream](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/DpRrtZJBbRdz8-hCv74X6_image.png) ::: :::WorkflowBlockItem In the **Name** field, enter a name for the media stream. ::: :::WorkflowBlockItem In the **Type** field, select the relevant stream type (video, audio, ancillary data). ::: :::WorkflowBlockItem In the **Stream ID** field, enter a unique numeric identifier for this media stream. ::: :::WorkflowBlockItem In the **Media Clock Rate** field, select the clock rate in KHz for the stream. For video 90000 is selected; for audio, select between 48000 and 96000; for ancillary data 96000 is selected. ::: :::WorkflowBlockItem In the **Video Format** field, select the maximum format of the video (affects flow pricing). ::: :::WorkflowBlockItem In the **Exact Framerate** field, select the frame rate for the video (in frames per second). ::: :::WorkflowBlockItem In the **Colorimetry** field, select the format used for the representation of color. ::: :::WorkflowBlockItem In the **Scan Mode** field, select the type of compression used to smooth the video appearance. ::: :::WorkflowBlockItem In the **TCS** field, select the transfer characteristics system that is used in the video. ::: :::WorkflowBlockItem In the **Range** field, select the encoding range of the video. ::: :::WorkflowBlockItem In the **PAR** field, select the pixel aspect ration of the video. ::: :::WorkflowBlockItem To add additional Media Streams, click **Add Media Stream**. ::: ::::WorkflowBlockItem Select the **Muted** checkbox if you would like to disable error/recovery notifications for this Channel upon initial configuration. :::hint{type="info"} You can Enable/Unmute the Channel at any time. ::: :::: ::::WorkflowBlockItem Click **Save**. :::hint{type="info"} A MediaConnect Flow Channel can be assigned to a standard Target of the following types in ZEN Master: Push, Pull, RIST, RTP/RTP-FEC ::: :::: ::::: **New MediaConnect Flow Channel Configuration Parameters Table** | **Parameter** | **Description** | | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the MediaConnect Flow Channel 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 Channel 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 Channel. 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. | | ***Configuration*** | Verify that **Create New** is selected (default). | | AWS Account | Select from the drop-down list the AWS MediaConnect account that you would like to use for this Flow.
Note: If the Source does not exist in the cluster, then the cluster will pull the Source automatically. | | Region | Select from the drop-down list the AWS region that you would like to use for this Flow. | | Availability Zone | Select from the drop-down list the Availability Zone that you would like to use for this Flow. | | Source | Select from the drop-down list the AWS MediaConnect type Source that you would like to assign to this Channel.
Note: Specifying a **Source** is optional. You can create a Channel without assigning a Source, although it won’t be activated until you assign a Source at a later time. You can also switch to a different Source at a later time. To learn about creating a MediaConnect Source, see [Adding an AWS MediaConnect Source – Creating a ZEN Master Managed Flow](docId\:ynOP9bIsiol7ZUVi6KLMz). | | Description | Enter a description. This may help you distinguish one flow from another. | | ***Monitoring Configuration*** | | | Enable Thumbnails | Select this option to enable thumbnails to update in the AWS Media Source Stream tab. | | Frozen Video Minimal Duration \[seconds] | Specify the default minimal duration in seconds of frozen video after which a Frozen video alert will be triggered. Leave empty to disable. | | Blank Video Minimal Duration \[seconds] | Specify the default minimal duration in seconds of blank video after which a Blank video alert will be triggered. Leave empty to disable. | | Silent Audio Minimal Duration \[seconds] | Specify the default minimal duration in seconds of silent audio after which a Silent Audio alert will be triggered. Leave empty to disable. | | ***VPC Interfaces*** | if you want to stream content between your Virtual Private Cloud (VPC) and MediaConnect, without going over the public internet, click Add VPC Interface | | Name | Enter a name for the VPC interface | | Type | Select the type of network adapter that you want MediaConnect to use on this interface. | | Role ARN | Select the Role ARN of the IAM role that you have created when you set up MediaConnect as a trusted device | | Subnet | Select the VPC subnet that you want MediaConnect to use to set up your VPC configuration | | Security Groups | Select the relevant security groups and the inbound and outbound rules | | *Media Streams* | Click **Add Media Stream** to add a media stream to represent each component (e.g. video, audio, etc.) of the flow. Media streams can only be added to a flow if the Source uses the ST 2110-22 JPEG-XS or CDI protocols. | | Name | Enter a name for the media stream | | Type | Select the relevant stream type (video, audio, ancillary data) | | Stream ID | Enter a unique numeric identifier for this media stream | | Media Clock Rate | Select the clock rate in KHz for the stream. For video 90000 is selected; for audio, select between 48000 and 96000; for ancillary data 96000 is selected. | | Video Format | Select the maximum format of the video (affects flow pricing). | | Exact Framerate | Select the frame rate for the video (in frames per second). Sample format: 60000/1001. | | Colorimetry | Select the format used for the representation of color. | | Scan Mode | Select the type of compression used to smooth the video appearance. | | TCS | Select the transfer characteristics system that is used in the video. | | Range | Select the encoding range of the video. | | PAR | Select the pixel aspect ration of the video. Sample format: 12:11 | | ***Initial State*** | | | Muted | Select this checkbox if you would like to disable error/recovery notifications for this Channel upon initial configuration. | [title] Viewing Clusters Details [path] ZEN Master/ZEN Master User Guide/Broadcasters/Viewing Existing Clusters/ ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/XF0s4G9XlI_zVh83e7Guu-20251125-161745.jpg) | ***Details Tab*** |
| | ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | API Credentials | The username and password for accessing the APIs. Click **Show **to display. Click **Copy Password** to copy the password. | | Alternative Cluster
| Displays the configued path for an altternative cluster (disaster recovery) | | Events Configuration Profile | The Events Profile that is applied to this Broadcaster Cluster. Click the link to view the profile in the [Events Profile Rules](docId\:AgUE5_LD2Sz1HLysiWPsi) screen. | | Management Type | The Management type: manual, AWS, Azure or GCP. | | Account Name | The name of the cloud provider account under which the managed cluster is registered. | | RTMP Server | If RTMP Server is enabled, the RTMP server port is displayed. | | Ignore DTLS certificate when not supported | Indicates if **Ignore DTLS certificate when not supported** checkbox is enabled/disabled. When enabled, it is possible to support resources using older versions of Zixi software (\. | | Pull Outputs | Indicates if **Pull Outputs** checkbox is enabled/disabled. When enabled, the Broadcaster automatically allows access to Pull Outputs. | | Deletion Protection | Indicates whether the deletion protection is enabled or disabled. The deletion protection prevents deleting the Cluster. To delete it, you will need to first disable the Deletion Protection. | | Load Balance Pull Targets | The following load balancing methods for Pull outputs:
* **Minimize the number of broadcasters** (default) – transfers excess load to other broadcasters only when the allotted capacity on the host broadcaster is filled. * **Uniform distribution** – distributes the load equally between all available broadcasters under all circumstances. | | HTTP Streaming Port | The port configured for HTTP streaming. | | Subnet | The identifier/name of the subnet in which the cluster resides | | Security Groups | The identifier/name of the security group to which the cluster pertains | | AWS AMI | The AWS (Amazon Machine Image) that was selected to create the virtual server running the Broadcaster. | | Root Device Size | The size (in GB) of the **root volume**
attached to the EC2 instance. | | DPDK Support | Indicates if DPDK (high-performance networking feature) support is enabled/disabled. When enabled, ZEN Master will apply a second NIC to the launched instance. | | Activation key | The cluster’s activation key. | | Authorization Mode | The method used to verify authorization to access the broadcaster cluster. Possible values are: ZEN, External Server, Global Password, Free for All and Manual. | | Region | The cloud service region. | | Key Pair | The Key Pair used to access the cluster | | VPC | The identifier/name of the Virtual Private Cloud | | Instance Type | The name of the instance type on which the cluster is running on | | Broadcaster Version | The software version of the Broadcaster | [title] Viewing Existing Cluster Info Pane [path] ZEN Master/ZEN Master User Guide/Broadcasters/Viewing Existing Clusters/ When a cluster is selected, the list pane is minimized and detailed info about the selected cluster is shown on the right side of the screen. The right side of the screen includes an **Info Pane** (at the top), which displays basic information and the various tabs. | **Parameter** | **Description** | | ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | DNS Prefix | The first label in the DNS name of the domain. Click the copy icon to copy the details. | | Management Type | The Management type: manual, AWS, Azure or GCP. | | Instance Type
| The name of the instance type on which the cluster is running on. Click the copy icon to copy the details. | | Region | The cloud service region. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Cluster has been enabled. * No - the Priority checkbox of the Access Tag of this Cluster has been enabled. | | Tags | The Tags that are associated with this cluster.
Tags are managed by Administrators via Configuration > Tags and assigned to non-Admin users via Roles. Click to edit. | | Authorization Mode | The method used to verify authorization to access the broadcaster cluster. Possible values are: ZEN, External Server, Global Password, Free for All and Manual. | | Broadcaster Version | The version number of the Broadcaster(s) in the cluster. | | Log SCTE-35
| When enabled, SCTE-35 events are logged, and SCTE-35 notifications are sent. Requires version 13.1.40262 or newer Broadcasters. | | Activation Key
| The cluster’s activation key. | | Events Configuration Profile | The Events Configuration Profile that was assigned to this Cluster. Events Profiles are used to customize the way that Events are handled in ZEN Master. Click to view the event configuration. | ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/UmjCsJe_H8spTpqYfk3ar-20251125-154500.jpg) The **Info Panel** includes the following details: The following tabs are displayed in the right pane: - **Broadcasters** – shows a list of the Broadcasters that are related to this cluster and data about the Broadcasters. You can also add or delete Broadcasters in this tab. - **Redirection Rules **– shows a list redirection rules, which are routing rules for Pull requests from clusters or CIDR IP Ranges. The rules can be applied to the client end-point Cluster, or IP CIDR Range, from where the pull request is initiated. - **Details** – shows configuration details of the cluster. - **Events** – shows all events related to this cluster that have been generated by the system, such as connections, errors, warnings and disconnections. To learn about the data that is displayed in the Events tab see [Events](docId\:BgoWcWCc5rMvqDKmLBTtQ). - **Changes**- displays the history of changes that were made to the object configuration. To learn more about changes tracking, see [Change Tracking](docId\:hc-KMARjxkvIaZ69v6IVv). - **Notes **– free-form text can be added with pertinent information about this Cluster. [title] Adding a Source - RIST [path] ZEN Master/ZEN Master User Guide/Sources/Adding ZEN Master Sources/ ZEN Master can receive a Source directly from a RIST input. 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. Zixi supports the following RIST profiles: - **Simple Profile**– (Zixi Broadcasters v13+) The RIST Simple Profile provides best-in-class packet protection, as well as support for multi-link bonding and seamless switching. - **Main Profile **– (Zixi Broadcasters v14)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. :::hint{type="info"} 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/). ::: The following procedure describes how to add a RIST Source in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. ## To add a RIST Source: :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Source selection** window is displayed. ![Create Source Options](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-3mXDQJHXUppSRZJSBYBnR-20250805-132303.png) ::: :::WorkflowBlockItem Click on **RIST**. The **Create New RIST Source** window opens. ![New RIST Source](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/eCZgaTS4cPerO-xMPUqTL-20251104-202614.png) ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, enter a unique name to identify this Source in the system. ::: :::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 **RIST Configuration** section, under Profile, select the radio button for the desired Profile. Options are *Simple* (default) or *Main*. - If you selected **Simple**, then fill in the configuration fields as follows: 1. If you would like to join a Multicast group, in the **Multicast Address** field enter the Multicast address. **Note:** The multicast address should be in the range of 224.0.0.0 \~ 239.225.255.255. 2. If you entered a *Multicast Address*, then, in the **Source Specific Multicast **field, you can specify a particular IP from which you will accept data. 3. In the **Port **field, specify the port to listen on for the incoming content. **Note: **This port must be open on all firewalls between the Ingest Cluster and the input device. 4. If you would like to use FEC, then select the **Use Forward Error Correction **checkbox. **Note: **When FEC is used, repair packets are sent on additional ports, enabling packet recovery. - If you selected **Main**, then then fill in the configuration fields as follows: 1. Under **Mode**, select the mode used for sending the stream. Options are *Push *or *Pull*. 2. In the **Port **field, specify the port to listen on for the incoming content. 3. For *Pull* mode, in the **Remote Host **field, enter the hostname of the RIST server. 4. For *Pull* mode, in the **Remote Port **field, specify the remote port in the Source RIST device. Default: 0 (any port). 5. If you would like to use FEC, then select the **Use Forward Error Correction **checkbox. 6. If you would like to use DTLS, select the **Use Datagram Transport Layer Security **checkbox. ::: ::::WorkflowBlockItem In the **Max Bitrate** field, select from the drop-down list the maximum bitrate for this Source. *The Max Bitrate parameter in a Zixi Push Output is not enforced as a hard limit. It is used as a guideline for transport, buffering, and pacing, but Zixi does not actively throttle or drop packets to keep the stream below this value. As a result, the actual bitrate may exceed the configured Max Bitrate, especially with variable bitrate content or bitrate bursts.* *To enforce a strict bitrate limit, this must be controlled at the encoder level or via external network traffic shaping/QoS mechanisms.* :::hint{type="info"} Make sure that the value is greater than the max bitrate of the input. **If you are unsure of the max bitrate, set the value to approximately twice the actual (average) bitrate.** The default is set automatically based on the current bitrate of the input. See [High Max Bitrate Configuration](docId\:IJrN4V8zGysjoKXEVCkHx) ::: :::: :::WorkflowBlockItem In the **Latency** field, enter the latency in milliseconds (default: *4000*) ::: :::WorkflowBlockItem In the **Source Configuration** section, 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 preference. 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 **Input NIC** 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 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 [Adding PID Mapping Profiles](docId\:gFTCaYurPL7DInoUyd14z). ::: :::: :::WorkflowBlockItem Select the **Alert on PID changes** checkbox if you would like to generate email notifications whenever a PID change is detected. ::: ::::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 closed captions, select **Monitor CEA-608 **checkbox**.** :::hint{type="info"} Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: If you would like to monitor CEA-708 closed captions, select **Monitor CEA-708 **checkbox**.** :::hint{type="info"} Monitoring CEA-708 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: :::: ::::WorkflowBlockItem If you would like to disable auto-pull, select the **Disable Auto-Pull** 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. (Default: 1000 ms) ::: ::::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 Additional SCTE-35 options are available when you expand the **SCTE-35 Manipulation** section: ![SCTE-35 Manipulation](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/FxvVWM-bhpg9ZdVYW_LCl-20251104-153319.png) Here you can: - Enable SCTE-35 Insertion - Specify the length of a search window for a NULL packet for SCTE-35 intertion - Set the SCTE-35 PID - Remove any existing SCTE-35 messages from the stream See the **Parameters Table** below for an explanation of these options. ::: ::::WorkflowBlockItem In the **Initial State **section, select the Disabled checkbox if you would like to disable this Source upon initial configuration. 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 Under **Error Concealment,** click the Enable Error Concealment checkbox to enable the following error concealment mechanisms that can correct transaport stream for downstream IRDs: :::Paragraph{indent="1"} 1\. **Continuous Timeline** - corrects errors that are related to timeline jumps in the source. This mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input. ::: :::Paragraph{indent="1"} 2\. **Replace Frames** - If there are frames with CC errors, it replaces them with skip frames (inserts the last good frame received in place of missing ones). This solves issues such as an IRD that lost synchronization when it received broken frames. This mechanism also creates a variant of the input (doubling the input). ::: :::Paragraph{indent="1"} 3\. **Renumber CC **- The Continuity Counter is part of the TS encapsulation. When there are CC errors in TR101 analysis it means that the counter has a gap due to the lost frames. This mechanism can re-write the CC counter for the downstream devices, so they will see a continuous increase of the counter. ::: :::Paragraph{indent="1"} 4\. **Delay (ms) **- Enter the delay that the Error Concealment adds to the stream in miliseconds. Error Concealment needs to buffer the stream to analyze it. One second is a reasonable value. Lower values may cause the Error Concealment to not be able to fix some of the frames. ::: :::Paragraph{indent="1"} 5\. **CBR Padding** - enter a value for the rate at which padding will be added to maintain a specific output transport bitrate. For example, if you have a video bitrate at 5000 kbps or that varies from 3000-5000 kbps and audio at 64 kbps, total bitrate will be max 5064 kbps or min 3064 kbps. With CBR padding set at 6000 kbps, 6000 kbps is being delivered downstream at all times, ensuring a consistent bitrate. ::: :::Paragraph{indent="1"} 6.** PCR Interval** - Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. This depends on standard used by downstream encoders or decoders. Options include: ::: :::Paragraph{listStyleType="disc" indent="2"} ATSC standard - 100 ms ::: :::Paragraph{listStyleType="disc" indent="2"} DVB standard - 40 ms ::: 7. **Remux Buffer Size** - Specify the time added for remuxing the stream (default: 2500 ms). 8. **Smoothing** - Time added for smoothing a bursty stream - adds to latency, but produces a smoother output. See [Improving Stream Resiliency: Error Correction and Concealment](docId:9_OLo1Argk_2aDoSHYFBb) for more information. ![Error Concealment Options](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/jEyT42FS_YflpTNxqCc9Q_zm-error-concealment-options.png) :::: :::WorkflowBlockItem If you would like to adjust the advanced settings, click **Advanced**. The **Advanced** settings fields are displayed: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/SM02u6PYAujCTjNSbkixv_rist-source-advanced.png) ::: :::WorkflowBlockItem If you would like to track usage for this Source, enter your **Billing Code** details. See [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ). ::: :::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 apply Input NIC selection to the network device, select the **Apply Input NIC selection to network device** checkbox. ::: :::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 Click **Save**. ::: ::::: **RIST Source Configuration Parameters Table** | **Parameter** | **Description** | | -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | ***Info*** | | | Name | Specify a name for the RIST 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: *Event 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. | | ***RIST Configuration*** | | | Profile | Select the radio button for the desired Profile. Options are *Simple *(default) or* Main.* | | ***For Simple*** | | | Multicast Address | If you would like to join a multicast group, enter the multicast address.
The multicast address should be in the range of 224.0.0.0 \~ 239.225.255.255. | | Source Specific multicast | Specify a particular IP from which you will accept data. | | Port | Specify the port to listen on for the incoming content.
This port must be open on all firewalls between the Ingest Cluster and the input device. | | Use Forward Error Connection (FEC) | If you would like to use FEC, then select this checkbox.
When FEC is used, repair packets are sent on additional ports, enabling packet recovery. | | Max Bitrate | In the Max Bitrate field, select from the drop-down list the maximum bitrate for this Source. | | Latency \{ms} | Select the latency time for the stream (default 4000). | | ***For Main*** | | | Mode | Select the mode used for sending the Source. Options are: *Push* or *Pull*. | | *For Push Mode* | | | Port | Specify the port to listen on for the incoming content.
This port must be open on all firewalls between the Ingest Cluster and the input device. | | Use Forward Error Correction (FEC) | If you would like to use FEC, then select this checkbox.
When FEC is used, repair packets are sent on additional ports, enabling packet recovery. | | Use Datagram Transport Layer Security (DTLS) | If you would like to encrypt the stream dynamically using DTLS, select this checkbox. | | Max Bitrate | In the Max Bitrate field, select from the drop-down list the maximum bitrate for this Source.
Max Bitrate is used by the Broadcaster to determine buffer size when processing the transport stream - it does not cap the bitrate. We recommend setting it to 1.5x or 2x the actual (average) bitrate. Setting the max bitrate too low may result in dropped frames and other issues. | | Latency (ms) | Select the latency time for the stream (default 4000). | | *For Pull Mode* | | | Port | Specify the port to listen on for the incoming content.
This port must be open on all firewalls between the Ingest Cluster and the input device. | | Remote Host | Enter the hostname of the RIST server. | | Remote Port | Specify the remote port in the Source RIST device. Default: 0 (any port). | | ***Source 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 | If you would like to specify which NIC is used, select the IP of that NIC from the drop-down list. By default, *Any*is selected. | | 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. | | 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. | |
| If you would like to generate email notifications whenever a PID change is detected, select this checkbox. | | 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. | | Monitor CEA-608 Closed Captions | If you would like to monitor CEA-608 closed captions, select this checkbox.
Note: Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. | | Monitor CEA-708 Closed Captions | If you would like to monitor CEA-708 closed captions, select this checkbox.
Note: Monitoring 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 desired latency for auto-pull actions. (Default: 1,000 ms) | | 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. | | ***SCTE-35 Manipulation *** | | | Enable SCTE-35 Manipulation | Select checkbox to enable SCTE-35 Manipulation. | | SCTE-35 PID | Set the SCTE-35 PID in which the messages will be inserted. | | Remove Existing SCTE-35 | Remove any existing SCTE-35 messages from the stream. | | NULL Packet Search Window (ms) | Look for a NULL packet 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 | | ***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/recovery notifications for this Source upon initial configuration. | | ***Error Concealment*** | | | Enable Error Concealment | Select this checkbox to enable the error concealment mechanisms listed below to correct transport stream for downstream IRDs. | | Continuous Timeline | Corrects errors that are related to timeline jumps in the source. This mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input. | | Replace Frames | If there are frames with CC errors, it replaces them with skip frames (inserts the last good frame received in place of missing ones). This solves issues such as an IRD that lost synchronization when it received broken frames. This mechanism also creates a variant of the input (doubling the input). | | Renumber CC | encapsulation. When there are CC errors in TR101 analysis it means that the counter has a gap due to the lost frames. This mechanism can re-write the CC counter for the downstream devices, so they will see a continuous increase of the counter. | | Delay (ms) | Enter the delay that the Error Concealment adds to the stream in miliseconds. Error Concealment needs to buffer the stream to analyze it. One second is a reasonable value. Lower values may cause the Error Concealment to not be able to fix some of the frames. | | CBR Padding (kbps) | Enter a value for the rate at which padding will be added to maintain a specific output transport bitrate. For example, if you have a video bitrate at 5000 kbps or that varies from 3000-5000 kbps and audio at 64 kbps, total bitrate will be max 5064 kbps or min 3064 kbps. With CBR padding set at 6000 kbps, 6000 kbps is being delivered downstream at all times, ensuring a consistent bitrate. | | PCR Interval (ms) | Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. Options include:
* ATSC standard - 100 ms * DVB standard - 40 ms | | ***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+) | | 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 Password | Enter the password that corresponds to this auto-pull billing code. | | Auto-Pull Billing Code | Specify the maximum transmission unit (largest data packet that a network-connected device will accept) in bytes for the Auto Pull. | | 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. | | Apply Input NIC selection to network device | Select this checkbox to apply Input NIC selection to the network device. | | 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 for empty audio streams to prevent false warnings - enter a comma-delimited list of PID numbers that should not be monitored for null content. | [title] Source Content Analysis [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/ Shows a list of streaming errors that occurred on this Source. The list includes sub-sections for Content Analysis, TR101 Priority 1 and TR101 Priority 2. Content Analysis shows errors detected in the audio and video content itself. TR101 shows errors detected in the stream. This information can be helpful for troubleshooting problems in the system. For example, if you get *Continuity Count* errors you should check in the History Tab if this coincides with detection of *Unrecovered Packets*, which would indicate a problem with the way that your Zixi Source is being processed. You can reset the Content Analysis and TR101 logs by clicking on the Reset button at the bottom of the page. :::hint{type="info"} *PCR Accuracy Errors *are only relevant for CBR streams. For VBR streams these errors can be ignored. ::: ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-Bk7DhC7vDYIrTUHW2Qryw-20250721-144936.png) The following table explains the data shown for each listing. | **Parameter** | **Description** | | --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Status** | An indicator of the status for this Event Type.
* Red – The Source has experienced an event of this Event Type. * Green – This Source has not experienced an event of this Event Type. | | **Name** | The type of event specified in this listing. | | **Count** | The number of events of this type that have occurred on this Source. | | **Time** | The date and time of the **most recent** event of this type. | | **Description** | A description of the **most recent** event that occurred. | [title] Sources [path] ZEN Master/ZEN Master User Guide/ Sources are the input streams, which are managed in ZEN Master. A source can originate from a ZEC, a Broadcaster, an external source, such as external encoder or an external ZEC that has not been configured in the ZEN Master system, or an AWS MediaConnect Flow. All ZEN Master sources are managed on Broadcaster Ingest clusters in ZEN Master. If the input has already been configured on a Broadcaster cluster, then you can select *Monitor Only* in the *New Source* menu in order to manage the input in ZEN with limited functionality. If you would like to add a new input to a Broadcaster cluster and configure it to be managed in ZEN then select *Zixi* in the New Source menu. In the New Source menu you also specify the entity from which the source is being received, e.g. Feeder or Broadcaster. You can also combine two or more binary identical sources to create a unified* Failover* group that uses Zixi's patented DNA like re-sequencing algorithm to fill in missing packets for the sources. If you would like to create a new Source with a configuration similar to an existing Source you can use the Clone feature, see [Cloning a Source](docId\:CYYa5KqjokSdneAIfjuFM) . - [Adding ZEN Master Sources](docId\:FUeKsDqQp0ltvQR-7oAna) - [Adding AWS Media Sources](docId\:v9xGBuOfembDGDPQSS_uG) - [Adding a Source - AWS MediaConnect](docId\:Qi_aQkV6Wt6YIRhaTIKvU) - [Cloning a Source](docId\:CYYa5KqjokSdneAIfjuFM) - [Viewing Existing Sources](docId\:DZbMC_Tk_K3MrDXvG7qP5) - [SCTE-35 Insertion](docId\:P41x2TyDYny_zgjl3-XXA) [title] Adding an AWS MediaConnect Source [path] ZEN Master/ZEN Master User Guide/Sources/Adding AWS Media Sources/ ![MediaConnect Sources](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/S_FlGADNg-DkAz6Svnx8T_image.png) This Source is configured on an AWS MediaConnect that serves as the **Ingest Object**. The **Origin** can be one of the following: - [Zixi Protocol](docId:-s6sKwATSNdjavAhcbWcP) **- **the following** Origin **components can stream to the **AWS MediaConnect Ingest component** using the Zixi protocol: - **Feeder/ZEC/Broadcaster** - these components are managed by ZEN Master. The streaming uses the Zixi protocol. Once the AWS MediaConnect Flow channel is configured, ZEN Master will automatically configure the component to push the stream to the relevant MediaConnect Flow. - **Zixi Other** - this can be a Zixi-enabled encoder that streams using the Zixi protocol. This component is not managed by ZEN Master. - [RTP-FEC protocol](docId\:SB2YFGj1E8iklUSUAvYvn) - any non-Zixi component streaming to the AWS MediaConnect Ingest component using the RTP-FEC protocol. This Origin is not managed by ZEN Master. - [RTP protocol](docId\:AHTQjXFJioOUWXMZb0CDj) - any non-Zixi component streaming to the AWS MediaConnect Ingest component using the RTP protocol. This Origin is not managed by ZEN Master. - [RIST protocol](docId\:TezsS2_X2v1-0J6SDod-G) - any non-Zixi component streaming to the AWS MediaConnect Ingest component using the RIST protocol. This Origin is not managed by ZEN Master. - [SRT protocol](docId\:X9Jogs03ZhS2YNPBDRba1)** **- any non-Zixi component streaming to the AWS MediaConnect Ingest component using the SRT protocol. This Origin is not managed by ZEN Master. - [CDI protocol](docId:0Rppy-L7HX8jHvcsboDbj) - any non-Zixi component streaming to the AWS MediaConnect Ingest component using the CDI protocol. This Origin is not managed by ZEN Master. [AWS Elemental Link protocol](docId\:DPvTZ8aJZ6HOBGDaYVY4A)** **- an AWS Elemental Link Encoder streaming to the **AWS MediaConnect Ingest component **using the AWS Elemental Link protocol. This Origin is not managed by ZEN Master. :::hint{type="info"} You don’t need to have the AWS MediaConnect Flow channel ready at this point. You can create it later in the **Channels **section and connect it to the Source. ::: [title] Adding a Zixi-Broadcaster MediaConnect Source [path] ZEN Master/ZEN Master User Guide/Sources/Adding AWS Media Sources/Adding an AWS MediaConnect Source/Adding a Zixi-protocol MediaConnect Source/ You can add an input from a Zixi Broadcaster to an AWS MediaConnect Ingest Cluster to be managed as a source in ZEN. In this case, the Broadcaster is referred to as the **Origin Broadcaster** which streams to the **Ingest Cluster**. The streaming uses the Zixi protocol. Once the AWS MediaConnect Flow channel is configured, ZEN Master will automatically configure the component to push the stream to the relevant MediaConnect Flow. ![Zixi-Broadcaster MediaConnect Diagram](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/EyagFqmeQqaO2_UbyV6TH_image.png) 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.   The following procedure describes how to add a Zixi Broadcaster MediaConnect Source . In addition, an explanation of each of the configuration parameters is given in the table below. **To create a Zixi-Broadcaster MediaConnect Source:** ::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The Create New Source window is displayed. ![Create New Source window](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/AxSEVtTg03J7Up0wQFdjQ_image.png) ::: :::WorkflowBlockItem Under **AWS Media**, click on **AWS MediaConnect**. The Create New AWS Media Source window opens. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-b728uXrwi7W_eU8Y2aNf2-20250629-120255.png) ::: :::WorkflowBlockItem In the **Info **section, in the **Name** field, type a logical name for the 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. *Events Profiles* consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. ::: :::WorkflowBlockItem In the **Input** section, under **Protocol**, select the **Zixi** radio button.  ::: :::WorkflowBlockItem In the **Application** section, select **Broadcaster.** ::: :::WorkflowBlockItem In the **Broadcaster **field, select from the drop-down list one of the available Broadcasters. ::: :::WorkflowBlockItem In the **Broadcaster Input** field, select the desired input from the drop-down list of inputs on the selected Broadcaster. If you want the Source to be sent over a single NIC (i.e. no bonding) then do not select the **Bonding** checkbox. ::: :::WorkflowBlockItem In the **Broadcaster Output NIC**s 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 In the **Bonding **section, do the following: - Select the **Bonding** checkbox. - Select two or more NICs by clicking the **+ **button for each of the desired NICs. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-GvSpzfJDxQ2QdhnqwN3uo-20250629-120605.png) - Selected NICs are shown above the Filter box. (You can remove an NIC by clicking the **- **button for that 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. ::: :::WorkflowBlockItem In the **Latency \[ms]** field, select the latency time for the stream (default 4000). ::: :::WorkflowBlockItem You are required by MediaConnect to enter a valid **Whitelist CIDR block**. The whitelist CIDR block is a range of IP addresses that should be allowed to contribute content to your source. These IP addresses must be in the form of a Classless Inter-Domain Routing block. For example, 10.0.0.0/16. Through source needs to be in the range covered by this CIDR block. Any IP address with this range is allowed to send content to this flow. ::: :::WorkflowBlockItem In the **Initial State** section, select the **Muted** checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. You can Unmute the Source at any time. ::: :::WorkflowBlockItem If you would like to adjust the advanced settings, click Advanced. The **Advanced **settings fields are displayed: ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-OPyZCbdSmeg9vlDus6IM--20250629-120840.png) ::: :::WorkflowBlockItem Click **Save**. ::: :::: **Parameters Table** | **Parameter** | **Description** | | ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the AWS Media 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. | | ***Input*** | | | Protocol | To create a Zixi Input AWS Media Source, verify that **Zixi** is selected (default). | | Application | Select **Broadcaster**. | | Broadcaster | Select from the drop-down list the desired Broadcaster. | | Broadcaster Input | Select from the drop-down list one of the Inputs that are available on the selected Feeder. | | Bonding | Select the checkbox if you would like to use bonding. | | Broadcaster Output NICs | 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. | | Latency \[ms] | Specify the latency time for the stream (default 4000). | | ***Source Configuration*** | | | Whitelist CIDR Block | Specify the CIDR for the range of IPs that you would like to allow to contribute content to this Source.
You are required by MediaConnect to enter a valid Whitelist CIDR block. | | ***Initial State*** | | | Muted | Select this checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. | | ***Advanced*** | | | Traffic Shaping \[kbps] | Specify the traffic shaping setting to limit the momentary bitrate spikes. This mechanism adjusts the packet rates to control data flow in order to prevent network congestion. It delays or queues less critical packets to prioritize important traffic. Specify the birtate limit in Kbps that will serve as the threshold bitrate afterwhich it will apply the traffic shapping mechanism. | | Max FEC Overhead \[%] | Specify the percentage of the Source bitrate that will be allocated to Forward Error Correction. By default, Zixi's dynamic FEC adjusts based on network conditions. However by specifying this setting you can cap the FEC allocation in specific scenarios. | | Frame Thinning Latency \[ms] | The Frame Thinning feature removes frames from the stream to get to a lower bitrate if the stream is traversing a crowded network instead of using transcoding to lower the bitrate. To allow the analysis and selection of the frames, Broadcaster needs a buffer. This setting specifies the buffer size (latency) that is allowed in milliseconds in order to remove these frames. The higher the value, the more accurate results that the Frame Thinning feature will reproduce. A reasonable value is 1 seconds.

| [title] Viewing Preview in VLC [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/ The preview is played back directly from the Zixi Broadcaster and can be used to preview the stream before any Channel processing. The playback is only possible when the session is active. This means that you must be logged in to view the content. You can choose between two viewing modes: - **High Resilience** – uses relatively high latency setting (4 seconds) for the Zixi protocol to provide very good resiliency for any network conditions. - **Low Latency** – uses low latency (500ms including VLCs latency requirements), for situations that require viewing the Source as close to real-time as possible. This mode can only be used when the Network supports that level of performance. For Manual clusters with broadcasters that are configured with a private IP, you can select whether the private IP or public IP is used for viewing the preview. :::hint{type="info"} The first time that you view a Source preview you will need to ensure that the VLC player is installed with the Zixi plugin. See [Installing the VLC Player and the Zixi VLC Plug-In](docId\:xCta6Jsvuk7v69VXPn-dU). ::: **To view a Source preview in VLC:** :::::WorkflowBlock :::WorkflowBlockItem In the **Info Pane** section for the desired Source, click on the **VLC** button below **Play**. ![Play > VLC](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/8CmDfPb4H0Qrpvhwq1UoA_image.png) You are redirected to the Source preview landing page. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-rp8B5zcC-LI4u1Gx3SFhw-20250720-163521.png) ::: :::WorkflowBlockItem In the **Mode** section, select the Latency Mode. Options are: ***Low Latency*** or ***High Resilience***. ::: :::WorkflowBlockItem In the **Network section**, select Public Mode. Options are Public or Private. ::: ::::WorkflowBlockItem Click **Play**. The preview is shown in VLC. :::hint{type="info"} Your button selections on the landing page are saved in the browser and will be remembered from session to session in that browser. Also, you only need to click the “Play” button on the landing page the first time you view the page. The next time you preview a Source, the browser will go to the landing page and start the playback sequence automatically. If you want to change the settings, you can close VLC, causing the landing page to be shown again. You can share the link for the landing page with other ZEN Master users. If they are already logged in to ZEN Master the landing page will open on their browser and they can click Play. If they are not logged in, they will be taken to the ZEN Master login page first and then to the Source preview landing page after logging in. ::: :::: ::::: [title] Adding a Source - File [path] ZEN Master/ZEN Master User Guide/Sources/Adding ZEN Master Sources/ Create a Source from a .ts file. The file needs to already exist in the Root folder on the input Broadcaster (Local File option) or at the remote location (URL option). :::hint{type="info"} - The default Root folder for Broadcasters created by ZEN Master is currently /zixi/zixi\_broadcaster-centos7-transcoder/files. Manually created Broadcasters may have a different Root folder. - ZEN Master does not provide a mechanism for uploading and managing files on the server hosting the Broadcaster. There are numerous web-based file managers that can be deployed for remote file management on the server hosting the Broadcaster ::: ## To add a File Source :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Source selection** window is displayed. ![Create Source Options](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-3mXDQJHXUppSRZJSBYBnR-20250805-132303.png) ::: :::WorkflowBlockItem Click on **File**. The **Create New File Source** window opens. ![New File Source](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-jmgSWk5eUSQ6i04ml7N6R-20250519-182555.png) ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, enter a unique name to identify this Source in the system. ::: :::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 If you would like to stream a file from a local drive, skip to step 10. To stream a file using a URL, use the following procedure: 1. In the **Source** section, verify that **URL** is selected (default). 2. In the **URL** field, enter the URL for the .ts file you would like to stream (e.g. [https://example.com/source.ts](https://example.com/source.ts)). ::: :::WorkflowBlockItem If you selected the **Use RTP protocol** checkbox, then if you would like to use FEC, then select the **Use Forward Error Correction **checkbox. ::: ::::WorkflowBlockItem To upload a file from a local drive, use the following procedure: 1. In the **Source** section, select **Local Drive**. 2. In the **File** field, select from the list the desired .ts file you would like to stream. The selected file will be highlighted and displayed under the list. :::hint{type="info"} You can sort the files in the list by clicking on the column headings. ::: :::: :::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 closed captions, select **Monitor CEA-608 **checkbox**.** :::hint{type="info"} Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: f you would like to monitor CEA-708 closed captions, select **Monitor CEA-708 **checkbox**.** :::hint{type="info"} Monitoring CEA-708 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: :::: ::::WorkflowBlockItem If you would like to disable auto-pull, select the **Disable Auto-Pull** 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. (Default: 1000 ms) ::: ::::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 Additional SCTE-35 options are available when you expand the **SCTE-35 Manipulation** section: ![SCTE-35 Manipulation](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/FxvVWM-bhpg9ZdVYW_LCl-20251104-153319.png) Here you can: - Enable SCTE-35 Insertion - Specify the length of a search window for a NULL packet for SCTE-35 intertion - Set the SCTE-35 PID - Remove any existing SCTE-35 messages from the stream See the **Parameters Table** below for an explanation of these options. ::: :::WorkflowBlockItem In the **Initial State** section, select the Disabled checkbox if you would like to disable this Source upon initial configuration. Select the **Muted** checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. ::: ::::WorkflowBlockItem :::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: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/rVVKHiN_EukFiSfzypq6H_file-source-advanced.png) ::: :::WorkflowBlockItem If you would like to track usage for this Source, enter your **Billing Code** details. See [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ). ::: :::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 Click **Save**. ::: ::::: ## File Source Configuration Parameters Table | Parameter | Description | | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the File 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](https://zixidocumentation.atlassian.net/wiki/spaces/ZMUG/pages/828014604/Creating+a+Tag). | | 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 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*** | | | Broadcaster | Select from the drop-down list the Broadcaster on which the file is located. | | Source | Select the source of your .ts file.
Select one of the following options:
* **URL** (default) – stream a .ts file from a URL * **Local Drive** – stream a .ts file from the Root folder on the input Broadcaster | | URL (for URL) | Enter the URL for the .ts file you would like to stream
(e.g. https\://example.com/source.ts). | | File (for Local Drive) | Select from the list the desired .ts file you would like to stream. The selected file must exist in the Root folder on the input Broadcaster.
Note: You can sort the files in the list by clicking on the column headings. | | *Configuration* | | | 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. | | Monitor CEA-608 Closed Captions | If you would like to monitor CEA-608 closed captions, select this checkbox.
Note**:** Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. | | Monitor CEA-708 Closed Captions | If you would like to monitor CEA-708 closed captions, select this checkbox.
Note**:** Monitoring 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 desired latency for auto-pull actions. (Default: 1,000 ms) | | 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. | | ***SCTE-35 Manipulation *** | | | Enable SCTE-35 Manipulation | Select checkbox to enable SCTE-35 Manipulation. | | SCTE-35 PID | Set the SCTE-35 PID in which the messages will be inserted. | | Remove Existing SCTE-35 | Remove any existing SCTE-35 messages from the stream. | | NULL Packet Search Window (ms) | Look for a NULL packet 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 | | ***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/recovery 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 . (Supported for Broadcasters v14.8+) | | 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 | Specify the maximum transmission unit (largest data packet that a network-connected device will accept) in bytes for the Auto Pull. | | Auto-Pull Billing Password | Enter the password that corresponds to this auto-pull billing code. | | 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. | | 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 for empty audio streams to prevent false warnings - enter a comma-delimited list of PID numbers that should not be monitored for null content. | [title] Adding Broadcasters to a Managed Cluster [path] ZEN Master/ZEN Master User Guide/Broadcasters/Creating a Broadcaster Cluster/Adding Broadcasters to a Cluster/ **To add one or more Broadcasters to a Managed Cluster:** :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, select **Broadcasters**. ::: :::WorkflowBlockItem From the list of Broadcaster clusters, select the cluster to which you want to add a Broadcaster. The details of the cluster are displayed at the right of the screen. ::: :::WorkflowBlockItem Select the Broadcasters tab (for Tab view). ![Broadcasters Tab](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/0EceX18uqPQ9_3Tg7WtO9_image.png) ::: :::WorkflowBlockItem Click **+ Add Broadcaster**. The **Create New Broadcaster** screen is displayed. ![Create New Broadcaster screen](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/66piE1W6PKTOXIAANwfDR_image.png) ::: :::WorkflowBlockItem In the **Info** section, In the **Name** field, by default, the name is pre-filled based on the cluster name and a timestamp, however it is possible to edit this name. ::: :::WorkflowBlockItem The Broadcaster's location is used to represent it in the proper position in the Map display (see Maps). By default, the location is determined automatically based on the Broadcaster's IP. If you would like to manually set the location of the Broadcaster (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 Select the **Broadcaster Type**. Options are: - **Primary **(default) – The Broadcaster functions as an active member of the cluster. - **Backup** – The Broadcaster does not receive Sources/Channels unless all Primary Broadcasters are unavailable (or it is manually configured to receive that Source). ::: :::WorkflowBlockItem If you would like to adjust the advanced settings, click on **Advanced**. The **Advanced settings** are displayed: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/h7YD0UshtiBAyQtuMxdh6_image.png" size="90" width="431" height="240" position="center" showCaption="false"} ::: :::WorkflowBlockItem In the **Streaming IP** section, the **Auto Detect** checkbox is selected by default. If you would like to manually specify the streaming IP, **deselect** the checkbox and enter the broadcaster’s public IP in the **IP**. ::: ::::WorkflowBlockItem In the **Private IP** section, the **Use Streaming IP** checkbox is selected by default. If you would like to specify a separate private IP, **deselect** the checkbox and enter the broadcaster’s private IP in the **IP**. :::hint{type="info"} By specifying a private IP, you enable ZEN Master to access streams through the private IP. This enables you to view Source previews over the private IP. ::: :::: :::WorkflowBlockItem In the **Bandwidth Limits** section, you can specify limits for the **Input** and **Output**. ::: :::WorkflowBlockItem Click **Save**. ::: ::::: [title] Adding a Zixi-ZEC MediaConnect Source [path] ZEN Master/ZEN Master User Guide/Sources/Adding AWS Media Sources/Adding an AWS MediaConnect Source/Adding a Zixi-protocol MediaConnect Source/ You can add an input from a ZEC to an AWS MediaConnect Ingest Cluster to be managed as a source in ZEN. In this case, the ZEC is referred to as the **Origin Broadcaster** which streams to the **Ingest Cluster**. The streaming uses the Zixi protocol. Once the AWS MediaConnect Flow channel is configured, ZEN Master will automatically configure the component to push the stream to the relevant MediaConnect Flow. ![Zixi-ZEC MediaConnect Diagram](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/4WwB5eCeuP6GS7j3y00Oi_image.png) When configuring a Source using a Push stream from a ZEC 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.   The following procedure describes how to add a ZEC MediaConnect Source . In addition, an explanation of each of the configuration parameters is given in the table below. **To create a Zixi-ZEC MediaConnect Source:** :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The Create New Source window is displayed. ![Create New Source window](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/AxSEVtTg03J7Up0wQFdjQ_image.png) ::: :::WorkflowBlockItem Under **AWS Media**, click on **AWS MediaConnect**. The Create New AWS Media Source window opens. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-BHNNpbgwDLZi2e3yF4Zaj-20250629-131009.png) ::: :::WorkflowBlockItem In the **Info **section, in the **Name** field, type a logical name for the 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. *Events Profiles* consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. ::: :::WorkflowBlockItem In the **Input** section, under **Protocol**, select the **Zixi** radio button.  ::: :::WorkflowBlockItem In the **Application** section, select **ZEC**. ::: :::WorkflowBlockItem In the **ZEC **field, select from the drop-down list one of the available ZECs. In the **ZEC Input** field, select the desired input from the drop-down list of ZEC inputs on the selected Broadcaster. ::: ::::WorkflowBlockItem If you would like to use **Bonding **section, do the following: - Select the **Bonding** checkbox. - Select two or more NICs by clicking the **+** button for each of the desired NICs. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/AKGeIoMd7Ja85DkWNekLI_image.png" size="100" width="876" height="375" position="center" alt="Selecting NICs for Bonding" showCaption="false" indent="2"} - Selected NICs are shown above the Filter box. (You can remove an NIC by clicking the **- **button for that 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 In the **Latency \[ms]** field, select the latency time for the stream (default 4000). ::: :::WorkflowBlockItem You are required by MediaConnect to enter a valid **Whitelist CIDR block**. The whitelist CIDR block is a range of IP addresses that should be allowed to contribute content to your source. These IP addresses must be in the form of a Classless Inter-Domain Routing block. For example, 10.0.0.0/16. Through source needs to be in the range covered by this CIDR block. Any IP address with this range is allowed to send content to this flow. ::: :::WorkflowBlockItem In the **Initial State** section, select the **Muted** checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. You can Unmute the Source at any time. ::: :::WorkflowBlockItem If you would like to adjust the advanced settings, click **Advanced**. The **Advanced **settings fields are displayed: ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-QzEMHTwj-Fxcrh01kbPcg-20250629-131309.png) ::: :::WorkflowBlockItem Click **Save**. ::: ::::: **Parameter Table** | **Parameter** | **Description** | | ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the AWS Media 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. | | ***Input*** | | | Protocol | To create a Zixi Input AWS Media Source, verify that **Zixi** is selected (default). | | Application | Select **ZEC**. | | ZEC | Select from the drop-down list the desired ZEC. | | ZEC Input | Select from the drop-down list one of the Inputs that are available on the selected ZEC. | | Bonding | Select the checkbox if you would like to use bonding. | | Broadcaster Output NICs | 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. | | Latency \[ms] | Specify the latency time for the stream (default 4000). | | ***Source Configuration*** | | | Whitelist CIDR Block | Specify the CIDR for the range of IPs that you would like to allow to contribute content to this Source.
You are required by MediaConnect to enter a valid Whitelist CIDR block. | | ***Initial State*** | | | Muted | Select this checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. | | ***Advanced*** | | | Traffic Shaping \[kbps] | Specify the traffic shaping setting to limit the momentary bitrate spikes. This mechanism adjusts the packet rates to control data flow in order to prevent network congestion. It delays or queues less critical packets to prioritize important traffic. Specify the birtate limit in Kbps that will serve as the threshold bitrate afterwhich it will apply the traffic shapping mechanism. | | Max FEC Overhead \[%] | Specify the percentage of the Source bitrate that will be allocated to Forward Error Correction. By default, Zixi's dynamic FEC adjusts based on network conditions. However by specifying this setting you can cap the FEC allocation in specific scenarios. | | Frame Thinning Latency \[ms] | The Frame Thinning feature removes frames from the stream to get to a lower bitrate if the stream is traversing a crowded network instead of using transcoding to lower the bitrate. To allow the analysis and selection of the frames, ZEC needs a buffer. This setting specifies the buffer size (latency) that is allowed in milliseconds in order to remove these frames. The higher the value, the more accurate results that the Frame Thinning feature will reproduce. A reasonable value is 1 seconds. | [title] Adding a Source – Inter-Cluster [path] ZEN Master/ZEN Master User Guide/Sources/Adding ZEN Master Sources/ You can create an Inter-Cluster Source to pull a stream from an existing Source that is managed by ZEN Master into a new Cluster in ZEN Master. This enables you to specify the latency and private IP address used for pulling the stream. The new Source will be monitored fully by ZEN Master. This can be helpful, for example, if your deployment utilizes separate Broadcaster clusters for ingesting source streams and delivering streams to Receivers. Creating an Inter-Cluster Source enables you to explicitly pull the Source from the ingesting cluster to the delivery cluster using your customized specifications. The following procedure describes how to add an Inter-Cluster Source in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. ## To add a Source from an existing cluster: :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Source selection** window is displayed. ![Create Source Options](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-3mXDQJHXUppSRZJSBYBnR-20250805-132303.png) ::: :::WorkflowBlockItem Click on **Inter-Cluster**. The **Create New Inter-Cluster** window opens. ![New Inter-Cluster Source](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/a5-xqeMP8D6IcvSJBM43b-20251104-190727.png) ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, type a logical name for the 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 **Input** section, in the **Sources **field, select from the drop-down list a source that is managed on ZEN Master that will be sent to the new Ingest Cluster. ::: :::WorkflowBlockItem In the **Configuration **section, 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, specify which Broadcaster/s within the cluster on which ZEN Master can deploy the source. Either select one or more specific broadcasters (for Manual clusters) 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 If you would like to use a private IP, select the **Prefer Private Broadcaster IP** checkbox. :::hint{type="info"} Using this feature may be cost effective when using Manual clusters. To use this feature, you must first enter a Private IP in the Broadcaster's advanced configuration (go to **Broadcasters** screen > select the relevant **Cluster > Broadcasters** tab > **Edit** the relevant broadcaster), see [Adding a Broadcaster to a Manual Cluster](docId\:C6F1oz95Yk6Lk8TJkG4Z4). ::: :::: :::WorkflowBlockItem In the **Input NIC** 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 In the **Latency \[ms]** field, select the latency time for the stream. Default value: *4000*. :::hint{type="info"} For Clusters that are in close geographical proximity lower latency can be used. ::: :::: ::::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 [Adding PID Mapping Profiles](docId\:gFTCaYurPL7DInoUyd14z) . ::: :::: :::WorkflowBlockItem If you would like to generate email notifications whenever a PID change is detected In the **Configuration** section, select the **Alert on PID changes** checkbox. ::: ::::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 Additional SCTE-35 options are available when you expand the **SCTE-35 Manipulation** section: ![SCTE-35 Manipulation](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/FxvVWM-bhpg9ZdVYW_LCl-20251104-153319.png) Here you can: - Enable SCTE-35 Insertion - Specify the length of a search window for a NULL packet for SCTE-35 intertion - Set the SCTE-35 PID - Remove any existing SCTE-35 messages from the stream See the **Parameters Table** below for an explanation of these options. ::: :::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 closed captions, select **Monitor CEA-608 **checkbox**.** :::hint{type="info"} Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: If you would like to monitor CEA-708 closed captions, select **Monitor CEA-708 **checkbox**.** :::hint{type="info"} Monitoring CEA-708 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: :::: ::::WorkflowBlockItem If you would like to disable auto-pull, select the **Disable Auto-Pull** 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 desired latency for auto-pull actions. (Default: 1000 ms) ::: ::::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 Under **Error Concealment,** click the Enable Error Concealment checkbox to enable the following error concealment mechanisms that can correct transaport stream for downstream IRDs: :::Paragraph{indent="1"} 1\. **Continuous Timeline** - corrects errors that are related to timeline jumps in the source. This mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input. ::: :::Paragraph{indent="1"} 2\. **Replace Frames** - If there are frames with CC errors, it replaces them with skip frames (inserts the last good frame received in place of missing ones). This solves issues such as an IRD that lost synchronization when it received broken frames. This mechanism also creates a variant of the input (doubling the input). ::: :::Paragraph{indent="1"} 3\. **Renumber CC **- The Continuity Counter is part of the TS encapsulation. When there are CC errors in TR101 analysis it means that the counter has a gap due to the lost frames. This mechanism can re-write the CC counter for the downstream devices, so they will see a continuous increase of the counter. ::: :::Paragraph{indent="1"} 4\. **Delay (ms) **- Enter the delay that the Error Concealment adds to the stream in miliseconds. Error Concealment needs to buffer the stream to analyze it. One second is a reasonable value. Lower values may cause the Error Concealment to not be able to fix some of the frames. ::: :::Paragraph{indent="1"} 5\. **CBR Padding** - enter a value for the rate at which padding will be added to maintain a specific output transport bitrate. For example, if you have a video bitrate at 5000 kbps or that varies from 3000-5000 kbps and audio at 64 kbps, total bitrate will be max 5064 kbps or min 3064 kbps. With CBR padding set at 6000 kbps, 6000 kbps is being delivered downstream at all times, ensuring a consistent bitrate. ::: :::Paragraph{indent="1"} 6.** PCR Interval** - Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. This depends on standard used by downstream encoders or decoders. Options include: ::: :::Paragraph{listStyleType="disc" indent="2"} ATSC standard - 100 ms ::: :::Paragraph{listStyleType="disc" indent="2"} DVB standard - 40 ms ::: 7. **Remux Buffer Size** - Specify the time added for remuxing the stream (default: 2500 ms). 8. **Smoothing** - Time added for smoothing a bursty stream - adds to latency, but produces a smoother output. See [Improving Stream Resiliency: Error Correction and Concealment](docId:9_OLo1Argk_2aDoSHYFBb) for more information. ![Error Concealment Options](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/jEyT42FS_YflpTNxqCc9Q_zm-error-concealment-options.png) :::: :::WorkflowBlockItem If you would like to adjust the advanced settings, click **Advanced**. The **Advanced** settings fields are displayed: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/irAtz1o0h_YCdaFdAqe_h_intercluster-source-advanced.png) ::: :::WorkflowBlockItem If you would like to track usage for this Source, enter your **Billing Code** details. See [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ). ::: :::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 Click **Save**. ::: ::::: ## Inter-Cluster Source Configuration Parameters Table | **Parameter** | **Description** | | ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | ***Info*** | | | Name | Specify the name of the Inter-Cluster 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 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*** | | | Source | Select from the drop-down list the Source that the transcoded Source is based on. | | ***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. | | Prefer Private Broadcaster IP | If you would like to use a private IP, select the **Prefer Private Broadcaster IP **checkbox.
Using this feature may be cost effective when using manual clusters. To use this feature, you must first enter a Private IP in the Broadcaster's advanced configuration (go to **Broadcasters** screen > select the relevant Cluster > **Broadcasters** tab > **Edit** the relevant broadcaster), see [Adding a Broadcaster to a Manual Cluster](docId\:xYscySO498lY77ZjQr-51) . | | Input NIC
(For Target Broadcaster selected) | Select the IPv4 address of an Input NIC from the drop-down list. | | Latency \[ms] | Select the latency time for the stream (default 4000). | | PID Mapping Profile
(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 | If enabled, Zixi adjusts the latency dynamically to optimize it for network conditions. | | Log SCTE-35 | Select this checkbox if kyou 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. | | Monitor CEA-608 Closed Captions | If you would like to monitor CEA-608 closed captions, select this checkbox.
**Note:** Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. | | Monitor CEA-708 Closed Captions | If you would like to monitor CEA-708 closed captions, select this checkbox.
**Note:** Monitoring 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 desired latency for auto-pull actions. (Default: 1,000 ms) | | 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. | | ***SCTE-35 Manipulation *** | | | Enable SCTE-35 Insertion | Select checkbox to enable SCTE-35 Insertion. | | SCTE-35 PID | Set the SCTE-35 PID in which the messages will be inserted. | | Remove Existing SCTE-35 | Remove any existing SCTE-35 messages from the stream. | | NULL Packet Search Window (ms) | Look for a NULL packet 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 | | ***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/recovery notifications for this Source upon initial configuration. | | ***Error Concealment*** | | | Enable Error Concealment | Select this checkbox to enable the error concealment mechanisms listed below to correct transport stream for downstream IRDs. | | Continuous Timeline | Corrects errors that are related to timeline jumps in the source. This mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input. | | Replace Frames | If there are frames with CC errors, it replaces them with skip frames (inserts the last good frame received in place of missing ones). This solves issues such as an IRD that lost synchronization when it received broken frames. This mechanism also creates a variant of the input (doubling the input). | | Renumber CC | encapsulation. When there are CC errors in TR101 analysis it means that the counter has a gap due to the lost frames. This mechanism can re-write the CC counter for the downstream devices, so they will see a continuous increase of the counter. | | Delay (ms) | Enter the delay that the Error Concealment adds to the stream in miliseconds. Error Concealment needs to buffer the stream to analyze it. One second is a reasonable value. Lower values may cause the Error Concealment to not be able to fix some of the frames. | | CBR Padding (kbps) | Enter a value for the rate at which padding will be added to maintain a specific output transport bitrate. For example, if you have a video bitrate at 5000 kbps or that varies from 3000-5000 kbps and audio at 64 kbps, total bitrate will be max 5064 kbps or min 3064 kbps. With CBR padding set at 6000 kbps, 6000 kbps is being delivered downstream at all times, ensuring a consistent bitrate. | | PCR Interval (ms) | Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. Options include:
* ATSC standard - 100 ms * DVB standard - 40 ms | | ***Advanced*** | | | Billing Codes | If you would like to track usage for this Source, enter your **Billing Code** details, see . (Supported for Broadcasters v14.8+) | | 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. | | Auto Pull MTU | Specify the maximum transmission unit (largest data packet that a network-connected device will accept) in bytes for the Auto Pull. | | Frozen Video Minimal Duration | 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 | 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 for empty audio streams to prevent false warnings - enter a comma-delimited list of PID numbers that should not be monitored for null content. | [title] Source Info Pane [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/ The **Info pane **section shows the following information: | **Parameter** | **Description** | | ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Type | The type of the Source in ZEN Master e.g., Broadcaster, ZEC, Monitor Only, RIST, File etc.

| | ***Broadcaster*** | | | Bitrate | The current bitrate of the stream. | | Uptime | For online Sources, shows the number of hours, minutes and seconds that the Source has been online. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
Yes - the Priority checkbox of the Access Tag of this Source has been enabled.
No - the Priority checkbox of the Access Tag of this Source has been enabled. | | Play | Downloads a .vlc stream file that is automatically played back in the VLC player with the necessary parameters to view the Zixi stream (Requires Zixi VLC Plugin), see [Viewing Preview in VLC](docId\:RmCwt-Gw-6f2PrOG2l0ay) . | | Tags | The Tag/s that is associated with this Source. | | Input | The details of the source’s input. | | Source IP | The IP address of the Source's input resource. Transcoded – means that the source is transcoded. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | Latency | The maximal latency that the stream has reached throughout time. | | Encrypted | Indicates whether the source is encrypted or not and the encryption type used. | | Location | The location of the Source. | | Network | The network on which the source is hosted. | | | The details of the Source’s input. | | Source Password | Click **Show** to display the Source's password. | | ***Demux*** | | | Bitrate | The current bitrate of the stream. | | Uptime | For online Sources, shows the number of hours, minutes and seconds that the Source has been online. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Source has been enabled. * No - the Priority checkbox of the Access Tag of this Source has been enabled. | | Play | Downloads a .vlc stream file that is automatically played back in the VLC player with the necessary parameters to view the Zixi stream (Requires Zixi VLC Plugin), see [Viewing Preview in VLC](docId\:RmCwt-Gw-6f2PrOG2l0ay). | | Tags | The Tag/s that is associated with this Source. | | Input | The details of the source’s input. | | Source IP | The IP address of the Source's input resource. Transcoded – means that the source is transcoded. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | Encrypted | Indicates whether the source is encrypted or not. | | ***Failover*** | | | Bitrate | The current bitrate of the stream. | | Uptime | For online Sources, shows the number of hours, minutes and seconds that the Source has been online. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Source has been enabled. * No - the Priority checkbox of the Access Tag of this Source has been enabled. | | Play | Downloads a .vlc stream file that is automatically played back in the VLC player with the necessary parameters to view the Zixi stream (Requires Zixi VLC Plugin), see [Viewing Preview in VLC](docId\:RmCwt-Gw-6f2PrOG2l0ay). | | Tags | The Tag/s that is associated with this Source. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | Encrypted | Indicates whether the source is encrypted or not. | | ***File*** | | | Bitrate | The current bitrate of the stream. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
Yes - the Priority checkbox of the Access Tag of this Source has been enabled.
No - the Priority checkbox of the Access Tag of this Source has been enabled. | | Tags | The Tag/s that is associated with this Source. | | Encrypted | Indicates whether the source is encrypted or not. | | Uptime | For online Sources, shows the number of hours, minutes and seconds that the Source has been online. | | Play | Downloads a .vlc stream file that is automatically played back in the VLC player with the necessary parameters to view the Zixi stream (Requires Zixi VLC Plugin), see [Viewing Preview in VLC](docId\:RmCwt-Gw-6f2PrOG2l0ay). | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | **HLS** | | | Bitrate | The current bitrate of the stream. | | Uptime | For online Sources, shows the number of hours, minutes and seconds that the Source has been online. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Source has been enabled. * No - the Priority checkbox of the Access Tag of this Source has been enabled. | | Play | Downloads a .vlc stream file that is automatically played back in the VLC player with the necessary parameters to view the Zixi stream (Requires Zixi VLC Plugin), see Viewing [Viewing Preview in VLC](docId\:RmCwt-Gw-6f2PrOG2l0ay). | | Tags | The Tag/s that is associated with this Source. | | Input | The details of the source’s input. | | Max Bitrate | The maximal bitrate. | | Encrypted | Indicates whether the source is encrypted or not. | | Location | The location of the Source. | | Network | The network on which the source is hosted. | | **Inter-Cluster** | | | Bitrate | The current bitrate of the stream. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
Yes - the Priority checkbox of the Access Tag of this Source has been enabled.
No - the Priority checkbox of the Access Tag of this Source has been enabled. | | Tags | The Tag/s that is associated with this Source. | | Input | The details of the source’s input. | | Latency | The maximal latency that the stream has reached throughout time. | | Encrypted | Indicates whether the source is encrypted or not. | | Location | The location of the Source. | | Network | The network on which the source is hosted. | | Uptime | For online Sources, shows the number of hours, minutes and seconds that the Source has been online. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Source has been enabled. * No - the Priority checkbox of the Access Tag of this Source has been enabled. | | Play | Downloads a .vlc stream file that is automatically played back in the VLC player with the necessary parameters to view the Zixi stream (Requires Zixi VLC Plugin), see Viewing [Viewing Preview in VLC](docId\:RmCwt-Gw-6f2PrOG2l0ay). | | Source IP | The IP address of the Source's input resource. Transcoded – means that the source is transcoded. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | **Monitor Only** | | | Bitrate | The current bitrate of the stream. | | Uptime | For online Sources, shows the number of hours, minutes and seconds that the Source has been online. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Source has been enabled. * No - the Priority checkbox of the Access Tag of this Source has been enabled. | | Play | Downloads a .vlc stream file that is automatically played back in the VLC player with the necessary parameters to view the Zixi stream (Requires Zixi VLC Plugin), see [Viewing Preview in VLC](docId\:RmCwt-Gw-6f2PrOG2l0ay). | | Tags | The Tag/s that is associated with this Source. | | Source IP | The IP address of the Origin source component. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | Encrypted | Indicates whether the source is encrypted or not. | | Location | The location of the Source. | | Network | The network on which the source is hosted. | | **Multiplex** | | | Bitrate | The current bitrate of the stream. | | Uptime | For online Sources, shows the number of hours, minutes and seconds that the Source has been online. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Source has been enabled. * No - the Priority checkbox of the Access Tag of this Source has been enabled. | | Play | Downloads a .vlc stream file that is automatically played back in the VLC player with the necessary parameters to view the Zixi stream (Requires Zixi VLC Plugin), see [Viewing Preview in VLC](docId\:RmCwt-Gw-6f2PrOG2l0ay). | | Tags | The Tag/s that is associated with this Source. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | Encrypted | Indicates whether the source is encrypted or not. | | **Multiview** | | | Bitrate | The current bitrate of the stream. | | Uptime | For online Sources, shows the number of hours, minutes and seconds that the Source has been online. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Source has been enabled. * No - the Priority checkbox of the Access Tag of this Source has been enabled. | | Play | Downloads a .vlc stream file that is automatically played back in the VLC player with the necessary parameters to view the Zixi stream (Requires Zixi VLC Plugin), see [Viewing Preview in VLC](docId\:RmCwt-Gw-6f2PrOG2l0ay). | | Tags | The Tag/s that is associated with this Source. | | Source IP | The IP address of the Source's input resource. Transcoded – means that the source is transcoded. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | Encrypted | Indicates whether the source is encrypted or not. | | Location | The location of the Source. | | Network | The network on which the source is hosted. | | **NDI** | | | Bitrate | The current bitrate of the stream. | | Uptime | For online Sources, shows the number of hours, minutes and seconds that the Source has been online. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Play | Downloads a .vlc stream file that is automatically played back in the VLC player with the necessary parameters to view the Zixi stream (Requires Zixi VLC Plugin), see [Viewing Preview in VLC](docId\:RmCwt-Gw-6f2PrOG2l0ay). | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Source has been enabled. * No - the Priority checkbox of the Access Tag of this Source has been enabled. | | Tags | The Tag/s that is associated with this Source. | | Input | The details of the source’s input. | | Source IP | The IP address of the Source's input resource. Transcoded – means that the source is transcoded. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | Encrypted | Indicates whether the source is encrypted or not. | | **Other** | | | Bitrate | The current bitrate of the stream. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Source has been enabled. * No - the Priority checkbox of the Access Tag of this Source has been enabled. | | Tags | The Tag/s that is associated with this Source. | | Type | The type of the Source in ZEN Master e.g., Broadcaster, ZEC, Monitor Only, RIST, File etc. | | Source Password | If the source is password protected, click **Show** to display the password. | | Encrypted | Indicates whether the source is encrypted or not. | | Location | The location of the Source. | | Network | The network on which the source is hosted. | | **RTP** | | | Bitrate | The current bitrate of the stream. | | Uptime | For online Sources, shows the number of hours, minutes and seconds that the Source has been online. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Source has been enabled. * No - the Priority checkbox of the Access Tag of this Source has been enabled. | | Play | Downloads a .vlc stream file that is automatically played back in the VLC player with the necessary parameters to view the Zixi stream (Requires Zixi VLC Plugin), see [Viewing Preview in VLC](docId\:RmCwt-Gw-6f2PrOG2l0ay). | | Tags | The Tag/s that is associated with this Source. | | Input | The details of the source’s input. | | Source IP | The IP address of the Source's input resource. Transcoded – means that the source is transcoded. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | Encrypted | Indicates whether the source is encrypted or not. | | Location | The location of the Source. | | Network | The network on which the source is hosted. | | **PID Mapping** | | | Bitrate | The current bitrate of the stream. | | Uptime | For online Sources, shows the number of hours, minutes and seconds that the Source has been online. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Source has been enabled. * No - the Priority checkbox of the Access Tag of this Source has been enabled. | | Play | Downloads a .vlc stream file that is automatically played back in the VLC player with the necessary parameters to view the Zixi stream (Requires Zixi VLC Plugin), see [Viewing Preview in VLC](docId\:RmCwt-Gw-6f2PrOG2l0ay). | | Tags | The Tag/s that is associated with this Source. | | Input | The details of the source’s input. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | Encrypted | Indicates whether the source is encrypted or not. | | **Pull** | | | Bitrate | The current bitrate of the stream. | | Uptime | For online Sources, shows the number of hours, minutes and seconds that the Source has been online. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Source has been enabled. * No - the Priority checkbox of the Access Tag of this Source has been enabled. | | Play | Downloads a .vlc stream file that is automatically played back in the VLC player with the necessary parameters to view the Zixi stream (Requires Zixi VLC Plugin), see [Viewing Preview in VLC](docId\:RmCwt-Gw-6f2PrOG2l0ay). | | Tags | The Tag/s that is associated with this Source. | | Input | The details of the source’s input. | | Source IP | The IP address of the Source's input resource. Transcoded – means that the source is transcoded. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | Encrypted | Indicates whether the source is encrypted or not. | | Location | The location of the Source. | | Network | The network on which the source is hosted. | | **SRT** | | | Bitrate | The current bitrate of the stream. | | Uptime | For online Sources, shows the number of hours, minutes and seconds that the Source has been online. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Source has been enabled. * No - the Priority checkbox of the Access Tag of this Source has been enabled. | | Play | Downloads a .vlc stream file that is automatically played back in the VLC player with the necessary parameters to view the Zixi stream (Requires Zixi VLC Plugin), see [Viewing Preview in VLC](docId\:RmCwt-Gw-6f2PrOG2l0ay). | | Tags | The Tag/s that is associated with this Source. | | Input | The details of the source’s input. | | Source IP | The IP address of the Source's input resource. Transcoded – means that the source is transcoded. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | Latency | The maximal latency that the stream has reached throughout time. | | Encrypted | Indicates whether the source is encrypted or not. | | Location | The location of the Source. | | Network | The network on which the source is hosted. | | **Transcoded** | | | Bitrate | The current bitrate of the stream. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Source has been enabled. * No - the Priority checkbox of the Access Tag of this Source has been enabled. | | Tags | The Tag/s that is associated with this Source. | | Input | The details of the source’s input. | | Encrypted | Indicates whether the source is encrypted or not. | | **ZEC** | | | Bitrate | The current bitrate of the stream. | | Uptime | For online Sources, shows the number of hours, minutes and seconds that the Source has been online. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Source has been enabled. * No - the Priority checkbox of the Access Tag of this Source has been enabled. | | Play | Downloads a .vlc stream file that is automatically played back in the VLC player with the necessary parameters to view the Zixi stream (Requires Zixi VLC Plugin), see [Viewing Preview in VLC](docId\:RmCwt-Gw-6f2PrOG2l0ay). | | Tags | The Tag/s that is associated with this Source. | | Input | The details of the source’s input. | | Source IP | The IP address of the Source's input resource. Transcoded – means that the source is transcoded. | | Source Password | If the source is password protected, click **Show **to display the password. | | Latency | The maximal latency that the stream has reached throughout time. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | Encrypted | Indicates whether the source is encrypted or not. | | Location | The location of the Source. | | Network | The network on which the source is hosted. | | **Zixi** | | | Bitrate | The current bitrate of the stream. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Source has been enabled. * No - the Priority checkbox of the Access Tag of this Source has been enabled. | | Tags | The Tag/s that is associated with this Source. | | Encrypted | Indicates whether the source is encrypted or not. | [title] Actions on Sources [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/ ## Actions on a Single Source Click on one of the Sources to display information about the Source on the right-pane. On the upper right side of the **Info Pane**, you will see the following options: - **Mute/Unmute** – disables/activates notification for error/recovery events. Set the date and time when the mute will automatically be cleared by clicking on the down arrow and selecting **mute until.** - **Disable/ Enable **-Disabling a Source stops all active streams for that Source without deleting the configuration of the Source. - **Edit - **enables you to edit the Source configuration. - **Refresh - **refreshes the page. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Ui9tb65OCYuZOZ6FhySKD_image.png) By clicking on the three dots, its possible to choose: - **Mute until **– Set a date and time when the mute will automatically be cleared. - **+ Add Channel** – Create a new Channel for this Source with the parameters automatically populated with this Source's details. - **Clone **– Create an additional Source based on the settings of the selected Source. - **Config **– Click to view instructions on how to configure the Source device (e.g., Zixi enabled encoder) to connect to ZEN Master. - **Share **– Shares a link to a source object thumbnail page by sending a URL. The link can be accessed by external users, without requiring them to have a ZEN Master account. See [Sharing a Source](https://zixidocumentation.atlassian.net/wiki/spaces/ZMUG/pages/4871487489/Sharing+a+Source). - **Traceroute **– Shows the traceroutes used by the stream. - **Delete** – Deletes the Source configuration. ## Actions on Multiple Sources You can perform a more limited set of actions on multiple sources by **checking the sources** and then clicking the **Actions** menu: ![Actions on Multiple Sources](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/RRj0XRp3Ppto1r6sl07fb-20251104-152146.png) After you select an action, a confirmation dialog will appear to ensure that you want to complete the action (or cancel it instead): ::Image[]{src="https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/Dc135cdquo15WN9OLjw6z-20251104-152319.png" size="90" width="1080" height="844" position="center" alt="Confirmation of Actions on Multiple Sources" darkWidth="1080" darkHeight="844" showCaption="false"} [title] Channels [path] ZEN Master/ZEN Master User Guide/ Channels are a combination of one or more sources that are prepared for output in the ZEN system. Each channel is assigned to a specific Channel Processing Broadcaster cluster. There are six types of Channels, each involving a different process in preparing the stream for output. The following is a description of the Channel types: - **Transcoded Channel** – transcodes a single Source to multiple bitrates for output to an HTTP, S3, MediaStore or GCP Target. - **Pass-through** **Channel** – no actual processing is done on the stream. A Pass-Through Channel with a single Source simply sends the Source to an output. A Pass-Through channel with multiple Sources creates redundancy by defining parallel streams from multiple Sources as a single entity. This ensures that if one Source becomes inactive the stream will be automatically transmitted from the parallel Source. - **AWS MediaConnect Flow** - create and manage a completely new MediaConnect Flow in ZEN Master. A MediaConnect Source that was configured in ZEN Master can be assigned to the MediaConnect Flow Channel. - **AWS MediaLive Channel** – create and manage a new AWS MediaLive Channel in ZEN Master. By clicking *More Options* you can also choose: - **Adaptive Channel** – combines multiple Sources to create a unified HLS stream for output to an HTTP, S3, MediaStore or GCP Target. If you would like to create a new Channel with a configuration similar to an existing Channel you can use the Clone feature, see [Cloning a Channel](docId:8h-dmm0aWbAKXqphd8vKK). - [Channel Sources](docId\:s4BHhHfSKwKGXnd-3_OLh) - [Redundancy in ZEN Master](docId\:k9mukecY4pzgeowUJDrHH) - [Adding Transcoded Channels](docId\:xwF-mFNvRA5E3jQL2YMjU) - [Adding Pass-Through Channels](docId:4b-XOt6dB_1rg-wKrq8iu) - [Adding MediaConnect Flow Channels](docId\:VGHKldpL2Bb4KpPWwQZLq) - [Adding a AWS MediaLive Channel](docId:1RM8mcDM_28pYF0cG82dY) - [Adding Adaptive Channels](docId\:rKvnZF-Tft8VGnzZsb79b) - [Cloning a Channel](docId:8h-dmm0aWbAKXqphd8vKK) - [Viewing Existing Channels](docId\:OjRj8Lq8Uz66l32ubWb56) [title] Adding MediaConnect Flow Channels [path] ZEN Master/ZEN Master User Guide/Channels/ ZEN Master supports two different methods for integrating MediaConnect Flows. - **Method 1 - Connecting MediaConnect Flows to ZEN Master:** This method uses an independent MediaConnect Flow as a Source (as described in [Adding an AWS MediaConnect Source – Creating a ZEN Master Managed Flow](docId\:ynOP9bIsiol7ZUVi6KLMz)) or Target (as described in [Adding Zixi AWS MediaConnect Targets](docId\:E6rfLr5hPPecWd0nSWUOT)) in ZEN Master. The resultant Source or Target functions as a standard ZEN Master entity. - **Method 2 – Creating ZEN Master Managed Flows: **This method involves creating a MediaConnect Flow that is fully managed within ZEN Master. This involves creating specialized MediaConnect Sources as well as specialized MediaConnect Flow Channels in ZEN Master. This method enables you to manage the Flow completely from within ZEN Master, including interchanging between Sources and Flow Channels. There are two ways of creating these Managed Flows: - **Create a new MediaConnect Flow** - create a completely new MediaConnect Flow from the ZEN Master console (i.e. without accessing the MediaConnect console or using their APIs). This involves creating a specialized MediaConnect Source in ZEN master (as described in [Creating a New AWS MediaConnect Flow Channel](docId\:PubzSp2XgdFcXqAb5LJiO)) and then creating a specialized MediaConnect Flow Channel (as described in [Adding MediaConnect Flow Channels](docId\:VGHKldpL2Bb4KpPWwQZLq)). This enables you to work exclusively within the ZEN Master UI. - **Import an Existing MediaConnect Flow to Manage in ZEN Master** - This method involves inporting an existing Flow from MediaConnect into ZEN Master (as described in [Importing a MediaConnect Flow Channel](docId\:OH_oqC5Akr_EWESGmo7j8)). The input from your MediaConnect Flow is automatically created as a specialized MediaConnect Source in ZEN Master and the outputs are created as Targets in ZEN Master. In addition, the Flow itself is created as a specialized MediaConnect Flow Channel. All elements can be monitored and managed in ZEN Master. :::hint{type="info"} Once you have created or imported a ZEN Master Managed Flow (method 2), you should manage that Flow entirely through ZEN Master and **not** through the MediaConnect console. ::: MediaConnect Flows that are created as Channels in ZEN Master are independent of the Sources that are assigned to them so that you can swap Sources between Channels at any time. :::hint{type="info"} MediaConnect Sources created using Method 2 **must** be assigned to a special type of Channel, a MediaConnect Flow Channel. MediaConnect Sources created using Method 1 can be assigned to standard ZEN Master Channels. ::: The following sections describe the procedure for creating ZEN Master Managed Flows by creating a new Flow in ZEN Master or importing an existing Flow. For Method 1, you just create a MediaConnect Source in ZEN Master as described in [Adding an AWS MediaConnect Source – Creating a ZEN Master Managed Flow](docId\:ynOP9bIsiol7ZUVi6KLMz). - [Creating a New AWS MediaConnect Flow Channel](docId\:PubzSp2XgdFcXqAb5LJiO) - [Importing a MediaConnect Flow Channel](docId\:OH_oqC5Akr_EWESGmo7j8) [title] Adding a AWS MediaLive Channel [path] ZEN Master/ZEN Master User Guide/Channels/ AWS MedialLive service is an Elemental Transcoder that performs both transcoding (encoding) and HLS packaging in a single service. The input to the MediaLive channel must be a MediaConnect channel or an AWS Elemental Link. **Requirements:** - The input to the MediaLive channel must be a MediaConnect channel or an AWS Elemental Link. So before configuring the MediaLive channel, make sure you have a MediaConnect channel or an AWS Elemental Link configured. It is not possible to go from a Broadcaster or a MediaLive Channel directly. - Before configuring the MediaLive channel, the Target must be created and it must be enabled. If you try to attach a Target to a MediaLive channel that was not enabled, you will have to disable the MediaLive Channel then attach the Target, enable the Target and then enable the MedialLive Channel. **To create a new MediaLive Channel:** :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click** Channels**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Channel** selection menu is displayed. ![Create New Channel selection menu](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/9qvMY-FsApjKFyZ_GIVGQ_image.png) ::: :::WorkflowBlockItem Click on **AWS MediaLive Flow**. The **Create MediaLive Flow** window is displayed. ![Create MediaLive Flow window](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/tHd7ck83g0MdznacAN7z6_image.png) ::: :::WorkflowBlockItem In the **Info** section, in the** Name** field, enter a logical name for the Channel. ::: :::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 an Tag, you are relating this Channel 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 Channel. 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 In the **Configuration** section, verify that **Create New** is selected (default). ::: ::::WorkflowBlockItem In the **AWS Account** field, select from the drop-down list the AWS MediaConnect account that you would like to use for this Flow. :::hint{type="info"} If the Source does not exist in the cluster, then the cluster will pull the Source automatically. ::: :::: :::WorkflowBlockItem In the **Region** field, select from the drop-down list the AWS region that you would like to use for this Flow. ::: :::WorkflowBlockItem In the **Availability Zone** field, select from the drop-down list the Availability Zone that you would like to use for this Flow. ::: :::WorkflowBlockItem To use an existing IAM role ARN, select **Select Existing** and select an existing Role ARN from the drop-down list. ::: :::WorkflowBlockItem To specify a custom ARN, select Specify Custom ARN and enter the Amazon Resource Name in the Role ARN ::: ::::WorkflowBlockItem In the **Source** field, select one of the following: - **AWS MediaConnect Flow** - select this option if you want to place a MediaConnect Flow be fore the MediaLive channel. Select from the drop-down list the AWS MediaConnect Flow that you would like to assign to this Channel. :::hint{type="info"} Specifying a Source is optional. You can create a Channel without assigning a Source, although it won’t be activated until you assign a Source at a later time. You can also switch to a different Source at a later time. To learn about creating a MediaConnect Source, see [Adding an AWS MediaConnect Source – Creating a ZEN Master Managed Flow](docId\:ynOP9bIsiol7ZUVi6KLMz). ::: - **AWS Elemental Link** - AWS Medialive Link Source AWS Account and Region must match settings above. Select the AWS Elemental Link Source from the drop down menu. :::: :::WorkflowBlockItem In the **Initial State** section, select the **Disabled** checkbox if you would like to disable this Channel upon initial configuration. ::: ::::WorkflowBlockItem Select the **Muted** checkbox if you would like to disable error/recovery notifications for this Channel upon initial configuration. :::hint{type="info"} You can Enable/Unmute the Channel at any time. ::: :::: :::WorkflowBlockItem Click **Save**. ::: ::::: **New MediaLive Channel Configuration Parameters Table** | **Parameter** | **Description** | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the MediaConnect Flow Channel 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 Channel 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 Channel. 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. | | ***Configuration*** | Verify that **Create New** is selected (default). | | AWS Account | Select from the drop-down list the AWS MediaConnect account that you would like to use for this Flow.
Note: If the Source does not exist in the cluster, then the cluster will pull the Source automatically. | | Region | Select from the drop-down list the AWS region that you would like to use for this Flow. | | Availability Zone | Select from the drop-down list the Availability Zone that you would like to use for this Flow. | | IAM Role | Select **Select Existing** or **Specify Custom ARN**. | | Role ARN | For *Select Existing:*
Select from the drop-down list an existing Role ARN of the IAM role that you previously created.
For *Specify Custom ARN:*
Enter a specific ARN in the field. | | Source | Select from the drop-down list the AWS MediaConnect type Source that you would like to assign to this Channel.
Note: Specifying a **Source** is optional. You can create a Channel without assigning a Source, although it won’t be activated until you assign a Source at a later time. You can also switch to a different Source at a later time. To learn about creating a MediaConnect Source, see [Adding an AWS MediaConnect Source – Creating a ZEN Master Managed Flow](docId\:ynOP9bIsiol7ZUVi6KLMz). | | *Initial State* | | | Disabled | Select this checkbox if you would like to disable this Channel upon initial configuration. | | Muted | Select this checkbox if you would like to disable error/recovery notifications for this Channel upon initial configuration. | [title] Adding Pass-Through Channels [path] ZEN Master/ZEN Master User Guide/Channels/ Pass-Through channels do not involve any actual processing to the stream. A Pass-Through Channel with a single Source simply sends the Source to an output. A Pass-Through Channel with multiple Sources creates redundancy by defining parallel streams from multiple Sources as a single entity. This ensures that if one Source becomes inactive the stream will be automatically transmitted from the parallel Source. To learn more about redundancy in ZEN Master see [Redundancy in ZEN Master](docId\:k9mukecY4pzgeowUJDrHH) . The following procedure describes how to add a Pass-Through Channel in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. **To add a Pass-Through channel:** :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click** Channels**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Channel** selection menu is displayed. ![Create New Channel selection menu](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/9qvMY-FsApjKFyZ_GIVGQ_image.png) ::: :::WorkflowBlockItem Click on **Pass-Through**. The **Create Pass-Through Channel** window is displayed. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-1NJiOOGtA2jCiGrNcs4H5-20250727-132122.png) ::: :::WorkflowBlockItem In the **Info** section, in the** Name** field, enter a logical name for the Channel. ::: :::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 an Tag, you are relating this Channel 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 Channel. 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 In the **Configuration** section, in the **Processing Cluster** field, select from the drop-down list one of the Channel Processing clusters that has been configured in ZEN Master. The selected cluster will be used to process this Channel. :::hint{type="info"} - If the Source does not exist in the cluster, then the cluster will pull the Source automatically. ::: :::: ::::WorkflowBlockItem In the **Target Broadcaster/s** field, select your broadcaster preference. Either select a specific broadcaster to be used OR specify your preference for using primary vs. backup broadcasters. Options are: *Primary Broadcasters only, Backup Broadcasters only* or *Any*. :::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 If you want to configure an alternative path for disaster recovery, in the **Alternative Channel (Disaster Recovery)** field, select the Channel that will be used as the alternative path. For more details, see [Disaster Recovery (Alternative Path)](docId\:poo4ZS1-ZjRa1snDylqE0). ::: ::::WorkflowBlockItem In the** Sources** section, add one or more Sources to the Channel and designate whether it should be used as a backup source for redundancy. 1. Find the Source that you would like to add either by scrolling through the list of available Sources or by entering a search word into the **Filter** If the Source that you would like to add is not yet configured in ZEN Master, see [Sources](docId\:WrXQ4NJAqG_e7h-u3v0de)**.** 2. Add a Source by clicking the button next to the Source. The Source is moved to the top of the list, above the **Filter** 3. To designate the Source as a backup, select the **Backup** 4. Repeat the above procedure for each Source that you would like to add to the Channel. :::hint{type="info"} - If you would like to remove a selected Source, click on the **-** button next to the Source. - All Access Tags that are assigned to the selected Sources are added by default to the Channel. ::: :::: :::WorkflowBlockItem In the **Initial State** section, select the **Disabled** checkbox if you would like to disable this Channel upon initial configuration. ::: ::::WorkflowBlockItem Select the **Muted** checkbox if you would like to disable error/recovery notifications for this Channel upon initial configuration. :::hint{type="info"} You can Enable/Unmute the Channel at any time. ::: :::: :::WorkflowBlockItem If you would like to customize, click **Advanced**). The **Advanced** settings are displayed. ![Advanced settings](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/_8J-7bUX3W86LDVsjIjcx_image.png) ::: :::WorkflowBlockItem Click **Save**. ::: ::::: **Pass-Through Channel Configuration Parameters Table** | **Parameter** | **Description** | | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | ***Info*** | | | Name | Specify a name for the Transcoded Channel 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 Channel 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 Channel. 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. | | ***Configuration*** | | | Processing Cluster | Select from the drop-down list one of the Channel Processing clusters that has been configured in ZEN Master. The selected cluster will be used to process this Channel.
Note: If the Source does not exist in the cluster, then the cluster will pull the Source automatically. | | Target Broadcaster/s | Select your broadcaster preference. 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. | | Alternative Channel (Disaster Recovery) | Enables reverting an entire path after the Source (i.e., Channel/Broadcaster to the Target) to go through an alternative path, which is usually hosted on an alternative cloud/region. The redirection to the alternative path is manual. So, in case of a fault, if there is no time to troubleshoot a problem, this mechanism allows the user to select the feed that has an issue, click a button and revert the stream to go through a pre-configured alternative path.
For example, if you have a Channel and a Broadcaster on GCP and a secondary Channel and Broadcaster on Azure. If something goes wrong with the GCP path, you can click the Go to Alternative button and failover everything to Azure. | | Sources | Select from the drop-down list the desired Source. | | ***Initial State*** | | | Disabled | Select this checkbox if you would like to disable this Channel upon initial configuration. | | Muted | Select this checkbox if you would like to disable error/recovery notifications for this Channel upon initial configuration. | | ***Advanced*** | | | External ID | The ID that is used when integrating ZEN Master with an external ESNI/ESAM server. For more detail, contact your Zixi representative. | [title] Connecting a Stream from a Zixi-Enabled Device (Encoder UI) [path] ZEN Master/ZEN Master User Guide/Sources/Adding ZEN Master Sources/Adding a Zixi Source – Other-Enabled Device/ If you have added a source from a Zixi-enabled device, you will need to configure it on the encoder in order to connect it to ZEN Master. The UI structure varies for different Zixi-enabled encoders, however the following settings should be configured to connect to ZEN Master. **To connect a Zixi-enabled encoder:** 1. In **ZEN Master**, in the main navigation, click **Sources**. 2. Select the relevant source from the list of Sources. 3. In the **Details** pane at the bottom of the screen, click the **Manual Configuration **tab. This tab contains specific configuration settings for the selected Source. Use the values shown for the following parameters to configure the Zixi Enabled encoder: | **Parameter** | **Description** | | ------------- | ----------------------------------------------------------- | | **Host** | The IP address/URL of the ZEN Master host. | | **Password** | The access password that has been configured in ZEN Master. | | **Port** | The port that has been configured in ZEN Master. | | **Stream ID** | The stream name. | [title] Adding a Zixi-Feeder MediaConnect Source [path] ZEN Master/ZEN Master User Guide/Sources/Adding AWS Media Sources/Adding an AWS MediaConnect Source/Adding a Zixi-protocol MediaConnect Source/ You can add an input from a Zixi Feeder to an AWS MediaConnect Ingest Cluster to be managed as a source in ZEN. In this case, the Feeder is referred to as the **Origin Feeder** which streams to the **Ingest Cluster**. The streaming uses the Zixi protocol. Once the AWS MediaConnect Flow channel is configured, ZEN Master will automatically configure the component to push the stream to the relevant MediaConnect Flow. ![Zixi-Feeder MediaConnect Diagram](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/PNZUnGVa1f9Od9qcY6mhd_image.png) It is possible to 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. You can specify which NICs are used for Bonding or you can select *Automatic* to enable ZEN Master to divide the bandwidth evenly among all available NICs.  You can select several inputs from a single Feeder to simultaneously create a new Source for each input. The following procedure describes how to add a Zixi Feeder MediaConnect Source . In addition, an explanation of each of the configuration parameters is given in the table below. **To create a Zixi-Feeder MediaConnect Source:** :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The Create New Source window is displayed. ![Create New Source window](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/AxSEVtTg03J7Up0wQFdjQ_image.png) ::: :::WorkflowBlockItem Under **AWS Media**, click on **AWS MediaConnect**. The Create New AWS Media Source window opens. ![Create New AWS Media Source window](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/crH-vf3TZurFRDhdc8vJj_image.png) ::: :::WorkflowBlockItem In the **Info **section, in the **Name** field, type a logical name for the 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. *Events Profiles* consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. ::: :::WorkflowBlockItem In the **Input** section, under **Protocol**, select the **Zixi** radio button.  ::: :::WorkflowBlockItem In the **Application** section, select **Feeder**. For a Zixi Feeder that is managed by ZEN Master, ZEN Master automatically configures the Feeder to push the stream to MediaConnect. ::: :::WorkflowBlockItem In the **Feeder **field, select from the drop-down list one of the available Feeders. ::: :::WorkflowBlockItem In the **Bonding **section, select the radio button for the desired bonding mode. Options are: - **None** (default) – no bonding - **Manual** – you specify which NICs are used for bonding - ** Auto** – all available NICs are used for bonding ::: :::WorkflowBlockItem If you selected *None* for **Bonding**, then in the **Feeder Output NIC** field, you would need 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 selected **Manual** for **Bonding**, then in the **Feeder Output NIC** field, use the following procedure to specify which NICs are used. Select two or more NICs by clicking the **+ **button for each of the desired NICs. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/e4iW-cY2q7YYbNnE4EPbq_image.png" size="80" width="750" height="387" position="center" alt="Select NICs for Bonding" showCaption="false"} Selected NICs are shown above the Filter box. (You can remove an NIC by clicking the **- **button for that NIC). ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/mp0xBMEeMvumD8MlObJYg_image.png" size="80" width="755" height="380" position="center" alt="Remove NICs from Selection" showCaption="false"} 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. :::hint{type="info"} If the **Backup** checkbox is not selected then this NIC is used in parallel with the other selected NICs. ::: :::: :::WorkflowBlockItem In the **Latency \[ms]** field, select the latency time for the stream (default 4000). ::: :::WorkflowBlockItem You are required by MediaConnect to enter a valid **Whitelist CIDR block**. The whitelist CIDR block is a range of IP addresses that should be allowed to contribute content to your source. These IP addresses must be in the form of a Classless Inter-Domain Routing block. For example, 10.0.0.0/16. Through source needs to be in the range covered by this CIDR block. Any IP address with this range is allowed to send content to this flow. ::: :::WorkflowBlockItem In the **Initial State** section, select the **Muted** checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. You can **Unmute** the Source at any time. ::: :::WorkflowBlockItem Click **Save**. ::: ::::: **Parameters Table** | **Parameter** | **Description** | | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the AWS Media 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. | | ***Input*** | | | Protocol | To create a Zixi Input AWS Media Source, verify that **Zixi** is selected (default). | | Application | Select **Feeder**. For a Zixi Feeder that is managed by ZEN Master, ZEN Master automatically configures the Feeder to push the stream to MediaConnect. | | Feeder | Select from the drop-down list the desired Feeder. | | Feeder Input | Select from the drop-down list one of the Inputs that are available on the selected Feeder. | | Bonding | Select the desired bonding mode. Options are:
* **None** (default) – no bonding * **Manual** – you specify which NICs are used for bonding * **Auto** – all available NICs are used for bonding | | Feeder Output NIC/s (for *None* and *Manual* bonding) | 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 Manual for Bonding, 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. | | Max Bitrate | Select from the drop-down list the maximum bitrate for this Source.
Make sure that the value is greater than the max bitrate for the input. The default is set automatically based on the current bitrate of the input. | | Latency \[ms] | Specify the latency time for the stream (default 4000). | | Whitelist CIDR Block | Specify the CIDR for the range of IPs that you would like to allow to contribute content to this Source.
You are required by MediaConnect to enter a valid Whitelist CIDR block. | | ***Initial State*** | | | Muted | Select this checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. | [title] Broadcaster History System [path] ZEN Master/ZEN Master User Guide/Broadcasters/Viewing Existing Clusters/Viewing Existing Broadcasters/Broadcaster History/ The System graph shows system performance metrics over time. For broadcasters that are using NVIDIA GPU for transcoding, the graph shows the GPU usage of the encoder pipeline, decoder pipeline and CUDA pipeline. The GPU memory consumption is also shown. ![Broadcaster History System Graph](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/vretusjuFHERrq_2E8gB6_image.png) ZEN Master shows data for the following parameters in the System graph: - **VOD HDD **– The hard drive utilization for VOD. - **System HDD **– The hard drive utilization of the Broadcaster. - **CPU **– The CPU utilization level. - **Memory **– The memory utilization level. [title] Adding an SRT-protocol MediaConnect Source [path] ZEN Master/ZEN Master User Guide/Sources/Adding AWS Media Sources/Adding an AWS MediaConnect Source/ **To create a SRT MediaConnect Source:** ::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The Create New Source window is displayed. ![Create New Source window](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/AxSEVtTg03J7Up0wQFdjQ_image.png) ::: :::WorkflowBlockItem Under **AWS Media**, click on **AWS MediaConnect**. The Create New AWS Media Source window opens. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-3WYtnQ77aDiZoB8xGhwCl-20250713-112557.png) ::: :::WorkflowBlockItem In the **Info **section, in the **Name** field, type a logical name for the 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. *Events Profiles* consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. ::: :::WorkflowBlockItem In the **Input** section, under **Protocol**, select the **SRT Push (Listener)** radio button.  ::: :::WorkflowBlockItem In the **Ingest Port** field, enter the port that the Flow will listen on for incoming content. ::: :::WorkflowBlockItem In the **Max Bitrate** field, enter the maximum bitrate to be used on this NIC. ::: :::WorkflowBlockItem In the **Latency **\[ms] field, select the latency time for the stream (default 4000). ::: :::WorkflowBlockItem You are required by MediaConnect to enter a valid **Whitelist CIDR block**. The whitelist CIDR block is a range of IP addresses that should be allowed to contribute content to your source. These IP addresses must be in the form of a Classless Inter-Domain Routing block. For example, 10.0.0.0/16. Through source needs to be in the range covered by this CIDR block. Any IP address with this range is allowed to send content to this flow. ::: :::WorkflowBlockItem In the **Initial State** section, select the **Muted** checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. You can Unmute the Source at any time. ::: :::WorkflowBlockItem Click **Save**. ::: :::: **Parameters Table** | **Parameter** | **Description** | | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the AWS Media 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. | | ***Input*** | | | Protocol | To create a SRT protocol Input AWS Media Source, verify that SRT Push (Listener) is selected. | | Ingest Port | Enter the port that the Flow will listen on for incoming content. | | Max Bitrate | Select from the drop-down list the maximum bitrate for this Source.
Make sure that the value is greater than the max bitrate for the input. The default is set automatically based on the current bitrate of the input. | | Latency (ms) | Select the latency time for the stream (default 4000). | | Whitelist CIDR Block | Specify the CIDR for the range of IPs that you would like to allow to contribute content to this Source.
You are required by MediaConnect to enter a valid Whitelist CIDR block. | | ***Initial State*** | | | Muted | Select this checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. | [title] Adding AWS Media Sources [path] ZEN Master/ZEN Master User Guide/Sources/ In the AWS Media Sources options, the AWS MediaConnect Flow service or the AWS MediaLive serves as the “Ingests Cluster”, replacing the Broadcaster Cluster of the ZEN Master Sources options. The following Sources can be added as AWS Media Sources: - [Adding an AWS MediaConnect Source](docId:6XCPTtsxg9FAg5KmiWue5) - Create a Source to use with an AWS MediaConnect Flow. - [Adding an Elemental Link Source](docId\:DPvTZ8aJZ6HOBGDaYVY4A) - Source from AWS Elemental Link device to AWS MediaLive. [title] Importing a MediaConnect Flow Channel [path] ZEN Master/ZEN Master User Guide/Channels/Adding MediaConnect Flow Channels/ **To import an existing MediaConnect Flow Channel:** :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click** Channels**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Channel** selection menu is displayed. ![Create New Channel selection menu](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/9qvMY-FsApjKFyZ_GIVGQ_image.png) ::: :::WorkflowBlockItem Click on **AWS MediaConnect Flow**. The **Create MediaConnect Flow** window is displayed. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-0PpvmiTkyMKA1tFHp4vls-20250727-140841.png) ::: :::WorkflowBlockItem In the **Info** section, in the** Name** field, enter a logical name for the Channel. ::: :::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 an Tag, you are relating this Channel 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 Channel. 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 In the **Configuration** section, select **Import Existing**. ::: ::::WorkflowBlockItem In the **AWS Account** field, select from the drop-down list the AWS MediaConnect account that you would like to use for this Flow. :::hint{type="info"} If the Source does not exist in the cluster, then the cluster will pull the Source automatically. ::: :::: :::WorkflowBlockItem In the **Region** field, select from the drop-down list the AWS region that you would like to use for this Flow. ::: :::WorkflowBlockItem In the **AWS MediaConnect Flow** field, select from the drop-down list the Flow from which you would like to create this Channel. ::: ::::WorkflowBlockItem In the **Source** field, select from the drop-down list the AWS MediaConnect type Source that you would like to assign to this Channel. :::hint{type="info"} Specifying a **Source** is optional. You can create a Channel without assigning a Source, although it won’t be activated until you assign a Source at a later time. You can also switch to a different Source at a later time. To learn about creating a MediaConnect Source, see [Adding an AWS MediaConnect Source – Creating a ZEN Master Managed Flow](docId\:ynOP9bIsiol7ZUVi6KLMz) . ::: :::: ::::WorkflowBlockItem In the Initial State, select the **Muted** checkbox if you would like to disable error/recovery notifications for this Channel upon initial configuration. :::hint{type="info"} You can Enable/Unmute the Channel at any time. ::: :::: :::WorkflowBlockItem Click **Save**. ::: ::::: **Import MediaConnect Flow Channel Configuration Parameters Table** | **Parameter** | **Description** | | ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the MediaConnect Flow Channel 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 Channel 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 Channel. 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. | | ***Configuration*** | Select **Import Existing**. | | AWS Account | Select from the drop-down list the AWS MediaConnect account that you would like to use for this Flow.
Note: If the Source does not exist in the cluster, then the cluster will pull the Source automatically. | | Region | Select from the drop-down list the AWS region that you would like to use for this Flow. | | AWS MediaConnect Flow | Select from the drop-down list the Flow from which you would like to create this Channel. | | *Initial State* | | | Muted | Select this checkbox if you would like to disable error/recovery notifications for this Channel upon initial configuration. | [title] Adding a Zixi-protocol MediaConnect Source [path] ZEN Master/ZEN Master User Guide/Sources/Adding AWS Media Sources/Adding an AWS MediaConnect Source/ - [Adding a Zixi-Feeder MediaConnect Source](docId\:qprlN1i3asa3MHjHkHGmu) - [Adding a Zixi-Broadcaster MediaConnect Source](docId\:phjQLilB55V6QyYgb1a2i) - [Adding a Zixi-ZEC MediaConnect Source](docId\:KrKH4IY4VCEjAzs-E74wV) - [Adding a Zixi-Other MediaConnect Source](docId\:C2CdgBA_Mv0bDIedn0MmN) [title] Broadcaster History UDP [path] ZEN Master/ZEN Master User Guide/Broadcasters/Viewing Existing Clusters/Viewing Existing Broadcasters/Broadcaster History/ **­**This graph shows a graphical representation of the UDP Receive and Send Errors that occurred over time. The graph includes the following: - **UDP Receive Errors** - indicates the number of UDP Receive errors over time. If there are 10 errors at a certain point in time the value in the Y-axis will go up to 10. - **UDP Send Errors** - indicates the number of a UDP Send error over time. If there are 10 errors at a certain point in time the value in the Y-axis will go up to 10. ![Broadcaster History UDP Graph](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/BhZI5ZCbccj6KFUH4ihq8_image.png) [title] Adding Broadcasters to a Cluster [path] ZEN Master/ZEN Master User Guide/Broadcasters/Creating a Broadcaster Cluster/ After creating a Broadcaster cluster, you need to add one or more Broadcasters to the cluster in order for the cluster to become functional. Assign the appropriate number of Broadcasters and type of instances according to the load that you plan on using on the cluster. - [Adding a Broadcaster to a Manual Cluster](docId\:xYscySO498lY77ZjQr-51) - [Adding Broadcasters to a Managed Cluster](docId\:dVW_b0TjsUGUzCq2ffKVS) [title] Source Configuration [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/ For sources from Zixi enabled-devices (i.e. 'Configure & Monitor (Other)'), this tab contains specific configuration settings for the selected Source. When configuring a Source from a resource that is not managed in ZEN Master, you will need to use these settings to enable ZEN Master to connect to the encoder (see [Connecting a Stream from a Zixi-Enabled Device (Encoder UI)](docId\:bjr4vrAM5n_7U6j6H393N)). [title] Broadcaster History Network [path] ZEN Master/ZEN Master User Guide/Broadcasters/Viewing Existing Clusters/Viewing Existing Broadcasters/Broadcaster History/ **­**This graph shows network activity over time. This includes the following: - **Received Bitrate** - the bitrate amount (in Mb/s) of incoming traffic. - ![Broadcaster History Network Graph](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/zc8fLmfwUs8N2S2UwK4iy_image.png) [title] Adding a Source – Transcoded [path] ZEN Master/ZEN Master User Guide/Sources/Adding ZEN Master Sources/ You can create a transcoded Source based on an existing Source. The transcoding parameters are set by selecting one of the pre-configured transcoding profiles. The transcoded Source can then be added to a Pass-Through Channel making it available to various types of Targets such as YouTube Live or Facebook Live using RTMP protocol. The following procedure describes how to add a Transcoded Source in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. :::hint{type="info"} For a comparison of transcoders - codecs and color support - see [Comparison of Transcoders: Video Codec and Color Support](docId:0kUGUMogtknAKZY-UG6Qs). ::: ## To add a Transcoded Source: :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Source selection** window is displayed. ![Create Source Options](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-3mXDQJHXUppSRZJSBYBnR-20250805-132303.png) ::: :::WorkflowBlockItem Click on **Transcoded**. The **Create New Transcoded Source** window opens. ![New Source Transcoded](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-XySBnYnshESjXiYTEOlQm-20250519-165115.png) ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, enter a unique name to identify this Source in the system. ::: :::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 **Input** section, in the **Source** field, select from the drop-down list the Source that the transcoded source is based on. ::: :::WorkflowBlockItem In the **Configuration **section, in the **Ingest Cluster** field, select from the drop-down list the Ingest Cluster on which the Sources that you would like to group together are located. ::: ::::WorkflowBlockItem In the **Target Broadcaster/s** field, specify which Broadcaster/s within the cluster on which ZEN Master can deploy the source. Either select a specific broadcaster (for Manual clusters) 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 **Transcoding Profile** field, select one of the pre-configured transcoding profiles to apply to this source. If you would like to create a new transcoding profile, see [Adding Transcoding Profiles](docId:3L1DNIo6v_15jzCFdhRKN) . ::: :::WorkflowBlockItem If you would like to preserve closed captions for this Source, verify that the **Preserve closed captions **checkbox is selected (default). ::: :::WorkflowBlockItem If you would like to crop the input stream, select the **Crop** checkbox and set the cropping parameters as follows: ![cropping parameters ](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/-EzRG9f7kanY_-NuPojT0_image.png) 1. In the **Units** section, select the type of units used to define the crop. Options are: *Pixels* or *Percentages*. 2. Enter the crop position for each of the parameters *Left*, *Top*, *Width* and *Height* in the appropriate fields. ::: ::::WorkflowBlockItem If you would like to assign the transcoding process to a multi GPU Broadcaster, select the **Assign to GPU** checkbox, and then select from the drop-down list the desired GPU instance. Options are: 0 (default), 1, 2 and 3. :::hint{type="info"} This feature is useful if you are running several heavy transcoding activities, as it enables you to distribute the load among several different GPUs. ::: :::: :::WorkflowBlockItem In the **Pad to CBR** field, enter the amount of CBR padding to be added (in kbps). ::: :::WorkflowBlockItem In the **Configuration** section, select the **Alert on PID changes** checkbox if you would like to generate email notifications whenever a PID change is detected. ::: ::::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 Additional SCTE-35 options are available when you expand the SCTE-35 Manipulation section: ![SCTE-35 Manipulation](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/FxvVWM-bhpg9ZdVYW_LCl-20251104-153319.png) Here you can: - Enable SCTE-35 Manipulation - Specify the length of a search window for a NULL packet for SCTE-35 intertion - Set the SCTE-35 PID - Remove any existing SCTE-35 messages from the stream See the **Parameters Table** below for an explanation of these options. ::: :::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 Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. :::hint{type="info"} Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: If you would like to monitor CEA-708 closed captions, select **Monitor CEA-708 **checkbox**.** :::hint{type="info"} If Monitoring CEA-708 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: :::: ::::WorkflowBlockItem If you would like to disable auto-pull, select the **Disable Auto-Pull** 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. (Default: 1000 ms) ::: ::::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 Select the **Ignore Transcode Thresholds** checkbox if you would like to override the Transcode thresholds on your Ingest Cluster (i.e. to allow use of full CPU/GPU and memory capacity). ::: :::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: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/o8ps8fSlaqV0B45MqIh0A_transcoded-source-advanced.png) ::: :::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 In the **Encoder** dropdown, you can choose to Auto Detect the original encoding, NVIDIA, H.264, or H.265 (HEVC): ![Encoder options](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/b77Z4neULK5pXHp9QPlwx-20260401-221155.png) ::: :::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 Select **Force I-Frames on SCTE-35 markers** if a SCTE35 marker is detected and it contains a specific video timestamp (PTS), the encoder will generate an IDR-frame on the video frame with the closest or equal timestamp. If there is no timestamp in the SCTE35 marker, the transcoder will generate an IDR frame as soon as it can ::: :::WorkflowBlockItem In the **HTML Overlay URL** field, if you want to include an HTML overlay on the stream, such as a scoreboard, enter the URL of the HTML. The external HTML will be pulled directly to the processing Broadcaster and rendered over the transcoded video output. For more information, see [HTML Overlay Installation](docId:1svyta7P777nBTqPN8yt8) . ::: :::WorkflowBlockItem Click **Save**. ::: ::::: ## Transcoded Source Configuration Parameters Table | **Parameter** | **Description** | | --------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the Transcoded 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*** | | | Source | Select from the drop-down list the Source that the transcoded Source is based on. | | ***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. | | Transcoding Profile | Select one of the pre-configured transcoding profiles to apply to this Source. If you would like to create a new transcoding profile, see [Adding Transcoding Profiles](docId:3L1DNIo6v_15jzCFdhRKN) . | | Preserve closed captions | If you would like to preserve closed captions for this Source, select this checkbox (default). | | Crop | If you would like to crop the input stream, select this checkbox and set the cropping parameters as follows:
1) In the Units section, select the type of units used to define the crop. Options are: Pixels or Percentages. 2) Enter the crop position for each of the parameters Left, Top, Width and Height in the appropriate fields. | | Assign to GPU | Select this checkbox if you would like to assign the transcoding process to a multi GPU Broadcaster, and then select from the drop-down list the desired GPU instance. Options are: 0 (default), 1, 2, and 3
Note: this feature is useful if you are running several heavy transcoding activities, as it enables you to distribute the load among several different GPUs. | | Pad to CBR \[kbps] | Specify the amount of CBR padding to be added (in kbps).
This parameter is optional. If you do not specify a TS Bitrate, the transport stream will be variable bitrate (VBR) with no additional null packets added. If you specify a bitrate, the transport stream will be constant bitrate (CBR) where null packets are added as necessary to achieve the specified bitrate.
CBR transport streams are typically required when sending a stream to a satellite head-end or to a professional integrated receiver-decoder (IRD). The overhead of MPEG TS is about 7%. To determine the bitrate setting, sum the max video bitrate and audio bitrate from the encoding profile and then add the other PIDs (if choosing to pass all PIDs) and add 7%. If the bitrate needed for the transport stream exceeds the value specified, the Broadcaster will give a “bitrate too low” error message.
VBR transport streams are typically used for HLS, DASH, RTMP, and other similar live streaming workflows. | | Alert on PID changes | If you would like to generate email notifications whenever a PID change is detected, select this checkbox. | | Log SCTE-35 | If you would like to log SCTE-35 markers for this stream, select this checkbox.
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. | | Monitor CEA-608 Closed Captions | If you would like to monitor CEA-608 closed captions, select this checkbox.
**Note:** Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. | | Monitor CEA-708 Closed Captions | If you would like to monitor CEA-708 closed captions, select this checkbox.
**Note:** Monitoring 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 desired latency for auto-pull actions. (Default: 1,000 ms) | | Ignore Transcode Thresholds | Select this checkbox if you would like to override the Transcode thresholds for your Ingest Cluster (i.e. to allow use of full CPU/GPU and memory capacity). | | ***SCTE-35 Manipulation *** | | | Enable SCTE-35 Manipulation | Select checkbox to enable SCTE-35 Manipulation. | | SCTE-35 PID | Set the SCTE-35 PID in which the messages will be inserted. | | Remove Existing SCTE-35 | Remove any existing SCTE-35 messages from the stream. | | NULL Packet Search Window (ms) | Look for a NULL packet 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 | | ***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/recovery notifications for this Source upon initial configuration. | | ***Advanced*** | | | 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. | | Auto Pull MTU | Specify the maximum transmission unit (largest data packet that a network-connected device will accept) in bytes for the Auto Pull. | | Encoder | If you would like to specify a specific encoder to use for transcoding (decode and reencode processes), select the desired option from the drop down menu. By default, if there is an Nvidia GPU available, it would auto detect and use that, however you can override this behavior by selecting a different option from the list. | | Frozen Video Minimal Duration | 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 | 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. | | Force I-Frames on SCTE-35 markers | Selecting this option will do the following:
* If a SCTE35 marker is detected and it contains a specific video timestamp (PTS), the encoder will generate an IDR-frame on the video frame with the closest or equal timestamp. * If there is no timestamp in the SCTE35 marker, the transcoder will generate an IDR frame as soon as it can. | | HTML Overlay URL | If you want to include an HTML overlay on the stream, such as a scoreboard, enter the URL of the HTML. The external HTML will be pulled directly to the processing Broadcaster and rendered over the transcoded video output. For more information, see [HTML Overlay Installation](docId:1svyta7P777nBTqPN8yt8). | | Use HTML overlay for audio | Select this checkbox to use the audio channel in the HTML overlay feed. | | Overlay Audio PID | Specify the PID of the overlay audio. | | Transcode TSID | Specify the Transport Stream ID in the PAT that allows downstream receivers to uniquely identify transport streams within a delivery network. | [title] Adding a Source - SRT [path] ZEN Master/ZEN Master User Guide/Sources/Adding ZEN Master Sources/ ZEN Master can receive a Source directly from an SRT input. :::hint{type="info"} When this method is used, the stream is not protected by the Zixi protocol. ::: ZEN Master can receive SRT streams that are sent using either *Push* or *Pull *method. :::hint{type="success"} Reference: Broadcaster versions and their associated SRT Library Version 19 - SRT Library 1.5.4 Version 18 - SRT Library 1.5.4 Version 17 - SRT Library 1.5.3 Version 16 - SRT Library 1.4.4 ::: The following procedure describes how to add an SRT Source in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. ## To add an SRT Source: :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Source selection** window is displayed. ![Create Source Options](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-3mXDQJHXUppSRZJSBYBnR-20250805-132303.png) ::: :::WorkflowBlockItem Click on **SRT**. The **Create New SRT Source** window opens. ![New SRT Source](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/FqyxS5NQRdqUPdepoOT7s-20251104-201839.png) ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, enter a unique name to identify this Source in the system. ::: :::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 **SRT Configuration **section, under **Mode**, select the mode used to send the stream. Options are: *Push (Listener)* or *Pull (Caller)*. ::: :::WorkflowBlockItem Select the **Verify Stream ID** checkbox to verify that the stream ID of this input matches the stream ID in the SRT feed before allowing the connection ::: :::WorkflowBlockItem If you selected *Pull (Caller)* mode, then in the **Host** field, enter the hostname of the SRT server. ::: ::::WorkflowBlockItem In the Port field, specify the port to listen on for the incoming content. :::hint{type="warning"} This port must be open on all firewalls between the Ingest Cluster and the input device. ::: :::: ::::WorkflowBlockItem In the **Max Bitrate** field, select from the drop-down list the maximum bitrate for this Source. :::hint{type="info"} Make sure that the value is greater than the max bitrate of the input. **If you are unsure of the max bitrate, set the value to approximately twice the actual (average) bitrate.** The default is set automatically based on the current bitrate of the input. See [High Max Bitrate Configuration](docId\:IJrN4V8zGysjoKXEVCkHx). ::: :::: :::WorkflowBlockItem If you are using a password to authenticate this SRT connection, then in the **Password** field, enter the password. The password must be identical (case sensitive) to the password configured on the SRT server. ::: :::WorkflowBlockItem In the **Source Configuration** section, 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 preference. 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 **Input NIC** 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 In the **Latency** field, enter the latency in milliseconds (default: *1000*) ::: ::::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 [Adding PID Mapping Profiles](docId\:gFTCaYurPL7DInoUyd14z). ::: :::: :::WorkflowBlockItem Select the **Alert on PID changes** checkbox if you would like to generate email notifications whenever a PID change is detected. ::: ::::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 :::hint{type="info"} Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: If you would like to monitor CEA-608 closed captions, select **Monitor CEA-608 **checkbox**.** If you would like to monitor CEA-708 closed captions, select **Monitor CEA-708 **checkbox**.** :::hint{type="info"} Monitoring CEA-708 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: :::: ::::WorkflowBlockItem If you would like to disable auto-pull, select the **Disable Auto-Pull** 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. (Default: 1000 ms) ::: ::::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 Additional SCTE-35 options are available when you expand the **SCTE-35 Manipulation** section: ![SCTE-35 Manipulation](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/FxvVWM-bhpg9ZdVYW_LCl-20251104-153319.png) Here you can: - Enable SCTE-35 Insertion - Specify the length of a search window for a NULL packet for SCTE-35 intertion - Set the SCTE-35 PID - Remove any existing SCTE-35 messages from the stream See the **Parameters Table** below for an explanation of these options. ::: :::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 Under **Error Concealment,** click the Enable Error Concealment checkbox to enable the following error concealment mechanisms that can correct transaport stream for downstream IRDs: :::Paragraph{indent="1"} 1\. **Continuous Timeline** - corrects errors that are related to timeline jumps in the source. This mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input. ::: :::Paragraph{indent="1"} 2\. **Replace Frames** - If there are frames with CC errors, it replaces them with skip frames (inserts the last good frame received in place of missing ones). This solves issues such as an IRD that lost synchronization when it received broken frames. This mechanism also creates a variant of the input (doubling the input). ::: :::Paragraph{indent="1"} 3\. **Renumber CC **- The Continuity Counter is part of the TS encapsulation. When there are CC errors in TR101 analysis it means that the counter has a gap due to the lost frames. This mechanism can re-write the CC counter for the downstream devices, so they will see a continuous increase of the counter. ::: :::Paragraph{indent="1"} 4\. **Delay (ms) **- Enter the delay that the Error Concealment adds to the stream in miliseconds. Error Concealment needs to buffer the stream to analyze it. One second is a reasonable value. Lower values may cause the Error Concealment to not be able to fix some of the frames. ::: :::Paragraph{indent="1"} 5\. **CBR Padding** - enter a value for the rate at which padding will be added to maintain a specific output transport bitrate. For example, if you have a video bitrate at 5000 kbps or that varies from 3000-5000 kbps and audio at 64 kbps, total bitrate will be max 5064 kbps or min 3064 kbps. With CBR padding set at 6000 kbps, 6000 kbps is being delivered downstream at all times, ensuring a consistent bitrate. ::: :::Paragraph{indent="1"} 6.** PCR Interval** - Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. This depends on standard used by downstream encoders or decoders. Options include: ::: :::Paragraph{listStyleType="disc" indent="2"} ATSC standard - 100 ms ::: :::Paragraph{listStyleType="disc" indent="2"} DVB standard - 40 ms ::: 7. **Remux Buffer Size** - Specify the time added for remuxing the stream (default: 2500 ms). 8. **Smoothing** - Time added for smoothing a bursty stream - adds to latency, but produces a smoother output. See [Improving Stream Resiliency: Error Correction and Concealment](docId:9_OLo1Argk_2aDoSHYFBb) for more information. ![Error Concealment Options](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/jEyT42FS_YflpTNxqCc9Q_zm-error-concealment-options.png) :::: :::WorkflowBlockItem If you would like to adjust the advanced settings, click **Advanced**. The **Advanced** settings fields are displayed: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/u9aqLnI5X2jGFol7lhMsh_srt-source-advanced-options.png) ::: :::WorkflowBlockItem You can select the version of SRT to use - Zixi uses the latest version, so you should only do this if the systems in your workflow use a earlier version that is not compatible with the current one. ::: :::WorkflowBlockItem If you would like to track usage for this Source, enter your **Billing Code** details. See [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ). ::: :::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 Click **Save**. ::: ::::: ## SRT Source Configuration Parameters Table | **Parameter** | **Description** | | ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | ***Info*** | | | Name | Specify a name for the SRT 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. | | ***SRT Configuration*** | | | Mode | To create an SRT Source, select the mode used for sending the stream. Options are: *Push (Listener)* or *Pull (Caller)*. | | Verify Stream ID | Select this option to verify that the stream ID of this input matches the stream ID in the SRT feed before allowing the connection. | | Host (for *Pull (Caller)*) | Enter the hostname for the SRT server. | | Port | Specify the port to listen on for the incoming content.
This port must be open on all firewalls between the Ingest Cluster and the input device. | | Max Bitrate | Select from the drop-down list the maximum bitrate for this Source.
Max Bitrate is used by the Broadcaster to determine buffer size when processing the transport stream - it does not cap the bitrate. We recommend setting it to 1.5x or 2x the actual (average) bitrate. Setting the max bitrate too low may result in dropped frames and other issues. | | Password | If you are using a password to authenticate this SRT connection, then enter the password in this field. The password must be identical (case sensitive) to the password configured on the SRT server. | | ***Source 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 | If you would like to specify which NIC is used, 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 1000). | | 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. | | Log SCTE-35 | Select this checkbox if kyou 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 | Disables the Source thumbnail from appearing in the Sources list and other places. Disabling thumbnail may improve system performance. | | Monitor CEA-608 Closed Captions | If you would like to monitor CEA-608 closed captions, select this checkbox.
**Note:** Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. | | Monitor CEA-708 Closed Captions | If you would like to monitor CEA-708 closed captions, select this checkbox.
**Note:** Monitoring 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 desired latency for auto-pull actions. (Default: 1,000 ms) | | 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. | | ***SCTE-35 Manipulation ***
| | | Enable SCTE-35 Manipulation | Select checkbox to enable SCTE-35 Manipulation. | | SCTE-35 PID | Set the SCTE-35 PID in which the messages will be inserted. | | Remove Existing SCTE-35 | Remove any existing SCTE-35 messages from the stream. | | NULL Packet Search Window (ms) | Replace any existing SCTE-35 messages with NULL. | | ***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/recovery notifications for this Source upon initial configuration. | | ***Error Concealment*** | | | Enable Error Concealment | Select this checkbox to enable the error concealment mechanisms listed below to correct transport stream for downstream IRDs. | | Continuous Timeline | Corrects errors that are related to timeline jumps in the source. This mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input. | | Replace Frames | If there are frames with CC errors, it replaces them with skip frames (inserts the last good frame received in place of missing ones). This solves issues such as an IRD that lost synchronization when it received broken frames. This mechanism also creates a variant of the input (doubling the input). | | Renumber CC | encapsulation. When there are CC errors in TR101 analysis it means that the counter has a gap due to the lost frames. This mechanism can re-write the CC counter for the downstream devices, so they will see a continuous increase of the counter. | | Delay (ms) | Enter the delay that the Error Concealment adds to the stream in miliseconds. Error Concealment needs to buffer the stream to analyze it. One second is a reasonable value. Lower values may cause the Error Concealment to not be able to fix some of the fra | | CBR Padding (kbps) | Enter a value for the rate at which padding will be added to maintain a specific output transport bitrate. For example, if you have a video bitrate at 5000 kbps or that varies from 3000-5000 kbps and audio at 64 kbps, total bitrate will be max 5064 kbps or min 3064 kbps. With CBR padding set at 6000 kbps, 6000 kbps is being delivered downstream at all times, ensuring a consistent bitrate. | | PCR Interval (ms) | Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. Options include:
* ATSC standard - 100 ms * DVB standard - 40 ms
| | ***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+) | | Billing Password | Enter the password that corresponds to this billing code. | | Auto-Pull Billing Code | Specify the maximum transmission unit (largest data packet that a network-connected device will accept) in bytes for the Auto Pull. | | Auto-Pull Billing Password | Enter the password that corresponds to this auto-pull billing code. | | 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. | | Apply Input NIC selection to network device | Select this checkbox to apply Input NIC selection to the network device. | | 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 for empty audio streams to prevent false warnings - enter a comma-delimited list of PID numbers that should not be monitored for null content. | [title] Adding a Zixi-Other MediaConnect Source [path] ZEN Master/ZEN Master User Guide/Sources/Adding AWS Media Sources/Adding an AWS MediaConnect Source/Adding a Zixi-protocol MediaConnect Source/ You can configure an input from a Zixi-enabled device (i.e. a Zixi-enabled encoder) to be used as a source in ZEN Master. In this case, the Zixi-enabled device is referred to as the **Origin Other** which streams to the **Ingest Cluster**. The Origin Other is not managed by ZEN Master. However, since ZEN Master is connected to AWS MediaConnect it is possible to start/stop the stream from ZEN Master. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-jCXAAN-Jg3zKx53JdNn7m-20250714-094918.png) **To create a Zixi-Other MediaConnect Source:** ::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The Create New Source window is displayed. ![Create New Source window](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/AxSEVtTg03J7Up0wQFdjQ_image.png) ::: :::WorkflowBlockItem Under **AWS Media**, click on **AWS MediaConnect**. The Create New AWS Media Source window opens. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-QBQTMkUlkfGf5UAdHkU00-20250629-134027.png) ::: :::WorkflowBlockItem In the **Info **section, in the **Name** field, type a logical name for the 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. *Events Profiles* consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. ::: :::WorkflowBlockItem In the **Input** section, under **Protocol**, select the **Zixi** radio button.  ::: :::WorkflowBlockItem In the **Application** section, select **Other**. ::: :::WorkflowBlockItem In the **Max Bitrate** field, enter the maximum bitrate to be used on this NIC. ::: :::WorkflowBlockItem In the **Latency \[ms]** field, select the latency time for the stream (default 4000). ::: :::WorkflowBlockItem You are required by MediaConnect to enter a valid **Whitelist CIDR block**. The whitelist CIDR block is a range of IP addresses that should be allowed to contribute content to your source. These IP addresses must be in the form of a Classless Inter-Domain Routing block. For example, 10.0.0.0/16. Through source needs to be in the range covered by this CIDR block. Any IP address with this range is allowed to send content to this flow. ::: :::WorkflowBlockItem In the **Initial State** section, select the **Muted** checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. You can **Unmute **the Source at any time. ::: :::WorkflowBlockItem Click **Save**. ::: :::: **Parameters Table** | **Parameter** | **Description** | | ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the AWS Media 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. | | ***Input*** | | | Protocol | To create a Zixi Input AWS Media Source, verify that **Zixi** is selected (default). | | Application | Select **OTHER**. This Zixi Feeder is not managed by ZEN Master. | | Max Bitrate | Select from the drop-down list the maximum bitrate for this Source.
Make sure that the value is greater than the max bitrate for the input. The default is set automatically based on the current bitrate of the input. | | Latency \[ms] | Specify the latency time for the stream (default 4000). | | ***Source Configuration***
| | | Whitelist CIDR Block | Specify the CIDR for the range of IPs that you would like to allow to contribute content to this Source.
You are required by MediaConnect to enter a valid Whitelist CIDR block. | | ***Initial State*** | | | Muted | Select this checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. | [title] Adding an RTP-FEC-protocol MediaConnect Source [path] ZEN Master/ZEN Master User Guide/Sources/Adding AWS Media Sources/Adding an AWS MediaConnect Source/ **To create a RTP-FEC MediaConnect Source:** ::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The Create New Source window is displayed. ![Create New Source window](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/AxSEVtTg03J7Up0wQFdjQ_image.png) ::: :::WorkflowBlockItem Under **AWS Media**, click on **AWS MediaConnect**. The Create New AWS Media Source window opens. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-6WQqDANrgPv2tg_KDkkwE-20250706-125542.png) ::: :::WorkflowBlockItem In the **Info **section, in the **Name** field, type a logical name for the 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. *Events Profiles* consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. ::: :::WorkflowBlockItem In the **Input** section, under **Protocol**, select the **RTP-FEC** radio button.  ::: :::WorkflowBlockItem In the **Ingest Port** field, enter the port that the Flow will listen on for incoming content. ::: :::WorkflowBlockItem In the **Max Bitrate** field, enter the maximum bitrate to be used on this NIC. ::: :::WorkflowBlockItem You are required by MediaConnect to enter a valid **Whitelist CIDR block**. The whitelist CIDR block is a range of IP addresses that should be allowed to contribute content to your source. These IP addresses must be in the form of a Classless Inter-Domain Routing block. For example, 10.0.0.0/16. Through source needs to be in the range covered by this CIDR block. Any IP address with this range is allowed to send content to this flow. ::: :::WorkflowBlockItem In the **Initial State** section, select the **Muted** checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. You can Unmute the Source at any time. ::: :::WorkflowBlockItem Click **Save**. ::: :::: **Parameters Table** | **Parameter** | **Description** | | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the AWS Media 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. | | ***Input*** | | | Protocol | To create a RTP-FEC Input AWS Media Source, verify that RTP-FEC is selected. | | Ingest Port | Enter the port that the Flow will listen on for incoming content. | | Max Bitrate | Select from the drop-down list the maximum bitrate for this Source.
Make sure that the value is greater than the max bitrate for the input. The default is set automatically based on the current bitrate of the input. | | Whitelist CIDR Block | Specify the CIDR for the range of IPs that you would like to allow to contribute content to this Source.
You are required by MediaConnect to enter a valid Whitelist CIDR block. | | ***Initial State*** | | | Muted | Select this checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. | [title] Adding an AWS MediaConnect Source [path] ZEN Master/ZEN Master User Guide/Sources/Adding AWS Media Sources/Adding an AWS MediaConnect Source/ This Source is configured on an **AWS MediaConnect** that serves as the **Ingest Object**. The stream originates from an **AWS Elemental Link** device, which serves as the **Origin**. The Origin is not managed by ZEN Master. However, since ZEN Master is connected to AWS MediaConnect and AWS MediaConnect is connected to the AWS Elemental Link, by enabling/disabling the Source you are also starting/stoping the stream through ZEN Master. :::hint{type="info"} At the time of the Source configuration the spcific AWS MediaConnect component doesn't have to be necessarily running. The AWS MediaConnect component can be started at a later time and it may, in turn, start the stream, which is coming from the connected AWS Elemental Link. ::: ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-3HO5WSJY24cmfcnp_IRZ6-20250724-132304.png) The following procedure describes how to add an AWS Elemental Link MediaConnect Source. In addition, an explanation of each of the configuration parameters is given in the table below. **To create an AWS Elemental Link MediaConnect Source:** ::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Source** window is displayed. ![Create New Source window](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/AxSEVtTg03J7Up0wQFdjQ_image.png) ::: :::WorkflowBlockItem Under **AWS Media**, click on **AWS MediaConnect**. The **Create New AWS Media Source** window opens. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-ZfzLN_WjYQQauGkCnCqk5-20250817-103256.png) ::: :::WorkflowBlockItem In the **Info **section, in the **Name** field, type a logical name for the 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. *Events Profiles* consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. ::: :::WorkflowBlockItem In the **Input** section, under **Protocol**, select the AWS Elemental Link radio button.  ::: :::WorkflowBlockItem Under the **Source Configuration** section, in the AWS Account field, select from the drop-down the AWS account that matches the AWS account of the AWS MediaConnect Channel that serves as the Ingest Object. ::: :::WorkflowBlockItem In the **Region **field, select from the drop-down list the AWS region that matches the AWS MediaConnect Channel that serves as the Ingest Object. ::: :::WorkflowBlockItem In the **AWS Elemental Link** field, select the AWS Elemental Link device that serves as the Origin. The origin AWS Elemental Link has to be registered to the AWS Account. ::: :::WorkflowBlockItem In the **Initial State** section, select the **Muted **checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. You can Unmute the Source at any time. ::: :::WorkflowBlockItem Click **Save**. ::: :::: **Parameters Table** | **Parameter** | **Description** | | ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the AWS Media 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. | | ***Input*** | | | AWS Elemental Link radio button | In the Input section, under Protocol, select the AWS Elemental Link radio button. | | ***Source Configuration*** | | | AWS Account | Under the Source Configuration section, in the AWS Account field, select from the drop-down the AWS account that matches the AWS account of the AWS MediaConnect Channel that serves as the Ingest Object. | | Region | In the Region field, select from the drop-down list the AWS region that matches the AWS MediaConnect Channel that serves as the Ingest Object. | | | | | ***Initial State*** | | | Muted | Select this checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. | [title] Adding an Elemental Link Source [path] ZEN Master/ZEN Master User Guide/Sources/Adding AWS Media Sources/ This Source is configured on an **AWS MediaLive** that serves as the **Ingest Object**. The stream originates from an **AWS Elemental Link** device, which serves as the **Origin**. The Origin is not managed by ZEN Master. However, since ZEN Master is connected to AWS MediaLive and AWS MediaLive is connected to the AWS Elemental Link, by enabling/disabling the Source you are also starting/stoping the stream through ZEN Master. :::hint{type="info"} At the time of the Source configuration the spcific AWS MediaLive component doesn't have to be necessarily running. The AWS MediaLive component can be started at a later time and it may, in turn, start the stream, which is coming from the connected AWS Elemental Link. ::: ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-MOwEeZD35qtZyD05EqfiD-20250710-114123.png) The following procedure describes how to add an Elemental Link Source. In addition, an explanation of each of the configuration parameters is given in the table below. **To create an Elemental Link Source:** ::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Source** window is displayed. ![Create New Source window](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/AxSEVtTg03J7Up0wQFdjQ_image.png) ::: :::WorkflowBlockItem Under **AWS Media**, click on **AWS Elemental Link**. The **Create New AWS Elemental Link Source** window opens. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-vup77MDM5pnpK6f63M6LJ-20250713-114029.png) ::: :::WorkflowBlockItem In the **Info **section, in the **Name** field, type a logical name for the 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. *Events Profiles* consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. ::: :::WorkflowBlockItem Under the **Source Configuration** section, in the **AWS Account **field, select from the drop-down the AWS account that matches the AWS account of the AWS Medialive Channel that serves as the **Ingest Object**. ::: :::WorkflowBlockItem In the **Region** field, select from the drop-down list the AWS region that matches the AWS Medialive Channel that serves as the Ingest Object. ::: :::WorkflowBlockItem In the **AWS Elemental Link** field, select the AWS Elemental Link device that serves as the **Origin**. The origin AWS Elemental Link has to be registered to the **AWS Account**. ::: :::WorkflowBlockItem In the **Initial State** section, select the **Muted** checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. You can Unmute the Source at any time. ::: :::WorkflowBlockItem Click **Save**. ::: :::: **Parameters Table** | **Parameter** | **Description** | | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the AWS Media 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. | | ***Source Configuration*** | | | AWS Account | Under the Source Configuration section, in the AWS Account field, select from the drop-down the AWS account that matches the AWS account of the AWS Medialive Channel that serves as the Ingest Object. | | Region | In the Region field, select from the drop-down list the AWS region that matches the AWS Medialive Channel that serves as the Ingest Object. | | AWS Elemental Link | In the AWS Elemental Link field, select the AWS Elemental Link device that serves as the Origin. The origin AWS Elemental Link has to be registered to the **AWS Account**. | | ***Initial State*** | | | Muted | Select this checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. | [title] Viewing Existing Sources [path] ZEN Master/ZEN Master User Guide/Sources/ The Sources screen displays all existing sources, and information about the status and configuration of each source. It is possible to add more columns to the list. If you want to view resources that were marked as Priority, add the Priority column and sort by it. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/0IvN3-WT_-Z9qJVFIE5-j-20260118-122532.jpg) The main display includes the following data and actions for each source: | **Parameter** | **Description** | | -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Name | Name of the Source. | | Status | The connection status of the source. | | Event | The Events section shows all the events that have been generated by the system that relate to the selected Source (e.g. connections, errors, and disconnections). | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Broadcaster | Shows a list of the Broadcasters that are related to this source and data about the Broadcasters. | | Type | The type of the Source in ZEN Master e.g., Broadcaster, ZEC, Monitor Only, RIST, File etc. | | Input | The details of the source’s input. | | TR101 | An indicator of the TR101 analysis. There are two indicators, P1 for high priority warnings and P2 for low priority warnings.
Green – no current errors
Red – there are current errors | | IP | The IP of the remote device as seen by ZEN Master. | | Bitrate | The stream's current bitrate, when streaming. | | Uptime | The time period that the source has been online. | | Alt. Path | Specifies if an Alternative Path has been configured or not. The Alternative Path is configured through the Broadcaster Cluster or the Channel configuration screens and attached to a target by following the instructions in [Attaching a Target to an Alternative Path](docId\:Cf1NmnbVZxuSnsMEaEmkr). | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. Priority Sources are indicated with a 'v'. | | Tags | The Tag/s that is associated with this Remote Access Profile. | | Shared | Indicates that the Source has been shared. | | PID Mapping | The PID Mapping Profile used for the PID mapping in the Source. | | Billing Code | Billing codes are used to identify and differentiate traffic. | When a Source is selected, the current data about the Source is displayed in the **Info pane**. The Info pane displays statistical data about the current state of the Source. Each Source type displays different statistics, see [Source Info Pane](docId\:VybGOZcLBl0-3h-yfHP92) for more details. - [Actions on Sources](docId:7RiDbifG03IGgIwYl9E8X) - [Viewing Preview in VLC](docId\:RmCwt-Gw-6f2PrOG2l0ay) - [Source Info Pane](docId\:VybGOZcLBl0-3h-yfHP92) - [Source Stream](docId\:dbcol69jr73U2Wy3SOFGw) - [Source Details](docId:24DluW1rPZPo8fRJZIEve) - [Source Sources (for Failover)](docId\:n7VIQR5-7Jl8H5VQyfkgY) - [Source Content Analysis](docId\:xFDKQoErtqJ1DveJY6rh5) - [Source History](docId:7zapE3l6cY_1Z0vz9mxC-) - [Source Health](docId\:u9HiSo79St8XRe5r1aPq6) - [Source Events](docId\:BWvxQ5RR5hOxfayi7v0wm) - [Source SCTE-35 Log](docId\:IW9uyevxz7I_Rtg2Z4ygy) - [Source Configuration](docId\:DPEbtrZLUShfLw88bdOtK) - [Source Notes](docId\:n7DP26yF5BU4u601nOzFo) - [Source Change Tracking](docId\:XcDZiIQf7cKdcBQxq1RRz) - [Source Incidents](docId\:kb7ZcVmh6e47eFw99oIwN) - [Source Traceroute](docId\:oqfgWM3R_gfsOSPCaX-LY) [title] Updating the Broadcaster API Password [path] ZEN Master/ZEN Master User Guide/Broadcasters/Creating a Broadcaster Cluster/Adding Broadcasters to a Cluster/Adding a Broadcaster to a Manual Cluster/ If you update the **admin password** on a Broadcaster, it is important that you update it in ZEN Master also, so that ZEN Master can continue to manage the Broadcaster. ::::WorkflowBlock :::WorkflowBlockItem In ZEN Master, go to the **Broadcasters** section. ::: :::WorkflowBlockItem Click on the **Broadcasters** button at the top to get a list of Broadcasters and find the one you changed the password for: ![Broadcaster List](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-xzh5z8T6kZ63l4o3vc-Ps-20250801-193601.png) ::: :::WorkflowBlockItem Click on the Broadcaster to reveal the details and then click the **Edit icon** in the top-right portion of the screen to edit it: ![Edit Broadcaster](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-GJ8mc3SnR6GQv0Zn7hayt-20250801-194121.png) ::: :::WorkflowBlockItem In the **Edit Broadcaster** screen, enter the new admin password for the Broadcaster in the **API Password **field and click **Save**. ::: :::: [title] Adding a Source - Demux [path] ZEN Master/ZEN Master User Guide/Sources/Adding ZEN Master Sources/ The Demux source can be used to demux an MPTS (Multi Program Transport Streams) stream into single SPTS (Single Program Transport Streams) streams by creating the Demux Source on a Broadcaster. To create a demux source, make sure you have an MPTS source. The following procedure describes how to add an Demux Source in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. ## To add a Demux Source: :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Source selection** window is displayed. ![Create Source Options](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-3mXDQJHXUppSRZJSBYBnR-20250805-132303.png) ::: :::WorkflowBlockItem Click on **Demux**. The **Create New Demux Source** window opens. ![Create New Demux Source](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/dEVWv-T3NpAyJ6wp46kAT-20251105-161040.png) ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, enter a unique name to identify this Source in the system. ::: :::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 **Input** section, under **Source**, select an MPTS source from the list. ::: :::WorkflowBlockItem In the **Program Number** field, select the program for which you want to create a separate SPTS stream. ::: :::WorkflowBlockItem In the **Pad to CBR** field, specify the amount of CBR padding to be added (in kbps). This parameter is optional. If you do not specify a TS Bitrate, the transport stream will be variable bitrate (VBR) with no additional null packets added. If you specify a bitrate, the transport stream will be constant bitrate (CBR) where null packets are added as necessary to achieve the specified bitrate. ::: :::WorkflowBlockItem In the **PCR Interval** field, select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. Options include: - ATSC standard - 100 ms - DVB standard - 40 ms ::: ::::WorkflowBlockItem In the **Max Bitrate** field, select from the drop-down list the maximum bitrate for this Source. :::hint{type="info"} 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. ::: :::: :::WorkflowBlockItem In the** Configuration** section, 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 preference. 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 Select the **Alert on PID changes** checkbox if you would like to generate email notifications whenever a PID change is detected. ::: ::::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. ::: ::::WorkflowBlockItem :::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 closed captions, select **Monitor CEA-608 **checkbox**.** :::hint{type="info"} Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: If you would like to monitor CEA-708 closed captions, select **Monitor CEA-708 **checkbox**.** :::hint{type="info"} Monitoring CEA-708 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: :::: ::::WorkflowBlockItem If you would like to disable auto-pull, select the **Disable Auto-Pull** 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. (Default: 1000 ms) ::: ::::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 Additional SCTE-35 options are available when you expand the **SCTE-35 Manipulation** section: ![SCTE-35 Manipulation](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/FxvVWM-bhpg9ZdVYW_LCl-20251104-153319.png) Here you can: - Enable SCTE-35 Manipulation - Specify the length of a search window for a NULL packet for SCTE-35 intertion - Set the SCTE-35 PID - Remove any existing SCTE-35 messages from the stream See the **Parameters Table** below for an explanation of these options. ::: ::::WorkflowBlockItem In the Initial State section, select the Disabled checkbox if you would like to disable this Source upon initial configuration. 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 Under **Error Concealment,** click the Enable Error Concealment checkbox to enable the following error concealment mechanisms that can correct transaport stream for downstream IRDs: :::Paragraph{indent="1"} 1\. **Continuous Timeline** - corrects errors that are related to timeline jumps in the source. This mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input. ::: :::Paragraph{indent="1"} 2\. **Replace Frames** - If there are frames with CC errors, it replaces them with skip frames (inserts the last good frame received in place of missing ones). This solves issues such as an IRD that lost synchronization when it received broken frames. This mechanism also creates a variant of the input (doubling the input). ::: :::Paragraph{indent="1"} 3\. **Renumber CC **- The Continuity Counter is part of the TS encapsulation. When there are CC errors in TR101 analysis it means that the counter has a gap due to the lost frames. This mechanism can re-write the CC counter for the downstream devices, so they will see a continuous increase of the counter. ::: :::Paragraph{indent="1"} 4\. **Delay (ms) **- Enter the delay that the Error Concealment adds to the stream in miliseconds. Error Concealment needs to buffer the stream to analyze it. One second is a reasonable value. Lower values may cause the Error Concealment to not be able to fix some of the frames. ::: :::Paragraph{indent="1"} 5\. **CBR Padding** - enter a value for the rate at which padding will be added to maintain a specific output transport bitrate. For example, if you have a video bitrate at 5000 kbps or that varies from 3000-5000 kbps and audio at 64 kbps, total bitrate will be max 5064 kbps or min 3064 kbps. With CBR padding set at 6000 kbps, 6000 kbps is being delivered downstream at all times, ensuring a consistent bitrate. ::: :::Paragraph{indent="1"} 6.** PCR Interval** - Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. This depends on standard used by downstream encoders or decoders. Options include: ::: :::Paragraph{listStyleType="disc" indent="2"} ATSC standard - 100 ms ::: :::Paragraph{listStyleType="disc" indent="2"} DVB standard - 40 ms ::: 7. **Remux Buffer Size** - Specify the time added for remuxing the stream (default: 2500 ms). 8. **Smoothing** - Time added for smoothing a bursty stream - adds to latency, but produces a smoother output. See [Improving Stream Resiliency: Error Correction and Concealment](docId:9_OLo1Argk_2aDoSHYFBb) for more information. ![Error Concealment Options](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/jEyT42FS_YflpTNxqCc9Q_zm-error-concealment-options.png) :::: :::WorkflowBlockItem If you would like to adjust the advanced settings, click **Advanced**. The **Advanced** settings fields are displayed: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/RkwEfR8KDIaxHJmXYJzoS_demux-source-advanced.png) ::: :::WorkflowBlockItem If you would like to track usage for this Source, enter your **Billing Code** details. See [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ). ::: :::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 apply Input NIC selection to the network device, select the **Apply Input NIC selection to network device** checkbox ::: :::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 Click **Save**. ::: ::::: ### Demux Source Configuration Parameters Table | Parameter | Description | | ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the Demux 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*** | | | Source | Select an MPTS source from the list. | | Program Number | Select the program for which you want to create a separate SPTS stream. | | Pad to CBR | Specify the amount of CBR padding to be added (in kbps). This parameter is optional. If you do not specify a TS Bitrate, the transport stream will be variable bitrate (VBR) with no additional null packets added. If you specify a bitrate, the transport stream will be constant bitrate (CBR) where null packets are added as necessary to achieve the specified bitrate. | | PCR Interval (ms) | Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. Options include:
* ATSC standard - 100 ms * DVB standard - 40 ms | | Max Bitrate | 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. | | ***Configuration*** | | | Ingest Cluster | Select from the drop-down list one of the available Ingest Clusters as the destination for the Source. | | Target Broadcaster/s | 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.*
**Note**: For managed clusters, it is not recommended to select a specific Broadcaster, as the Broadcaster’s availability may not remain stable. | | Alert on PID changes | If you would like to generate email notifications whenever a PID change is detected, select this checkbox. | | 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. | | 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 | Disables the Source thumbnail from appearing in the Sources list and other places. Disabling thumbnail may improve system performance. | | Monitor CEA-608 Closed Captions | If you would like to monitor CEA-608 closed captions, select this checkbox.
Note: Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. | | Monitor CEA-708 Closed Captions | If you would like to monitor CEA-708 closed captions, select this checkbox.
Note: Monitoring 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 desired latency for auto-pull actions. (Default: 1,000 ms) | | 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. | | ***SCTE-35 Manipulation *** | | | Enable SCTE-35 Manipulation | Select checkbox to enable SCTE-35 Manipulation. | | SCTE-35 PID | Set the SCTE-35 PID in which the messages will be inserted. | | Remove Existing SCTE-35 | Remove any existing SCTE-35 messages from the stream. | | NULL Packet Search Window (ms) | Look for a NULL packet 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 | | ***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/recovery notifications for this Source upon initial configuration. | | ***Error Concealment*** |

| | Enable Error Concealment | Select this checkbox to enable the error concealment mechanisms listed below to correct transport stream for downstream IRDs. | | Continuous Timeline | Corrects errors that are related to timeline jumps in the source. This mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input. | | Replace Frames | If there are frames with CC errors, it replaces them with skip frames (inserts the last good frame received in place of missing ones). This solves issues such as an IRD that lost synchronization when it received broken frames. This mechanism also creates a variant of the input (doubling the input). | | Renumber CC | encapsulation. When there are CC errors in TR101 analysis it means that the counter has a gap due to the lost frames. This mechanism can re-write the CC counter for the downstream devices, so they will see a continuous increase of the counter. | | Delay (ms) | Enter the delay that the Error Concealment adds to the stream in miliseconds. Error Concealment needs to buffer the stream to analyze it. One second is a reasonable value. Lower values may cause the Error Concealment to not be able to fix some of the frames. | | CBR Padding (kbps) | Enter a value for the rate at which padding will be added to maintain a specific output transport bitrate. For example, if you have a video bitrate at 5000 kbps or that varies from 3000-5000 kbps and audio at 64 kbps, total bitrate will be max 5064 kbps or min 3064 kbps. With CBR padding set at 6000 kbps, 6000 kbps is being delivered downstream at all times, ensuring a consistent bitrate. | | PCR Interval (ms) | Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. Options include:
* ATSC standard - 100 ms * DVB standard - 40 ms | | ***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+) | | 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
| Specify the maximum transmission unit (largest data packet that a network-connected device will accept) in bytes for the Auto Pull. | | Auto-Pull Billing Password
| Enter the password that corresponds to this auto-pull billing code. | | 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. | | Apply Input NIC selection to network device | Select this checkbox to apply Input NIC selection to the network device. | | 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 for empty audio streams to prevent false warnings - enter a comma-delimited list of PID numbers that should not be monitored for null content. | [title] Adding a Source - MPTS Multiplex [path] ZEN Master/ZEN Master User Guide/Sources/Adding ZEN Master Sources/ The MPTS (Multi Program Transport Streams) Multiplex source takes multiple SPTS sources and combines them to a single grouped feed with multiple video tracks. A typical use case would be bundling a group of separate programs together to be distributed as cable channels for more efficient transmission. The MPTS should have a Target bitrate that is higher than the sum of all of the effective bitrates of the individual streams included in the multiplex source. The process involves selecting multiple sources from the list of existing sources. Each source will become a Program in the MPTS source. You will need to name the program and can optionally specify a Program number (by default the first program number is 0). This program number will be assigned to the program in the newly created MPTS. The following procedure describes how to add a Multiplex Source in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. ## To add a Multiplex Source: :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Source selection** window is displayed. ![Create Source Options](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-3mXDQJHXUppSRZJSBYBnR-20250805-132303.png) ::: :::WorkflowBlockItem Click on **MPTS** **Multiplex**. The **Create New MPTS Multiplex Source** window opens. ![Create New MPTS Multiplex Source](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/UGt42wPO8OzaRJBdxcFA7-20251105-162510.png) ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, enter a unique name to identify this Source in the system. ::: :::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** Configuration** section, 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 preference. 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 Under **Sources**, in the **Target Bitrate (kbps)** filed, specify the target bitrate for the multiplex stream in kbps. The target bitrate number should be at least as high as the sum of all of the effective bitrates of the individual sources included in the multiplex source. ::: :::WorkflowBlockItem From the **Sources** list, select the relevant sources to add them to the Multiplex source and specify the following settings when they are added to the table below the selector: - In the **Program Name** field, enter a name for the program. This overwrites any pre-existing Program Name previously assigned to the stream. - In the **Program **field, enter a program number for the SPTS source. This overwrites any pre-existing program number previously assigned to the source. - In the **Base PID**, enter a Base PID number for the STPS source. Zixi will automatically assign new PID numbers for all PIDs in the SPTS stream with consecutive numbers following the Base PID number based on this number. ::: :::WorkflowBlockItem Select the **Alert on PID changes** checkbox if you would like to generate email notifications whenever a PID change is detected. ::: ::::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 closed captions, select **Monitor CEA-608 **checkbox**.** ::: ::::WorkflowBlockItem :::hint{type="info"} Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: If you would like to monitor CEA-708 closed captions, select **Monitor CEA-708 **checkbox**.** :::hint{type="info"} Monitoring CEA-708 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: :::: ::::WorkflowBlockItem If you would like to disable auto-pull, select the **Disable Auto-Pull** 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. (Default: 1000 ms) ::: ::::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 Additional SCTE-35 options are available when you expand the** SCTE-35 Manipulation** section: ![SCTE-35 Manipulation](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/FxvVWM-bhpg9ZdVYW_LCl-20251104-153319.png) Here you can: - Enable SCTE-35 Manipulation - Specify the length of a search window for a NULL packet for SCTE-35 intertion - Set the SCTE-35 PID - Remove any existing SCTE-35 messages from the stream See the **Parameters Table** below for an explanation of these options. ::: :::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 Under **Error Concealment,** click the Enable Error Concealment checkbox to enable the following error concealment mechanisms that can correct transaport stream for downstream IRDs: :::Paragraph{indent="1"} 1\. **Continuous Timeline** - corrects errors that are related to timeline jumps in the source. This mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input. ::: :::Paragraph{indent="1"} 2\. **Replace Frames** - If there are frames with CC errors, it replaces them with skip frames (inserts the last good frame received in place of missing ones). This solves issues such as an IRD that lost synchronization when it received broken frames. This mechanism also creates a variant of the input (doubling the input). ::: :::Paragraph{indent="1"} 3\. **Renumber CC **- The Continuity Counter is part of the TS encapsulation. When there are CC errors in TR101 analysis it means that the counter has a gap due to the lost frames. This mechanism can re-write the CC counter for the downstream devices, so they will see a continuous increase of the counter. ::: :::Paragraph{indent="1"} 4\. **Delay (ms) **- Enter the delay that the Error Concealment adds to the stream in miliseconds. Error Concealment needs to buffer the stream to analyze it. One second is a reasonable value. Lower values may cause the Error Concealment to not be able to fix some of the frames. ::: :::Paragraph{indent="1"} 5\. **CBR Padding** - enter a value for the rate at which padding will be added to maintain a specific output transport bitrate. For example, if you have a video bitrate at 5000 kbps or that varies from 3000-5000 kbps and audio at 64 kbps, total bitrate will be max 5064 kbps or min 3064 kbps. With CBR padding set at 6000 kbps, 6000 kbps is being delivered downstream at all times, ensuring a consistent bitrate. ::: :::Paragraph{indent="1"} 6.** PCR Interval** - Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. This depends on standard used by downstream encoders or decoders. Options include: ::: :::Paragraph{listStyleType="disc" indent="2"} ATSC standard - 100 ms ::: :::Paragraph{listStyleType="disc" indent="2"} DVB standard - 40 ms ::: 7. **Remux Buffer Size** - Specify the time added for remuxing the stream (default: 2500 ms). 8. **Smoothing** - Time added for smoothing a bursty stream - adds to latency, but produces a smoother output. See [Improving Stream Resiliency: Error Correction and Concealment](docId:9_OLo1Argk_2aDoSHYFBb) for more information. ![Error Concealment Options](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/jEyT42FS_YflpTNxqCc9Q_zm-error-concealment-options.png) :::: :::WorkflowBlockItem If you would like to adjust the advanced settings, click **Advanced**. The **Advanced** settings fields are displayed: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/rFDhcfneI2PHGEenRNP53_mpts-source-advanced.png) ::: :::WorkflowBlockItem If you would like to track usage for this Source, enter your **Billing Code** details. See [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ). ::: :::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 apply Input NIC selection to the network device, select the **Apply Input NIC selection to network device** checkbox ::: :::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 Click **Save**. ::: ::::: ## Multiplex Source Configuration Parameters Table | **Parameter** | **Description** | | ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the Multiplex 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. | | ***Configuration*** | | | Ingest Cluster | Select from the drop-down list one of the available Ingest Clusters as the destination for the Source. | | Target Broadcaster/s | 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.*
**Note**: For managed clusters, it is not recommended to select a specific Broadcaster, as the Broadcaster’s availability may not remain stable. | | ***Sources*** | | | Target Bitrate\[kbps] | Specify the target bitrate for the multiplex stream in kbps. The target bitrate number should be at least as high as the sum of all of the effective bitrates of the individual STPS sources included in the multiplex source. | | Sources | Click the **+** button on the relevant sources to add them to the Multiplex source. | | Program Name | Enter a name for the program. This overwrites any pre-existing Program Name previously assigned to the stream. | | Program | Enter a program number for the SPTS source. This overwrites any pre-existing program number previously assigned to the source. | | Base PID | Enter a Base PID number for the SPTS source. Zixi will automatically assign new PID numbers for all PIDs in the SPTS stream with consecutive numbers following the Base PID number based on this number. | | Remove Inactive Streams from Multiplex | Select this checkbox if you would like to automatically remove inactive streams from the MPTS source. | | Alert on PID changes | If you would like to generate email notifications whenever a PID change is detected, select this checkbox. | | 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. | | 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. | | Monitor CEA-608 Closed Captions | If you would like to monitor CEA-608 closed captions, select this checkbox.
Note: Monitoring CEA-608 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-708 closed captions, select this checkbox.
Note: Monitoring 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 desired latency for auto-pull actions. (Default: 1,000 ms) | | 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. | | ***SCTE-35 Manipulation*** | | | Enable SCTE-35 Manipulation | Select checkbox to enable SCTE-35 Manipulation. | | SCTE-35 PID | Set the SCTE-35 PID in which the messages will be inserted. | | Remove Existing SCTE-35 | Remove any existing SCTE-35 messages from the stream. | | NULL Packet Search Window (ms) | Look for a NULL packet 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 | | ***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/recovery notifications for this Source upon initial configuration. | | ***Error Concealment*** | | | Enable Error Concealment | Select this checkbox to enable the error concealment mechanisms listed below to correct transport stream for downstream IRDs. | | Continuous Timeline | Corrects errors that are related to timeline jumps in the source. This mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input. | | Replace Frames | If there are frames with CC errors, it replaces them with skip frames (inserts the last good frame received in place of missing ones). This solves issues such as an IRD that lost synchronization when it received broken frames. This mechanism also creates a variant of the input (doubling the input). | | Renumber CC | encapsulation. When there are CC errors in TR101 analysis it means that the counter has a gap due to the lost frames. This mechanism can re-write the CC counter for the downstream devices, so they will see a continuous increase of the counter. | | Delay (ms) | Enter the delay that the Error Concealment adds to the stream in miliseconds. Error Concealment needs to buffer the stream to analyze it. One second is a reasonable value. Lower values may cause the Error Concealment to not be able to fix some of the frames. | | CBR Padding (kbps) | Enter a value for the rate at which padding will be added to maintain a specific output transport bitrate. For example, if you have a video bitrate at 5000 kbps or that varies from 3000-5000 kbps and audio at 64 kbps, total bitrate will be max 5064 kbps or min 3064 kbps. With CBR padding set at 6000 kbps, 6000 kbps is being delivered downstream at all times, ensuring a consistent bitrate. | | PCR Interval (ms) | Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. Options include:
* ATSC standard - 100 ms * DVB standard - 40 ms | | ***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+) | | 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
| Specify the maximum transmission unit (largest data packet that a network-connected device will accept) in bytes for the Auto Pull. | | Auto-Pull Billing Password
| Enter the password that corresponds to this auto-pull billing code. | | Auto Pull MTU (seconds) | Specify the maximum transmission unit (largest data packet that a network-connected device will accept) in bytes for the Auto Pull. | | Apply Input NIC selection to network device | Select this checkbox to apply Input NIC selection to the network device. | | 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 for empty audio streams to prevent false warnings - enter a comma-delimited list of PID numbers that should not be monitored for null content. | [title] Adding a Zixi Source – Broadcaster Pull [path] ZEN Master/ZEN Master User Guide/Sources/Adding ZEN Master Sources/ ## Adding a Zixi Source – Broadcaster Pull 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**. ![Broadcaster Source Diagram](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/CNE5OFY6Bc_n2jCt5SlgZ_image.png) The following procedure describes how to add a Zixi Broadcaster Zixi Pull source 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 Push](docId\:vuNNBbUKYIyBi9EYCRX3C) ### 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. ![Create Source Options](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-3mXDQJHXUppSRZJSBYBnR-20250805-132303.png) ::: :::WorkflowBlockItem Click on **Zixi**. The **Create Zixi Source** window opens. ![New Broadcaster Zixi Pull Source](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/zQIb_jDvmYkL0nSs8HPxm-20251028-191821.png) ::: :::WorkflowBlockItem Be sure to set the **Mode** to **Pull** 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 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. - If you have an alternative host for backup, enter that IP address in the **Alt Host** field. - 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, 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 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 If you want to insert SCTE-35 messages into the stream, expand the SCTE-35 Manipulation section to expose the fields: ![SCTE-35 Manipulation Section](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/4w6UoDJpUU0eqGpc-KQhc-20251029-183843.png) ::: :::WorkflowBlockItem Check **Enable SCTE-35 Manipulation** to enable insertion and other management of SCTE-35 messages ::: :::WorkflowBlockItem Set the **NULL Packet Search Window** if needed - factors to consider: - 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 You can also specify a specific **SCTE-35 PID **number. ::: :::WorkflowBlockItem If you want to ensure that your inserted SCTE-35 messages are the only ones, you can elect to remove any pre-existing ones from 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 Under **Error Concealment,** click the Enable Error Concealment checkbox to enable the following error concealment mechanisms that can correct transaport stream for downstream IRDs: :::Paragraph{indent="1"} 1\. **Continuous Timeline** - corrects errors that are related to timeline jumps in the source. This mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input. ::: :::Paragraph{indent="1"} 2\. **Replace Frames** - If there are frames with CC errors, it replaces them with skip frames (inserts the last good frame received in place of missing ones). This solves issues such as an IRD that lost synchronization when it received broken frames. This mechanism also creates a variant of the input (doubling the input). ::: :::Paragraph{indent="1"} 3\. **Renumber CC **- The Continuity Counter is part of the TS encapsulation. When there are CC errors in TR101 analysis it means that the counter has a gap due to the lost frames. This mechanism can re-write the CC counter for the downstream devices, so they will see a continuous increase of the counter. ::: :::Paragraph{indent="1"} 4\. **Delay (ms) **- Enter the delay that the Error Concealment adds to the stream in miliseconds. Error Concealment needs to buffer the stream to analyze it. One second is a reasonable value. Lower values may cause the Error Concealment to not be able to fix some of the frames. ::: :::Paragraph{indent="1"} 5\. **CBR Padding** - enter a value for the rate at which padding will be added to maintain a specific output transport bitrate. For example, if you have a video bitrate at 5000 kbps or that varies from 3000-5000 kbps and audio at 64 kbps, total bitrate will be max 5064 kbps or min 3064 kbps. With CBR padding set at 6000 kbps, 6000 kbps is being delivered downstream at all times, ensuring a consistent bitrate. ::: :::Paragraph{indent="1"} 6.** PCR Interval** - Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. This depends on standard used by downstream encoders or decoders. Options include: ::: :::Paragraph{listStyleType="disc" indent="2"} ATSC standard - 100 ms ::: :::Paragraph{listStyleType="disc" indent="2"} DVB standard - 40 ms ::: 7. **Remux Buffer Size** - Specify the time added for remuxing the stream (default: 2500 ms). 8. **Smoothing** - Time added for smoothing a bursty stream - adds to latency, but produces a smoother output. See [Improving Stream Resiliency: Error Correction and Concealment](docId:9_OLo1Argk_2aDoSHYFBb) for more information. ![Error Concealment Options](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/jEyT42FS_YflpTNxqCc9Q_zm-error-concealment-options.png) :::: :::WorkflowBlockItem If you would like to adjust the advanced settings, click **Advanced**. The **Advanced** settings fields are displayed. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/TMswOWHiIMbI2GdFr2lc1_bx-pull-source-advanced.png) ::: :::WorkflowBlockItem If you would like to track usage for this Source, enter your **Billing Code** details. See [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ). ::: :::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. Choose *Pull*. | | Application | To create a Zixi Broadcaster Source, select the **Broadcaster** radio button. | | ***For Pull Mode*** | | | Host | Enter the IP address of the Broadcaster from which the stream is being pulled. | | Port | Enter the port through which the Broadcaster receives the stream from another Broadcaster server. Default: 2088
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. | | Stream ID | Enter the precise stream ID (case sensitive) assigned to this stream on the input broadcaster. | | Password | If you are using a password for this stream, enter the string for authentication. It must be identical to the string configured on the input broadcaster. | | ***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. | | ***SCTE-35 Manipulation*** | | | Enable SCTE-35 Manipulation | Enable insertion and other management of SCTE-35 messages (used typically to create ad breaks) | | NULL Packet Search Window (ms) | Look for a NULL packet 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 | If you wish to override any existing SCTE-35 messages with your own, you can elect to have existing ones removed | | ***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. | | ***Error Concealment *** | :::Paragraph{indent="1"} ::: | | Enable Error Concealment | Select this checkbox to enable the error concealment mechanisms listed below to correct transport stream for downstream IRDs. | | Continuous Timeline | Corrects errors that are related to timeline jumps in the source. This mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input. | | Replace Frames | If there are frames with CC errors, it replaces them with skip frames (inserts the last good frame received in place of missing ones). This solves issues such as an IRD that lost synchronization when it received broken frames. This mechanism also creates a variant of the input (doubling the input). | | Renumber CC | encapsulation. When there are CC errors in TR101 analysis it means that the counter has a gap due to the lost frames. This mechanism can re-write the CC counter for the downstream devices, so they will see a continuous increase of the counter. | | Delay (ms) | Enter the delay that the Error Concealment adds to the stream in miliseconds. Error Concealment needs to buffer the stream to analyze it. One second is a reasonable value. Lower values may cause the Error Concealment to not be able to fix some of the frames. | | CBR Padding (kbps) | Enter a value for the rate at which padding will be added to maintain a specific output transport bitrate. For example, if you have a video bitrate at 5000 kbps or that varies from 3000-5000 kbps and audio at 64 kbps, total bitrate will be max 5064 kbps or min 3064 kbps. With CBR padding set at 6000 kbps, 6000 kbps is being delivered downstream at all times, ensuring a consistent bitrate. | | PCR Interval (ms) | Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. Options include:
* ATSC standard - 100 ms * DVB standard - 40 ms | | ***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+) | | 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. Available for sources for Zixi Broadcaster **18.2** or later. | | 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. | [title] Adding a Zixi Source – Other-Enabled Device [path] ZEN Master/ZEN Master User Guide/Sources/Adding ZEN Master Sources/ You can configure an input from a Zixi-enabled device (i.e. a Zixi-enabled encoder) to be used as a source in ZEN Master. This is done by selecting **Zixi** in the New Source Menu. After configuring the Source, you will need to connect the input resource to ZEN Master using the procedure described in section [Connecting a Stream from a Zixi-Enabled Device (Encoder UI)](docId\:bjr4vrAM5n_7U6j6H393N). :::hint{type="info"} In case the stream is meant to be password-protected, the password itself is configured in ZEN Master, when configuring the Source, and then added to the stream on the Zixi-enabled device, as part of the [Connecting a Stream from a Zixi-Enabled Device (Encoder UI)](docId\:bjr4vrAM5n_7U6j6H393N) process. ::: In this case, the Zixi-enabled device is referred to as the **Origin Other** which streams to the **Ingest Broadcaster**. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-1kp8eFNkQZdNni_mB3gSn-20250302-143625.png) The following procedure describes how to add a Zixi-Enabled device Source in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. **To add a source from a Zixi-enabled device :** :::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). ::: :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Source selection** window is displayed. ![Create Source Options](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-3mXDQJHXUppSRZJSBYBnR-20250805-132303.png) ::: :::WorkflowBlockItem Click on **Zixi**. The **Create Zixi Source** window opens. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-FOIohYAgf29Fm5OLcbKaG-20250608-131804.png) ::: :::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 **Input** section, verify that under *Mode*, **Push **is selected (default), and in **Application**, select the **Other **radio button. The fields relevant for creating a Source from a Zixi-enabled device are shown. ::: :::WorkflowBlockItem In the **Configuration** section, 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 **Source Password** field, enter a password that will be used to connect the Stream. This password will be added to the stream on the Zixi-enabled device, as part of the [Connecting a Stream from a Zixi-Enabled Device (Encoder UI)](docId\:bjr4vrAM5n_7U6j6H393N) process. ::: :::WorkflowBlockItem In the **Priority Client ID** field, if you have more than one Zixi-Enabled devices (e.g., Encoders) pushing the stream, you can optionally enter the ID of one of these devices and it will receive priority in establishing a connection. By default (without this setting), the connection is established by the order of connection, however this setting will overwrite this default behavior and connect the stream coming from the priority device when possible.. ::: ::::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 [Adding PID Mapping Profiles](docId\:gFTCaYurPL7DInoUyd14z) . ::: :::: :::WorkflowBlockItem If you would like to generate email notifications whenever a PID change is detected, select the **Alert on PID changes** checkbox. ::: ::::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. ::: :::hint{type="info"} 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/CEA-708 closed captions, select the **Monitor CEA-608/CEA-708** checkbox. :::hint{type="info"} Monitoring CEA-608/CEA-708 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: :::: ::::WorkflowBlockItem If you would like to disable auto-pull, select the **Disable Auto-Pull **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 the Source is using AES for 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: ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-gEhzUj2KDWzi-XlEvL8E0-20250820-134543.png) ::: :::WorkflowBlockItem If you would like to track usage for this Source, enter your Billing Code details. See [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ) . ::: :::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-Enabled Device - 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 Source from a Zixi-enabled device, verify that
**Push **is selected (default).
| | Application | To create a Source from a Zixi-enabled device, select the
**Other **radio button.
| | ***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. | | Priority Client ID | The ID of the client application that should be prioritized when pushing to this source. Requires Broadcasters version 17.3 or higher and Zen Master authorization enabled on the Broadcaster Cluster. | | 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. | | 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 | Disables the Source thumbnail from appearing in the Sources list and other places. Disabling thumbnail may improve system performance. | | 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 | 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+) | | 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. | | 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. | | 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. | [title] Adding a Zixi Source – OnAir [path] ZEN Master/ZEN Master User Guide/Sources/Adding ZEN Master Sources/ ## Adding a Zixi Source – OnAir The **OnAir** source is a special variety of the **Zixi Push** source, designed to accept a live stream from the Zixi [On Air Pro](docId:8mmLXna1om5BAcjoA-oiC) app for iOS (available in the App Store). ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Hj0pkpkw_GBtUOp542W8e-20260327-184639.png) Once the source is created, you can email the configuration details to the device user, who will be able to click a link in the message to open the OnAir Pro app and set up the connection automatically. ### To add an OnAir Source: :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Source selection** window is displayed. ![Choose Source Type](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/myJFcCTpb-bf5zY4fTKIt-20260327-185125.png) ::: :::WorkflowBlockItem Click on **Zixi**. The **Create Zixi Source** window opens. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/DXL_qEqfrQbbcIL4IbONQ-20260327-184619.png) ::: :::WorkflowBlockItem Be sure to set the **Mode** to **Push** and the **Application** to **OnAir** 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 Check the **Use Private IP** checkbox if the device with the OnAir Pro app is on a VPN with a private IP address, and enter that IP address in the **Location** field. ::: :::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 Enter a **Source Password** if you want to require a password to allow a stream to connect to the source. ::: :::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 (optional). ::: ::::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 To prevent the source from being accidentally deleted, check **Deletion Protection**. ::: ::::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. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ltrmJMVzzv_5-xJ1tHsRu_onair-push-source-advanced.png) ::: ::::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 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 The Ignore Monitoring PIDs field prevents ZEN Master from issuing alerts for empty audio streams. If you wish to enable this, enter a comma-delimited list of PID numbers that should not be monitored for null content. ::: :::WorkflowBlockItem Click **Save**. ::: ::::: ## Emailing Source Details to Be Used on the Device ::::WorkflowBlock :::WorkflowBlockItem In the top right “kebab” icon, select **Config**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/GWsMSRmMz4ccm8JXWkezc_.blob) ::: :::WorkflowBlockItem Enter an email address to send the Source configuration to your Apple device. ::: :::WorkflowBlockItem Click outside the input area and click **Send**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/5G1zqeNJhvjSH2_1S4jnA_.blob) ::: :::WorkflowBlockItem Close the **Configuration** window. ::: :::: See [Streaming using ZEN Master](docId\:IKoURGnTRFnzRLlqiYqUr) for instructions on how to use the configuration information in the email in the On Air Pro app. ## 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. For OnAir, choose *Push* | | Application | To create an OnAir source, select the **OnAir** radio button. | | ***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. | | Public Output | If you would like to allow access to the stream directly through a supported player, select the **Allow** checkbox. | | Password (optional 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.). | | 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) | | 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. | | 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. | [title] Broadcasters Clusters Creating Redirection Rules [path] ZEN Master/ZEN Master User Guide/Broadcasters/Viewing Existing Clusters/ ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/WB4TmodPl6BC-xg5zm-7V-20251125-155624.jpg) | Description | A description of the rule. | | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | From | The Cluster from which the Pull Request was initiated | | To | The type of redirection:
* **Redirect to public IP** - pull requests that match this rule will be resolved by redirecting it through a public IP. This is the default behavior. * **Redirect to private IP** - pull requests that match this rule will be resolved by redirecting it through a private IP. * **Redirect to NIC** - pull requests that match this rule will be resolved by redirecting it to a specific NIC. * **Block **- pull requests that match this rule will be blocked. | | Latency Override | The latency when the redirection rule applies. Latency is determined by the following order: Redirection rule latency -> source autopull/pull target latency -> default 1000ms. | | Order | The order value for this rule. Rules are evaluated from lowest to highest order, the first rule that matches will be applied. | | Actions | The following actions are displayed:
* Edit rule * Delete rule | [title] Source Sources (for Failover) [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/ Shows information about each of the component Sources that are included in the Failover group. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-nvAqbHh4DBC7tPlR-4A63-20250721-142150.png) The following table explains the data shown for each listing: | Parameter | Description | | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Name | The name of the Source. | | Status | The Status of the Source. | | Offset \[ms] | Shows the offset level between the Failover Sources in milliseconds. | | Active | Yes - the Source is currently streaming.
No - the Source is in standby (not streaming) | | Packets | The total number of packets that were streamed. | | Priority | Preferred - the Source was configured as a preferred. Preferred source take precedence over non-preferred source (i.e., sources that were not marked as preferred).
Slate - Slate sources are sources that stream slate content, which is content that can be served when there are gaps in a live stream ad break that cannot be filled with a dynamically-served ad. | | Actions | You can manually select one of the streams to be active by clicking on the *Lock *button. The Source designated as *Locked* will be used whenever it is available until you click *Unlock*. | [title] Source Details [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/ The **Details** section shows the following information: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/S9ICdHyDPKCFhwGFf3g2S-20260115-133759.jpg) | **Parameter** | **Description** | | -------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Type | The type of the Source in ZEN Master e.g., Broadcaster, ZEC, Monitor Only, RIST, File etc.
Note: a “**From** **MediaConnect**" Source is a Source that receives a stream from MediaConnect (*Method 1* integration), a "**To** **MediaConnect**" Source is a ZEN Master Managed MediaConnect Source, which was created in ZEN Master (*Method 2 *integration), see [Adding a Source - AWS MediaConnect](docId\:Qi_aQkV6Wt6YIRhaTIKvU) . | | **AWS Media** | | | Name | The name of the Source. | | Input | The name of the Input stream. | | Events Configuration Profile | The Events Configuration Profile that was selected for this source. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Latency (ms) | The latency value for the Source. | | Ingest Port | The port that the Flow listens on for incoming content. | | Whitelist CIDR Block | The CIDR for the range of IPs that is allowed to contribute content to this Source. | | AWS MediaConnect Flow | The name of the AWS MediaConnect Flow to which the Source will connect. | | AWS MediaLive Channel | The name of the AWS MediaLive Channel to which the Source will connect. | | AWS Account | The logical name of the AWS Account in ZEN Master (Configuration > Amazon AWS > Accounts). | | Region | The AWS Region in which the MediaConnect/MediaLive is deployed. | | **Broadcaster** | | | Events Configuration Profile | The Events Configuration Profile that was selected for this source. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Input | The name of the Origin Broadcaster Input. | | Location | The location of the Origin Broadcaster. | | Network | The ISP/network of the Origin Broadcaster. | | Source IP | The IP address of the Origin Broadcaster. Transcoded – means that the source is transcoded. | | Source Password | Click **Show** to display the Source's password. Click Copy to copy the password. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Target Broadcaster/s | Specifies which Broadcaster/s within the cluster on which ZEN Master can deploy the source. | | Application | The origin application used to send the Source to the Ingest Cluster. In this case it is a Broadcaster. | | Device | The OS of the Origin Broadcaster machine. | | Build | The Build version of the Origin Broadcaster. | | Encrypted | The type of encryption used to protect the stream. | | Remote ID | The ID of the Origin ZEC/Broadcaster/Device. | | Certificate | Indicates whether the DTLS certificate has been installed and its expiration date. | | RTP Payload | Indicates that RTP headers are present and being preserved. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | Latency | The maximal latency configured for the Source. | | Public Output | If enabled, it allows access to the stream directly through a supported player. | | Preserve closed captions | If enabled, closed captions are preserved for this Source. | | Alert on PID Changes | Shows if the Alert on PID changed is enabled/disabled. This feature generates email notifications whenever a PID change is detected In the Configuration section. | | Content Analysis | Shows if the Content Analysis is enabled/disabled and the type of Content Analysis that has been configured (Full/TR101 Only/None). Content Analysis shows errors detected in the audio and video content itself. | | Hide Thumbnail | Shows if the Source is enabled to hide the Source's thumbnail from where it is displayed (e.g., the Preview Pane, Grids, etc.).
| | SCTE-35 Alerts | Shows if the Source is enabled to send alerts for SCTE-35 markers. Requires SCTE-35 Logging. | | Enable SCTE-35 Insertion | If this setting is enabled, Broadcaster is able to insert a SCTE-35 marker to the stream based on a placement by an external system through the ESAM agent. When the placement opportunity occurs, the ESAM agent generates an API call to the Broadcaster, which initiates the insertion of the SCTE-35 marker into the input stream. | | Frame Thinning Latency | The Frame Thinning feature removes frames from the stream to get to a lower bitrate if the stream is traversing a crowded network instead of using transcoding to lower the bitrate. To allow the analysis and selection of the frames, Broadcaster needs a buffer. The setting specifies the buffer size (latency) that is allowed in milliseconds in order to remove these frames. The higher the thinning latency, the more accurate results the thinner will reproduce. Recommended/reasonable value is 1 second.
O ms - Frame Thinning is disabled. | | Frozen Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a frozen video state. | | Blank Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a blank video state.
| | **Demux** | | | Events Configuration Profile | The Events Configuration Profile that was selected for this source. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Input | The name of the Input stream. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Target Broadcaster/s | Specifies which Broadcaster/s within the cluster on which ZEN Master can deploy the source. | | Application | The application used to process the Source. | | Device | The OS of the Origin Broadcaster machine. | | Build | The Build version of the Origin Broadcaster. | | Encrypted | If one of the Encryption methods was selected, in the Encryption Key field, enter an encryption key that will be used to encrypt the connection OR click Random to generate a random encryption key. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | Public Output | If enabled, it allows access to the stream directly through a supported player. | | Preserve closed captions | If enabled, closed captions are preserved for this Source. | | Alert on PID Changes | Shows if the Alert on PID changed is enabled/disabled. This feature generates email notifications whenever a PID change is detected In the Configuration section. | | Content Analysis | Shows if the Content Analysis is enabled/disabled and the type of Content Analysis that has been configured (Full/TR101 Only/None). Content Analysis shows errors detected in the audio and video content itself. | | Hide Thumbnail | Shows is the Source is enabled to hide the Source's thumbnail from where it is displayed (e.g., the Preview Pane, Grids, etc.). | | Log SCTE-35 | Shows if the Source is enabled to log SCTE-35 markers. | | SCTE-35 Alerts | Shows if the Source is enabled to send alerts for SCTE-35 markers. | | Enable SCTE-35 Insertion | If this setting is enabled, Broadcaster is able to insert a SCTE-35 marker to the stream based on a placement by an external system through the ESAM agent. When the placement opportunity occurs, the ESAM agent generates an API call to the Broadcaster, which initiates the insertion of the SCTE-35 marker into the input stream. | | Frame Thinning Latency | The Frame Thinning feature removes frames from the stream to get to a lower bitrate if the stream is traversing a crowded network instead of using transcoding to lower the bitrate. To allow the analysis and selection of the frames, Broadcaster needs a buffer. The setting specifies the buffer size (latency) that is allowed in milliseconds in order to remove these frames. The higher the thinning latency, the more accurate results the thinner will reproduce. Recommended/reasonable value is 1 second.
O ms - Frame Thinning is disabled. | | Frozen Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a frozen video state. | | Blank Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a blank video state. | | **Failover** | | | Events Configuration Profile | The Events Configuration Profile that was selected for this source. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Primary Sources | The names of the Sources that have been configured as **Preferred** sources in the Failover. The active source is indicated as Active. | | Secondary Sources | The names of the Sources that have been configured as Non-preferred sources in the Failover. The active source is indicated as Active. | | Slate Sources | The names of the Sources that have been configured as Slate sources in the Failover. The active source is indicated as Active. | | Automatically switch to Preferred Source | If enabeled, switches automatically to the configured preferred source. | | Failover Mode | The mode used to merge the streams:
* **Stream Switch - **ZEN Master treats the streams as different and does not try to merge them. If packets are missing from one stream, ZEN Master will switch to the alternate stream. * **Content Hitless Merge **- if the Sources do not have RTP headers, Zixi will merge the streams using the MPEG-TS payload content itself. This method uses Zixi's patented DNA like sequencing algorithm to fill in the missing packets. * **SMPTE 2022-7 Hitless **- if the Sources use RTP, and the RTP headers were maintained, Zixi can use the SMPTE 2022-7 to compare and merge the two streams. This option uses the sequence and the timestamp in the packets to compare which packets are missing, providing optimal results. | | Zero Bitrate/Offline Detection Window |
The time frame with zero bitrate or offline state after which the system will perform the failover. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Target Broadcaster/s | Specifies which Broadcaster/s within the cluster on which ZEN Master can deploy the source. | | Application | The application used to process the Source. | | Device | The OS of the Origin Broadcaster machine. | | Build | The Build version of the Origin Broadcaster. | | Encrypted | If one of the Encryption methods was selected, in the Encryption Key field, enter an encryption key that will be used to encrypt the connection OR click Random to generate a random encryption key. | | Preserve RTP Headers | If enabled, the system preserves the RTP headers (which include the timestamps and sequences) and propagates them the output. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | Public Output | If enabled, it allows access to the stream directly through a supported player. | | Preserve closed captions | Shows if the Preserve Closed Caption is enabled/disabled. This feature preserves the closed captions from the source. | | Alert on PID Changes | Shows if the Alert on PID changed is enabled/disabled. This feature generates email notifications whenever a PID change is detected In the Configuration section. | | Content Analysis | Shows if the Content Analysis is enabled/disabled and the type of Content Analysis that has been configured (Full/TR101 Only/None). Content Analysis shows errors detected in the audio and video content itself. | | Hide Thumbnail | Shows if the Source is enabled to hide the Source's thumbnail from where it is displayed (e.g., the Preview Pane, Grids, etc.). | | SCTE-35 Alerts | Shows if the Source is enabled to send alerts for SCTE-35 markers. | | Enable SCTE-35 Insertion | If this setting is enabled, Broadcaster is able to insert a SCTE-35 marker to the stream based on a placement by an external system through the ESAM agent. When the placement opportunity occurs, the ESAM agent generates an API call to the Broadcaster, which initiates the insertion of the SCTE-35 marker into the input stream. | | Frame Thinning Latency | The Frame Thinning feature removes frames from the stream to get to a lower bitrate if the stream is traversing a crowded network instead of using transcoding to lower the bitrate. To allow the analysis and selection of the frames, Broadcaster needs a buffer. The setting specifies the buffer size (latency) that is allowed in milliseconds in order to remove these frames. The higher the thinning latency, the more accurate results the thinner will reproduce. Recommended/reasonable value is 1 second.
O ms - Frame Thinning is disabled. | | Frozen Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a frozen video state. | | Blank Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a blank video state. | | **File** | | | Events Configuration Profile | The Events Configuration Profile that was selected for this source. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | URL | For File source type, the URL of the source stream. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Target Broadcaster/s | Specifies which Broadcaster/s within the cluster on which ZEN Master can deploy the source. | | Application | The application used to process the Source. | | Device | The OS of the Origin Broadcaster machine. | | Build | The Build version of the Origin Broadcaster. | | Encrypted | If one of the Encryption methods was selected, in the Encryption Key field, enter an encryption key that will be used to encrypt the connection OR click Random to generate a random encryption key. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | Public Output | If enabled, it allows access to the stream directly through a supported player. | | Preserve closed captions | If enabled, closed captions are preserved for this Source. | | Content Analysis | Shows if the Content Analysis is enabled/disabled. Content Analysis shows errors detected in the audio and video content itself. | | Hide Thumbnail | Shows if the Source is enabled to hide the Source's thumbnail from where it is displayed (e.g., the Preview Pane, Grids, etc.). | | Enable SCTE-35 Insertion | If this setting is enabled, Broadcaster is able to insert a SCTE-35 marker to the stream based on a placement by an external system through the ESAM agent. When the placement opportunity occurs, the ESAM agent generates an API call to the Broadcaster, which initiates the insertion of the SCTE-35 marker into the input stream. | | Frame Thinning Latency | The Frame Thinning feature removes frames from the stream to get to a lower bitrate if the stream is traversing a crowded network instead of using transcoding to lower the bitrate. To allow the analysis and selection of the frames, Broadcaster needs a buffer. The setting specifies the buffer size (latency) that is allowed in milliseconds in order to remove these frames. The higher the thinning latency, the more accurate results the thinner will reproduce. Recommended/reasonable value is 1 second.
O ms - Frame Thinning is disabled. | | Frozen Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a frozen video state. | | Blank Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a blank video state. | | **HLS** | | | Events Configuration Profile | The Events Configuration Profile that was selected for this source. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Input | The name of the Input stream. | | Location | The location of the Source. | | Network | The ISP/ network of the Source. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Target Broadcaster/s | Specifies which Broadcaster/s within the cluster on which ZEN Master can deploy the source. | | Application | The application used to process the Source. | | Device | The OS of the Origin Broadcaster machine. | | Build | The Build version of the Origin Broadcaster. | | Encrypted | If one of the Encryption methods was selected, in the Encryption Key field, enter an encryption key that will be used to encrypt the connection OR click Random to generate a random encryption key | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | Buffer Size | The amount of video data downloaded and stored by the player before playback begins in milliseconds.
| | Convert EXT-X-CUE-OUT/EXT-X-CUE-IN ad markers to SCTE-35 | If enabled, the system converts EXT-X-CUE-OUT/EXT-X-CUE-IN ad markers to SCTE-35. | | Public Output | If enabled, it allows access to the stream directly through a supported player. | | Preserve closed captions | Shows if the Preserve Closed Caption is enabled/disabled. This feature preserves the closed captions from the source. | | Alert on PID Changes | Shows if the Alert on PID changed is enabled/disabled. This feature generates email notifications whenever a PID change is detected In the Configuration section. | | Content Analysis | Shows if the Content Analysis is enabled/disabled. Content Analysis shows errors detected in the audio and video content itself. | | Hide Thumbnail | Shows if the Source is enabled to hide the Source's thumbnail from where it is displayed (e.g., the Preview Pane, Grids, etc.). | | SCTE-35 Alerts | Shows if the Source is enabled to send alerts for SCTE-35 markers. | | Enable SCTE-35 Insertion | If this setting is enabled, Broadcaster is able to insert a SCTE-35 marker to the stream based on a placement by an external system through the ESAM agent. When the placement opportunity occurs, the ESAM agent generates an API call to the Broadcaster, which initiates the insertion of the SCTE-35 marker into the input stream. | | Frame Thinning Latency | The Frame Thinning feature removes frames from the stream to get to a lower bitrate if the stream is traversing a crowded network instead of using transcoding to lower the bitrate. To allow the analysis and selection of the frames, Broadcaster needs a buffer. The setting specifies the buffer size (latency) that is allowed in milliseconds in order to remove these frames. The higher the thinning latency, the more accurate results the thinner will reproduce. Recommended/reasonable value is 1 second.
O ms - Frame Thinning is disabled. | | Frozen Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a frozen video state. | | Blank Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a blank video state. | | **Inter-Cluster** | | | Input | The name of the Input stream. | | Events Configuration Profile | The Events Configuration Profile that was selected for this source. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Source IP | The IP address of the Source's input resource. Transcoded - means that the source is transcoded. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Target Broadcaster/s | Specifies which Broadcaster/s within the cluster on which ZEN Master can deploy the source. | | Prefer Private Broadcaster IP | If enabled, this setting overrides the Cluster redirection rules. It requires a **Private IP** to be set in Broadcaster Advanced settings. | | Location | The location of the Source. | | Secondary Sources | For Failover source type, the names of the Sources that have been configured as Secondary sources in the Failover. | | Network | The ISP/ network of the Source. | | Application | The application used to process the Source. | | Device | The OS of the Origin Broadcaster machine. | | Build | The Build version of the Origin Broadcaster. | | Encrypted | If one of the Encryption methods was selected, in the Encryption Key field, enter an encryption key that will be used to encrypt the connection OR click Random to generate a random encryption key. | | Health | The current Health score of the source | | Remote ID | The ID of the Origin ZEC/Broadcaster/Device. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | Latency | The configured latency in milliseconds. | | Public Output | If enabled, it allows access to the stream directly through a supported player. | | Preserve closed captions | If enabled, closed captions are preserved for this Source. | | Alert on PID Changes | Shows if the Alert on PID changed is enabled/disabled. This feature generates email notifications whenever a PID change is detected In the Configuration section. | | Minimize Latency | If enabled, Zixi adjusts the latency dynamically to optimize it for network conditions. | | Content Analysis | Shows if the Content Analysis is enabled/disabled. Content Analysis shows errors detected in the audio and video content itself. | | Hide Thumbnail | Shows if the Source is enabled to hide the Source's thumbnail from where it is displayed (e.g., the Preview Pane, Grids, etc.). | | Log SCTE-35 | Shows if the Source is enabled to log SCTE-35 markers. | | SCTE-35 Alerts | Shows if the Source is enabled to send alerts for SCTE-35 markers. | | Enable SCTE-35 Insertion | If this setting is enabled, Broadcaster is able to insert a SCTE-35 marker to the stream based on a placement by an external system through the ESAM agent. When the placement opportunity occurs, the ESAM agent generates an API call to the Broadcaster, which initiates the insertion of the SCTE-35 marker into the input stream. | | Frame Thinning Latency | The Frame Thinning feature removes frames from the stream to get to a lower bitrate if the stream is traversing a crowded network instead of using transcoding to lower the bitrate. To allow the analysis and selection of the frames, Broadcaster needs a buffer. The setting specifies the buffer size (latency) that is allowed in milliseconds in order to remove these frames. The higher the thinning latency, the more accurate results the thinner will reproduce. Recommended/reasonable value is 1 second.
O ms - Frame Thinning is disabled. | | Frozen Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a frozen video state. | | Blank Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a blank video state. | | Certificate | Indicates whether the DTLS certificate has been installed and its expiration date. | | RTP Payload | Indicates that RTP headers are present and being preserved. | | Traceroute History | Shows if the Traceroute History is enabled/disabled. This feature shows historical traceroutes that have been used for this stream. The graph shows RTTs for each server used by the stream over time. | | **Monitor Only** | | | Events Configuration Profile | The Events Configuration Profile that was selected for this source. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Location | The location of the Source. | | Network | The ISP/ network of the Source. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Target Broadcaster/s | Specifies which Broadcaster/s within the cluster on which ZEN Master can deploy the source. | | Encrypted | If one of the Encryption methods was selected, in the Encryption Key field, enter an encryption key that will be used to encrypt the connection OR click Random to generate a random encryption key. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | Public Output | If enabled, it allows access to the stream directly through a supported player. | | Preserve closed captions | If enabled, closed captions are preserved for this Source. | | Alert on PID Changes | Shows if the Alert on PID changed is enabled/disabled. This feature generates email notifications whenever a PID change is detected In the Configuration section. | | Content Analysis | Shows if the Content Analysis is enabled/disabled. Content Analysis shows errors detected in the audio and video content itself. | | Hide Thumbnail | Shows if the Source is enabled to hide the Source's thumbnail from where it is displayed (e.g., the Preview Pane, Grids, etc.). | | Log SCTE-35 | Shows if the Source is enabled to log SCTE-35 markers. | | SCTE- 35 Alerts | Shows if the Source is enabled to send alerts for SCTE-35 markers. | | Enable SCTE-35 Insertion | If this setting is enabled, Broadcaster is able to insert a SCTE-35 marker to the stream based on a placement by an external system through the ESAM agent. When the placement opportunity occurs, the ESAM agent generates an API call to the Broadcaster, which initiates the insertion of the SCTE-35 marker into the input stream. | | Frame Thinning Latency | The Frame Thinning feature removes frames from the stream to get to a lower bitrate if the stream is traversing a crowded network instead of using transcoding to lower the bitrate. To allow the analysis and selection of the frames, Broadcaster needs a buffer. The setting specifies the buffer size (latency) that is allowed in milliseconds in order to remove these frames. The higher the thinning latency, the more accurate results the thinner will reproduce. Recommended/reasonable value is 1 second.
O ms - Frame Thinning is disabled. | | Frozen Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a frozen video state. | | Blank Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a blank video state. | | Source IP | The IP address of the Source's input resource. Transcoded – means that the source is transcoded. | | **Multiplex** | | | Events Configuration Profile | The Events Configuration Profile that was selected for this source. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Sources | The Sources that were selected to become a Program in the MPTS source. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Application | The application used to process the Source. | | Device | The OS of the Origin Broadcaster machine. | | Build | The Build version of the Origin Broadcaster. | | Encrypted | If one of the Encryption methods was selected, in the Encryption Key field, enter an encryption key that will be used to encrypt the connection OR click Random to generate a random encryption key. | | Target Bitrate | The configured target bitrate of the multiplex stream in kbps, which should be at least as high as the sum of all of the effective bitrates of the individual STPS sources included in the multiplex source. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | Public Output | If enabled, it allows access to the stream directly through a supported player. | | Target Broadcaster/s | Specifies which Broadcaster/s within the cluster on which ZEN Master can deploy the source. | | Preserve closed captions | If enabled, closed captions are preserved for this Source. | | Remove Inactive Streams from Multiplex | If enabled, the system will remove inactive streams from the Miltiplex source. | | Hide Thumbnail | Shows if the Source is enabled to hide the Source's thumbnail from where it is displayed (e.g., the Preview Pane, Grids, etc.). | | Alert on PID Changes | Shows if the Alert on PID changed is enabled/disabled. This feature generates email notifications whenever a PID change is detected In the Configuration section. | | SCTE-35 Alerts | Shows if the Source is enabled to send alerts for SCTE-35 markers. | | Enable SCTE-35 Insertion | If this setting is enabled, Broadcaster is able to insert a SCTE-35 marker to the stream based on a placement by an external system through the ESAM agent. When the placement opportunity occurs, the ESAM agent generates an API call to the Broadcaster, which initiates the insertion of the SCTE-35 marker into the input stream. | | Frame Thinning Latency | The Frame Thinning feature removes frames from the stream to get to a lower bitrate if the stream is traversing a crowded network instead of using transcoding to lower the bitrate. To allow the analysis and selection of the frames, Broadcaster needs a buffer. The setting specifies the buffer size (latency) that is allowed in milliseconds in order to remove these frames. The higher the thinning latency, the more accurate results the thinner will reproduce. Recommended/reasonable value is 1 second.
O ms - Frame Thinning is disabled. | | Frozen Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a frozen video state. | | Blank Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a blank video state. | | Content Analysis | Shows if the Content Analysis is enabled/disabled. Content Analysis shows errors detected in the audio and video content itself. | | **Multiview** | | | Events Configuration Profile | The Events Configuration Profile that was selected for this source. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Sources | The Sources that were selected to be part of the Multiview Source. | | Location | The location of the Source. | | Network | The ISP/ network of the Source. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Target Broadcaster/s | Specifies which Broadcaster/s within the cluster on which ZEN Master can deploy the source. | | Encrypted | If one of the Encryption methods was selected, in the Encryption Key field, enter an encryption key that will be used to encrypt the connection OR click Random to generate a random encryption key. | | Public Output | If enabled, it allows access to the stream directly through a supported player. | | Preserve closed captions | If enabled, closed captions are preserved for this Source. | | Alert on PID Changes | Shows if the Alert on PID changed is enabled/disabled. This feature generates email notifications whenever a PID change is detected In the Configuration section. | | Content Analysis | Shows if the Content Analysis is enabled/disabled. Content Analysis shows errors detected in the audio and video content itself. | | Hide Thumbnail | Shows if the Source is enabled to hide the Source's thumbnail from where it is displayed (e.g., the Preview Pane, Grids, etc.). | | SCTE-35 Alerts | Shows if the Source is enabled to send alerts for SCTE-35 markers. | | Enable SCTE-35 Insertion | If this setting is enabled, Broadcaster is able to insert a SCTE-35 marker to the stream based on a placement by an external system through the ESAM agent. When the placement opportunity occurs, the ESAM agent generates an API call to the Broadcaster, which initiates the insertion of the SCTE-35 marker into the input stream. | | Frame Thinning Latency | The Frame Thinning feature removes frames from the stream to get to a lower bitrate if the stream is traversing a crowded network instead of using transcoding to lower the bitrate. To allow the analysis and selection of the frames, Broadcaster needs a buffer. The setting specifies the buffer size (latency) that is allowed in milliseconds in order to remove these frames. The higher the thinning latency, the more accurate results the thinner will reproduce. Recommended/reasonable value is 1 second.
O ms - Frame Thinning is disabled. | | Frozen Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a frozen video state. | | Blank Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a blank video state. | | **NDI** | | | Events Configuration Profile | The Events Configuration Profile that was selected for this source. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Transcoding Profile | Transcoding Profiles – displays all existing Transcoding profiles and details about their configuration. See VIEWING EXISTING TRANSCODING PROFILES. On this screen, you can add new Transcoding Profiles and manage existing Transcoding Profiles. | | Input | The details of the source’s input. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Target Broadcaster/s | Specifies which Broadcaster/s within the cluster on which ZEN Master can deploy the source. | | Encrypted | If one of the Encryption methods was selected, in the Encryption Key field, enter an encryption key that will be used to encrypt the connection OR click Random to generate a random encryption key. | | Public Output | If enabled, it allows access to the stream directly through a supported player. | | Preserve closed captions | If enabled, closed captions are preserved for this Source. | | Alert on PID Changes | Shows if the Alert on PID changed is enabled/disabled. This feature generates email notifications whenever a PID change is detected In the Configuration section. | | Content Analysis | Shows if the Content Analysis is enabled/disabled. Content Analysis shows errors detected in the audio and video content itself. | | Hide Thumbnail | Shows if the Source is enabled to hide the Source's thumbnail from where it is displayed (e.g., the Preview Pane, Grids, etc.). | | SCTE-35 Alerts | Shows if the Source is enabled to send alerts for SCTE-35 markers. | | | Transcoding Profiles – displays all existing Transcoding profiles and details about their configuration. See VIEWING EXISTING TRANSCODING PROFILES. On this screen, you can add new Transcoding Profiles and manage existing Transcoding Profiles. | | Enable SCTE-35 Insertion | If this setting is enabled, Broadcaster is able to insert a SCTE-35 marker to the stream based on a placement by an external system through the ESAM agent. When the placement opportunity occurs, the ESAM agent generates an API call to the Broadcaster, which initiates the insertion of the SCTE-35 marker into the input stream. | | Frame Thinning Latency | The Frame Thinning feature removes frames from the stream to get to a lower bitrate if the stream is traversing a crowded network instead of using transcoding to lower the bitrate. To allow the analysis and selection of the frames, Broadcaster needs a buffer. The setting specifies the buffer size (latency) that is allowed in milliseconds in order to remove these frames. The higher the thinning latency, the more accurate results the thinner will reproduce. Recommended/reasonable value is 1 second.
O ms - Frame Thinning is disabled. | | Frozen Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a frozen video state. | | Blank Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a blank video state. | | Source IP | The IP address of the Source's input resource. Transcoded – means that the source is transcoded. | | Application | The application used to process the Source. | | Device | The OS of the Origin Broadcaster machine. | | Build | The Build version of the Origin Broadcaster. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | **Other** | | | Events Configuration Profile | The Events Configuration Profile that was selected for this source. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Source IP | The IP address of the Source's input resource. Transcoded – means that the source is transcoded. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Target Broadcaster/s | Specifies which Broadcaster/s within the cluster on which ZEN Master can deploy the source. | | Application | The application used to process the Source. | | Device | The OS of the Origin Broadcaster machine. | | Build | The Build version of the Origin Broadcaster. | | Encrypted | If one of the Encryption methods was selected, in the Encryption Key field, enter an encryption key that will be used to encrypt the connection OR click Random to generate a random encryption key. | | Remote ID | The ID of the Origin ZEC/Broadcaster/Device. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | Public Output | If enabled, it allows access to the stream directly through a supported player. | | Preserve closed captions | If enabled, closed captions are preserved for this Source. | | Alert on PID Changes | Shows if the Alert on PID changed is enabled/disabled. This feature generates email notifications whenever a PID change is detected In the Configuration section. | | Minimize Latency | If enabled, Zixi adjusts the latency dynamically to optimize it for network conditions. | | Content Analysis | Shows if the Content Analysis is enabled/disabled. Content Analysis shows errors detected in the audio and video content itself. | | Hide Thumbnail | Shows if the Source is enabled to hide the Source's thumbnail from where it is displayed (e.g., the Preview Pane, Grids, etc.). | | Log SCTE-35 | Shows if the Source is enabled to log SCTE-35 markers. | | SCTE-35 Alerts | Shows if the Source is enabled to send alerts for SCTE-35 markers. | | Enable SCTE-35 Insertion | If this setting is enabled, Broadcaster is able to insert a SCTE-35 marker to the stream based on a placement by an external system through the ESAM agent. When the placement opportunity occurs, the ESAM agent generates an API call to the Broadcaster, which initiates the insertion of the SCTE-35 marker into the input stream. | | Frame Thinning Latency | The Frame Thinning feature removes frames from the stream to get to a lower bitrate if the stream is traversing a crowded network instead of using transcoding to lower the bitrate. To allow the analysis and selection of the frames, Broadcaster needs a buffer. The setting specifies the buffer size (latency) that is allowed in milliseconds in order to remove these frames. The higher the thinning latency, the more accurate results the thinner will reproduce. Recommended/reasonable value is 1 second.
O ms - Frame Thinning is disabled. | | Frozen Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a frozen video state. | | Blank Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a blank video state. | | Health | The current Health score of the source | | Location | The location of the Source. | | Network | The ISP/ network of the Source. | | Source Password | Click **Show** to display the Source's password. Click Copy to copy the password. | | Certificate | Indicates whether the DTLS certificate has been installed and its expiration date. | | **PID Mapping** | | | Events Configuration Profile | The Events Configuration Profile that was selected for this source. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Input | The details of the source’s input. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Target Broadcaster/s | Specifies which Broadcaster/s within the cluster on which ZEN Master can deploy the source. | | Application | The application used to process the Source. | | Device | The OS of the Origin Broadcaster machine. | | Build | The Build version of the Origin Broadcaster. | | Encrypted | If one of the Encryption methods was selected, in the Encryption Key field, enter an encryption key that will be used to encrypt the connection OR click Random to generate a random encryption key. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | Public Output | If enabled, it allows access to the stream directly through a supported player. | | Preserve closed captions | If enabled, closed captions are preserved for this Source. | | Alert on PID Changes | Shows if the Alert on PID changed is enabled/disabled. This feature generates email notifications whenever a PID change is detected In the Configuration section. | | Content Analysis | Shows if the Content Analysis is enabled/disabled. Content Analysis shows errors detected in the audio and video content itself. | | Hide Thumbnail | Shows if the Source is enabled to hide the Source's thumbnail from where it is displayed (e.g., the Preview Pane, Grids, etc.). | | SCTE-35 Alerts | Shows if the Source is enabled to send alerts for SCTE-35 markers. | | Enable SCTE-35 Insertion | If this setting is enabled, Broadcaster is able to insert a SCTE-35 marker to the stream based on a placement by an external system through the ESAM agent. When the placement opportunity occurs, the ESAM agent generates an API call to the Broadcaster, which initiates the insertion of the SCTE-35 marker into the input stream. | | Frame Thinning Latency | The Frame Thinning feature removes frames from the stream to get to a lower bitrate if the stream is traversing a crowded network instead of using transcoding to lower the bitrate. To allow the analysis and selection of the frames, Broadcaster needs a buffer. The setting specifies the buffer size (latency) that is allowed in milliseconds in order to remove these frames. The higher the thinning latency, the more accurate results the thinner will reproduce. Recommended/reasonable value is 1 second.
O ms - Frame Thinning is disabled. | | Frozen Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a frozen video state. | | Blank Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a blank video state. | | **Pull** | | | Events Configuration Profile | The Events Configuration Profile that was selected for this source. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Input | The details of the source’s input. | | Location | The location of the Source. | | Network | The ISP/ network of the Source. | | Remote Host | The host name/number of the remote server. | | Remote Port | The port on the remote server. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Target Broadcaster/s | Specifies which Broadcaster/s within the cluster on which ZEN Master can deploy the source. | | Encrypted | If one of the Encryption methods was selected, in the Encryption Key field, enter an encryption key that will be used to encrypt the connection OR click Random to generate a random encryption key. | | Public Output | If enabled, it allows access to the stream directly through a supported player. | | Preserve closed captions | If enabled, closed captions are preserved for this Source. | | Alert on PID Changes | Shows if the Alert on PID changed is enabled/disabled. This feature generates email notifications whenever a PID change is detected In the Configuration section. | | Minimize Latency | If enabled, Zixi adjusts the latency dynamically to optimize it for network conditions. | | Content Analysis | Shows if the Content Analysis is enabled/disabled. Content Analysis shows errors detected in the audio and video content itself. | | Hide Thumbnail | Shows if the Source is enabled to hide the Source's thumbnail from where it is displayed (e.g., the Preview Pane, Grids, etc.). | | SCTE-35 Alerts | Shows if the Source is enabled to send alerts for SCTE-35 markers. | | Enable SCTE-35 Insertion | If this setting is enabled, Broadcaster is able to insert a SCTE-35 marker to the stream based on a placement by an external system through the ESAM agent. When the placement opportunity occurs, the ESAM agent generates an API call to the Broadcaster, which initiates the insertion of the SCTE-35 marker into the input stream. | | Frame Thinning Latency | The Frame Thinning feature removes frames from the stream to get to a lower bitrate if the stream is traversing a crowded network instead of using transcoding to lower the bitrate. To allow the analysis and selection of the frames, Broadcaster needs a buffer. The setting specifies the buffer size (latency) that is allowed in milliseconds in order to remove these frames. The higher the thinning latency, the more accurate results the thinner will reproduce. Recommended/reasonable value is 1 second.
O ms - Frame Thinning is disabled. | | Frozen Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a frozen video state. | | Blank Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a blank video state. | | Source IP | The IP address of the Source's input resource. Transcoded – means that the source is transcoded. | | Application | The application used to process the Source. | | Device | The OS of the Origin Broadcaster machine. | | Build | The Build version of the Origin Broadcaster. | | Remote ID | The ID of the Origin ZEC/Broadcaster/Device. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | **SRT** | | | Events Configuration Profile | The Events Configuration Profile that was selected for this source. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Input | The name of the Input stream. | | Location | The location of the Source. | | Network | The ISP/ network of the Source. | | Source IP | The IP address of the Source's input resource. Transcoded – means that the source is transcoded. | | Remote Host | The host name/number of the remote server. | | Remote Port | The port on the remote server. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Target Broadcaster/s | Specifies which Broadcaster/s within the cluster on which ZEN Master can deploy the source. | | Application | The application used to process the Source. | | Device | The OS of the Origin Broadcaster machine. | | Build | The Build version of the Origin Broadcaster. | | Encrypted | If one of the Encryption methods was selected, in the Encryption Key field, enter an encryption key that will be used to encrypt the connection OR click Random to generate a random encryption key. | | Verify Stream ID | If enabled, verifies that the stream ID of this input matches the stream ID in the SRT feed before allowing the connection. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | Latency | The configured latency in milliseconds. | | Public Output | If enabled, it allows access to the stream directly through a supported player. | | Preserve closed captions | If enabled, closed captions are preserved for this Source. | | Alert on PID Changes | Shows if the Alert on PID changed is enabled/disabled. This feature generates email notifications whenever a PID change is detected In the Configuration section. | | Content Analysis | Shows if the Content Analysis is enabled/disabled. Content Analysis shows errors detected in the audio and video content itself. | | Hide Thumbnail | Shows if the Source is enabled to hide the Source's thumbnail from where it is displayed (e.g., the Preview Pane, Grids, etc.). | | SCTE-35 Alerts | Shows if the Source is enabled to send alerts for SCTE-35 markers. | | Enable SCTE-35 Insertion | If this setting is enabled, Broadcaster is able to insert a SCTE-35 marker to the stream based on a placement by an external system through the ESAM agent. When the placement opportunity occurs, the ESAM agent generates an API call to the Broadcaster, which initiates the insertion of the SCTE-35 marker into the input stream. | | Frame Thinning Latency | The Frame Thinning feature removes frames from the stream to get to a lower bitrate if the stream is traversing a crowded network instead of using transcoding to lower the bitrate. To allow the analysis and selection of the frames, Broadcaster needs a buffer. The setting specifies the buffer size (latency) that is allowed in milliseconds in order to remove these frames. The higher the thinning latency, the more accurate results the thinner will reproduce. Recommended/reasonable value is 1 second.
O ms - Frame Thinning is disabled. | | Frozen Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a frozen video state. | | Blank Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a blank video state. | | **Transcoded** | | | Events Configuration Profile | The Events Configuration Profile that was selected for this source. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | | | | Transcoding Profile | Transcoding Profiles – displays all existing Transcoding profiles and details about their configuration. See VIEWING EXISTING TRANSCODING PROFILES. On this screen, you can add new Transcoding Profiles and manage existing Transcoding Profiles. | | Input | The details of the source’s input. | | HTML Overlay URL | The URL of the HTML Overlay. The external HTML will be pulled directly to the processing Broadcaster and rendered over the transcoded video output. For more information, see [HTML Overlay Installation](docId:1svyta7P777nBTqPN8yt8). | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Target Broadcaster/s | Specifies which Broadcaster/s within the cluster on which ZEN Master can deploy the source. | | Encrypted | If one of the Encryption methods was selected, in the Encryption Key field, enter an encryption key that will be used to encrypt the connection OR click Random to generate a random encryption key. | | Public Output | If enabled, it allows access to the stream directly through a supported player. | | Preserve closed captions | If enabled, closed captions are preserved for this Source. | | Alert on PID Changes | Shows if the Alert on PID changed is enabled/disabled. This feature generates email notifications whenever a PID change is detected In the Configuration section. | | Content Analysis | Shows if the Content Analysis is enabled/disabled. Content Analysis shows errors detected in the audio and video content itself. | | Hide Thumbnail | Shows if the Source is enabled to hide the Source's thumbnail from where it is displayed (e.g., the Preview Pane, Grids, etc.). | | SCTE-35 Alerts | Shows if the Source is enabled to send alerts for SCTE-35 markers. | | Ignore Transcode Thresholds | If enabled, the system will override the Transcode thresholds for your Ingest Cluster (i.e. to allow use of full CPU/GPU and memory capacity). | | Source IP | The IP address of the Source's input resource. Transcoded – means that the source is transcoded. | | Device | The OS of the Origin Broadcaster machine. | | Build | The Build version of the Origin Broadcaster. | | Enable SCTE-35 Insertion | If this setting is enabled, Broadcaster is able to insert a SCTE-35 marker to the stream based on a placement by an external system through the ESAM agent. When the placement opportunity occurs, the ESAM agent generates an API call to the Broadcaster, which initiates the insertion of the SCTE-35 marker into the input stream. | | Frame Thinning Latency | The Frame Thinning feature removes frames from the stream to get to a lower bitrate if the stream is traversing a crowded network instead of using transcoding to lower the bitrate. To allow the analysis and selection of the frames, Broadcaster needs a buffer. The setting specifies the buffer size (latency) that is allowed in milliseconds in order to remove these frames. The higher the thinning latency, the more accurate results the thinner will reproduce. Recommended/reasonable value is 1 second.
O ms - Frame Thinning is disabled. | | Encoder | The encoder used for transcoding (decode and reencode processes) | | Frozen Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a frozen video state. | | Blank Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a blank video state. | | **ZEC** | | | Events Configuration Profile | The Events Configuration Profile that was selected for this source. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Input | The details of the source’s input. | | Location | The location of the Source. | | Network | The ISP/ network of the Source. | | Source Password | Click Show to display the Source's password. Click Copy to copy the password. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Target Broadcaster/s | Specifies which Broadcaster/s within the cluster on which ZEN Master can deploy the source. | | Encrypted | If one of the Encryption methods was selected, in the Encryption Key field, enter an encryption key that will be used to encrypt the connection OR click Random to generate a random encryption key. | | Latency | The configured latency in milliseconds. | | Public Output | If enabled, it allows access to the stream directly through a supported player. | | Preserve closed captions | If enabled, closed captions are preserved for this Source. | | Alert on PID Changes | Shows if the Alert on PID changed is enabled/disabled. This feature generates email notifications whenever a PID change is detected In the Configuration section. | | Content Analysis | Shows if the Content Analysis is enabled/disabled. Content Analysis shows errors detected in the audio and video content itself. | | Hide Thumbnail | Shows if the Source is enabled to hide the Source's thumbnail from where it is displayed (e.g., the Preview Pane, Grids, etc.). | | Log SCTE-35 | Shows if the Source is enabled to log SCTE-35 markers. | | SCTE-35 Alerts | Shows if the Source is enabled to send alerts for SCTE-35 markers. | | Enable SCTE-35 Insertion | If this setting is enabled, Broadcaster is able to insert a SCTE-35 marker to the stream based on a placement by an external system through the ESAM agent. When the placement opportunity occurs, the ESAM agent generates an API call to the Broadcaster, which initiates the insertion of the SCTE-35 marker into the input stream. | | Frame Thinning Latency | The Frame Thinning feature removes frames from the stream to get to a lower bitrate if the stream is traversing a crowded network instead of using transcoding to lower the bitrate. To allow the analysis and selection of the frames, Broadcaster needs a buffer. The setting specifies the buffer size (latency) that is allowed in milliseconds in order to remove these frames. The higher the thinning latency, the more accurate results the thinner will reproduce. Recommended/reasonable value is 1 second.
O ms - Frame Thinning is disabled. | | Frozen Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a frozen video state. | | Blank Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a blank video state. | | **Zixi** | | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Target Broadcaster/s | Specifies which Broadcaster/s within the cluster on which ZEN Master can deploy the source. | | Encrypted | If one of the Encryption methods was selected, in the Encryption Key field, enter an encryption key that will be used to encrypt the connection OR click Random to generate a random encryption key. | | Public Output | If enabled, it allows access to the stream directly through a supported player. | | Preserve closed captions | If enabled, closed captions are preserved for this Source. | | Alert on PID Changes | Shows if the Alert on PID changed is enabled/disabled. This feature generates email notifications whenever a PID change is detected In the Configuration section. | | Content Analysis | Shows if the Content Analysis is enabled/disabled. Content Analysis shows errors detected in the audio and video content itself. | | Hide Thumbnail | Shows if the Source is enabled to hide the Source's thumbnail from where it is displayed (e.g., the Preview Pane, Grids, etc.). | | SCTE-35 Alerts | Shows if the Source is enabled to send alerts for SCTE-35 markers. | | Enable SCTE-35 Insertion | If this setting is enabled, Broadcaster is able to insert a SCTE-35 marker to the stream based on a placement by an external system through the ESAM agent. When the placement opportunity occurs, the ESAM agent generates an API call to the Broadcaster, which initiates the insertion of the SCTE-35 marker into the input stream. | | Frame Thinning Latency | The Frame Thinning feature removes frames from the stream to get to a lower bitrate if the stream is traversing a crowded network instead of using transcoding to lower the bitrate. To allow the analysis and selection of the frames, Broadcaster needs a buffer. The setting specifies the buffer size (latency) that is allowed in milliseconds in order to remove these frames. The higher the thinning latency, the more accurate results the thinner will reproduce. Recommended/reasonable value is 1 second.
O ms - Frame Thinning is disabled. | | **RTP** | | | Events Configuration Profile | The Events Configuration Profile that was selected for this source. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Input | The details of the source’s input. | | Source IP | The IP address of the Source's input resource. | | Location | The location of the Source. | | Network | The ISP/ network of the Source. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Target Broadcaster/s | Specifies which Broadcaster/s within the cluster on which ZEN Master can deploy the source. | | Encrypted | If one of the Encryption methods was selected, in the Encryption Key field, enter an encryption key that will be used to encrypt the connection OR click Random to generate a random encryption key. | | Max Bitrate | The maximal bitrate that the stream has reached throughout time. | | Use Forward Error Correction (FEC) | If FEC is enabled, repair packets are sent on additional ports, enabling packet recovery. | | Preserve RTP Headers | If enabled, the system preserves the RTP headers (which include the timestamps and sequences) and propagates them the output. | | Public Output | If enabled, it allows access to the stream directly through a supported player. | | Preserve closed captions | If enabled, closed captions are preserved for this Source. | | Alert on PID Changes | Shows if the Alert on PID changed is enabled/disabled. This feature generates email notifications whenever a PID change is detected In the Configuration section. | | Content Analysis | Shows if the Content Analysis is enabled/disabled. Content Analysis shows errors detected in the audio and video content itself. | | Hide Thumbnail | Shows if the Source is enabled to hide the Source's thumbnail from where it is displayed (e.g., the Preview Pane, Grids, etc.). | | SCTE-35 Alerts | Shows if the Source is enabled to send alerts for SCTE-35 markers. | | Enable SCTE-35 Insertion | If this setting is enabled, Broadcaster is able to insert a SCTE-35 marker to the stream based on a placement by an external system through the ESAM agent. When the placement opportunity occurs, the ESAM agent generates an API call to the Broadcaster, which initiates the insertion of the SCTE-35 marker into the input stream. | | Frame Thinning Latency | The Frame Thinning feature removes frames from the stream to get to a lower bitrate if the stream is traversing a crowded network instead of using transcoding to lower the bitrate. To allow the analysis and selection of the frames, Broadcaster needs a buffer. The setting specifies the buffer size (latency) that is allowed in milliseconds in order to remove these frames. The higher the thinning latency, the more accurate results the thinner will reproduce. Recommended/reasonable value is 1 second.
O ms - Frame Thinning is disabled. | | Frozen Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a frozen video state. | | Blank Video Minimal Duration | Specifies the threshold in seconds afterwhich the Content Analysis will alert on a blank video state. | | Dejitter Clock Source | The mechanism used in the calculation of the jitter:
* Arrival times * RTP timestamps | | Dejitter Buffer | The length of the de-jitter buffer (in milliseconds). The buffer is used to collect packets and measure the jitter of the source that is arriving with jitter. | | **UDP** | | | Events Configuration Profile | The Events Configuration Profile that was selected for this source. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Input | The details of the source’s input. | | Ingest Cluster | The Ingest cluster in ZEN Master that receives this stream. Click on the link to view details about the Ingest Cluster. | | Target Broadcaster/s | Specifies which Broadcaster/s within the cluster on which ZEN Master can deploy the source. | | Encrypted | If one of the Encryption methods was selected, in the Encryption Key field, enter an encryption key that will be used to encrypt the connection OR click Random to generate a random encryption key. | | Public Output | If enabled, it allows access to the stream directly through a supported player. | | Preserve closed captions | If enabled, closed captions are preserved for this Source. | | Alert on PID Changes | Shows if the Alert on PID changed is enabled/disabled. This feature generates email notifications whenever a PID change is detected In the Configuration section. | | Content Analysis | Shows if the Content Analysis is enabled/disabled. Content Analysis shows errors detected in the audio and video content itself. | | Hide Thumbnail | Shows if the Source is enabled to hide the Source's thumbnail from where it is displayed (e.g., the Preview Pane, Grids, etc.). | | SCTE-35 Alerts | Shows if the Source is enabled to send alerts for SCTE-35 markers. | | Enable SCTE-35 Insertion | If this setting is enabled, Broadcaster is able to insert a SCTE-35 marker to the stream based on a placement by an external system through the ESAM agent. When the placement opportunity occurs, the ESAM agent generates an API call to the Broadcaster, which initiates the insertion of the SCTE-35 marker into the input stream. | | Frame Thinning Latency | The Frame Thinning feature removes frames from the stream to get to a lower bitrate if the stream is traversing a crowded network instead of using transcoding to lower the bitrate. To allow the analysis and selection of the frames, Broadcaster needs a buffer. The setting specifies the buffer size (latency) that is allowed in milliseconds in order to remove these frames. The higher the thinning latency, the more accurate results the thinner will reproduce. Recommended/reasonable value is 1 second.
O ms - Frame Thinning is disabled. | | Dejitter Clock Source | The mechanism used in the calculation of the jitter:
* Arrival times * RTP timestamps | - [Source Diagram](docId\:l4l9iLS6MUqI4um1l0pqz) [title] Creating a New Redirection Rule [path] ZEN Master/ZEN Master User Guide/Broadcasters/Creating a Broadcaster Cluster/ By default in case of a Pull stream in Zixi Broadcaster uses the DNS to resolve the IP of its destination. However, if you are pulling the stream from one cluster to another and both clusters are hosted within the same cloud region, you may want to avoid going through an external DNS server. Another scenario is that for security reasons the traffic cannot flow outside the network. By creating a redirection rule, you can specify specific routing rules for Pull requests from clusters or CIDR IP Ranges. Rules can be applied to the client end-point Cluster, or IP CIDR Range, from where the pull request is initiated. Rules are evaluated in order from lowest order to highest. You can specify the order of a rule in the rule configuration. The first matching rule will apply. If there is no match, the default rule Prefer public IP with DTLS will be used. :::hint{type="info"} - It is possible to use this as feature as an allow list by creating a 0.0.0.0/0 block rule and give it the highest order. In this case, any connection not matched by a rule with a lower order will finally be matched by the blocking rule. - Private/NIC CIDR do not support DTLS and will redirect to a non-DTLS port. ::: ## To create a new redirection rule: ::::WorkflowBlock :::WorkflowBlockItem Go to **Broadcasters** and select a **Cluster**. ::: :::WorkflowBlockItem Click the **Redirection Rules **tab. ![Redirection Rules](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/lzZUN-_xc2cSzd5pOHde-_image.png) ::: :::WorkflowBlockItem Click **Add Rule**. ![Add Rule button](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/7LH9JK9pf6XJHY1Ks1ou4_image.png) The **Create Redirection Rule** dialog is displayed: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/-tfr6jODhw9nykmMJ-SGL_image.png" size="80" width="374" height="460" position="center" alt="Create Redirection Rule" showCaption="false"} ::: :::WorkflowBlockItem In the **Description** field, write a description for the rule. ::: :::WorkflowBlockItem In the **From** field, select one of the following: 1. **Cluster** - select this option to apply this rule on a Pull Request from a Cluster. 2. **CIDR** - select this option to apply this rule on a Pull Request from a CIDR IP range. CIDR rules apply to any Zixi pull request, including those from ZECs, IRDs etc. ::: :::WorkflowBlockItem If you have selected the **Cluster **option, in the **Cluster** field, select the **Cluster** from which the Pull Request is sent. ::: :::WorkflowBlockItem If you have selected the **CIDR** option, in the **CIDR** field specify the CIDR IP range. ::: :::WorkflowBlockItem In the **To** field, select one of the following redirection options: 1. **Redirect to public IP** - pull requests that match this rule will be resolved by redirecting it through a public IP. This is the default behavior. 2. **Redirect to private IP** - pull requests that match this rule will be resolved by redirecting it through a private IP. 3. **Redirect to NIC** - pull requests that match this rule will be resolved by redirecting it to a specific NIC. 4. **Block **- pull requests that match this rule will be blocked. ::: :::WorkflowBlockItem If you have selected the **Redirect to NIC** option, in the **NIC CIDR** field, specify the CIDR IP range of the NIC. ::: :::WorkflowBlockItem In the **Latency Override** field, specify the latency when the redirection rule applies. Latency is determined by the following order: Redirection rule latency -> source autopull/pull target latency -> default 1000ms. ::: :::WorkflowBlockItem In the **Order** field, specify the order value for this rule. Rules are evaluated from lowest to highest order, the first rule that matches will be applied. ::: :::WorkflowBlockItem Click Save. ::: :::: [title] Adding an ST 2110 JPEG XS MediaConnect Source [path] ZEN Master/ZEN Master User Guide/Sources/Adding AWS Media Sources/Adding an AWS MediaConnect Source/ This Source is configured on an **AWS MediaConnect** that serves as the **Ingest Object**. The stream originates from any non-Zixi device (e.g., encoder, IRD, etc.), which serves as the **Origin**. The stream uses the ST 2110 JPEG XS protocol. The Origin is not managed by ZEN Master. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-xZ6QuRaTDHXrizvhjQiO_-20250811-134858.png) The following procedure describes how to create an ST 2110 JPEG XS MediaConnect Source. In addition, an explanation of each of the configuration parameters is given in the table below. **To create a ST 2110 JPEG XS MediaConnect Source:** ::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The Create New Source window is displayed. ![Create New Source window](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/AxSEVtTg03J7Up0wQFdjQ_image.png) ::: :::WorkflowBlockItem Under **AWS Media**, click on **AWS MediaConnect**. The Create New AWS Media Source window opens. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-_X1H9JyJG1N1nF9tgTUKg-20250713-113617.png) ::: :::WorkflowBlockItem In the **Info **section, in the **Name** field, type a logical name for the 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. *Events Profiles* consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. ::: :::WorkflowBlockItem In the **Input** section, under **Protocol**, select the **ST 2110 JPEG XS** radio button.  ::: :::WorkflowBlockItem In the **Max sync buffer** field, specify the size of the buffer that will be used to synchronize incoming source data. This value is measured in milliseconds (ms). ::: :::WorkflowBlockItem In the **Initial State** section, select the **Muted** checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. You can Unmute the Source at any time. ::: :::WorkflowBlockItem Click **Save**. ::: :::: **Parameters Table** | **Parameter** | **Description** | | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the AWS Media 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. | | ***Input*** | | | Protocol | To create a **ST 2110 JPEG XS** protocol Input AWS Media Source, verify that **ST 2110 JPEG XS** is selected. | | Max sync buffer | Specify the size of the buffer that will be used to synchronize incoming source data. This value is measured in milliseconds (ms). Default - 200 | | ***Initial State*** | | | Muted | Select this checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. | [title] Viewing Existing Broadcasters [path] ZEN Master/ZEN Master User Guide/Broadcasters/Viewing Existing Clusters/ To view the full list of Broadcasters, from the main Broadcasters screen, click the **Broadcasters** view button. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/yq8ewoEBsx7xz2X8Joj3L-20260111-110700.jpg) To view the Broadcasters of a specific Broadcaster Cluster, from the Clusters screen, click the dropdown arrow of a specific Broadcaster Cluster to view its related Broadcasters. The following is a brief description of the sections that are shown: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/sO6f-i6qpg72qfgxtQhRl-20260111-114524.jpg) When a Broadcaster is selected, the following tabs are shown at the right side of the screen: - ***History*** - shows a graphical representation of the system usage over time. If you see an issue and want to open an Incident for further examination, click the **Open Incident** button and follow the instructions in [Creating an Incident Manually](docId\:aomjabSyzYLzY3GQ4zH8o) . The following graphs are shown. 1. ***System*** - shows system performance metrics over time. For broadcasters that are using NVIDIA GPU for transcoding, the History graph shows the GPU usage of the encoder pipeline, decoder pipeline and CUDA pipeline. The GPU memory consumption is also shown. 2. **Network** – shows the send and receive bitrates over time. 3. **UDP** **Statistics** - shows a graphical representation of the UDP Receive Errors that occurred over time. (This is helpful for isolating errors that occurred on the broadcaster itself from errors that occurred in the network). - ***Active Objects*** – lists the objects that are related to the Broadcaster with their statuses. Click on the object’s name to view the object’s details. - ***Details*** - shows details about the broadcaster (e.g. IP, Host ID, Version etc.) as well as its status and license status. It also shows details about the protocol and ports used by the Broadcaster. If there is a configuration error then click the **Update Configuration** button to automatically update the configuration settings. This may require a restart of the Broadcaster. - ***Events*** – shows all events related to this Broadcaster that have been generated by the system, such as connections, errors, warnings and disconnections. To learn about the data that is displayed in the Events tab see [Events](docId\:BgoWcWCc5rMvqDKmLBTtQ) . Click **Quick Report** to generate a report of events related to this Channel and download the .xls file. - ***Changes***– displays the history of changes that were made to the object configuration. - ***Incidents***– displays a list of the incidents concerning this Broadcaster. Incidents groups together errors relating to the Source into incidents to simplify the process of identifying the common root cause. Incidents can be manually created or automatically generated. - ***Notes ***– free-form text can be added with pertinent information about this Broadcaster. - [Broadcaster Details](docId:3znlWTlZ5djBOiYba6h20) - [Viewing Broadcaster Active Objects](docId\:yFRwMx4J_4vr1ykI0EsTb) - [Broadcaster History](docId\:D75iFW_FOZXfd-Pptvxdw) - [Actions on Broadcasters](docId\:B1y6nShFZcUwCd0_GSPG-) [title] Broadcasters Info Pane [path] ZEN Master/ZEN Master User Guide/Broadcasters/Viewing Existing Clusters/Viewing Existing Broadcasters/ To view the full details of a specific Broadcaster, click on it from the list. The **Info Pane** includes the following details: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/dC3-Q_eWb9CUYNcE8shT--20260111-111130.jpg) | Parameter | Description | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | CPU  | The CPU utilization rate. | | RAM | The memory utilization rate. | | HDD | The Hard Drive utilization rate. | | In Bitrate | The inbound bitrate | | Out Bitrate | The outbound bitrate | | Inputs | The number of inputs | | Adaptive | The number of adaptive streams | | Outputs | The number of outputs | | Uptime | The time period that the Broadcaster has been online. | | Open | Click to access the Zixi Broadcaster UI.  | | Public IP | The public IP address of the Broadcaster. Click the copy icon to copy the details. | | Private IP | The private IP address of the Broadcaster. Click the copy icon to copy the details. | | Version | The software version of the Broadcaster. Click the copy icon to copy the details. | | AgentZ | Indicates whether AgentZ has been installed for this Broadcaster. Agent Z is a Sidecar tool that sits on a Zixi Broadcaster, it acquires the system health data and other statistics locally and pushes it to ZEN Master. By enabling this option, ZEN Master will automatically install AgentZ on any existing and future Broadcasters connected to the Cluster. The feature is off by default. Due to AgentZ installation requiring a restart, ZEN Master will not auto-install AgentZ on a Broadcaster that already contains any inputs to avoid disturbing active streams. | | Location | The location of the Broadcaster. By default, the location is determined automatically based on the Broadcaster's IP. However it is possible to specify another location during configuration.  | | Network | The Network in which the Broadcaster is located. The Networks are discovered automatically by ZEN Master using IP-to-location method. A network is defined as an ASN from a specific country and region/state. | - [Broadcaster Details](docId:3znlWTlZ5djBOiYba6h20) - [Viewing Broadcaster Active Objects](docId\:yFRwMx4J_4vr1ykI0EsTb) - [Broadcaster History](docId\:D75iFW_FOZXfd-Pptvxdw) - [Actions on Broadcasters](docId\:B1y6nShFZcUwCd0_GSPG-) [title] Viewing Existing Clusters [path] ZEN Master/ZEN Master User Guide/Broadcasters/ To view the Broadcaster Cluster list, make sure that the **Clusters** view is selected. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ZG7wcdjbNZaldtw-TJHHn-20260118-153029.jpg) The main display (before selecting a specific cluster) includes the following data for each Broadcaster cluster: | **Parameter** | **Description** | | ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Name | The name of the cluster as configured in ZEN Master. | | Status | The connection status of the Broadcaster cluster. Possible values:
* Green (OK) – None of the Broadcasters are in error state. * Red (Error) – all Broadcasters are in error state. * Orange (Warning) - at least one of the Broadcasters is in Warning state.
The 🔕 icon next to a Broadcaster cluster indicates that the Broadcaster cluster is muted, disabling notifications for error/recovery events. | | Broadcasters | The number of related Zixi Broadcasters and their connection status:
* Green – OK (i.e. connected) * Red – error state * Gray – pending/disabled * Orange - warning | | Management | The type of management. Possible types are:
* **Manual** – management is done manually by adding specific Zixi Broadcaster instances (see [Adding a Broadcaster Cluster](docId\:HvUAD4qveuFoJnjHj1gSW) – [Adding a Broadcaster to a Manual Cluster](docId\:xYscySO498lY77ZjQr-51)). * **AWS** – the cluster is managed by ZEN Master in your AWS cloud service (see [Adding a Broadcaster Cluster - Managed](docId:6sLx4TD__ZKr2XFhO8qZ6)). * **Azure **– the cluster is managed by ZEN Master in your Azure cloud service (see [Adding a Broadcaster Cluster - Managed](docId:6sLx4TD__ZKr2XFhO8qZ6)). * **GCP **– the cluster is managed by ZEN Master in your GCP cloud service (see [Adding a Broadcaster Cluster - Managed](docId:6sLx4TD__ZKr2XFhO8qZ6)). | | Instance Type (for Managed clusters) | The Instance Type the cloud service account is using. | | Region | Cloud service region | | Tags | The Tags that are associated with this cluster.
Tags are managed by Administrators via Configuration > Tags and assigned to non-Admin users via Roles. Click to edit. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Cluster has been enabled. * No - the Priority checkbox of the Access Tag of this Cluster has been enabled. | The Broadcaster Cluster screen displays all existing clusters, and information about the clusters' status and configuration. Broadcaster Clusters that include configured Broadcasters in them are marked with a drop-down icon. Clicking the drop-down icon reveals the underlying Broadcasters. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/oU87WvY4xpwHBXwcea5-U-20260129-100726.jpg) When one of the clusters is selected, the details of that cluster, divided into tabs, appears at the right side of the screen. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/2VO-Kl2cp7uKQr89KMb6l-20251125-154933.jpg) | **Parameter** | **Description** | | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Name | The name of the Zixi Broadcaster. | | Status | The connection status of the Zixi Broadcaster:
* Green – OK * Red – error state * Gray – pending/disabled * Orange - warning
The wrench icon indicates that maintenance mode is turned on, which prevents new streams from being assigned to this Broadcaster. | | CPU | The percentage of CPU utilization on the Zixi Broadcaster machine. | | RAM | The percentage of RAM utilization on the Zixi Broadcaster machine. | | HDD | The percentage of hard disk utilization on the Zixi Broadcaster machine. | | In Bitrate | The inbound bitrate in kbps | | Out Bitrate | The outbound bitrate in kbps | | Streams | The total number inputs, outputs and adaptive groups currently active on the Broadcaster. | | Uptime | The time period that the Zixi Broadcaster has been online. | | Primary | Yes - the Broadcaster is configured as "primary". No - the Broadcaster is configured as "backup". | | Public IP | The IP address of the Broadcaster. | | OS | The OS of the Broadcaster machine. | | Instance Id | The cloud instance type. | | Version | The software version of the Zixi Broadcaster. | | AgentZ | Indicates whether AgentZ has been installed for this Broadcaster. Agent Z is a Sidecar tool that sits on a Zixi Broadcaster, it acquires the system health data and other statistics locally and pushes it to ZEN Master. By enabling this option, ZEN Master will automatically install AgentZ on any existing and future Broadcasters connected to the Cluster. The feature is off by default. Due to AgentZ installation requiring a restart, ZEN Master will not auto-install AgentZ on a Broadcaster that already contains any inputs to avoid disturbing active streams. | - [Broadcasters Clusters Creating Redirection Rules](docId:9mshRNjfil6cvjqKqHdPV) - [Viewing Existing Cluster Info Pane](docId\:IkXEjEcr15mhATLHUK8kX) - [Viewing Clusters Details](docId\:jiNtNPOFH46khVsGGT_uG) - [Actions on Broadcaster Clusters](docId\:hhnFwk0IR570I05ruBqp-) - [Viewing Existing Broadcasters](docId\:bWnGCh0s5T0ogkLBUFlLa) [title] Adding a Source - NDI [path] ZEN Master/ZEN Master User Guide/Sources/Adding ZEN Master Sources/ ZEN Master can receive a Source directly from an NDI input. Because NDI streams are provided to the Broadcaster as raw video frames, you need to encode the stream by selecting a Transcoding Profile that encodes both the video and audio (i.e. doesn't pass through either the video or audio). :::hint{type="info"} - NDI Sources are only supported on v14+ Broadcasters. - PID Mapping and SCTE 35 logging are not available with NDI because this data does not appear in NDI streams. - NDI sources can be resized but not padded with black bars. Enabling the “Keep aspect ratio” checkbox in the transcoding profile will cause the transcoder to fail ::: The following procedure describes how to add an NDI Source in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. ## To add an NDI Source: :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Source selection** window is displayed. ![Create Source Options](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-3mXDQJHXUppSRZJSBYBnR-20250805-132303.png) ::: :::WorkflowBlockItem Click on **NDI**. The **Create New NDI Source** window opens. ![New NDI Source](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-BJVDkqfmfUkkcVGd70e_6-20250519-185519.png) ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, enter a unique name to identify this Source in the system. ::: :::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: - Click on the **Edit** icon next to the **Location **field. A search box is shown below the **Location** field. - Enter identifying info for the location (e.g. street address, zip code, coordinates). Search results are displayed below the search box as you type. - Click on the desired location. The selected location populates the **Location** field. ::: :::WorkflowBlockItem In the ** Configuration** section, 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 preference. 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 **NDI Stream** field, select from the drop-down list the desired NDI stream on the local network where the Broadcaster is hosted. ::: ::::WorkflowBlockItem In the **Profile** field, select one of the pre-configured Profiles to apply to this Source. If you would like to create a new transcoding profile, see [Adding Transcoding Profiles](docId:3L1DNIo6v_15jzCFdhRKN) . :::hint{type="info"} You must select a Transcoding Profile that either encodes both the video and audio or transcodes one and removes the other. A profile that passes through either the video or audio cannot be used. ::: :::: ::::WorkflowBlockItem If you would like to assign the transcoding process to a multi GPU Broadcaster, select the **Assign to GPU** checkbox, and then select from the drop-down list the desired GPU instance. Options are: 0(default), 1, 2 and 3. :::hint{type="info"} This feature is useful if you are running several heavy transcoding activities, as it enables you to distribute the load among several different GPUs. ::: :::: :::WorkflowBlockItem In the **Pad to CBR** field, enter the amount of CBR padding to be added (in kbps). ::: :::WorkflowBlockItem In the **Audio Reference Level** field, enter the audio reference level (0-20). ::: :::WorkflowBlockItem If you would like to generate email notifications whenever a PID change is detected, select the **Alert on PID changes **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 closed captions, select **Monitor CEA-608 **checkbox**.** :::hint{type="info"} Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: If you would like to monitor CEA-708 closed captions, select **Monitor CEA-708 **checkbox**.** :::hint{type="info"} Monitoring CEA-708 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: :::: ::::WorkflowBlockItem If you would like to disable auto-pull, select the **Disable Auto-Pull** 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. (Default: 1000 ms) ::: ::::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 Additional SCTE-35 options are available when you expand the **SCTE-35 Manipulation** section: ![SCTE-35 Manipulation](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/FxvVWM-bhpg9ZdVYW_LCl-20251104-153319.png) Here you can: - Enable SCTE-35 Insertion - Specify the length of a search window for a NULL packet for SCTE-35 intertion - Set the SCTE-35 PID - Remove any existing SCTE-35 messages from the stream See the **Parameters Table** below for an explanation of these options. ::: :::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. ::: :::WorkflowBlockItem Under **Audio Sources Configuration**, assign one or more audio channels to one or more Audio PIDs. Following the assignment of the audio channels to the audio PIDs, you will be able to encode them separately and include them in the MPEG-TS. For example: Let's assume the NDI source has 8 audio channels (0...7). You can create 4 audio PIDs with the following configurations: PID 1002: 0,1 PID 1003: 2,3 PID 1004: 4,5,6,7 PID 1005: 2,3 To assign channel(s) to a PID: - Under **Channel**, assign a channel to the PID by selecting a channel for from the drop-down menu. - Repeat the process to add additional channels to the PID. - To configure additional PIDs, click **Add+** and select the corresponding channel(s). ::: :::WorkflowBlockItem If you would like to adjust the advanced settings, click **Advanced**. The **Advanced** settings fields are displayed: ![Advanced settings ](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-7D34UCDnshlDBB7sY8bbj-20250804-170318.png) ::: :::WorkflowBlockItem If you would like to track usage for this Source, enter your **Billing Code** details. See [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ). ::: :::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 Click **Save**. ::: ::::: ## NDI Source Configuration Parameters Table | **Parameter** | **Description** | | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | ***Info*** | | | Name | Specify a name for the NDI 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. | | ***Configuration*** | | | Ingest Cluster | Select from the drop-down list one of the available Ingest Clusters as the destination for the Source. | | Target Broadcaster/s | 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.*
Note: For managed clusters, it is not recommended to select a specific Broadcaster, as the Broadcaster’s availability may not remain stable. | | NDI Stream | Select from the drop-down list the NDI stream on the local network where the Broadcaster is hosted. | | Profile | Select one of the pre-configured transcoding profiles to apply to this Source. If you would like to create a new transcoding profile, see [Adding Transcoding Profiles](docId:3L1DNIo6v_15jzCFdhRKN) .
Note: You must select a Transcoding Profile that either encodes both the video and audio or transcodes one and removes the other. A profile that passes through either the video or audio cannot be used. | | Assign to GPU | Select this checkbox if you would like to assign the transcoding process to a multi GPU Broadcaster, and then select from the drop-down list the desired GPU instance. Options are: 0 (default), 1, 2, and 3.
Note: This feature is useful if you are running several heavy transcoding activities, as it enables you to distribute the load among several different GPUs. | | Pad to CBR \[kbps] | Specify the amount of CBR padding to be added (in kbps). | | Audio Reference Level | Specify the audio reference level (0-20). | | Alert on PID changes | If you would like to generate email notifications whenever a PID change is detected, 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. | | Hyde Thumbnail | Disables the Source thumbnail from appearing in the Sources list and other places. Disabling thumbnail may improve system performance. | | Monitor CEA-608 Closed Captions | If you would like to monitor CEA-608 closed captions, select this checkbox.
Note**:** Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. | | Monitor CEA-708 Closed Captions | If you would like to monitor CEA-708 closed captions, select this checkbox.
Note**:** Monitoring 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. | | Auto-Pull Latency | 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) | | 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. | | ***SCTE-35 Manipulation *** | | | Enable SCTE-35 Manipulation | Select checkbox to enable SCTE-35 Manipulation. | | SCTE-35 PID | Set the SCTE-35 PID in which the messages will be inserted. | | Remove Existing SCTE-35 | Remove any existing SCTE-35 messages from the stream. | | Replace with NULL | Replace any existing SCTE-35 messages with NULL. | | ***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/recovery notifications for this Source upon initial configuration. | | **Audio Sources Configuration** | | | Audio Sources Configuration | NDI input support up to 16 audio channels. The Audio Sources Configuration, allows you to select which channel(s) should be allocated to a certain audio PID. You can add multiple audio PIDs and mix and match. | | Audio PID Channels | Select a channel from the drop down menu to be allocated to the Audio PID. You can select multiple channels for a single Audio PID. To configure additional PIDs, click **Add+** and select the corresponding channel(s). | | ***Advanced*** | | | Auto-Pull Billing Code | Specify the maximum transmission unit (largest data packet that a network-connected device will accept) in bytes for the Auto Pull. | | Auto-Pull Billing Password | Enter the password that corresponds to this auto-pull billing code. | | 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. | | 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 for empty audio streams to prevent false warnings - enter a comma-delimited list of PID numbers that should not be monitored for null content. | [title] Adding Transcoded Channels [path] ZEN Master/ZEN Master User Guide/Channels/ Transcoded channels transcode a single source into multiple bitrates for output to an HTTP or S3 target. :::hint{type="info"} For a comparison of transcoders - codecs and color support - see [Comparison of Transcoders: Video Codec and Color Support](docId:0kUGUMogtknAKZY-UG6Qs). ::: Supported Video and Audio formats include: - **Video Decoding** – MPEG2, H.264/AVC , H.265/HEVC - **Video Encoding** – MPEG2, H.264/AVC , H.265/HEVC - **Audio Decoding** – AAC, MPEG-1 Audio Layer I / II / III, MPEG-2 Audio Layer I / II / III, AC-3 (Dolby Digital) :::hint{type="info"} For AC-3, which can contain up to six discrete channels of sound, the transcoder only supports the left and right channels and will ignore the other channels. ::: - **Audio Encoding** – AAC, AAC-HE (High Efficiency) and AAC-HEv2; Pass through (no encoding) – any audio codec (MPEG1/2 / AAC / AC-3, E-AC-3 (Dolby Digital Plus). :::hint{type="info"} AAC-HE and AAC-HEv2 are only supported for Zixi Broadcasters, v13 and up. ::: The following procedure describes how to add a Transcoded Channel in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. ## To add a Transcoded Channel: :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click** Channels**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Channel** selection menu is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/9qvMY-FsApjKFyZ_GIVGQ_image.png" size="90" width="1060" height="542" position="center" alt="Create New Channel selection menu" darkWidth="1060" darkHeight="542" showCaption="false"} ::: :::WorkflowBlockItem Click on **Transcoded**. The **Create Transcoded Channel** window is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/dFNJEtQZ2x9Lik5VZvv9i-20260209-191854.png" size="70" width="1190" height="3475" position="center" alt="New Transcoded Channel" darkWidth="1190" darkHeight="3475" showCaption="false"} ::: :::WorkflowBlockItem In the **Info** section, in the** Name** field, enter a logical name for the Channel. ::: :::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 an Tag, you are relating this Channel 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 Channel. 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 In the **Configuration** section, in the **Processing Cluster** field, select from the drop-down list one of the Channel Processing clusters that has been configured in ZEN Master. The selected cluster will be used to process this Channel. :::hint{type="info"} - For heavy transcoding processes, use a Processing Cluster with a GPU. ZEN Master supports use of AWS, GCP and Azure instances that include Nvidia GPU. - If the Source does not exist in the cluster, then the cluster will pull the Source automatically. - If you are assigning the Transcoded Channel to a specific Broadcaster, make sure that the Broadcaster has sufficient available resources (CPU, GPU etc.) to handle the additional load. ::: :::: ::::WorkflowBlockItem In the **Target Broadcaster/s** field, select your broadcaster preference. 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 **Source** field, select from the drop-down list the desired Source. ::: :::WorkflowBlockItem If you want to configure an alternative path for disaster recovery, in the **Alternative Channel (Disaster Recovery)** field, select the Channel that will be used as the alternative path. For more details, see [Disaster Recovery (Alternative Path)](docId\:poo4ZS1-ZjRa1snDylqE0). ::: ::::WorkflowBlockItem If you would like to enable the channel to be delivered to [TAMS](docId\:Xb6n9zuNCcGOdDaBrvsba), check **TAMS Enabled** - note that to deliver to TAMS, you must be using a v19 Broadcaster (or later). When you check the box, a new set of fields is revealed under **Include Source:** ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/8Egtxjnd-9BH5ers1OQzb-20260209-193449.png" size="50" width="966" height="356" position="center" alt="TAMS source fields" darkWidth="966" darkHeight="356" showCaption="false"} The Bitrate field is optional (but see the notes in the Parameters Table below). For sources that will be delivered to TAMS, the IDs for the video and audio streams are required, and in the form of UUIDs. :::hint{type="warning"} Note: the **Support MultiAudio** option in the **Advanced** settings **must be selected **for channels that will be delivered to TAMS. ::: :::: :::WorkflowBlockItem If you would like to pass the original **Source **through, then do the following: - Select the **Include Source** checkbox. - Enter the desired Bitrate for this Source. ::: :::WorkflowBlockItem In the **Slate Source** field, select a source (typically a File source), which will be streamed as a technical fallback slate. This option is available when transcoding to a multi-bitrate ladder and not passing through the original source. ::: :::WorkflowBlockItem If you would like to log the HLS Ad Markers for this Channel, select the **Log HLS Ad Markers** checkbox. ::: :::WorkflowBlockItem If you would like to preserve closed captions for this Channel, verify that the **Preserve closed captions **checkbox is selected (default). ::: :::WorkflowBlockItem If you would like to crop the input stream, select the **Crop** checkbox and set the cropping parameters as follows: ::Image[]{src="https://app.archbee.com/api/optimize/yloo8L9Y5DmjuuW_iCtAX-thAwdz-cboU08BaixNxg0-20250727-115948.png" size="82" width="900" height="269" position="center" alt="Crop Settings" darkWidth="900" darkHeight="269" showCaption="false"} 1. In the **Units** section, select the type of units used to define the crop. Options are: *Pixels* or *Percentages*. 2. Enter the crop position for each of the parameters *Left*, *Top*, *Width* and *Height* in the appropriate fields. ::: :::WorkflowBlockItem In the **Renditions** section add one or more Transcoding Profiles to the Channel and configure the bitrate for each profile. This is done as follows: 1. Find the Transcoding Profile that you would like to add either by scrolling through the list of available profiles or by entering a search word into the **Filter** text-box. If the Transcoding Profile that you would like to add is not yet configured in ZEN Master see [Adding Transcoding Profiles](docId:3L1DNIo6v_15jzCFdhRKN) . 2. Add a Transcoding Profile by clicking the **+** button next to the profile. 3. Click on the Bitrate textbox for the profile and enter the expected bitrate. Default: the estimated bitrate based on the transcoding profile. **Note: **The value should be the sum of the video and audio bitrates plus a small amount to account for streaming overhead. By default, a value is assigned based on the transcoding profile. For Sources in which either the video, audio or both are not transcoded, the user must manually input the value based on the actual bitrates of the Source. It is important to enter an accurate value since it will be included in the HLS/DASH manifest. 4. If you would like to assign the transcoding process to a multi GPU broadcaster, select the **Multi GPU** checkbox, and then select from the drop-down list the desired GPU instance. Options are: 0 (default), 1, 2 and 3. **Note:** This feature is useful if you are running several heavy transcoding activities, as it enables you to distribute the load among several different GPUs. 5. Repeat the above procedure for each Transcoding Profile that you would like to add to the Channel. **Note:** If you would like to remove a Transcoding Profile from the Channel, click on the **-** button next to the Source. ::: ::::WorkflowBlockItem If you would like to assign the transcoding process to a multi GPU Broadcaster, select the **Multi GPU** checkbox. :::hint{type="info"} This feature is useful if you are running several heavy transcoding activities, as it enables you to distribute the load among several different GPUs. ::: :::: :::WorkflowBlockItem Select the **Ignore Transcode Thresholds** checkbox if you would like to override the Transcode thresholds on your Ingest Cluster (i.e. to allow use of full CPU/GPU and memory capacity). ::: :::WorkflowBlockItem In the **Initial State** section, select the **Disabled** checkbox if you would like to disable this Channel upon initial configuration. ::: ::::WorkflowBlockItem Select the **Muted** checkbox if you would like to disable error/recovery notifications for this Channel upon initial configuration. :::hint{type="info"} You can Enable/Unmute the Channel at any time. ::: :::: :::WorkflowBlockItem If you would like to configure the Billing Code and/or customize the HLS/CMAF (DASH + fMP4 HLS) configuration, click **Advanced** (for Broadcasters running v12+). The **Advanced** settings are displayed. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/zWr8yTA-bL1aPXVT9HJiy_segmentation-timecode.png) ::: :::WorkflowBlockItem If you would like to track usage for this Channel, enter your **Billing Code **details. See [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ) . ::: :::WorkflowBlockItem Under **HLS**, set the values for the ***Segments*** and ***Segment Duration***, or if you would like to disable HLS, deselect the checkbox. ::: :::WorkflowBlockItem If you would like to enable **CMAF (DASH + fMP4 HLS)**, select the checkbox and set the values for the ***Segments*** and ***Segment Duration.*** ::: :::WorkflowBlockItem If you would like to convert the captions format from CEA-708 to WebVTT, then select the **Convert CEA-708 to WebVTT **checkbox. ::: ::::WorkflowBlockItem If you check the **Convert CEA-708 to WebVTT **checkbox, a set of options for positioning the WebVTT captions will appear: ::Image[]{src="https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/cb0A07nEA76HF7ArFIuw1-20251022-192424.png" size="80" width="1194" height="454" position="center" alt="Options for Positioning Captions" darkWidth="1194" darkHeight="454" showCaption="false"} :::hint{type="info"} **Note: Positioning captions requires Broadcaster v18.8 or later.** ::: :::: :::WorkflowBlockItem Under **Timecode (EXT-X-PROGRAM-DATE-TIME) Source**, select your preference for inserting a timecode. Options are: *None*, *System time* (default), *SEI Timecode, or Segmentation Time.* ::: :::WorkflowBlockItem Select the **Disable Renditions Synchronization** checkbox if you would like to disable synchronization between the Sources. (Supported for Broadcasters v14.8+) ::: :::WorkflowBlockItem Select the **Drop Unaligned Segments** checkbox, if you want to drop segments of a multi-bitrate adaptive group that are not aligned. These segments will not be included in the playlist. ::: :::WorkflowBlockItem Select **Force I-Frames on SCTE-35 markers **if a SCTE35 marker is detected and it contains a specific video timestamp (PTS), the encoder will generate an IDR-frame on the video frame with the closest or equal timestamp. If there is no timestamp in the SCTE35 marker, the transcoder will generate an IDR frame as soon as it can. ::: :::WorkflowBlockItem Select **Segment on SCTE-35 **if you want to use the SCTE-35 markers found in the source input to segment the stream and the #EXT-X-CUE-IN/#EXT-X-CUE-OUT tags will be added to the manifest. ::: :::WorkflowBlockItem Select **Don't add** **EXT-X-CUE-IN **to remove the EXT-X-CUE-IN tag, which indicates where to return back to the program, from the playlist. ::: :::WorkflowBlockItem In the field **SCTE-35 tag **field, select the ad marker tag that will be used to segment the stream: - EXT-X-CUE – cue-in and cue-out ad markers. - EXT-X-DATERANGE - With EXT-X-DATERANGE ad marker tags, you use SCTE35-OUT attributes to specify the timing of the ad avail. - EXT-X-CUE and EXT-X-DATERANGE – Zixi will use both ad marker tags to segment. - EXT-X-CUE & EXT-OATCLS-SCTE35 - the EXT-OATCLS-SCTE35 marker tag includes the Base-64 encoded SCTE payload. Zixi will use both ad marker tags to segment. ::: :::WorkflowBlockItem In the field **Segments between EXT-X-PROGRAM-DATE-TIME tags **field, בonfigure the the frequency in which the EXT-X-PROGRAM-DATE-TIME tags will appear in the manifest by specifying the number of segments between each EXT-X-PROGRAM-DATE-TIME tag. ::: :::WorkflowBlockItem Select **Drop first segment **to drop the first segment in the manifest. For HLS workflows, this can help ensure smoother playback by eliminating non-keyframe segments that might cause decoding issues. ::: ::::WorkflowBlockItem If the input stream includes multiple audio channels, select the **Support MultiAudio** option to enable multiple separate audio channels. :::hint{type="warning"} Note: this option **must** be selected for channels that will be sent to **TAMS**. ::: :::: :::WorkflowBlockItem Select **Ascending Playlist Order** to order the master playlist in ascending order by bitrate. ::: :::WorkflowBlockItem In the **Encoder** field, if you would like to specify a specific encoder to use for transcoding (decode and reencode processes), select the desired option from the drop down menu. By default, if there is an Nvidia GPU available, it would auto detect and use that, however you can override this behavior by selecting a different option from the list. ![Encoder Options](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/b77Z4neULK5pXHp9QPlwx-20260401-221155.png) ::: :::WorkflowBlockItem Click **Save**. ::: ::::: ## Transcoded Channel Configuration Parameters Table | **Parameter** | **Description** | | ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the Transcoded Channel 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 Channel 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 Channel. 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. | | ***Configuration*** | | | Processing Cluster | Select from the drop-down list one of the Channel Processing clusters that has been configured in ZEN Master. The selected cluster will be used to process this Channel.
Note: For heavy transcoding processes, use a Processing Cluster with a GPU. ZEN Master supports use of AWS, GCP and Azure instances that include Nvidia GPU.
Note: If the Source does not exist in the cluster, then the cluster will pull the Source automatically.
Note: If you are assigning the Transcoded Channel to a specific broadcaster, make sure that the broadcaster has sufficient available resources (CPU, GPU etc.) to handle the additional load. | | Target Broadcaster/s | Select your broadcaster preference. 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. | | Source | Select from the drop-down list the desired Source. | | Alternative Channel (Disaster Recovery) | Enables reverting an entire path after the Source (i.e., Channel/Broadcaster to the Target) to go through an alternative path, which is usually hosted on an alternative cloud/region. The redirection to the alternative path is manual. So, in case of a fault, if there is no time to troubleshoot a problem, this mechanism allows the user to select the feed that has an issue, click a button and revert the stream to go through a pre-configured alternative path.
For example, if you have a Channel and a Broadcaster on GCP and a secondary Channel and Broadcaster on Azure. If something goes wrong with the GCP path, you can click the Go to Alternative button and failover everything to Azure. | | TAMS Enabled | Enables sending the channel to TAMS target repository. Requires that **Support MultiAudio **also be checked. | | Include Source | If you would like to pass the original Source through, select this checkbox and enter the desired Bitrate for the Source. | | Slate Source | Select a source (typically a File source), which will be streamed as a technical fallback slate. This option is available when transcoding to a multi-bitrate ladder and not passing through the original source. | | Log HLS Ad Markers | If you would like to log the HLS Ad Markers for this Channel, select this checkbox. | | Preserve closed captions | If you would like to preserve closed captions for this Channel, verify that this checkbox is selected (default). | | Crop | If you would like to crop the input stream, select this checkbox, select the type of units used to define the crop (options are: Pixels or Percentages), and specify the crop position for each of the parameters (*Left, Top, Width *and *Height*) in the appropriate fields. | | Renditions | In the **Renditions** section add one or more Transcoding Profiles to the Channel and configure the bitrate for each profile. | | Transcoding Profiles | Add one or more Transcoding Profiles to the Channel by clicking the button next to the profile, and configure the expected bitrate for each profile. The default bitrate is the estimated bitrate based on the transcoding profile.
Note: The value should be the sum of the video and audio bitrates plus a small amount to account for streaming overhead. By default, a value is assigned based on the transcoding profile. For Sources in which either the video, audio or both are not transcoded, the user must manually input the value based on the actual bitrates of the Source. It is important to enter an accurate value since it will be included in the HLS/DASH manifest.
To assign the transcoding process to a multi GPU Broadcaster, select the **Multi GPU** checkbox, and then select from the drop-down list the desired GPU instance. Options are: *0* (default), *1*, *2* and *3*.
Note: This feature is useful if you are running several heavy transcoding activities, as it enables you to distribute the load among several different GPUs.
Note: If you would like to remove a Transcoding Profile from the Channel, click on the button next to the Source. | | Multi GPU | If you would like to assign the transcoding process to a multi GPU Broadcaster, select the **Multi GPU** checkbox. This feature is useful if you are running several heavy transcoding activities, as it enables you to distribute the load among several different GPUs. | | Ignore Transcode Thresholds | Select this checkbox if you would like to override the Transcode thresholds for you Ingest Cluster (i.e. to allow use of full CPU/GPU and memory capacity). | | ***Initial State*** | | | Disabled | Select this checkbox if you would like to disable this Channel upon initial configuration. | | Muted | Select this checkbox if you would like to disable error/recovery notifications for this Channel upon initial configuration. | | ***Advanced*** | | | Billing Code | If you would like to track usage for this Channel, enter your Billing Code details, see [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ) . | | 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. | | HLS | Specify the values for **Segments** and **Segment Duration**. If you would like to disable HLS, deselect the checkbox. | | CMAF (DASH + fMP4 HLS) | If you would like to enable CMAF (DASH + fMP4 HLS), select this checkbox and specify the values for **Segments** and **Segment Duration**. | | Convert CEA- 08 to WebVTT | If you would like to convert the captions format from CEA-708 to WebVTT, then select this checkbox. | | Custom WebVTT Positioning | Check to change the position of captions in the video frame.
**Note that positioning captions requires Broadcaster v18.8 or later.** | | Vertical Position (%) | - **Definition:** Specifies the **vertical position** of the cue box. - **Range:** 0–100 (as a percentage of the video height) - **Meaning:** - 0% positions the cue at the **top** of the video frame. - 100% positions the cue at the **bottom** of the frame. - If omitted, the cue defaults to near the bottom (depending on browser defaults). | | Horizontal Position (%) | * **Definition:** Specifies the **horizontal position** of the cue box’s **anchor point**. * **Range:** 0–100 (as a percentage of the video width) * **Meaning:** - 0% aligns the cue box with the **left edge** of the video. - 100% aligns it with the **right edge**. - Intermediate values shift the cue horizontally across the video. | | Text Alignment | - **Definition:** Defines the **text alignment** or **anchor point** within the cue box. - **Accepted values:** - **Left** – The cue box’s left edge is anchored to the specified position. - **Middle** – The cue box’s center is anchored to the specified position. - **Right** – The cue box’s right edge is anchored to the specified position. - **Meaning:** Controls how the text block aligns relative to the position value. | | Timecode (EXT-X-PROGRAM-DATE-TIME) Source | Select your preference for inserting a timecode. Options are: None, System time (default) or SEI Timecode. | | Disable Renditions Synchronization | Select this checkbox if you would like to disable synchronization between the Sources. (Supported for Broadcasters v14.8+) | | Drop Unaligned Segments | Select this checkbox if you want to drop segments of a multi-bitrate adaptive group that are not aligned. These segments will not be included in the playlist. | | Force I-Frames on SCTE-35 markers | Selecting this option will do the following:
- If a SCTE35 marker is detected and it contains a specific video timestamp (PTS), the encoder will generate an IDR-frame on the video frame with the closest or equal timestamp. - If there is no timestamp in the SCTE35 marker, the transcoder will generate an IDR frame as soon as it can. | | Segment on SCTE-35 | If enabled, SCTE-35 markers found in the source input will be used to segment the stream and the #EXT-X-CUE-IN/#EXT-X-CUE-OUT tags will be added to the manifest. | | Don't add EXT-X-CUE-IN | Select this option to remove the** EXT-X-CUE-IN** tag, which indicates where to return back to the program, from the playlist. | | SCTE-35 tag | Select the ad marker tag that will be used to segment the stream:
- EXT-X-CUE – cue-in and cue-out ad markers. - EXT-X-DATERANGE - With EXT-X-DATERANGE ad marker tags, you use SCTE35-OUT attributes to specify the timing of the ad avail. - EXT-X-CUE and EXT-X-DATERANGE – Zixi will use both ad marker tags to segment. - EXT-X-CUE & EXT-OATCLS-SCTE35 - the EXT-OATCLS-SCTE35 marker tag includes the Base-64 encoded SCTE payload. Zixi will use both ad marker tags to segment.
| | Segments between EXT-X-PROGRAM-DATE-TIME tags | Configure the the frequency in which the EXT-X-PROGRAM-DATE-TIME tags will appear in the manifest by specifying the number of segments between each EXT-X-PROGRAM-DATE-TIME tag. | | Drop first segment | Enabling this option will drop the first segment in the manifest. For HLS workflows, this can help ensure smoother playback by eliminating non-keyframe segments that might cause decoding issues. | | Support MultiAudio | If the input stream includes multiple audio channels, select this option to enable multiple separate audio channels. This option **must** be checked if the channel is **TAMS enabled**. | | Ascending Playlist Order | Select this option to order the master playlist in ascending order by bitrate. | | Encoder | If you would like to specify a specific encoder to use for transcoding (decode and reencode processes), select the desired option from the drop down menu. By default, if there is an Nvidia GPU available, it would auto detect and use that, however you can override this behavior by selecting a different option from the list. | [title] Source History Content Analysis [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/Source History/ This graph shows the number of Content Analysis errors of each type (e.g. CC Errors, Blank Picture etc.) that occurred over time**. **Errors are shown separately for each PID. The graph also displays the following quality scores: **ePSNR** - For Broadcaster (v13 and up) streams, the estimated Peak Signal-to-Noise Ratio (ePSNR) is shown for each relevant PID. The scale for the ePSNR is shown along the right side of the graph. ePSNR values can range from 11 to 60, with 60 representing the highest quality. :::hint{type="info"} - Additional ePSNR data is shown in the [Source History Encoding Quality ePSNR](docId\:USjyWgfUK7rbD0hVqd0ZA) section. - ePSNR analysis is supported for MPEG2 or H.264 content, but not for most types of HEVC/H.265 content. Also, Sources must be 8-bit (not HDR) and Progressive (not Interlaced). ::: **eVMAF** - the estimated Video Multimethod Assessment Fusion is shown for each relevant PID. This quality score uses machine learning to predict how humans perceive video quality. The score can range from 0 to 100 , where a higher score represents better quality. In both the PSNR and VMAF cases, Zixi trained Machine Learning models to estimate the score without needing to do the full calculation because in both cases the original, uncompressed reference is needed for the full calculation. The ML model is also computationally more efficient (less CPU) than the full calculations. The Y-axis represent the following: - Left axis - the number of CC Errors or TR101 misses. - Right axis - the quality score (ePSNR/eVMAF) ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-w5iiDcWxKJwhlZq8VGZZI-20250407-163328.png) ZEN Master shows data for the following Content Analysis parameters: - **CC (Continuity Count) Errors** – incorrect packet order, a packet occurs more than twice, lost packet - **Blank Picture** - blank frames of any color for a duration of \~60s or longer - **Frozen Video** – no motion detected for a duration of \~60s or longer - **Audio Clipping** - clipped audio on AAC or MPEG audio - **Silent Audio** – silent audio (dBFS \< -90) on AAC or MPEG audio with a duration of \~30s or longer - **CQA Misses** - shows the number of frames for which CQA (Content Quality Analytics) was skipped (i.e. to conserve resources). - **TR101 Misses** - shows the number of frames for which TR101 was skipped (i.e. to conserve resources). - **ePSNR **- weighted average of estimated Peak Signal-to-Noise Ratio (PSNR). - **eVMAF **- estimated Video Multimethod Assessment Fusion score. - [title] Source Stream [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/ ![View Source Stream](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/9qLZriwYr11--kFmgt5Do-20260216-192510.png) ## Preview Pane The **Preview Pane** includes a thumbnail tile, showing the current content of the source. The tile displays an overlay of the timestamp and includes the following controls: - **Show Overlay** - Shows/hides the overlay time stamp. - **Play Inline** - Mouseover the thumbnail to reveal the **Play Inline **button: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/mGNzk5udEaXproM9MBw6P-20260216-191857.png" size="24" width="710" height="642" position="center" darkWidth="710" darkHeight="642" showCaption="false" indent="2"} :::hint{type="info"} Note: the **Play Inline** feature iis not available for all accounts - if it is not available on yours and you would like to have it enabled, contact your Zixi Account Manager. ::: The video will start playback in the HTML5 player built into ZEN Master. Mouseover the video to reveal the **Stop** button: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Ww13BP8PwC469_-jThNzE-20260216-192057.png" size="24" width="908" height="694" position="center" alt="Stop Inline Playback" darkWidth="908" darkHeight="694" showCaption="false"} :::hint{type="info"} Note that the HTML5 player does not support all video codecs. If Inline Playback shows a blank screen, use the VLC option instead ::: - **Play VLC** - Click to play preview using VLC. For more details, see [Viewing Preview in VLC](docId\:RmCwt-Gw-6f2PrOG2l0ay) . ### Notes on Inline Playback - The **Play Inline** feature is not available for all accounts - if it is not available on yours and you would like to have it enabled, contact your Zixi Account Manager. - Codec support is limited to what the browser can decode; not all codecs work. - Bitrate is capped at 8 MBPS. - There is a 2 GB cap on each stream (\~30 min at 8 MBPS). - When the data cap is hit, the stream is throttled to a very low bitrate, effectively stalling playback (there is no real failover/drop, just unusable throughput). - Firewalls must be opened to allow Zen Master to pull video from broadcasters, port 7777 TCP open to ZM backend outgoing IPs. - Because traffic is proxied through the ZEN Master backend, there is an egress cost. ## Stream Information Shows a stream information tree that displays cumulative statistics regarding the stream. You can reset the stream information by clicking on the *Reset* button at the bottom of the page. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-9tA0PIhhB1czkEW0rDErf-20250429-143802.png" size="36" width="262" height="139" position="center" darkWidth="262" darkHeight="139" showCaption="false"} - **Start Expanded** - select to display the stream information tree in an expanded mode by default. [title] Adding a Source - HLS [path] ZEN Master/ZEN Master User Guide/Sources/Adding ZEN Master Sources/ ZEN Master can receive a Source directly from an HLS input. :::hint{type="info"} This method only supports single bitrate media playlists. If a multi bitrate playlist was entered, ZEN Master will load the component playlist out of it and you will need to select one of the renditions. If you want the full master playlist to be in ZEN Master, you can repeat the following procedure for each of the renditions. ::: The following procedure describes how to add an HLS Source in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. ## To add an HLS Source: :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Source selection** window is displayed. ![Create Source Options](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-3mXDQJHXUppSRZJSBYBnR-20250805-132303.png) ::: :::WorkflowBlockItem Click on **HLS**. The **Create New HLS Source** window opens. ![Create HLS Source](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/JwAOGdJaC3dEVrsI-OzJk-20260327-213432.png) ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, enter a unique name to identify this Source in the system. ::: :::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 **HLS Configuration **section, in the **URL** field, enter an HLS master or media playlist URL (e.g. [https://example.com/index.m3u8](https://example.com/index.m3u8)). ::: :::WorkflowBlockItem Click on the **Load media playlists** button to verify the URL. ::: :::WorkflowBlockItem In the **HLS media stream URL** field, select the relevant media stream from the drop-down list. ::: :::WorkflowBlockItem In the **Buffer Size \[ms]** field, select the buffer size. (Default: 30,000) ::: :::WorkflowBlockItem If you would like to convert EXT-X-CUE-OUT/EXT-X-CUE-IN ad markers to SCTE-35, select the **Convert EXT-X-CUE-OUT/EXT-X-CUE-IN ad markers to SCTE-35** checkbox. ::: :::WorkflowBlockItem Check **Remux HLS to MPEG-TS **to convert the HLS to an MPEG-TS stream ::: :::WorkflowBlockItem Set the **Target Bitrate** to the desired bitrate if you are converting the HLS to MPEG-TS. ::: :::WorkflowBlockItem In the **Source Configuration** section, 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 preference. 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 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 [Adding PID Mapping Profiles](docId\:gFTCaYurPL7DInoUyd14z). ::: :::: :::WorkflowBlockItem Select the **Alert on PID changes** checkbox if you would like to generate email notifications whenever a PID change is detected. ::: ::::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. ::: ::::WorkflowBlockItem :::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 closed captions, select **Monitor CEA-608 **checkbox**.** :::hint{type="info"} Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: f you would like to monitor CEA-708 closed captions, select **Monitor CEA-708 **checkbox**.** :::hint{type="info"} Monitoring CEA-708 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: :::: :::WorkflowBlockItem If you would like to disable auto-pull, select the **Disable Auto-Pull** checkbox. ::: ::::WorkflowBlockItem :::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. (Default: 1000 ms) ::: ::::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 Additional SCTE-35 options are available when you expand the **SCTE-35 Manipulation** section: ![SCTE-35 Manipulation](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/FxvVWM-bhpg9ZdVYW_LCl-20251104-153319.png) Here you can: - Enable SCTE-35 Manipulation - Specify the length of a search window for a NULL packet for SCTE-35 intertion - Set the SCTE-35 PID - Remove any existing SCTE-35 messages from the stream See the **Parameters Table** below for an explanation of these options. ::: :::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 Under **Error Concealment,** click the Enable Error Concealment checkbox to enable the following error concealment mechanisms that can correct transaport stream for downstream IRDs: :::Paragraph{indent="1"} 1\. **Continuous Timeline** - corrects errors that are related to timeline jumps in the source. This mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input. ::: :::Paragraph{indent="1"} 2\. **Replace Frames** - If there are frames with CC errors, it replaces them with skip frames (inserts the last good frame received in place of missing ones). This solves issues such as an IRD that lost synchronization when it received broken frames. This mechanism also creates a variant of the input (doubling the input). ::: :::Paragraph{indent="1"} 3\. **Renumber CC **- The Continuity Counter is part of the TS encapsulation. When there are CC errors in TR101 analysis it means that the counter has a gap due to the lost frames. This mechanism can re-write the CC counter for the downstream devices, so they will see a continuous increase of the counter. ::: :::Paragraph{indent="1"} 4\. **Delay (ms) **- Enter the delay that the Error Concealment adds to the stream in miliseconds. Error Concealment needs to buffer the stream to analyze it. One second is a reasonable value. Lower values may cause the Error Concealment to not be able to fix some of the frames. ::: :::Paragraph{indent="1"} 5\. **CBR Padding** - enter a value for the rate at which padding will be added to maintain a specific output transport bitrate. For example, if you have a video bitrate at 5000 kbps or that varies from 3000-5000 kbps and audio at 64 kbps, total bitrate will be max 5064 kbps or min 3064 kbps. With CBR padding set at 6000 kbps, 6000 kbps is being delivered downstream at all times, ensuring a consistent bitrate. ::: :::Paragraph{indent="1"} 6.** PCR Interval** - Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. This depends on standard used by downstream encoders or decoders. Options include: ::: :::Paragraph{listStyleType="disc" indent="2"} ATSC standard - 100 ms ::: :::Paragraph{listStyleType="disc" indent="2"} DVB standard - 40 ms ::: 7. **Remux Buffer Size** - Specify the time added for remuxing the stream (default: 2500 ms). 8. **Smoothing** - Time added for smoothing a bursty stream - adds to latency, but produces a smoother output. See [Improving Stream Resiliency: Error Correction and Concealment](docId:9_OLo1Argk_2aDoSHYFBb) for more information. ![Error Concealment Options](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/jEyT42FS_YflpTNxqCc9Q_zm-error-concealment-options.png) :::: :::WorkflowBlockItem If you would like to adjust the advanced settings, click **Advanced**. The **Advanced** settings fields are displayed: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/htLaHnFpOnlrKedQ0NAR0_hls-source-advanced.png) ::: :::WorkflowBlockItem If you would like to track usage for this Source, enter your **Billing Code** details. See [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ). ::: :::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 Click **Save**. ::: ::::: ### HLS Source Configuration Parameters Table | Parameter | Description | | -------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the HLS 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. | | ***HLS Configuration*** | | | URL | Enter an HLS master or media playlist URL (e.g. https\://example.com/index.m3u8). | | Load media playlists | Click on this button to verify the URL. | | HLS media stream URL | Select the relevant media stream from the drop-down list. | | Buffer Size \[ms] | Select the Buffer size. (Default: 30,000) | | Convert EXT-X-CUE-OUT/EXT-X-CUE-IN ad markers to SCTE-35 | Select this checkbox if you would like to convert EXT-X-CUE-OUT/EXT-X-CUE-IN ad markers to SCTE-35. | | Remux HLS to MPEG-TS | Convert the HLS stream to MPEG-TS | | Target Bitrate | If you are converting the HLS to MPEG-TS, set the target bitrate | | ***Source Configuration*** | | | Ingest Cluster | Select from the drop-down list one of the available Ingest Clusters as the destination for the Source. | | Target Broadcaster/s | 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.*
**Note**: For managed clusters, it is not recommended to select a specific Broadcaster, as the Broadcaster’s availability may not remain stable. | | PID Mapping Profile
(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. | | 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 | Disables the Source thumbnail from appearing in the Sources list and other places. Disabling thumbnail may improve system performance. | | Monitor CEA-608 Closed Captions | If you would like to monitor CEA-608 closed captions, select this checkbox.
**Note:** Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. | | Monitor CEA-708 Closed Captions | If you would like to monitor CEA-708 closed captions, select this checkbox.
**Note:** Monitoring 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 desired latency for auto-pull actions. (Default: 1,000 ms) | | 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. | | ***SCTE-35 Manipulation*** | | | Enable SCTE-35 Manipulation | Select checkbox to enable SCTE-35 Manipulation. | | SCTE-35 PID | Set the SCTE-35 PID in which the messages will be inserted. | | Remove Existing SCTE-35 | Remove any existing SCTE-35 messages from the stream. | | NULL Packet Search Window (ms) | Look for a NULL packet 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 | | ***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/recovery notifications for this Source upon initial configuration. | | ***Error Concealment*** | | | Enable Error Concealment | Select this checkbox to enable the error concealment mechanisms listed below to correct transport stream for downstream IRDs. | | Continuous Timeline | Corrects errors that are related to timeline jumps in the source. This mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input. | | Replace Frames | If there are frames with CC errors, it replaces them with skip frames (inserts the last good frame received in place of missing ones). This solves issues such as an IRD that lost synchronization when it received broken frames. This mechanism also creates a variant of the input (doubling the input). | | Renumber CC | encapsulation. When there are CC errors in TR101 analysis it means that the counter has a gap due to the lost frames. This mechanism can re-write the CC counter for the downstream devices, so they will see a continuous increase of the counter. | | Delay (ms) | Enter the delay that the Error Concealment adds to the stream in miliseconds. Error Concealment needs to buffer the stream to analyze it. One second is a reasonable value. Lower values may cause the Error Concealment to not be able to fix some of the frames. | | CBR Padding (kbps) | Enter a value for the rate at which padding will be added to maintain a specific output transport bitrate. For example, if you have a video bitrate at 5000 kbps or that varies from 3000-5000 kbps and audio at 64 kbps, total bitrate will be max 5064 kbps or min 3064 kbps. With CBR padding set at 6000 kbps, 6000 kbps is being delivered downstream at all times, ensuring a consistent bitrate. | | PCR Interval (ms) | Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. Options include:
* ATSC standard - 100 ms * DVB standard - 40 ms | | ***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+) | | 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 | Specify the maximum transmission unit (largest data packet that a network-connected device will accept) in bytes for the Auto Pull. | | Auto-Pull Billing Password | Enter the password that corresponds to this auto-pull billing code. | | 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. | | 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 for empty audio streams to prevent false warnings - enter a comma-delimited list of PID numbers that should not be monitored for null content. | [title] Adding a Zixi Source – AWS MediaConnect [path] ZEN Master/ZEN Master User Guide/Sources/Adding ZEN Master Sources/ You can configure an input from an AWS MediaConnect service to be used as a Source in ZEN Master. This is done by selecting **Zixi** in the New Source Menu. In this case, the Zixi-enabled device is referred to as the **Origin AWS MediaConnect** which streams to the **Ingest Broadcaster** using either Zixi Push or Zixi Pull. ![AWS MediaConnect Source Diagram](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/mXeyHTckIw2zKhC1sItyg_image.png) The following procedure describes how to add a Zixi Source from AWS MediaConnect in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. **To add a Zixi source from an AWS MediaConnect service:** :::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). ::: :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Source selection** window is displayed. ![Create Source Options](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-3mXDQJHXUppSRZJSBYBnR-20250805-132303.png) ::: :::WorkflowBlockItem Click on **Zixi**. The **Create New Zixi Source** window opens. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-KZ3pu-UfCy_7xvKMyoj4a-20250608-100617.png) ::: :::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 Under the **Input** section, under **Mode**, select **Push** to push the stream from the Origin AWS MediaConnect to the Ingest Broadcaster; Or Pull to have the Ingest Broadcaster pull the stream from the Origin AWS MediaConnect. ::: :::WorkflowBlockItem In the **Application** section, select the **AWS MediaConnect**. ::: :::WorkflowBlockItem In the **AWS Account** field, select from the drop-down list the AWS Account on which the source is coming from. ::: :::WorkflowBlockItem In the **Region** field, select from the drop-down list the AWS region in which the flow is configured. ::: :::WorkflowBlockItem In the **AWS MediaConnect Flow** field, select from the drop-down list the Flow that you would like to use as the Source. ::: :::WorkflowBlockItem In the **Configuration** section, 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, 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*. :::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 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 [Adding PID Mapping Profiles](docId\:gFTCaYurPL7DInoUyd14z) . ::: :::: :::WorkflowBlockItem If you would like to generate email notifications whenever a PID change is detected, select the **Alert on PID changes **checkbox. ::: ::::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/CEA-708 closed captions, select **Monitor CEA-608/CEA-708 **checkbox**.** :::hint{type="info"} Monitoring CEA-608/CEA-708 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: :::: ::::WorkflowBlockItem If you would like to disable auto-pull, select the **Disable Auto-Pull** 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 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: ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-Lllja-kkjvTmCQcg07UBO-20250820-130629.png) ::: :::WorkflowBlockItem If you would like to track usage for this Source, enter your **Billing Code** details. See [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ). ::: :::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**. ::: ::::: | **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 **AWS MediaConnect **radio button. | | AWS Account
| Select from the drop-down list the AWS Account for the** Origin AWS MediaConnect** (where the Source will originate). | | Region | Select from the drop-down list the AWS region of the Origin AWS MediaConnect on which the origin media connect flow is configured. | | AWS MediaConnect Flow
| Select from the drop-down list the Origin MediaConnect Flow that you would like to use as the Source. | | ***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. | | Latency \[ms] | Select the latency time for the stream (default 4000). | | 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 | If enabled, Zixi adjusts the latency dynamically to optimize it for network conditions. | | 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. | | 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+) | | 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. | | 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. | | 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. | [title] Adding a Source – Monitor Only [path] ZEN Master/ZEN Master User Guide/Sources/Adding ZEN Master Sources/ You can designate an input that already exists in a Broadcaster cluster to be added as a Source in ZEN Master for monitoring purposes only. This is done by selecting **Monitor Only** in the **New Source** menu. In this case, the Input already exists in the Brodcaster within the **Ingest Cluster**. The **Origin Device** is unknown and not managed or monitored by ZEN Master. The stream can be Pushed to or Pulled by the Ingest Cluster, as manually configured in the Input configuration of the Broadcaster. The steam can use any protocol that is supported by Broadcaster, including protocols that are not supported in ZEN Master (e.g., RTSP). :::hint{type="info"} This behavior is uncommon to other Sources because in this case the input on the Broadcaster must already exist, while in other cases, for example, after configuring the Source in ZEN Master, ZEN Master will create the input on the Broadcaster. ::: ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-mrjzZkPuEXFAGpOlbRZ3Z-20250226-125115.png) - **Multiple inputs** - You can select several inputs from a single Broadcaster to simultaneously create a new Source in ZEN Master for each input. The following procedure describes how to add a Monitor Only Source in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. **To add a Monitor Only Source:** :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Source selection** window is displayed. ![Create Source Options](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-3mXDQJHXUppSRZJSBYBnR-20250805-132303.png) ::: :::WorkflowBlockItem Click on **Monitor Only**. The **Create Monitor Only Source** window opens. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-6f679W15LPAIFUjONiebo-20250226-131735.png) ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, leave blank. The name of the Source will be the same name as the Broadcaster Input. ::: :::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 **Input** section, in the **Broadcaster** field, select from the drop-down list the Broadcaster on which you have created the Input(s) that will be monitored by ZEN Master. A list of available Inputs on that Broadcaster is displayed. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX--JcurdkuDRoms6qJHxPFH-20250226-132520.png) ::: ::::WorkflowBlockItem Select one or more Inputs by clicking the **+** button for the desired Input. :::hint{type="info"} Each input that is selected creates a **separate** Source in ZEN Master ::: Selected Inputs are shown above the **Filter** box. (You can remove an Input by clicking the **-** button for that Input). ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-PD-MRDq5PACrp9-AR_z5b-20250226-132713.png) :::: :::WorkflowBlockItem In the **Configuration** section, select the **Alert on PID changes** checkbox if you would like to generate email notifications whenever a PID change is detected. ::: ::::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](http://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 disable the Source thumbnail from appearing in the Sources list and other places, select the **Hide Thumbnail** option. Disabling thumbnail may improve system performance. ::: ::::WorkflowBlockItem If you would like to monitor CEA-608 closed captions, select **Monitor CEA-608 **checkbox**.** :::hint{type="info"} Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: If you would like to monitor CEA-708 closed captions, select **Monitor CEA-708 **checkbox**.** :::hint{type="info"} Monitoring CEA-708 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: :::: ::::WorkflowBlockItem If you would like to disable auto-pull, select the **Disable Auto-Pull** 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 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: ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-vL66gI1BXQ0U26Riw7NWN-20250226-160943.png) ::: :::WorkflowBlockItem If you would like to track usage for this Source, enter your **Billing Code** details. See [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ). ::: :::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 Click **Save**. ::: ::::: | **Parameter** | **Description** | | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | ***Info*** | | | Name | Leave this field blank. The name of the Source will be the same name as the Broadcaster Input. | | 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*** | | | Broadcaster | Select from the drop-down list the Broadcaster on which you have created the Input(s) that will be monitored by ZEN Master. | | Broadcaster Inputs | 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.
Each input that is selected creates a separate Source in ZEN Master. | | ***Configuration*** | | | Alert on PID changes | If you would like to generate email notifications whenever a PID change is detected, select this checkbox. | | 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](http://www.etsi.org/deliver/etsi_tr/101200_101299/101290/01.03.01_60/tr_101290v010301p.pdf). * **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 | Disables the Source thumbnail from appearing in the Sources list and other places. Disabling thumbnail may improve system performance. | | Monitor CEA-608 Closed Captions | If you would like to monitor CEA-608 closed captions, select this checkbox.
Note: Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. | | Monitor CEA-708 Closed Captions | If you would like to monitor CEA-708 closed captions, select this checkbox.
Note: Monitoring 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) | | 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*** | | | 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. | | 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. | | 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. | [title] Source History SCTE-35 [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/Source History/ This graph shows the distribution of SCTE-35 messages of various types over time. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-CFUXLCboQosSrX0EcnIGX-20250409-095042.png) The left y-axis measures the number of SCTE-35 messages sent. The legend at the bottom indicates the type of SCTE-35 messages that are included in the graph. [title] Source History Network [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/Source History/ ­This graph shows network activity over time. This includes the percentage of lost packets and not recovered packets as well as values for RTT and Jitter. ![Network History](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Lq5mMF_5lbeF24ZNd1TpO_image.png) The left y-axis measures the percentage of percentage of lost packets and not recovered packets. The right y-axis measures the min and max Jitter and RTT in milliseconds. [title] Source History Transcoding [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/Source History/ The graph shows key transcoding performance metrics and error-related events, such as overflows, frame drops, and resets. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-tOrAXP0vh-q5e9pRuqU_K-20250416-114125.png) **Y-axis (Left): **Tracks **error-related events **such as frame drops, overflows, and resets. **Y-axis (Right): **Displays the number of frames processed per second as a green line, indicating the transcoded output video. [title] Source History Network Bitrate [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/Source History/ This graph shows the total bitrate of the stream over time. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-UuEjpLd2Jk4wVAXTZ4pyE-20250409-134713.png) The y-axis measures the bitrate level of the stream in Kb/s. :::hint{type="info"} The network bitrate can be lower than the sum of elemental stream bitrates because if it's a zixi stream, the network data is compressed, whereas, the elementary stream bitrate shows the uncompressed values. ::: [title] Source History Elementary Stream Bitrates [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/Source History/ This graph shows the bitrates for each individual PID over time. ![History of bitrates for individual PIDs](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/X8udguq073KFl1rprmc0F_image.png) :::hint{type="info"} The network bitrate can be lower than the sum of elemental stream bitrates because if it's a zixi stream, the network data is compressed, whereas, the elementary stream bitrate shows the uncompressed values. ::: The y-axis measures the bitrate level of the stream in Kb/s. [title] Source History Failover [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/Source History/ For Failover Sources, this graph shows how the failover Sources have been used throughout time. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-rbPP-skV-uz1A756S7jXa-20250409-110241.png) The legend indicates the sources that are displayed in the graph. The y-axis measures the stream rate for each source. [title] Source History Packet Timing [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/Source History/ For Push and Pull Sources from a Broadcaster (v13 and above), this graph shows a candlestick graph of distribution of packet arrival times over time. It's a key indicator of **network jitter and timing consistency** in video transmission. Each orange vertical box plot represents the variation in packet timing over a specific time interval. :::hint{type="info"} Dynamic use of FEC in the Zixi protocol can compensate for minor fluctuations in packet recovery times. ::: ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-PMnj79ZjIQmtWWctgv6Wv-20250416-125514.png) The candlestick graph shows the min and max in the narrow line and 25th percentile and 75th percentile in the thick line. This information can be helpful in choosing the latency setting for the stream, since there is no need to allow longer latency than the time that is actually being used for packet recovery. **Y-axis (Time in milliseconds):** Indicates the packet timing spread — higher values may suggest irregularities or jitter. **Box plot elements:** - **Top whisker:** Maximum packet delay observed - **Top of box:** 75th percentile - **Bottom of box = Min = 25th percentile:** In this case, many intervals show tight lower bounds. [title] Source History Encoding Quality eVAMF [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/Source History/ This graph illustrates the **estimated VMAF (Video Multimethod Assessment Fusion) ** scores over time, providing a detailed measure of perceived video quality that correlates well with human visual perception. Each orange box plot represents the distribution of eVMAF values during the corresponding time window. **Y-axis (eVMAF Score): **Represents the estimated VMAF value, ranging up to 100 — higher scores indicate better perceptual video quality. **Box plot components:** - Top whisker: Maximum score - Top of box: 75th percentile - Bottom of box: 25th percentile - Bottom whisker: Minimum score ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-agtZdmFr6l5HlIKPYGyR3-20250414-142938.png) [title] Source History Bonding (for Network Bonding Sources) [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/Source History/ For *Bonded streams*, this graph shows graphs for packet recovery and link performance. The Links graph shows separate performance info (Jitter, RTT and bitrate) over time for each NIC that is being used. :::hint{type="info"} ZEN Master shows data for bonded streams that are configured in ZEN Master as well as for bonded streams that are configured directly on the Feeder. ::: ![Source History Bonding](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/uyLM89QEGMaKqXCCfwjYs_image.png) [title] Source Events [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/ The Events section shows all the events that have been generated by the system that relate to the selected Source (e.g. connections, errors, and disconnections). To learn about the data that is displayed in the Events tab see [Events](https://zixidocumentation.atlassian.net/wiki/spaces/ZMUG/pages/483688494/Events). Click **Quick Report** to generate a report of events related to this Source and download the .xls file. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-6R38D1bauRZwrn-0SFuXX-20250721-155125.png) [title] Source Notes [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/ This tab shows free-form notes with information about the Source. To add a note, type it into the Add new note field. ![Notes Tab](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/nAja5dt-7NZ6ZgAD_sff4_image.png) [title] Source Change Tracking [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/ Change Tracking displays the history of changes that were made to the Source’s configuration. For more information, see [Change Tracking](docId\:hc-KMARjxkvIaZ69v6IVv). [title] Source Traceroute [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/ For streams sent from a Zixi Feeder to a Zixi Broadcaster (v13 or above) or from a Broadcaster to a Receiver, this tab shows the traceroutes currently being used by the stream. :::hint{type="info"} You can view historical traceroutes data, including RTT for each traceroute, in the Traceroute graph under the History tab, see [Source History Traceroute](docId\:A3FAy5SZOHg7D_ApiMJLb). ::: [title] Source Incidents [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/ The Incident view groups together errors relating to the Source into incidents to simplify the process of identifying the common root cause. Incidents can be manually created or automatically generated. For more information, see [Incidents](docId\:KM0I5TNPzuO-ygFv6QcVq). [title] Actions on Broadcasters [path] ZEN Master/ZEN Master User Guide/Broadcasters/Viewing Existing Clusters/Viewing Existing Broadcasters/ The top of the Info pane includes buttons for taking the following actions on the selected Broadcaster: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/JVIc7OzF5abuB6k-p6PfU-20260213-190302.png" size="70" width="1400" height="552" position="center" alt="Broadcaster Action Menu" darkWidth="1400" darkHeight="552" showCaption="false"} - **Mute/Unmute** – disables/activates notification for error/recovery events. Set the date and time when the mute will automatically be cleared by clicking on the down arrow and selecting **mute until.** - **Disable – **disables the Broadcaster. When disabling a Broadcaster, you can migrate the existing sources and channels to a different Broadcaster by selecting the **Migrate sources and channels to different Broadcaster(s)** option and then selecting the Broadcaster(s) preference on which the streams will be hosted in the **Target Broadcaster/s** drop down menu. Options are: *Prefer Primary Broadcasters*, *Primary Broadcasters only*, *Backup Broadcasters only *or* Prefer Backup Broadcasters. *The selected target broadcaster option will override the original Target Broadcaster option of the Source/Channel, however if the source/channel is configured to a specific/named Broadcaster Target it will not participate in the migration process. Similarly, if the selected setting is *Backup Broadcasters only* and the Broadcaster that is being disabled is the only Backup Broadcaster in the cluster, the migration will not be possible. - **Edit** – enables you to edit the Broadcaster configuration. - **Refresh – **refreshes the screen. - **Open Broadcaster – **click to access the Broadcaster UI. - **Set Maintenance – **click to turn on Maintenance Mode, which prevents new streams from being assigned to this Broadcaster. - **Config - **click to view instructions on how to configure the Broadcaster to connect to ZEN Master. - [Install Version](docId\:B1y6nShFZcUwCd0_GSPG-) - click to upgrade/downgrade the Broadcaster's software version. To install the new version: - In the **New Broadcaster Version **field, select the new version to install. Private version are indicated with a lock icon. - In the **Architechture** field, make sure that the correct server architecture is selected. - Click **Install**. - See additional information in the [Installing a New Broadcaster Version Using ZEN Master](docId\:B1y6nShFZcUwCd0_GSPG-) section below - **Refresh Instance** - for Broadcasters running on AWS, this feature allows Users to ‘swap’ out the existing instance for a fresh instance, useful for OS patching, instance re-sizing, OS Updates, etc. The new instance will re-connect to ZEN Master in place of the existing instance. See the [Refresh Instance](docId\:B1y6nShFZcUwCd0_GSPG-) section below. - **Run SSM Command **- ZEN Master now provides the facility to run AWS SSM commands directly within the ZEN Master User Interface. While multifunctional, this feature is primarily provided in support of Infosec teams with system update and patching requirements. See the [Run SSM Commands](docId\:B1y6nShFZcUwCd0_GSPG-) section below for more details. - **Delete** – deletes the Broadcaster. When deleting a Broadcaster, you can migrate the existing streams to a different Broadcaster by selecting the **Migrate sources and channels to different Broadcaster(s)** option and then selecting the Broadcaster(s) preference on which the streams will be hosted in the **Target Broadcaster/s** drop down menu. Options are: *Prefer Primary Broadcasters*, *Primary Broadcasters only*, *Backup Broadcasters only *or* Prefer Backup Broadcasters. *The selected target broadcaster option will override the original Target Broadcaster option of the Source/Channel, however if the source/channel is configured to a specific/named Broadcaster Target it will not participate in the migration process. Similarly, if the selected setting is *Backup Broadcasters only* and the Broadcaster that is being deleted is the only Backup Broadcaster in the cluster, the migration will not be possible. - **Widgets/Tabs **view. ## Installing a New Broadcaster Version Using ZEN Master When you click **Install Version** in the action dropdown, the following screen opens: ![Install New Version UI](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/XO3Lf43JtSyLPiDLWnoHg-20251107-183312.png) Note that you are shown the current Broadcaster version, along with a dropdown menu of other available versions, with the latest on top. Also note the list of objects on the Broadcaster, which we will return to shortly. When choose a new version and click **Install, **in most cases ZEN Master will handle the new installation completely, and there will be no need for you to open the Broadcaster UI. :::hint{type="warning"} In some cases this will not succeed, because upgrading from some older versions (from 16.x to 18.x or 19.x, for example) requires some changes on the server or container that the Broadcaster runs on that ZEN Master cannot make. In these cases, you will see a red error message explaining the issue. ::: Note also that once installation starts, the **objects list** will change to display both **Initial Status** and **Status. **This will help you ensure that sources and targets restart properly after installation of the new version (or in some cases, that the new version fixes an issue with a source or target). ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Fm5Jxs9lOIzWc0gIcVXPn-20251107-184247.png) :::hint{type="info"} Note that object status does not update automatically as soon as the installation is complete, but rather updates every 30 seconds automatically. Also note the indication of the Broadcaster the object is operating on - if this Broadcaster is part of cluster with failover, a source might have been redirected to another Broadcaster during the update. ::: When the installation of a new Broadcaster version completes successfully, a green success message will appear. ::Image[]{src="https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/7_tC5glf0OfUjGTWVJAQl-20251107-191509.png" size="70" width="1024" height="120" position="center" alt="Success Message" darkWidth="1024" darkHeight="120" showCaption="false"} ## Refresh Instance When you select this option on the Broadcaster Action Menu, the following screen will open: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/0ppwwwHzlaoOg66m1E78A-20260213-201933.png" size="80" width="2176" height="1624" position="center" alt="Refresh Instance" showCaption="false"} You cannot modify the changes to be made to the Broadcaster and AMI versions, or the instance size. You can select sources and specify the actions to be taken on them. By modifying the **cluster settings** before running Instance Refresh, you can specify the Broadcaster and AMI versions you want for the cluster. While Refresh is running, ZEN Master will: - Update the active object status with the initial and current status of all objects. - Monitor the Broadcaster status. - Notify the User on completion success. Click **Refresh Instance** to begin the refresh, or **Close** to abort it. ## Run SSM Command :::hint{type="warning"} Note that to enable this feature, some setup is required on the AWS side (by an admin on your AWS account) to provide the set of scripts you want to enable ZEN Master to run, and you will also need to modify the AWS policy to allow ZEN Master to initiate the commands. See the section on **AWS Requirements** below. ::: When SSM is enabled for your account, selecting the **Run SSM Command** from the Broadcaster **Action Menu **opens this screen: ![Run SSM Command](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Hm6i8HtblhfwujAEF8Aa8-20260326-181220.png) In this view you will see: 1. Current Broadcaster details (not editable). 2. Optional **S3 Bucket** details if you want the output to go to S3. 3. A **dropdown list of SSM Commands** (e.g. ‘yum update’) available to ZEN Master. 4. The Broadcaster **Active Objects** table. 5. To execute the command, click the **Run SSM** Command action button. ![SSM Command Running](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/h5FEXlR0Yju40Ep9PNVeZ-20260214-151931.png) When you run a selected SSM command, ZEN Master will: 1. Update the active object status with the initial and current status of all objects. 2. Monitor the SSM status and displays the tail end of the command output in SSM. 3. Upon successful completion, notify you. If the script fails, you can use the error status and output notes to help further investigation: ![SSM Command Failure](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/LFSmU91QVP6PatQACizhR-20260215-223446.png) ### AWS Requirements Here is a list of actions that are needed on the AWS side, by an AWS administrator, to enable SSM commands in Zen Master: - Update the AWS IAM policy for ZEN Master - Create a role with AmazonSSMManagedInstanceCore policy - Apply that policy to your ZEN Master cluster - Create an SSM document with these settings, options, and parameters: - **Document type**: Command - **Platform types**: Linux - **Target type**: AWS\::EC2\::Instance - No parameters For more details, see [AWS SSM User Guide](docId\:SAhJY3H8uS6uNT2OkuNtR). ### Install SCTE-35 Modification Agent The SCTE-35 Modification Agent allows the Broadcaster to add, remove, and modify SCTE-35 markers in a transport stream - see [SCTE-35 Insertion](docId\:P41x2TyDYny_zgjl3-XXA) for more information. From the **Broadcaster Details screen** in ZEN Master, you can install the agent automatically rather than having to do it manually on the Broadcaster: ![Install SCTE-35 Agent from Broadcaster Details](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/FR2KBZe-jquDkybzXlwfv-20260330-185958.png) Click on **Install scte-35 modification agent **to show the confirmation dialog: ![confirmation dialog](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/5jtyAOfgBg86yF3MubczS-20260331-133032.png) Click the **Install scte-35 modification agent **button to start the installation. Note that the installation process happens asynchronously and takes some time, so you will not see any further indication in the **Details** tab. After a few minutes, go to the **Events** tab, and there you will see a message that the installation occurred if it succeeded: ![Installation Confirmed Event](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Rp4at9w56JOn7ZJ7Qecvf-20260331-133500.png) [title] Adding an RTP-protocol MediaConnect Source [path] ZEN Master/ZEN Master User Guide/Sources/Adding AWS Media Sources/Adding an AWS MediaConnect Source/ **To create a RTP MediaConnect Source:** ::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The Create New Source window is displayed. ![Create New Source window](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/AxSEVtTg03J7Up0wQFdjQ_image.png) ::: :::WorkflowBlockItem Under **AWS Media**, click on **AWS MediaConnect**. The Create New AWS Media Source window opens. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-_ty9SEjl4WcVpxQtdq9Yb-20250706-125902.png) ::: :::WorkflowBlockItem In the **Info **section, in the **Name** field, type a logical name for the 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. *Events Profiles* consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. ::: :::WorkflowBlockItem In the **Input** section, under **Protocol**, select the **RTP** radio button.  ::: :::WorkflowBlockItem In the **Ingest Port** field, enter the port that the Flow will listen on for incoming content. ::: :::WorkflowBlockItem In the **Max Bitrate** field, enter the maximum bitrate to be used on this NIC. ::: :::WorkflowBlockItem You are required by MediaConnect to enter a valid **Whitelist CIDR block**. The whitelist CIDR block is a range of IP addresses that should be allowed to contribute content to your source. These IP addresses must be in the form of a Classless Inter-Domain Routing block. For example, 10.0.0.0/16. Through source needs to be in the range covered by this CIDR block. Any IP address with this range is allowed to send content to this flow. ::: :::WorkflowBlockItem In the **Initial State** section, select the **Muted** checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. You can Unmute the Source at any time. ::: :::WorkflowBlockItem Click **Save**. ::: :::: **Parameters Table** | **Parameter** | **Description** | | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the AWS Media 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. | | ***Input*** | | | Protocol | To create a RTP protocol Input AWS Media Source, verify that RTP is selected. | | Ingest Port | Enter the port that the Flow will listen on for incoming content. | | Max Bitrate | Select from the drop-down list the maximum bitrate for this Source.
Make sure that the value is greater than the max bitrate for the input. The default is set automatically based on the current bitrate of the input. | | Whitelist CIDR Block | Specify the CIDR for the range of IPs that you would like to allow to contribute content to this Source.
You are required by MediaConnect to enter a valid Whitelist CIDR block. | | ***Initial State*** | | | Muted | Select this checkbox if you would like to disable error/recovery notifications for this Source upon initial configuration. | [title] Adding a Broadcaster to a Manual Cluster [path] ZEN Master/ZEN Master User Guide/Broadcasters/Creating a Broadcaster Cluster/Adding Broadcasters to a Cluster/ If when adding the Broadcaster Cluster, you selected the **Manual **option for the *Management Type*, you need to manually add Broadcasters to the cluster as follows. **To manually add a Broadcaster to a Cluster:** :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, select **Broadcasters**. ::: :::WorkflowBlockItem From the list of Broadcaster clusters, select the cluster to which you want to add a Broadcaster. The details of the cluster are displayed at the right of the screen: ![Broadcaster Cluster List](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/mueq8qICw6M9KjI7fSevS_image.png) ::: ::::WorkflowBlockItem In the Broadcasters section, click **+ Add Broadcaster.** :::hint{type="info"} In **tab** view, you need to first select the **Broadcasters tab** and then click on the** + Add Broadcaster** button. ::: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/4NhqfWPN84dNpU0jdwXb-_image.png) :::: :::WorkflowBlockItem The **Create New Broadcaster **window is displayed. ![Create New Broadcaster](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-2GDVhqobXvvn_uzJLLFZD-20250801-152825.png) ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, type a logical name for the Broadcaster. This name is internal, so you don’t necessarily need to use exactly the same name used to configure the Zixi Broadcaster. ::: :::WorkflowBlockItem The Broadcaster's location is used to represent it in the proper position in the Map display (see Maps). By default, the location is determined automatically based on the Broadcaster's IP. If you would like to manually set the location of the Broadcaster (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, in the **API User** field, enter "*admin*". ::: ::::WorkflowBlockItem In the **API Password** field, enter the *admin password* on the Broadcaster. :::hint{type="info"} These credentials allow ZEN Master to access the Broadcaster API, because the admin for the Broadcaster is automatically granted access. ::: :::: :::WorkflowBlockItem Select an **SSH Key **from the dropdown (if you haven't created or added an SSH key to ZEN Master you will need to stop here and do that before you can complete these steps - see [Configuring SSH Keys](docId\:qXuh0ckZbygbyCRZvjtwS)). ::: :::WorkflowBlockItem Select the Broadcaster **Type**. Options are: - **Primary** (default)– The Broadcaster functions as an active member of the cluster. - **Backup** – The Broadcaster does not receive Sources/Channels unless all Primary Broadcasters are unavailable (or it is manually configured to receive that Source). ::: :::WorkflowBlockItem If you would like to adjust the advanced settings, click on **Advanced**. The **Advanced settings** are displayed: ![Advanced Settings](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/1CQoS1GPvAlvOr3JmlZdq_image.png) ::: :::WorkflowBlockItem Under **Public IP**, specify the public IP of the Broadcaster by selecting one of the following: 1. **Auto Detect** (default) - select this checkbox if you want ZEN Master to detect the public IP automatically. 2. **Manual** - To manually specify the public IP, **deselect **the checkbox and enter the broadcaster’s *public* IP in the **IP** field. ::: ::::WorkflowBlockItem Under Private IP, specify the public IP of the Broadcaster by selecting one of the following: 1. **Auto Detect/Use Public IP** (default) - select this checkbox if you want ZEN Master to detect the public IP automatically or to use the public IP if the private IP is not detected. 2. **Manual** - If you would like to specify a separate private IP, deselect the checkbox and enter the broadcaster’s *private* IP in the **IP **field. :::hint{type="info"} By specifying a private IP, you enable ZEN Master to access streams through the private IP. This enables you to view Source previews and send inter-cluster Sources over the private IP. ::: :::: :::WorkflowBlockItem In the **Bandwidth Limits** section, you can specify limits for the **Input** and **Output** bandwidth in Mbps. ::: :::WorkflowBlockItem Click **Save**. ::: :::WorkflowBlockItem Note that when you look at the Broadcaster in the list on ZEN Master, the status will be **Pending** - it will remain so until you complete the setup by following the steps in: - [Connecting the Zixi Broadcaster (Zixi Broadcaster UI – For Manual)](docId\:OeXqmQgq_YZFbIi_OqjPO) ::: ::::: - [Connecting the Zixi Broadcaster (Zixi Broadcaster UI – For Manual)](docId\:OeXqmQgq_YZFbIi_OqjPO) - [Updating the Broadcaster API Password](docId\:ZLhH8f67VyaRBdiQpwRfg) [title] Actions on Broadcaster Clusters [path] ZEN Master/ZEN Master User Guide/Broadcasters/Viewing Existing Clusters/ ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/UBa_xJbc5HUgnvIe14xFH-20251125-150428.jpg) The top of the Info pane includes buttons for taking the following actions on the selected Broadcaster Cluster: - **Mute/Unmute** – disables/activates notification for error/recovery events. Set the date and time when the mute will automatically be cleared by clicking on the down arrow and selecting **mute until.** - **Edit **–enables you to edit the Broadcaster Cluster configuration. - **Refresh** –refreshes the page. - **Add Broadcaster** - Add a Broadcaster to the Cluster. See [Adding Broadcasters to a Cluster](docId\:iIvjIF17ieMQlgBjoBxxZ) . - **Delete** – deletes the Broadcaster Cluster. - **Widgets/Tabs **view. [title] Source Diagram [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/ This section shows a schematic diagram that displays all resources (ZEC, Broadcasters, and Receivers) and system objects (Sources, Channels, Targets) that relate to this Source and the relationships between the various elements. The diagram also shows relevant data about each object as well as its current status. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/enDKmGp6J-MvwyQPE0VJs_image.png" size="80" width="1798" height="1092" position="center" alt="Source Diagram" darkWidth="1798" darkHeight="1092" showCaption="false"} :::hint{type="info"} Only objects for which you have viewing permission are shown in the diagram. When an object that you are not authorized to view fills an essential role in the flow, then the object is shown with basic info but without detailed data. ::: ## Action Menus ### Gear Menu Click the ⚙️ icon in the upper right corner of the diagram to reveal a menu that allows you to add downstream objects to the diagram: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/uLfMQECqiP351xzuRH-EL_image.png" size="24" width="502" height="510" position="center" alt="Diagram Option" darkWidth="502" darkHeight="510" showCaption="false"} Select the Show Downstream Objects checkbox to display downstream objects: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/iEhUqRv3fP4aFuRZ10q7-_image.png" size="80" width="1802" height="1082" position="center" alt="Downstream Channel" darkWidth="1802" darkHeight="1082" showCaption="false"} ### Kabab Menu To the right of each object name in the diagram, there is a kabab icon you can click on to reveal a context menu for that object: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Bm1dStflgT0oEbCdP8dRT_diagram-context-menu.png) Note that the items in the menu will change according to object type. The example shown above is the context menu for a source in **Failover Source** and includes an option to **Lock** (or **Unlock**) the source, as well as **Edit**, **Disable**, or **Mute** it. [title] Adding a Source - SPTS Multiplex [path] ZEN Master/ZEN Master User Guide/Sources/Adding ZEN Master Sources/ The SPTS source can be used to combine parts of multiple SPTS streams or programs within and MPTS stream into a single SPTS (Single Program Transport Streams) Multiplex source on a Broadcaster. The streams you want to include from multiple SPTS sources are specified by PID numbers.The MPTS should have a Target bitrate that is higher than the sum of all of the effective bitrates of the individual streams included in the SPTS Multiplex source. Typical use cases would include using an audio stream from one source with the video stream from another and combining two video streams for a video-within-video display or multi-angle video streams (in the cases of combining multiple video streams, the downstream receiver or player would need to handle how to display and/or switch between them). :::hint{type="warning"} Note that the SPTS Multiplex source requires Zixi Broadcaster V19 or later. ::: The following procedure describes how to add an SPTS Multiplex Source in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. ## To add an SPTS Multiplex Source: :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Source selection** window is displayed. ![Create Source Options](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-3mXDQJHXUppSRZJSBYBnR-20250805-132303.png) ::: :::WorkflowBlockItem Click on **Multiplex**. The **Create New SPTS Multiplex Source** window opens. ![SPTS Multiplex Source settings ](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-TVBkP9ygrgPcdJCxvpSUT-20250805-133157.png) ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, enter a unique name to identify this Source in the system. ::: :::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** Configuration** section, 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 preference. 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 Under **Sources**, in the **Pad to CBR (kbps)** field, do one of the following: - To enable VBR - leave this field blank. - To enable CBR - Specify the desired CBR bitrate of the SPTS Multiplex. This should be greater than the sum of the max bitrates of the content streams you are combining from the input sources. :::hint{type="info"} To find the max, min, and average bitrate for a stream, see see [Finding PID numbers and Bitrates](docId\:XFlBxEvjE2UD-0UVTnnx7) section below. ::: :::: ::::WorkflowBlockItem From the **Sources** list, select the sources to add them to the Multiplex source. They will then appear in the table below the source selector: ![Sources for SPTS Multiplex](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-qT0NghTd1HKALyhLW9IOu-20250807-190401.png) In that table below, specify the following settings: - Select the **Primary** source that will provide the video stream. - In the **PIDS **fields, enter one or more PID numbers for the streams that you want to include in the new SPTS Multiplex source. You can map the PID to a new number by using the syntax **\[original PID]: \[new PID]** (the *:\[new PID]* is optional). For example: 256,257:260,300. If you're not sure how to find the PID numbers, see [Finding PID numbers and Bitrates](docId\:XFlBxEvjE2UD-0UVTnnx7) section below. :::hint{type="info"} PIDs must be entered, leaving the PIDs blank results in a Broadcaster error ::: - Click the **- **button to remove a source**.** :::hint{type="warning"} Note: if one of the sources you are adding to the primary source is an HTML overlay, you will need to have the [HTML Overlay](docId:6SNc7FcKnryvMtgzr06kB) installed. HTML Overlays can also be added to Transcoded Sources if you are using Broadcaster v18 or later. ::: :::: :::WorkflowBlockItem Check the **Remove inactive streams from output **to avoid errors messages about missing content. ::: :::WorkflowBlockItem Select the **Alert on PID changes** checkbox if you would like to generate email notifications whenever a PID change is detected. ::: ::::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 closed captions, select **Monitor CEA-608 **checkbox**.** ::: ::::WorkflowBlockItem :::hint{type="info"} Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: If you would like to monitor CEA-708 closed captions, select **Monitor CEA-708 **checkbox**.** :::hint{type="info"} Monitoring CEA-708 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: :::: ::::WorkflowBlockItem If you would like to disable auto-pull, select the **Disable Auto-Pull** 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. (Default: 1000 ms) ::: ::::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 Additional SCTE-35 options are available when you expand the** SCTE-35 Manipulation** section: ![SCTE-35 Manipulation](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/FxvVWM-bhpg9ZdVYW_LCl-20251104-153319.png) Here you can: - Enable SCTE-35 Manipulation - Specify the length of a search window for a NULL packet for SCTE-35 intertion - Set the SCTE-35 PID - Remove any existing SCTE-35 messages from the stream See the **Parameters Table** below for an explanation of these options. ::: :::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 Under **Error Concealment,** click the Enable Error Concealment checkbox to enable the following error concealment mechanisms that can correct transaport stream for downstream IRDs: :::Paragraph{indent="1"} 1\. **Continuous Timeline** - corrects errors that are related to timeline jumps in the source. This mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input. ::: :::Paragraph{indent="1"} 2\. **Replace Frames** - If there are frames with CC errors, it replaces them with skip frames (inserts the last good frame received in place of missing ones). This solves issues such as an IRD that lost synchronization when it received broken frames. This mechanism also creates a variant of the input (doubling the input). ::: :::Paragraph{indent="1"} 3\. **Renumber CC **- The Continuity Counter is part of the TS encapsulation. When there are CC errors in TR101 analysis it means that the counter has a gap due to the lost frames. This mechanism can re-write the CC counter for the downstream devices, so they will see a continuous increase of the counter. ::: :::Paragraph{indent="1"} 4\. **Delay (ms) **- Enter the delay that the Error Concealment adds to the stream in miliseconds. Error Concealment needs to buffer the stream to analyze it. One second is a reasonable value. Lower values may cause the Error Concealment to not be able to fix some of the frames. ::: :::Paragraph{indent="1"} 5\. **CBR Padding** - enter a value for the rate at which padding will be added to maintain a specific output transport bitrate. For example, if you have a video bitrate at 5000 kbps or that varies from 3000-5000 kbps and audio at 64 kbps, total bitrate will be max 5064 kbps or min 3064 kbps. With CBR padding set at 6000 kbps, 6000 kbps is being delivered downstream at all times, ensuring a consistent bitrate. ::: :::Paragraph{indent="1"} 6.** PCR Interval** - Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. This depends on standard used by downstream encoders or decoders. Options include: ::: :::Paragraph{listStyleType="disc" indent="2"} ATSC standard - 100 ms ::: :::Paragraph{listStyleType="disc" indent="2"} DVB standard - 40 ms ::: 7. **Remux Buffer Size** - Specify the time added for remuxing the stream (default: 2500 ms). 8. **Smoothing** - Time added for smoothing a bursty stream - adds to latency, but produces a smoother output. See [Improving Stream Resiliency: Error Correction and Concealment](docId:9_OLo1Argk_2aDoSHYFBb) for more information. ![Error Concealment Options](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/jEyT42FS_YflpTNxqCc9Q_zm-error-concealment-options.png) :::: :::WorkflowBlockItem If you would like to adjust the advanced settings, click **Advanced**. The **Advanced** settings fields are displayed: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ONBTRUO2BodIkESATPaDb_spts-source-advanced.png) ::: :::WorkflowBlockItem If you would like to track usage for this Source, enter your **Billing Code** details. See [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ). ::: :::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 apply Input NIC selection to the network device, select the **Apply Input NIC selection to network device** checkbox ::: :::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 Click **Save**. ::: ::::: ## Finding PID numbers and Bitrates To find PID numbers and bitrates for video and audio streams, you can use ZEN Master's stream analysis for sources. To enable that, you will need to select **Full Content Analysis **when you create the source, or edit the source and select the **Full** option under **Content Analysis**: ![Enabling Content Analysis](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-OgmBb70ArRG4sqgWqKN_M-20250807-143653.png) Once Content Analysis is enabled, you can view the [Source Stream](docId\:dbcol69jr73U2Wy3SOFGw) to find the information you need: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-C32dt2znjJTGIXBfWrgTd-20250807-152823.png" size="58" width="684" height="746" position="center" alt="PID Number and Bitrate information" darkWidth="684" darkHeight="746" showCaption="false"} ## Parameters Table | **Parameter** | **Description** | | ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the Multiplex 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. | | ***Configuration*** | | | Ingest Cluster | Select from the drop-down list one of the available Ingest Clusters as the destination for the Source. | | Target Broadcaster/s | 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.*
**Note**: For managed clusters, it is not recommended to select a specific Broadcaster, as the Broadcaster’s availability may not remain stable. | | ***Sources*** | | | Pad to CBR \[kbps] | Do one of the following:
* To enable VBR - leave this field blank. * To enable CBR - Specify the desired CBR bitrate of the SPTS Multiplex. This should be greater than the sum of the max bitrates of the content streams you are combining from the input sources. | | Sources | Click the **+** button on the relevant sources to add them to the Multiplex source. | | Program Name | Enter a name for the program. This overwrites any pre-existing Program Name previously assigned to the stream. | | Program | Enter a program number for the SPTS source. This overwrites any pre-existing program number previously assigned to the source. | | Base PID | Enter a Base PID number for the SPTS source. Zixi will automatically assign new PID numbers for all PIDs in the SPTS stream with consecutive numbers following the Base PID number based on this number. | | Remove Inactive Streams from Multiplex | Select this checkbox if you would like to automatically remove inactive streams from the MPTS source. | | Alert on PID changes | If you would like to generate email notifications whenever a PID change is detected, select this checkbox. | | 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. | | 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. | | Monitor CEA-608 Closed Captions | If you would like to monitor CEA-608 closed captions, select this checkbox.
Note: Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. | | Monitor CEA-708 Closed Captions | If you would like to monitor CEA-708 closed captions, select this checkbox.
Note: Monitoring 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 desired latency for auto-pull actions. (Default: 1,000 ms) | | 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. | | ***SCTE-35 Manipulation*** | | | Enable SCTE-35 Manipulation | Select checkbox to enable SCTE-35 Manipulation. | | SCTE-35 PID | Set the SCTE-35 PID in which the messages will be inserted. | | Remove Existing SCTE-35 | Remove any existing SCTE-35 messages from the stream. | | Replace with NULL | Replace any existing SCTE-35 messages with NULL. | | ***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/recovery notifications for this Source upon initial configuration. | | ***Error Concealment*** | | | Enable Error Concealment | Select this checkbox to enable the error concealment mechanisms listed below to correct transport stream for downstream IRDs. | | Continuous Timeline | Corrects errors that are related to timeline jumps in the source. This mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input. | | Replace Frames | If there are frames with CC errors, it replaces them with skip frames (inserts the last good frame received in place of missing ones). This solves issues such as an IRD that lost synchronization when it received broken frames. This mechanism also creates a variant of the input (doubling the input). | | Renumber CC | encapsulation. When there are CC errors in TR101 analysis it means that the counter has a gap due to the lost frames. This mechanism can re-write the CC counter for the downstream devices, so they will see a continuous increase of the counter. | | Delay (ms) | Enter the delay that the Error Concealment adds to the stream in miliseconds. Error Concealment needs to buffer the stream to analyze it. One second is a reasonable value. Lower values may cause the Error Concealment to not be able to fix some of the frames. | | CBR Padding (kbps) | Enter a value for the rate at which padding will be added to maintain a specific output transport bitrate. For example, if you have a video bitrate at 5000 kbps or that varies from 3000-5000 kbps and audio at 64 kbps, total bitrate will be max 5064 kbps or min 3064 kbps. With CBR padding set at 6000 kbps, 6000 kbps is being delivered downstream at all times, ensuring a consistent bitrate. | | PCR Interval (ms) | Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. Options include:
* ATSC standard - 100 ms * DVB standard - 40 ms | | ***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+) | | 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
| Specify the maximum transmission unit (largest data packet that a network-connected device will accept) in bytes for the Auto Pull. | | Auto-Pull Billing Password
| Enter the password that corresponds to this auto-pull billing code. | | Auto Pull MTU (seconds) | Specify the maximum transmission unit (largest data packet that a network-connected device will accept) in bytes for the Auto Pull. | | Apply Input NIC selection to network device | Select this checkbox to apply Input NIC selection to the network device. | | 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 for empty audio streams to prevent false warnings - enter a comma-delimited list of PID numbers that should not be monitored for null content. | [title] Adding ZEN Master Sources [path] ZEN Master/ZEN Master User Guide/Sources/ ZEN Master Sources are Inputs on a Broadcaster Cluster. The following Sources can be added as ZEN Master Sources: - **Zixi** - Zixi push from a connected Feeder, Broadcaster, AWS MediaConnect, or other Zixi-enabled device to ZEN Master. - **Monitor Only** - Monitor an existing input on a ZEN Master enabled Broadcaster: Limited functionality - **Failover** - Combine existing Sources into a single Source that will switch between them to maintain quality. - **Transcoded** - Transcode an existing source into a new one. - **PID Mapping** - Create a Source with modified PIDs from an existing source - **Inter-Cluster** - Send a Source from one cluster to another - **UDP/RTP** - Receive UDP or RTP stream directly. - **File** - Create a Source from a .ts file on a Broadcaster - **SRT** - Receive stream via SRT protocol - **RIST** - Receive stream via RIST protocol - **NDI** - Receive an NDI stream in the local network and encode it for transmission - **RTMP** - Receive stream via RTMP protocol - **HLS** - Receive stream via HLS protocol - **Demux** - Create a Demux Source on a Broadcaster - **Multiviewer** - Collection of selected sources in a grid - **MPTS Multiplex** - Create an MPTS Multiplex Source on a Broadcaster - **SPTS Multiplex** - Create an SPTS Multiplex Source on a Broadcaster [title] Adding a Zixi Source – Feeder [path] ZEN Master/ZEN Master User Guide/Sources/Adding ZEN Master Sources/ You can add an input from a Zixi Feeder to a Broadcaster cluster to be managed as a source in ZEN. This is done by selecting **Zixi** in the New Source menu. In this case, the Feeder is referred to as the **Origin Feeder** which streams to the **Ingest Broadcaster**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/j1jcTuCSCh32BabGGBgdn_image.png) - **Network bonding -** When configuring a Source using a Push stream from a Zixi Feeder to 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 Zixi Broadcaster. You can specify which NICs are used for Bonding or you can select *Automatic *to enable ZEN Master to divide the bandwidth evenly among all available NICs. - **Multiple inputs - **You can select several inputs from a single Feeder to simultaneously create a new Source in ZEN Master for each input. The following procedure describes how to add a Zixi Feeder Source in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. ### To add a Zixi Source: :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Source** window is displayed. ![Create Source Options](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-3mXDQJHXUppSRZJSBYBnR-20250805-132303.png) ::: :::WorkflowBlockItem Click on **Zixi**. The **Create Zixi Source** window opens. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-v1GUTP1OaZREeLbn5PNXl-20250608-102210.png) ::: :::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). 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: - Click on the **Edit** icon next to the **Location** field. A search box is shown below the **Location** field. - Enter identifying info for the location (e.g. street address, zip code, coordinates). Search results are displayed below the search box as you type. - Click on the desired location. The selected location populates the **Location** field. ::: :::WorkflowBlockItem In the **Input** section, verify under **Mode** that **Push** is selected (default), and under **Application** that the **Feeder** radio button is selected (default). ::: :::WorkflowBlockItem In the **Feeder **field, select from the drop-down list one of the available Feeders the Feeder that will be the **Origin Feeder**. ::: ::::WorkflowBlockItem Specify the input/s that will be part of the Source coming from the **Origin Feeder.** - If you would like to create a Source from a single input, do not select the **Create multiple Sources from multiple Inputs** checkbox, and in the **Feeder Input** field, select from the drop-down list the desired Input. - If you would like to create sources from multiple inputs, use the following procedure: - Select the Create multiple 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 **Feeder Inputs** section and the Name field in the Info section is disabled. ::: :::hint{type="success"} You can create up to 25 Sources at once. ::: - In the **Feeder Inputs** field select from the list one or more Inputs by clicking the + button for the desired input. 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 Feeder. - 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 for the source. The default is set automatically based on the current bitrate of the source. :::hint{type="info"} 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. ::: :::: :::WorkflowBlockItem If you would like the Source configured in ZEN Master to replace (i.e. stop) any current Outputs configured on the Feeder, select the **Replace existing manual outputs.** ::: :::WorkflowBlockItem In the Bonding section, select the radio button for the desired bonding mode. Options are: - **None** (default) – no bonding - **Manual** – you specify which NICs are used for bonding - **Auto** – all available NICs are used for bonding If you selected Auto, proceed to step 14. If you selected Manual proceed to step 13. If you selected None then continue with the following step. ::: :::WorkflowBlockItem If you selected None for Bonding, then in the **Feeder Output NIC** 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. Proceed to step 14. ::: ::::WorkflowBlockItem If you selected *Manual* for **Bonding**, then in the **Feeder Output NIC** field, use the following procedure to specify which NICs are used. - Select two or more NICs by clicking the + button for each of the desired NICs. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ovYxb0-r2iyclvgY0vOAL_image.png" size="80" width="827" height="353" position="center" alt="Bonding Dialog" showCaption="false"} - Selected NICs are shown above the Filter box. (You can remove a NIC by clicking the - button for that NIC). ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/WEf-_heg3mGQP51Vt_g6u_image.png" size="80" width="824" height="354" position="center" alt="Selected NICs for Bonding" showCaption="false"} - 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. :::hint{type="info"} If the **Backup** checkbox is not selected then this NIC is used in parallel with the other selected NICs. ::: :::: :::WorkflowBlockItem In the **Configuration** section, 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, 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*. :::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 If you would like to set a password to authenticate the stream from the Feeder, in the **Source Password** field, enter the password or generate a random password by clicking on **Random**. You need to configure the identical password (case sensitive) on the Feeder. ::: ::::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 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. ::: :::hint{type="info"} 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 290TR 101 290 ](https://www.etsi.org/deliver/etsi_tr/101200_101299/101290/01.03.01_60/tr_101290v010301p.pdf)Technical Report. **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/CEA-708 closed captions, select the **Monitor CEA-608/CEA-708** checkbox. :::hint{type="info"} Monitoring CEA-608/CEA-708 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: :::: ::::WorkflowBlockItem If you would like to disable auto-pull, select the **Disable Auto-Pull **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 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: ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-XnvItjR5VBTtfpxMJS8Jw-20250820-123543.png) ::: ::::WorkflowBlockItem If you would like to track usage for this Source, enter your **Billing Code** details. See [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ) . :::hint{type="info"} Note that billing codes are **not** supported for **Push** Sources until Broadcaster **v19+**. ::: :::: :::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 Click **Save**. ::: ::::: ### 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 Feeder Source, verify that **Push **is selected (default). | | Application | To create a Zixi Feeder Source, verify that the **Feeder **radio button is selected (default). | | Feeder | Select from the drop-down list the desired Feeder. | | 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. | | Feeder Input/s

| Select from the list one or more of the Inputs that are available on the selected Feeder.

For multiple Inputs, click on the + (plus) button for each of the desired Inputs.

Selected Inputs are shown above the **Filter **box. (You can remove an Input by clicking the - (minus) 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 Feeder.
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 Feeder, select this checkbox. | | Bonding | Select the desired bonding mode. Options are:
* **None **(default) – no bonding * **Manual **– you specify which NICs are used for bonding * **Auto **– all available NICs are used for bonding | | Feeder Output NIC/s (for None and Manual bonding) | 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 Manual for **Bonding**, then click the + (plus) 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 - (minus) 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. | | 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. | | Password
(Optional) | If you would like to set a password to authenticate the stream from the Feeder, enter the password or generate a random password by clicking on **Random**. You need to enter the identical password on the Feeder. | | PID Mapping Profile
(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 | If enabled, Zixi adjusts the latency dynamically to optimize it for network conditions. | | 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. | | 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) | | 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/recovery 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 Passwords | Enter the password that corresponds to this billing code. | | Validate Billing Code | Check to make sure the Billing Code exists. | | 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. | | 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. | | 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. | | 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. | [title] Adding a Zixi Source – Broadcaster Push [path] ZEN Master/ZEN Master User Guide/Sources/Adding ZEN Master Sources/ ## 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**. ![Broadcaster Source Diagram](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/CNE5OFY6Bc_n2jCt5SlgZ_image.png) - **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. ![Create Source Options](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-3mXDQJHXUppSRZJSBYBnR-20250805-132303.png) ::: :::WorkflowBlockItem Click on **Zixi**. The **Create Zixi Source** window opens. ![Create New Broadcaster Zixi Push Sour](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/e1aZ5gYjhGANSacRzZ30S-20251028-165939.png) ::: :::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://archbee-image-uploads.s3.amazonaws.com/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. ![NICs for Bonding](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/-WMVndadnSJAQjAOi2LH4_image.png) - Selected NICs are shown above the **Filter** box. (You can remove a NIC by clicking the **-** button for that NIC). ![Remove NIC](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Yj0MQ4jA-TEa5cl4EmNj0_image.png) - 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. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/hmED6gDJlf3Amgi9mRgmm_bx-push-source-advanced.png) ::: ::::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. | [title] Adding a Source - Multiviewer [path] ZEN Master/ZEN Master User Guide/Sources/Adding ZEN Master Sources/ A Multiviewer source displays multiple video feeds in a grid-like view for monitoring purposes. It enables real-time monitoring and visualization of multiple video feeds in a single multi-viewer source, while displaying real-time statistics. ZEN Master offers one multi-viewer option: - **TAG Video Systems** – ZEN Master supports TAG Video System’s Multi-Viewer solution (e.g., MCM-9000). Existing TAG deployments can be used without special integration. For more information, see - [https://tagvs.com/](https://tagvs.com/) ZEN Master manages multi-viewers as objects in ZEN Master through the **Multi-Viewers** screen. Before creating a Multiviewer source, you will need to configure at least one Multiviewer in the **Multi-Viewers** section. For more detailed instructions, see the [Multi-Viewers](docId\:i_PdRyv31_RpsbkUtNUgI) section. :::hint{type="info"} The TAG Multiviewer needs to be preconfigured with the desired layout configurations, the Encoder profile, and other video settings. ::: The following steps describe how to add a Multiviewer Source in ZEN Master. An explanation of each configuration parameter is provided in the table below. ## To add a Multiviewer Source: :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Source selection** window is displayed. ![Create Source Options](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-3mXDQJHXUppSRZJSBYBnR-20250805-132303.png) ::: :::WorkflowBlockItem Click on **Multiviewer**. The **Create New Multiviewer Source** window opens. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/drNKJhA4m2QXAk3ujgYNM_image.png) ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, enter a unique name to identify this Source in the system. ::: :::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 Under **Inputs**, under the **Multiview Type**, the following is the only multiviewer supported at this time: - **Tag** – to use a TAG Video System’s Multi-Viewer solution (e.g., MCM-9000). ::: :::WorkflowBlockItem In the **Multiviewer** field, select the relevant Multiviewer from the drop-down menu. This list is populated by the objects that were configured in the @Multi-Viewers screen. ::: :::WorkflowBlockItem For **TAG** option, in the **Layout** field, select the desired layout from the list of preconfigured layouts. These layouts are configured in the TAG system itself. After selecting the desired layout, an empty grid is displayed with empty rectangles to assign the desired sources from the list of sources. In the **Encoder **section, select the relevant Encoder profile. Encoders are configured in the TAG system itself. ![Grid Display for Multiviewer](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/YkHB5nfWGreet0d7IA9sf_image.png) ::: :::WorkflowBlockItem In the Sources section, do one of the following: - Click the **+** button to add the source to the first (top left rectangle) and repeat the process to add sources to the designated grid spots (left to right, top to bottom). - Drag the source to the relevant grid slot. ::: :::WorkflowBlockItem In the **Configuration **section, 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 preference. 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 **Public Output** field, to allow access to the stream directly through a supported player, select the Allow checkbox. :::hint{type="info"} 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 closed captions, select **Monitor CEA-608 **checkbox**.** :::hint{type="info"} Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: If you would like to monitor CEA-708 closed captions, select **Monitor CEA-708 **checkbox**.** :::hint{type="info"} Monitoring CEA-708 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: To disable auto-pull, select the **Disable Auto-Pull** 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. ::: 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 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 are passed to the WebRTC library, where it is 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 **Additional SCTE-35** options are available when you expand the SCTE-35 Manipulation section: ![SCTE-35 Manipulation](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/FxvVWM-bhpg9ZdVYW_LCl-20251104-153319.png) Here you can: - Enable SCTE-35 Manipulation - Specify the length of a search window for a NULL packet for SCTE-35 intertion - Set the SCTE-35 PID - Remove any existing SCTE-35 messages from the stream See the **Parameters Table** below for an explanation of these options. ::: ::::WorkflowBlockItem In the **Initial State** section, select the Disabled checkbox if you would like to disable this Source upon initial configuration. :::hint{type="info"} You can Enable/Unmute the Source at any time. ::: To adjust the advanced settings, click **Advanced**. The **Advanced** settings fields are displayed: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/0ZS3TguA52VYKjLJFRAdG_multiviewer-source-advanced.png) :::: :::WorkflowBlockItem To track usage for this Source, enter your **Billing Code** details. See [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ). ::: :::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 Click **Save**. ::: ::::: ## Multiviewer Source Configuration Parameters Table | Parameter | Description | | --------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the Multiviewer 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. | | *Inputs* | | | Multiview Type | The following is supported:
* **Tag** – to use a TAG Video System’s Multi-Viewer solution (e.g., MCM-9000). | | Multiviewer | Select the relevant Multiviewer from the drop-down menu. This list is populated by the objects that were configured in the screen. | | Layout | For **TAG option**, select the desired layout from the list of preconfigured layouts. These layouts are configured in the TAG system itself.
After selecting the desired layout, an empty grid is displayed with empty rectangles to assign the desired sources from the list of sources. | | Encoder | Select the relevant Encoder profile. Encoders are configured in the TAG system itself. | | Sources | In the **Sources** section, do one of the following:
* Click the **+** button to add the source to the first (top left rectangle) and repeat the process to add sources to the designated grid spots (left to right, top to bottom). * Drag the source to the relevant grid slot | | ***Configuration*** | | | Ingest Cluster | Select from the drop-down list one of the available Ingest Clusters as the destination for the Source. | | Target Broadcaster/s | 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.*
**Note**: For managed clusters, it is not recommended to select a specific Broadcaster, as the Broadcaster’s availability may not remain stable. | | Profile | For the Zixi option, select a **Transcoding Profile** which will be used for encoding purposes. ZEN Master offers default profiles, but additional profiles can be configured. See [Transcoding Profiles](docId\:kmselIGIGobBQMjZCI-YB). | | Public Output | To allow access to the stream directly through a supported player, select the Allow checkbox. | | 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 | Disables the Source thumbnail from appearing in the Sources list and other places. Disabling thumbnail may improve system performance. | | Monitor CEA-608 Closed Captions | To monitor CEA-608 closed captions, select this checkbox.
Note: Monitoring CEA-608 Closed Captions requires using a Broadcaster version 14.4 or newer. | | Monitor CEA-708 Closed Captions | To monitor CEA-708 closed captions, select this checkbox.
Note: Monitoring CEA-708 Closed Captions requires using a Broadcaster version 14.4 or newer. | | Disable Auto-Pull | 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 desired latency for auto-pull actions. (Default: 1,000 ms). | | 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. | | ***SCTE-35 Manipulation *** | | | Enable SCTE-35 Manipulation | To enable SCTE-35 Manipulation, select this option. | | SCTE-35 PID | Set the SCTE-35 PID in which the messages will be inserted. | | Remove Existing SCTE-35 | Remove any existing SCTE-35 messages from the stream. | | NULL Packet Search Window (ms) | Replace any existing SCTE-35 messages with NULL. | | ***Initial State*** | | | Disabled | To disable this Source upon initial configuration, select this option. | | Muted | To disable error/recovery notifications for this Source upon initial configuration, select this option. | | ***Advanced*** | | | Billing Codes | To track usage for this Source, enter your **Billing Code** details, see [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ). (Supported for Broadcasters v14.8+) | | 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 | Optionally specify a password for the billing code. | | Auto-Pull Billing Code | 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. | | 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. | | 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 for empty audio streams to prevent false warnings - enter a comma-delimited list of PID numbers that should not be monitored for null content. | [title] Adding a Source - UDP/RTP [path] ZEN Master/ZEN Master User Guide/Sources/Adding ZEN Master Sources/ ZEN Master can receive a Source directly from a UDP/RTP input. :::hint{type="info"} When this method is used, the stream is not protected by the Zixi protocol. ::: The UDP streams can be one of the following types: - **UDP** – plain UDP - **RTP** (Real-Time Transport Protocol) - fixes packet reordering (when possible) and supports use of FEC (Forward Error Correction) The following procedure describes how to add a UDP/RTP Source in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. ## To add a UDP/RTP Source: :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Sources**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Source selection** window is displayed. ![Create Source Options](https://archbee-image-uploads.s3.amazonaws.com/amUtKWPrNQCS-26DKyGuI-3mXDQJHXUppSRZJSBYBnR-20250805-132303.png) ::: :::WorkflowBlockItem Click on **UDP/RTP**. The **Create New UDP/RTP** window opens. ![New UDP/RTP Source](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/I_cmxmAClN5YSka-YrRd9-20251104-195915.png) ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, enter a unique name to identify this Source in the system. ::: :::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 **UDP/RTP Configuration** section, if your input stream uses RTP protocol, then select the **Use RTP protocol** checkbox. :::hint{type="info"} Using RTP protocol fixes packet reordering (when possible) and supports use of FEC (Forward Error Correction). ::: :::: ::::WorkflowBlockItem If you selected the **Use RTP protocol** checkbox, then if you would like to use FEC, then select the **Use Forward Error Correction **checkbox. :::hint{type="info"} When FEC is used, repair packets are sent on additional ports, enabling packet recovery. ::: :::: :::WorkflowBlockItem If you selected the **Use RTP protocol** checkbox, then if you would like to preserve the RTP headers (which include the timestamps and sequences) and propagate them the output, then select the **Preserve RTP Headers** checkbox. ::: ::::WorkflowBlockItem If you would like to join a multicast group, in the **Multicast Address** field enter the multicast address. :::hint{type="info"} The multicast address should be in the range of 224.0.0.0 \~ 239.225.255.255. ::: :::: :::WorkflowBlockItem If you entered a multicast address, then, in the **Source Specific Multicast** field, you can specify a particular IP from which you will accept data. ::: ::::WorkflowBlockItem In the **Port** field, specify the port to listen on for the incoming content. :::hint{type="warning"} This port must be open on all firewalls between the Ingest Cluster and the input device. ::: :::: :::WorkflowBlockItem In the **Max Bitrate** field, select from the drop-down list the maximum bitrate for this Source. ::: :::WorkflowBlockItem In the **Source Configuration** section, 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 preference. 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 **Input NIC** 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 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 [Adding PID Mapping Profiles](docId\:gFTCaYurPL7DInoUyd14z). ::: :::: :::WorkflowBlockItem Select the **Alert on PID changes** checkbox if you would like to generate email notifications whenever a PID change is detected. ::: ::::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 Additional SCTE-35 options are available when you expand the **SCTE-35 Manipulation** section: ![SCTE-35 Manipulation](https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/FxvVWM-bhpg9ZdVYW_LCl-20251104-153319.png) Here you can: - Enable SCTE-35 Insertion - Specify the length of a search window for a NULL packet for SCTE-35 intertion - Set the SCTE-35 PID - Remove any existing SCTE-35 messages from the stream See the **Parameters Table** below for an explanation of these options. ::: :::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 closed captions, select **Monitor CEA-608 **checkbox**.** :::hint{type="info"} Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: If you would like to monitor CEA-708 closed captions, select **Monitor CEA-708 **checkbox**.** :::hint{type="info"} Monitoring CEA-708 Closed Captions requires using a version 14.4 or newer Broadcaster. ::: :::: ::::WorkflowBlockItem If you would like to disable auto-pull, select the **Disable Auto-Pull** 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. (Default: 1000 ms) ::: ::::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 Under **Error Concealment,** click the Enable Error Concealment checkbox to enable the following error concealment mechanisms that can correct transaport stream for downstream IRDs: :::Paragraph{indent="1"} 1\. **Continuous Timeline** - corrects errors that are related to timeline jumps in the source. This mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input. ::: :::Paragraph{indent="1"} 2\. **Replace Frames** - If there are frames with CC errors, it replaces them with skip frames (inserts the last good frame received in place of missing ones). This solves issues such as an IRD that lost synchronization when it received broken frames. This mechanism also creates a variant of the input (doubling the input). ::: :::Paragraph{indent="1"} 3\. **Renumber CC **- The Continuity Counter is part of the TS encapsulation. When there are CC errors in TR101 analysis it means that the counter has a gap due to the lost frames. This mechanism can re-write the CC counter for the downstream devices, so they will see a continuous increase of the counter. ::: :::Paragraph{indent="1"} 4\. **Delay (ms) **- Enter the delay that the Error Concealment adds to the stream in miliseconds. Error Concealment needs to buffer the stream to analyze it. One second is a reasonable value. Lower values may cause the Error Concealment to not be able to fix some of the frames. ::: :::Paragraph{indent="1"} 5\. **CBR Padding** - enter a value for the rate at which padding will be added to maintain a specific output transport bitrate. For example, if you have a video bitrate at 5000 kbps or that varies from 3000-5000 kbps and audio at 64 kbps, total bitrate will be max 5064 kbps or min 3064 kbps. With CBR padding set at 6000 kbps, 6000 kbps is being delivered downstream at all times, ensuring a consistent bitrate. ::: :::Paragraph{indent="1"} 6.** PCR Interval** - Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. This depends on standard used by downstream encoders or decoders. Options include: ::: :::Paragraph{listStyleType="disc" indent="2"} ATSC standard - 100 ms ::: :::Paragraph{listStyleType="disc" indent="2"} DVB standard - 40 ms ::: 7. **Remux Buffer Size** - Specify the time added for remuxing the stream (default: 2500 ms). 8. **Smoothing** - Time added for smoothing a bursty stream - adds to latency, but produces a smoother output. See [Improving Stream Resiliency: Error Correction and Concealment](docId:9_OLo1Argk_2aDoSHYFBb) for more information. ![Error Concealment Options](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/jEyT42FS_YflpTNxqCc9Q_zm-error-concealment-options.png) :::: :::WorkflowBlockItem If you would like to adjust the advanced settings, click **Advanced**. The **Advanced** settings fields are displayed: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/lrd1QOEriaYP3sIp6qqH4_udp-source-advanced.png) ::: :::WorkflowBlockItem If you would like to track usage for this Source, enter your **Billing Code** details. See [Billing Codes](docId\:lalXJ_N928TeGCPDpBirJ). ::: :::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 Click **Save**. ::: ::::: **UDP/RTP Source Configuration Parameters Table** | **Parameter** | **Description** | | --------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | ***Info*** | | | Name | Specify a name for the UDP/RTP 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. | | ***UDP/RTP Configuration*** | | | Use RTP protocol | If your input stream uses RTP protocol, then select this checkbox.
Using RTP protocol fixes packet reordering (when possible) and supports use of FEC (Forward Error Correction). | | Use Forward Error Correction (FEC) (for Use RTP protocol) | If you would like to use FEC, then select this checkbox.
When FEC is used, repair packets are sent on additional ports, enabling packet recovery. | | Preserve RTP Headers | Select this checkbox to preserve the RTP headers (which include the timestamps and sequences) and propagate them the output. | | Multicast Address | If you would like to join a multicast group, enter the multicast address.
The multicast address should be in the range of 224.0.0.0 \~ 239.225.255.255. | | Source Specific Multicast (for Multicast Address) | Specify a particular IP from which you will accept data. | | Port | Specify the port to listen on for the incoming content.
This port must be open on all firewalls between the Ingest Cluster and the input device. | | Max Bitrate | 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. | | ***Source 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 | 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. | | PID Mapping Profile
(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. | | Log SCTE-35 | Select this checkbox if kyou 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 | | Monitor CEA-608 Closed Captions | If you would like to monitor CEA-608 closed captions, select this checkbox.
**Note:** Monitoring CEA-608 Closed Captions requires using a version 14.4 or newer Broadcaster. | | Monitor CEA-708 Closed Captions | If you would like to monitor CEA-708 closed captions, select this checkbox.
**Note:** Monitoring 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 desired latency for auto-pull actions. (Default: 1,000 ms) | | 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. | | ***SCTE-35 Manipulation *** | | | Enable SCTE-35 Insertion | Select checkbox to enable SCTE-35 Insertion. | | SCTE-35 PID | Set the SCTE-35 PID in which the messages will be inserted. | | Remove Existing SCTE-35 | Remove any existing SCTE-35 messages from the stream. | | NULL Packet Search Window (ms) | Look for a NULL packet 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 | | ***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/recovery notifications for this Source upon initial configuration. | | ***Error Concealment*** | | | Enable Error Concealment | Select this checkbox to enable the error concealment mechanisms listed below to correct transport stream for downstream IRDs. | | Continuous Timeline | Corrects errors that are related to timeline jumps in the source. This mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input. | | Replace Frames | If there are frames with CC errors, it replaces them with skip frames (inserts the last good frame received in place of missing ones). This solves issues such as an IRD that lost synchronization when it received broken frames. This mechanism also creates a variant of the input (doubling the input). | | Renumber CC | encapsulation. When there are CC errors in TR101 analysis it means that the counter has a gap due to the lost frames. This mechanism can re-write the CC counter for the downstream devices, so they will see a continuous increase of the counter. | | Delay (ms) | Enter the delay that the Error Concealment adds to the stream in miliseconds. Error Concealment needs to buffer the stream to analyze it. One second is a reasonable value. Lower values may cause the Error Concealment to not be able to fix some of the frames. | | CBR Padding (kbps) | Enter a value for the rate at which padding will be added to maintain a specific output transport bitrate. For example, if you have a video bitrate at 5000 kbps or that varies from 3000-5000 kbps and audio at 64 kbps, total bitrate will be max 5064 kbps or min 3064 kbps. With CBR padding set at 6000 kbps, 6000 kbps is being delivered downstream at all times, ensuring a consistent bitrate. | | PCR Interval (ms) | Select the frequency at which Program Clock Reference is inserted into the outputs Transport stream. Options include:
* ATSC standard - 100 ms * DVB standard - 40 m | | ***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+) | | 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. | | Auto Pull MTU | Specify the maximum transmission unit (largest data packet that a network-connected device will accept) in bytes for the Auto Pull. | | Apply Input NIC selection to network device | Select this checkbox to apply Input NIC selection to the network device. | | Frozen Video Minimal Duration | 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 | 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. | | Dejitter Buffer | The length of the de-jitter buffer (in milliseconds). The buffer is used to collect packets and measure the jitter of the source that is arriving with jitter. | | Dejitter Clock Source | Select which mechanism should be used in the calculation of the jitter:
* Arrival times * RTP timestamps | | Ignore Monitoring PIDs | Ignore PIDs for empty audio streams to prevent false warnings - enter a comma-delimited list of PID numbers that should not be monitored for null content. | [title] Source SCTE-35 Log [path] ZEN Master/ZEN Master User Guide/Sources/Viewing Existing Sources/ If SCTE-35 was enabled for the Source, the SCTE-35 section shows a log of all the SCTE-35 markers for this Source. To learn about the data that is displayed in the SCTE-35 tab, see [SCTE-35](docId\:cBSZctkAkxCo1zpUyaqmm). ![log of SCTE-35 markers](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ulkXyc8lsEBFBuNFKJOf5_image.png) ## SCTE-35 Graph The graph marks the various events on a timeline. The event types and their colors are indicated in the legend, which is located at the bottom of the graph. The X-axis indicates the timeline and the Y-axis indicates the number of events. The graph features the following functionality: - Set the time range of the display either by selecting one of the preset time ranges or by entering a custom time range. (Default: *Last 6 hr*) - Manually refresh graph data or set the automatic refresh frequency. - Hover over a point on the graph to show the total values for that time. - Click and drag the cursor over a time range to zoom in on that time range. The table at the bottom will be also filtered to include only events within the zoomed time range. - Double click on the graph to zoom out on the graph (i.e. expand the time range). - Click on the title of a data element in the key to display only that element. ## SCTE-35 Table The SCTE-35 table displays the SCTE-35 messages that were detected. The rows are color coded according to the type of message (e.g., Program Start/End, Chapter Start/End, etc.). You can filter the list using the graph or by typing a message (or part of it) in the Filter Message field. | **Column ** | **Description** | | | ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------ | ------ | | Date/Time | The date and time that the SCTE-35 message was detected. |
| | PID | The PID that the SCTE-35 message appeared in |
| | Auto Return | Specifies whether to auto-return from from a cue-out, for break of the specified duration. |
| | Pre-roll | Specifies the duration of the pre-roll. |
| | PTS | The Presentation Timestamp. The time at which the SCTE-35 message insertion request was received. The PTS is a "timer", not a clock time. |
| | Message | The contents of the SCTE-35 message. |
| | Actions | Click the "i" icon to view a JSON containing the raw message and a parsing of the message content. | | - **Filter Message** - filters the list based on the inputted text. - **Hide/Show Colors** - hides or shows the color coding of the table. - **Columns** - hides/shows columns in the table. - **Report** - click to download the table as an Excel file report. [title] SCTE-35 Insertion [path] ZEN Master/ZEN Master User Guide/Sources/ Zixi supports SCTE-35 Insertion on Sources using the API *(*[ZEN Master API](docId\:SafxBsM3wuvfg1NwpeAau)* )* The SCTE-35 payload to be inserted must be pre-formed by the customer and encoded as base-64 or hex. ## Setup :::::WorkflowBlock :::WorkflowBlockItem In sources that support SCTE-35 insertion, select **Enable SCTE-35 Manipulation:** ::Image[****]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/oRh0KK21lwl31l_qktBxQ-20260102-200402.png" size="68" width="770" height="168" position="center" alt="Enable SCTE-35 Manipulation" darkWidth="770" darkHeight="168" showCaption="false"} ::: ::::WorkflowBlockItem Enter a Null Packet Search Window to designate an appropriate timeout interval when searching for a NULL packet to replace with the SCTE-35 packet to maintain PCR accuracy in CBR streams. If no NULL Packet is detected by the time the timeout is reached, the SCTE-35 will be inserted anyway, breaking PCR Accuracy momentarily. (If stream is VBR, set this to 0) :::hint{type="info"} **Note: Pre Broadcaster v19, 0 seconds will still insert immediately for VBR streams, but all other values will have a fixed timeout of 2 seconds** ::: ![Null Packet Window](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/LClViGZYGA27ghOlB9Bc2-20260102-200914.png) :::: :::WorkflowBlockItem Choose whether to Remove Existing SCTE-35 packets or not. (Generally, this is only selected if leveraging a SCTE-35 Modification workflow, not for SCTE-35 injection) ::: ::::: ## Insertion Use the ZEN Master API to insert the desired SCTE-35 payload encoded as Base64: - POST to *https\://api.zen.zixi.com/*v2**/sources/\:sourceId/scte35** - Payload: ```json { "scte35": "" } ```   [title] Viewing Existing Remote Access Profiles [path] ZEN Master/ZEN Master User Guide/Remote Access/ The Remote Access screen displays all of the existing remote access profiles and information about the profile. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/3dYKbAtFO9qOoo32whxSH-20260111-122544.jpg) :::hint{type="info"} It is possible to add more columns to the list. If you want to view resources that were marked as Priority, add the Priority column and sort by it. ::: | **Parameter** | **Description** | | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Name | The name of the remote access profile as configured in ZEN Master. | | Tag | The Tag/s that is associated with this Remote Access Profile. | | Status | The connection status of the remote access profile. Possible values:
* Green – OK * Red – error state * Pink (shown together with a checkmark) – acknowledged error state * Gray – pending/disabled (waiting for initial connection)
The muted icon next to a remote access connection indicates that the object is muted, disabling notifications for error/recovery events. | | IP | The IP of the remote device as seen by ZEN Master. | | Type | The profile configuration type – Zixi or Videon. | | Link | Click **Open** to access the remote device UI. | When a Remote Access Profile is selected, the following tabs are shown at the right side of the screen.The info can also be shown in Tabs, Widgets or Expand view. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/1JwQE9PZB7S-yo4mXzpgG-20260104-145641.jpg) - **Events** - A log of the events that were generated in ZEN Master in relation to the selected remote access profile. To learn about viewing event logs in ZEN Master, see [Events](https://zixidocumentation.atlassian.net/wiki/spaces/ZMUG/pages/483688494/Events). Click **Quick Report** to generate a report of events related to this device and download the .xls file. - **Details** – configuration details of the remote access profile. - **Notes **– free-form text can be added with pertinent information about this remote access profile. [title] Adding MediaLive HTTP Targets [path] ZEN Master/ZEN Master User Guide/Targets/ The MediaLive HTTP Target can be used to create AWS MediaLive transcoding channels which can be targeted to a S3 Bucket, MediaStore or HTTP Server. The following procedure describes how to add an AWS MediaLive HTTP Target in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. **To add a new MediaLive HTTP Target:** :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Targets**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Target** window is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/zvFxXsgvX6d6ikzJ2Qcmd_image.png" size="80" width="730" height="1406" position="center" alt="Create New Target window" showCaption="false"} ::: :::WorkflowBlockItem Click on **MediaLive HTTP**. The **Create New MediaLive HTTP Target** window is displayed. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/_X9lEO7ElUvz31w1M2g8g-20251113-153157.jpg) ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, enter a logical name for the **MediaLive HTTP** 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 Under the **Configuration** section, under **Channel**, select from the drop-down list an AWS MediaLive Channel that will be sent to the Target. (Optional field) :::hint{type="info"} - The Channel Type is automatically set as *ZEN Master Channel* and can’t be changed. - 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 Under **Type**, select the type of AWS MediaLive Target - *S3 Bucket*, *MediaStore* or *HTTP Server*. ::: :::WorkflowBlockItem In the **S3/MediaStore/HTTPServer** **URI** field, enter the Uniform Resource Identifier for the Target. ::: :::WorkflowBlockItem Under **Renditions**, select one or more Transcoding Profiles by clicking the **+ **button for the desired Source. Selected Transcoding Profiles are shown above the Filter (You can remove a Transcoding Profile by clicking the **-** button). ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/G-9hvg-dn6Y1n7AYdrU8V-20251113-153527.jpg) ::: :::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 Click **Save.** :::hint{type="info"} You can verify that the new Target was created by viewing the Source tab in the MediaConnect UI. ::: :::: ::::: **MediaLive HTTP Target Configuration Parameters Table** | **Parameter** | **Description** | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | ***Info*** | | | Name | Specify a name for the NDI 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 | The location of the Target. | | ***Configuration*** | | | Channel
(Optional) | Select from the drop-down list an AWS MediaLive 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. | | Type | Select the type of AWS MediaLive Target:
* S3 Bucket * MediaStore * HTTP Server | | S3/MediaStore/HTTPServer URI | Enter the Uniform Resource Identifier for the Target. | | Renditions | Select one or more Transcoding Profiles by clicking the **+ **button for the desired Source. Selected Transcoding Profiles are shown above the Filter (You can remove a Transcoding Profile by clicking the **-** button) | | ***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. | [title] Actions on a Remote Access Profile [path] ZEN Master/ZEN Master User Guide/Remote Access/Viewing Existing Remote Access Profiles/Untitled/ Click on one of the Remote Access Profile to display information on the right-pane. On the upper right side of the **Info Pane**, you will see the following options: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/9-ClJL1jQ-rd9Ogh9gSdO-20260115-122239.jpg) - **Mute/ Unmute** – disables/activates notification for error/recovery events. Set the date and time when the mute will automatically be cleared by clicking on the down arrow and selecting **mute until.** - **Disable/Enable** – disabling a Remote Access stops all activity for that device without deleting the configuration of the device. - **Edit** – enables you to edit the Zixi Receiver configuration. - **Refresh **– refreshes the data on the screen. - **Mute until **– set a date and time when the mute will automatically be cleared. - **Open **– click to access the Remote Access Profile UI. - **Clone **– create an additional Remote Access based on the settings of the selected Remote Access. - **Delete** – deletes the Remote Access configuration. [title] Live Event Management [path] ZEN Master/ZEN Master User Guide/Live Events/ ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/bWcM9QiwNTGnMlJv_WSVa-20251117-125310.png) The Live Event Management screen is the "front-end" screen where a Live Event Operator can monitor the live event and control its broadcast, including manual override controls for full control over stage transitions. The screen includes the following main elements: - **Stages progress bar** – the progress bar displays the various stages of the live event and their scheduled times. The current stage and previous stages are marked in blue. - **Stage Countdown **- displays a count-down to the next stage. - **Delivery Flow** – displays all the ZEN Master objects that are assigned to the delivery flow per channel. Each Failover Source/Channel creates a separate delivery flow. Multiple delivery flows are displayed on the screen. Each delivery flow includes the following elements (from left to right): - **Channel column** – displays a preview of what is currently being delivered as the output of the channel. The header displays the channel status, name, and processing cluster. The status icon indicates the channel state and the name of the source that is currently streaming. Click the **Expand** icon to view the Channel details. - **Sources column **– displays small previews of the sources in the Failover Source/Channel and their status. Click the Expand icon to view the Source details. The header of the source displays the source status, name, and processing cluster. In addition, it displays the **Source's Priority Configuration** - Preferred/Secondary/Slate, while indicating which of the sources is currently Active. Hovering the mouse on top of the source displays the following buttons: - **Preview** - displays a preview of the source on the Preview column. - **Lock** - locks the Source so that it is the only Source that is going to be played in the Live Event, even if there is a failover event. Locked sources are indicated with a lock icon. - **Preview column - **displays the Source feed of the Source on which the **Preview** button was clicked. Selecting the **Show Overlay** checkbox displays a timecode and audio levels overlay on the Preview video. - **Clips - **At the bottom of the screen the Clips section displays small previews of the promo clips that were created for this Live Event. Hovering the mouse on top of the clip displays the following buttons: - **Preview - **displays a preview of the clip on the Preview column. - **Insert - **forces the clip to play immediately in the Live Event. - **Refresh** – click this button to refresh the entire screen. - **Edit **- click this button to edit the event configuration. - **Full Screen** - click to view in full screen mode. - **Live Event Controls** – offers a variety of buttons to manually control the event. For more information, see [Live Event Manual Controls](docId\:woR-auFr6SSXoBmH1V5gT). [title] Target Diagram [path] ZEN Master/ZEN Master User Guide/Targets/Viewing Existing Targets/ This section shows a schematic diagram that displays all components (ZECs, Feeders, Broadcasters, and Receivers) and system objects (Sources, Channels, Targets) that relate to this Channel and the relationships between the various elements. The diagram shows the following elements from left to right and their statuses: - **Source component** - the system that streams the stream. For example, ZEC or Broadcaster, AWS Media Source. The object is marked by its type (e.g., ZEC) and below it is the name of the component - **Ingest Cluster **- the Cluster that hosts the component that sends the Source. The top name represents the Broadcaster Cluster name, under it is the Broadcaster name, and within Broadcaster is the Source Type (e.g., ZEC Source) and the Source name. - **Processing Cluster** - the Cluster that performs the processing (e.g., Transcoding). The top name represents the Broadcaster Cluster name, under it is the Broadcaster name, and within Broadcaster is the Channel (e.g., ZEC Source), which includes the Channel name, and the Target Types with their respective Target names. - **AWS components** - for AWS Media Channels the components may include AWS MediaConnect Flow and MediaLive Channel. :::hint{type="info"} Only objects for which you have viewing permission are shown in the diagram. When an object that you are not authorized to view fills an essential role in the flow, then the object is shown with basic info but without detailed data. ::: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/gYS_oh7JlmiP-YmyjBNEB-20260119-153815.png) Click on the **+/-** button to zoom in/out on the display. :::hint{type="info"} When ZEN Master is displayed in a narrow window the diagram is displayed in a vertical orientation. ::: ## Play Inline ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/6UsVJbMsFE_MySITAZYqL-20260119-154507.png" size="30" width="253" height="265" position="center" darkWidth="253" darkHeight="265" showCaption="false"} The **Play Inline** button will play the original MPEG Transport Stream in a player in the browser. Because the Zixi Broadcaster is often behind a firewall, when using ZEN Master the stream is proxied through the ZEN Master backend to which the user's browser has access. Previewing a video with "Play Inline" will only run for a few minutes each time and is intended to be a quick preview of the video. For longer term preview with no timeout, consider using VLC or WebRTC instead. Because it is the original transport stream being delivered to the browser via HTTP, the full bitrate of the stream will be transferred. This is different to webRTC, which transcodes the stream to a lower bitrate and is different from Zixi protocol that does lossless compression on the stream when possible. :::hint{type="info"} To enable this feature, make sure that the **Allow automatic HTTP Pull output** setting in Broadcaster is enabled (Settings > Live Protocols > HTTP Server). Note that enabling this setting will require a restart. ::: ## Display Settings ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ENq47dfGWn0baw2SmBOsZ-20260119-154740.png" size="32" width="231" height="211" position="center" darkWidth="231" darkHeight="211" showCaption="false"} Click the **Cog** icon to open the following display settings: - Show Broadcasters - shows/hides the Broadcasters used in the channel. - Show Clusters - shows/hides the Broadcaster Clusters used in the channel. - Show Details - shows/hides the details of the components. - Show Thumbnails - shows/hides the Source thumbnail. - Horizontal Layout - displays the diagram from left to right. - Vertical Layout - displays the diagram from top to bottom. ## Channel Switching ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/VP7SHR3ajAlL6WSCL9VzS_channel-switching.png) - Switch to the primary or a backup channel manually [title] Adding ST 2110 JPEG XS Targets [path] ZEN Master/ZEN Master User Guide/Targets/ JPEG XS targets are supported only on Flows that have a CDI or JPEG XS Source. You can configure an AWS MediaConnect "Flow" that has already been set up in your MediaConnect account to be used in the JPEG XS Target in ZEN Master. :::hint{type="info"} In order to use this feature, you must first link ZEN Master to an AWS account, see [Linking an AWS Account](docId\:erygXkCUfmmZ8BaKidJz4) ::: The following procedure describes how to add an JPEG XS Target in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. **To add a new JPEG XS Target:** :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Targets**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Target** window is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/zvFxXsgvX6d6ikzJ2Qcmd_image.png" size="80" width="730" height="1406" position="center" alt="Create New Target window" showCaption="false"} ::: :::WorkflowBlockItem Click on **JPEG XS**. The **Create New JPEG XS Target** window is displayed. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/d5KNbTnNFGwDpDUeeciUQ-20251026-131647.jpeg) ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, enter a logical name for the **JPEG XS** 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 Under the **Configuration** section, in the **AWS MediaConnect Flow** field, select from the drop-down list a MediaConnect Flow that have an EFA VPC interface with a CDI or JPEG XS Source. ::: :::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 Click **Save.** ::: ::::: **JPEG XS Target Configuration Parameters Table** | **Parameter** | **Description** | | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | ***Info*** | | | Name | Specify a name for the NDI 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. | | ***Configuration*** | | | MediaConnect Flow | Select from the drop-down list a MediaConnect Flow that have an EFA VPC interface with a CDI or JPEG XS Source. | | ***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. | [title] Using the Live Events Filter [path] ZEN Master/ZEN Master User Guide/Live Events/Viewing Existing Events/ ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/2Z-vkg0y0IG2b_xVsBd8w-20260412-123424.png) At the top of the Live Events screen you can use a combination of the following filters and then click **Apply**: - **Search** – searches the name of the live event. Start typing the name of the live event to filter the list accordingly. - **Stages **– filter by the current stage of the live event: **Scheduled**, **Active**, **Completed**. Deselect the checkboxes to exclude live events, whose current stage matches the deselected checkbox. For example, to exclude all the Completed events, deselect the **Completed **checkbox. - **Tags **– click to select by tags. For more information, see [Configuring Tags](docId\:vPSZIytS_uzxdb-zvrAcX). - **From **– click to select the date and time in which the event starts. - **To** – click to select the date and time in which the event ends. The filtered list is displayed at the bottom in table or timeline formats. Click **Report** to generate a spreadsheet report of the filtered results. [title] Channel Diagram [path] ZEN Master/ZEN Master User Guide/Channels/Viewing Existing Channels/ This section shows a schematic diagram that displays all components (ZECs, Feeders, Broadcasters, and Receivers) and system objects (Sources, Channels, Targets) that relate to this Channel and the relationships between the various elements. The diagram shows the following elements from left to right and their statuses1: - **Source component** - the system that streams the stream. For example, ZEC or Broadcaster, AWS Media Source. The object is marked by its type (e.g., ZEC) and below it is the name of the component - **Ingest Cluster **- the Cluster that hosts the component that sends the Source. The top name represents the Broadcaster Cluster name, under it is the Broadcaster name, and within Broadcaster is the Source Type (e.g., ZEC Source) and the Source name. - **Processing Cluster** - the Cluster that performs the processing (e.g., Transcoding). The top name represents the Broadcaster Cluster name, under it is the Broadcaster name, and within Broadcaster is the Channel (e.g., ZEC Source), which includes the Channel name, and the Target Types with their respective Target names. - **AWS components** - for AWS Media Channels the components may include AWS MediaConnect Flow and MediaLive Channel. :::hint{type="info"} Only objects for which you have viewing permission are shown in the diagram. When an object that you are not authorized to view fills an essential role in the flow, then the object is shown with basic info but without detailed data. ::: ![Sample Channel Diagram](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/eS5vzKn8-KiYEIMa4nz2o_image.png) Click on the **+/-** button to zoom in/out on the display. :::hint{type="info"} When ZEN Master is displayed in a narrow window the diagram is displayed in a vertical orientation. ::: ## Play Inline The **Play Inline** button will play the original MPEG Transport Stream in a player in the browser. Because the Zixi Broadcaster is often behind a firewall, when using ZEN Master the stream is proxied through the ZEN Master backend to which the user's browser has access. Previewing a video with "Play Inline" will only run for a few minutes each time and is intended to be a quick preview of the video. For longer term preview with no timeout, consider using VLC or WebRTC instead. Because it is the original transport stream being delivered to the browser via HTTP, the full bitrate of the stream will be transferred. This is different to webRTC, which transcodes the stream to a lower bitrate and is different from Zixi protocol that does lossless compression on the stream when possible. :::hint{type="info"} To enable this feature, make sure that the **Allow automatic HTTP Pull output** setting in Broadcaster is enabled (Settings > Live Protocols > HTTP Server). Note that enabling this setting will require a restart. ::: ## Display Settings Click the **Cog** icon to open the following display settings: - Show Broadcasters - shows/hides the Broadcasters used in the channel. - Show Clusters - shows/hides the Broadcaster Clusters used in the channel. - Show Details - shows/hides the details of the components. - Show Thumbnails - shows/hides the Source thumbnail. - Horizontal Layout - displays the diagram from left to right. - Vertical Layout - displays the diagram from top to bottom. [title] Log Events [path] ZEN Master/ZEN Master User Guide/Logs/Events/ The following table describes the types of events that are logged for each type of system object and shows the severity level of each event. All events are logged. In addition, Error events generate email notifications. You can customize the notification settings, see [Notifications](docId\:rdrWYWtdNanWgFgazFEag). | **Object** | **Event** | **Level** | | -------------------------------------------------------------- | ------------------------------------------------------------------------------------------------- | --------- | | **Feeder** | Connection issues | Error | | API error | Warning | | | CPU/Mem above 90% | Error | | | Expired/missing license | Error | | | **Broadcaster** | Connection issues | Error | | API error | Warning | | | CPU/GPU/Mem/HDD above broadcaster configured limits | Error | | | GPU decoder/encoder usage above configured limits | Warning | | | Input/Output bandwidth above limits configured in Zen | Error | | | Expired/missing license | Error | | | Version not supported for various Zen features | Error | | | Configuration doesn't match Zen requirements (e.g. ports/dtls) | Error | | |
|
| | |
|
| | | **Broadcaster Cluster**



| Add |
| |
|
| | |
|
| | |
|
| | |

**Receivers** | Connection issues | Error | | API error | Warning | | | CPU above 90% | Error | | | Expired/missing license | Error | | | **Source** | Missing implementation (e.g. feeder output is not on the feeder) | Error | | Connection issues | Error | | | TR101 Priority 1 and CQA | Warning | | | Low bitrate, | Warning | | | Bitrate above max bitrate | Warning | | | Unrecovered packets | Warning | | | Content Analysis errors (if enabled in ZEN) | Error | | | **Channel** | Missing implementation | Error | | Missing inputs that are required for the channel | Error | | | Transcoding errors | Error | | | **Target** | Missing implementation | Error | | | Connection issues (e.g. GCP authorization errors, RTMP authorization errors etc.) | Error | | | HLS verification for adaptive targets (playlists are downloadable and chunks respond to http HEAD | Warning | | **Remote Access** | Checks if tunnel is alive | Error | | **License** | Checks if expired or expiring soon | Error | | **Live Event** |
|
| | **Automation** |
|
| | **User Events** |
|
| | **Account Management** | Logs updates and changes to security objects, including Users, Groups and Roles. |
| [title] Status [path] ZEN Master/ZEN Master User Guide/Dashboard/ The account status section shows a color-coded status indicator for each of the resources and ZEN entities managed through ZEN Master. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/jDA9Gd6zaPkADtQjjbrLU_image.png" size="76" width="564" height="209" position="center" alt="Status Section" showCaption="false"} For each object type, the number next to the status indicator shows how many entities are currently in that status. The following is an explanation of the status indicators: - Green – OK (i.e. connected and functioning without errors) - Red – error state/disconnected - Pink – acknowledged error state - Yellow – warning state - Gray – standby (i.e. pending, disabled or not assigned) - Muted icon - muted (i.e. notification for error/recovery events have been disabled) :::hint{type="info"} The meaning of the status indicators differs slightly for each object type. ::: [title] Alarms Notification List [path] ZEN Master/ZEN Master User Guide/Logs/ List of Notification alarms that can be customized within ZEN Master. ### Alarm Notification List - Adaptive Channel - Adaptive Group - Other - Unaligned Timestamp - Offline - Missing - Other - Rendition Error - Other - Source Missing - Transcoding - Transcoding Error - Broadcaster - API - Error - Configuration - DTLS - Error - License - Error - Expiring - Limit - Status - Error - Restart - Terminated - Usage - CPU - GPU - GPU Decoder - GPU Encoder - GPU Memory - HDD - Input Bandwidth - Memory - Output Bandwidth - MediaConnect Flow - API - Error - Status - Analysis - Flow Error - Low Bitrate - Not Recovered Packets - Offline - Reconnection - TR101 - Authorization - Upload Error - Validation - HLS Playlist - HLS Playlist Critical - Subtitles - Pull - Failover - Partial - Remote Access - Connection - Error - Source - Analysis - Audio Clipping - Blank Picture - CEA-608/CEA-708 Closed Captions - Frozen Video - Low Audio Level - Missing SCTE-35 - PIDS Change - Silent Audio - TR101 P1 Tables - TR101 P1 Transport - TR101 P2 - Configuration - Error - Non-Identical Sources - Version - Offline - Error - Unknown - Status - Error - Error Concealment - Low Bitrate - Not Recovered Packets - Over Max Bitrate - Reconnection - Transcoding - Error - Target - Offline - Broadcaster Error - Missing - Other - Stopped - Status - Low Bitrate - Not Recovered Packets - Reconnection - Send Errors - ZEC - API - Error - License - Error - Expiring - Usage - CPU - Memory For more information on configuring alarms within Zen Master please see [Zen Master Monitoring](docId:_aySQ8V9hS7NFM2S0HzxV) and [Configuring Events Profiles](docId\:CWshWpVMDch_ryL86IMTS). [title] Target Info Pane [path] ZEN Master/ZEN Master User Guide/Targets/Viewing Existing Targets/ When a Target is selected, the list pane is minimized and detailed info about the selected Target is shown on the right side of the screen. The info can be shown in *Tabs,* Widgets or Expand view: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/KQPDQAw8RlHNN9N59Sbel-20260111-120640.jpg) | **Parameter** | **Description** | | ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Type | The type of the Target in ZEN Master e.g., S3, Pull, Push, RIST, RTP, UDP, File etc. | | ***Push*** | | | Channel | The channel that is associated with the Target. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Target has been enabled. * No - the Priority checkbox of the Access Tag of this Target has been enabled. | | Tags | The Tag/s that is associated with this Target. | | Source Preferece | The preference for connecting to a Source. Possible values include:
* **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. | | Location | The location of the Target. | | Network | The network on which the Target is hosted. | | Events Configuration Profile | The Events Configuration Profile that was selected for this Target. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Latency | The latency value that was configured for the Target. Actual latency will be set by Cluster redirection rules, then this value, and then the remote device’s configuration. | | ***Pull*** | | | Channel | The channel that is associated with the Target. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Target has been enabled. * No - the Priority checkbox of the Access Tag of this Target has been enabled. | | Tags | The Tag/s that is associated with this Target. | | Source Preference | The preference for connecting to a Source. Possible values include:
* **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. | | Location | The location of the Target. | | Network | The network on which the Target is hosted. | | Events Configuration Profile | The Events Configuration Profile that was selected for this Target. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Latency | The latency value that was configured for the Target. Actual latency will be set by Cluster redirection rules, then this value, and then the remote device’s configuration.
| | ***HTTP*** | | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Target has been enabled. * No - the Priority checkbox of the Access Tag of this Target has been enabled. | | Play Target | Click **Target** to play the Target content. | | Tags | The Tag/s that is associated with this Target. | | Location | The location of the Target. | | Network | The network on which the Target is hosted. | | Events Configuration Profile | The Events Configuration Profile that was selected for this Target. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Encapsulation | The type of encapsulation used in the stream. Options are:
* DASH - CMAF (DASH + fMP4 HLS) * HLS | | ***MediaLive HTTP*** | | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Target has been enabled. * No - the Priority checkbox of the Access Tag of this Target has been enabled. | | Tags | The Tag/s that is associated with this Target. | | Events Configuration Profile | The Events Configuration Profile that was selected for this Target. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | ***Azure*** | | | Channel | The channel that is associated with the Target. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Target has been enabled. * No - the Priority checkbox of the Access Tag of this Target has been enabled. | | Play HLS | Click **HLS** to play the Target content. | | Tags | The Tag/s that is associated with this Target. | | Location | The location of the Target. | | Network | The network on which the Target is hosted. | | Events Configuration Profile | The Events Configuration Profile that was selected for this Target. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Encapsulation | The type of encapsulation used in the stream. Options are:
* DASH - CMAF (DASH + fMP4 HLS) * HLS | | ***AWS Media*** | | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Target has been enabled. * No - the Priority checkbox of the Access Tag of this Target has been enabled. | | Tags | The Tag/s that is associated with this Target. | | Source Preference | The preference for connecting to a Source. Possible values include:
* **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. | | Location | The location of the Target. | | Network | The network on which the Target is hosted. | | Events Configuration Profile | The Events Configuration Profile that was selected for this Target. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | ***RIST*** | | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Target has been enabled. * No - the Priority checkbox of the Access Tag of this Target has been enabled. | | Tags | The Tag/s that is associated with this Target. | | Source Preference | The preference for connecting to a Source. Possible values include:
* **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. | | Location | The location of the Target. | | Network | The network on which the Target is hosted. | | Events Configuration Profile | The Events Configuration Profile that was selected for this Target. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | ***RTMP*** | | | Active Broadcaster | The Broadcaster instance that is currently being used to stream. | | Channel | The channel that is associated with the Target. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Target has been enabled. * No - the Priority checkbox of the Access Tag of this Target has been enabled. | | Tags | The Tag/s that is associated with this Target. | | Source Preference | The preference for connecting to a Source. Possible values include:
* **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. | | Events Configuration Profile | The Events Configuration Profile that was selected for this Target. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Bitrate | The current bitrate of the stream. | | ***RTP*** | | | Active Broadcaster | The Broadcaster instance that is currently being used to stream. | | Channel | The channel that is associated with the Target. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Target has been enabled. * No - the Priority checkbox of the Access Tag of this Target has been enabled. | | Tags | The Tag/s that is associated with this Target. | | Target | The IP address and port of the destination to which the stream is being pushed. | | Source Preference | The preference for connecting to a Source. Possible values include:
* **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. | | Events Configuration Profile | The Events Configuration Profile that was selected for this Target. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | ***S3*** | | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Target has been enabled. * No - the Priority checkbox of the Access Tag of this Target has been enabled. | | Play Target | Click to load a player to view the stream. | | Tags | The Tag/s that is associated with this Target. | | Location | The location of the Target. | | Network | The network on which the Target is hosted. | | Events Configuration Profile | The Events Configuration Profile that was selected for this Target. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Encapsulation | The stream encapsulation. Possible values:
* CMAF (DASH + fMP4 HLS) * HLS | | Region | The cloud service region. | | ***SRT Pull (Listener)*** | | | Channel | The channel that is associated with the Target. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Target has been enabled. * No - the Priority checkbox of the Access Tag of this Target has been enabled. | | Tags | The Tag/s that is associated with this Target. | | Source Preference | The preference for connecting to a Source. Possible values include:
* **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. | | Location | The location of the Target. | | Network | The network on which the Target is hosted. | | Events Configuration Profile | The Events Configuration Profile that was selected for this Target. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Latency | The latency value that was configured for the Target. Actual latency will be set by Cluster redirection rules, then this value, and then the remote device’s configuration. | | ***SRT Push (Caller)*** | | | Active Broadcaster | The Broadcaster instance that is currently being used to stream. | | Channel | The channel that is associated with the Target. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Target has been enabled. * No - the Priority checkbox of the Access Tag of this Target has been enabled. | | Tags | The Tag/s that is associated with this Target. | | Target | The IP address and port of the destination to which the stream is being pushed. | | Source Preference | The preference for connecting to a Source. Possible values include:
* **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. | | Events Configuration Profile | The Events Configuration Profile that was selected for this Target. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Latency | The latency value that was configured for the Target. Actual latency will be set by Cluster redirection rules, then this value, and then the remote device’s configuration. | | ***UDP*** | | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
* Yes - the Priority checkbox of the Access Tag of this Target has been enabled. * No - the Priority checkbox of the Access Tag of this Target has been enabled. | | Tags | The Tag/s that is associated with this Target. | | Target | The IP address and port of the destination to which the stream is being pushed. | | Source Preference | The preference for connecting to a Source. Possible values include:
* **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. | | Events Configuration Profile | The Events Configuration Profile that was selected for this Target. Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | [title] Adding NDI Targets [path] ZEN Master/ZEN Master User Guide/Targets/ You can enable NDI output on a Pass-Through Channel Source. :::hint{type="info"} - NDI Targets are only supported on v14+ broadcasters. - NDI Targets use only the primary Source of a Channel. ::: The following procedure describes how to add an NDI Target in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. **To add a new NDI Target:** :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Targets**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Target** window is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/zvFxXsgvX6d6ikzJ2Qcmd_image.png" size="80" width="730" height="1406" position="center" alt="Create New Target window" showCaption="false"} ::: :::WorkflowBlockItem Click on **NDI**. The **Create New NDI Target** window is displayed. ![Create New NDI Target window](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/I37s1G5vcEVnslsiiWzAK_image.png) ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, enter a logical name for the **NDI** 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, 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 **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 Click **Save.** ::: ::::: **NDI Target Configuration Parameters Table** | **Parameter** | **Description** | | ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the NDI 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
(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.
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. | | ***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. | [title] Channel Ad Markers [path] ZEN Master/ZEN Master User Guide/Channels/Viewing Existing Channels/ The Ad Markers tab is only shown for relevant Channels. If an Adaptive or Transcoded Channel has a stream that contains Ad Markers, then information about these markers is shown in the Ad Markers tab. HLS ad markers are written as plaintext into the outgoing XML manifests of the transmuxed HLS. ![Channel Ad Markers](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/yLdhtV5EqpPsMO_TpEUXH_image.png) The following table describes the information shown for each Ad Marker in the stream. | **Parameter** | **Description** | | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Bitrate** | The name of the 'component' on which the ad marker was written | | **Time** | The timestamp of the ad marker. | | **Network** | The type of ad marker. Possible types are:
* **Cue-out** – marks the beginning of the ad insertion opportunity * **Cue-in** – marks the end of the ad insertion opportunity | | **PTS** | The Presentation Timestamp. The time at which the SCTE-35 message insertion request was received. The PTS is a "timer", not a clock time. | | **Duration** | The duration of ad break (if the marker is a cue-out). | | **Program** | The elementary program that the SCTE marker is affecting. | | **Auto-return** | Specifies whether to auto-return from from a cue-out, for break of the specified duration. | [title] Manually Extending a Stage Past the Next Stage [path] ZEN Master/ZEN Master User Guide/Live Events/Live Event Management/ After changing an **Auto **Stage to **Manual **(see, [Switching to Manual or Auto During the Event](docId\:CpoByE-8DDBja2Qg9gY98)), a dialog will be displayed asking you to choose whether you want to **Maintain start time** or **Maintain duration**. In this section we will explain what is the meaning of each option is and what are its consequences for the next stages when you use them to extend a stage, **but the extension is longer than the next stage**. ## Maintain Start Time Extension Past the Next Stage In this option the next stage **is skipped**. Every stage after that which is also configured as Auto, **will be according to the originally configured Start Time**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/2Vwh7yjOli6QN-bQLzm5L-20251110-140323.png) In the example illustrated above the** First Half stage is manually extended by 15 minutes**. In this case the following will occur: - During the “First Half” stage the operator switched to manual and selected the **Maintain Start Time** option. - After 15 minutes into the first half extension the operator clicked **Start Next Stage** and moved directly to the **Second Half stage** (the **Half Time Break stage is skipped**). - The start times of the following stages (marked by a red rectangle) will begin automatically according to the original configuration: - **Second Half** **stage will begin** at **9:00 PM **(the original configured start time for the Second Half stage). - The **Second Half** **will end **automatically at** 9:45 PM** (the original configured start time for the Off stage). - **Note that if the First Half extension were to go past 9:00 PM, for example 9:10 PM, the Second Half would begin at 9:10 PM and end at 9:45 PM.** ## Maintain Duration Extension Past the Next Stage In this option the next stage, following the manual transition, is skipped. Every stage after that, which is also configured as Auto, will be according to the originally configured **Duration**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/LyUx9rQ3Z38cNxSs1Jykz-20251110-142227.png) - In the example illustrated above the **First Half stage is manually extended by 15 minutes**. In this case the following will occur: - During the “First Half” stage the operator switched to manual and selected the **Maintain Duration **option. - After 15 minutes into the first half extension the operator clicked Start Next Stage and moved to the Half Time Break stage. - The **start times** of the following stages **will be shifted by 15 minute**s, as they will begin automatically according to the original duration configuration (marked by a red rectangle): - **Half Time Break stage will end** automatically at **9:15 PM** (based on the original configured duration for the Half Time Break stage) and the Second Half will start automatically. - The **Second Half** **will end** automatically at **10:00 PM** (based on the original configured duration for the Second Half stage). [title] Manually Shortening a Stage [path] ZEN Master/ZEN Master User Guide/Live Events/Live Event Management/ After changing an **Auto **Stage to **Manual **(see, [Switching to Manual or Auto During the Event](docId\:CpoByE-8DDBja2Qg9gY98)), a dialog will be displayed asking you to choose whether you want to **Maintain start time** or **Maintain duration**. In this section we will explain what is the meaning of each option and what are its consequences for the next stages when you use them **to shorten a stage**. ## Maintain Start Time Shortening In this option the **start time of the next stage** will be according to the originally configured **Start Time**. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/sMt8dhMhlyKaej77aszTi-20251110-131745.png) In the example illustrated above, the First Half stage is **manually shortened by 5 minutes**. In this case the following will occur: - During the “First Half” stage the operator switched to manual and selected the **Maintain Start Time** option. - 5 minutes before the original end of the First Half, the operator clicked **Start Next Stage **and moved to the Half Time Break stage. - The Half Time Break is extended by 5 minutes, as it started early. - The start times of the following stages (marked by a red rectangle) will begin automatically according to the original configuration: - **Half Time Break stage **will end automatically at** 9:00 PM** (the original configured start time for the Second Half stage) and the Second Half will start automatically. - **The Second Half **will end automatically at **9:45 PM **(the original configured start time for the Off stage). ## Maintain Duration Shortening In this option the **start time of the next stage **will be according to the **Duration **of each stage. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/sDes4woJPpz4XeZPpK1CP-20251110-133618.png) In the example illustrated above the first half is manually shortened by 5 minutes. In this case the following will occur: - During the “First Half” stage the operator switched to manual and selected the **Maintain Duration** option. - 5 minutes before the original end of the first half, the operator clicked Start Next Stage and moved to the Half Time Break stage. - The start times of the following stages will be **shifted 5 minutes earlier**, as they will begin automatically according to the original duration configuration (marked by a red rectangle): - **Half Time Break stage** will end automatically at **8:55 PM** (based on the original configured duration for the Half Time Break stage) and the Second Half will start automatically. - **The Second Half** will end automatically at** 9:40 PM** (based on the original configured duration for the Second Half stage). [title] Channel Bitrates [path] ZEN Master/ZEN Master User Guide/Channels/Viewing Existing Channels/ This section is shown for Adaptive and Transcoded Channels. It displays a list of stream bitrate variants. HLS transmux (conversion) in an Adaptive or Transcoded Channel recives a Zixi input stream in and then generates HLS stream variants as an output. In case of an Adaptive Channel, there is one input and for each output. For Transcoding Channel, there is a single input for all the outputs. **Adaptive:** ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/5A_rHQc6HonRJevTAMcfA-20260118-144339.jpg) | **Column** | **Description** | | ----------------- | ---------------------------------------------------------------- | | **Source** | The name of each source variant. | | **Status** | The status of the Adaptive stream output. | | **Source Status** | The status of the Adaptive stream output's corresponding input. | | **Bitrate** | The bitrate of the Source profile. | **Transcoded: ** ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/BSDQ8dvBMPma6_wm8EpB4-20260118-145040.jpg) | **Column** | **Description** | | ----------------- | ----------------------------------------------------------------------------------------------- | | **Name ** | The name of the transcoding profile. | | **Status** | The status of the Transcoded stream output. | | **Source Status** | The status of the Transcoded stream output's corresponding input. | | **Bitrate** | The bitrate of the Source/transcoding profile. | | **Profile ** | The transcoding profile. Hover over the ℹ️ icon to show detailed information about the profile. | [title] Adding Zixi AWS MediaConnect Targets [path] ZEN Master/ZEN Master User Guide/Targets/ You can configure an AWS MediaConnect "flow" that you have already set up in your MediaConnect account to be used as a Target in ZEN Master. :::hint{type="info"} In order to use this feature, you must first link ZEN Master to an AWS account, see [Linking an AWS Account](docId\:erygXkCUfmmZ8BaKidJz4), ::: The following procedure describes how to add an AWS MediaConnect Target in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. ## To add a new MediaConnect Target: :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Targets**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Target** window is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/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 **Zixi**. The **Create New Zixi Target** window is displayed. ::Image[]{src="https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/qFGMJiPwTNlLxZN433YW8-20251103-191634.png" size="90" width="1396" height="2592" position="center" alt="New Zixi MediaConnect Target" darkWidth="1396" darkHeight="2592" showCaption="false"} ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, enter a logical name for the MediaConnect 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, 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 **Type **section, select MediaConnect. The fields relevant for MediaConnect Targets are shown. :::hint{type="info"} The Channel Type is automatically set as ZEN Master Channel and can’t be changed. ::: :::: ::::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** AWS Account** field, select from the drop-down list the AWS account that you would like to set as the Target. ::: :::WorkflowBlockItem In the **Region** field, select from the drop-down list the AWS region of the MediaConnect flow that you would like to set as the Target. ::: :::WorkflowBlockItem In the **AWS MediaConnect Flow** field, select from the drop-down list the MediaConnect Flow that you would like to set as the Target. ::: :::WorkflowBlockItem In the **Latency** field, enter the latency in milliseconds. ::: :::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://archbee-image-uploads.s3.amazonaws.com/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 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 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 See the **Parameters Table** below for additional fields, including **Advanced** Settings: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/z5BGh_mMtb5otqBuCC0_h_mediaconnect-target-advanced.png) ::: :::WorkflowBlockItem Click **Save**. ::: ::::: ## AWS MediaConnect Target Configuration Parameters Table | **Parameter** | **Description** | | ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the AWS MediaConnect 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*** | | | Type | Select **AWS MediaConnect**. | | Channel | 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. | | AWS Account | Select from the drop-down list the AWS account that you would like to set as the Target. | | Region | Select from the drop-down list the AWS region of the MediaConnect flow that you would like to set as the Target. | | AWS MediaConnect Flow | Select from the drop-down list the MediaConnect Flow that you would like to set as the Target. | | Latency | Enter the latency in milliseconds. | | ***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 | Select if you wish to override all existing SCTE-35 messages with your own. | | 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 Settings*** | | | 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 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. | | MTU | Specify the maximum transmission unit (largest data packet that a network-connected device will accept) in bytes. | | 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. | [title] Cloning a Channel [path] ZEN Master/ZEN Master User Guide/Channels/ If you would like to create a new Channel with properties similar to those of an existing Channel, you can use the *Clone* feature to simplify the process. **To Clone a Channel:** 1. In the main navigation, click **Channels**. 2. Select the Channel that you would like to Clone (i.e. the Channel that is already configured in ZEN Master which has settings similar to those that you would like to set for the new Channel that you are creating). 3. On the upper right side of the Info Pane, click on the three dots. Select the option **Clone**. The **Add New Channel **window is displayed with all fields other than **Name** populated with the configuration data of the original Channel. 4. In the **Name** field, enter the name of the new Channel. 5. Change any of the fields that you would like to configure differently than the original Channel. See the above sections that describe how to create new Channels of various types. 6. Click **Save**. The Channel is created. ![](https://archbee-image-uploads.s3.amazonaws.com/yloo8L9Y5DmjuuW_iCtAX-m8W--KrZTdz-LspI-95uu-20250729-130147.png) [title] Creating a Map [path] ZEN Master/ZEN Master User Guide/Maps/ You need to first create Maps in the system, each of which contains a set of objects to be shown on the Map display. Then, you can open the Map to see those objects displayed in their geographical locations. The objects displayed on the Map are organized in layers, which can be shown or hidden together. Each Channel that is included in a Map constitutes a separate layer, including all objects associated with that Channel. You can also create custom layers that include any group of specific objects. For example, you can create a layer that shows all of your Broadcasters or you can create a layer that shows all objects related to a certain product **To create a new Map:** :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Maps**. ::: :::WorkflowBlockItem Click + Add. The Create New Map screen is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/J3N-WUi8Nap-3OPRJBUH7_image.png" size="90" width="823" height="1138" position="center" alt="Create New Map screen" showCaption="false"} ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, specify a name for the Map. ::: :::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 Map 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 **Configuration** section, in the **Default Region** field, select from the drop-down list the default region for your assets. Available options are: *Africa*, *Asia*, *Australia/Oceania*, *Europe*, *North America* (*default*) or *South America*. :::hint{type="info"} The default region will be used to position the marker if there is no IP based geolocation and you haven’t manually set the location for the asset. ::: :::: :::WorkflowBlockItem In the **Default Style** field, select from the drop-down list the default background style for this Map. Available options are: *Street* (default)*, Topographic, Dark *or *Light*. ::: :::WorkflowBlockItem Select the **Cluster Markers **checkbox if you would like the Map to cluster nearby Markers together as a single Marker. ::: :::WorkflowBlockItem In the **Channels **section, in the **MediaConnect Flows **field, select from the drop-down list one or more of the MediaConnect Flows to be viewed as a layer on this map. ::: :::WorkflowBlockItem In the **Adaptive Channels** field, select from the drop-down list one or more of the Adaptive Channels to be viewed as a layer on this map. ::: :::WorkflowBlockItem In the **Pass-Through Channels** field, select from the drop-down list one or more of the Pass-Through Channels to be viewed as a layer on this map. ::: :::WorkflowBlockItem In the **Objects** section, if you would like to add individual objects as a layer on this map, click **+ Add Layer**. The **Objects fields** are displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/9dykstdLnDVS0MX-qHUPP_image.png" size="80" width="837" height="872" position="center" alt="Objects fields" showCaption="false"} Configure the layer as follows: 1. In the **Layer Name** field, specify a name for the layer. 2. In the **Feeders/Receivers/Broadcasters/Sources/MediaConnect Sources/Targets** field, select from the drop-down lists one or more of the available objects to be added to this layer. 3. If you would like to add an additional layer to the map, click **+ Add Layer**. ::: :::WorkflowBlockItem If you would like to add additional layers, repeat the previous procedure for each layer. ::: :::WorkflowBlockItem Click **Save**. ::: ::::: [title] Child Targets (for Dynamic Targets) [path] ZEN Master/ZEN Master User Guide/Targets/Viewing Existing Targets/ Dynamic Pull Targets enable you to connect multiple ZECs/Receivers or Zixi-enabled decoders to the same Target. For Dynamic Targets, the **Child Targets** tab shows all devices that have been connected to the Target. The name of each Child Target consists of the name of the parent Target followed by the device ID. You can click on a **Child Target **tab to view additional info of the devices that have been connected to the Dynamic Target. While viewing the details of a Child Target, you can click on the **Convert** button to convert it into an independent Pull Target. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/Q5SmEbjyXT6QbmrS3RA0v-20251029-143920.png) | Column | Description | | ------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Name | The name of the child target comprises the name "Dynamic-Pull" followied by the name of the host that is pulling the stream. | | Status | Shows the status of the Target. Possible statuses are:
* **OK** - the Target is running properly. * **Not Assigned **- the Target is not assigned to a Channel. * **Disabled **- the Target has been disabled. * **Channel Disabled **- the Target is assigned to a Channel, but the Channel has been disabled. * **Error **- the Target is in an error state. Hover over to view the error details. * **Pending **- the Target is in a Pending state until it is connected.
The 🔒 icon next to a Target indicates that the Target is password-protected.
The 🔕 icon next to a Target indicates that the Target is muted, disabling notifications for error/recovery events. | | Target | The name of the host that is pulling the stream | ## Editing the Child Target **To edit the Child Target:** 1. On the **Child Targets** screen, click on the relevant Child Target. :::Paragraph{indent="1"} ::: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/M4q1weEt8eSDTrDeHO_Uk-20251029-151736.png" size="100" width="757" height="250" position="center" showCaption="false" indent="2"} 2. Click the **Details **tab. 3. Click **Convert to an independent pull target**. :::Paragraph{indent="1"} ::: ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/PMdKRyZs3fNuuJUlazTh3-20251029-152101.png" size="100" width="793" height="409" position="center" showCaption="false" indent="2"} :::Paragraph{indent="1"} Following the conversion the target will be removed from the Child Targets tab of the original parent Target. ::: 4. After it has been converted, click **Edit** to modify its settings. :::hint{type="info"} - If the Channel of a parent Target is changed, this will only affect new Child Targets that are connected **after** the change was made. The existing Child Targets will remain connected to the original Channel. To change the Channel for existing Child Targets, change the Channel of the parent and then select the desired child Targets in the Target list and **delete** them. Each Target will then reconnect and obtain the new Channel configuration from the parent Target. - When you delete a parent Dynamic Target, all Child Targets under that parent are automatically converted to independent Pull Targets. ::: [title] Adding SRT Targets [path] ZEN Master/ZEN Master User Guide/Targets/ ZEN Master can send a Source directly to an SRT Pull Target. :::hint{type="info"} When this method is used, the stream is not protected by the Zixi protocol. ::: The following procedure describes how to add an SRT Target in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. ## To add a new SRT Target: :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Targets**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Target** window is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/LxmYOhwQV9fXXnUWIb80Z_image.png" size="80" width="730" height="1406" position="center" alt="Create New Target window" darkWidth="730" darkHeight="1406" showCaption="false"} ::: :::WorkflowBlockItem Click on **SRT**. The **Create New SRT Target** window is displayed. ::Image[]{src="https://app.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/8kr_RZ2nW02KobSxnOSOR-20251104-150219.png" size="80" width="1380" height="2908" position="center" alt="New SRT Target" darkWidth="1380" darkHeight="2908" showCaption="false"} ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, enter a logical name for the SRT 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: - Click on the **Edit** icon next to the **Location **field. A search box is shown below the **Location** field. - Enter identifying info for the location (e.g. street address, zip code, coordinates). Search results are displayed below the search box as you type. - 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*. :::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 If you selected *ZEN Master Channel*, skip to step 16. If you selected *AWS* *MediaConnect Flow*, follow steps 10-15, then skip to step 21. ::: :::WorkflowBlockItem For a *MediaConnect Flow*, under **AWS MediaConnect** **Flow, **select a flow from the drop-down list. ::: :::WorkflowBlockItem For a *MediaConnect Flow*, in the **VPC **field, select the VPC interface name. ::: :::WorkflowBlockItem For a AWS *MediaConnect Flow*, the **Type ***Pull* (Listener) is selected by default. ::: :::WorkflowBlockItem For a AWS *MediaConnect Flow*, in the **Port** field, enter the port number of the receiving end. ::: ::::WorkflowBlockItem For a AWS *MediaConnect Flow*, in the **CIDR Allow List** field, enter the range of IP addresses that should be allowed to contribute content to your source. :::hint{type="info"} The whitelist CIDR block is a range of IP addresses that should be allowed to contribute content to your source. These IP addresses must be in the form of a Classless Inter-Domain Routing (CIDR) block; for example, 10.0.0.0/16. The source needs to be in the range covered by this CIDR block. Any IP address within this range is allowed to send content to this flow. ::: :::: :::WorkflowBlockItem For a *MediaConnect Flow*, in the **Latency \[ms]** field, enter the latency in milliseconds. ::: :::WorkflowBlockItem For a *ZEN Master Channel*, in the **Channel** field, select from the drop-down list the Channel that will be sent to the Target (optional field). ::: ::::WorkflowBlockItem For a *ZEN Master* *Channel*, 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** – 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. :::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 For a *ZEN Master Channel*, under **Type**, select the method for sending the stream. Options are: *Pull* (Listener) or *Push (Caller)*. ::: ::::WorkflowBlockItem For a *ZEN Master Channel*, if you selected* Pull* method, then do the following: - In the **Port** field, enter the port that the server will listen on. - In the **Bind to local NIC by CIDR **field**, **you can enter the CIDR that represents the IP range where the desired NIC is accessed. (Optional) - For a ZEN Master Channel, in the **Latency **\[ms] field, enter the latency in milliseconds. - For a ZEN Master Channel, under **Encryption**, if you would like to encrypt the stream, select one of the encryption methods. Options are: Disabled (default), AES 128, AES 192 or AES 256. :::hint{type="info"} The encryption and decryption for SRT Targets is done automatically based on the password string, there is no need to enter a decryption key on the Target input. ::: - In the **Passphrase **field, enter the SRT stream access credentials – Passphrase. Click show to display the passphrase. - 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) . - For a ZEN Master Channel, select the **Prefer Private Broadcaster IP **checkbox if you would like ZEN to configure connections to use private broadcaster IPs when available. :::: ::::WorkflowBlockItem For a *ZEN Master Channel*, if you selected *Push *method, then do the following: - Select the **Single Output **checkbox if you would like to limit the output to a single stream. :::hint{type="info"} This setting is required for servers that do not properly support concurrent connections. By selecting **Single Output** you will be losing Failover functionality. ::: - In the **Host** field, enter the hostname or IP address of the receiving device. - In the **Port **field, enter the target port on the receiving device. - In the **Stream ID** field, enter the Stream ID that matches the stream in the SRT feed. - In the **Latency \[ms]** field, enter the latency in milliseconds. - Under **Encryption**, if you would like to encrypt the stream, select one of the encryption methods. Options are: *Disabled (default), AES 128, AES 192 *or* AES 256*. :::hint{type="info"} The encryption and decryption for SRT Targets is done automatically based on the password string, there is no need to enter a decryption key on the Target input. ::: - In the **Passphrase **field, enter the SRT stream access credentials – Passphrase. Click show to display the passphrase. - 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://archbee-image-uploads.s3.amazonaws.com/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 **Paramaters Table** below for explanations of the fields. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/aaDdMQuZoYYyrn-lM63_5_srt-target-advanced.png) ::: :::WorkflowBlockItem Click **Save**. ::: ::::: ## SRT Target Configuration Parameters Table | **Parameter** | **Description** | | ------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ***Info*** | | | Name | Specify a name for the SRT 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 an 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 *AWSMediaConnect Flow*. | | **For *AWS MediaConnect Flow:*** | | | AWS MediaConnect Flow | Select an AWS MediaConnect Flow from the drop-down list. | | VPC | Select the VPC interface name. | | Type | Choose between Push or Pull. | | Port | Enter the number of the port on the receiving end. | | CIDR Allow List | Enter the range of IP addresses that should be allowed to contribute content to your source.
**Note**: These IP addresses must be in the form of a Classless Inter-Domain Routing (CIDR) block; for example, 10.0.0.0/16. The source needs to be in the range covered by this CIDR block. Any IP address within this range is allowed to send content to this flow. | | **For *Zen Master Channel:*** | | | Type | Select the method for receiving the stream. Options are: *Pull* or *Push.* | | 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. | | ***For Pull Method (Zen Master Channel Only):*** | | | Bind to local NIC by CIDR | Enter the CIDR that represents the IP range where the desired NIC is accessed. | | Prefer Private Broadcaster IP | Select this checkbox if you would like ZEN to configure connections to use private broadcaster IPs when available. The default behavior when this is not selected is to prefer use of public IPs. Broadcasters typically have a public and private ip address for each network interface. If you pull from the public IP, the request goes out over the internet, even if the target system is on the same local private ip range. To avoid paying for unecessary egress data rates, enabling this setting tells the Broadcaster to seek for the private network connection. | | ***For Push Method (Zen Master Channel Only):*** | | | Single Output | Mark this checkbox if you would like to limit the output to a single stream. | | Host | Enter the Target port on the receiving device. | | Stream ID | Enter the Stream ID that matches the stream in the SRT feed. | | ***For All Methods:*** | | | Port | Enter the port that the server will listen on. | | Latency \[ms] | Enter the latency in milliseconds. | | Password (Zen Master Channel Only) | Enter the SRT stream access credentials – Password. Click **show** to display the password. | | Encryption (Zen Master Channel Only) | If you would like to encrypt the stream, select one of the encryption methods. Options are: *Disabled (default), AES 128, AES 192 *or* AES 256*.
Note: The encryption and decryption for SRT Targets is done automatically based on the password string, there is no need to enter a decryption key on the Target input. | | Passphrase | If encryption is enabled (AES 128/AES 192/AES256), type the **Passphrase** that you want to use. | | 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 . (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. | | SRT Version | Specify a version of SRT to use from the dropdown list. Note that Zixi uses the latest version and we recommend that you use that unless your systems use an earlier version that is not compatible with the latest one. | [title] Channel Info Pane [path] ZEN Master/ZEN Master User Guide/Channels/Viewing Existing Channels/ The **Info pane **section shows the following information: ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/B1wnyp7QMQJ4P8HPL3TBs-20260118-130929.jpg) | **Parameter** | **Description** | | ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Type | The type of the Channel e.g., Pass-Through, Transcoding, Adaptive, AWS Media Flow and AWS MediaLive Channel.
  | | **Transcoded** | | | Processing Cluster | The assigned Processing Cluster. | | Priority
  | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
Yes - the Priority checkbox of the Access Tag of this Channel has been enabled.
No - the Priority checkbox of the Access Tag of this Channel has been enabled. | | Tags | Tags are used for access control. Tags are associated with certain roles (through the Users & Roles screen), and roles, in turn, are associated with users and user groups. | | Mode |  N/A | | Protocols |  The protocol of the stream. | | Events Configuration Profile | Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | Source | The name of the Broadcaster Source that is being transcoded. | | **Pass-Through** | | | Processing Cluster | The assigned Processing Cluster. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
Yes - the Priority checkbox of the Access Tag of this Channel has been enabled.
No - the Priority checkbox of the Access Tag of this Channel has been enabled. | | Tags | Tags are used for access control. Tags are associated with certain roles (through the Users & Roles screen), and roles, in turn, are associated with users and user groups. | | Target Broadcaster/s | The assigned Broadcaster to deliver this Channel. | | Alternative Channel | The selected Alternative Channel. This setting enables reverting an entire path after the Source (i.e., Channel/Broadcaster to the Target) to go through an alternative path, which is usually hosted on an alternative cloud/region. The redirection to the alternative path is manual. So, in case of a fault, if there is no time to troubleshoot a problem, this mechanism allows the user to select the feed that has an issue, click a button and revert the stream to go through a pre-configured alternative path.
For example, if you have a Channel and a Broadcaster on GCP and a secondary Channel and Broadcaster on Azure. If something goes wrong with the GCP path, you can click the Go to Alternative button and failover everything to Azure. | | Events Configuration Profile | Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | **AWS MediaLive Channel** | | | AWS MediaLive Channel |  The selected AWS MediaLive Channel. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
Yes - the Priority checkbox of the Access Tag of this Channel has been enabled.
No - the Priority checkbox of the Access Tag of this Channel has been enabled. | | Tags | Tags are used for access control. Tags are associated with certain roles (through the Users & Roles screen), and roles, in turn, are associated with users and user groups. | | MediaConnect Source | | | Events Configuration Profile | Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | **AWS MediaConnect Flow** | | | AWS MediaConnect Flow |  The selected AWS MediaConnect Flow. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
Yes - the Priority checkbox of the Access Tag of this Channel has been enabled.
No - the Priority checkbox of the Access Tag of this Channel has been enabled. | | Tags | Tags are used for access control. Tags are associated with certain roles (through the Users & Roles screen), and roles, in turn, are associated with users and user groups. | | Region | The cloud service region. | | Events Configuration Profile | Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | | MediaConnect Source | The selected MediaConnect source. | | **Adaptive** | | | Processing Cluster | The assigned Processing Cluster. | | Target Broadcaster |  The Broadcaster that is assigned to this channel. | | Priority | Objects can be labeled as Priority so that they can be quickly found in the list of objects. This is helpful if you want to easily find these objects by sorting and filtering the list. 
Yes - the Priority checkbox of the Access Tag of this Channel has been enabled.
No - the Priority checkbox of the Access Tag of this Channel has been enabled. | | Tags | Tags are used for access control. Tags are associated with certain roles (through the Users & Roles screen), and roles, in turn, are associated with users and user groups. | | Mode |  N/A | | Protocols |  The protocol of the stream. | | Events Configuration Profile | Events Profiles consist of a series of rules that determine precisely how various types of Events are logged and what results they trigger. | [title] Targets [path] ZEN Master/ZEN Master User Guide/ Targets are internal logical entities used by ZEN to simplify management of Zixi resources. A target represents a destination to which a Channel is sent. The targets are configured once and assigned to the relevant Channels. ZEN Master supports the following types of targets: - [Adding HTTP Targets](docId\:Nth0upANEbiTHSEGzcKa3) - [Adding Zixi Pull Targets](docId:1tcWt65YZrnyWQiS7EAKA) - [Connecting an Unmanaged Pull Target](docId\:qeUKY1d_1HK3OGweHNJb7) - [Adding Zixi Push Targets](docId\:w7pgXYFK9SDyNQH_LRisd) - [Adding Zixi AWS MediaConnect Targets](docId\:E6rfLr5hPPecWd0nSWUOT) - [Adding RIST Targets](docId\:MrGwbni-X_Tm9L5upmkz8) - [Adding UDP/RTP Targets](docId\:UNZPMFAYf4TC32bChHPan) - [Adding RTMP Targets](docId\:DzT6L9b505pdRiJfVRBGs) - [Adding SRT Targets](docId\:f0RaMeGFw8RacR47wYlUO) - [Adding NDI Targets](docId\:BDr_Dnw7YhPENPVLIxbm3) - [Adding CDI Targets](docId\:erIUd6yOlaz45gXYmaj17) - [Adding ST 2110 JPEG XS Targets](docId\:bDwyCVtTK_1huG7KK34Ri) - [Adding MediaLive HTTP Targets](docId:9WNP5VijgMTixynTvNROw) - [Adding Entitlement Targets](docId\:kbKZ_oiim6ZTIPSUkE7Ab) - [Viewing Existing Targets](docId\:PBUhNBoOCrnR9k0j1O0Zh) [title] Adding UDP/RTP Targets [path] ZEN Master/ZEN Master User Guide/Targets/ The following procedure describes how to add a UDP/RTP Target in ZEN Master. In addition, an explanation of each of the configuration parameters is given in the table below. ## To add a new UDP/RTP Target: :::::WorkflowBlock :::WorkflowBlockItem In the main navigation, click **Targets**. ::: :::WorkflowBlockItem Click **+ Add**. The **Create New Target** window is displayed. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/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 **UDP/RTP**. The **Create New UDP/RTP Target** window is displayed. ![New UDP?RTP Target](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/OfSnwgHGV5-B_OpIdjil8_zm-create-udp-rtp-target.png) ::: :::WorkflowBlockItem In the **Info** section, in the **Name** field, enter a logical name for the **UDP/RTP** 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*, *AWS* *MediaConnect Flow, or MediaLive Channel*. ::: ::::WorkflowBlockItem 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 (ZEN Master Channel option), 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 **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 In the **TTL** field, specify the desired TTL value. ::: :::WorkflowBlockItem If your receiving device is configured for RTP, then select the **RTP **checkbox. ::: :::WorkflowBlockItem If you selected **RTP**, then 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 **Smoothing **\[ms] field, specify the size of the buffer in Milliseconds. A larger buffer enables smoother entry, however, it may influence the latency rate. The Smoothing feature uses a buffer to time packets according to the stream's clock, by creating a queue in the buffer, allowing smoother entry into the Broadcaster. This is useful when there are bursts in the rate in which the stream arrives. ::: :::WorkflowBlockItem If you want to Remultiplex or Pad the stream, check the box to reveal additional options: ![Remultiplex/Pad Options](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/lya9p1cTTax0CXPM1bIwR_zm-udp-rtp-targer-remux-options.png) ::: :::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 selected **Pad** for the **Remux mode**, In the **Remux Bitrate** field, enter the desired bitrate (in kbps) for the remuxed stream. ::: :::WorkflowBlockItem If you selected **Remux** for the **Remux mode**, edit the following fields as needed: - In the **Remux Bitrate** field, enter the desired bitrate (in kbps) for the remuxed stream (required). - In the **Remux PCR Interval **field, specify the frequency at which the Program Clock Reference is inserted into the output Transport stream. Default - 90 ms. - In the **Remux Buffer** field, specify the time allowed for remuxing. Default - 1000 ms. - Check **No NULL Packets** to discard NULL packets during remuxing. ::: :::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 **Transcoding Profile** field (MediaLive Channel option), select a transcoding profile from the drop-down menu. ::: :::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. ::: :::WorkflowBlockItem Select **Enable SCTE-35 Manipulation** to enable insertion and management of SCTE-35 messages (used typically to create ad breaks). ![SCTE-35 Settings](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/u_kJpVt3DRHk78LSBYop7-20260326-183853.png) ::: :::WorkflowBlockItem Select **Enable SCTE-35 Manipulation** to enable insertion and other 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 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. ![](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/GnOe2gYHeXgpZJ_FIwLk3_udp-target-advanced.png) ::: :::WorkflowBlockItem Click **Save**. ::: ::::: ## UDP/RTP 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. | | TTL | Specify the desired TTL value. | | RTP | If your receiving device is configured for RTP, select this checkbox. | | 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*. | | Smoothing \[ms] | The Smoothing feature uses a buffer to time packets according to the stream's clock, by creating a queue in the buffer, allowing smoother entry into the Broadcaster. This is useful when there are bursts in the rate in which the stream arrives. Specify the size of the buffer in Milliseconds. A larger buffer enables smoother entry, however, it may influence the latency rate. | | Transcoding Profile (MediaLive Channel option) | Select the desired transcoding profile from the drop-down menu. | | Remux Bitrate \[kbps] | Specify the desired bitrate (in kbps) for the remuxed stream. | | 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 | In the **External ID** field, enter the ID that is used when integrating ZEN Master with an external ESNI/ESAM server. For more detail, contact your Zixi representative. For more detail, contact your Zixi representative. | [title] Events [path] ZEN Master/ZEN Master User Guide/Logs/ Zen Master maintains a log of all events such as connections, errors, disconnections etc. Events for a specific resource (i.e. ZEC, Feeder, Broadcaster or Receiver) or ZEN Master entity (i.e. source, channel or target) can be viewed in the Events tab of the relevant entity. The complete list of events can be viewed on the **Logs > Events** screen. You can filter the results by several different parameters. ![Events Log](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/suvMx7H33YtIT-ZsR9Yit_image.png) The event descriptions include the following details: | **Parameter** | **Description** | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Actions** | For events that are not an OK state, display the following actions:
* **Open Incident** - creates an Incident, see [Creating an Incident Manually](docId\:aomjabSyzYLzY3GQ4zH8o) . * **Configure** - opens the Edit Rule screen for the Events Profile that generated the event. From this panel, you can optionally modify the Event Profile. You can overwrite the existing Events Profile (which will apply to to all objects using the profile) or save the changes as a new Events Profile: - **To overwrite the existing profile** - perform the modifications (see [Configuring Events Profiles](docId\:CWshWpVMDch_ryL86IMTS) for more details), under **Update Current Profile**, select **Overwrite**, click **Update Current Profile**. - **To create a new profile** - perform the modifications (see [Configuring Events Profiles](docId\:CWshWpVMDch_ryL86IMTS) for more details), under **Update Current Profile**, select **Create New**, click **Update Current Profile**. | | **Date/Time** | The date and time of the event. | | **Event Type Indicator** | Event types are:
* Red (Error) – an error in the system. * Yellow (Warning) – an event that raises concern about the performance of the system. * Blue (Info) – a change in the system that does not raise concern and user actions. * Green (OK) - a procedure was implemented effectively. * Gray (System activity) – an activity was done in the system, such as creating or deleting a system entity. | | **Message** | A brief description of the event. For error events, specifies the cause of the error and suggests corrective actions. | | **Object** | Shows the type of object (e.g. Broadcaster Cluster, Adaptive Channel, Source, etc.) followed by the name of the specific instance of the relevant object. | | **Rule** | The name of the event profile rule that generated this event, see [Configuring Events Profiles](docId\:CWshWpVMDch_ryL86IMTS) . | - [Filtering Events](docId\:Y3PKViSEp0WSfz7SIjx8q) - [Log Events](docId:1T4tHq4g0xaSWNG_TuArL) [title] Viewing Existing PID Mapping Profiles [path] ZEN Master/ZEN Master User Guide/Transformations/PID Mapping Profiles/ The PID Mapping Profiles screen displays all existing PID Mapping profiles, and information about the configuration of each profile. ![PID Mapping Profiles screen](https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/ofW970sHP1qWrED9kvkiA_image.png) When a PID Mapping profile is selected, the list pane is minimized and detailed info about the selected profile, divided into sections, is shown on the right of the screen. ::Image[]{src="https://archbee-image-uploads.s3.amazonaws.com/mzxtTQEvCNIdUNgF2kuwJ/8MEvtiuFIAJBx-S0Tyzp8_image.png" size="80" width="1164" height="823" position="center" alt="PID Mapping profile details" showCaption="false"} When a profile is selected, the following sections are shown in the Info pane: - **Details** - configuration details of the PID Mapping profile. - **Rules** - the rules that apply to the selected profile. - **Sources** - the Sources The main display includes the following data and actions for each profile: | **Parameter** | **Description** | | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Selection Checkbox | Select one or more profiles and perform batch actions on all selected profiles. Available actions are:
* **Delete All** - deletes the profile configuration for the selected profile.