VB-Cable in a Terminal Server environment
Posted: Mon May 27, 2024 8:18 am
Hi forum, I hope you could share a bit of light on using VB-CABLE in a not-quite-usual environment:
At the moment, we're evaluating the integration of VB-CABLE for a project and on a local machine everything looks promising.
The intended use case for this project includes the ability to be used in a Terminal Server environment (MS RDS or Citrix, mainly), though.
In our tests with an RDP connection from a Windows client to a Windows Server host we could not find any difference in the available audio devices in the session, regardless if VB-CABLE was installed on the client and/or server:
Unless you activate audio redirection in the RDP client for recording and playback, you don't get any audio device in your session.
With audio redirection activated, the session only has the default "Remoteaudio" playback and recording devices and VB-CABLE is not listed in the audio devices at all.
Is there a way to use VB-CABLE on the server inside an RDP session somehow?
At the moment, we're evaluating the integration of VB-CABLE for a project and on a local machine everything looks promising.
The intended use case for this project includes the ability to be used in a Terminal Server environment (MS RDS or Citrix, mainly), though.
In our tests with an RDP connection from a Windows client to a Windows Server host we could not find any difference in the available audio devices in the session, regardless if VB-CABLE was installed on the client and/or server:
Unless you activate audio redirection in the RDP client for recording and playback, you don't get any audio device in your session.
With audio redirection activated, the session only has the default "Remoteaudio" playback and recording devices and VB-CABLE is not listed in the audio devices at all.
Is there a way to use VB-CABLE on the server inside an RDP session somehow?