Changes between Version 2 and Version 4 of Ticket #9510


Ignore:
Timestamp:
Jan 31, 2023, 6:24:22 PM (4 years ago)
Author:
Andreas Unterweger
Comment:

The issue is still present, even with recent master. I pointed the URL to a different file from the FFmpeg samples. It occurs not only with this file, but every file I tried as an input. As stated above, this seems to be an issue of the HLS segmenter.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #9510

    • Property Status new → reopened

  • Ticket #9510 – Description

    v2 v4  
    44
    55{{{
    6 ./ffmpeg -y -i timer_1M.mp4 -acodec aac -b:a 64k -vcodec h264 -b:v 1M -f hls -hls_segment_type fmp4 -strftime 1 -hls_segment_filename '%%18d.m4s' -hls_flags second_level_segment_index+split_by_time -hls_time 0.6 -hls_init_time 0.600001 index.m3u8
     6./ffmpeg -y -i CDR-Dinner_LAN_800k.mp4 -acodec aac -b:a 64k -vcodec h264 -b:v 1M -f hls -hls_segment_type fmp4 -strftime 1 -hls_segment_filename '%%18d.m4s' -hls_flags second_level_segment_index+split_by_time -hls_time 0.6 -hls_init_time 0.600001 index.m3u8
    77}}}
    88
    … …  
    1111Removing the hls_init_time parameter from the command "resolves" the issue, i.e., the segments are then split correctly and have video frames.
    1212
    13 I tried this with different files, including [https://file-examples-com.github.io/uploads/2017/04/file_example_MP4_480_1_5MG.mp4]. Changing the GOP size with -g:v does not make the error go away, which is why I think it is a bug in the HLS segmenter.
     13I tried this with different files, including [https://samples.ffmpeg.org/MPEG-4/CDR-Dinner_LAN_800k.mp4]. Changing the GOP size with -g:v does not make the error go away, which is why I think it is a bug in the HLS segmenter.