I was having issues with WASAPI, and thought maybe it was just the screwy laptop I was using.
Now I’ve tried it on a bunch of different computers, and find that it is pretty universally problematic.
Primarily, when initializing a device, it always reports “the inputs and outputs have no common sample rate”.
This is using JuceDemo, compiling from the tip. I’ve seen this issue for months now.
Any idea when this might get addressed?
… and in my book this again is proof enough, along with the subpar general performance of the API, and the past experiences with DX effects and similar attempts by Redmond, that WASAPI is another failed attempt by Redmond to replace working technology with their “not made here” mentality.
@AaronLeese ASIO4ALL is pretty great, but not a total solution. Our app requires mixing the JUCE audio with system sounds/other apps and ASIO4ALL blocks that and makes our lives difficult. We’re also running into the sample rate errors though, as well as tons of latency through WASAPI since JUCE hasn’t upgraded to using IAudioclient3 for windows 10.