Stephen Lau wrote:
I'm noticing a problem (on my Android 2.1 test devices) where if I use
MediaPlayer and have it start playing a stream and then try to seek to a
point past where it buffers, the player gets out of sync.
I would expect it to issue a new HTTP GET from the server with a byte
range offset corresponding to the approximate location I'm seeking to
(since the content length is known).
Instead the player starts playing from the end of its buffered point,
but reports back the progress (via getCurrentPosition) as if it were
playing from the requested seek point.
Example: I'm playing a track and the currently playing position is 0:08
while it has 0:30 seconds buffered. If I seek to 1:00,
getCurrentPosition() starts returning 60s, but the audio playing is
actually from 0:30.
Any ideas what could be wrong?
cheers,
steve
Nevermind.. turns out I was hitting Android bug 4124. Works fine on
2.2.. I'll just implement a workaround for <FroYo.
cheers,
steve
--
stephen lau | st...@grommit.com | http://whacked.net | @stevel
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
