While I agree with you that ffmpeg is hard to fully utilize in its current form, how do you design a "wrapper" for a CLI tool with 68,915 (I could be off by a few) parameters?
There's only one way to manage that, and that is to hide some options and functionality. Then it stops being an ffmpeg GUI, it starts becoming a "video transcoding application" (or an "audio grabber application "or a "subtitle insertion application") with ffmpeg as its backend.
There's only one way to manage that, and that is to hide some options and functionality. Then it stops being an ffmpeg GUI, it starts becoming a "video transcoding application" (or an "audio grabber application "or a "subtitle insertion application") with ffmpeg as its backend.
See a similar thing for openssl here: https://smallstep.com/blog/if-openssl-were-a-gui/
Maybe someone can build a very specific AI that generates ffmpeg commands for you, based on its man page and what you input as free text?