[Bug 752085] dashdemux: revert changes introduced in fix for bug 751850

[GStreamer (GNOME Bugzilla)]

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

Thiago Sousa Santos <thiagossantos at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |thiagossantos at gmail.com

--- Comment #18 from Thiago Sousa Santos <thiagossantos at gmail.com> ---
I guess you already figured it all out, but just some clarification:

Segment == fragment here, I guess the mismatches are because the different
specs (HLS/DASH/MSS) calls them differently and the naming got mixed when doing
the API.

the segment_index is the 'next' fragment to download, meaning it is initialized
at 0 because get_next_fragment will return the next fragment to be downloaded.
It is just one logical way of thinking, it could also be named the current
fragment if we changed all the function names. I'm ok if you wanted to change
to make it more clear.

When at the last fragment, advance_fragment() should increment the index (or
decrement if reverse playback) and, as it is out of the fragments range, return
EOS in this case.

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