ffmpeg/tests/ref/vsynth/vsynth_lena-dnxhd-1080i-colr

5ba3ddb58b10e5f0069cb4f82d594695 *tests/data/fate/vsynth_lena-dnxhd-1080i-colr.mov
3031929 tests/data/fate/vsynth_lena-dnxhd-1080i-colr.mov
ce4993a69ef55c8c4b18138716f17b6f *tests/data/fate/vsynth_lena-dnxhd-1080i-colr.out.rawvideo
stddev:    1.33 PSNR: 45.59 MAXDIFF:   22 bytes:  7603200/   760320
avformat/movenc: Move avid DNxHD padding to the correct spot Outputting DNxHD into .mov containers 'corrupts' following atoms until end of stsd ffmpeg and qtdump could not decode pasp/colr atoms in the files made by ffmpeg, when outputting DNxHD due to the incorrect padding placement. Now we add the padding in the correct place Tidy up FATE changes due to padding changes. Signed-off-by: Michael Niedermayer <michaelni@gmx.at> 2015-02-16 11:40:36 +01:00			`5ba3ddb58b10e5f0069cb4f82d594695 *tests/data/fate/vsynth_lena-dnxhd-1080i-colr.mov`
avformat/movenc: Add simplistic 'colr' tag writing support to mov container Signed-off-by: Michael Niedermayer <michaelni@gmx.at> 2015-01-26 16:39:24 +01:00			`3031929 tests/data/fate/vsynth_lena-dnxhd-1080i-colr.mov`
dnxhddec: use dequantization formula from specs The current one, while correct, does not yield the best possible results. The specificiations suggest another formula, which results in quality gains in the decoded output from fate tests. This justifies changing said formula. Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> 2015-10-01 22:01:26 +02:00			`ce4993a69ef55c8c4b18138716f17b6f *tests/data/fate/vsynth_lena-dnxhd-1080i-colr.out.rawvideo`
			`stddev: 1.33 PSNR: 45.59 MAXDIFF: 22 bytes: 7603200/ 760320`