dashdemux: include segment duration when calculating seek range
authorAlex Ashley <bugzilla@ashley-family.net>
Wed, 24 Feb 2016 15:54:54 +0000 (15:54 +0000)
committerVincent Penquerc'h <vincent.penquerch@collabora.co.uk>
Tue, 2 Aug 2016 11:52:34 +0000 (12:52 +0100)
commitd9bcf4dbd93df05255feb6f52dec68dbe13622ac
treee207b63a7399155cd6c7773f6640cffa9b27d23e
parent535f10b61d0c45c8e7f73de298432b5e97385e05
dashdemux: include segment duration when calculating seek range

The gst_dash_demux_get_live_seek_range () function returns a stop value
that is beyond the available range. The functions
gst_mpd_client_check_time_position() and
gst_mpd_client_get_next_segment_availability_end_time() in
gstmpdparser.c include the segment duration when checking if a segment
is available. The gst_dash_demux_get_live_seek_range() function
in gstdashdemux.c ignores the segment duration.

According to the DASH specification, if maxSegmentDuration is not present,
then the maximum Segment duration is the maximum duration of any Segment
documented in the MPD.

https://bugzilla.gnome.org/show_bug.cgi?id=753751
ext/dash/gstdashdemux.c
ext/dash/gstmpdparser.c
ext/dash/gstmpdparser.h