[Bug 748316] hlsdemux: The end offset (range_end) of a segment is not calculated properly in the m3u8 parser

[GStreamer (GNOME Bugzilla)]

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

Sebastian Dröge (slomo) <slomo at coaxion.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #313245|needs-work                  |none
             status|                            |
 Attachment #313245|0                           |1
        is obsolete|                            |

--- Comment #40 from Sebastian Dröge (slomo) <slomo at coaxion.net> ---
Created attachment 313266
  --> https://bugzilla.gnome.org/attachment.cgi?id=313266&action=edit
souphttpsrc: Make non-inclusive segment boundaries inclusive

The problem is that the filesrc and souphttpsrc are behaving
differently regarding the calculation of the segment boundaries. The
filesrc is using a non-inclusive boundaries, while the souphttpsrc
uses inclusive. Currently the hlsdemux calculates the boundaries as
inclusive, so for this reason there is no problem with the souphttpsrc,
but there is an issue in the filesrc.

The GstSegment is non-inclusive, so the proposed solution is to use
non-inclusive boundaries in the hlsdemux in order to be consistent.
Make the change in the hlsdemux, will break the souphttpsrc, which
will expect inclusive boundaries, but the hlsdemux will offer
non-inclusive. This change makes sure that the non-inclusive
boundaries are converted to inclusive.

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