[FFmpeg-trac] #3902(avformat:new): FFmpeg MD5 output different with same data #3
FFmpeg
trac at avcodec.org
Fri Aug 29 20:49:23 CEST 2014
#3902: FFmpeg MD5 output different with same data #3
-------------------------------------+-------------------------------------
Reporter: | Owner:
ahthovaikied | Status: new
Type: defect | Component: avformat
Priority: normal | Resolution:
Version: git-master | Blocked By:
Keywords: md5 mpeg2 | Reproduced by developer: 0
ac3 mkv |
Blocking: |
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Comment (by ahthovaikied):
Replying to [comment:6 cehoyos]:
> Please test running the same {{{ffmpeg}}} binary on both systems.
I had some difficulty to build a binary portable across the 2 machines,
and had to change the build configuration by adding {{{--disable-hwaccels
--disable-devices --disable-vdpau}}}.
Full configure line is now:
{{{
--enable-gpl --enable-version3 --enable-nonfree --disable-runtime-
cpudetect --disable-ffserver --disable-ffplay --disable-encoders
--disable-decoders --disable-filters --disable-debug --disable-hwaccels
--disable-devices --disable-vdpau
}}}
By the way, isn't this a bug that I require both {{{--disable-hwaccels}}}
and {{{--disable-vdpau}}} to not link against libvdpau?
I built the binary on the corei7 machine, then rsynced the binary to the
atom, and...
{{{
$ ffmpeg -loglevel quiet -i cut.mkv -map v -map a -c copy -f md5 -
MD5=726d4f2a3d79e000e0bbde6397311bb2
}}}
...MD5 is now the same on both machines.
What is you interpretation of this?
--
Ticket URL: <https://trac.ffmpeg.org/ticket/3902#comment:7>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list