Latest WACUP public preview for x86 & x64 is build #24496 (May 8th 2026) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #24496 (May 8th 2026) (x86 & x64 changelogs)

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Alex/AT

Pages: [1]
1
Some more information: push mode seems to work sometimes, but it needs few WACUP restarts to happen so.
If pull mode is used (pull never works), and then changed to push and back instead, push also never works.
If push is working after WACUP restart, it continues working until closed. Changing to pull once fails it until next working restart.
So it seems to be a matter of some timing issue / deadlock / stale lock / handle loss happening somewhere at initialization or close to it.

2
Any chances there is some debug logging that can be enabled to see what happens during YASAPI inner workings maybe?

3
There are some crashes sometimes when I try to enter YASAPI configuration page by clicking on plugin from Output page.
If I enter it from the Output menu at the left, no crashes happen.

Plugin test result:
#24496, #24472, #24360, #23960, #23528, #23410, #23234 (DLL size 52224) - not working
#22982, #22656, #22626, #22278, #22222, #22022, #21640, #21622 (DLL size 51712) - not working
#21136, #21102 (DLL size 52736, same as in 20202) - NOT working
#20202 (DLL size 52736) - WORKING
#20088, #19994, #19516, #19100 (DLL size 52736, same as in 20202) - working
#17040 (DLL size 49664) - working

That's based on just specific .dll version testing in #24496 (replacing the DLL with DLL from build being tested).

To make sure it's not dependent on some API/ABI, I also tested #23234, #22982, #21622, #21136, #21102 as portable builds.
None are working properly, although #21136 and #21102 seem to work in Push mode (I normally tested Exclusive/Pull).

So obviously something happened between #20202 and #21102 there. It's kind of strange given DLL seems to be the same between 20202 and 21136/21102 though. Other video/audio players (AIMP, MPC-HC) work in Exclusive/Pull(Event) mode just fine.

4
Failing version of plugin also reports strange buffer usage (see the attachment). Ring buffer is filled just a little, and shared buffer is not filled. And this is static - it does not change at all. It seems playback thread either hangs or aborts somewhere (may be wrong of course, no knowledge about the internals :) ).

5
x86 specifically. I also tested x64 indeed, but it exhibits the same behavior.

Yes, other output plugins all work. Just WASAPI one is bugged. WASAPI one does not work when passed through Neo Mixer plugin either.

6
Preview Build Discussion / Issues with build #24496 (May 8th 2026)
« on: May 12, 2026, 07:40:08 AM »
Let's start with something...

No So Yasapi output stopped working in this build. Windows 11, Creative AE-9. Tried push/pull, shared/exclusive to no avail.

Playback just skips tracks without any sound. Stop 'hangs' for several seconds, then either stops or just continues skipping tracks. Sometimes (once in a couple of start/stops it either shows buffer playback loop condition (same small piece repeating without updating), or plays one track then returns to the above behavior.

Downgrading out_notsoyasapi.dll to the one from build #20202 (not exactly specific bugless version, maybe some later ones also work, but this is just the one I have archived) immediately makes it work. If there's a way to download older builds, I can easily test each one to find in which build exactly it stops working).

Pages: [1]