Re: [FFmpeg-devel] [PATCH v3 0/2] libavfilter/vf_fps: Rewrite using activate callback

2018-03-08 Thread Nicolas George
Calvin Walton (2018-02-22): > This revision of the patch fixes statistics by counting the number of > times each frame has been output, rather than trying to guess at the > time each frame is output whether it was a duplicate or drop. > > I ended up leaving the conditional check > if

Re: [FFmpeg-devel] [PATCH v3 0/2] libavfilter/vf_fps: Rewrite using activate callback

2018-03-02 Thread Nicolas George
Calvin Walton (2018-03-02): > Ping? > > I've been using this patch set in my production system for the past > week. There I've been running some fairly complicated filter pipelines > generated by scripts with good results - it's working reliably (no > stalls/hangs) and has solved my memory usage

Re: [FFmpeg-devel] [PATCH v3 0/2] libavfilter/vf_fps: Rewrite using activate callback

2018-03-02 Thread Calvin Walton
Ping? I've been using this patch set in my production system for the past week. There I've been running some fairly complicated filter pipelines generated by scripts with good results - it's working reliably (no stalls/hangs) and has solved my memory usage issue. Calvin. On Thu, 2018-02-22 at

[FFmpeg-devel] [PATCH v3 0/2] libavfilter/vf_fps: Rewrite using activate callback

2018-02-22 Thread Calvin Walton
This revision of the patch fixes statistics by counting the number of times each frame has been output, rather than trying to guess at the time each frame is output whether it was a duplicate or drop. I ended up leaving the conditional check if (s->status && s->frames_count == 0) { at the