POWER STUDIO

Multi-Studio Coordination

Some stations run multiple Power Studio instances or multiple studios against the same station environment.

Use Multi studio mode when one Power Studio instance must coordinate playout with one or more other instances. Typical examples are a central playout computer with one or more studios, or a workstation that can temporarily take over playout from the central playout node.

What Multi Studio Coordinates

Multi studio coordination keeps runtime playout state aligned between configured Power Studio instances. Depending on the station setup, it can coordinate:

  • Which instance currently has active playout control.
  • Whether a connected instance is allowed to leave automation and take control.
  • On-air state for the local instance and for numbered studio nodes.
  • Connection state of configured slave studio nodes, including detection when a studio connection drops.
  • The next item and items that are already playing elsewhere.
  • Playlist refresh/load messages between connected instances.
  • Return-to-central-playout timing and forced break behavior.
  • Timeshift start and stop messages.

Multi studio coordination does not replace normal database, audio storage and workstation planning. All participating instances must still use compatible database settings, audio paths, plugins, audio routing and user permissions.

For a remote or temporary location studio, the connection detection can also act as automatic line monitoring. Power Studio can detect when the configured slave studio connection disappears, but the station still needs a tested fallback plan for audio routing, mixer or matrix control and return-to-central behavior.

Multi-Studio Settings

Open Options and Settings and select Multi studio.

The page contains the Multi studio mode switch, the role for the current instance, the server address and port, and a Computers list.

Roles

Power Studio supports these Multi studio roles:

  • Multi studio mode off: this instance does not participate in Multi studio coordination.
  • Central Playout node: this instance acts as the coordinating playout node and accepts configured slave studio nodes.
  • Slave studio node: this instance connects to the Central Playout node and can take or return playout control when the setup allows it.

Use only one Central Playout node for one coordinated group. Start the Central Playout node first, then start the slave studio nodes.

Training Mode temporarily disables coordination behavior for the running instance. If a configured Multi studio instance appears not to coordinate while it is in Training Mode, switch back to Live Assist Mode or Automation Mode before troubleshooting the network connection.

Server Address And Port

For a Central Playout node, configure the listening port. The default port shown by Power Studio is 12668.

For a Slave studio node, configure:

  • Server address: the DNS name or IP address of the Central Playout computer.
  • Listening port: the same port configured on the Central Playout node.

Make sure the central computer firewall allows incoming connections on the selected port from the studio computers that need to connect. Keep the port inside the trusted studio network or a managed VPN. Do not expose the coordination port directly to the public internet.

Computers List

The Computers grid is part of the station configuration. It tells the Central Playout node which Power Studio instances are allowed to participate.

Use the columns as follows:

  • Computer name: the Windows computer name of the Power Studio machine.
  • Post Fix: the configPostFix value of that specific Power Studio instance.
  • Connect allowed: must be checked before that instance can connect to the Central Playout node.
  • Studio nr.: the visible studio number used for Multi studio on-air status and external control mappings. Use 1 to 5 for studios that must publish a numbered on-air state.

Power Studio identifies a connecting slave studio by the combination of Windows computer name and configPostFix. If the combination is not present in the Computers list, or if Connect allowed is not checked, the Central Playout node rejects the connection.

Use clear, stable names. If a computer is replaced, update the computer name in this list and verify the new machine has the correct database connection, license, audio routing, local folders and permissions.

Multiple Instances On One Computer

When more than one Power Studio instance runs on the same Windows computer, each instance must have its own configPostFix. Configure this before adding the instance to the Multi studio Computers list.

See Multiple Instances On One Computer for the full setup workflow and Configuration Tool transform example.

  1. Decide which computer or instance is the Central Playout node.
  2. Decide which computers or instances are slave studio nodes.
  3. If multiple instances run on one computer, assign and configure a unique configPostFix for each instance first. See Multiple Instances On One Computer.
  4. Confirm all participating instances use the same Power Studio version.
  5. Confirm all participating instances use the correct station database and audio paths.
  6. On the Central Playout node, enable Multi studio mode and select Central Playout node.
  7. Set the listening port.
  8. Add every participating computer/instance to the Computers list.
  9. Check Connect allowed for the instances that may connect.
  10. Assign a Studio nr. for each actual studio that must publish a numbered on-air state.
  11. On each Slave studio node, enable Multi studio mode, select Slave studio node, and enter the Central Playout server address and port.
  12. Restart the Central Playout node first, then restart the slave studio nodes.
  13. Test Live Assist Mode, Automation Mode, handover, return-to-central behavior, slave disconnection detection, playlist refresh and any hardware mappings that use Multi studio on-air state.

Operational Rules

Keep these rules in mind:

  • Use the same Power Studio version on all coordinated instances.
  • Use the same database connection details where clients share one station database.
  • Use identical audio file paths on all computers.
  • Keep the Central Playout node running before slave studio nodes depend on it.
  • Document which computer or instance is responsible for on-air playout, production, voice tracking and administration.
  • Do not change the central/slave role during active broadcast operation.

When updating a multi-instance machine, update secondary folders manually. Copy the updated application files, including the updated PowerStudio.exe.config, then apply the correct Configuration Tool transform for each instance before starting it. Do not overwrite instance-specific logs or license files. Recheck the configPostFix after applying the transform. See Multiple Instances On One Computer and Updating Power Studio.

Troubleshooting

If a slave studio does not connect:

  • Confirm the Central Playout node is running and not in Training Mode.
  • Confirm the slave studio is not in Training Mode.
  • Confirm the slave uses the correct server address and port.
  • Confirm Windows Firewall on the central computer allows the selected port from the slave computer.
  • Confirm the Computers list contains the slave computer's Windows computer name.
  • Confirm the Computers list contains the exact configPostFix for that instance.
  • Confirm Connect allowed is checked.
  • Confirm both instances use the same Power Studio version.

If the wrong studio appears on-air in external control hardware, check the Studio nr. assignments and the plugin mapping that uses MultiStudioOnAir1 through MultiStudioOnAir5.

If two instances on the same computer behave as if they share settings, stop and verify that each instance has a different configPostFix in its own PowerStudio.exe.config. See Multiple Instances On One Computer.