ZEN MASTER July 2019 RELEASE NOTES

the following updates will be pushed to zen master on july 9, 2019 running zixi broadcasters on google cloud platform zen master now supports broadcaster clusters on google cloud platform (gcp) follow the steps below to configure zen master to use gcp and launch broadcasters on gcp login to your gcp service accounts console at https //console cloud google com/iam admin/serviceaccounts and select your project and click 'create service account' name the account, e g 'zen master' and click 'create' click 'create key' select the 'json' type and click 'create' save the downloaded file and click 'close' next, configure zen master to use the gcp service account open the gcp configuration page under the settings menu and click 'add account' name the account and upload the json file downloaded from gcp click 'save' to confirm to launch broadcasters on gcp in zen master, add a new broadcaster cluster and select the gcp scaling account that you just added after clicking ‘continue’, select the region, zones, network and machine type if you will be using the broadcaster for transcoding, also select the gpu type capabilities of the tesla k80 and p100 can be found at https //developer nvidia com/video encode decode gpu support matrix after completing the other required fields, you will now be able to launch broadcasters on gcp using azure blob storage for hls and dash zen master now supports storing hls and dash manifests and segments on azure blob storage, to be used as an origin for cdn delivery follow the steps below to configure zen master to use azure blob storage if you have not already linked an azure subscription to zen master, follow the detailed steps shown under on the microsoft azure page under settings if you already have a linked azure subscription or after linking the azure subscription, you simply need to add a new role assignment for azure blob storage open access control (iam) under your azure subscription, select the ‘role assignments’ tab, and select ‘add role assignment’ select ‘storage blob data contributor’ and then select the same service principal that you created when you originally linked zen master to the azure subscription click ‘save’ and you will see that service principal under ‘storage blob data contributor’ next, when you create an http target you can select azure that the type and select the appropriate azure account linked to zen master rtt and jitter history on targets round trip time (rtt) and jitter is now available on the network graph in the history tab for targets minor improvements and bug fixes • improved error message when a broadcaster configured with zen master authorization that is not working properly previously displayed “authorization” error in a broadcaster status; will now report the exact error • transcode profiles can now be cloned • advanced transcode profile settings are now displayed details tab • traceroutes history is now off by default and needs to be manually enabled in source/targets advanced settings • added type to sources table and filter buttons by type • improved aws scaling broadcaster names aws broadcaster now follow the same naming convention as gcp/azure {cluster name} {unique id} • support floating point hls/dash segment duration configurations both as cluster default and per adaptive channel • fixed version error message when transcoding license is missing • fixed issue where import key does not have the key field as mandatory • fixed invalid fec row and col error message • fixed issue with usage reports total not matching details • fixed issue with usage report not matching actual usage • fixed issue with graphs and traceroute menu refreshing periodically for no reason • fixed issue where it was impossible to delete a user that had custom notifications configured • fixed issue where view only user does not show feeder/broadcaster logo on source • fixed issue where view only user does not display all components in channel view • now ignore unaligned pts errors on transcoded channels as they are not relevant • fixed error when adding receiver with same named outputs