VB-Audio's Forums

yes, i think this last issue is fixed with the latest posted version 3.1.0.1

Correction / new functions 3.1.1.1 / 2.1.1.1 / 1.1.1.1 QUALIFICATION : RELEASE. - VAIO: Latency menu was not displayed correctly on Voicemeeter Standard and now the latency can also be defined by RIGHT CLICK on VAIO extension button. - COMPRESSOR: knee change now update the transfer graph display. ...

well, the problem can be in the way Win11 is managing our Virtual IO... I don't know... But Voicemeeter itself usually cannot generate such delay (out of the monitoring delay option in system settings). Tomorrow we will post a new version of Voicemeeter (on our Discord server), if you want to test i...

Voicemeeter cannot generate 500ms delay (max is around 70) so you may have a problem on other place.
we recommend to read this topic about latency optimization: viewtopic.php?f=6&t=480

OK, done.

You can at least disable some VAIOs in the Windows Audio settings i guess or in Windows Sound Dialog box.

we are going to update the VB-CABLE before end of year (to provide a new Win10/11 x64 version).

ok, this is an idea, i note it!

This is certainly possible to improve the overall latency by a more "direct process" but this will be less reliable, less stable.

Yes, Voicemeeter can be connected to Matrix of course, like any other audio application. I Don't understand your question about Dolby Atmos. Audio applications are managing PCM audio only. Any Codec or Protocol are taken in charge by audio device directly (usually not by audio applications). VAIO #3...