Its not slow. My loop sequencer app does such and can mix 10 tracks of 44khz stereo data no problem. The only "problem" on android is the buffer sizes are never small enuogh for real time play. That's the only real issue, which I doubt will be solved by simply allowing g native access. Something g deeper has to happen for that fix. Right now the ndk is more than fast enough to play data
On Aug 13, 11:59 am, Kevin Duffey <[email protected]> wrote: > To clarify what I meant by C being the choice over Java for Android.. > I simply meant that in order to compete with iPhone on their native > games and audio applications (BeatMaker, other synth apps, etc), once > Google provides us with OpenAL (or something similar??) and better 2D/3D > video access to the underlying hardware via APIs, You'll see a lot more > C code in games and music apps than Java. I am not saying it will all go > that way.. you still need the Java to get things rolling. For most apps, > and even quite a few game varieties, I think Java is the way to go. > > I just wish it was already available. Hopefully 3.0 will usher in the > native audio/video support that iPhone developers enjoy and we'll > finally be able to make multi-touch music apps for Android. I know that > BeatMaker alone was responsible for 1000's of iTouch sales, and the app > was $20 to boot. There is a lot of potential, especially with the larger > tablet screens, for really robust music apps, as well as much better > games, once we have these capabilities. I am sure this will be available > at some point.. I just wish it was sooner than later. Having to pass > audio buffers back up through JNI to be played is very slow and > limiting. I wont exclaim to be an expert tho.. I've not yet had the > pleasure of working with NDK, but I did buy a book and read some > articles on it's current limitations. > > Hence, why I said what I said. > > On 8/13/2010 2:35 AM, Ralf Schneider wrote: > > > > > I forget! There is hope: NaCl is doing it right (IMHO)! > > May be Android will one day get fast apps via PNaCl > > (nativeclient.googlecode.com/svn/data/site/pnacl.pdf > > <http://nativeclient.googlecode.com/svn/data/site/pnacl.pdf>) > > > 2010/8/13 Ralf Schneider <[email protected] > > <mailto:[email protected]>>: > > > I was just pointing out a logical flaw in another post: The poster was > > > defending Java and in the last part he suddenly told: C will rule > > > Android development as soon as there is video and audio access via the > > > NDK > > > > Actually I agree. For: implementation, maintenance, and debugging ... > > > Java is far better than C or C++. > > > > But, performance matters, too! Not for most Apps, but for many of the > > > interesting ones (Games, AR-Apps, Image recoginition, ...). > > > > Anyway these kind of discussions most time lead to nowhere. There is > > > already too much (programming) religion involved. So it's easier to > > > just troll around. > > > > My personal opinion is this: > > > I would prefer a complete and stable C API. => Android should be a set > > > of stable C-APIs > > > Java/Dalvik/.net/whatever can run on top of them. > > > > So, everybody can be happy. The Java coders, the Python coders, The > > > C-hardcore-coders... > > > > 2010/8/13 Dianne Hackborn <[email protected] > > <mailto:[email protected]>>: > > >> On Fri, Aug 13, 2010 at 1:34 AM, Ralf Schneider > > <[email protected] <mailto:[email protected]>> > > >> wrote: > > > >>> If Java is so great, why will the NDK(C/C++) become the language of > > >>> choice - as soon as google provides a useable API? > > > >> The language of choice for what? Not most app developers. Except for > > >> certain apps, Java is going to be a far better choice for ease of > > >> implementation, maintenance, and debugging. > > >> -- > > >> Dianne Hackborn > > >> Android framework engineer > > >> [email protected] <mailto:[email protected]> > > > >> Note: please don't send private questions to me, as I don't have > > time to > > >> provide private support, and so won't reply to such e-mails. All such > > >> questions should be posted on public forums, where I and others can > > see and > > >> answer them. > > > >> -- > > >> You received this message because you are subscribed to the Google > > >> Groups "Android Developers" group. > > >> To post to this group, send email to > > [email protected] > > <mailto:[email protected]> > > >> To unsubscribe from this group, send email to > > >> [email protected] > > <mailto:android-developers%[email protected]> > > >> For more options, visit this group at > > >>http://groups.google.com/group/android-developers?hl=en > > > -- > > You received this message because you are subscribed to the Google > > Groups "Android Developers" group. > > To post to this group, send email to [email protected] > > To unsubscribe from this group, send email to > > [email protected] > > For more options, visit this group at > >http://groups.google.com/group/android-developers?hl=en -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
