--- title: ZEN Master 18 November 2025 Release Notes slug: zen-master-18-november-2025-release-notes docTags: createdAt: 2025-11-05T19:44:22.643Z --- 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://api.archbee.com/api/optimize/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://api.archbee.com/api/optimize/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.