Stefano Sabatini (HE12025-03-26): > One of the possible uses is to expose the data printed by > filters. E.g. detection filters are printing the information either in > the stderr using custom formats, this should really be converted to > something easier to consume (whatever formats for which you don't > need a custom parser). > > The metadata muxer also might benefit from using a text writer, to > avoid again the need for a custom parser, and probably there are more > use cases easy to spot.
For the record, I have had detailed plans for all this for years. But since it is very related to strings, it requires AVWriter, and it requires the abstraction and type description layer that I want to introduce that starts with AVWriter. Therefore, it cannot go forward unless FFmpeg has once more proper leadership able to greenlight it. > So at some point we want to make this API accessbile from the > libraries, that is to move them into libavutil. Again, it's fine to > expose this at the tools level first so we can experiment and refine > the interface before moving to a stable one. I wild recommend using the fftools as a staging area. 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".
