ZEN Master 18 November 2025 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 api keys 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 all existing api keys, those created prior to the november 18th update, will expire 1 year from the release, on november 18th 2026 for new keys created after the release, the default and max expiration is 1 year see configuring api keys docid\ y5vwl7q34graoprjlhzui create new api key live events 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 the live events ui is updated to work with failover sources to support failover sources, two new api parameters are introduced new failover source ids for post/put new failoversources for get/responses 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 deprecated failover channel ids deprecated failoverchannels see adding a live event docid\ sfglqbra 439cjrutduvb failover channels deprecation in the august 18th release of zen master, zixi ceased further duplicative development of failover channels and transitioned to focusing on failover sources existing workflows and api endpoints remain until the planned completion in april 2026 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 we will begin the process of transitioning live events to use failover sources directly, and associated ui updates in the next release see adding failover channels (deprecated) docid\ wbnr0r5h8tkjdmr 2trrd esni ui the november 18th release introduces the monitoring tools for the esni scheduling back end the ui is available when the esni server module of zen master is enabled and configured speak to your technical representative to arrange a demo see monitoring in zen master docid\ zenkylmpoxgyc7zoh5jv1 esni schedule change tracking will now record the initial creation of the object in order to store the initial configuration applie only to objects created after this release see change tracking docid\ hc kmarjxkviaz69v6ivv change tracking support private ip only for aws cluster administration when selecting a vpc with a nat gateway there is no longer a need to attach a public ipv4 to instances for administration this has multiple potential benefits reduces public ipv4 costs allows the use of a second nic with a public ip for dpdk server without the need to allocate an additional elastic ip potential security benefits see adding a broadcaster cluster managed docid 6slx4td zkr2xfho8qz6 ‘private ip’ support for zixi push sources ‘private ip’ is now supported for zixi push sources between systems within zen master note if checked, only the specific broadcasters as selection options for ‘target broadcaster’ the resulting ‘private ip’ will be displayed in the source details see adding a zixi source – broadcaster docid\ vunnbbukyiybi9eycrx3c use private ip zixi push source broadcaster upgrade detailed dialog continuing progress for broadcaster version tools within zen master, the broadcaster dialog is once again available via the broadcaster’s top right menu as of the november release the “install version” option provides the more details broadcaster installation dialog broadcaster upgrade dialog broadcaster active metrics current, and target version selection system architecture confirmation details the ‘active objects’ table allows users to disable/mute objects before upgrading “error message’ panel the ‘install’ action button ‘install’ will upload the selected installer to the broadcaster and initiate the upgrade the installation script runs as before, and zen masters standard monitoring cycle continues to monitor during the process pre/post installation objects status shown side by side object status before/after upgrade as the installation begins the ‘initial status’ column records an historical snapshot of the pre install object 2 3 4 status the current object ‘status’ column continues to monitor the objects a users can therefore compare the original and current status of an object as the upgrade progresses and connections are restored 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 upgrade completion, error messages, etc will appear in the gui as the installation progresses, and be logged 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 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 see actions on broadcasters docid\ b1y6nshfzcuwcd0 gspg automatic recovery all zm sources/channels/targets on aws broadcasters that get terminated/restarted by aws 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 a subset of zen master managed configurations exists locally in the instance, such as those of zixi pull inputs, udp outputs, etc 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 see zixi and aws docid\ b capfgytnyegrttsssm1 new multi select confirmation dialogs and tools dialogs confirming changes on multiple objects now display the list of objects and the result of the action, successful or otherwise, for each object when performing a group action, such as muting many sources at once, the rearchitected table provides improved clarity and filtering for object management see actions on sources docid 7ridbifg03iggiwyl9e8x confirm actions on multiple objects improvements and changes multi edit forms now support updating cluster/target broadcaster users can update the ‘processing cluster’ and ‘target broadcaster’ for multiple channels at the same time zen master diagrams can now be exported as png files full screen mode for tabs/panels in details view enhances ability to easily monitor singular tabs and details screens in nocs etc zixi pull sources now support alternative hosts for disaster recovery configurations involving the alt host mechanism, pull sources are now supported it is now possible to stop/start aws broadcasters without deleting them individual broadcasters in aws clusters can now be disabled and enabled note this feature requires an iam policy update live events can now be ordered by countdown support for new aws instance types options now include instances from the c8gn family, as well as c7gn 4xlarge added an event log when objects are put into flapping remote ip is now logged on connection/reconnection for sources state “automatically switch to preferred source” is now the default for new failover sources opening a link to an object that doesn't exist will now show a ‘404 landing’ page further optimizations to channel/target list page initial loading times added webvtt positioning to transcoded/adaptive channels in the channel advanced section, the controls appear when ‘convert cea 708 to webtvtt’ and ‘custom webvtt positioning’ are both enabled see adding transcoded channels docid\ xwf mfnvra5e3jql2ymju adding adaptive channels docid\ rkvnzf tft8vgnzzsb79b added playback (vlc/webrtc) buttons to thumbnail grids vlc playback option is available in the grid element hover over see viewing thumbnail grid display docid\ alrdekalu0zyp5ifvaayo added used packet counters to failover source diagrams used packets failover sources removed the zen master generated id’s from tag multiviewer source implementation exposed adaptive fec controls on zixi sources/targets see the docs on adding zixi sources and targets added sdt table to existing stream analyzer 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