Thanks Dan, that is quite informative!

> We are absolutely committed to improving audio support.

Great to hear that!

> You can find the javax.sound code, as it currently exists, in the open
> source tree at </platform/dalvik/libcore-disabled/>.

OK, at 
http://android.git.kernel.org/?p=platform/dalvik.git;a=tree;f=libcore-disabled

> When Dianne said...
>
> > Contributing patches would be a much more effective approach than a 
> > petition.
>
> ...the specific patches she presumably meant would be patches to make
> this as-yet incomplete code into a stable, usable, library.

My concern is that at its lowest level javax.sound too is mostly
hampered by Android MediaPlayer being a "more or less stand-alone and
closed-source native application" that communicates with Android
through a too limited set of methods and data structures (e.g.,
files). In that case even a perfect javax.sound implementation at Java
level still does not help to solve our current problems. BTW, I'm not
too fond of javax.sound myself because of its rather complexity/
functionality ratio, so I personally do not push for its
implementation and support anyway.

> There is nothing that you could have done using the javax API, as
> implemented, that you couldn't have also done using the
> Android-specific API

Or I suppose also vice versa, what cannot be done with the Android-
specific API (in terms of in-memory work) could also not be done in
javax.sound, because the implementation bottleneck is mostly in the
low-level interface with the native MediaPlayer engine, which lacks
shared memory features (e.g., for direct access to audio buffers) for
concern about possible security issues?

For me a major step forward would already be when the Android-specific
MediaPlayer API for setDataSource() gets extended with methods that
accept a byte array (or stream, or other in-memory data structure) as
its argument - plus of course the low level implementation to make it
interface with the native MediaPlayer engine. I cannot see in media/
jni/android_media_MediaPlayer.cpp what degrees of freedom
process_media_player_call() offers through its arguments, and none of
this seems described in public documents? This may cripple third-party
development of those proposed "patches". Maybe I see things too
gloomy? I stand corrected!

Thanks


On Nov 20, 8:07 pm, Dan Bornstein <[EMAIL PROTECTED]> wrote:
> On Thu, Nov 20, 2008 at 6:10 AM, Robert Green <[EMAIL PROTECTED]> wrote:
> > That's very unfortunate.  iPhone has one up on the android in this
> > arena.
>
> There are two separate questions here, I think. One is about improved
> audio support. The other is about whether that support will come in
> the form of an implementation of the javax sampled sound API.
>
> We are absolutely committed to improving audio support. There already
> are Android-specific classes and methods for a lot of audio-related
> functionality, but we know full well that there is much more that
> could be done. You can safely expect to see us continue to improve the
> Android-specific API.
>
> We did have a go at implementing javax.sound for 1.0, but effectively
> due to time constraints, we were not able to bring that code up to
> production quality. So, rather than ship an "attractive nuisance" that
> would have caused developers pain, agony, and suffering, we decided
> instead that the platform API would be better off without it, for now.
> There is nothing that you could have done using the javax API, as
> implemented, that you couldn't have also done using the
> Android-specific API; the difference is more that porting pre-existing
> code would have been easier if the more standard API were in place
> (and if it worked as expected).
>
> You can find the javax.sound code, as it currently exists, in the open
> source tree at </platform/dalvik/libcore-disabled/>. When Dianne
> said...
>
> > Contributing patches would be a much more effective approach than a 
> > petition.
>
> ...the specific patches she presumably meant would be patches to make
> this as-yet incomplete code into a stable, usable, library.
>
> -dan
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to