Page 1 of 1

VB-Cable in a Terminal Server environment

Posted: Mon May 27, 2024 8:18 am
by mav
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?

Re: VB-Cable in a Terminal Server environment

Posted: Tue May 28, 2024 1:31 pm
by Vincent Burel
If possible, you might install latest Voicemeeter version to check if the behavior is the same in your environment...
because we are about to update VB-CABLE with this new model of Virtual audio driver (currently provided by Voicemeeter).

Re: VB-Cable in a Terminal Server environment

Posted: Wed May 29, 2024 7:54 am
by mav
Thanks, we'll take a look.