Edit history

When sharing the entire screen on Windows with audio enabled, Fluxer appears to capture audio from multiple active playback devices instead of only the default or selected playback device. This causes major problems when using virtual audio software such as Elgato Wave Link or similar setups. For example, voice chat is routed through a virtual playback device. Fluxer captures that virtual device as part of the full-screen stream, so other users hear themselves twice:

• once normally through the voice call
• a second time through the stream audio, with a noticeable delay

The second copy may also bypass the intended audio processing/routing, resulting in unprocessed or differently processed microphone/voice audio. Similar problems can occur with virtual microphone monitoring or other virtual playback devices, because their audio can also end up in the stream even though they were never intended to be shared. Disabling these virtual devices is not a practical workaround, because software such as Wave Link depends on them for audio routing. This issue only occurs when sharing the entire screen. Sharing an individual application/window does not produce the same problem.

Allow users to select which playback device is used for audio when sharing the entire screen. For example:

• Windows default playback device
• A specific playback device
• All system audio

At minimum, Fluxer should provide an option to capture only the Windows default playback device instead of combining audio from multiple playback devices. This would prevent virtual voice chat, microphone monitoring, and other Wave Link devices from being unintentionally included in the stream.

Setup where the issue occurs: Windows Fluxer Desktop Client Elgato Wave Link / multiple virtual audio devices Entire Screen sharing with audio enabled The important distinction is that the unwanted audio is coming from other virtual playback devices, not just from the normal Windows default output. Because voice chat can be routed through one of these virtual devices, Fluxer captures the other participants again and sends them back through the stream. They therefore hear their own voice a second time with stream latency/delay.