I believe the OpenCore HTTP streaming engine maintains a circular buffer of data. As data is played out, the buffer space it occupied is re-filled with new data. When you seek backwards in the stream, it has to re-fill the buffer from the earlier part of the stream.
On Jan 29, 1:05 pm, ed <edwin.fuq...@gmail.com> wrote: > I've been using androids MediaPlayer to stream from an http url and > have a question about seeking. Currently, our urls expire after they > have been used once or a certain time out has expired to dissuade > scraping content. Now, this obviously makes progressive streaming > past the buffer impossible with the exact same url as you need to open > a new http connection with the same mangled key, which we > intentionally don't allow. > > However, MediaPlayer seems to do this when seeking before the current > position (i.e. seeking from 1:00 in the audio to 0:30). As the file > has already been downloaded up to the current position I'm confused as > to why MediaPlayer is still trying to initate a new http connection in > this case? The only thing I can think of is that MediaPlayer is > getting rid of audio its already played up to the current position, > and hence needs to restart the connection if you try to seek back on > the stream. Is this correct, or is there something else going on? > > Thanks, > Ed --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
