Timestamps are unset in a packet for stream 0. Deprecated?
|Reported by:||barhom||Owned by:|
|Blocking:||Reproduced by developer:||no|
|Analyzed by developer:||no|
Summary of the bug:
timeout 7s multicat -uU @220.127.116.11:3301 input.ts
This input.ts is recorded from satellite from a channel called "ERI TV" being broadcasted on Nilesat. I do not control the source.
I am trying to segment this channel by the following
ffmpeg -i udp://18.104.22.168:3301 -c copy -f hls /tmp/removeme/playlist.m3u8
The HLS segmenter runs fine and produces segments being written to /tmp/removeme/.
The problem is that the playlist.m3u8 EXTINF data contains wrong information about the segments
cat playlist.m3u8 #EXTM3U #EXT-X-VERSION:3 #EXT-X-TARGETDURATION:0 #EXT-X-MEDIA-SEQUENCE:43 #EXTINF:0.320000, playlist43.ts #EXTINF:0.320000, playlist44.ts #EXTINF:0.320000, playlist45.ts #EXTINF:0.320000, playlist46.ts #EXTINF:0.400000, playlist47.ts
The segment-length should be a few seconds, not 0.32s to 0.4s as is shown above.
The problem probably has something to do with that ffmpeg outputs the following error message
[hls @ 0x55a762d467c0] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly [mpegts @ 0x55a762d16a40] Timestamps are unset in a packet for stream 0. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly}}} I found that a temporary fix would be to include -fflags +genpts. Is this to be recommended? What is the downside of my doing -fflags +genpts on all my segmentation? Should this work without +genpts? Thanks for the response. input.ts is attached