tests/filtergraphs/setpts

settb=1/1000,
setpts=1/(35*TB) * (N + 0.05 * sin(N*2*PI/25)):strip_fps=1
FATE: add a test for the setpts filter 2013-03-13 11:03:08 +01:00			`settb=1/1000,`
avfilter/setpts: add option strip_fps to decide framerate handling In f121d95, the outlink framerate was unconditionally unset. This breaks/bloats outputs from CFR muxers unless the user explicitly sets a sane framerate. And the most common invocation for setpts seen in workflows, our docs and across the web is `PTS-STARTPTS` or others of the general form `PTS+constant` which preserves the input framerate. Default value is false, which restores old behaviour. Fixes #11428 2025-01-23 10:52:16 +05:30			`setpts=1/(35TB) (N + 0.05 * sin(N2PI/25)):strip_fps=1`