VB-Audio's Forums

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...

Matrix (audio router) is not made to replace Voicemeeter (Audio Mixer). these are 2x different kind of applications.

Matrix VAIO input 3 is a Line Out device... you may try the Input 2 (4,6 or 8) instead, because it is a speaker device that you can configure in 7.1

Matrix Latency, some points to know: 1- The main latency is given by the Matrix main stream buffer size (given by the master device) - we recommend to use an ASIO device as master device with 256 smp (or 128 smp min) buffer size (44.1/48 kHz) - or the internal clock if you have no ASIO device. 2- Th...