[FFmpeg-trac] #3871(avcodec:new): FFmpeg MD5 output different with same data #2

FFmpeg trac at avcodec.org
Wed Aug 20 22:04:10 CEST 2014


#3871: FFmpeg MD5 output different with same data #2
--------------------------------------+-----------------------------------
             Reporter:  ahthovaikied  |                    Owner:
                 Type:  defect        |                   Status:  new
             Priority:  normal        |                Component:  avcodec
              Version:  2.2.4         |               Resolution:
             Keywords:  md5 aac h264  |               Blocked By:
             Blocking:                |  Reproduced by developer:  0
Analyzed by developer:  0             |
--------------------------------------+-----------------------------------

Comment (by ahthovaikied):

 Replying to [comment:1 kurosu]:
 > You can also use git bisect to narrow down the commit that would cause a
 change in MD5.
 Yup, I am trying that.
 However I had trouble when running :
 {{{
 git bisect start
 git bisect good HEAD
 git bisect bad n2.2.7
 git bisect run script_that_builds_ffmpeg_and_compare_md5
 }}}
 I had the error
 {{{Bisecting: a merge base must be tested}}}
 And then after the first build:
 {{{'bisect_state bad' returned error code 3}}}

 I am trying between HEAD and HEAD~2000 now.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/3871#comment:6>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list