From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.ffmpeg.org (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id A73AC4CF47 for ; Tue, 12 Aug 2025 11:59:43 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTP id 6D787687BD9; Tue, 12 Aug 2025 14:59:39 +0300 (EEST) Received: from relay3-d.mail.gandi.net (relay3-d.mail.gandi.net [217.70.183.195]) by ffbox0-bg.ffmpeg.org (Postfix) with ESMTPS id 632DD687BD9 for ; Tue, 12 Aug 2025 14:59:32 +0300 (EEST) Received: by mail.gandi.net (Postfix) with ESMTPSA id 858CD2058C for ; Tue, 12 Aug 2025 11:59:31 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1754999971; 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=hpLULG47+JNinyQCadJB1V3wQoCmWEyJnhy9klzBd8w=; b=QwDtXXvcx4r8CeoQRYFlKu1FQ9OYCGMHkmzcToY/qDb2PqrKn+/Tzsfq45liRADwZpZkG5 5/cCjncKxkHSAXSlcgVGeTLsdHIeERy8Mm1ZxQTqraBgBKce+ko7/0GH5068oVJVuhNwhn ZaodRW9xqSE+W28GbjaTa+jAaw7U8rcNrhao9lViqZ25wVhyHktMEdhqIMGSf/w5z/2IPR jaFRd5FhWsK2tYyCLX+HNTRxxmucmSVo0JScgCBCkJZjBUiUCrdzJ/3LwvjtLD+he9HiF7 aZjZVvsACU14l224TtJU2+/DWzGnWjvrSgCoYX7Iy9c9H3zgjm8HNVQT0UdPPg== Date: Tue, 12 Aug 2025 13:59:30 +0200 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20250812115930.GI29660@pb2> References: <6e208946-690c-4cbb-9539-bd85df02430c@lynne.ee> <20250811131052.GZ29660@pb2> <00ad392c-084e-4ab9-a314-48412d56c348@lynne.ee> MIME-Version: 1.0 In-Reply-To: <00ad392c-084e-4ab9-a314-48412d56c348@lynne.ee> X-GND-State: clean X-GND-Score: -70 X-GND-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdefgddufeehvdejucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuifetpfffkfdpucggtfgfnhhsuhgsshgtrhhisggvnecuuegrihhlohhuthemuceftddunecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenfghrlhcuvffnffculdeftddmnecujfgurhepfffhvffukfhfgggtuggjsehgtderredttddvnecuhfhrohhmpefoihgthhgrvghlucfpihgvuggvrhhmrgihvghruceomhhitghhrggvlhesnhhivgguvghrmhgrhigvrhdrtggtqeenucggtffrrghtthgvrhhnpeeigeektdejudffjefhteegjedtgeettefggedthfejgfevhfetgeekjedtvdfhveenucfkphepgedurdeiiedrieehrddujeeinecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehinhgvthepgedurdeiiedrieehrddujeeipdhhvghloheplhhotggrlhhhohhsthdpmhgrihhlfhhrohhmpehmihgthhgrvghlsehnihgvuggvrhhmrgihvghrrdgttgdpnhgspghrtghpthhtohepuddprhgtphhtthhopehffhhmphgvghdquggvvhgvlhesfhhfmhhpvghgrdhorhhg X-GND-Sasl: michael@niedermayer.cc Subject: Re: [FFmpeg-devel] Plugins architecture 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="===============2194386560251526384==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============2194386560251526384== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="iQYn6y8Ii+ajMmDT" Content-Disposition: inline --iQYn6y8Ii+ajMmDT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Lynne On Tue, Aug 12, 2025 at 03:38:31PM +0900, Lynne wrote: > On 11/08/2025 22:10, Michael Niedermayer wrote: > > Hi Lynne > >=20 > > On Mon, Aug 11, 2025 at 09:22:26PM +0900, Lynne wrote: > > [...] > > > To me, at least, I can imagine five options: > > >=20 > > > Option 1 - we have an official binary plugin interface, free for > > > everyone to use with no limitation. > >=20 > > That requires someone to create that "binary plugin interface", > > that person seems not existing, so i dont think its an "option" >=20 > Its a better option in that its a one-time affair, and also there's no > endorsement of such plugins by us. noone has endorsed anything and supporting binary plugins is not a "one time affair" its the very opposit, its ongoing continous work to maintain a compatible and working API and ABI > Also, we had such an infrastructure in the past with users being able to > give their own AVCodec structures to lavc, without us having guarantees t= hat > we wouldn't break this. > It wouldn't take much to revert that and implement support for this, along > with freezing AVCodec longer-term than major bumps. thats just talk, you wont maintain any of this. and i doubt the community will freeze the whole API and ABI for it nor should we. And if its not frozen then a API needs to be designed for these binary plug= ins But you are welcome to create a functioing API for binary plugins and maintain it long term. Iam certainly not going to stop you. This of course has nothing to do with source pligins. They are entirely separate things. thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Everything should be made as simple as possible, but not simpler. -- Albert Einstein --iQYn6y8Ii+ajMmDT Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEKAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCaJssnwAKCRBhHseHBAsP q5+5AKCMLR2CiCX7OqNV8HW4RwAjhEQccACfW8jxFyl2T9UI82q7HKZfcc+7B5w= =V18j -----END PGP SIGNATURE----- --iQYn6y8Ii+ajMmDT-- --===============2194386560251526384== 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". --===============2194386560251526384==--