From 75897c2cbc49b77fa8a9399d33d1d1ab8fda8828 Mon Sep 17 00:00:00 2001
From: bicarus <202771338+bicarus-dev@users.noreply.github.com>
Date: Sun, 2 Aug 2026 20:47:22 -0700
Subject: [PATCH] Updated Asus Xonar AE (markdown)

---
 Asus-Xonar-AE.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Asus-Xonar-AE.md b/Asus-Xonar-AE.md
index 93c65c7..139d224 100644
--- a/Asus-Xonar-AE.md
+++ b/Asus-Xonar-AE.md
@@ -149,7 +149,7 @@ Try completely closing Sonic Studio from the tray icon and launch the game again
 
 For native ASIO supported games (newer IIDX and SDVX, GITADORA) this shouldn't happen - make sure you carefully follow the steps above, as they have been thoroughly tested by the community. Check the logs - if you see WASAPI initialization messages, then you did something wrong (possibly dirty DLL that is patched to use WASAPI and not ASIO).
 
-For other games that use WASAPI Exclusive, like Gitadora, pop'n, etc - this happens because these games are negotiating the minimum buffer size supported by the device (usually 3ms) and end up with buffer underrun. To fix this, try setting `WASAPI Exclusive Buffer Size (-exclusivebuffer)` to a reasonable number like `8`.
+For other games that use WASAPI Exclusive, like Gitadora, pop'n, etc - this happens because these games are negotiating the minimum buffer size supported by the device (usually 3ms) and end up with buffer underrun. To fix this, try setting `WASAPI Exclusive Buffer Size (-exclusivebuffer)` to a reasonable number like `10`.
 
 ## Running IIDX/SDVX results in no sound, slowing to a crawl, and audio completely dies after (ASIO crash)