VB-Audio's Forums

Read ASIO was the better option, but that was a real ASIO driver, not ASIO4ALL. Connecting to WDM driver is better, thanks. Something I noticed is that during use it only uses 5% of CPU time, but when not in use Voicemeeter uses up to 23%. Is there any setting beyond defaults to keep it at a minimum...

I started Voicemeeter and connected the software player (VAIO) and Windows sound (AUX), nothing is playing yet, but noticed the CPU load was already hovering at around 55%.

If VoiceMeeter's max latency is set to default 4096, what is VB-CABLE's default max latency? Trying to understand this: "Settings internal latency for Voicemeeter virtual input includes another constraint: the main buffer size used by Voicemeeter (given by the output A1 buffer size). The Virtua...

When audio is playing, Voicemeeter's CPU load is normally 4-6% while using "ASIO4ALL" as A1 output, and 5-7% when using "WDM: Speakers" as A1 output. When no audio is playing, the CPU load is normally up to 20%. When the computer comes back from standby/sleep , Voicemeeter goes u...

After reinstalling Voicemeeter Banana, noticed the default installation of Voicemeeter Banana (voicemeeterpro.exe) is 32-bit, is there a 64-bit version?

Also, the CPU load is hovering at around 16-21% when not in use, other times is around 7-14%.

Wasn't sure if the default for VB-CABLE A is 4096, but set VB-CABLE A and both Voicemeeter internal inputs (VAIO & AUX) to 4096 and is working fine. Is there a difference between connecting a software video player to virtual input VAIO, or connecting the player to VB-CABLE A, then to Hardware In...

Everything was working fine and suddenly got the red info for the internal virtual inputs. Uninstalled everything and only re-installed VB-CABLE A and Voicemeeter Banana. When I start Voicemeeter I'm still getting the red info. I used both control panels to set the sampling frequency for both at 480...