[FFmpeg-trac] #1842(undetermined:open): create better HTTP Live Streaming with segment

[FFmpeg]

#1842: create better HTTP Live Streaming with segment
-------------------------------------+-------------------------------------
             Reporter:  teric        |                    Owner:
                 Type:  enhancement  |                   Status:  open
             Priority:  wish         |                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 [ticket:1842 teric]:
 > Summary of the bug:
 > How to reproduce:
 > {{{
 > % ffmpeg -i -threads 2 -i rtmp://10.10.80.80/live/shandong_HD live=1 -re
 -copyts -acodec libfaac -vcodec libx264 -vprofile baseline -bsf
 h264_mp4toannexb -v error -map 0 -b:v 500k -b:a 64k -f ssegment
 -segment_list livelist.m3u8 -segment_list_flags +live -segment_list_size 3
 -segment_time 10 d%05d.ts
 >
 > ffmpeg 1.0
 > }}}
 >

 > Firstly, iPad or VLC expect the adjacent lists(m3u8) includes
 '''overlaped items''', OR VLC will stop always and iPad will stop/jitter
 occasionally.

 Can you elaborate on this? I based the segmenter work on the only M3U8
 spec available, but I'm aware that special devices may have special
 requirements (which may or may not be documented). Do you have such
 documents/links, or your claim is based on your experience (which is fine,
 just I need to know if I need to rely on some reference spec)?
 [...]
 > Secondly, when the stream is restarted, ffmpeg(segment) should create
 > segments with different filenames, OR these files will stay stale in CDN
 > cache
 [...]
 > '''so we can use timestamp as the init segment index.'''

 Sure this is an idea.

 > You can refer to my patch for detail.

 I'll have a look at the patch, but posting it on the ML should allow a
 much easier review and should get more attention, so I'd recommend you to
 post the patch on ffmpeg-devel.

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