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

FFmpeg trac at avcodec.org
Sat Aug 23 16:04:27 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 cehoyos):

 Replying to [comment:12 ahthovaikied]:
 > So let's say I want to copy streams (without transcoding) in another
 Matroska file. That is the same command line except you replace {{{md5}}}
 by {{{matroska}}}, and stdout by a filepath. How is that different?

 It isn't, it can fail for some files depending on your configure options.

 Please understand that this isn't necessarily the case for your example in
 this ticket (your bisect will show once you try it as suggested below), I
 just want to explain to you that imo your whole process is flawed (at
 least with the configure line you are apparently using) because it will
 fail for some examples. And I am not convinced that a demuxers output is
 ''specifed'' the way you seem to believe it is (and the way you test it).

 > Replying to [comment:11 cehoyos]:
 > > Since 2.3 is "newer" than n2.2.7 you did mark n2.3 (and all revisions
 that behave the same) as {{{bad}}} and n2.2.7 (and all revisions with the
 same output) as {{{good}}}? This is the only way {{{git bisect}}} works
 and it will show you the commit that introduces the change.
 > Yes I know how git bisect works. That is what I did.

 Funny that your output shows that you tried something different that
 cannot work (and this has nothing to do with FFmpeg).

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


More information about the FFmpeg-trac mailing list