ZEN MASTER DECEMBER 2018 RELEASE NOTES

the following updates were pushed to zen master on december 5, 2018 creating new source from transcoded source zen master now allows you to create a new source from a transcode of an existing source a typical use case for this feature would be to create a rendition of a live stream suitable, in terms of bitrate and codec, for publishing to youtube live or facebook live via rtmp for the rtmp example, start by adding a new source and select the type “transcoded” define the name and other parameters for the source and choose one of your pre existing transcoding profiles next, define a new pass through channel using the source that you just created next, create a new rtmp target finally, select the channel you just created for the new target and fill in the publishing details for the rtmp server hitless failover configuration for receivers hitless failover provides seamless switching between multiple binary identical source streams previously, zen master allowed configuration of hitless failover between multiple sources feeding a channel on a broadcaster cluster zen master now allows for configuration of hitless failover on receiver endpoints to enable hitless failover, add a new source and select hitless failover define multiple identical sources for this new hitless failover source create a new passthrough channel with the new hitless failover source and then add a new target and select pull select active/active in the pull target dialog to enable hitless failover if the channel has two sources defined, the receiver will pull both sources of the channel and combine them using hitless failover, starting with v12 2 receivers, or it will configure two inputs for one output on older receivers v12 broadcaster is required for hitless failover bitrates calculation for hls/dash manifest when defining transcode profiles for a transcoded channel, the bitrate value that will be stated in the hls/dash manifest file for each profile must be calculated in the case where the video or audio is passed through and not transcoded, zen master does not know the bitrate value and thus cannot calculate the value to include in the manifest the user will be required to enter a bitrate value note that the bitrate values in the manifest are used by playback devices to switch to the appropriate stream rendition based on current network bandwidth so it is important to enter an accurate value when both the video and audio are transcoded, zen master calculates the bitrate for the manifest file automatically the calculation is the video bitrate plus audio bitrate plus a small amount added to account for streaming overhead minor improvements and bug fixes • more detailed transcoding error reporting including specific error messages instead of a generic "transcoding error" • presentation time stamp (pts) reported on scte35 cue in events • verify that the broadcaster license supports virtual machines when launching on aws • 32kbs and 64 kbps options now available for transcoding audio bitrate • added option to select nic on feeders and receivers • added pagination support for channels, targets and sources in the api • fixed an issue rewriting ports config on the broadcaster tunnel connection • fixed an issue preventing the add pull target dialog from closing without an error • fixed pull targets requiring up to one minute to connect when enabling a channel • fixed issue with unintended outputs being created on the broadcaster when using pull targets • fixed issue with the full warning message not showing in object details in some cases • fixed missing source dtls/encryption icon • fixed issue with deleting remote access devices • fixed issue with attempting to configure dtls on v10 feeders, broadcasters, and receivers where dtls is not supported