Remote Audio for Windows using Fluid

Allan Campbell

March 22, 2024 21:10

Is it correct that Jump Desktop still does not have native support for sending Windows host audio to the remote client?

I have a desktop I use both "live" and remotely via Jump Desktop. Having to keep changing the default audio (and having to install VB Audio Cable) is tedious - this should be automatic at this point, as all other remote-control tolls support audio natively.

This has been a topic for at least 7 years now... when will JD have native support for Windows remote audio?

Comments

6 comments

Abdul Ghani Madid March 25, 2024 14:04

Hi Allan, Thank you for reaching out to us.

Could you provide more details about the Windows machine you're connecting to?
Also, is it a virtual machine?
If it is, the workaround is to install the VB Audio Cable on the Windows Virtual machine.

Thanks.

0

Comment actions Permalink
Volker Schrepf April 07, 2024 22:18

I'm having the same problem. My machine is not virtual, I'm running on a Windows 11 in remote and client is on an iPad Pro 12.9. Ther is no sound when i run under fluid remote, both windows and secure screen sharing have perfect audio.

hope you can help.

thanks

0

Comment actions Permalink
Allan Campbell April 07, 2024 23:43

No, the machine I am connecting to is not a virtual machine. It is a typical Win 11 pro machine (Dell XPS 8950).

0

Comment actions Permalink
Allan Campbell April 11, 2024 01:27 (Edited April 11, 2024 01:45)

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

0

Comment actions Permalink
Allan Campbell April 11, 2024 02:00 (Edited April 11, 2024 06:00)

It would really be ideal if the Jump Desktop Connect allowed selecting the audio source that the user wants to capture. And, downmix that to stereo. (My Realtek driver creates a stereo downmix device automatically, i could in theory have Jump Desktop Connect capture that).

0

Comment actions Permalink
Volker Schrepf April 11, 2024 15:51

Allan,

Thanks for the update which helped me understand what’s happening and fix this issue for the time being. I agree with you that JumpDesk needs to correct this as it’s a pain to have to change from my 5.1 to stereo just to hear sound when I remote into my desktop.

0

Comment actions Permalink

Please sign in to leave a comment.

Comments

Didn't find what you were looking for?