POWER STUDIO

Library Import

Library Import helps add larger sets of audio files to the Power Studio database.

Use it when preparing a new station database, migrating a music library, or adding a structured batch of tracks.

Library Import can also be used in migration workflows where an existing external library must be brought into Power Studio. For example, stations migrating from a Zenlex database can use the supported import path instead of rebuilding all metadata manually.

Supported Source Systems

Library Import can import media library data from these source systems:

  • Aeron Studio / PC Radio 6 (Express).
  • Aeron Studio Postgres.
  • Carmen Server.
  • Jazler 2.
  • Zenlex.

The first page of the wizard asks for the source system. The following pages then ask for the database location, connection or data source that belongs to that system, plus any audio folders or mapping choices needed for the import.

For Aeron Studio / PC Radio 6 (Express), make sure the NexusDB ODBC data source is available on the computer running Library Import and that the configured audio folders can be accessed. For Aeron Studio Postgres, prepare the database connection and the audio folders used by the old system.

For Carmen Server, prepare the Carmen data location and review the tempo mapping before importing. For Jazler 2, select the folder that contains the Jazler database files and make sure the media paths stored in the Jazler database are reachable. For Zenlex, select the Zenlex database location and the audio base folder, then review the content type mapping.

Before importing:

  • Put the audio files in their final storage location.
  • Confirm all Power Studio computers can access the same path.
  • Decide default content types and categories.
  • Make sure file tags are as clean as possible.

After importing, review a sample of tracks in Power Studio. Check title, artist, content type, categories and file paths before relying on the imported library for scheduling.

For repeated import sessions, keep notes about the default values used for content type, active flags, categories and other metadata. Reusing known-good start values makes later imports more consistent and reduces cleanup work after the import.