VB-Audio's Forums

Very bizarre error I encountered recently. I started up Dying Light with my usual audio setup of sending audio into VoiceMeeter Banana through the virtual input and duplicating it out to a pair of speakers and a headset. After roughly 2 days of it working, upon restart of the PC, Voicemeeter no longer received any sound from the game. When I change default audio device to the physical speakers, it successfully outputs sound, but it fails to do so when VM inputs are used.

Attempted Fixes:

• Changed default windows device to aux input
  Had voicemeeter only output to one physical device at a time
  Set default windows device to VBCable A then B and attempted to send that to devices using voicemeeter listening
  Updated audio driver to most recent version from motherboard manufacturer
  Updated audio driver to most recent generic driver from realtek
  Uninstalled driver completely and let Windows default driver run the output
  Reinstalled voicemeeter but kept settings
  Uninstalled voicemeeter and settings, then installed after 2 reboots
  Set all devices to be 48000 and then 44100 HZ in windows audio settings
  Disabled all devices in windows audio settings except for one physical device and one VM input
  Disabled exclusive mode on actual devices
  Disabled exclusive mode on Voicemeeter Inputs

I've tested nearly every other program I have, and none of them have an issue outputting to the virtual cable. Does anyone have any additional attempts I should try for getting this to output correctly?

This can happen if your VAIO internal latncy is too small
(Voicemeeter Virtual input latency default is between 4096 and 7168 sample).
did you change this?

Video game often use Direct X audio interface with buffer around 1024 to 2048 samples...
for example 2048 sample will not work with Voicemeeter virtual input if internal latency is only 4096

I tried setting the VAIO internal latency to 1024 and 2048 samples and the internal SR to 44100 and 48000 Hz. Music players, web browsers, and other games successfully output sound to the VM cable with no issues. Guess it might just be some weird audio workaround that Dying Light uses for its soundscape. VoiceMeeter doesn't receive any sound at all from the game, so it seems like the issue is something to do with whatever audio engine it uses.

SHEERSPECTOR wrote:I tried setting the VAIO internal latency to 1024 and 2048 samples and the internal SR to 44100 and 48000 Hz. Music players, web browsers, and other games successfully output sound to the VM cable with no issues. Guess it might just be some weird audio workaround that Dying Light uses for its soundscape. VoiceMeeter doesn't receive any sound at all from the game, so it seems like the issue is something to do with whatever audio engine it uses.

no, what i 've tried to explain is that VAIO internal latency must be above 4096 or better set to 7168 sample to give more chance to your game to work ok (1024 is usually too small for most of audio app and 2048 is not enough for most of game using DirectX audio).

Sorry for delay. I misunderstood the sample options and was under the impression it was sample rate and believed decreasing it caused the time between samples to rise. Thanks for correcting me. I tried both 4096 and 7168 sample latency for my virtual cables. Seems this game still does not want to output sound to them, so I'll update my ticket with the game developer and see if they have any suggestions. I'm not sure what audio interface this game uses. Since everything else on my computer seems to work regardless of internal latency or SR, it looks like this is an issue of whatever audio engine they use. If I get word back from the developers on what the issue is, I'll post it here.