> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vaudiolink.eu/llms.txt
> Use this file to discover all available pages before exploring further.

# Route audio safely in OBS

> Prevent echo, feedback, duplicate backing tracks, and accidental return audio.

Most collaboration echo is not network echo. It is the same signal reaching OBS or a participant through more than one route.

## Recommended baseline

1. Use headphones on both computers.
2. Add the plugin-managed incoming or combined output once.
3. Open **Edit → Advanced Audio Properties**.
4. Keep incoming vAudioLink sources on **Monitor Off** while establishing the session.
5. Add monitoring only through a deliberately isolated route.
6. Make a local test recording and inspect each signal separately.

## Product routing map

| Product      | Program source              | Monitor-only or special source   | Common mistake                             |
| ------------ | --------------------------- | -------------------------------- | ------------------------------------------ |
| ASMR Collab  | Incoming guest audio source | None required                    | Capturing the same guest from Discord      |
| Music Collab | **vAudioLink Output**       | **vAudioLink Backing (monitor)** | Sending the monitor backing to program too |
| Scene Share  | **Incoming Program**        | None                             | Adding its audio through a second path     |

## Find a duplicate path

<Steps>
  <Step title="Mute everything except one path">
    Temporarily mute Discord capture, desktop audio, application audio capture, browser sources, and vAudioLink sources.
  </Step>

  <Step title="Enable the intended vAudioLink path">
    Unmute only the incoming or combined source that should reach the program. Record and listen.
  </Step>

  <Step title="Add other paths one at a time">
    Re-enable each capture or monitor route individually. The duplicate returns when the conflicting path is enabled.
  </Step>

  <Step title="Remove or isolate the duplicate">
    Either remove it from the program mix or route it only to a monitoring device that cannot return to the sender.
  </Step>
</Steps>

## Symptoms and likely causes

| Symptom                              | Likely cause                                            |
| ------------------------------------ | ------------------------------------------------------- |
| Guest hears their voice late         | Incoming guest source is monitored back to them         |
| Audience hears two guests            | Discord and vAudioLink are both in the program          |
| Backing track sounds doubled         | Combined output and monitor backing both reach program  |
| Scene Share audio has a delayed copy | Incoming Program plus another received-audio source     |
| Loud howl or rising tone             | Speaker or monitor output is feeding an open microphone |

<Warning>
  Lowering volume does not remove a feedback route. Break the loop before continuing the session.
</Warning>

## Preserve user settings

vAudioLink docks own their managed collaboration sources. They should not alter the user's global OBS Stream, Output, or Audio settings. If troubleshooting suggests changing those settings, save the current values first and prefer fixing the source-level route.