Reply 100 of 161, by mirh
So.. I guess like I missed the right time window for a proper reply, so I'll just try to keep this short.
If you want to develop with WASAPI (or XAudio2) out of personal interest that's a thing, you just have to say it and I'm fine.
Otherwise, I already underlined how "open" is really the least of my practical points. I don't want these to be conflated with the usual ideological, technical-poor ones.
Then, gosh, I guess like for two totally unknown people to collaborate some way, at least one of them has to have code somewhere in the wild to "trust the other", but this is an aside.
I got in touch with Chris eventually (hence [part of] the delay).. And there doesn't seem to be any intrinsic "added" requirement to specify buffers.
Furthermore for as much, yes, the "audio chain" would get conceptually lengthened, there's no indication of any significant penalty in latency (I have read on dolphin git that, with a X-fi, you can nonchalantly get down to 6ms for example)
And concluding, seriously, he seems as much available as humanly possible (he even came here to answer), and he already expressed in the past a vague desire to get EAX reimplemented - just not a work he'd do in first person.
If he saw a PR, it certainly wouldn't be rejected as out-of-scope. Imo.
But again, your call.