I am attempting to use the Windows 11 native WASAPI driver with the USB interface that is integrated into my Studiologic Numa X Piano keyboard. I am receiving the following error message when I try to start the Cantabile 4 audio engine.
The error occurs on two different laptops. This is what the C4 audio driver panel looks like.
Clearly, it sees the WASAPI driver and the Numa X Piano device (XPIANO88). The buffer size appears to be selectable, but always reverts to 256 regardless of what selection I make from the drop-down list.
I am able to use ASIO4ALL, however I feel like I may get better performance and results from native Windows WASAPI. The Numa X Piano does not have its own ASIO driver, as the vendor’s documentation says to use WASAPI.
I am on Windows 11 Pro 64-bit 24H2 and Cantabile build 4218. Any thoughts on what is causing this error and how to fix it?
However, I am glitching more with WASAPI than I did with ASIO4ALL at the same buffer sizes (144 or 192). Any ideas on how to optimize the WASAPI driver for Cantabile? Is there a third-party WASAPI control panel app that lets you adjust settings, similar to ASIO4ALL?
…OR is there a better alternative to ASIO4ALL in cases where the USB audio interface does not have its own proprietary driver?
Figured out the glitching problem with the WASAPI driver. The Omen Gaming Hub app on my HP laptop was somehow interfering with the WASAPI driver. I uninstalled the app and now WASAPI is running great at a buffer size of 144 with no glitching and negligible latency.
@dave_dore if I disable the Shared Mode checkbox in Cantabile, I get the error message I noted in the OP and the audio engine fails to start.
Edit: I installed a GitHub driver called ASIO2WASAPI, which does have an exclusive mode option. I verified that no other app can use the audio device when using the ASIO2WASAPI driver in Cantabile. So maybe that is my best option. I’m getting 5ms latency with a buffer size of 240, which is about as low as I can go without glitching.
