POWER STUDIO

Recorder

Power Studio includes recording functions for station workflows such as voice tracking, production and logging-related tasks.

Configure Recording

Before recording, configure:

  • Recording input device.
  • Recording format.
  • Recording destination folder.
  • Latency offset where needed.
  • Any required encoders.
  • SoundCloud credentials when the station uses the built-in publish workflow.

Use a reliable local or network path with enough free disk space.

The recording settings page lets you select the recording device, choose the record format, configure the encoder or format details, set the voice track folder and set the normal recorder file path.

When recording and encoding are too heavy for an older workstation, use Advanced Audio Settings to review whether recordings should be processed offline. Offline processing applies encoding or processing after the recording has finished instead of doing all work during the recording itself. This can reduce the risk of recording glitches on slower computers, but the final file will only be ready after the post-processing step is complete.

Check Recording

Record a short test and verify:

  • Correct input source.
  • Correct level.
  • No clipping.
  • Expected file format.
  • File can be played back in Power Studio.

Retest after changing sound devices or driver settings.

Recording Window

The Recorder window shows recording time, the current file and metadata fields such as title and description. It can export a recording, publish through configured publish targets and apply a processing profile.

Use clear titles and descriptions when recordings are shared with other staff. If recordings are published, check the configured account and destination before publishing a production recording.

Processing Profiles

Processing profiles can be used when exporting or publishing recordings. Keep the profile names meaningful, such as Voice cleanup, Podcast export or Production master.

Do not change processing profiles during an active recording workflow unless the operator knows which file will be affected.

Remote Control

Recorder functions can be controlled remotely through the REST API and through Bitfocus Companion when the REST API plugin is enabled. This lets a station place Recorder buttons on a Stream Deck or integrate recording actions with another trusted control system.

Typical remote controls include:

  • Play and stop.
  • Toggle recording.
  • Start recording.
  • Stop recording.
  • Move through configured recorder profiles.

Remote control does not remove the need to monitor the recording. The operator should still confirm the correct input, level, destination folder, recording profile and available disk space before starting an important recording.

When using Companion or another REST API client, confirm that a Power Studio user is logged in with permission to operate the Recorder. Also test the button color or feedback state so the operator can see whether recording is active.