POWER STUDIO

Plugins

The Plugins page enables, disables and configures installed plugins.

Plugins extend Power Studio with content workflows, metadata output, visual radio links, studio hardware control, REST API access, Companion control and external system integrations.

Plugin configuration can affect external systems immediately after Power Studio starts. Treat plugin changes like studio wiring changes: make one change at a time, restart when needed, and test the connected device or service.

Enable Only What The Station Uses

Enable only the plugins the station actually uses.

An unused plugin can still add configuration complexity, startup work, reconnect behavior or external output state. Keeping the plugin list clean makes the system easier to support.

Disable plugins that belonged to old hardware, old visual-radio systems or test integrations. Leave the documentation and setup notes available, but do not keep the runtime plugin active unless it is part of the current station workflow.

Configure Plugin

Select a plugin and open its configuration screen when the plugin has one.

Plugin configuration can include:

  • network host and port settings;
  • serial, USB, MIDI or GPIO device settings;
  • API keys or service credentials;
  • player, cart and playlist mappings;
  • title-output templates;
  • reconnect behavior;
  • matrix or mixer mappings.

Each plugin has its own documentation page. Use those pages for exact setup steps.

Change One Plugin At A Time

Do not change several hardware or output plugins in the same maintenance window unless there is a clear rollout plan.

For each plugin:

  1. Record the current settings.
  2. Change the plugin configuration.
  3. Restart Power Studio if required.
  4. Confirm the plugin connects.
  5. Confirm the external system receives the expected state.
  6. Confirm the plugin recovers after a disconnect or external-device restart.

This is especially important for mixer-control, GPIO, metadata output, visual radio and REST API integrations.

Restart And Reconnect

Plugin changes often require a Power Studio restart. After enabling, disabling or changing a plugin, test the complete path:

  1. The plugin starts.
  2. The plugin connects to its device or service.
  3. The plugin handles reconnects.
  4. The plugin respects user permissions and player count.
  5. The plugin behaves correctly after Power Studio is restarted.

For hardware and control plugins, also test what happens when the mixer, GPIO device, REST client or network connection is restarted later. A plugin may connect successfully on startup but still need to recover correctly during the day.

Permissions And Player Count

Some plugins depend on the number of Playout Players and on the commands the current user is allowed to execute.

After changing player count, user permissions or plugin mappings, test:

  • Player A-D commands;
  • cart commands;
  • playlist commands;
  • Automation, Live Assist and Training Mode switching;
  • status feedback such as playing, cued, selected, next item or on-air state.

If a plugin works from Power Studio but not from a hardware controller, check both plugin mapping and user permissions.

Plugin Documentation

Use the plugin documentation pages for plugin-specific configuration:

The main plugin overview is Plugins.

Common Pitfalls

  • Enabling a plugin before the required driver or device software is installed.
  • Reusing an IP address, port or device name from an old studio setup.
  • Forgetting to update plugin mappings after reducing or increasing the number of players.
  • Testing only startup connection and not reconnect behavior.
  • Leaving a test metadata or visual-radio output enabled in production.