Android Audio: Beyond Winning On It
summary
Android still lacks a native audio‑plugin framework like Audio Unit v3, which blocks DAWs from hosting third‑party instruments; latency is largely solved (pro audio CDD targets ~20 ms round‑trip, many devices <20 ms) and Android offers AAudio/Oboe, MIDI 2.0, Jetpack Media3 and new in‑process codec loading in Android 16. Hard limits: Play Store forbids loading arbitrary native libs, IPC plus UI hosting needs SurfaceControlViewHost (Android 11), and real‑time priority inheritance remains platform‑restricted. Experimental plugin hosts and cross‑platform C++/WebAssembly workarounds exist but are incomplete.
AI-written summary · about
chapters (11)
- 0:00Android audio challenges
- 3:30Android vs iOS audio lag
- 7:10Audio latency in Android
- 9:19Java vs C++ for audio
- 11:28Android missing audio plugins
- 15:07Audio plugins importance
- 20:37Audio plugin technical hurdles
- 26:38iOS audio plugin solution
- 29:12Android real-time limits
- 33:56Solutions for Android plugins
- 36:47Summary and future steps
related talks
17mA Brief History of Real Time Audio (or Wasn’t That API Deprecated?)
39mDemystifying Low Latency Audio on Android
26mUnderstanding and Implementing Audio on Android
16mUnderstanding and Implementing Audio on Android
40mAccessible audio: Android hearing aid support and the audio framework
20mLow latency Audio - because your ears are worth it
40mHigh Performance Audio
42mLet's make some noise with Android
