WASAPI and ASIO feedback

[Captain Planet]

Great to see some active development of winamp.
For me its still the greatest music player out there for a number of reasons:
Small footprint
Bit perfect playback
Simple navigation for folder playback (press insert, arrow keys to navigate to folder, hit enter, job done)

I'm still using winamp 5.8 daily but the wasapi output is a bit flaky at times, although ASIO works fine

Onto the WACUP preview and i've noticed that:
The ASIO output is working, although enabling volume control doesn't do anything except off/full, and for that the system volume control had to be used.
The WASAPI output doesn't seem to work for me at all, I get an error message 'error connecting : "yasapi_player.c" (953).' So any suggestions for this would be welcomed.

Keep up the good work, lets hope winamp will still be around for many years to come.

[Captain Planet]

After further experimentation the WASAPI error only seems to occur in shared mode. In exclusive mode its now playing ok.
A further observation using the WASAPI output is the visualisation within the main skin window (e.g. spectrum analyser) doesn't appear to be fully working and just rolls from left to right and back. Pausing and then unpausing the track results in the visualisation starting to work...until the end of the track, then off again until paused/unpaused.

[dro]

Great to see some active development of winamp.

Not seeing that as this is it's own thing

ASIO direct volume control was experimental & is hit&miss on how well it works. I will have to come back to it as I might have a solution that'll work based on something else I've been working on recently. However ASIO even working for you is a surprise as that mode is the most unstable from my testing.

The visualisation issue with NotSoYasapi is known & I've just not gotten around to trying to work out what's going wrong with it (it's not my favourite of plug-ins tbh). The point it's throwing an error is when it's trying to create the player so if it's failing in shared mode then it might be something else already has exclusive access? I'll need to add some more information to that failure so it's easier to determine what is actually happening.

-dro