[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 #313266|accepted-commit_now         |committed
             status|                            |

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

commit 21c6da6764c0cd015e9f3c5eecba36e297187deb
Author: Stavros Vagionitis <stavrosv at digisoft.tv>
Date:   Wed Oct 14 10:43:19 2015 +0300

    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.

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

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