Core Features•9 min read

Send Your Voice to the Right Place

Learn the three audio routes Echo uses and how to tell which part of the chain is not working.

Verified for v1.2.6WindowsmacOS
Browse all guides9 guides

Understand the Three Audio Routes

RouteWhat It Should Be
Input DeviceThe physical microphone you speak into.
Audio OutputA virtual audio device that carries Echo into Discord, games, OBS, or another app.
Headphone DeviceThe headphones or speakers used only for Hear Yourself.

Select Your Devices in Echo

Echo Live Audio settings showing input, output, monitor, and volume controls
Open Settings > Audio to choose the microphone Echo hears, the route other apps receive, and the headphones used for monitoring.Full screenshot
  1. 1

    Open Settings > Audio

    Keep the device names visible while you set up the rest of the route.

  2. 2

    Choose Input Device

    Select your real USB, headset, laptop, or audio-interface microphone. Do not select the virtual cable as your input.

  3. 3

    Choose Audio Output

    Select the supported virtual device that should carry Echo to other apps. Echo blocks ordinary hardware outputs here to reduce accidental feedback and loud loops.

  4. 4

    Choose Headphone Device

    Select the headphones or speakers you actually listen to, then enable Monitor only when you want to hear yourself.

What the Virtual Cable Does

A virtual cable links Echo to apps that expect a microphone. Echo does not replace your physical microphone driver, and Hear Yourself alone does not send converted audio into Discord.

Windows

Echo currently recognizes supported virtual devices such as VB-Cable and compatible alternatives. A newly installed audio driver may require a Windows restart before its endpoints appear.

macOS

Echo can use a supported virtual device such as BlackHole for app routing. Local monitoring can still work without a cable, but Discord or OBS needs a route it can select as an input.

Route Echo into Discord or a Game

  1. 1

    Confirm Echo works first

    Load a voice and use Hear Yourself with headphones. This confirms the microphone and conversion path before you add Discord.

  2. 2

    Check Echo's Audio Output

    Note the selected virtual device in Settings > Audio.

  3. 3

    Open the receiving app

    In Discord, your game, or OBS, choose the matching virtual cable recording endpoint as the microphone or input source.

  4. 4

    Run the receiving app's microphone test

    Speak normally and confirm it receives the converted voice rather than your physical microphone.

Use Hear Yourself Without Changing Output

  • Enable Monitor to hear a local copy through Headphone Device.
  • Use Monitor Volume to change only what you hear.
  • Use Output Volume to change what Discord, games, and OBS receive.
  • Use headphones whenever possible so the monitored voice does not re-enter the microphone.
  • Bluetooth headphones can add noticeable listening delay even when Echo processing is keeping up.

Set a Safe Output Level

  1. 1

    Speak at your normal level

    Watch the Output Volume meter while using the voice you plan to keep.

  2. 2

    Use Auto Level as a starting point

    Let Echo measure active speech and choose a safer initial output level.

  3. 3

    Check the receiving app

    Confirm Discord, OBS, or the game is not adding excessive automatic gain after Echo.

Find the Broken Part of the Route

What You ObserveMost Likely Place to Check
Echo shows no microphone activityMicrophone permission, Input Device, connection, or exclusive access.
Hear Yourself works, but Discord hears nothingEcho Audio Output and Discord input endpoint do not match.
Discord hears the normal voiceDiscord is using the physical microphone instead of the virtual cable.
Discord works, but Hear Yourself is silentEnable Monitor, Headphone Device, or Monitor Volume.
Everyone hears echo or a loud loopA speaker or virtual cable is feeding back into the microphone or monitor route. Stop processing and rebuild the route with headphones.
A newly connected device is missingRefresh Devices, then reconnect or restart Echo if the driver appeared after launch.
Last verified 2026-07-31 for Echo Live v1.2.6.

Still stuck?

Copy the exact error and include Settings > System > Copy for Support.