POWER STUDIO

Multi Studio

The Multi studio page configures coordination between Power Studio instances.

Use this page only when the station has a multi-studio workflow, for example one central playout instance and one or more studios that can take over, go on air, or control shared external routing.

Multi Studio settings become most powerful when combined with hardware control. A mixer, GPIO system, Ember+ matrix, Axia V-Mixer, DHD Global Logics, D&R AXUM/AXITE system or analogue switcher such as a Sonifex Redbox SS10 can use the active studio state to follow the correct room automatically.

Multi Studio also supervises the connection to configured slave studio nodes. When a location studio or remote studio connection drops, Power Studio can detect that state, so the feature can also serve as automatic line monitoring for a coordinated studio link.

Enable Multi Studio Mode

Enable Multi studio mode only when this instance participates in a coordinated setup.

Choose one role:

  • Central Playout node accepts and coordinates configured slave studio nodes.
  • Slave studio node connects to the central node.

There should be one clearly assigned central node for the setup. Slave studios should connect to that node.

Keep the central node simple and reliable. It should not be a laptop that is often taken home or a production PC that is frequently restarted during office work.

Server Address And Port

For the central node, configure the Listening port. The default shown by Power Studio is 12668.

For a slave node, configure:

  • Server address: central playout computer name or IP address.
  • Listening port: the port configured on the central node.

Keep the coordination port inside the trusted studio network or a managed VPN. Do not expose it directly to the public internet.

If Windows Firewall is enabled, allow the required traffic between the Power Studio machines. If the machines cannot reach each other consistently, multi-studio state may be delayed or unreliable.

Use stable computer names or fixed IP planning for the central node. If DHCP or DNS changes cause a slave to connect to the wrong address or no address, the problem can look like an application issue while it is really a network naming issue.

For a location studio over VPN, test what happens when the VPN or network connection is interrupted. The central node should detect that the slave studio connection has disappeared, but the station must still verify the desired return-to-central behavior and any mixer, matrix or GPIO switching that depends on that state.

Computers

The Computers list controls which machines may participate:

  • Computer name is the Windows computer name.
  • Post Fix is the instance-specific configPostFix when multiple instances or transformed configs are used.
  • Connect allowed must be enabled for the instance to connect.
  • Studio nr. identifies the studio for multi-studio state, hardware mappings and external control.

The combination of computer name and post fix must identify the intended Power Studio instance. This matters when several instances run on the same computer or when a test instance shares the same database.

Disable Connect allowed for old machines, test instances and decommissioned workstations. Leaving obsolete entries enabled makes troubleshooting harder when a machine name is reused or a test instance appears in coordination unexpectedly.

Studio Numbers

Use stable studio numbers. Hardware-control plugins, GPIO logic, matrix switching and external control systems can use the studio number to decide which studio is active.

Do not reuse a studio number for a different room without checking all connected systems. A mixer, matrix or Companion page may still treat that number as the old studio.

Create a small studio-number plan and keep it consistent. For example, Studio 1 remains Studio 1 across Power Studio, mixer logic, matrix mappings, GPIO labels and Stream Deck pages.

Relation To Multiple Instances

When multiple Power Studio instances run on one computer, each instance needs its own configPostFix in the application settings. The Configuration Tool can apply config transforms to create those instance-specific settings.

After creating or changing an instance, return to this page and add or update the matching computer name and post fix entry.

See Multiple Instances On One Computer for the full setup.

Do not copy a configuration to another instance without changing the post fix and multi-studio entry. Two instances with the same identity can produce confusing coordination behavior.

Network And Control-System Tips

For reliable multi-studio operation:

  • keep all participating machines on the same trusted studio network or managed VPN;
  • avoid sleep mode on machines that must remain available;
  • document which machine is central and which machines are slaves;
  • test firewall rules after Windows or antivirus updates;
  • test hardware routing after any studio-number change.

If external routing depends on Multi Studio, test both the Power Studio screen state and the external device state. The screen can show the right studio while a matrix, console or GPIO mapping still needs adjustment.

Common integration patterns are:

  • LiveWire Control can drive an Axia V-Mixer or Mini-Mixer so an Axia system follows the active studio.
  • Ember+ Control can switch matrix crosspoints or logic parameters in an Ember+ compatible router, console or matrix.
  • DHD Global Logics can exchange logic states with a DHD system, so DHD mixer or control-system logic follows the active studio.
  • D&R MambaNet can be used with D&R AXUM/AXITE systems where MambaNet objects or control modules operate the studio switching workflow.
  • Analogue source switchers, such as Sonifex Redbox SS10 units, can be part of the same design when they are controlled through a suitable GPIO, contact-closure or logic interface.

Operational Checks

After changing Multi Studio settings:

  1. Restart the affected Power Studio instances.
  2. Confirm the slave can connect to the central node.
  3. Confirm each instance shows the expected studio number.
  4. Test on-air handover or control-system behavior in a safe moment.
  5. If hardware routing depends on multi-studio state, test the mixer or matrix integration too.
  6. Disconnect and reconnect a slave to confirm connection-loss detection and recovery behavior.

See Multi-Studio Coordination for the operational workflow.