ffmpegagent (HE12025-02-28): > This patchset doesn't aim to improve or change the API itself - that would > be a bit too much at once.
So you asked for advice, got come counsel from me and did exactly the opposite. Do not be surprised if the result is less than satisfactory. > * Public API isn't documented yet When designing a public API, the user documentation, and in particular a quick-start guide with clear examples, should be the first thing you show, and probably even one of the very first things you write. Without that, I can only repeat what I told you two days ago: The writers in ffprobe are an ad-hoc construction to turn the shallow data structures produced by ffprobe into a common denominator of JSON, XML, CSV and a few custom formats. It is not a good candidate to be turned into an API. -- Nicolas George _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
