4 ms·
You can develop apps in C/C++ with the NDK, cutting out Java almost entirely and avoiding its associated latencies. This is what all serious games do. However,
by nneonneo 8y ago
You can develop apps in C/C++ with the NDK, cutting out Java almost entirely and avoiding its associated latencies. This is what all serious games do.
However, the lack of a widely-supported low-latency audio stack is still a killer.
- romwell 8y agoAndroid Oboe[1] might fix that (an API that goes through (OpenSL ES or AAudio depending on what is available). Then, in future far, far away we might get a touch input method that isn't too laggy for interaction with audio. Last year, the best we could get was around 30ms[2] on iSomething; and I hope that 120hz refresh rate becomes the standard (but even that is huuuuge compared to a MIDI controller). [1]https://github.com/google/oboe https://github.com/google/oboe [2]https://www.reddit.com/r/Android/comments/7teiwe/lets_discuss_touch_latencyaccuracy_on_flagships/ https://www.reddit.com/r/Android/comments/7teiwe/lets_discus...