From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTP id 5C1D745948 for ; Tue, 23 Apr 2024 11:18:38 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 56C8168D2B6; Tue, 23 Apr 2024 14:18:36 +0300 (EEST) Received: from relay3-d.mail.gandi.net (relay3-d.mail.gandi.net [217.70.183.195]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 027D468CCF9 for ; Tue, 23 Apr 2024 14:18:29 +0300 (EEST) Received: by mail.gandi.net (Postfix) with ESMTPSA id 3827E60004 for ; Tue, 23 Apr 2024 11:18:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1713871109; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=96nJjK7YGQXjO8NnUWQC8phakY/2w7JbPKYy/Umtt/U=; b=JRq7HHAGYpqhY8++AKmTi4GWkpzfIArKmGUgJo14JbJlPOjXOLFSLpA2yGqi2l62b7mdfe vR2yJWIQ8aUF9Rx4+WhuCfjb9ksLGmLNqTYMNFuwnH1iuGOeq60vJYrAJcUxBt3VsiAZ3p IF8FsLvuMZceFpKOEyNIOiC2hnoC89JX8xfCA/ZctwPQXDwoIzdfsMlu6JEOPGJiZFghA/ 6sb6x0S8UywSVTC2CG4pT2I1POQFn6haMbP+iqrjh2ueE/7v8Sbm+8zfQ+rNcBtZFcq/lX 4OaIzTrWKpX0DvAJ2iUY64U9ut0FTWwayh6I6vg9xudaLngefAHi+Pg3rALZIQ== Date: Tue, 23 Apr 2024 13:18:28 +0200 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20240423111828.GJ6420@pb2> References: <20240422120925.380253-1-ffmpeg-devel@pileofstuff.org> <171386408794.22242.4320691091356910947@lain.khirnov.net> <171386667402.5069.14623062002271611181@lain.khirnov.net> <20240423111552.GI6420@pb2> MIME-Version: 1.0 In-Reply-To: <20240423111552.GI6420@pb2> X-GND-Sasl: michael@niedermayer.cc Subject: Re: [FFmpeg-devel] [PATCH v2] lavu/opt: Clarify that AVOptions is not indended for general use X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: multipart/mixed; boundary="===============6012647590857964900==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============6012647590857964900== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="4QtlUgeVfweBfGH0" Content-Disposition: inline --4QtlUgeVfweBfGH0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 23, 2024 at 01:15:52PM +0200, Michael Niedermayer wrote: > On Tue, Apr 23, 2024 at 11:10:43AM +0100, Andrew Sayers wrote: > > On Tue, Apr 23, 2024 at 12:04:34PM +0200, Anton Khirnov wrote: > > > Quoting Andrew Sayers (2024-04-23 11:51:00) > > > > On Tue, Apr 23, 2024 at 11:21:27AM +0200, Anton Khirnov wrote: > > > > > > lavu/opt: Clarify that AVOptions is not indended for general use > > > > >=20 > > > > > They _are_ intended for general use though. > > > >=20 > > > > In that case I'm confused... > > > >=20 > > > > Let's say I make a desktop app to transcode videos. Obviously I wo= uld use > > > > AVOptions to display configuration options for different encoders. = And it's > > > > possible to create AVOptions objects for my UI. But how strongly i= s that use > > > > case recommended? > > > >=20 > > > > To provide a particularly difficult example - let's say I want to l= et the user > > > > choose between interface themes, and I want to show both some text = and a > > > > picture of the theme. AVOption doesn't include a "text + picture" = option, > > > > so how would I extend it to meet my needs? > > >=20 > > > If they fit your use case, then use them, otherwise don't - that's tr= ue > > > for pretty much all APIs we provide. > >=20 > > Ah ok, so how about if I changed "intended" to "optimized" in the subje= ct? >=20 > If FFmpeg which is a multimedia tool in no place needs or wants to store > pictures through its option API in a way not curently supported. > I would say thats not going to qualify as "general use" outside specializ= ed > software thats already dealing with a lot of pictures >=20 > still you certainly can handle binary data (like a bitmap picture) through > AVOption And if you disagree, which you probably do :) send a patch to improve AVOption to cover more general use thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB He who knows, does not speak. He who speaks, does not know. -- Lao Tsu --4QtlUgeVfweBfGH0 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZieZBAAKCRBhHseHBAsP qw75AJ0Zd4cc/T//OLrasLFlD/l7wkm6DwCglAGGzOmJNRkkBujS7invmyXI2Lk= =+4+5 -----END PGP SIGNATURE----- --4QtlUgeVfweBfGH0-- --===============6012647590857964900== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ 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". --===============6012647590857964900==--