#3035: h264 decoder duplicates 8-th frame
-------------------------------------+-------------------------------------
Reporter: eugene | Owner: (none)
smirnov |
Type: defect | Status: closed
Priority: normal | Component: avcodec
Version: unspecified | Resolution: fixed
Keywords: h264 | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Changes (by Balling):
* status: open => closed
* resolution: => fixed
Comment:
Comparing with JM 19.0 (ldecod.exe -p InputFile=0004.h264 -p
OutputFile=oldtown_ref.yuv)
https://github.com/sjilss/h264_qdct_ptc/commit/d10376624227d7c55327ca2bca59ccff8bb43995
we can say the decoder is bitperfect (md5 of the 1.yuv is
C90157A2A0D2C073F190CA9DDF4506D4). It was fixed somewhere between
4a11a6f4ccc7c56ccc82adf0c3ab4054d4c22d1e and HEAD of master. Who cares
where...
md5 of broken decode with old ffmpeg was A0A2580FD0EA30B6827690CA366ACF70.
md5 of old ffmpeg with -vsync 0 was also C90157A2A0D2C073F190CA9DDF4506D4.
-vsync passthrough (vsync 0 was deprecated) now prints also
C90157A2A0D2C073F190CA9DDF4506D4.
It was decoding two more frames than correctly now 1644 vs 1642.
I will also point out that -vsync 0 makes the same vfrdet result as now
for any vsync.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/3035#comment:5>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac
To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".
