p-rivero
commented
1 year ago One possible cause for this is that CABLE-D isn't actually unused: VB-Cable usually redirects the audio of those cable inputs to some cable output, so if you are still hearing echo it's because you are listening to the output of CABLE-D. You can test this by setting Output device of some app to CABLE-D and see if you can still hear it. If you can, then CABLE-D is being redirected to your default output device, so you can't use it.
Another possibility is that CABLE-D really is unused, but EarTrumpet is not redirecting the audio to it. Try using the Windows settings audio panel to change the Output device to CABLE-D, and see if that works.
However keep in mind that, either way, you will be streaming ALL the audio from your computer. If you are on a Discord call, the other people will hear themselves, which is probably not what you want. You should pick which apps you want viewers to hear, and set their output to CABLE-D. In DiscordAudioStream, capture the audio of CABLE-D. Make sure the output device of DiscordAudioStream are your default speakers. If you did it correctly, you shouldn't hear the captured apps until you press the button to start streaming.
I would like to capture my screen (including audio), but if I use my usual speakers it would loop. Muting the application or setting it to 0% stops me from hearing it but also stops discord from hearing it. A solution to that would probably to output the sound to another device (in this case an unused speaker/VB-Cable) that I won't listen to.
Using EarTrumpet, I have tried starting my stream and redirecting the audio to another device, but unfortunately it continues to stream to the default device rather than the one i chose.