AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
![]() otherwise WDM or KS with 512 sample buffers.įor the Virtual connection between EXA to Voicemeeter virtual input. The EXA to Voicemeeter connection (MME, DX, KS, WASAPI) with what buffer size.įor Voicemeeter Main Stream we recommend to first select ASIO device as output A1 (with 256 or 512 sample buffer). ![]() The Voicemeeter Main Stream (given by output A1 device = Monitoring) In this case latency is basically given by 2 connections: I guess users want to connect EXA to Voicemeeter to be able to manage the sound to different audio device or application (VOIP). I dont use any of the other apps listed by HammockTime, so can't comment on those, sorry. I have had this cause problems if I do try to use one of the final output devices as a manually selected audio device in another app (some apps like Winamp, most DAWs, Audacity, for example let you choose the output device instead of using the windows default device. Any output device then used by VM in either A1 and/or A2 output will be locked exclusive by VM and cannot be used by any other application. The VoiceMeeter (VM) VAIO Input, MUST to be set as your default sound device for VM to work. Thus you have 2 layers of latency: EXA > VM > Output.īetter to just have the one layer and let EXA talk direct to the final output device and disable VM or similar.Īnother final note. VoiceMeeter (VM) then takes that input and again buffers into either MME, WDM or KS depending on what your final output device is. VoiceMeeter (VM) Input uses a VAIO driver (windows default), so EXA is using that to load its samples into and buffer. I think the issue here is that you have 2 layers of latency. In other words, it might actually be useful to refer to the apps by name in order to alert users to possible latency issues. They might simply be using them because they filled a need and a quick search led them there, or a friend might have recommended them. Zach, I was also thinking that some users might not know these kinds of utils as audio "routing" or "patching" tools. R3LAY VPB Virtual PatchBay (formerly JADE Engine) It would be good to find out which do have a noticeable impact and which don't (if there are any), because these tools are useful when dealing with audio and it'd be nice to be able to have them running if at all possible. In the interest of documenting the apps that might affect EXA, I've looked around for Windows utils that can affect latency.
0 Comments
Read More
Leave a Reply. |