Niklas Haas (HE12025-02-17): > For the record, this approach seems to work well - adding a const char *label > to the AVFilterPad struct and then setting it during > avfilter_graph_segment_create_filters() recovers the full label names without > any need for shenanigans.
Thanks for looking into it. > That aside, how do you feel about scrapping the current ASCII art > output entirely in favor of the new format? I think that it is, at the > very least, providing just as much information, and IMO more readable. > The ASCII art graph is not really enhancing clarity for me. > > (Though given what Soft Works noted below, it may be a good idea to focus that > version instead) We need at least two formats: one easy to read for humans, one reliable to parse for scripts. Therefore, we need a mechanism to select the format. Under these circumstances, I see no merit in removing the current format; somebody might have built something around it. (Ideally, the computer-readable outputs should offer various formats: JSON, XML, etc. For that, we would need to move into the library with a proper API the code in ffprobe. And for that we need a good strings API. Yet another thing blocked by the people blocking AVWriter.) On the other hand, I do not object to a new format being made the default. Regards, -- 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".
