Location Set

A location set is a Power Studio installation used away from the main studio. It can be a temporary broadcast setup, a remote studio, or a prepared fallback workstation for use outside the normal studio network.

There are three common workflows for audio and database access:

For normal remote voice tracking or remote production work, first decide whether the station uses Power Sync or direct studio access over VPN with Local Asset Cache. A classic location set uses a local database and local audio copy. A VPN-connected location set behaves more like a remote studio that remains connected to the live studio environment.

Choose The Workflow

Choose the workflow before copying databases or audio files.

Use a local database with manually copied audio when the location must be able to operate without a stable connection to the studio. This is the most self-contained approach, but it requires a careful copy procedure and manual verification. Because the location uses its own restored database, it must also generate and use its own playlists for the broadcast period.

Use a local database with Power Sync audio when the location should still have local audio files, but the station wants Power Sync to automate the audio-copy process. This is usually easier and more reliable than manual copying when the location set needs repeated updates or when many files have changed. Power Sync handles the audio files; the local Power Studio database still needs its own generated playlists.

Use a direct studio connection over VPN when the location should work directly in the live studio environment. In this workflow, Power Studio connects to the studio database and uses the studio audio storage through the expected shared path. The location then works in the station's own playlist, with the same scheduled commercials, news, promos and other station content that are part of the studio workflow. The Local Asset Cache can improve audio reliability, but the location still depends on the VPN for database access, shared audio access and any Multi Studio coordination.

The VPN workflow needs a more stable internet connection than a fully local location set. If the connection drops, the location may lose access to the database, shared audio, Multi Studio coordination or automatic switching behavior. Test this workflow under realistic network conditions before relying on it for a real broadcast.

Workflow 1: Local Database With Manually Copied Audio

This workflow creates a local copy of the station environment.

Prepare The Database

1. Install PostgreSQL on the location computer.
2. Create an empty database with the licensed database name.
3. On the on-air system, create a database backup in custom format.
4. Copy the backup to the location computer.
5. Restore the backup into the empty database.

Create the backup as close as possible to the location broadcast so tracks, playlists and metadata are current. Use PostgreSQL's custom backup format and restore it as a custom or tar backup in pgAdmin.

When the location set needs a fresh copy later, replace the location database with a new restore from the on-air database instead of trying to manually synchronize individual tables.

Because this workflow uses a local database, the location set does not automatically follow the current studio playlist after the database has been restored. Generate the playlists needed for the location broadcast in the local database and verify that the expected commercials, news, promos, jingles, voice tracks and live elements are present before leaving the studio.

Prepare Audio Files

Copy the on-air audio storage to the location computer. The most important rule is path consistency: Power Studio must see the audio files at the exact same path as in the studio.

If the studio uses M:\Audio, the location set should also use M:\Audio. You can use a mapped drive, a local folder mounted as a drive letter, or another station-approved method.

After copying the files, open several music tracks, jingles, promos and dynamic items from the restored database. This checks both the file paths and the completeness of the copied audio storage.

Manual copying is fine when the station has a clear procedure and enough time to verify the result. The risk is that changed, new or replaced files can be missed, especially when the location set is updated more than once.

Workflow 2: Local Database With Power Sync Audio

This workflow still uses a local restored database, but lets Power Sync copy and update the audio files.

Prepare the local database in the same way as workflow 1. Then use Power Sync to keep the required media files available on the location computer.

Power Sync is usually more convenient and reliable than manual copying because it can automate repeated audio updates. It also reduces the chance that a new jingle, changed commercial, replacement track or freshly recorded voice track is forgotten during a manual copy.

Start Power Sync early enough, especially the first time. The initial synchronization can take a long time because many audio files may need to be transferred before the location set is complete enough for real use.

Power Sync does not make the local database a live copy of the studio database. The location set still needs playlists generated in its own restored database. Treat playlist generation, commercial blocks, news items and other scheduled content as part of the local preparation workflow, then use Power Sync to make sure the audio files referenced by that local database are present on the location computer.

Before leaving the studio or starting the broadcast:

• confirm the local database restore is current enough for the broadcast;
• generate the location playlists needed for the broadcast period;
• confirm commercials, news, promos and other scheduled station content are present in those local playlists;
• confirm Power Sync has completed the required synchronization;
• open representative music, jingles, promos, commercials and voice tracks;
• confirm newly changed or added files are present on the location computer;
• test what happens when Power Studio runs without access to the studio network.

See Power Sync Remote Workflow.

Workflow 3: Direct Studio Connection Over VPN

In this workflow, the location computer connects directly to the studio environment over a VPN.

The location computer typically:

• connects to the PostgreSQL database in the studio;
• uses the studio audio storage through the same path as studio workstations;
• may use Local Asset Cache to improve audio reliability;
• can be configured as a studio in Multi Studio when the station wants coordinated on-air switching and automatic connection supervision.

The main advantage is that the location set works in the live station environment. Playlist changes, asset changes and database changes are immediately part of the same station database. The location runs in the station playlist instead of a separate local playlist copy, so the broadcast automatically follows the station's scheduled commercials, news, promos and other fixed content. If Multi Studio is configured, the location can act as a studio node and the central playout setup can automatically switch or follow the active studio according to the station's normal Multi Studio workflow.

Multi Studio also detects when the connection to the location studio drops. In that sense it can function as automatic line monitoring for a remote or temporary studio link. The station should still test the expected fallback behavior, audio routing and external switching before relying on this during a live broadcast.

For a live location broadcast with workflow 3, use a suitable low-latency audio codec for the programme audio between the location and the studio. The VPN/database connection keeps Power Studio connected to the station environment, but the on-air audio path still needs broadcast-style attention: stable upload, low delay, predictable buffering, return audio if required, and a tested fallback when the codec or internet connection fails.

The main disadvantage is that this workflow needs a stable internet connection and a reliable VPN. A weak connection can affect database access, audio access, Multi Studio coordination and automatic switching. Local Asset Cache can reduce the risk of audio dropouts, but it does not replace the need for a working database connection or Multi Studio network connection.

Before using this workflow:

1. Configure and test the VPN.
2. Confirm the location computer reaches the studio PostgreSQL server.
3. Confirm the studio audio path is available from the location computer.
4. Enable and test Local Asset Cache if the station wants extra protection for audio access.
5. Configure Multi Studio only if the location should participate as a real studio node.
6. Configure and test the low-latency programme-audio codec or contribution link.
7. Test automatic studio switching, connection-loss detection, mixer or matrix control, audio routing and fallback behavior before the live broadcast.

See Planning Your Installation, Local Asset Cache, Multi Studio settings and Multi-Studio Coordination.

Configure Power Studio

For a local-database location set:

1. Install Power Studio.
2. Copy the license file to the installation folder.
3. Use the Configuration Tool to point the application to the local PostgreSQL database.
4. Test audio routing, playlists and file access before going on location.

For a VPN-connected location set:

1. Install Power Studio.
2. Copy the license file to the installation folder.
3. Use the Configuration Tool to point the application to the studio PostgreSQL database.
4. Confirm the VPN is connected before starting Power Studio.
5. Test audio routing, playlist access, audio file access and any Multi Studio role before going on air.

For a restored database that already matches the installed version, the Configuration Tool's Update button is usually not needed.

Do not use a location set without testing the chosen workflow first. Verify login, playlist loading, audio routing, PFL, carts, macros, local or remote audio access, and any required plugins before leaving the studio.