I did not realize my mistake until it was too late.įor the book and this article, I used Linux. In fact, the tutorial forms much of this book. The book has a full tutorial and is not just a collection of hacks. In the spirit of open source, I have made its ebook version free. It is now a 152-page full-colour paperback on Amazon - FFMPEG Quick Hacks. When I went in depth about FFmpeg, I decided to write a book instead. Last year, in the midst of the lockdown, I decided to write a follow-up for the article - sort of 'More FFmpeg tips and tricks'. I had even written a FFmpeg tips-and-tricks article in a magazine without knowing any better. The only filter I used was the volume filter, which I used (blindly) to amplify low-volume audio files. Backgroundįor several years, I did not bother with FFmpeg filters. The syntax for FFmpeg filters is obscure and the documentation is a bit cryptic. (Since humans are sensitive to luminance components, in most cases, it is the idea that only processing luminance components suffices.A lot more FFmpeg functionality is in the form of filters. Only the luminance component is processed. This example is the same as that in the official document. If you can not understand the way of thinking in the frequency domain, use “avgblur” etc.
Even so, of course, easiness to understand of dedicated blur filters is much larger than this filter. Just like “convolution” you can also use the generic filter “fftfilt” for blurring purposes.Īs the name suggests, this filter allows you to apply arbitrary expressions to samples in frequency domain.Īs with “convolution”, understanding and familiarity with mathematics or image processing is also necessary for use of this, I personally think that thinking in the frequency domain is intuitive, so blurring control by this filter may be easier than “convolution”.
0 kommentar(er)
