The issue is on the other end of the 'cable'. Selected as an output device and appears to have audio routed to it when Yes, VB Cable appears on the list of output devices, can be

Near as I can tell, this is not an SDR Console (or other sourceĪpp) issue. If it appears in the list then a logfile would be interesting - start Can you start a radio using VB Audio? Does To: Re: No Virtual Audio VAC output with VB-Audio? In less than a month, the then current insider build will become the public 'spring update' release and at that point, any insider issues will become issues for EVERYONE using Windows. That said, anyone who codes Windows programs probably should have an insider build tucked away somewhere just to get early warning of issues like this. Any app that needs VB Cable as its INPUT shows VB Cable on its list of sound devices but throws an error when VB Cable is actually selected.Īgain, this is probably not an SDR Console issue. Yes, VB Cable appears on the list of output devices, can be selected as an output device and appears to have audio routed to it when selected. Near as I can tell, this is not an SDR Console (or other source app) issue. If it appears in the list then a logfile would be interesting - start the Can you start a radio using VB Audio? Does it Sound device configuration is also more involved and while it looks straightforward, some of what it does doesn't seem to be logical. But apps like external decoders no longer see items like VB Cable as a sound device. MS seems to have changed how the sound system works. I also tried contacting them directly by Email, but haven't had an answer yet. But so far they have not activated my forum account so I can't post. =That's bad news, Paul.ĭavidWell, I'm trying to report it. This has been true for at least several Insider builds and will become a serious issue for anyone trying to pass audio to a secondary program whenever the spring Windows 10 update goes live (April?). MS apparently changed how the sound system works and it seems like destination apps do not see the VB Cable output device correctly and throw an error on startup. While it might not relate directly, is anyone here running an Insider build of Windows 10? I find that VB Cable and Voicemeeter DO NOT work on recent Insider builds. I have been reading this thread with interest.

Virtual audio output windows 10