David Reid

I'm the author of miniaudio. The `ma_decoder` and `ma_device` objects are completely decoupled so whether or not the device is started should be irrelevant. One thing to consider, however, is...

I'm the developer of miniaudio, and I'm pretty sure this is due to a bad device configuration. The buffer size is way too small. I suspect this is the offending...

Oh, I didn't even notice that `aBuffer` parameter! So with the buffer size stuff, it's all up to the backend. It's technically just a hint - miniaudio will tell the...

I think that should do the trick. Did that fix your specific issue? Another thing that should be done at some point is to upgrade miniaudio because the version currently...

There's already a PR for that (not from me): https://github.com/jarikomppa/soloud/pull/294. Though that pull request itself is a bit out of date.

I don't use SoLoud myself (I occasionally scan it's issue tracker to catch potential miniaudio issues like this one) and there's no activity on this project at the moment so...

Yes, I'd be open to that. I have indeed done similar things to this for avoid including windows.h in headers. However, that said, the includes are done programmatically via the...

I was going to look into this one, but I don't think it's possible with vkbind's single file design. If, for example, the application does the following, it's going to...

I also thought of something like that, but is that portable across all different implementations of the Win32 library? As in, is it consistent with all versions of Visual Studio,...

The other problem however is if windows.h is included after vkbind: ```c #define VK_USE_PLATFORM_WIN32_KHR #define VKBIND_IMPLEMENTATION #include "vkbind.h" //