Niklas Haas a69b08790b avfilter/vf_tinterlace: support full-range YUV ... This filter, when used in the "pad" mode, currently makes the distinction between limited and full range solely by testing for YUVJ pixel formats at link setup time. This is deprecated and should be improved to perform the detection based on the per-frame metadata. In order to make this distinction based on color range metadata, which is only known at the time of filtering frames, for simplicity, we simply allocate two copies of the "black" frame - one for limited range and the other for full range metadata. This could be done more dynamically (e.g. as-needed or simply by blitting the appropriate pixel value directly), but this change is relatively simple and preserves the structure of the existing code. This commit actually fixes a bug in FATE - the new output is correct for the first time. The previous md5 ref was of a frame that incorrectly combined full-range pixel data with limited-range black fields. The corresponding result has been updated. Signed-off-by: Niklas Haas <git@haasn.dev>		2022-12-20 14:02:37 +01:00
..
api	tests/api: use AVFrame.duration instead of AVFrame.pkt_duration	2022-07-19 12:27:18 +02:00
checkasm	checkasm/v210enc: test the entire width of 10-bit planar input arrays	2022-12-01 18:19:03 +01:00
fate	fate: add QOI/XBM/XWD image2pipe tests	2022-12-03 19:38:11 +01:00
filtergraphs
ref	avfilter/vf_tinterlace: support full-range YUV	2022-12-20 14:02:37 +01:00
.gitignore
audiogen.c
audiomatch.c
base64.c
copycooker.sh
extended.ffconcat
fate-run.sh	tests/fate-run: Allow to set input options for encoding pass	2022-09-10 01:38:07 +02:00
fate-valgrind.supp
fate.sh
Makefile	fate/segafilm: Add tests for segafilm (de)muxer	2022-09-20 18:32:28 +02:00
md5.sh
refcmp-metadata.awk
reference.pnm
rotozoom.c
simple1.ffconcat
simple2.ffconcat
test.ffmeta
tiny_psnr.c
tiny_ssim.c
utils.c
videogen.c