POWER STUDIO

Multiple Instances On One Computer

Some stations run more than one Power Studio instance on the same Windows computer. This can be useful for a central playout instance and a local studio instance, for testing a separate station configuration, or for a production role that must stay separate from the normal on-air workflow.

This is an advanced setup. Use it only when the station has a clear reason, a documented multi-instance plan and an assigned role for every instance. Multiple instances share the same Windows computer, but they must not accidentally share the same local Power Studio identity.

ConfigPostFix Is Required

When more than one Power Studio instance runs on the same Windows computer, each instance must have its own configPostFix.

The configPostFix separates instance-specific settings such as:

  • Machine settings.
  • User settings.
  • Local cache folders.
  • License file selection.
  • The single-instance lock.
  • Multi studio machine identity.

The postfix is also sent to the Central Playout node when a slave studio connects. Without a unique configPostFix, two instances on the same computer are difficult to distinguish and may use the wrong local settings, local cache, license file or Multi studio registration.

Use a short, stable postfix that describes the role, for example:

  • Studio1
  • Studio2
  • Production
  • Central

configPostFix is an application setting in PowerStudio.exe.config. It belongs in the <appSettings> section below the root <configuration> element:

<configuration>
  <appSettings>
    <add key="configPostFix" value="Studio2" />
  </appSettings>
</configuration>

The value is the postfix for that specific Power Studio instance. The default or primary instance may have no postfix, but every additional instance on the same computer must have a unique non-empty value.

Do not change the configPostFix casually after the station is in use. A changed postfix makes Power Studio treat the instance as a different local configuration. Plan the change, check the license file, verify local audio and user settings, and update the Multi studio Computers list when the instance participates in Multi studio coordination.

Separate Instance Ownership

Every instance should have clear ownership for:

  • The folder from which the instance is started.
  • The PowerStudio.exe.config file.
  • The license file used by that instance.
  • Local logs.
  • Local cache folders.
  • Audio routing and recording devices.
  • Startup behavior.
  • Multi studio role, if used.

Do not copy one instance folder over another without preserving the instance-specific identity. The application binaries can be updated, and the updated PowerStudio.exe.config file should normally be copied too because new Power Studio versions may add or change configuration entries. Keep the instance-specific config changes in a Configuration Tool transform profile, then apply that transform again after updating the files.

The license, logs and local identity must remain correct for each instance.

Set ConfigPostFix With A Configuration Transform

The easiest way to prepare a separate instance configuration is to use the Configuration Tool transform feature.

  1. Close Power Studio for the instance you are configuring.
  2. Create a transform profile file named like PowerStudio.exe.Studio 2.config.
  3. Store the file where the Configuration Tool can find the transform profile.
  4. Open the Configuration Tool from that instance folder.
  5. Select the profile in Transform configuration.
  6. Click Transform.
  7. Restart Power Studio.
  8. Confirm the instance starts with the intended local configuration.
  9. If the instance participates in Multi studio coordination, open Options and Settings > Multi studio and add or update the Computers list entry for the computer name and postfix.

The Configuration Tool creates a backup of the current PowerStudio.exe.config before applying the transform.

Example transform for a second instance with postfix Studio2:

<?xml version="1.0"?>
<configuration xmlns:xdt="http://schemas.microsoft.com/XML-Document-Transform">
  
  <!-- Add appSettings and update the configPostFix setting -->
  <appSettings xdt:Transform="Merge" />

  <appSettings>
    <add key="configPostFix" xdt:Transform="Remove" xdt:Locator="Match(key)" />
  </appSettings>
  
  <appSettings>
    <add key="configPostFix" value="Studio2" xdt:Transform="Insert" />    
  </appSettings>  
</configuration>

Use a different postfix for every Power Studio instance on the same computer.

Do not edit configPostFix directly as an isolated advanced setting unless Power Studio support specifically instructs you to do so. A transform profile is safer because it makes the intended configuration change repeatable and reviewable before it is applied.

Multi Studio Coordination

When multiple instances on one computer are used with Multi studio coordination, the Central Playout node identifies a connecting slave studio by the combination of Windows computer name and configPostFix.

In the Multi studio Computers list:

  • Use the Windows computer name in Computer name.
  • Use the instance postfix in Post Fix.
  • Check Connect allowed only for instances that may connect.
  • Assign a Studio nr. only when that instance should publish a numbered on-air state.

See Multi-Studio Coordination for the full central/slave setup workflow.

Updating Multiple Instances

When updating a computer that runs multiple Power Studio instances, the installer updates the main installation folder only. Other instance folders must be updated manually.

Copy the updated application files, including the updated PowerStudio.exe.config, to the other instance folders. Then apply the correct Configuration Tool transform for each instance before starting it. This writes the instance-specific settings, such as configPostFix, into the new config file while still keeping configuration changes that came with the new Power Studio version.

Do not overwrite the instance-specific license file or logs.

See Updating Power Studio for the update checklist.

Troubleshooting

If two instances on the same computer behave as if they share settings:

  • Confirm each instance starts from the intended folder.
  • Confirm each instance has a different configPostFix.
  • Confirm the correct PowerStudio.exe.config file is being used.
  • Confirm local cache folders and logs do not point to the same location unless that is intentional.
  • Confirm the Multi studio Computers list contains the exact computer name and postfix combination.

If a changed postfix makes an instance appear as a different workstation, restore the previous configuration or update the station configuration deliberately. Do not continue troubleshooting audio routing, cache behavior or Multi studio identity before the postfix is correct.