Open mcmtroffaes opened 7 years ago
This would really make a good addition. Aside from new possibilities it might speed up the export time as well.
Nice to hear you're positive about the idea :) thanks! Turns out that my patch is failing on MIPS but hopefully once that's fixed we'll be able to take advantage of it from upstream ffmpeg.
Just a quick note here that I'm still trying to get the motion blur filter into ffmpeg: https://ffmpeg.org/pipermail/ffmpeg-devel/2017-June/211866.html
It would be pretty neat if ffmpeg's filters would be available to be used during export process, say through a new option in our ini file.
Whilst at it, note I've updated the framestep filter in ffmpeg to support motion blur: https://ffmpeg.org/pipermail/ffmpeg-devel/2017-April/209795.html - if this gets merged, then this should open up some interesting possibilities, for example when you want to apply some filters for special effects before and/or after motion blur is applied. Also we could drop the motion blur code entirely and leave it just to ffmpeg; in that scenario, we'd for instance have that:
fps = 600 videofilter = framestep=step=10:blend=5
would be the same as
fps = 60 motion_blur_samples = 9 motion_blur_strength = 0.5
The framestep filter could also be combined with tblend to produce "rolling over" motion blur, e.g.
fps = 600 videofilter = framestep=step=10:blend=10,tblend=average
Anyway, supporting filters would give the user a bit more control over the sort of motion blur they want to achieve, and enable a whole host of other effects as well.