Question

I’ve been experimenting with making an android app for the past week or two and have reached a point where I need to decide on a general plan of action concerning the code I’m writing.

started with SoundPool, easy to use, not very flexible. went on to AudioTrack, seems good but slow.

So now I’m looking at the ndk..
Does the ndk have direct access to AudioTrack? or something else?

What is the general concensus on this kind of thing?

A guess is to make the UI in java and the ‘sound engine’ in C++

I’d like to get started on the right track before I write too much.

edit:

It is a music studio that plays and manipulates wav files from the sdcard as well as realtime sound synthesis.

Answer 1

There are a ton of Audio Latency issues in Android. There’s really not anything that can be done about it. It seems like ICS (4.0) may have done some improvements on it, from what I’ve read.

You could subscribe to Andraudio and you’d actually be better off directing Android Audio questions through their emailing list than through Stackoverflow:
http://music.columbia.edu/mailman/listinfo/andraudio