Actions on Broadcasters

the top of the info pane includes buttons for taking the following actions on the selected broadcaster action menu mute/unmute – disables/activates notification for error/recovery events set the date and time when the mute will automatically be cleared by clicking on the down arrow and selecting mute until disable – disables the broadcaster when disabling a broadcaster, you can migrate the existing sources and channels to a different broadcaster by selecting the migrate sources and channels to different broadcaster(s) option and then selecting the broadcaster(s) preference on which the streams will be hosted in the target broadcaster/s drop down menu options are prefer primary broadcasters , primary broadcasters only , backup broadcasters only or prefer backup broadcasters the selected target broadcaster option will override the original target broadcaster option of the source/channel, however if the source/channel is configured to a specific/named broadcaster target it will not participate in the migration process similarly, if the selected setting is backup broadcasters only and the broadcaster that is being disabled is the only backup broadcaster in the cluster, the migration will not be possible edit – enables you to edit the broadcaster configuration refresh – refreshes the screen open broadcaster – click to access the broadcaster ui set maintenance – click to turn on maintenance mode, which prevents new streams from being assigned to this broadcaster config click to view instructions on how to configure the broadcaster to connect to zen master install version click to upgrade/downgrade the broadcaster's software version to install the new version in the new broadcaster version field, select the new version to install private version are indicated with a lock icon in the architechture field, make sure that the correct server architecture is selected click install see additional information in the section below delete – deletes the broadcaster when deleting a broadcaster, you can migrate the existing streams to a different broadcaster by selecting the migrate sources and channels to different broadcaster(s) option and then selecting the broadcaster(s) preference on which the streams will be hosted in the target broadcaster/s drop down menu options are prefer primary broadcasters , primary broadcasters only , backup broadcasters only or prefer backup broadcasters the selected target broadcaster option will override the original target broadcaster option of the source/channel, however if the source/channel is configured to a specific/named broadcaster target it will not participate in the migration process similarly, if the selected setting is backup broadcasters only and the broadcaster that is being deleted is the only backup broadcaster in the cluster, the migration will not be possible widgets/tabs view installing a new broadcaster version using zen master when you click install version in the action dropdown, the following screen opens install new version ui note that you are shown the current broadcaster version, along with a dropdown menu of other available versions, with the latest on top also note the list of objects on the broadcaster, which we will return to shortly when choose a new version and click install, in most cases zen master will handle the new installation completely, and there will be no need for you to open the broadcaster ui in some cases this will not succeed, because upgrading from some older versions (from 16 x to 18 x or 19 x, for example) requires some changes on the server or container that the broadcaster runs on that zen master cannot make in these cases, you will see a red error message explaining the issue note also that once installation starts, the objects list will change to display both initial status and status this will help you ensure that sources and targets restart properly after installation of the new version (or in some cases, that the new version fixes an issue with a source or target) note that object status does not update automatically as soon as the installation is complete, but rather updates every 30 seconds automatically also note the indication of the broadcaster the object is operating on if this broadcaster is part of cluster with failover, a source might have been redirected to another broadcaster during the update when the installation of a new broadcaster version completes successfully, a green success message will appear success message