No audio devices detected in RDP session
Hi,
We have Virtual Cable installed on a server, when we RDP to it using RDM, no audio devices are detected.
If we RDP to the same server using RoyalTSX, the Virtual Cable audio device is correctly detected.
For both RDM and RoyalTSX we leave the audio at the Remote Computer.
I'm not sure if this is a bug in RDM or a missing feature, but I thought I'd ask since we're trying to transition away from RoyalTSX and this is a small bump in the road for us :)
Windows Audio (RDM):
Windows Audio (Royal TSX):
All Comments (7)
Hi Jimmi,
In RDM, any other settings than "Bring to this computer" will simply not configure the FreeRDP sound redirection (i.e. the audio channel (rdpsnd) won't be started). I've checked in our native code, and, in our case, "Do not play" and "Leave at remote computer" are functionally the same.
What behaviour are you expecting for "Leave at remote computer" exactly?
Best regards,
Xavier Fortin
Hi Xavier,
As usual, thank you for the quick response.
Virtual Cable is a Windows Audio Driver working as a Virtual Audio Cable.
With that installed, the expectation is that it is available during RDP sessions.
I don't understand why the driver is not detected with RDP sessions through RDM, but it is detected with RoyalTSX.
In Device Manager, I can see the inputs and outputs with RoyalTSX, but they're missing with RDM:
Kind Regards
Jimmi Larsen
I'm in talk with one of my colleague, and he seems to think we should not be treating those two options the same. So the error is most likely on our side.
That being said, I still need to confirm with you. I'm not familiar with Virtual Audio Cable, but the express purpose of the "Leave at remote computer" option is to have the sound run on the remote computer itself (i.e. not bringing it to the client computer). Is that what you want/need?
Best regards,
Xavier Fortin
Hi Xavier,
That is correct, with 'Leave at remote computer" I would expect audio from the remote server to play on the remote server.
Kind Regards
Jimmi Larsen
Perfect, we will correct the bug on our side. I will post back here when a fix is available.
Best regards,
Xavier Fortin
Cheers Xavier!
Hi Jimmi,
This issue should be resolved in the latest version of RDM (2021.2.2.0).
Do not hesitate if you have any further issues or questions.
Best regards,
Xavier Fortin