- 05 Dec, 2019 1 commit
-
-
Michael Niedermayer authored
Fixes: fate-fitsdec-bitpix-64 Possibly Fixes: -nan is outside the range of representable values of type 'unsigned short' Possibly Fixes: 17769/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_FITS_fuzzer-5678314672357376 Found-by: continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpegSigned-off-by: Michael Niedermayer <michael@niedermayer.cc>
-
- 30 Aug, 2017 1 commit
-
-
Paras Chadha authored
Signed-off-by: Paras Chadha <paraschadha18@gmail.com>
-
- 13 Apr, 2016 1 commit
-
-
James Almer authored
Reviewed-by: Michael Niedermayer <michael@niedermayer.cc> Signed-off-by: James Almer <jamrial@gmail.com>
-
- 22 Apr, 2014 1 commit
-
-
Anton Khirnov authored
It is not supposed to be changed from outside of lavc. Set the stream timebase and average framerate instead.
-
- 26 Feb, 2012 1 commit
-
-
Anton Khirnov authored
r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a
-
- 03 Feb, 2012 1 commit
-
-
Anton Khirnov authored
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.
-
- 24 Aug, 2010 1 commit
-
-
Vitor Sessak authored
Originally committed as revision 24911 to svn://svn.ffmpeg.org/ffmpeg/trunk
-