From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <ffmpeg-devel-bounces@ffmpeg.org> Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id 7B2854B9EA for <ffmpegdev@gitmailbox.com>; Thu, 27 Mar 2025 19:27:57 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id D47D2687C5B; Thu, 27 Mar 2025 21:27:52 +0200 (EET) Received: from nef.ens.fr (nef2.ens.fr [129.199.96.40]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id AAA09687BAB for <ffmpeg-devel@ffmpeg.org>; Thu, 27 Mar 2025 21:27:46 +0200 (EET) X-ENS-nef-client: 129.199.129.80 ( name = phare.normalesup.org ) Received: from phare.normalesup.org (phare.normalesup.org [129.199.129.80]) by nef.ens.fr (8.14.4/1.01.28121999) with ESMTP id 52RJRjvY004683 for <ffmpeg-devel@ffmpeg.org>; Thu, 27 Mar 2025 20:27:45 +0100 Received: by phare.normalesup.org (Postfix, from userid 1001) id A4DD72EFA6; Thu, 27 Mar 2025 20:27:45 +0100 (CET) Date: Thu, 27 Mar 2025 20:27:45 +0100 From: Nicolas George <george@nsup.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Message-ID: <Z-WmsURm8nm7qBbK@phare.normalesup.org> References: <DM8P223MB0365AB64AECCC838CF7CB41DBADE2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> <Z92viSTlKU0La9Ua@mariano> <DM8P223MB036550001F5BE5292F899C3FBADB2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> <Z+SFLmfGERrM6a70@mariano> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <Z+SFLmfGERrM6a70@mariano> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (nef.ens.fr [129.199.96.32]); Thu, 27 Mar 2025 20:27:45 +0100 (CET) Subject: Re: [FFmpeg-devel] [RFC] FFmpeg Execution Graph Visualization X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches <ffmpeg-devel.ffmpeg.org> List-Unsubscribe: <https://ffmpeg.org/mailman/options/ffmpeg-devel>, <mailto:ffmpeg-devel-request@ffmpeg.org?subject=unsubscribe> List-Archive: <https://ffmpeg.org/pipermail/ffmpeg-devel> List-Post: <mailto:ffmpeg-devel@ffmpeg.org> List-Help: <mailto:ffmpeg-devel-request@ffmpeg.org?subject=help> List-Subscribe: <https://ffmpeg.org/mailman/listinfo/ffmpeg-devel>, <mailto:ffmpeg-devel-request@ffmpeg.org?subject=subscribe> Reply-To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" <ffmpeg-devel-bounces@ffmpeg.org> Archived-At: <https://master.gitmailbox.com/ffmpegdev/Z-WmsURm8nm7qBbK@phare.normalesup.org/> List-Archive: <https://master.gitmailbox.com/ffmpegdev/> List-Post: <mailto:ffmpegdev@gitmailbox.com> 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-request@ffmpeg.org with subject "unsubscribe".