I’m working on an interactive audio app and I’m trying to use the WASAPI drivers (as opposed to DirectSound) to get good performance.
One problem I’ve noticed, though, is that you can’t open a full-duplex WASAPI audio device in Juce unless the input and output sample rates match in the Control Panel.
My app is targeting users who probably won’t know how to access those settings, so I’m trying to make it work even if the sample rates are different.
Anyone dealt with this issue before? Jules, any plans to handle this case?
Here are some strategies I thought of:
- Change the WASAPIAudioIODevice classes (inside JUCE) so that one AudioIODevice can have different sample rates for input and output, and one is resampled to match the other somehow. The buffering would be tricky.
- Have two different AudioDeviceManagers in my app, each of which handles only input or output, and try my best to synchronize them somehow with my app code.
Any thoughts, suggestions, ideas appreciated.