Power Sync Remote Workflow
Power Sync is used when a remote Power Studio workstation should work with the central studio database, but should not depend on opening every audio file live over a VPN or internet connection.
This is useful for remote voice tracking and asset management, especially when the remote connection is slower, less predictable, or not suitable for opening high-quality audio files in real time. Instead of relying on live audio access during the session, Power Sync keeps a local copy of the required media files on the remote computer and keeps those files up to date.
See the Power Sync product page for the product overview.
When To Use Power Sync
Use Power Sync when:
- presenters voice track from home or another remote location;
- producers or administrators manage assets from outside the studio;
- the internet connection is not fast enough for reliable real-time audio access;
- the station wants predictable local playback during remote production work;
- remote users need to create or update audio files and send those changes back to the studio;
- the remote computer should keep audio synchronized even when Power Studio is not running.
Power Sync is often the best remote workflow when audio files are large, the connection has variable latency, or the station wants remote work to feel close to a local studio workstation.
For temporary location sets, manually copying audio files can also be a valid workflow. Power Sync does not make manual copies wrong, but it can automate the process and reduce the risk of forgetting changed, new or replaced files.
How It Differs From Local Asset Cache
Power Sync and Local Asset Cache solve related problems in different ways.
| Workflow | Main purpose | Typical use |
|---|---|---|
| Power Sync | Synchronizes audio files to a remote computer so they are available locally. | Remote voice tracking and asset management over slower or less predictable internet connections. |
| Local Asset Cache | Caches audio just in time while Power Studio uses shared studio storage. | Studio workstations, VPN workflows, network shares and cache-only fallback scenarios. |
Power Sync synchronization is managed by Power Sync. Local Asset Cache settings such as Download full playout playlist and Play only cached files do not start, monitor or configure Power Sync.
Planning Synchronization
Start synchronization early enough, especially before the first real remote session. The initial synchronization can take a long time because Power Sync may need to copy a large part of the library, or all audio files in the selected sync scope.
After the first synchronization, later updates are usually smaller, but still need time. Plan extra margin before important remote voice tracking sessions, location broadcasts or large asset-management jobs.
Before relying on a remote workstation, confirm:
- the workstation connects to the correct Power Studio database;
- Power Sync has completed the required synchronization;
- the expected audio is available locally on the remote computer;
- newly recorded or changed audio is synchronized back to the studio;
- the presenter can open the playlist, preview audio, record a test voice track and save changes.
Remote Voice Tracking
For remote voice tracking, Power Sync helps avoid problems caused by slow live file access. The presenter works against the station database, while the audio needed for playback and recording is available locally.
Before recording a real show:
- Start Power Sync early enough for the required audio to synchronize.
- Open the correct playlist in Power Studio.
- Preview several representative tracks.
- Record and save a short test voice track.
- Confirm the new voice track becomes available back in the studio.
Do not wait until just before a deadline to start the first synchronization. A remote setup may look correctly configured while audio is still being copied in the background.
Asset Management
Power Sync can also be used when remote users add, replace or maintain audio assets. This is useful for music directors, producers or administrators who work outside the studio but still need their changes to become available in the central station environment.
Use clear operational rules for remote asset work:
- import or update only approved broadcast audio;
- use the same metadata standards as the studio;
- check content type, title, artist and categories before saving;
- allow time for new or changed files to synchronize back to the studio;
- verify important new audio from a studio workstation before relying on it on air.
Operational Advice
Treat Power Sync as part of the remote production workflow, not as a substitute for backups. The central database and audio storage still need normal backup protection.
Document which remote computers use Power Sync, which users are allowed to work remotely, and who checks synchronization status before important production work.
If a remote session has missing audio, stop and check Power Sync status before recording. Voice tracks recorded against incomplete or wrong audio can technically save correctly, but still be timed against the wrong playback.