High + Low Level API Clarification

[Eecornwell]

In the documentation, I do not see any clear boundaries between using both the low and high level api's concurrently (besides possibly device registration). Because your audio engine includes a spatial feature, I would like to use the engine for playback and use the low level api to get microphone data. I have the audio engine (spatial audio playback) working great inside of Unreal using a sound file saved locally. What I would like to do is use the low level callback to feed the engine the sound data. Is this even possible?

[mackron]

The high and low level APIs are completely decoupled and can be used simultaneously. You can use ma_engine for your playback stuff, which is part of the high level API, then use ma_device for your capture stuff (this being the low-level API). You can then save the captured audio to a buffer and then play it back through the engine. Getting the data movement from the capture side to the engine will be the most annoying part as it might require a bit of fiddling because you've got two separate threads interacting with the same buffer (the capture side and the engine side), but it's absolutely possible to do what you're after.

[mackron]

Further to this, I was thinking this was an interesting use case and the kind of thing some people would benefit from. I've gone ahead and added a simple example to the dev branch. It's not the most robust solution possible, and if you're wanting something more advanced you would need to adjust for that, but at the very least it shows you that it's possible and might give you a starting point.

The example is currently only in the dev branch: https://github.com/mackron/miniaudio/blob/dev/examples/hilo_interop.c

[Eecornwell]

This is perfect! Thank you for the well written example, code, and documentation! I will definitely be using this.