diff options
author | Anton Khirnov <anton@khirnov.net> | 2022-12-10 09:45:50 +0100 |
---|---|---|
committer | Anton Khirnov <anton@khirnov.net> | 2023-01-10 11:49:28 +0100 |
commit | 260f3918937463f1b90e1b77cba80b917f3cb8c1 (patch) | |
tree | 27667ff7aa2c447d4dd5e3609196b50f4abe2e5d /libavfilter/vf_chromashift.c | |
parent | e884360e913a08c085ae29ffc1461a2bb205d550 (diff) | |
download | ffmpeg-260f3918937463f1b90e1b77cba80b917f3cb8c1.tar.gz |
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).
Diffstat (limited to 'libavfilter/vf_chromashift.c')
0 files changed, 0 insertions, 0 deletions