It’s intentionally opinionated and scoped to my own workflow, if you want full control, FFmpeg is still the right tool.
Since your README.md starts with an example of ffmpeg and gripes "This is not a normal sentence", it would be nice to simultaneously show the precise analogue as "ffhuman".
That way the reader immediately understands what your tool has to offer. Otherwise it can feel like we're learning two things instead of just one.
I’ve moved the ffhuman command right up before the FFmpeg example at the top so the before/after is immediately visible.