VB-Audio's Forums

So I have been noticing that for a while now, Voicemeeter (banana at least) the program seems to hang at random times. Basically I will notice that the CPU is being used and one of two things happen.
1: System process is running high.
2: Voicemeeter Banana is running high.

Both cases will be usually 25-35% of the CPU. I check Voicemeeter and it seems to be running smooth. What I've locked it down to is that my microphone from my headset seems to be the culprit. Either I luck out and get it fixed by removing the mic from hardware input 1 and resetting it back (It is set to WDM) or the program freezes, forced to force close and not reopen. Voicemeeter will also be stuck running in the Process list and will deny the system of force closure even by command prompt admin commands. I will have to restart the computer if its in this stuck method as nothing will reset the audio even with the -r command or restarting the audio service.

System:
i5-4690
Realtek Audio
Windows 10 Pro 64-bit build 1703

As you might be aware, since I'm part of the issue with the optical audio bug that has not been resolved, I can only run my headset that runs through optical at MME for 5.1 surround, or WDM for Stereo only

there is 3 problems in your message:

- About CPU usage drops to 25-35% (while it has previously worked with 5% or less CPU load during hours). this is a problem we are working on.
- About Voicemeeter freeze, not responding or cannot be closed... The only case we know concerns MME interface and is described here: viewtopic.php?f=6&t=430 (confirm this is describing your problem ? )
- About optical output management under WIN10, we have not yet tested it...

About the link you gave: The thing is the MME interface is that is only for the output selection, not the input. The Output is optical. The headset when used in this way has a USB Mic where its only as an input. So I'm not sure if in this case, you're referring to the mic's input being MME, in which case, the Mic's input is WDM and is USB so I don't believe it as related. Sometimes, this can occur while I'm on the computer at the time so I would figure if there was a sound for something removed, it would play to which then I would check my connections. Alas, no. Since this happened again, I can point out the pic.


As you can see about behind that window, Hardware Input 3 is fine. That is for my other mic equipment. That is going to B1 and is analog. It is WDM. Input 1 is going to B2 and if you notice, it has no audio information going on when in this case, it should (the usual pickup noise in the background). It to is WDM as well and it is the one that has the USB mode.

could you please post a screenshot of the system settings dialog box (in Voicemeeter Menu) ?

general rules: in case of problem, go back to default settings.

Your problem comes certainley from this option:
WDM input Exclusive Mode: set it back to NO (there is a warning when you set it to YES).

you may set back WDM buffer size to 512 samples too.

ah WDM buffer, I set it there in an attempt back to solve the Optical Bug on that other post just to see if I could figure out why it was the way it was. Was thinking along Frequency alignment. Couldn't remember about that WDM Input.

Well that is definitely interesting. Seems buffer on the USB mic changed to 485, Analog Mic to 528, and WDM analog speakers to 512. Also, my Analog Mic is seemingly less sensitive. DOH! I can't believe I completely forgot about those changes.

New screenshot... Will keep you up to date over the next few days to see if the issue returns.

just updating to say that ya, the fix worked. No issue in these past few days. Also, just updated Windows 10 to Fall Creators Update the day prior and still working well.

good to know, thanks!