On 2011-12-30 20:38:42 +0100, Mike Melanson  wrote:
> Module: libav
> Branch: master
> Commit: ae51b1a9ba28e6b31d0c40296e4d74eefa75ecf1
> 
> Author:    Mike Melanson <[email protected]>
> Committer: Ronald S. Bultje <[email protected]>
> Date:      Fri Dec 30 11:03:37 2011 -0800
> 
> FATE: Add test for H.264 MP4->annex.B bitstream filter.
> 
> This test uses an existing FATE sample (h264/interlaced_crop.mp4).
> 
> Signed-off-by: Ronald S. Bultje <[email protected]>
> 
> ---
> 
>  tests/fate/h264.mak                 |    2 ++
>  tests/ref/fate/h264-bsf-mp4toannexb |    1 +
>  2 files changed, 3 insertions(+), 0 deletions(-)
> 
> diff --git a/tests/fate/h264.mak b/tests/fate/h264.mak
> index c519f74..20bfda2 100644
> --- a/tests/fate/h264.mak
> +++ b/tests/fate/h264.mak
> @@ -175,6 +175,7 @@ FATE_H264  := $(FATE_H264:%=fate-h264-conformance-%)      
>               \
>                fate-h264-interlace-crop                                  \
>                fate-h264-lossless                                        \
>                fate-h264-extreme-plane-pred                              \
> +              fate-h264-bsf-mp4toannexb                                 \
>  
>  FATE_TESTS += $(FATE_H264)
>  fate-h264: $(FATE_H264)
> @@ -355,3 +356,4 @@ fate-h264-conformance-sva_nl2_e: CMD = framecrc -vsync 0 
> -i $(SAMPLES)/h264-conf
>  fate-h264-interlace-crop: CMD = framecrc -vsync 0 -i 
> $(SAMPLES)/h264/interlaced_crop.mp4 -vframes 3
>  fate-h264-lossless: CMD = framecrc -vsync 0 -i $(SAMPLES)/h264/lossless.h264
>  fate-h264-extreme-plane-pred: CMD = framemd5 -vsync 0 -i 
> $(SAMPLES)/h264/extreme-plane-pred.h264
> +fate-h264-bsf-mp4toannexb: CMD = md5 -i $(SAMPLES)/h264/interlaced_crop.mp4 
> -vcodec copy -bsf h264_mp4toannexb -f mpeg

this breaks in interesting ways. --disable-optimisations produces
a different md5 than recorded here but if I write to file and not to
the md5 protocol the files are identical.

So this doesn't seem to be a problem in the bitstream filter itself.

Janne
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel

Reply via email to