The plain language guide

From mic to
“I can hear it.”

A route is simply a path for sound. Follow these steps to move a microphone through an effect and into an app.

Microphone→Effect→Destination
01 / Get connected

Make your first route.

  1. Open AudioRouter. Allow device access when Windows asks. Audio starts only after you choose to start a session.
  2. Add an input. Choose the microphone or audio device you want to hear.
  3. Add an effect if you like. Connect an EQ, gate, or compressor after the input.
  4. Add a destination. Choose an output or compatible virtual endpoint.
  5. Connect the blocks. Drag from the source output to the next tool's input.
  6. Press Play. Watch the meters. Speak into the mic and adjust levels.
A microphone routed through effects into a call and headphones
02 / Connect an app

Send sound into a virtual cable.

A virtual cable acts like a wire between apps. One app plays sound into it; another chooses it as an input.

  1. Install a compatible virtual audio endpoint such as VB-CABLE or Voicemeeter.
  2. In the source app, choose the cable's playback side as its output.
  3. In AudioRouter, select the cable endpoint in a supported input or output device node and connect it into your route.
  4. In the destination app, choose the cable's capture side as its microphone.
  5. Play audio and check the meters at each step.

Tip: Read device direction carefully. Test with a quiet signal first.

03 / Save a take

Record a branch.

  1. Add a Recorder node to the part of the route you want to capture.
  2. Choose a folder and WAV or FLAC.
  3. Arm that recorder deliberately and check the destination.
  4. Start the session and begin recording.
  5. Stop the recorder and open the recording library.

For separate voice and desktop files, put a recorder on each branch.

04 / Go beyond the canvas

Connect a developer tool or assistant.

Open the API tab to start the local HTTP listener and manage its token. Open the MCP tab for Codex or Claude Code setup instructions.

  1. For scripts and apps, use the CLI or local HTTP API.
  2. For an MCP client, add the server command shown in the MCP tab.
  3. Enroll the client and start with read-only access.
  4. Grant extra permissions only when you want the integration to act.
API guide →   MCP guide →
05 / Quick fixes

If you can't hear sound.

  • Check every connection. An unconnected block gets no audio.
  • Check the device. Confirm it is plugged in and the app uses the expected endpoint.
  • Follow the meters. Find where the signal disappears.
  • Check mute and bypass. Muted silences; bypass skips the effect.
  • Check the app's own input setting. AudioRouter doesn't secretly change app choices.
  • Open Logs if there is a device or plugin error.

A missing microphone stays silent. AudioRouter will not quietly swap in another input.