POWER STUDIO

Multi Studio Setup

Use this guide when one Power Studio instance coordinates playout state with one or more studios.

Goal

At the end of this path, the central playout node and slave studio nodes should connect reliably, use stable studio numbers and have tested handover and return behavior.

What You Need To Decide

  • Which computer or instance is the Central Playout node.
  • Which computers or instances are slave studio nodes.
  • Which studio number belongs to each room.
  • Which firewall, VPN or network route the studio computers use.
  • Which mixer, GPIO, matrix or external control system should follow the active studio state.

Setup Path

  1. Plan the computers, roles and studio numbers.
  2. Confirm all participating computers use the same Power Studio version.
  3. Confirm all participating computers use the intended station database and audio paths.
  4. If several instances run on one computer, configure unique configPostFix values first. See Multiple Instances On One Computer.
  5. Configure the central node in Multi Studio.
  6. Add the slave computers to the central Computers list.
  7. Enable Connect allowed only for the intended instances.
  8. Configure each slave studio node with the central server address and listening port.
  9. Restart the central node first, then restart the slave nodes.
  10. Test handover, return-to-central behavior, connection loss and recovery.
  11. Test any external routing or hardware logic that depends on studio state.

Test Matrix

TestExpected result
Start central node, then slave nodeSlave connects to the central node.
Disconnect the slave network during a maintenance testCentral detects the missing slave connection.
Switch active studio statePower Studio and external routing show the intended studio.
Enter Training Mode on a slaveCoordination behavior is disabled for that instance.
Restart one nodeThe setup recovers without changing studio identity.