kcat

If Oboe is a normal/easy-to-get part of the Android ecosystem, it does seem to be a nice way to deal with some of the problems the OpenSL backend is experiencing....

Maybe, I'm not too familiar with Android development. From what little I do with it, I extract the NDK, and when building a CMake project (like Oboe) I set `CMAKE_TOOLCHAIN_FILE`...

> Their own guide (https://developer.android.com/ndk/guides/prebuilts) assume the library binaries are copied in the project you are building. > Isn't that enough though? I have to confess I have no idea...

Commit 0390828de06844514cde812e0475c6e1d338aad3 adds an initial attempt at an Oboe backend for playback. If the headers and prebuilt lib aren't visible to the compiler, you need to pass `-DOBOE_SOURCE=...` to cmake,...

> The latency seems considerably lower than the openes backend Part of that is likely because it's just taking the default buffer metrics for low-latency output, and ignoring OpenAL Soft's...

It should be written to the Android system(?) log, though I don't know how to get that with an emulator (it's been a while and I don't remember how to...

> And one more log, taken from a really crappy tablet (Lenovo IdeaTab A3000-H) How did that one perform? What was the test like (how many sources, were they or...

> Is there a way I can enable some form of "buffer health" reporting so I can give more detailed information about it? Not with OpenAL Soft specifically. You can...

Is there a documentation regarding what has changed and deprecated? Are there any recording examples for Oboe?

Commit 63f5240db253f0ea942a79da3a5f54e7338df493 adds capture support to Oboe. I haven't tested, and Oboe support in general is still considered experimental, but it's there to try out.