Dear Paul, On Thu, Nov 1, 2018 at 10:34 AM Paul B Mahol <one...@gmail.com> wrote: > Duplicates funcionality of tmix filter.
Many thanks for your reply, and for pointing out the existence of the tmix filter. Please forgive my ignorance about it. I see tmix was only added in April this year, whilst I've been carrying skipblend (and tried getting it upstreamed a few times) since June 2017. No matter, it's great to see this sort of functionality finally included! Would you consider accepting a patch that added an integer "cutoff" option to tmix, for the purpose of setting all weights for frames beyond "cutoff" to 0? The reason for requesting this is that in some workflows, one is blending together a lot of frames at once, and specifying a vector of, say, 100 ones followed by a zero, when blending together, say, 200 frames, whilst possible, is rather tedious; for instance "tmix=frames=200:cutoff=100" (weights are 1 by default so this should then work as expected). Kind regards, Matthias _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
