Voicemeeter or Audio problem after WIN10 update

The Virtual Audio Mixer discussions and support...
Vincent Burel
Site Admin
Posts: 1322
Joined: Sun Jan 17, 2010 12:01 pm

Voicemeeter or Audio problem after WIN10 update

Post by Vincent Burel »

In some cases, WIN10 update can bring some problems and disturb our audio driver installation (and any other). In fact all the audio stack can be impacted by a WIN10 update and make you PC totally unusable from a day to another. We talk about this audio driver installation problem with Microsoft guys since years: our last discussion about this: https://www.freelists.org/post/wdmaudio ... pdate-2004

The problem seems to come from the driver installation procedure not using the driver Hardware ID as unique identifier in the installation process, and consequently merge driver properties and pins with possible previous installed drivers.

It is possible the problem comes from VISTA and possibly also present on WIN7 (this is why we ask to our users to REBOOT after installation and REBOOT after de-installation - to let the system finalize the process correctly) but with WIN10 automatic update, where all audio drivers can be re-installed at once, the consequences are just a complete mess in the audio stack.


After each WIN10 update, we recommend to check your windows audio configuration: what is your default playback device and what is your default recording device (and default communication devices too if needed) and if our audio devices have kept the same name and icon according driver name... It seems windows audio driver installation can merge audio pins randomly when re-installing audio driver. more info about our VAIO's checking: viewtopic.php?f=7&t=688

With WIN10 April 2020 Update (version 2004) still bring potential problem in audio stack since it can re-install driver badly... The solution is to re-install our Voicemeeter and virtual audio cable as explaine below...

With WIN10 April 2018 Update comes new Windows options related to Microphones or any recording device:
Go to your Privacy Settings for Microphone (and camera) and switch the main switch to "on" if it is set to "off"

With WIN10 October 2018 Update the default audio format of our virtual audio cable could have been changed to 8000 Hz Mono !?! we don't know why, but we recommend to change it in 44100 Hz Stereo (in Windows Control Panel / Sound Dialog box -> Properties / Advanced Tab).
WindowDefaultAudioFormatSettings.gif
WindowDefaultAudioFormatSettings.gif (92.77 KiB) Viewed 73372 times
After WIN10 update, if you get problem in the sound (stability problem) or you get strange behavior with audio application (bad audio, frozen app), or with device (the device cannot be selected anymore in Voicemeeter) we recommend to re-install Voicemeeter and our Virtual Cable by the following steps:

1- Remove all USB audio device + REBOOT.
2- De-install VB-CABLE one by one + REBOOT
3- De-install Voicemeeter + REBOOT
4- Check your remaining audio devices are working ok.
5- Check there is no presence of our virtual audio driver in Windows Device Manager (in both sections: multimedia controller and audio input output).
6- Re-install VB-CABLE and Voicemeeter one by one , REBOOT after each operation, check your device list in Windows Sound Dialog box.
7- When all is re-installed, re-plug your USB audio device. check again your default playback and recording device
8- Run Voicemeeter and check systray option. Audio should work again correctly.

9- Check that Voicemeeter Devices are correctly named and displayed with right icon:
VBAudioVirtualAudioPlaybackDevicesList.jpg
VBAudioVirtualAudioPlaybackDevicesList.jpg (45.69 KiB) Viewed 74304 times
10 - ReStart Voicemeeter.
zapoqx
Posts: 30
Joined: Fri Nov 25, 2016 10:25 pm

Re: Voicemeeter problem after WIN10 update

Post by zapoqx »

Thanks for the heads up. I am probably gonna reinstall it anyways right now as the icons are completely changed over after the update. Also, not sure if its my sound drivers or what, but my mic that I recently got is now overly sensitive, even with using the realtek noise suppression.
Vincent Burel
Site Admin
Posts: 1322
Joined: Sun Jan 17, 2010 12:01 pm

Re: Voicemeeter problem after WIN10 update

Post by Vincent Burel »

yes, if our icons have been replaced by generic icons, it means a process has re-installed our driver without using our procedure.
And this also can bring problems, so it's better to re-install Voicemeeter and VB-CABLE in this particular case.
LoneStar
Posts: 9
Joined: Wed Feb 24, 2016 4:55 am

Re: Voicemeeter or Audio problem after WIN10 update

Post by LoneStar »

I needed to do a clean reinstall of Windows 10 which included an update to Build 15063 (Creator's Update). The Macro Buttons no longer respond with this new install. I do not know if it is a Windows problem or I have the button coding wrong.

This is one of my macro button instructions...

Command.Load="D:\Game Stuff\VoiceMeeter\VoiceMeeter Banana\VoiceMeeter Banana Profiles\1-ONLINE-HEADSET ONLY-BoS-TS3-ShadowPlay.xml";

The above was working button instructions a copied and saved to notepad prior to reinstalling Windows. The macro buttons were working with Windows 10 Anniversary Update.

Is there something I need to change to get the Macro Buttons working again?

Thank You,
Vincent Burel
Site Admin
Posts: 1322
Joined: Sun Jan 17, 2010 12:01 pm

Re: Voicemeeter or Audio problem after WIN10 update

Post by Vincent Burel »

you can test macro button with a simple function like
strip(0).mute=1
strip(0).mute=1
to see if it works generally speaking...
and check your disk/file path (if wrong, it will do nothing).
LoneStar
Posts: 9
Joined: Wed Feb 24, 2016 4:55 am

Re: Voicemeeter or Audio problem after WIN10 update

Post by LoneStar »

Pasted the functions...

strip(0).mute=1
strip(0).mute=1

into the "Request for Initial State" box. When I select the button or enter the assigned hotkey, the button flashed and nothing occurs...audio not muted.

Rechecked the disk/file path. It is correct. Below is the disk/path that I copied with Shift+copy "Copy as Path".

"D:\Game Stuff\VoiceMeeter\VoiceMeeter Banana\VoiceMeeter Banana Profiles\1-ONLINE-HEADSET ONLY-BoS-TS3-ShadowPlay.xml"

Thank You
Vincent Burel
Site Admin
Posts: 1322
Joined: Sun Jan 17, 2010 12:01 pm

Re: Voicemeeter or Audio problem after WIN10 update

Post by Vincent Burel »

well, the first goal is to check that MAcroButtons app works
so make a regular test:

REQUEST for button ON: strip(0).mute=1
REQUEST for button OFF: strip(0).mute=0

which version are you using ?
LoneStar
Posts: 9
Joined: Wed Feb 24, 2016 4:55 am

Re: Voicemeeter or Audio problem after WIN10 update

Post by LoneStar »

No need to go any further. The problem did involve VoiceMeeter or Windows 10. It was me. I pasted the functions in the wrong box. I pasted the functions in the "Request for Initial State:" box. The correct box should be "Request for Button ON / Trigger IN:" box.

Sorry I had to bother you with my dumb mistake.

Thank You,
Ron Mcpherson
Posts: 1
Joined: Sat May 05, 2018 2:09 am

Re: Voicemeeter or Audio problem after WIN10 update

Post by Ron Mcpherson »

i have had a problem with voicemeeter banana since the April 2018 win10 update in which all of of wireless devices disconnect from the computer network and the wireless mouse and keyboard have lag. If the program is active, this interference occurs and wireless devices drop their connection to the network and when i close the program, all the wireless devices reconnect and are happy. I unstalled and reinstalled the cables and voicemeeter banana as per the instructions above but the problem remains. Any additional suggestions?
Thanks in advance
Ron
emgotcha77
Posts: 1
Joined: Fri May 11, 2018 8:51 am

Re: Voicemeeter or Audio problem after WIN10 update

Post by emgotcha77 »

Hello everyone.

I already wrote some stuff about my April-Update problems on twitter.

Here again the whole story:

For all my inputs in Voicemeeter Banana i see an error message in "System settings / Options":
- for WDM: Failed to Open Input Device: pAudioClient->Initialize return error -2147024891 (0x80070005)
- for MME: Failed to Open Input Device: Function waveInOpen failed: Undefined external error.

KS inputs work, for some unknown reason :?:

Outputs work, whatever mode i use.

I tried step 1-6 + restart, already, mutliple times.

What really puzzles me is that KS-inputs seem to work and all outputs are ok too...

Any log files i can attach / send you? I searched a little bit in C: but couldn't find anything that looks like a VB*.log .

Oh, installed version is 2.0.4.0.
Post Reply