Adding Failover Channels (Deprecated)

failover channels are deprecated deprecated no additional features will be added, and they will be removed from zen master in april 2026 use a adding a source – failover docid\ fzrb10jkuzainyt8gfnk0 with a adding a pass through channel docid\ hr8tezamw7vqrdy yfykc instead live events docid\ tgt1qo5h jhljyi9bxd2x have also been updated to use failover sources rather than channels the failover channel has been specifically designed for the live events feature as part of this channel, you can select multiple sources and define which one is the slate source, and from the remaining selected channels which one is the preferred (primary) and which one is not preferred (secondary) failover channels are like pass through channels in that they do not involve any actual processing to the stream, but rather creates redundancy by defining parallel streams from multiple sources as a single entity this ensures that if one source becomes inactive the stream will be automatically transmitted from the parallel source how priorities influence the failover process a failover occurs when a current source has a malfunction and is no longer able to stream or that a high priority source that went into error has resumed streaming this means that the priority level hierarchy can influence on when a failover occurs, and if it occurs, to which of the sources it will failover to in a failover channel the priority is as follows preferred – high non preferred – medium slate – low so, the channel will play the preferred source by default if the preferred source becomes unavailable, it will failover to a non preferred stream (if one exists) if there is no non preferred stream of it becomes unavailable (while the preferred stream is still unavailable), zen master will failover to the slate how the failover process is overridden by a live event the failover behavior can be overridden by live event configuration there are some stages of the event, where the slate is the source that will be streamed for example, in pre live the live event is configured to select the slate source in the live event, it will automatically select the preferred source and if the preferred source is not available, it will fall back to a non preferred source if neither the non preferred nor a preferred source is available, it will fall back to a slate for more information, see live events https //zixidocumentation atlassian net/wiki/spaces/zmug/pages/4778557445/live+events the following procedure describes how to add a failover channel in zen master in addition, an explanation of each of the configuration parameters is given in the table below to add a failover channel in the main navigation, click channels click + add the create new channel selection menu is displayed create new channel selection menu click on failover the create new failover channel window is displayed in the info section, in the name field, enter a logical name for the channel in the tags field, select one or more of the predefined tags from the drop down list tags are used for access control by selecting an tag, you are relating this channel to that tag tags are associated with certain roles (through the users & roles screen), and roles, in turn, are associated with users and user groups if you would like to create a new tag, see creating a tag docid\ ypm9tw81ap6nq8stkv4rd in the events configuration profile field, select from the dropdown list the profile that you would like to apply to this channel by default, the default profile is applied events profiles consist of a series of rules that determine precisely how various types of events are logged and what results they trigger in the input section, in the processing cluster field, select from the drop down list one of the channel processing clusters that has been configured in zen master the selected cluster will be used to process this channel if the source does not exist in the cluster, then the cluster will pull the source automatically in the target broadcaster/s field, select your broadcaster preference either select a specific broadcaster to be used or specify your preference for using primary vs backup broadcasters, options are prefer primary broadcasters , primary broadcasters only , backup broadcasters only or prefer backup broadcasters if you want to configure an alternative path for disaster recovery, in the alternative channel (disaster recovery) field, select the channel that will be used as the alternative path for more details, see disaster recovery (alternative path) docid\ poo4zs1 zjra1sndylqe0 in the sources section, add one or more sources to the channel and specify whether they should be a preferred source (select the preferred checkbox), a non preferred source (do not select anything) or a slate source (select the slate checkbox this is done as follows find the source that you would like to add either by scrolling through the list of available sources or by entering a search word into the filter if the source that you would like to add is not yet configured in zen master, see sources https //zixidocumentation atlassian net/wiki/spaces/zmug/pages/412057659/sources add a source by clicking the + button next to the source selected sources are shown above the filter box do one of the following select the preferred checkbox if you would like to designate the source as preferred source select the slate checkbox if you would like to designate the source as a slate do not select any checkbox if you would like to designate the source as a non preferred source repeat the above procedure for each source that you would like to add to the channel if you would like to remove the selected secondary source, click on the ‘ x ’ in the secondary source textbox all access tags that are assigned to the selected sources are added by default to the channel if you would like to apply a pid mapping profile to this channel, then in the pid mapping profile field, select the desired profile from the drop down list in the initial state section, select the disabled checkbox if you would like to disable this channel upon initial configuration select the muted checkbox if you would like to disable error/recovery notifications for this channel upon initial configuration you can enable/unmute the channel at any time under the source section, select the automatically switch to preferred source , if you want the stream to switch automatically to the configured preferred source this feature requires broadcaster version 17 or newer for failover mode , select the desired mode for failing over/merging the streams options are stream switch – zen master treats the streams as different and does not try to merge them if packets are missing from one stream, zen master will switch to the alternate stream if the payload is not binary identical it will fall back to stream switch smpte 2022 7 hitless merge if the sources use rtp, and the rtp headers were maintained, zixi can use the smpte 2022 7 to compare and merge the two streams this option uses the sequence and the timestamp in the packets to compare which packets are missing, providing optimal results content hitless merge if the sources do not have rtp headers, zixi will merge the streams using the mpeg ts payload content itself this method uses zixi's patented dna like sequencing algorithm to fill in the missing packets if you have selected the content hitless merge or the smpte 2022 7 hitless merge option, in the merge search window \[ms] field, enter the time frame for which the system will search for the relevant packets in a matching stream (default 1000) if there is a latency difference between the streams, the search window value should be higher than the latency difference between the streams if merge mode is disabled, the time period specified in the search window field defines how long the stream will wait for packet before attempting to switch between streams if you have selected the stream switch option, in the zero bitrate/offline detection window \[ms] field, enter the time frame with zero bitrate or offline state after which the system will perform the failoverbox failover rules allow you to set rules for what type of error and how often they occur to change to the failover stream if you would like to change the rules, use the following procedure (supported for broadcasters v15+) select the checkbox next to the error for which you would like to change the error rules options are p1 transport errors, frozen video, blank picture, silent audio, and low bitrate ( zero bitrate/offline is set as selected on a fixed basis ) set the parameters for sample duration the duration (in seconds) of the window of each sample samples the number of samples that you check in each sampling samples threshold the number of error results (within a sampling) that trigger the failover pid scopes the rule to a specific pid in the transport stream (e g , if you have multiple audio programs it will only apply the rule to the specified one) for example, if you set sample duration=10, samples=6, samples threshold=2 then if during a 60 second time period an error occurs during 2 out of the 6 ten second windows, failover will be triggered when the payload is binary identical failover rules are ignored in favor of hitless merge of the sources mentioned pid(s) must be present on all participating streams broadcasters older than version 15 only support zero bitrate/offline failover broadcasters older than version 16 6 do not support pid based rules if you would like to enable content analysis (cqa), verify that the enable content analysis checkbox is selected (default) it is generally recommended to enable content analysis unless it is causing technical problems if content analysis is disabled, the system won't detect errors in the video and audio content of the stream and won't generate warnings for such events even when content analysis is disabled the system will still detect tr101 errors in the stream additional scte 35 options are available when you expand the scte 35 manipulation section scte 35 manipulation here you can enable scte 35 insertion set the scte 35 pid in which the messages will be inserted remove any existing scte 35 messages from the stream replace any existing scte 35 messages with null under error concealment , click the enable error concealment checkbox to enable the following error concealment mechanisms that can correct transport stream for downstream irds continuous timeline corrects errors that are related to timeline jumps in the source this mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input replace frames if there are frames with cc errors, it replaces them with skip frames this solves issues such as an ird that lost synchronization when it received broken frames this mechanism also creates a variant of the input (doubling the input) renumber cc the continuity counter is part of the ts encapsulation when there are cc errors in tr101 analysis it means that the counter has a gap due to lost frames this mechanism can re write the cc counter for the downstream devices, so they will see a continuous increase of the counter delay enter the delay that the error concealment adds to the stream in miliseconds error concealment needs to buffer the stream to analyze it one second is a reasonable value lower values may cause the error concealment to not be able to fix some of the frames cbr padding enter a value for the rate at which padding will be added to maintain a specific output transport bitrate pcr interval select the frequency at which program clock reference is inserted into the outputs transport stream options include atsc standard 100 ms dvb standard 40 ms if you would like to adjust the advanced settings, click advanced the advanced settings are displayed if you would like to track usage for this channel, enter your billing code details see billing codes https //zixidocumentation atlassian net/wiki/spaces/117/pages/4887944193/billing+codes click save failover channel configuration parameters table parameter description info name specify a name for the transcoded channel in zen master tags select one or more of the predefined tags from the drop down list tags are used for access control by selecting an tag, you are relating this channel to that tag tags are associated with certain roles (through the users & roles screen), and roles, in turn, are associated with users and user groups if you would like to create a new tag, see creating a tag docid\ ypm9tw81ap6nq8stkv4rd events configuration profile select from the dropdown list the profile that you would like to apply to this channel by default, the default profile is applied note events profiles consist of a series of rules that determine precisely how various types of events are logged and what results they trigger input processing cluster select from the drop down list one of the channel processing clusters that has been configured in zen master the selected cluster will be used to process this channel note if the source does not exist in the cluster, then the cluster will pull the source automatically target broadcaster/s either select a specific broadcaster to be used or specify your preference for using primary vs backup broadcasters, options are prefer primary broadcasters , primary broadcasters only , backup broadcasters only or prefer backup broadcasters alternative channel (disaster recovery) enables reverting an entire path after the source (i e , channel/broadcaster to the target) to go through an alternative path, which is usually hosted on an alternative cloud/region the redirection to the alternative path is manual so, in case of a fault, if there is no time to troubleshoot a problem, this mechanism allows the user to select the feed that has an issue, click a button and revert the stream to go through a pre configured alternative path for example, if you have a channel and a broadcaster on gcp and a secondary channel and broadcaster on azure if something goes wrong with the gcp path, you can click the go to alternative button and failover everything to azure sources add one or more sources to the channel by clicking the + button next to the source and select the checkboxes if you would like to designate them as a preferred source or as a slate if you would like to designate the source as non preferred, leave the checkboxes empty if you would like to remove a source from the channel, click on the button next to the source pid mapping profile if you would like to apply a pid mapping profile to this source, then select the desired profile from the dropdown list initial state disabled select this checkbox if you would like to disable this channel upon initial configuration muted select this checkbox if you would like to disable error/recovery notifications for this channel upon initial configuration source automatically switch to preferred source if the primary fails and it switches over to the secondary and later the primary returns, if the box is selected, it will switch back to the primary even if the secondary is good however if it it is not selected, it will stay on the secondary until the secondary is no longer available failover mode select the desired mode for failing over/merging the streams options are stream switch – zen master treats the streams as different and does not try to merge them if packets are missing from one stream, zen master will switch to the alternate stream if the payload is not binary identical it will fall back to stream switch smpte 2022 7 hitless merge if the sources use rtp, and the rtp headers were maintained, zixi can use the smpte 2022 7 to compare and merge the two streams this option uses the sequence and the timestamp in the packets to compare which packets are missing, providing optimal results content hitless merge if the sources do not have rtp headers, zixi will merge the streams using the mpeg ts payload content itself this method uses zixi's patented dna like sequencing algorithm to fill in the missing packets zero bitrate/offline detection window \[ms] specify the time frame for which the system will search for the relevant packets in a matching stream (default 1000) note if there is a latency difference between the streams, the search window value should be higher than the latency difference between the streams failover rules failover rules allow you to set rules for what type of error and how often they occur to change to the failover stream if you would like to change the rules, use the following procedure (supported for broadcasters v15+) select the checkbox next to the error for which you would like to change the error rules options are p1 transport errors , frozen video , blank picture, silent audio, and low bitrate set the parameters for sample duration – the duration (in seconds) of the window of each sample samples – the number of samples that you check in each sampling samples threshold – the number of error results (within a sampling) that trigger the failover pid scopes the rule to a specific pid in the transport stream (e g , if you have multiple audio programs it will only apply the rule to the specified one) note for example, if you set sample duration=10, samples=6, samples threshold=2 then if during a 60 second time period an error occurs during 2 out of the 6 ten second windows, failover will be triggered enable content analysis if you would like to enable content analysis (cqa), verify that this checkbox is selected (default) note it is generally recommended to enable content analysis unless it is causing technical problems if content analysis is disabled, the system won’t detect errors in the video and audio content of the stream and won’t generate warnings for such events even when content analysis is disabled the system will still detect tr101 errors in the stream scte 35 manipulation enable scte 35 insertion select chackbox to enable scte 35 insertion scte 35 pid set the scte 35 pid in which the messages will be inserted remove existing scte 35 remove any existing scte 35 messages from the stream replace with null replace any existing scte 35 messages with null error concealment enable error concealment select this checkbox to enable the error concealment mechanisms listed below to correct transport stream for downstream irds continuous timeline corrects errors that are related to timeline jumps in the source this mechanism will normalize the timeline by creating a variant of the input (the input is doubled) and normalizing the timeline of the doubled input replace frames if there are frames with cc errors, it replaces them with skip frames this solves issues such as an ird that lost synchronization when it received broken frames this mechanism also creates a variant of the input (doubling the input) renumber cc the continuity counter is part of the ts encapsulation when there are cc errors in tr101 analysis it means that the counter has a gap due to lost frames this mechanism can re write the cc counter for the downstream devices, so they will see a continuous increase of the counter delay (ms) enter the delay that the error concealment adds to the stream in miliseconds error concealment needs to buffer the stream to analyze it one second is a reasonable value lower values may cause the error concealment to not be able to fix some of the frames cbr padding (kbps) enter a value for the rate at which padding will be added to maintain a specific output transport bitrate pcr interval (ms) select the frequency at which program clock reference is inserted into the outputs transport stream options include atsc standard 100 ms dvb standard 40 ms advanced billing codes if you would like to track usage for this source, enter your billing code details, see billing codes docid\ lalxj n928tegcpdpbirj (supported for broadcasters v14 8+) billing password enter the password that corresponds to this billing code external id the id that is used when integrating zen master with an external esni/esam server for more detail, contact your zixi representative