Fix Windows audio capture for Fluid
Fluid Audio capture on a Windows host currently fails (no remote audio) if the host machine is set to more than two audio channels (e.g., 5.1 or 7.1 surround sound). The result is that the remote client hears no audio.
Discovery: If I switch my host Win11 machine from 5.1 audio to 2-channel (stereo) then Fluid audio starts working correctly and I can hear it on the remote client.
In the jump desktop log file, when the Windows default audio device is set to more than 2 channels, then an error appears in the host PC’s log when connecting from a Jump client:
2024-04-10 18:02:14:867 21408:20908 INFO [audiocap 1 l0hxd8v1] Device:Speakers (Realtek(R) Audio)({0.0.0.00000000}.{e45c4e77-8f61-4641-818e-2cde8887502c}), Format:65534 Channels:6 Samples:48000 BPS:32
2024-04-10 18:02:14:867 21408:20908 INFO [audiocap 1 l0hxd8v1] Subformat: {00000003-0000-0010-8000-00AA00389B71}
2024-04-10 18:02:14:870 21408:20908 ERROR [audiocap 1 l0hxd8v1] Could not initalize audio client: -2004287480
However, with the same audio device set to 2-channel (stereo) in Windows Control Panel:
024-04-10 21:19:37:563 15748:6920 INFO [audiocap 1 k0wq9zv5] Device:Speakers (Realtek(R) Audio)({0.0.0.00000000}.{e45c4e77-8f61-4641-818e-2cde8887502c}), Format:65534 Channels:2 Samples:48000 BPS:32
2024-04-10 21:19:37:563 15748:6920 INFO [audiocap 1 k0wq9zv5] Subformat: {00000003-0000-0010-8000-00AA00389B71}
2024-04-10 21:19:37:595 15748:3056 INFO [rtc.sc 1 k0wq9zv5] Capturer changed: RTC
2024-04-10 21:19:37:598 15748:6920 INFO [audiocap 1 k0wq9zv5] Started recording
Please address this so that people don't need to switch their PC to stereo/2-channel in order to hear remote audio.
Please sign in to leave a comment.
Comments
0 comments