POWER STUDIO

Local Asset Cache

When audio files are stored on a network share, Power Studio can use a local asset cache to improve reliability and performance. The cache stores audio locally on the workstation so Power Studio does not have to depend on the network at the exact moment an item is needed.

For remote work, distinguish this from Power Sync. With Power Sync, the required audio is duplicated locally by the Power Sync workflow, which is useful on slower or less predictable internet connections. Synchronization must be started early enough. The first synchronization can take a long time because it may need to copy a large part of the library, or all audio files in the selected sync scope. With a VPN workflow, the workstation uses the studio audio storage through the shared audio path, and the Local Asset Cache improves reliability by caching the audio Power Studio needs just in time.

The Local Asset Cache is especially useful when:

  • The on-air computer plays many files from network storage.
  • The studio network is useful but not perfectly reliable.
  • A remote broadcast or temporary location set depends on shared audio from another location over VPN.
  • Presenters voice track from home using the VPN/cache workflow.
  • Administrators maintain the database from home over VPN and occasionally need to preview audio.
  • The station wants extra protection against short network interruptions.

Keep enough free disk space on the local computer. Monitor cache behavior after changing audio storage paths or replacing the on-air workstation.

Do not treat the cache as the main backup. Back up the central audio storage separately.

Settings

Enable the cache in Options and Settings > General > Local asset cache. Local asset cache options include:

  • Local asset cache to enable the cache workflow.
  • Download full playout playlist to deliberately pre-cache the loaded Playout Playlist when that is useful for a specific broadcast or workstation.
  • Play only cached files when the station wants playout to use cached copies only.

These options belong to the Local Asset Cache. They do not start, monitor or configure Power Sync synchronization.

Use Play only cached files carefully. It can protect against network dropouts, but it also means missing cache files can become an operational problem. Test cache completeness before unattended hours.

For a VPN/cache location setup or home setup that must keep working when the network connection drops, Play only cached files can be useful. Treat this as a deliberate cache-only workflow: enable it only after the relevant playlists, carts, voice tracks and dynamic items have been tested from the cache.

Location And Home Use

For a remote location or temporary studio that uses VPN access to the studio audio storage, the cache can make Power Studio less dependent on a slow or unreliable connection to the main studio. In normal use, Power Studio decides what to cache as the operator opens, previews and prepares audio. For a location broadcast where the station wants to survive a connection drop during playout, it can make sense to deliberately download the full Playout Playlist and test cache-only operation before the broadcast.

If the remote location uses Power Sync instead of the VPN/cache workflow, plan time for synchronization before the broadcast. This is especially important for the first run, because the workstation may need to receive a large number of audio files before it is complete enough for real use. That synchronization is managed by Power Sync, not by the Local Asset Cache settings.

For home voice tracking or database maintenance over VPN, do not automatically cache the whole playlist unless there is a clear reason. A full playlist cache can download many large audio files over the VPN or internet connection, even when the user only needs to record a few voice tracks or edit metadata.

Recommended home setup for the VPN/cache workflow:

  • Enable Local asset cache.
  • Leave Download full playout playlist disabled for normal voice tracking or database maintenance.
  • Use Play only cached files only for a deliberate cache-only workflow where the user understands that missing cached files cannot be played.

Power Studio automatically decides which audio needs to be cached based on the files the workstation opens, previews or prepares for use. For normal VPN voice tracking, database maintenance and production work, do not plan a separate manual cache step.

For home database maintenance where no audio preview is needed, the cache may hardly be used. In that case, the most important checks are the database connection, VPN stability and permissions, not pre-caching audio.

Operational Advice

Use predictable audio paths before enabling caching. Moving files after they are cached can make troubleshooting harder because the database, the network share and the local cache no longer tell the same story.

After replacing a workstation, expect the cache to warm up again as Power Studio uses audio. If the station relies on full-playlist download or cache-only operation, test the relevant playlists before unattended hours.

For voice tracking from home or production work over VPN, open and review the playlist in the normal workflow and let Power Studio cache the needed audio. Leave practical margin for large first-time downloads on a slow VPN connection, but do not try to manage individual cache files manually.

If a network share becomes unavailable, first keep the station on air and then investigate the storage issue. The cache can reduce risk, but it does not replace healthy server, network and backup practices.

When dynamic audio is generated or downloaded shortly before playout, such as news, traffic or syndicated content, check the plugin's download and processing timing. The final audio must be available and processed before the playlist reaches the item. The Local Asset Cache will cache it when Power Studio requests or prepares that audio, unless the station has deliberately enabled cache-only behavior.