Avoiding Audio Echo with Virtual Desktop
When Stream to 3D captures PC-screen audio, the original source audio and the converted playback audio must use separate Windows output paths. If both return to the captured path, you can hear an echo that repeats or grows over time.
Routing goal
- Source path: the browser or 2D media player sends its audio to the Windows output selected for screen capture.
- Playback path: the player showing Stream to 3D's converted output sends its audio to the headset/Virtual Desktop path without returning to the captured source output.
The device names differ between PCs. The important rule is that the source application and converted playback application must not use the same captured output path.
Use Windows Volume mixer
- Start the source application and begin playing audio so it appears in Windows Volume mixer.
- Start the Stream to 3D converted playback so its player also appears in the mixer.
- Leave the source application on the Windows output used by the screen-capture Live Source.
- Route the converted playback application to a separate output used by Virtual Desktop or the headset.
- Test with a short clip. You should hear the converted playback in the headset without hearing the original source a second time.
In Windows 11, application output selection is under Settings > System > Sound > Volume mixer. Windows only lists an application after it has opened an audio stream, so start playback before looking for it.
When a separate output is not available
An audio-routing application such as Voicemeeter Banana can provide a separate playback route:
- Install the audio-routing application and restart Windows if requested.
- In Windows Volume mixer, route the converted playback application to a Voicemeeter input.
- In Voicemeeter, send that input to the output used by Virtual Desktop or the headset.
- Keep the original source application on the separate Windows output used for capture.
Do not add extra routes until the two-path setup works. Additional monitoring outputs can feed the converted audio back into the capture path and recreate the echo.
Troubleshooting
- Echo continues: check the current per-application outputs while both applications are playing. Windows can reset a route after an application or audio device changes.
- No audio is captured: confirm that the source application is using the output selected for screen audio capture.
- No audio reaches the headset: confirm that the converted playback path is routed to the output Virtual Desktop is using.
- An application is missing from Volume mixer: start audio in that application, then reopen the mixer.