4 ms·
Unfortunately it is not good. The current NDK integration is a dead end, we don't recommend using it, as we are working on a new version that use the native su
by krschultz 12y ago
Unfortunately it is not good.
The current NDK integration is a dead end, we don't recommend using it, as we are working on a new version that use the native support in Gradle.
https://code.google.com/p/android/issues/detail?id=73417 https://code.google.com/p/android/issues/detail?id=73417
- parkaboy 12y agoThere too goes the new low audio latency updates they were raving about out the window. As far as I can tell the NDK is needed for doing any real-time audio processing as you're forced into using a large 4096 buffer in the Java API (testing in Lollipop...) :/
- fidotron 12y agoYep. The entire rationale is that audio must be run on a thread which is never going to be GCed, and for that reason the low latency stuff only makes sense in the NDK.
- izacus 12y agoI think you hugely misunderstood the post. NDK is going nowhere, just the current Android Gradle PLUGIN support for compiling NDK code is a hack that will be rewritten in more Gradle native way. There is absolutely nothing stopping you from using NDK code with AS and Gradle.