retsv.blogg.se

1. VB VIRTUAL AUDIO CABLE DISCORD WINDOWS 10
2. VB VIRTUAL AUDIO CABLE DISCORD PRO
3. VB VIRTUAL AUDIO CABLE DISCORD WINDOWS

The 'Error Details' there definitely seems to be some junk memory, as the garbage output was different every time I ran.

VB VIRTUAL AUDIO CABLE DISCORD WINDOWS

(audio_device_:205): Windows Core Audio is *not* supported => Wave APIs will be utilized instead (audio_device_core_win.cc:584): AudioDeviceWindowsCore::~AudioDeviceWindowsCore() the Avrt DLL module is now unloaded (audio_device_core_win.cc:537): webrtc::AudioDeviceWindowsCore::~AudioDeviceWindowsCore destroyed (audio_device_core_win.cc:351): AudioDeviceWindowsCore::CoreAudioIsSupported() Failed to use Core Audio Playout for device id=12

Continuing through the logs, I found a message where Discord's WebRTC failed to initialize IAudioClient (it's interface into the Core Audio APIs), and thus falls back to "wave APIs":Ĭode: Select all (audio_device_core_win.cc:2066): IAudioClient::Initialize() failed: I adjusted many sample rates (in VM, on physical devices, etc), but changes seemed not to effect the result positively or negatively. The WebRTC logs discord produced seem to indicate it was unable to open any devices using the Core Audio APIs, often complaining about channel count and sample rates. I enabled logging in discord and tested and have combed through the logs. All worked wonderfully.Īt this point, I was convinced it was an API issue in Discord. It seemed pedantic, but I tested it with DirectSound and MME though audacity as well. On playback, everything sounded just wonderful. There was 0 push/pull loss while it was active, output levels looked like I'd expect, and everything seemed like it should be working.Ĭlosing discord, I opened up audacity and set it's API to WASAPI, Device to VoiceMeeter Output, and started recording. I've monitored the input via the "VB-Audio Virtual Cable Control Panel" while using the "Let's Check" button in Discord's audio options. If I switched to directly using a hardware Input, Discord doesn't seem to have the issue at all. The 'dropping' mostly can be worked around by disabling the Discord built-in 'echo cancellation', but that just exposes what I think is the real heart of the issue with the "broken" audio that is coming through. In Discord, the audio when coming from the VB Virtual Output is crackly, robotic, poppy, or even occasionally "drops" like the input cut to -70dB.

Here's a crummy diagram for the more visually inclined: B1 is the 'Default Windows Recording' option, but I can also manually select it in Discord as well.

VB VIRTUAL AUDIO CABLE DISCORD PRO

The Line in, and Void Pro are hooked to output B1.

Virtual Output: B1: Windows Default Recording, B2:, B3: Hardware Output: A1: Headset Earphone A2:, A3:, A4:, A5: Virtual Inputs: VM VAIO: Windows Default Playback, AUX: Discord Output, VAIO 3: Unused Hardware Input devices: 1: Microphone via a Wireless Headset, 2: Realtek Audio Line In, 3: Webcam Microphone, 4:, 5:

VB VIRTUAL AUDIO CABLE DISCORD WINDOWS 10

Windows 10 Pro for Workstations 2004, Build 19041.264 This was all working well for months, until I did windows updates (incl. Goal: Mix my microphone input & Line in (Currently hooked to an Alexa Input for music), and occasionally my webcam's microphone to the default windows recording (or at least specifically for discord). I was using VB-Cable, but currently have them uninstalled as to not worry about conflicting. I've removed as many components from my setup as I can that will still let me get to my desired configuration. This post might be a bit lengthy, but I'm trying to cover everything that I've tried and discovered about the issue I've had since I've upgraded to the May 2020 Windows feature update.