[FFmpeg-user] "Non-monotonous DTS in output stream" error, previous and current values are equal

Mark Filipak markfilipak.windows+ffmpeg at gmail.com
Tue Apr 7 01:33:32 EEST 2020


On 04/06/2020 10:01 AM, Crazy Red Elephant via ffmpeg-user wrote:
> So what do you think, Mark? I also noticed that if I use 1.2 version of ffmpeg there are no DTS errors and no dropping frames. The result file though acts weird when I try to create gifs from it for example. My gif creation software detects like 15 fps in it while "normal" videos give me the same amount fps in the gif as there are in the actual video. Not sure what's so special in version 1.2. Maybe it's because in old versions ffmpeg doesn't try to fix these timestamps or so... I still don't understand what's wrong with the source files :-(

Sorry, CRE, I don't know anything about animated GIFs and I'm way to ignorant about ffmpeg. I can't 
help. I wish I could. At the rate of progress I'm making, maybe sometime after 2022. :-(

- Mark.

PS: I don't even know how to get the ffmpeg version. Look:

 >ffmpeg -version
ffmpeg version N-94664-g0821bc4eee Copyright (c) 2000-2019 the FFmpeg developers
built with gcc 9.1.1 (GCC) 20190807
configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-fontconfig --enable-gnutls 
--enable-iconv --enable-libass --enable-libdav1d --enable-libbluray --enable-libfreetype 
--enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg 
--enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora 
--enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 
--enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp 
--enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex 
--enable-libxvid --enable-libaom --enable-libmfx --enable-amf --enable-ffnvcodec --enable-cuvid 
--enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth --enable-libopenmpt
libavutil      56. 33.100 / 56. 33.100
libavcodec     58. 55.101 / 58. 55.101
libavformat    58. 31.104 / 58. 31.104
libavdevice    58.  9.100 / 58.  9.100
libavfilter     7. 58.101 /  7. 58.101
libswscale      5.  6.100 /  5.  6.100
libswresample   3.  6.100 /  3.  6.100
libpostproc    55.  6.100 / 55.  6.100

> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Thursday, April 2, 2020 10:14 PM, Mark Filipak <markfilipak.windows+ffmpeg at gmail.com> wrote:
> 
>> Thanks, CRE. Now I know.
>>
>> On 04/01/2020 09:38 AM, Crazy Red Elephant via ffmpeg-user wrote:
>>
>>> Hi Mark, the option is called "Fix bitstream timing info", it's in the "Timestamps and default duration" box which is on the right side of the "Input" tab...
>>> On Sunday, March 15, 2020 3:41 PM, Mark Filipak markfilipak.windows+ffmpeg at gmail.com wrote:
>>>
>>>> On 03/15/2020 09:02 AM, Crazy Red Elephant via ffmpeg-user wrote:
>>>>
>>>>>> Are they actually disruptive, or could you just keep the original stream as is, knowing 1 out of 120 frames or something will be dropped when playing back?
>>>>>
>>>>> To me, yes. I know some other users also reported something about playback issues numerous times but the stream provider doesn't seem to care.
>>>>> I think I mentioned before that remuxing the video with MKVToolNix and the "generate timestamps" option checked...
>>>>
>>>> Can you help me find the "generate timestamps" option? I can't find it. I'd like to see what it does with a VOB that has 8 PGCs that are okay, but the 9th & 10th PGCs have audio in advance of video by about 4400ms.
>>
>> ffmpeg-user mailing list
>> ffmpeg-user at ffmpeg.org
>> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
>>
>> To unsubscribe, visit link above, or email
>> ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".
> 
> 
> _______________________________________________
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-user
> 
> To unsubscribe, visit link above, or email
> ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".
> 


More information about the ffmpeg-user mailing list