Anton Khirnov 260f391893 fftools/ffmpeg: always generate CFR output when -r is used ... Current code may, depending on the muxer, decide to use VSYNC_VFR tagged with the specified framerate, without actually performing framerate conversion. This is clearly wrong and against the documentation, which states unambiguously that -r should produce CFR output for video encoding. FATE test changes: * nuv-rtjpeg: replace -r with '-enc_time_base -1', which keeps the original timebase. Output frames are now produced with proper durations. * filter-mpdecimate: just drop the -r option, it is unnecessary * filter-fps-r: remove, this test makes no sense and actually produces broken VFR output (with incorrect frame durations).		2023-01-10 11:49:28 +01:00
..
api
checkasm	checkasm/v210dec: add extra space to the destination arrays	2022-12-21 00:36:49 +01:00
fate	fftools/ffmpeg: always generate CFR output when -r is used	2023-01-10 11:49:28 +01:00
filtergraphs
ref	fftools/ffmpeg: always generate CFR output when -r is used	2023-01-10 11:49:28 +01:00
.gitignore
audiogen.c
audiomatch.c
base64.c
copycooker.sh
extended.ffconcat
fate-run.sh
fate-valgrind.supp
fate.sh
Makefile	fate/segafilm: Add tests for segafilm (de)muxer	2022-09-20 18:32:28 +02:00
md5.sh
refcmp-metadata.awk
reference.pnm
rotozoom.c
simple1.ffconcat
simple2.ffconcat
test.ffmeta
tiny_psnr.c
tiny_ssim.c
utils.c
videogen.c