On Sat, Jan 14, 2012 at 11:45 AM, Brad O'Hearne <[email protected]> wrote: > 1. Adjust or disable entirely caching and buffering within the MediaPlayer. > > 2. Tell the MediaPlayer to ignore any processing for audio, which is not > needed in this use case. > > 3. Potentially be able to control or monitor the network transport of the > stream (much less important than #1). > > 4. It would be great to be able to get some statistical data on what part of > the pipeline latency exists: network transport, buffering, decoding, > rendering, etc. (again, much less important than #1).
AFAIK, nothing of what you seek is supported from the SDK. I haven't checked out the NDK's ability to work directly with the screen recently -- I know it can do OpenGL, but I'm not sure if a "push buffers"-style approach is possible. If it is, you might be able to use the NDK to roll your own streaming mechanism that meets your requirements. Also, if this is for custom hardware, all you seek should be possible via custom firwmare, albeit perhaps sans much documentation. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training in NYC: http://marakana.com/training/android/ -- 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
