[Bug 767071] qtdemux: Various SEGMENT event related fixes, including regression fixes

[GStreamer (GNOME Bugzilla)]

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

--- Comment #11 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
(In reply to Thiago Sousa Santos from comment #10)
> Review of attachment 328807 [details] [review]:
> 
> dash should default to creating a 'dummy segment' that has its stop time
> updated and increasing when new data is parsed. So what happens here is that
> the segment isn't activated as the stop-time is still too small if you seek
> forward to a fragment that isn't available yet.
> 
> Forwarding the segment directly for fragmented would work, but I think just
> doing it when dummy_segment == true would cover more cases. Also it worries
> me a bit that validate didn't catch any of these issues, will check what
> tests are missing there.

What's dummy_segment and how is that supposed to work? The problem here is that
adaptivedemux will have to push a SEGMENT event for the seek, and only after
that it can push the new moof from which qtdemux would know that there is
actually data available at the segment start.

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