2 ms·
> just looking up the relevant options Not the OP, but ffmpeg's documentation is pretty awful to navigate if you aren't an expert in it. It is very technical a
by StableAlkyne 1y ago
> just looking up the relevant options
Not the OP, but ffmpeg's documentation is pretty awful to navigate if you aren't an expert in it. It is very technical and exact, but fails to provide examples for most options.
For example, the fpsmax option says you can set the maximum frame rate using "Hz value, fraction or abbreviation." So now the user has to search for how any of these things are to be specified (does a bare 60 mean 60hz? Do you need to include Hz? Is it case sensitive? What are the abbreviations? What is the fraction a fraction of?). And that's a random option I found in the pile of documentation it has.
Maybe it's useful if you use it every day, but I completely understand why people use GUIs whose purpose is to construct the command. Or even LLMs to do the same thing.
- shadowgovt 1y agoI strongly suspect this is the niche that LLMs will settle into long-term in programming work. They're pretty good at munging over code, documentation, and discourse online to paper over the issues with some projects having docs written in human-communication-as-a-second-language form, which is a lot of projects. We've already migrated (via StackOverflow) far past 'RTFM' as the go-to answer, and LLMs seem the next logical step there: a machine to read all the sources and boil them down for you.