How To Control Windows Audio with Actions

On Windows, Commands, Automations, Timers, and SheevPad can change master playback volume, mute state, or default audio devices.

Available Actions

Open Utilities in Action Builder and choose:

Set Windows playback device
Set Windows input device
Set Windows system volume
Set Windows system mute

These actions control Windows audio, not an individual OBS or Streamlabs source.

Set Volume or Mute

Set Windows system volume changes the master volume of the current default Multimedia playback device from 0–100%.

Set Windows system mute can mute, unmute, or toggle that playback device.

For predictable buttons, use separate explicit Mute and Unmute actions instead of Toggle.

Change a Default Device

Select a playback or input device, then choose which Windows default roles it should receive:

Console + Multimedia for normal applications
Communications only for calling and communications apps
All roles when every Windows role should move

Playback and input/microphone endpoints are separate. Changing one does not silently change the other.

Already-open applications may keep their current endpoint until they reopen their audio stream.

Example SheevPad Buttons

Create recovery-friendly buttons such as:

Stream Speakers → Set Windows playback device → Speakers
Headphones → Set Windows playback device → Headphones
Mute PC → Set Windows system mute → Mute
Restore Volume → Set Windows system volume → 50

Test device changes before going live and keep a button that restores your normal configuration.

Common Problems

Actions are unavailable: Windows audio actions only work on Windows.
The wrong device changes: Confirm you selected playback versus input and the intended device ID/name.
A calling app did not move: Use Communications or All roles.
An open app stays on the old device: Restart its playback/capture or reopen the application.
OBS audio did not change: Use OBS Studio Control for OBS sources; Windows audio actions target system endpoints.