Audio Routing
The Audio Routing page assigns Power Studio audio functions to Windows audio devices and channel pairs.
For a live studio, route playout players to separate mixer faders where possible. That gives the presenter or technician clear control over levels, starts and stops. For simple unattended automation or web-only playout, fewer shared outputs may be acceptable if the complete signal goes directly to the stream encoder or processor.
Audio routing is local to the workstation. Configure and test it on every computer that plays, previews or records audio. A production workstation may have a very different routing plan from the on-air computer.
Main Output And PFL Output
Each player can have:
- A Main output used for program audio.
- A PFL output used when Playout Player PFL is enabled.
The PFL output shown for Player A-D belongs to the playout players themselves. It is used when the PFL button on a playout player is enabled and can reroute that loaded player from its normal output to its configured PFL output.
The standard routing approach is to route each playout player's PFL output to the same physical output as that player's normal playout output. In that setup, the main purpose of Playout Player PFL is the operational behavior inside Power Studio: the DJ or operator can listen, check and re-cue the loaded item without Power Studio treating that playback as normal on-air playout. The mixer channel, fader, cue button or monitor workflow must still be used correctly to keep audio off air when required.
When the studio workflow requires a separate software-level listening path, route the Player A-D PFL outputs to a dedicated cue, monitor or PFL output instead. This is useful when the audio interface or mixer has separate channels for operator headphones, cue speakers or technical monitoring.
The Playout Player rows configure Player A, Player B, Player C and Player D.
The Automation row configures the output used when Automation Mode plays through a shared automation channel. The Shares a channel with setting links that automation output to one of the players when the station uses a simpler mixer layout.
Common Routing Models
| Studio type | Typical routing | When to use |
|---|---|---|
| Full live studio | Player A-D to separate mixer faders, player PFL usually on the same physical player outputs, separate cart faders. | Best for presenter-driven Live Assist operation. |
| Full live studio with dedicated cue | Player A-D to separate mixer faders, player PFL to dedicated cue or monitor outputs, separate cart faders. | Useful when the mixer or audio interface has a separate operator listening path. |
| Compact studio | Players share fewer outputs, automation shares a channel with one player, player PFL usually follows the same physical outputs. | Useful when the mixer has limited channels. |
| Automation computer | Automation/program output to the main chain, separate preview routes optional. | For unattended operation or backup playout. |
| Production workstation | Track Browser, Mix Editor and Recorder routed to local speakers or interface. | For library work, voice tracking and editing. |
Document the chosen model for each room. If a device name changes after a driver update, that document helps restore the intended routing quickly.
Cart And Auxiliary Outputs
The cart player rows configure Cart A and Cart B.
The auxiliary rows configure:
- Playlist PFL for previewing playlist items.
- Track browser for previewing library search results.
- Mix editor for Mix Editor playback.
These auxiliary routes are separate preview/playback routes. They do not toggle PFL on Player A-D and they do not move a loaded playout player between outputs.
After changing routing, test every player, cart and preview path. Also test Automation Mode and Live Assist Mode, because their routing behavior can differ in a studio that uses an automation channel.
PFL And Preview Safety
Keep the two kinds of listening paths clear:
- Playout Player PFL belongs to Player A-D and changes how the loaded player behaves in Power Studio.
- Playlist PFL, Track Browser and Mix Editor use separate preview/playback routes.
Playlist PFL, Track Browser and Mix Editor preview routes should never be able to reach the on-air program output by accident. Test this with the mixer faders down and up:
- Preview a playlist item.
- Preview a Track Browser item.
- Play the Mix Editor.
- Confirm none of these signals is heard on the program output unless intentionally routed there.
Also test Player A-D PFL separately. If player PFL shares the same physical output as the normal player output, confirm that the mixer cue, fader and monitor workflow keep the item off air while the operator checks it. If player PFL uses a dedicated output, confirm that the dedicated route is heard only where intended.
If the station uses headphones from the mixer, also confirm that Playout Player PFL and preview routes are loud enough for operators without changing the main output level.
When Auto preview on PFL is enabled on the General settings page, switching PFL on can start the loaded playout player immediately. Test this setting with the configured Player A-D PFL outputs and the real mixer workflow before using it during live operation.
Broadcast Routing Advice
Use stable Windows device names wherever possible. If Windows or an audio driver exposes the same hardware with a different name after a driver update, check this page before going back on air.
In an on-air room, separate outputs make troubleshooting easier:
- A silent Player B fader is easier to diagnose than a single mixed output that carries all players.
- A clearly documented player PFL route prevents confusion between Playout Player PFL and separate preview players.
- A separate Mix Editor or Track Browser preview route helps producers work while the studio is live.
For audio-over-IP or mixer driver setups, keep the driver, Windows sound device, mixer source and Power Studio route documented together. The same route number can mean different things in the driver, the mixer and Power Studio.
See Audio Routing for installation examples and LiveWire Control for Axia-specific routing notes.
Troubleshooting Tips
If audio is silent or appears on the wrong fader:
- Check that Windows still shows the expected device.
- Check that the device channel pair matches the mixer source.
- Check whether Power Studio is in Automation Mode or Live Assist Mode.
- Check whether the automation output shares a player channel.
- Check whether the mixer fader source still points to the same driver or AoIP source.
If only Playout Player PFL is silent, check the Player A-D PFL output for that player. If Playlist PFL, Track Browser or Mix Editor preview is silent, check the auxiliary row for that function. If only Automation Mode is silent, check the Automation row and its Shares a channel with setting.