Planet Griff doesn’t think too much of Android’s ability to cater for mobile music making. This is largely based around the fact that apps for Android are java based which is generally to slow to do anything too creative.

It is a shame really as Android is open source. Perhaps Google will do something with it in the long run. Who knows.

tags technorati :

One comment

  1. I beg to differ. Java is perfectly capable of handling all aspects of digital music production. Because it runs in a virtual machine, load times can be increased as the virtual machine is loaded, but actual application performance is no different than C or any other byte compiled language. If all the other applications for Android are written in Java, then the virtual machine will already be resident in memory and load times will be indistinguishable from any other language. Long story short. Performance is not an issue for Java.I would point to JSyn (http://www.softsynth.com/jsyn/) as an example of real-time audio synthesis in a purely Java based environment.I’m certain processor specific modifications will be required, but it will not be an insurmountable challenge to modify JSyn, or develop a new real-time audio synthesis API for Android. All manner of other music applications already exist in Java form.Google is right to embrace Java. Plus Android is built on linux, so there’s no reason C code won’t execute on it, just as there’s no reason for there to not be a JavaVM for the iPhone, but Apple is blocking Sun from implementing it.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.