[FFmpeg-trac] #177(FFmpeg:new): "non monotone timestamps" error patch
FFmpeg
trac at avcodec.org
Mon May 9 14:12:05 CEST 2011
#177: "non monotone timestamps" error patch
--------------------------+--------------------------------
Reporter: andrixnet | Owner: michael
Type: defect | Status: new
Priority: minor | Component: FFmpeg
Version: unspecified | Keywords: monotone timestamp
Blocked By: | Blocking:
Reproduced: 0 | Analyzed: 0
--------------------------+--------------------------------
I have been using this patch for some time now, and so far I haven't had
problems with the streams produced by FFMPEG.
It has long been discussed on the internet, mailing lists, forums, etc,
about people having problems with some files when they tried converting
them with FFMPEG. The error reported was :
"non monotone timestamps 123>=123"
The test is a sane one, but including the equality in the test breaks
usability with lots of cases like DTS audio in the source, or simply
having a multi language audio MKV.
While FFMPEG was able to read the input, it was unable to produce a proper
multi language audio output.
The attached patch is based on a suggestion I read on a forum and I am
submitting it to the developers for consideration.
My question is : why that test has to be >= instead of > ?
Upon request I can provide some streams with multiple audio that are not
convertable because of this.
--
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/177>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list