On 03/09/2020 05:22 PM, Phil Rhodes via ffmpeg-user wrote:
To be scrupulously fair, documenting something like ffmpeg (which is what we're
really talking about here) is always going to be very difficult because it does
a huge range of things, some of which are very much orthogonal to each other.
It'll convert files; it'll act as a streaming server.
Oh, goodie! :-) Sounds like fun. Sounds like it might be amenable to
script-driven subdivision.
Whether it's a good idea for one commandline utility to include so much widely
variegated capability is academic at this point. Reasonably, it shouldn't...
Why, Phil, you really are a philosopher. :-)
...The name alone makes it abundantly clear that the thing has grown rather
haphazardly from much simpler beginnings.
Well, all kids are cute, no matter what, eh?
Inasmuch as there are actually a few pages of documentation with worked
examples, it is actually better-written-up than the vast majority of open
source projects...
What's missing is, in my humble opinion, just what I seek: Command lines
that are known to work.
Certainly the idea of examining the source to figure out how it works is pretty
absurd. The source tree for ffmpeg (let alone the many external dependencies
require to make it useful) is vast, and evaluating commandline options by
examining it would be the work of - literally - months.
Ding-ding-ding. You win a cigar!
May I share this? ...I had no idea that my simple request would be so
controversial. I'm not sure what to think about that.
_______________________________________________
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
