ffmpeg is amazing, but it’s like tar on steroids: I can never remember the right incantation. Google is required for even the simplest of things. I don’t know if it’s their goal, but I’d love a more user friendly set of command line arguments.
This is where GUI's shine, as opposed to command-line. Perhaps this is slightly off-topic, but my dream is an interface that combines the best of both worlds. Kind of an automated GUI-builder for command-line tools, that analyzes the combinations of options used most, breaks them down into workflows with options (that can be manually named), and you can thus execute one-off commands easily and quickly without having…
Seems like you'd need a universal CLI tool usage traverser and parser to figure out what's possible. Likely this would produce a decision tree of sorts with different modes and options excluding or including new options. We'd need a way to show all this, maybe nested tabs for modes and check boxes and other inputs at each appropriate level.
Layer on this a way to optimize for the most common cases like you said. Further, if this becomes popular, CLI tools could emit some sort of standard description language that would optionally customize the GUI. The GUI's output should be both the text command it constructed and the ability to run that command directly.
More future steps would be a way to reason about multiple commands, pipes, and other combinators.
Adding this to my side projects backlog. Thanks for the idea!