[FFmpeg-trac] #9193(undetermined:new): Invalid initialization segment with HLS FMP4 encoder
FFmpeg
trac at avcodec.org
Mon Apr 19 20:07:25 EEST 2021
#9193: Invalid initialization segment with HLS FMP4 encoder
-------------------------------------+-------------------------------------
Reporter: Jason | Owner: (none)
Type: defect | Status: new
Priority: normal | Component:
| undetermined
Version: git-master | Resolution:
Keywords: hls | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Description changed by Jason:
Old description:
> VERSION: ffmpeg version 4.4 | Windows & Linux
>
> The HLS encoder (used with fmp4 segmenting) began generating invalid
> initialization segments consisting of 5 boxes (ftyp, moov, sidx, moof, &
> mdat) with the latest release -- and an invalid first data segment
> consisting of a single styp box with no data. Subsequent segments after
> the first are OK.
>
> It appears if the initialization segment has taken over the data from the
> first segment.
>
> Version 4.3 and the dash encoder generate an initialization segment with
> a single ftyp and moov box, as expected.
>
> Here is sample command that exhibits the behavior:
>
> ./ffmpeg.exe -i "a.mp4" -y -an -codec:v libx264 -b:v 1000k -s 960x540
> -hls_time 4 -hls_segment_type fmp4 -hls_playlist_type event -f hls
> "output.m3u8"
New description:
VERSION: ffmpeg version 4.4 + head branch| Windows & Linux
The HLS encoder (used with fmp4 segmenting) began generating invalid
initialization segments consisting of 5 boxes (ftyp, moov, sidx, moof, &
mdat) with the latest release -- and an invalid first data segment
consisting of a single styp box with no data. Subsequent segments after
the first are OK.
It appears if the initialization segment has taken over the data from the
first segment.
Version 4.3 and the dash encoder generate an initialization segment with a
single ftyp and moov box, as expected.
Here is sample command and file that exhibits the behavior:
./ffmpeg.exe -i "https://carbon-
media.accelerator.net/00000000001/4ajEIDZneABc1Uin8Pw163" -y -report -an
-codec:v libx264 -b:v 1000k -s 960x540 -hls_time 4 -hls_segment_type fmp4
-hls_playlist_type event -f hls "output.m3u8"
The complete log output / report is attached.
--
--
Ticket URL: <https://trac.ffmpeg.org/ticket/9193#comment:5>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list