There are two available to select from and I used the MME one. To get a feel of how it works and to satisfy my curiosity, following this section of the manual gave great proof of concept, especially when you run the Audio Repeater.

VAC has its own control panel and I’ve left it purely as the default settings. To get the audio out of SDRConsole and into Fldigi it’s as simple as selecting the Audio setting within SDConsoleįldigi is using the virtual audio as an input source and everything, just works. Virtual Audio Cable on the other hand worked instantly. Unfortunately as hard as I tried I just couldn’t get VB-Audio Virtual Cable to work, which is a shame as it looks good. The most popular is Virtual Audio Cable (current version is 4.14)Ī free alternative is VB-Audio Virtual Cable

There are several virtual audio packages in existence which attempt, with varying degrees of success, to achieve this. The only difference is it isn’t physical.Īs the screen shots show, once installed on a system, Windows displays the Virtual Cable as any other sound device plugged into the machine. Think of a virtual audio cable as any other lead that you plug things into or equally plug into things. Sounds complicated? Trust me it isn’t when you’ve got the very simple setup and config screens in front of you. As many applications as are necessary can tap into this bus and multiple virtual cables can be created.

Equally to use the output in Fldigi to decode CW, PSK31 etc there needs to be a mechanism to pipe the audio between applications.Ī virtual audio program pipes the output from SDRConsole, normally destined for your speakers, onto an audio bus which is then available to any application requiring an audio input. Unless the radio is used directly at the desk, with a set of speakers plugged into it, it’s not possible to hear any audio output.

Vb virtual audio cable