johnf/m3u8-segmenter — Issue #17: m3u8-segmenter stops working after 27-53 hours
Author: bradskins
Created: 2011-12-09 15:01:38+00:00
State: open

When I use m3u8-segmenter for extended periods of time, it stops working and just displays this error:

[mpegts @ 0x803019a00] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 8589937458 >= 4878761008
Warning: Could not write frame of stream
[mpegts @ 0x803019a00] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 8589937458 >= 4878763097
Warning: Could not write frame of stream
[mpegts @ 0x803019a00] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 8589937458 >= 4878765186
Warning: Could not write frame of stream
[mpegts @ 0x803019a00] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 8589937458 >= 4878767275
Warning: Could not write frame of stream
[mpegts @ 0x803019a00] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 8589937458 >= 4878769364
Warning: Could not write frame of stream
[mpegts @ 0x803019a00] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 8589937458 >= 4878771453
Warning: Could not write frame of stream
[mpegts @ 0x803019a00] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 8589937458 >= 4878773542

I did a bit of digging and a common solution is to run ffmpeg with the -strict experimental flag set. Is there an equivalent flag in the API? Or is this due to some other problem? (this also happens with http-segmenter and segmenter.c...)