"The platform provides a software implementation of Khronos OpenSL ES, a standard API that gives applications access to powerful audio controls and effects from native code. Applications can use the API to manage audio devices and control audio input, output, and processing directly from native code"
But will this make enough difference to start to bring audio developers into Android in the same way as iOS?
I'd really like to hear some developer's opinions on this if possible. What do you think?
9 comments:
Not until Android users are willing to display a desire to pay for apps or Guitar Center (and others are willing to support music apps through advertizments.
So many folks who jailbreak the iphone or use Android phones brag all the time about the "free" pirate goods on their phones as well. Or at least the lowlife musician crowd I meet.
Gee someone's bitter.
re article: about time!
IOS now has CoreMIDI, but what will that mean?
Why do you always asks those kinds of question when it comes to new features on other systems than IOS?
First of all why does Android have to be the same as iOS? If you want iOS just buy an iOS device. Don't think of Android as the iOS' ugly step-sister. In spite of their external and surface similarities Android is a very different beast from iOS in terms of so many things -- connectedness, multitasking, app interoperability, license compatibility, availability of OSS, third-party and community-supported tools, form-factor options, monetization options and marketplaces. The list goes on.
Audio improvements at the native level, the audio effects and new media codecs are welcome additions to the platform.
Thankfully, what makes it at Guitar Center doesn't define the world music tools.
Johnny, I ask the question because I'm really interested in where Android goes. My experience with it hasn't been amazing so far, but I think it has a lot of potential as a mobile music platform, and when I hear stuff like this about native audio I really want to find out what it means and if it will move Android mobile music forward.
As long as it looks like 90% of the current devices on the market won't ever see an Android 2.3 update ever, the question about better audio in 2.3 is quite an obsolete question.
And (@Garloo) I NEVER pirated an app, not for iPod nor one for my Milestone. I even bought some music apps on my Android. And except Elektrum Drum none of them has seen an update to make them working correctly in months (esp. Jasuto which makes me quite angry)! That's what paying customers get as a reward!
The lack of music related apps/toys/one trick ponys for my Milestone actually made me program my own little 'noise' toys with the crap that they call App Inventor... Just to point out how desperate the situation for musicians with an Android device is these days ;)
Note, "software implementation" of OpenSL ES. This sounds like it won't have the low latency and control that CoreAudio has. I can't be 100% sure, but with OpenGL ES on the iPhone, your instructions run on the hardware GPU. A software implementation sounds like an emulation layer, meaning your instructions will be translated from OpenSL ES to native code prior to your audio being rendered. These steps will increase the minimum latency.
If the latency can be kept down below 10ms, then it might be acceptable. The big win is on the coding end - the capability to perform DSP generation and audio processing.
I trust you genuinely wonder if those kind of changes will get the platform where you'd like it to be, but the way you say it sounds like "but whatever will that mean, yawn".
@dcp
"made me program my own little 'noise' toys with the crap that they call App Inventor"
Mand I'd love to be able to do that on IOS, and not have to get a Mac only to use the IOS SDK, and then pay Apple to be able to use my own apps on my device. Really, if I could do that on IOS I would never buy an app ever!, .. or very rarely :)
oops, forgot to put @palm-sounds on top of my post.
Post a Comment