ZEN MASTER February 2019 RELEASE NOTES

The following updates were pushed to ZEN Master on February 4, 2019.

Content Quality Analytics (CQA) can now be enabled and disabled when creating a new source or editing an existing source. By default, CQA is enabled when a new source is created.



The user can now select which panels are displayed on the dashboard page. The settings are preserved in local storage and will be preserved on the same browser after logout and login.



Previously ZEN Master only allowed AWS g3s.xlarge and g3.4xlarge NVIDIA GPU instances to be selected for scaling Broadcaster clusters. These instance types do not support HEVC decoding. Now, ZEN Master also allows p3.2xlarge NVIDIA GPU instances to be selected; this instance type supports both HEVC decoding and encoding.



Under the Details tab, ZEN Master now allows you to play the stream for each rendition of an adaptive transcoded channel.



Under the Details tab, ZEN Master now provides a tooltip showing details of the transcode profile.

Pull targets can now be configured with multiple Receiver/Broadcaster outputs.



When adding a Broadcaster to a manual scaling cluster, there is no longer a length restriction on the name. Also, instead of being locked after a Broadcaster is created, the Broadcaster name can now be edited any time.





Instead of being locked after a cluster is created, AWS cluster subnets can now be updated any time.



The AWS IAM policy was updated to allow the AWS Autoscaling activity log to be merged into the ZEN Master events log. The user must update their IAM policy in AWS to take advantage of this change.



• ZEN Master now monitors the Authorization configuration status on v12.3.32764+ Broadcasters • Fixed history graphs not updating when selecting a different object • Invalid/expired license will no longer prevent editing of an AWS cluster • Fixed licenses page becoming unresponsive if user adds an invalid license key • Fixed Broadcaster upgrades that were not working through ZEN Master tunnels • Worked around Akamai dot (.) requirement to support publishing adaptive channels to Akamai; requires creating new sources • Fixed http target monitoring throwing errors if target path ends in a master playlist file, e.g. https://zixi-cloudstream.s3.amazonaws.com/woooozer/master.m3u8 • Removed extraneous information in event Log reports when there are warnings in the log