Chiebot-Mirror/FFmpeg - FFmpeg - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Anton Khirnov	9543161800	framehash: convert to new channel layout API Signed-off-by: James Almer <jamrial@gmail.com>	3 years ago
James Almer	e8a39f584a	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>	8 years ago
James Almer	33aa8a6221	avformat/framecrc: enable new output Reviewed-by: Michael Niedermayer <michael@niedermayer.cc> Signed-off-by: James Almer <jamrial@gmail.com>	9 years ago
Michael Niedermayer	153b5fb2fd	avformat/framecrcenc: print the checksum and size of extradata as well Signed-off-by: Michael Niedermayer <michaelni@gmx.at>	11 years ago
Michael Niedermayer	dc82b2c0f1	framecrcenc: print flags and side data elements The new fields are only printed when they differ from their defaults this way only few fate refs change Signed-off-by: Michael Niedermayer <michaelni@gmx.at>	12 years ago
Anton Khirnov	aba232cfa9	lavf: deprecate r_frame_rate. According to its description, it is supposed to be the LCM of all the frame durations. The usability of such a thing is vanishingly small, especially since we cannot determine it with any amount of reliability. Therefore get rid of it after the next bump. Replace it with the average framerate where it makes sense. FATE results for the wtv and xmv demux tests change. In the wtv case this is caused by the file being corrupted (or possibly badly cut) and containing invalid timestamps. This results in lavf estimating the framerate wrong and making up wrong frame durations. In the xmv case the file contains pts jumps, so again the estimated framerate is far from anything sane and lavf again makes up different frame durations. In some other tests lavf starts making up frame durations from different frame.	12 years ago
Anton Khirnov	d2afbd9a56	frame{crc/md5}: set the stream timebase from codec timebase. Right now those muxers use the default timebase in all cases(1/90000). This patch avoid unnecessary rescaling and makes the printed timestamps more readable. Also, extend the printed information to include the timebases and packet pts/duration and align the columns. Obviously changes the results of all fate tests which use those two muxers.	13 years ago
Mike Melanson	15f073ee6d	FATE: xmv-demux test; exercise the XMV demuxer without decoding the perceptual codecs inside. Code coverage: libavformat/xmv.c: 3% -> 91% Signed-off-by: Ronald S. Bultje <rsbultje@gmail.com>	13 years ago