virtualenv/FFmpeg
1
0
Fork 0
mirror of https://github.com/FFmpeg/FFmpeg.git synced 2024-12-12 19:18:44 +02:00
Code Issues Releases Activity
bae2e19777
FFmpeg/tests/fate/dnxhd.mak

23 lines
1.6 KiB
Makefile
Raw Normal View History

fate: add DNxHD/HR tests Currently only 2 profiles are evaluated because they are the only 2 with distributed test sequences. - CID 1260: YUV 4:2:2 10 bits with block-adaptive interlace coding, from ticket 4876; - CID 1270: YUV 4:4:4 10 bits (HR), 1920x839, from ticket 4581. They were generated from the ticket sequences by running the following kind of command-line; ffmpeg -i $INPUT -an -sn -vcodec copy -vframes 1 -y $OUTPUT.mov Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
2015-10-05 17:37:38 +02:00
FATE_DNXHD = fate-dnxhd-mbaff \
tests/fate: added dnxhr parser regression test Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
2016-02-16 08:01:28 +02:00
fate-dnxhr-444 \
fate: add DNxHR 12-bit example. Signed-off-by: Steven Robertson <steven@strobe.cc> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
2016-08-17 07:22:54 +02:00
fate-dnxhr-12bit \
tests/fate/dnxhd: add dnxhr prefix tests The data offset value in the prefix increases as the heights increases. This test adds a tests for some common dnxhr heights. can somebody add the following test footage to fate/dnxhd? https://dl.dropboxusercontent.com/u/170952/fate/dnxhd/prefix-256x1536.dnxhr https://dl.dropboxusercontent.com/u/170952/fate/dnxhd/prefix-256x1716.dnxhr https://dl.dropboxusercontent.com/u/170952/fate/dnxhd/prefix-256x2048.dnxhr https://dl.dropboxusercontent.com/u/170952/fate/dnxhd/prefix-256x2160.dnxhr https://dl.dropboxusercontent.com/u/170952/fate/dnxhd/prefix-256x3212.dnxhr Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
2016-07-21 03:15:38 +02:00
fate-dnxhr-parse \
fate-dnxhr-prefix1 \
fate-dnxhr-prefix2 \
fate-dnxhr-prefix3 \
fate-dnxhr-prefix4 \
fate-dnxhr-prefix5
fate: add DNxHD/HR tests Currently only 2 profiles are evaluated because they are the only 2 with distributed test sequences. - CID 1260: YUV 4:2:2 10 bits with block-adaptive interlace coding, from ticket 4876; - CID 1270: YUV 4:4:4 10 bits (HR), 1920x839, from ticket 4581. They were generated from the ticket sequences by running the following kind of command-line; ffmpeg -i $INPUT -an -sn -vcodec copy -vframes 1 -y $OUTPUT.mov Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
2015-10-05 17:37:38 +02:00
FATE_SAMPLES_AVCONV-$(call DEMDEC, MOV, DNXHD) += $(FATE_DNXHD)
fate-dnxhd: $(FATE_DNXHD) $(FATE_VCODEC_DNXHD)
fate: disable automatic conversions on many tests. Explicitly insert the scale or aresample filter where it would have been inserted by the negotiation. Re-enable conversions if it cannot be done easily. If a conversion is needed in a test, we want to know about it. If the negotiation changes and makes new conversion necessary, we want to know about it even more.
2020-08-14 18:58:27 +02:00
fate-dnxhd-mbaff: CMD = framecrc -flags +bitexact -idct simple -i $(TARGET_SAMPLES)/dnxhd/dnxhd100_cid1260.mov -pix_fmt yuv422p10le -vf scale
fate: add scale filters for big-endian architectures. Filters mostly work in native endianness, but they must output a specified endianness, usually little: that requires a final conversion for big endian. I do not know what's the deal with gif-deal: inserting explicitly the filters that are implicitly inserted result in less frames in output. Probably a strange problem of duration.
2020-09-14 21:23:20 +02:00
fate-dnxhr-444: CMD = framecrc -flags +bitexact -idct simple -i $(TARGET_SAMPLES)/dnxhd/dnxhr444_cid1270.mov -pix_fmt yuv444p10le -vf scale
fate-dnxhr-12bit: CMD = framecrc -flags +bitexact -idct simple -i $(TARGET_SAMPLES)/dnxhd/dnxhr_cid1271_12bit.mov -pix_fmt yuv422p12le -vf scale
tests/fate: added dnxhr parser regression test Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
2016-02-16 08:01:28 +02:00
fate-dnxhr-parse: CMD = framecrc -flags +bitexact -idct simple -i $(TARGET_SAMPLES)/dnxhd/dnxhr_cid1274.dnxhr -pix_fmt yuv422p
tests/fate/dnxhd: add dnxhr prefix tests The data offset value in the prefix increases as the heights increases. This test adds a tests for some common dnxhr heights. can somebody add the following test footage to fate/dnxhd? https://dl.dropboxusercontent.com/u/170952/fate/dnxhd/prefix-256x1536.dnxhr https://dl.dropboxusercontent.com/u/170952/fate/dnxhd/prefix-256x1716.dnxhr https://dl.dropboxusercontent.com/u/170952/fate/dnxhd/prefix-256x2048.dnxhr https://dl.dropboxusercontent.com/u/170952/fate/dnxhd/prefix-256x2160.dnxhr https://dl.dropboxusercontent.com/u/170952/fate/dnxhd/prefix-256x3212.dnxhr Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
2016-07-21 03:15:38 +02:00
fate-dnxhr-prefix1: CMD = framecrc -flags +bitexact -idct simple -i $(TARGET_SAMPLES)/dnxhd/prefix-256x1536.dnxhr -pix_fmt yuv422p
fate-dnxhr-prefix2: CMD = framecrc -flags +bitexact -idct simple -i $(TARGET_SAMPLES)/dnxhd/prefix-256x1716.dnxhr -pix_fmt yuv422p
fate-dnxhr-prefix3: CMD = framecrc -flags +bitexact -idct simple -i $(TARGET_SAMPLES)/dnxhd/prefix-256x2048.dnxhr -pix_fmt yuv422p
fate-dnxhr-prefix4: CMD = framecrc -flags +bitexact -idct simple -i $(TARGET_SAMPLES)/dnxhd/prefix-256x2160.dnxhr -pix_fmt yuv422p
fate-dnxhr-prefix5: CMD = framecrc -flags +bitexact -idct simple -i $(TARGET_SAMPLES)/dnxhd/prefix-256x3212.dnxhr -pix_fmt yuv422p
Reference in New Issue Copy Permalink