#Virtual audio cable free non trial full#
#Virtual audio cable free non trial software#
#Virtual audio cable free non trial trial#

And to be perfectly clear, this has absolutely nothing to do with the VDI functionality in Lync 2010 or 2013. Connections via Remote Desktop will not work the same way. I should note that this has to be done from the console session of a Hyper-V or VMware VM. You can select Virtual Audio Cable Line 1 for the speaker, and Line 2 for the microphone.Īt this point you can now make and receive phone calls within the VM (although you can’t hear anything!) Now open Lync again and check the Audio Device settings. Right-click on Control Panel and select “Run As Administrator” to open the configuration utility.Įnter 2 for cables and press Set. Navigate to the Virtual Audio Cable folder within the Start Menu.

#Virtual audio cable free non trial software#

After the software is installed you can create the virtual audio devices. To get started, unzip the package and run the installation on a VM.

#Virtual audio cable free non trial trial#

This prevents you from testing any audio functionality, which can be handy in a lab to validate Edge server or gateway integration scenarios.Ī solution here is to leverage a tool called Virtual Audio Cable, which offers a free trial available here: If you use the console or remote desktop on a virtual machine running Lync you’ll see the warning that no audio device is connected:Īnd if you check your Audio Device settings, Lync will tell you that no device has been found. Then exactly the same setup for for Spotify, where on VB-Audio control panel you can clearly see the audio reaching the input channels 1 & 2 on VB-Audio at a good level.The need to have dedicated PCs each with an audio device for testing Lync audio can sometimes be a challenge, especially in lab environments where all of the clients are virtualized. One shows the VB-Cable contol panel, SDR-Console output selected to VB-Audio input (and confirmed on Win sound device mixer), SDR receiving a good signal from Radio 5 Live, plenty of audio, and can be clearly heard with speaker selected, but when SDR Console selected to VB-Audio cable input as you can see on VB-Audio control panel, 0% audio on Input Channels 1 & 2. The weird bit is how it works perfectly for all apps except SDR Console.ĭaniel, regarding the VB-Audio control panel (a good shout). Jdow, no I did not trim the log, but did simply start it purely for purpose of generating the log hence probably why so short, but yes, works fine on speaker output and always has done. Throw it all into the hole and quickly back fill the hole and get out of their quickly lest it still manages to escape.

At precisely midnight drive a fire hardened oaken stake through the package and the disk inside. Dig a six foot deep posthole big enough for your packaged disk.

#Virtual audio cable free non trial full#

Go to a deserted crossroads at midnight with a full moon overhead. Wrap the floppy disk in 7, exactly 7, alternating layers of paraffin (US style wax) and lead foil. Then expunge it from your system with arcane mystical incantations. Take a copy of that tool onto a floppy disk or CDROM. It uprooted a program's direction to a secondary USB audio device and threw it onto the motherboard's RealTek digital output, which I do not use. And 'EEEEK', the asshat Volume Mixer can get programs all screwed up. It gives a better view of what is going on. Ah, you can get it using the start button. Just for the record if you can get the speaker icon into the system tray you can right click on it and get a much more useful Volume Mixer display. So looks like for some unknown reason the audio from SDR Console never reaches the VB-Audio input, wouldn't you say? Thanks for looking! Then exactly the same setup for for Spotify, where on VB-Audio control panel you can clearly see the audio reaching the input channels 1 & 2 on VB-Audio at a good level. Daniel, regarding the VB-Audio control panel (a good shout).

Please be noted that the software is just like a virtual audio cable and all the sounds are. The weird bit is how it works perfectly for all apps except SDR Console. Its free to try for 30 days, but the trial version places an audio 'watermark' on the output. jdow, no I did not trim the log, but did simply start it purely for purpose of generating the log hence probably why so short, but yes, works fine on speaker output and always has done.