wasapi not good.
Stand alone? What happens exactly? It should be the same as in Enterprise and I didn't see anything weird here. Is this beta006 specifically or also 005?
Standalone, both beta 5 and 6. Input seems fine, but as soon i select it on Normal Output it shopping sound constantly. Strange since input sync seems fine. Also i see it makes huge underflow on VAC cable.
KS is ok.
So, the buffer filling looks ok? Increasing the buffer size doesn't help? I need to ask because I see no issue here, so I need to figure out what's different. Have you ever used this in previous Enterprise builds? If not, there might just be some difference in how the sound card is opened (things like block size, exclusive or not).
Also noticed that with wasapi it opens cable to 24bit and MME is opening it at 16bit.
I think that that's normal? Is that different from before? MME does whatever Windows' mixer does - so what's configured in Windows. KS and Wasapi overrule the defaults.
For some reason on XP it does not write ini. It does not remember last state after ST restart.
Huh. That's weird. Will look into it.
Note: On my end, the Winamp build with the new GUI crashes on startup. I'll try to investigate and fix that too before running a new build.
Edit: I think I may have found something suspicious, but I'm at home now and I cannot easily test if I'm right (I want to test it on a lot of sound cards and be able to hear the output). But I think I found a difference in the block size that's used between the old and new code, and the could very well explain this issue - and maybe also why the latencies are different with the new I/O layer. The old code seems to let the sound card determine which size it wants (it uses "unspecified" by default, unless you override the size in the GUI settings). The new code has size 1024 hard coded, ignoring any GUI values. So that's definitely wrong.
On most sound cards this doesn't cause issues, which explains why I didn't notice it. If you use the older versions (with the old I/O framework) and set the block size to 1024, you should get the same behavior.
I will probably fix this on Monday when I can properly test it (unless I get bored during the weekend and go to the office to test it there
Edit #2: I see that on XP, the settings are saved, but the file name ends at .NEW, so for example C:\Documents and Settings\username\stereo_tool.ini.NEW . Remove the .NEW and the settings are loaded... There's some code to avoid loosing settings if something goes wrong (think a disk full error), which apparently doesn't completely do what it should. All of a sudden. Do you have any idea when this broke?