On 11/1/18, Matthias Troffaes <matthias.troff...@gmail.com> wrote: > Dear Paul, > > On Thu, Nov 1, 2018 at 11:21 AM Matthias Troffaes > <matthias.troff...@gmail.com> wrote: >> 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). > > I found a way of doing this differently, as I now found that tmix > doesn't actually step frames, unlike skipblend. For history's sake, > the way to get skipblend behaviour is to do something like > "tmix=frames=100,framestep=150" for instance assuming you want to > blend 100 frames, skip 50, and so on. It is *much* slower compared to > skipblend by quite a large factor, as tmix does a lot of redundant > computations, but it works.
I think that adding option to skip some frames can be added. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
