ZEN MASTER July 2020 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