Hello,
I am currently using the voicemeeter potato beta version. For now Im just using it as an audio repeater for my mic, virtual inputs, vb-cable and vb-cable a+b.
Now what I am wondering is what kind of latency in ms I am getting when using voicemeeters virtual inputs together with the vb-cables. I read about how to optimize latency etc. but I didnt quite understand everything written.
And I dont understand if the buffers in voicemeeter applies to both hardware and virtual inputs or just the hardware inputs, meaning that virtual inputs would have a slightly lower latency?
Im also wondering if its true that if I double the sample rate and also double the buffers I will get the same latency but with higher quality?
I have set all playback and recording devices to 48khz/24bit and the max latency on all vb-cables to 2048 smp. If I have calculated it all correctly the maximum possible latency I could receive with my current settings is 47,66 ms because (80+160+2048)/48000 = 0,04766. But correct me if Im wrong.
Virtual Inputs + VB-CABLE(s) buffer latency to ms
-
- Posts: 1
- Joined: Fri Sep 14, 2018 8:07 pm
Virtual Inputs + VB-CABLE(s) buffer latency to ms
- Attachments
-
- VB-CABLES Settings.jpg (175.89 KiB) Viewed 13950 times
-
- VoicemeeterPotato.png (201.73 KiB) Viewed 13950 times
-
- PotatoOptions.png (77.71 KiB) Viewed 13950 times
-
- Site Admin
- Posts: 2139
- Joined: Sun Jan 17, 2010 12:01 pm
Re: Virtual Inputs + VB-CABLE(s) buffer latency to ms
the Voicemeeter Latency is pending first on Main audio device latency (the one selected as output A1). That's why we recommend to select your best audio device as output A1 to get the most stable and reliable and low latency stream (ASIO driver can be often the better option for output A1).
Anyway the latency added by the Virtual I/O or VB-CABLE is pending on the internal Latency
2048 sample, means a latency max of 2048 / 2 samples = 21.3 ms at 48 kHz
and obliges connected application to send / recieve audio in buffer lower than 2048 / 3 = 682 samples.
So the Added Latency by VB-CABLE is expected to be closer than 14.2 ms (than 21.3).
more info about VB-CABLE latency: https://www.vb-audio.com/Cable/VBCABLE_ ... ttings.pdf
Anyway the latency added by the Virtual I/O or VB-CABLE is pending on the internal Latency
2048 sample, means a latency max of 2048 / 2 samples = 21.3 ms at 48 kHz
and obliges connected application to send / recieve audio in buffer lower than 2048 / 3 = 682 samples.
So the Added Latency by VB-CABLE is expected to be closer than 14.2 ms (than 21.3).
more info about VB-CABLE latency: https://www.vb-audio.com/Cable/VBCABLE_ ... ttings.pdf