This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Network Sync

    Network Sync lets several mAirList instances in the same local network exchange status information and commands. Its main uses are:

    • ON AIR synchronization: In a setup with several studios (or a studio and an automation PC), only one instance should be ON AIR at a time. When one instance goes ON AIR, all other instances of the same group automatically go OFF AIR.
    • Command forwarding: Remote control commands can be sent from one instance to the others, e.g. to start a player in another studio from a cartwall button.

    The instances communicate via UDP broadcasts, so no central server is required. All instances must be in the same network segment, and use the same UDP port.

    Configuration

    Network Sync is configured on the Advanced → Network Sync page of the configuration. This page is also available in the live configuration (mAirList Control Panel).

    Transports

    • UDP Broadcast: Check Enable to send and receive Network Sync messages via UDP broadcast (enabled by default). Enter the UDP Port (default 9393), and optionally the Bind IP, i.e. the local IP address(es) to use, separated by commas. Leave empty to use all network interfaces.

    ON AIR Sync

    Check Enable ON AIR synchronization to enable this feature, and set up the identification of this instance:

    • Client ID: The name of this instance in the network. Leave empty to use the computer name.
    • Group ID: Only instances with the same group ID are synchronized with each other. Use different group IDs if you run several independent setups (e.g. for different stations) in the same network.
    • Default Client: The client ID of the instance that should go ON AIR automatically when another instance of the group is switched OFF AIR, e.g. the automation PC that takes over when the live studio goes off air. Leave empty to disable this behavior.

    When ON AIR synchronization is enabled:

    • Whenever this instance goes ON AIR, all other instances of the same group go OFF AIR.
    • When this instance is switched OFF AIR (manually, by a command etc., but not by Network Sync itself), and a default client is configured, the default client is switched ON AIR, so that the program is never left without an ON AIR instance.

    Commands

    • Prefix for commands to be forwarded to network: Commands that start with this prefix (followed by a space) are not executed locally, but sent to all other instances, with the prefix removed. The default prefix is NETWORK.
    • Prefixes for commands received from network: Enter one prefix per line. A command received from the network is only executed if it starts with one of these prefixes (followed by a space); the prefix is removed before the command is executed. All other commands are ignored.

    For example, to address the instance in studio 2, enter STUDIO2 as an incoming prefix on that instance. Then, on any other instance, execute:

    NETWORK STUDIO2 PLAYER 1-1 START

    The command STUDIO2 PLAYER 1-1 START is broadcast to the network, and the instance in studio 2 executes PLAYER 1-1 START. You can configure several incoming prefixes per instance, e.g. an individual prefix and a common one such as ALL, to address all instances at once.