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 57A3149918 for ; Tue, 23 Apr 2024 21:48:19 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 42C9F68D2BB; Wed, 24 Apr 2024 00:48:18 +0300 (EEST) Received: from relay8-d.mail.gandi.net (relay8-d.mail.gandi.net [217.70.183.201]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 7614268D27C for ; Wed, 24 Apr 2024 00:48:12 +0300 (EEST) Received: by mail.gandi.net (Postfix) with ESMTPSA id D49891BF205 for ; Tue, 23 Apr 2024 21:48:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1713908892; 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=A70XXU0Efdu635kJqSdoaHo/KLFmWbFOXw/mjvocxGI=; b=L4/iArgi3TPZrr3MxN1whZ6URAQwpx7IQpx0vMQJTTby3d04aRdAvB9Ka3yRgxzEET9YQH MdtH3LJzXC8CoJoHUzUMqemskWdGkum8I0NDCEEIM/YxJ+9EGyJ3FhevsK4VjOB69tClNd PGRcwzu+n8KEDc+Rd3nuCVnM/KwZ1R45/ri2ZDPVBo6edH67OfaCoCxZtUzFPotGzRpfGj UEEhxCvc3SoP1IkZ5IHSkVwFlTaXWMnJKYAaVptQa3MiKSw0Za1uh8ISY1+Mo3Hf7tT97Y ewys9xxCXY2chGSSgVZT+xPKwzOHp4hec2d2FEsnQSl/jy7MfU/xwzyI2AaRDw== Date: Tue, 23 Apr 2024 23:48:10 +0200 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20240423214810.GN6420@pb2> References: <20240422120925.380253-1-ffmpeg-devel@pileofstuff.org> <171386408794.22242.4320691091356910947@lain.khirnov.net> <171386667402.5069.14623062002271611181@lain.khirnov.net> <20240423111552.GI6420@pb2> <927b5c94-c765-4852-a502-4369b4a624c6@gmail.com> <20240423205342.GL6420@pb2> <95887da9-e3d6-4739-b46a-7d6809aaa932@gmail.com> MIME-Version: 1.0 In-Reply-To: <95887da9-e3d6-4739-b46a-7d6809aaa932@gmail.com> 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="===============6386608523661635220==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============6386608523661635220== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="vmoZfhdnm7g2kM3x" Content-Disposition: inline --vmoZfhdnm7g2kM3x Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 23, 2024 at 06:23:04PM -0300, James Almer wrote: > On 4/23/2024 5:53 PM, Michael Niedermayer wrote: > > On Tue, Apr 23, 2024 at 05:24:03PM -0300, James Almer wrote: > > > On 4/23/2024 8:15 AM, 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 gene= ral 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. Obviousl= y I would use > > > > > > > AVOptions to display configuration options for different enco= ders. And it's > > > > > > > possible to create AVOptions objects for my UI. But how stro= ngly is that use > > > > > > > case recommended? > > > > > > >=20 > > > > > > > To provide a particularly difficult example - let's say I wan= t to let 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 + pic= ture" option, > > > > > > > so how would I extend it to meet my needs? > > > > > >=20 > > > > > > If they fit your use case, then use them, otherwise don't - tha= t's true > > > > > > for pretty much all APIs we provide. > > > > >=20 > > > > > Ah ok, so how about if I changed "intended" to "optimized" in the= subject? > > > >=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 spe= cialized > > > > software thats already dealing with a lot of pictures > > > >=20 > > > > still you certainly can handle binary data (like a bitmap picture) = through > > > > AVOption > > > >=20 > > > > thx > > >=20 > > > Take for example AVIAMFReconGain.recon_gain in libavutil/iamf.h, whic= h is > > > currently the only field not covered by an AVOption (And thus not cur= rently > > > configurable from the CLI). How could it be supported? Binary type do= esn't > > > work because it expects a pointer + size field and allocates the form= er. > >=20 > > i would guess some form of AV_OPT_TYPE_FLAG_ARRAY > >=20 > > we have similar arrays like intra_matrix in mpeg codecs >=20 > Same situation it seems, it expects a pointer + size field. So someone needs to add support for a fixed size or dim size0,size1,sizeDIM thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB It is what and why we do it that matters, not just one of them. --vmoZfhdnm7g2kM3x Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZigsmgAKCRBhHseHBAsP qwCCAJ4yZubKuwzvgf4Uat7peQsTxtaetwCfVYHibidxLufZkowvUQwiG0B43LE= =f7hP -----END PGP SIGNATURE----- --vmoZfhdnm7g2kM3x-- --===============6386608523661635220== 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". --===============6386608523661635220==--