I've run into some problems with the current fps filter memory usage, because of how it buffers all of the frames needed to fill in large timestamp gaps, rather than generate them on the fly.
In order to fix this, I have rewritten the fps filter to use the newer "activate" api. I have also added some additional fate tests to check for regressions in the filter. They pass with both the current fps filter and my new one. Calvin Walton (2): libavfilter/vf_fps: Add more fate tests libavfilter/vf_fps: Rewrite using activate callback libavfilter/vf_fps.c | 398 +++++++++++++++++------------- tests/fate/filter-video.mak | 10 +- tests/ref/fate/filter-fps-down | 15 ++ tests/ref/fate/filter-fps-down-eof-pass | 16 ++ tests/ref/fate/filter-fps-down-round-down | 15 ++ tests/ref/fate/filter-fps-down-round-up | 16 ++ tests/ref/fate/filter-fps-up | 17 ++ tests/ref/fate/filter-fps-up-round-down | 16 ++ tests/ref/fate/filter-fps-up-round-up | 17 ++ 9 files changed, 351 insertions(+), 169 deletions(-) create mode 100644 tests/ref/fate/filter-fps-down create mode 100644 tests/ref/fate/filter-fps-down-eof-pass create mode 100644 tests/ref/fate/filter-fps-down-round-down create mode 100644 tests/ref/fate/filter-fps-down-round-up create mode 100644 tests/ref/fate/filter-fps-up create mode 100644 tests/ref/fate/filter-fps-up-round-down create mode 100644 tests/ref/fate/filter-fps-up-round-up _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
