An uncut example m3u8 file is attached.
The varying output lengths are expected, due to
splitting along I-Frames, although negative
durations seems like an error.
As I am not sure if this is a case of user
error, I'd like to ask for any advice
to fix this issue and, if possible, find
out why it occurs before opening a trac
The command above is a shortened version
of the original command with which this
bug was discovered. A change of framerate
using -r 30 changes the output values,
but still leaves some negative timestamps.
This behaviour was tested on Ubuntu with
FFmpeg HEAD and on Windows with the latest
I would be thankful for any advice.