szantog

5 ms·

1. 1.▲
   by szantog 10y ago

   I'm one of the authors of the article, and the CTO of Superpowered. I apologize if the article was confusing. Marshmallow improves audio latency here and there on some devices, but even Android N has the fundamental audio stack problem
2. 2.▲
   by szantog 10y ago

   "We updated our findings with the recent improvements in Android M (Marshmallow), and recently released a solution for Android’s USB audio and MIDI challenges, opening a market of 1.1 billion devices for pro audio application creators.
3. 3.▲
   by szantog 11y ago

   Android's audio stack is "pushing" audio down to the audio driver, with the audio threads sleeping between every push. In other words, the audio driver's interrupts are not scheduling the actions. Having smaller period s
4. 4.▲
   by szantog 11y ago

   ALSA is super. The HAL connecting ALSA to AudioFlinger is the major problem, plus the audio stack's "push" philosophy.
5. 5.▲
   by szantog 11y ago

   All of the measurements and the latency graph shows you a pure NDK implementation.
6. 6.▲
   by szantog 11y ago

   They did not forgot to write nice professional audio and music tools for Android. They can't, because of audio latency and dropouts.
7. 7.▲
   by szantog 11y ago

   Audio Flinger is not Java. On the graph you see absolutely no part which runs on Java. Android's media architecture with it's "push" design is not more compatible than anything else with a "pull". The many laye