Skip to guide
← Tool guides

Audio, explained · 26 / 36

Application Capture

Capture one chosen application process tree.

Visual walkthrough1 configuration controlsAnimated walkthrough
See how it works ↓

Produces the selected app audio; a closed app produces silence while retaining its node.

01 / Understand

The idea, before the settings.

The picker selects an application identity rather than an interchangeable process number. Normal application playback continues.

Chosen app processApplication CaptureAudioRouter route

Use it in AudioRouter

  1. Open the application and make it play audio.
  2. Refresh the running-app list and choose the intended process in Tools.
  3. Add the source, connect it to your processing/output, Save and Play.
  4. Check the source meter while the selected app makes sound.

What success looks like

The selected application's audio enters the route independently of a whole-output loopback.

If it does not work

A restarted app can have a new process identity. Refresh and select it deliberately; check whether the target app is actually producing sound.

Select the node to open Properties. Click its name to rename it. While playing, supported parameter-only edits save after a short pause. For structural edits, use Save when the canvas marks a change. Enabled and Bypass are distinct live controls; see the in-app help for their behavior.

02 / Explore

Make the behavior visible.

This process-selection diagram is visual only; the website cannot inspect or capture your running applications.

This animated diagram is conceptual. It is not a DSP measurement or control for your running AudioRouter session.

03 / Configure

Every control, with a reason.

01

Application to capture

application

Choose a running application. The selection stores executable/path identity and process creation information; the PID label only helps distinguish current instances.

Range / choicesDepends on your selectionDefaultChoose explicitly

Try thisPick your music player from Using audio now, then connect it to a Mixer.

Keep in mind Stop before changing the application. Refresh applications if it has just started. Browser tabs are not separate capture sources.

04 / Put it to work

Start with a useful example.

Example 1

Separate game and voice

  1. Add an Application Capture for the game and a Physical Input for your microphone.
  2. Route each to its own processing chain.
  3. Combine them only where you want a mix.
Example 2

Troubleshoot a quiet app

  1. Check whether the node says app closed, ambiguous, unsupported, or connected.
  2. Start audio in the chosen application and refresh its inventory.
  3. Confirm the actual node meter, rather than assuming connected means audible.

These are starting points. Compare at a comfortable monitoring level and adjust for your own source.

05 / Get unstuck

Small details that matter.

  • Capturing an app does not mute its normal speaker playback; duplicate monitoring can result.
  • Two indistinguishable verified instances require deliberate selection.
  • Protected or unusual applications are not guaranteed to capture.