[Bug 764728] dashdemux: apply suggestedPresentationDelay to seek and seek range

[GStreamer (GNOME Bugzilla)]

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

A Ashley <bugzilla at ashley-family.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bugzilla at ashley-family.net

--- Comment #2 from A Ashley <bugzilla at ashley-family.net> ---
Changing gst_dash_demux_get_server_now_utc() to apply
suggestedPresentationDelay will change the segment numbers that dashdemux
requests. I think this is not a good idea.

The DASH standard does not mandate that suggestedPresentationDelay has to be
taken into account in the calculation of available segments.

To quote the DASH specification:

5.3.9.5.3 Media Segment information
For services with MPD at type='dynamic', the Segment availability start time of a
Media Segment is the sum of
- the value of the MPD at availabilityStartTime,
- the PeriodStart time of the containing Period as defined in 5.3.2.1,
- the MPD start time of the Media Segment, and
- the MPD duration of the Media Segment.

The Segment availability end time of a Media Segment is the sum of the Segment
availability start time, the MPD duration of the Media Segment and the value of
the attribute @timeShiftBufferDepth for this Representation.

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