FFmpeg/tests/ref/fate/copy-trac236

34b0ad38518b0eb8464aff04e6d0e143 *tests/data/fate/copy-trac236.mov
630878 tests/data/fate/copy-trac236.mov
#tb 0: 100/2997
#media_type 0: video
#codec_id 0: rawvideo
#dimensions 0: 720x480
#sar 0: 10/11
#tb 1: 1/48000
#media_type 1: audio
#codec_id 1: pcm_s16le
#sample_rate 1: 48000
#channel_layout 1: 3
#channel_layout_name 1: stereo
0,          0,          0,        1,   518400, 0x81ab2140
1,          0,          0,     1024,     4096, 0x67dc99a3
1,       1024,       1024,     1024,     4096, 0xf115a681
0,          1,          1,        1,   518400, 0x81ab2140
1,       2048,       2048,     1024,     4096, 0xf455b597
1,       3072,       3072,     1024,     4096, 0x67dc99a3
0,          2,          2,        1,   518400, 0x81ab2140
1,       4096,       4096,     1024,     4096, 0xf115a681
0,          3,          3,        1,   518400, 0x81ab2140
1,       5120,       5120,     1024,     4096, 0xf455b597
1,       6144,       6144,      759,     3036, 0xa291a36d
0,          4,          4,        1,   518400, 0x81ab2140
avformat/movenc: write the colr atom by default The write_colr flag has been marked as experimental for over 5 years. It should be safe to enable its behavior by default as follows: - Write the colr atom by default for mp4/mov if any of the following: - The primaries/trc/matrix are all specified, OR - There is an ICC profile, OR - The user specified +write_colr - Keep the write_colr flag for situations where the user wants to write the colr atom even if the color info is unspecified (e.g., http://ffmpeg.org/pipermail/ffmpeg-devel/2020-March/259334.html) This fixes https://trac.ffmpeg.org/ticket/7961 Signed-off-by: Michael Bradshaw <mjbshaw@google.com> 2020-04-13 19:11:38 +02:00			`34b0ad38518b0eb8464aff04e6d0e143 *tests/data/fate/copy-trac236.mov`
			`630878 tests/data/fate/copy-trac236.mov`
tests/fate-run.sh: Analyze file generated in transcode() This should be much more informative than a plain md5 difference Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> 2016-09-09 23:17:02 +02:00			`#tb 0: 100/2997`
			`#media_type 0: video`
			`#codec_id 0: rawvideo`
			`#dimensions 0: 720x480`
			`#sar 0: 10/11`
			`#tb 1: 1/48000`
			`#media_type 1: audio`
			`#codec_id 1: pcm_s16le`
			`#sample_rate 1: 48000`
			`#channel_layout 1: 3`
avformat/framehash: also print channel layout as a string This should be more useful for users since numerical values for channel layout can be confusing and unintuitive. Reviewed-by: Michael Niedermayer <michael@niedermayer.cc> Signed-off-by: James Almer <jamrial@gmail.com> 2016-09-29 01:55:18 +02:00			`#channel_layout_name 1: stereo`
tests/fate-run.sh: Analyze file generated in transcode() This should be much more informative than a plain md5 difference Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> 2016-09-09 23:17:02 +02:00			`0, 0, 0, 1, 518400, 0x81ab2140`
			`1, 0, 0, 1024, 4096, 0x67dc99a3`
			`1, 1024, 1024, 1024, 4096, 0xf115a681`
			`0, 1, 1, 1, 518400, 0x81ab2140`
			`1, 2048, 2048, 1024, 4096, 0xf455b597`
			`1, 3072, 3072, 1024, 4096, 0x67dc99a3`
			`0, 2, 2, 1, 518400, 0x81ab2140`
			`1, 4096, 4096, 1024, 4096, 0xf115a681`
			`0, 3, 3, 1, 518400, 0x81ab2140`
			`1, 5120, 5120, 1024, 4096, 0xf455b597`
			`1, 6144, 6144, 759, 3036, 0xa291a36d`
			`0, 4, 4, 1, 518400, 0x81ab2140`