[MPlayer-users] Random behavior while seeking in flv over http
gautier.berthou at gmail.com
Thu Sep 2 11:44:28 CEST 2010
On Sat, Jul 31, 2010 at 6:03 PM, Reimar Döffinger
<Reimar.Doeffinger at gmx.de> wrote:
> On Wed, Jul 28, 2010 at 11:50:19AM +0200, Gautier Berthou wrote:
>> I'm reading a flv file over http with mplayer and I don't understand
>> mplayer behavior when I try to seek : some time it sends a get
>> request, some time it doesn't (it always sends one when I seek
> This depends on how far ahead the read request are and how full the
> cache is.
> If you made the cache large enough (e.g. larger than the file),
> even seeking back should not send a request, otherwise that's a bug.
OK so if I understand well if I want it to send a request a soon as I
want to jump forward I should put the cache as small as possible
>> And when it sends a get request the bytes range is not always the good
>> (it's the good when I seek backward) : I ask to seek to 85% of the
>> movie the byte-range asked look more like the current reading position
>> and then mplayer wait until the downloading reach 85% of the movie to
>> restart to read.
> I don't think MPlayer supports an index for seeking, so it just does a
> kind of binary search for the right position.
> When seeking backwards you probably mean to a part that was already
> played - in that case it put the position in the index and knows exactly
> where to go.
What do you mean by a kind of binary search ? In my case it just sends
a get request corresponding to the read-position before seeking and
then it waits until it receives the all the movie until the part it
I would not call that seeking, isn't it possible to have the same kind
of behavior as with a mp4 file with which mplayer send a get request
corresponding to the place I'm seeking ?
> MPlayer-users mailing list
> MPlayer-users at mplayerhq.hu
More information about the MPlayer-users