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 4F4F6423E4 for ; Mon, 17 Jan 2022 13:51:14 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id E091068AFE9; Mon, 17 Jan 2022 15:51:11 +0200 (EET) Received: from nef.ens.fr (nef2.ens.fr [129.199.96.40]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 682DB68AF33 for ; Mon, 17 Jan 2022 15:51:05 +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 20HDp4SW024343 for ; Mon, 17 Jan 2022 14:51:04 +0100 Received: by phare.normalesup.org (Postfix, from userid 1001) id 0EF93E1DC8; Mon, 17 Jan 2022 14:51:04 +0100 (CET) Date: Mon, 17 Jan 2022 14:51:04 +0100 From: Nicolas George To: FFmpeg development discussions and patches Message-ID: References: <20220113015101.4-1-jamrial@gmail.com> <20220113015101.4-2-jamrial@gmail.com> MIME-Version: 1.0 In-Reply-To: X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (nef.ens.fr [129.199.96.32]); Mon, 17 Jan 2022 14:51:04 +0100 (CET) Subject: Re: [FFmpeg-devel] [PATCH 001/281] Add a new channel layout API 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="===============1961031650059298578==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============1961031650059298578== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="yS9itWqoZwu10CPt" Content-Disposition: inline --yS9itWqoZwu10CPt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable James Almer (12022-01-17): > And they can if they want to. It has a very specific purpose and it fulfi= lls > it. Just be clearer in the documentation. > Please, stop asking for this. It's an incredibly niche usecase you want f= or > libavfilter, so you can and should implement it there. The API is there a= nd > you can use it, you don't need to overdesign these general purpose helpers > to create these bizarre scenarios just to remove one or two filters from > your chain. I will not stop asking for this, it is not specific to libavfilter: with a quick search, I spot -map_channel that requires exactly the same feature. There may be filters that require an option to distinguish one channel in particular; even if there are no now, there may be in the future. Can you guarantee it does not and will not happen? This use case happens at several places, therefore the parsing belongs in a common API. Regards, --=20 Nicolas George --yS9itWqoZwu10CPt Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE6ooRQGBoNzw0KnwPcZVLI8pNxgwFAmHldEUACgkQcZVLI8pN xgxvJA//UDRXlXtWXeNm42Q/7BAqIYksbP5F3V47nPJZ+kCF9caoFd6vXT564LNE yu2Q0FD1qowFw6AuiWZ0mEP6C+0dCMtsqplu8Voi6RTTmaeSNzvlt6+EKJY8jAvh pliih34Hbztk8xw7mGADs63ChNCpuixNtjFxoYVQ2HabDpaiiWF7kLEMC27oXzab X61Iydp73iP7LX4IGcF9ukZwjg/rpPjdykAEaV9IPfcV+fphfG+WoUdc5iMwPvBf rDAJ6TcwcRqu+QX498xyiTM+Rc/0d7KC7y1/vsuuB5kosSTTAnWKldWVZlE8uE/I sQGYNcILHCsAf3Q64YjELh4JK2X7MCzWwITnWdsSV5mCx74WUizqB8XWU40fuaCf XpkOzZC44u1P0dZ6uzqYKIrA2cWeLMvt4M32ZwTt6+jwk++Nlj+Loa5O7r70ZOqW c+KFGu9gnodiKQExfNOsyAjJ8HjH5Hvyl2kXcSoH1K/EFfRaLYd3FLLotfv18RXd Ql9rtJS5pKxCwKJMLT46f79oZPQ3mQZfTJN6BoSyz6vIhbGRJ+PxTYl6vD0PEBM6 WRYU8ByMSZPjEVN9CmRNn9hOGT2fn0O1tKfCXkOfBGvUaui/YXZ8Uyr5YnWhHW9G w7CrACsU/q0+XdiO1u0Tixs11T292jrRBzUhyIE6c/T52wCc+78= =IXDU -----END PGP SIGNATURE----- --yS9itWqoZwu10CPt-- --===============1961031650059298578== 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". --===============1961031650059298578==--