[FFmpeg-trac] #1842(undetermined:open): Incorrect segmented HTTP Live Streaming playlists

FFmpeg trac at avcodec.org
Thu Nov 29 10:36:16 CET 2012


#1842: Incorrect segmented HTTP Live Streaming playlists
-------------------------------------+-------------------------------------
             Reporter:  teric        |                    Owner:
                 Type:  defect       |                   Status:  open
             Priority:  normal       |                Component:
              Version:  1.0          |  undetermined
             Keywords:               |               Resolution:
  segment,hls,m3u8                   |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------

Comment (by saste):

 Replying to [comment:4 brownard]:
 > The problem is that the segmenter doesn't correctly increment the #EXT-X
 -MEDIA-SEQUENCE tag as per the spec and I don't think the -segment-list-
 size works as the spec envisages.
 > The current behaviour is to completely empty the playlist when it
 reaches the specified size and increment the #EXT-X-MEDIA-SEQUENCE tag by
 1
 [...]
 > but the #EXT-X-MEDIA-SEQUENCE tag should be equal to the index of the
 first segment in the list, so in the example above the value in the second
 and third playlist should be 3 not 1 because the first segment in the list
 is the fourth overall.

 This one should be fixed.

 > What should happen is rather than emptying the playlist, the first item
 in the list should be removed and the new item appended so you have a
 "sliding window" with the #EXT-X-MEDIA-SEQUENCE increasing by 1 each time

 Current behavior is advertised in the docs as:
 {{{
  segment_list_size size
            Overwrite the listfile once it reaches size entries. If 0 the
 listfile is never overwritten. Default value is 0.
 }}}

 Now I see that having a sliding window seems more useful. Two questions:
 should the old behavior be retained according to you? How can the new
 behavior be enabled, if it has to convive with the old one? Also, in order
 to simplify discussion, I invite you to join ffmpeg-devel (but it is
 completely up to you).

 Another thing that you may want to check is the new hls muxer (but even if
 that works for you I'd like to fix the segmenter, which is a more generic
 beast).

-- 
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1842#comment:10>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list