From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [RFC] FFmpeg Execution Graph Visualization Date: Sat, 29 Mar 2025 04:00:29 +0000 Message-ID: <DM8P223MB0365C50FD29B96B35AF1442CBAA32@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw) In-Reply-To: <DM8P223MB03652B84BC0DFD2216E4A35EBAA62@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> > -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of > softworkz . > Sent: Donnerstag, 27. März 2025 00:26 > To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> > Subject: Re: [FFmpeg-devel] [RFC] FFmpeg Execution Graph Visualization > > > > > -----Original Message----- > > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of > > Stefano Sabatini > > Sent: Mittwoch, 26. März 2025 23:53 > > To: FFmpeg development discussions and patches <ffmpeg- > devel@ffmpeg.org> > > Subject: Re: [FFmpeg-devel] [RFC] FFmpeg Execution Graph Visualization > > [..] > > 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. > > > > 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. > > _______________________________________________ > > Yes, I see quite a number use cases as well. > It's still a work in progress, but I've set up a GitHub repo for > documentation and as a place of interaction. It's not for ffmpeg code, > but there are tests, examples and a documentation Wiki: > > https://github.com/softworkz/ffmpeg_output_apis/wiki > > (a number of things are still incomplete) > > > I'm also exploring a way for self-printing the data schema for each use > case. On the repo Wiki there are Entity-Relationship diagrams for the > FFprobe and the Graphs schema. I'll follow up with more details.. Hi Stefano, I've got everything in shape now in this repo I've also completed done the write-up on my experiment regarding schema self-printing: https://github.com/softworkz/ffmpeg_output_apis/wiki/Schema-Self-Printing I'd be curious what you think about it (of course others as well). Best, sw _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2025-03-29 4:00 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-03-18 2:32 Soft Works 2025-03-18 6:43 ` Diederick C. Niehorster 2025-03-21 18:27 ` Stefano Sabatini 2025-03-21 20:11 ` Soft Works 2025-03-26 22:52 ` Stefano Sabatini 2025-03-26 23:26 ` softworkz . 2025-03-29 4:00 ` softworkz . [this message] 2025-03-27 19:27 ` Nicolas George 2025-03-27 19:47 ` softworkz . 2025-03-28 23:47 ` Michael Niedermayer
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=DM8P223MB0365C50FD29B96B35AF1442CBAA32@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \ --to=softworkz-at-hotmail.com@ffmpeg.org \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git