4 ms·

I work for many years with FFMpeg that has no documentation and no code sample, and it's okay for me. I prefer that the developers keep their time optimizing th

I work for many years with FFMpeg that has no documentation and no code sample, and it's okay for me. I prefer that the developers keep their time optimizing the code rather than writing documentation that needs to be maintained and become a problem when not in sync. My state of mind is that if it's open source then just read the code.

akvadrako 8y ago
FFMpeg is not some random project - it's irreplaceable and very popular.
- deleted 8y ago
  [deleted]
saagarjha 8y ago
Well, the only way I get it to work is by searching up how to use it on Stack Overflow, so…
mort96 8y ago
FFmpeg's C API has pretty good documentation: https://www.ffmpeg.org/doxygen/4.0/ https://www.ffmpeg.org/doxygen/4.0/ The C API documentation includes a ton of example code: https://ffmpeg.org/doxygen/4.0/dir_687bdf86e8e626c2168c3a2d1c125116.html https://ffmpeg.org/doxygen/4.0/dir_687bdf86e8e626c2168c3a2d1... In addition to having both a man page and a --help option, The FFmpeg CLI tool has very thorough documentation: https://ffmpeg.org/ffmpeg.html https://ffmpeg.org/ffmpeg.html I don't understand how FFmpeg could in any way be considered to have no documentation and no code samples.