No audio with SDR# and VB-Audio Virtual Cable

Status
Not open for further replies.

P25_LA

Member
Joined
Mar 15, 2019
Messages
7
Location
Los Angeles, California
I'm driving myself crazy trying to figure this out. I had VB Cable and SDR# working fine but now all of the sudden if I go into Sound Control Panel (Win10 64bit) and select "Listen to this device" I can't hear anything. I have the output set to Default device, and if I go in to SDR# and set my Output to headphones I can hear audio fine from an active frequency. But, if I select VB-Audio Cable as output I can't hear anything and the levels register 0 when I look in the Windows 'Recording' tab for the control panel. This was working fine before but all of the sudden it quit.

I tried uninstalling/reinstalling VB-Cable and rebooting but the same behavior is observed. I know it's something simple, what am I missing? It's a big deal because for months I've been feeding the output from VB-cable to DSD+ to decode P25 and it's been working fine.
 

BM82557

Member
Joined
Aug 28, 2006
Messages
5,301
Location
Berkeley Co WV
Check your audio input devices and audio output devices numbers in Windows, from time to time mine have changed in Windows. I don't know what happens to cause it though.
 
S

simpilo

Guest
I'm driving myself crazy trying to figure this out. I had VB Cable and SDR# working fine but now all of the sudden if I go into Sound Control Panel (Win10 64bit) and select "Listen to this device" I can't hear anything. I have the output set to Default device, and if I go in to SDR# and set my Output to headphones I can hear audio fine from an active frequency. But, if I select VB-Audio Cable as output I can't hear anything and the levels register 0 when I look in the Windows 'Recording' tab for the control panel. This was working fine before but all of the sudden it quit.

I tried uninstalling/reinstalling VB-Cable and rebooting but the same behavior is observed. I know it's something simple, what am I missing? It's a big deal because for months I've been feeding the output from VB-cable to DSD+ to decode P25 and it's been working fine.
I don't know how Windows 10 displays it but make sure VB-Cable is set for default recording device matching my Windows 7 images.
They can't be that different. Playback default must always be your system sound speaker output.
 

Attachments

  • Playback.PNG
    Playback.PNG
    19.6 KB · Views: 42
  • recording.PNG
    recording.PNG
    20.6 KB · Views: 44

spongella

Member
Premium Subscriber
Joined
Feb 21, 2014
Messages
1,102
Location
W. NJ
I experience the same thing and use SDR# and VB cable. When I pipe the audio from SDR# via VB cable to MultiPSK software, the audio is fed to the sound card and I hear no audio anymore. It's a bit of a bother, but as long as I can see that the audio is being fed to the software (MultiPSK has a main window for this) that is fine.
 

spongella

Member
Premium Subscriber
Joined
Feb 21, 2014
Messages
1,102
Location
W. NJ
Yep, sometimes I've had to just run Zadig again just to get SDR# to recognize the dongle again. I wonder if when Windows updates occur this has something to do with it. Glad you got back up and running.
 
Status
Not open for further replies.
Top