--- title: ZEN Master 17 Feb 2026 Release slug: zen-master-17-feb-2026-release docTags: createdAt: 2026-02-16T16:36:26.587Z --- 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://api.archbee.com/api/optimize/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://api.archbee.com/api/optimize/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://api.archbee.com/api/optimize/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://api.archbee.com/api/optimize/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://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/NCYdIUx7DFZcCQEsNEaQV_.blob) ### SCTE-35 Modification Rule Simulator. Once created, SCTE-35 modification rules can be tested directly within the ZEN Master interface. ![](https://api.archbee.com/api/optimize/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://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/uubQ2K-fiHce5HtQaFa5g_.blob) ![](https://api.archbee.com/api/optimize/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://api.archbee.com/api/optimize/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://api.archbee.com/api/optimize/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://api.archbee.com/api/optimize/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://api.archbee.com/api/optimize/mzxtTQEvCNIdUNgF2kuwJ/mheZHPiD5NKrripAdQc96_.blob) ![](https://api.archbee.com/api/optimize/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://api.archbee.com/api/optimize/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://api.archbee.com/api/optimize/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** :::