I have the Alesis IO26 and it doesnt work in WDM mode, but works okay in ASIO mode.
My guess is because of the DICE II chipset. Power off your PreSonus FireStudio interface or StudioLive mixer.
Exclusive Mode was enabled in the sound card properties, which caused the issues. Although there are ASIO drivers and some of our class compliant devices may work on. Save and fast, we are here to support you and your hardware. On you can find most up to date drivers ready for download. These are Windows standard ASIO drivers and they are garbage. File Name: presonus-firestudio-mobile-asio-driver.exe.
On the contrary when the buffer size reported by Voicemeeter is almost the same size as the configured, I have no problems with the sound. I think the unit has to use ASIO drivers for Sonar not WDM. AtmanActive wrote:Success Following up on this thread of thought where Focusrites badly programmed ASIO drivers could be the problem, I pulled up my dusty old Centrance Mic Port that was lying around forgotten in a drawer and installed their ASIO drivers (I had to install 'Legacy' v7.4.19 drivers as latest v8.0. When I select ASIO, and select ASIO Presonus FireStudio as Input, it looks better because I can see the 16 channels, but an errors pops up and says. The ASIO driver you should be using is Presonus ASIO. When using ASIO, I have observed that sometimes Voicemeeter shows a buffer size of 1024 instead of 441 samples which is the value configured in the ASIO Control Panel of the device in this case I don't get any sound from the device. I don't have an M-Audio interface but I have noted a similar behavior in my PC: The A1 device functions correctly when using WDM or MME. See the ASIO Driver support section in Voicemeeter Potato User Manual for more information. Check for example the buffer size configured. ASIO has nothing to do with PreSonus-it's a Steinberg technology, and would represent an absolutely colossal rework that interface manufacturers would need to choose to support with new drivers for their current-model interfaces, and would break support for older ones unless made backward compatible. ❺re you able to open the M-Audio ASIO Control Panel from within Voicemeeter System Settings / Options window? It should appear when you click on the device name. There is a topic in this forum where other users of M-Audio interface have reported a similar problem: viewtopic.php?f=6&t=617 It uses a Tascam interface but contains a lot of information that could be useful in your case.
VB-Audio Software official YouTube channel has a video about how to setup Voicemeeter with an ASIO device: