POWER STUDIO

Common Troubleshooting

Use this page for first response checks. For detailed configuration, follow the related topic links.

No Audio

Possible causes:

  • the wrong Windows device or channel pair is selected;
  • the mixer source no longer points to the expected driver or audio-over-IP route;
  • Power Studio is in a different playout mode than expected;
  • the player, cart or preview route is configured differently from the route being monitored;
  • the audio file is missing, unavailable or blocked by storage permissions.

First checks:

  1. Confirm Windows still shows the expected audio device.
  2. Check Audio Routing for the affected player, cart or preview route.
  3. Play a known-good item from the same workstation.
  4. Check whether the issue affects one route or all routes.
  5. Check the mixer, interface or audio-over-IP source assignment.

Database Not Reachable

Possible causes:

  • PostgreSQL service is stopped;
  • firewall or network access changed;
  • the connection string points to the wrong server or database;
  • credentials changed;
  • the workstation is on the wrong VPN or network.

First checks:

  1. Confirm the PostgreSQL server is running.
  2. Confirm the workstation can reach the database server.
  3. Check the configured database connection.
  4. Confirm other Power Studio clients can connect.
  5. Review recent Windows, firewall, VPN or server changes.

Stream Does Not Start

Possible causes:

  • URL is a webpage instead of a direct stream URL;
  • stream provider changed codec, TLS or redirect behavior;
  • firewall or proxy blocks the request;
  • retry or reconnect settings are too strict;
  • the stream is silent or offline at the provider.

First checks:

  1. Test the stream in Power Studio, not only in a browser.
  2. Confirm the direct stream URL.
  3. Check retry, reconnect and default duration settings in Live Sources.
  4. Test from the on-air workstation and network.
  5. Confirm the fallback item or operator action.

Plugin Does Not Behave As Expected

Possible causes:

  • the plugin was changed but Power Studio was not restarted;
  • the plugin is enabled on the wrong computer;
  • credentials, API keys or network addresses changed;
  • a hardware device, service or provider is offline;
  • several systems are trying to perform the same scheduled task.

First checks:

  1. Restart Power Studio after plugin changes.
  2. Confirm the plugin is enabled only where the workflow requires it.
  3. Test the connected device, service or URL outside Power Studio where possible.
  4. Review the plugin-specific page in this manual.
  5. Check logs and document the exact time of the failure.