2.6 ToolsOnAir Network Communication (v3.0)

All ToolsOnAir components are highly dependant on a properly configured and stable network connection. Please contact your network administrator or local dealer if you need help.

Just Out, Just Connect and Just Control 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 Control 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.

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 user interface and just:connect is interrupted for more than two seconds, the interface will close and automatically fall back to the multi viewer interface, showing "NO CONNECTION". This mechanism avoids that the user makes any changes which would never be executed by the engine.

IPs and Ports

Under the same IP address a certain Port can be used only once. The default Port used by Just Out is 5509 and the default port of the first channel is 5519. Please make sure that the Ports used by Just Out and Just Connect are not used by another application. In case the Port is already used, the following warning will be shown:

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.