Skip to main content
Most collaboration echo is not network echo. It is the same signal reaching OBS or a participant through more than one route.
  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

​
Find a duplicate path

1

Mute everything except one path

Temporarily mute Discord capture, desktop audio, application audio capture, browser sources, and vAudioLink sources.
2

Enable the intended vAudioLink path

Unmute only the incoming or combined source that should reach the program. Record and listen.
3

Add other paths one at a time

Re-enable each capture or monitor route individually. The duplicate returns when the conflicting path is enabled.
4

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.

​
Symptoms and likely causes

Lowering volume does not remove a feedback route. Break the loop before continuing the session.

​
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.