ooh thats an interesting idea.
On Jan 2, 9:32 am, Dave Sparks <[email protected]> wrote:
> I haven't looked at imeem, but one way to get around the issue is
> using an HTTP proxy on the device. The proxy server could be buffering
> up the next stream while the current stream is playing.
>
> On Dec 30 2008, 11:37 pm, Dan McGuirk <[email protected]> wrote:
>
> > Hi,
>
> > I'm wondering if anyone knows how the imeem application is handling
> > its streaming audio. It seems to be able to buffer the entire track
> > as quickly as possible, as well as buffering the upcoming track before
> > it is played.
>
> > As far as I can tell from reading several other threads here, that is
> > only possible by writing the track to a file and then pointing the
> > media player at the file. But I'm watching df pretty closely and I
> > don't see the space used on any of the partitions going up as it
> > buffers. Is the data hiding somewhere?
>
> > Another possibility that was raised was that you could do this using a
> > file descriptor associated with a socket, sort of like in this
> > example:
>
> >http://groups.google.com/group/android-developers/browse_thread/threa...
>
> > But apparently this doesn't work--I'm guessing maybe because the
> > MediaPlayer tries to seek on the fd to determine its length?
> > (Guessing based on its behavior with normal files that are appended to
> > after it starts playing.)
>
> > Is there some other possibility? Obviously the imeem folks have it
> > working well somehow, but I don't quite get how. Some of the other
> > threads I've read seem to be telling me this isn't quite possible
> > (links below).
>
> > If I just pass URLs to MediaPlayer one after the other in the normal
> > way, there's way too long of a delay (10+ seconds) between tracks.
> > That's too long; long enough for the user to start thinking, "Why
> > isn't this working?", pick up the phone and double-check it, etc. So
> > I need some way to start buffering an upcoming track in advance (maybe
> > create a second MediaPlayer and call prepareAsync() early... although
> > this seems messy, and it can't be what imeem is doing).
>
> > Thanks for any help.
>
> > Related threads:
>
> >http://groups.google.com/group/android-developers/browse_thread/threa......
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
