--- title: ZEN MASTER April 2024 RELEASE NOTES slug: zen-master-april-2024-release-notes docTags: createdAt: 2025-03-21T19:00:41.214Z --- 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.