4 ms·
there are two problems here. the main problem is that nobody reads the manual, which actually starts out half-decent. the description is very clear, concise, an
by Hello71 7y ago
there are two problems here. the main problem is that nobody reads the manual, which actually starts out half-decent. the description is very clear, concise, and even contains the oft-whinged-about examples. https://ffmpeg.org/ffmpeg.html https://ffmpeg.org/ffmpeg.html
the second problem is that ffmpeg has a lot of features, and nobody wants to go through and fully document hundreds of formats, codecs, and filters.
- Daemon404 7y agoPart of the problem is that the documentation is so vast (the page you link is only one of many, many pages; the documentation has been split out into multiple pages for a while now) that as a user, it's fairly insane to try and consume and comprehend it all, especially if all you want to do is something quick.
- _Gyan_ 7y agoI'll be adding entries for all the missing demuxers/decoders/encoders/muxers eventually. At present, only a fraction have been documented.
- zbobet2012 7y agoThe third problem is that video is _complicated_. What does the nal-hrd=cbr do? Well you need to understand the HRD model and (which is about 5 pages of dense specs). Ffmpeg does a great job of guessing _what_ you want. But as soon as you're outside of those guesses you need to know _a lot_ to get things working.