- Thread starter
- #61
I think the drivers are a bit broken, since GetBuffer call to WASAPI is returning no error and still it manages to produce invalid buffer for the driver side that the actual audio data should be written. Good thing is that even MS thinks the GetBuffer should always provide a valid buffer since their example code is assuming that if no errors are reported the buffer will be valid.
In the mean time could you check if there are new audio drivers available and another thing would be to try a different audio chip if possible.
Please note this: I tried to install the wasapi plugin for FooBar2000 to test that kind of framework. It work .
I'm sure that WASAPI works on that card, but there still could be some bugs in the drivers that are just triggered audio renderer's code. Or it could be simply a bug in audio renderer's code, but it should do it on all HW. I haven't ever seen the GetBuffer call to fail and I have tested hundreds of hours of playback.
Here's the next version of that workaround. Now when the GetBuffer fails it will test 100 times to first release the buffer that was NULL and then request a new one. Every atempt has 5 ms period of sleep. Just lets see if the buffer will be available in the 500 ms period. If not I'm quite unsure what could be the next step to try.
I guess one thing could be to try to disable the WASAPIExclusive as disabled, if you haven't already tried it.