After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 678540 - hlsdemux: live streams starts at wrong segment
hlsdemux: live streams starts at wrong segment
Status: RESOLVED NOTABUG
Product: GStreamer
Classification: Platform
Component: gst-plugins-bad
git master
Other All
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-06-21 13:40 UTC by Gil Pedersen
Modified: 2014-02-23 10:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Gil Pedersen 2012-06-21 13:40:34 UTC 
A somewhat recent patch named "hlsdemux: In a live stream, do not start from 3 fragments before the end." from https://bugzilla.gnome.org/show_bug.cgi?id=674722 changed the playback starting point for live streams.
The spec doesn't define the segment at which a live stream should begin playback, however the CoreMedia based players from Apple starts three segments from the end and I don't see why gstreamer should suddenly start to behave any different.

I suggest the relevant patches (df958b4906ef8595f5006e9d97c484bb912fd757, bb9d1147b7c6e611541c0fecbfa2cfc4cfa48e78) are reverted to fix this issue.
Comment 1 shr 2012-12-17 09:21:21 UTC 
HLS spec does talks about from where the playing should start

http://tools.ietf.org/html/draft-pantos-http-live-streaming-10#section-6.3.3
6.3.3. Playing the Playlist file

   If the EXT-X-ENDLIST tag is not
   present and the client intends to play the media regularly (i.e. in
   playlist order at the nominal playback rate), the client SHOULD NOT
   choose a segment which starts less than three target durations from
   the end of the Playlist file.  Doing so can trigger playback stalls.
Comment 2 Sebastian Dröge (slomo) 2014-02-23 10:03:19 UTC 
Yes, I don't think this is actually a bug and we behave according to the spec here.