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

Author	SHA1	Message	Date
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
Alexandra Hájková	b08569a239	lavf: Replace the ASF demuxer The old one is the result of the reverse engineering and guesswork. The new one has been written following the now-available specification. This work is part of Outreach Program for Women Summer 2014 activities for the Libav project. The fate references had to be changed because the old demuxer truncates the last frame in some cases, the new one handles it properly. The seek-test reference is changed because seeking works differently in the new demuxer. When seeking, the packet is not read from the stream directly, but it is rather constructed by the demuxer. That is why position is -1 now in the reference. Signed-off-by: Anton Khirnov <anton@khirnov.net>	10 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
Justin Ruggles	6c65cf58fd	lavf: Use av_get_audio_frame_duration() in get_audio_frame_size() Also, do not give AVCodecContext.frame_size priority for muxing. Updated 2 FATE references: dxa-feeble - adds 1 audio frame that is still within 2 seconds as specified by -t 2 in the FATE test wmv8-drm-nodec - durations are not needed. previously they were estimated using the packet size and average bit rate.	13 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
Vitor Sessak	96573c0d76	lavf/utils.c: Order packets with identical PTS by stream index. This allows for more reproducible results when using multi-threading. Signed-off-by: Ronald S. Bultje <rsbultje@gmail.com>	14 years ago
Reimar Döffinger	853395b913	Add test for ASF -cryptokey that tests only demuxing, but both audio and video to complement the existing video-only decode test. Originally committed as revision 26054 to svn://svn.ffmpeg.org/ffmpeg/trunk	14 years ago