[FFmpeg-user] Application provided invalid, non monotonically increasing dts to muxer in stream

[MrNice]

On 19/09/15 18:02, MrNice wrote:
> 
> 
> On 17/09/15 14:51, MrNice wrote:
>>
>>
>> On 17/09/15 12:00, Carl Eugen Hoyos wrote:
>>> MrNice <wxcvbn2006 <at> iol.ie> writes:
>>>
>>>>> Does it also happen if you only record audio?
>>>>
>>>> Yes it happen with the command
>>>> ./ffmpeg 
>>>
>>>> -f v4l2 -ts mono2abs -channel 1 -video_size 720x576 
>>>> -pix_fmt yuyv422 -thread_queue_size 512 -i /dev/video0
>>>
>>> Does it also happen if you only provide audio 
>>> input to FFmpeg?
>>>
>>> Carl Eugen
>>>
>>>
>>
>> No error in a 50 mn recording with command
>> ./ffmpeg -debug 1 -f pulse -ar 44100 -ac 2 -channel_layout stereo
>> -thread_queue_size 512 -itsoffset -0.20 -i
>> alsa_input.pci-0000_00_14.2.analog-stereo -vn -c:a pcm_s16le
>> /Store3/Test/t_`date +%Y%m%d_%H%M`.mkv
>>
> 
> 
> More info after long tests.
> The error
> Application provided invalid, non monotonically increasing dts to muxer
> in stream 0:
> happens after at least 30 minutes recording. ie: Last time at 33:12
> Few seconds before or after happens warning message
> Past duration 0.xxxx too large
> 
> Following this link
> http://ffmpeg.org/pipermail/ffmpeg-user/2014-December/024695.html
> I tried with -af aresample=async=1 but still I get the error with 1
> frame dropped.
> 
> [matroska @ 0x25d9de0] Writing block at offset 9113825634, size 179818,
> pts 2026200, dts 2026200, duration 40, keyframe 0
> [matroska @ 0x25d9de0] Writing block at offset 9114005460, size 176978,
> pts 2026240, dts 2026240, duration 40, keyframe 0
> Past duration 0.602318 too large
> *** dropping frame 50652 from stream 0 at ts 50650
> [matroska @ 0x25d9de0] Starting new cluster at offset 9114182446 bytes,
> pts 2026280dts 2026280
> [matroska @ 0x25d9de0] Writing block at offset 9114182463, size 180336,
> pts 2026280, dts 2026280, duration 40, keyframe 1
> Past duration 0.601341 too large
> 
> What more to do?
> 
> As the errors are after 30 minutes, I could try to record by smaller
> parts. To be sure, I would like a way to stop recording if an error
> occurs. I tried -xerror but it's not working with this error.
> Any idea how to do?
> _


I was wrong: One more try and I got the error at 8:07

I need help!!!