2.8 ToolsOnAir Network Communication (v2.5)

just:out, just:connect and just:live/just:play can be installed on one or multiple machines. In both scenarios they communicate with each other via network communication protocols. When the user interacts with the just:live/just:play user interface, this information is sent to just:connect – stored there – and then sent to just:out so it can be executed and rendered by the engine.

The following figure applies to just:live and just:play. For simplicity only just:play is shown in this figure.

Network Latency & Performance

The latency of the Playout system highly depends on the speed and load of the network. For example, clicking the Jump to Next button can be executed in less than a second – but it can also take a few seconds if the network is under heavy load or improperly configured. Because of this we strongly recommend using a dedicated network for communication and a second network for the data transfer.

If the communication between a just:live/just:play user interface and just:connect is interrupted for more than two seconds, the interface will quit and restart automatically, showing the login window with a warning. This mechanism avoids that the user makes any changes which would never be executed by the engine.

Please contact your local network administrator to solve the underlying network related issue. The ToolsOnAir support team will not be able to help in this case.


→ Use the sidebar to navigate.