[Bug 753751] Dashdemux: returned seekable range for live streams is not usable

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=753751

--- Comment #85 from Vincent Penquerc'h <vincent.penquerch at collabora.co.uk> ---
(In reply to Sebastian Dröge (slomo) from comment #81)
> (In reply to Vincent Penquerc'h from comment #77)
> > (In reply to Sebastian Dröge (slomo) from comment #73)
> > > Comment on attachment 332132 [details] [review] [review] [review]
> > > allow seeking before start in live streams
> > > 
> > > Not sure if this is the nicest approach. We basically will shift stream time
> > > 0 into the future now to make the current seek start position 0. And if
> > > there is yet another seek to an earlier point, it will shift 0 again. That's
> > > very confusing from a user point of view.
> > 
> > It's the seek target that's being modified, so it behaves as if the seek had
> > originally been to dt after the actual target.
> 
> Can you explain? How does this look exactly from a user point of view, maybe
> with an example?

A program using gst decides to seek to the beginning of the current valid
range, and the range it thinks is current is 74 to 259. It will ask to seek to
74. The patch requests the current range, and sees it's now 75 to 260, so
adjusts the requested target to 75, and seeks there instead.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.