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 21C754799D for ; Thu, 28 Sep 2023 15:28:59 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 7AD3168CB78; Thu, 28 Sep 2023 18:28:57 +0300 (EEST) Received: from nef.ens.fr (nef2.ens.fr [129.199.96.40]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 2A25368CB06 for ; Thu, 28 Sep 2023 18:28:51 +0300 (EEST) 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 38SFSoVB017834 for ; Thu, 28 Sep 2023 17:28:50 +0200 Received: by phare.normalesup.org (Postfix, from userid 1001) id 67A45EB5BD; Thu, 28 Sep 2023 17:28:50 +0200 (CEST) Date: Thu, 28 Sep 2023 17:28:50 +0200 From: Nicolas George To: FFmpeg development discussions and patches Message-ID: References: <5cc700e859d15716ca1e9d7e0ca3d2faab77f3d5.camel@haerdin.se> <20230927201829.GT3543730@pb2> <4860785.31r3eYUQgx@basile.remlab.net> MIME-Version: 1.0 In-Reply-To: <4860785.31r3eYUQgx@basile.remlab.net> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (nef.ens.fr [129.199.96.32]); Thu, 28 Sep 2023 17:28:50 +0200 (CEST) Subject: Re: [FFmpeg-devel] [RFC] Release 6.1 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="===============9168953228418543071==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============9168953228418543071== Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="1l0Zgy/U32vsK/4m" Content-Disposition: inline --1l0Zgy/U32vsK/4m Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable R=E9mi Denis-Courmont (12023-09-28): > You can repeat the contrary as much as you want, we do not believe that y= our=20 > SDR code fits in FFmpeg. Why do you not understand this? We understand that very well. Once again, it is you who do not understand something: your BELIEF that SDR does not belong in ffmpeg is nothing more than that, a belief, an opinion, and it weighs nothing in front of the argument that some users want it. > Like no, seriously. If you really want to generic support for AM and FM R= X in=20 > FFmpeg, then you should use implement frontends for the already *existing= * HAL=20 > (that would be V4L radio and ALSA on Linux), or perhaps, write a new user- > space HAL library that would accomodate both hardware radio RX devices an= d=20 > SDR. Did you miss the part where he explained he was not interesting in doing it like that? > In fact, the SDR code has quite a number of impediments that all but guar= antee=20 > that it will not "catch on" in FFmpeg: > - it requires niche hardware, Like a few components of libavdevice, that is not an issue. > - it only works on some limited set of OSes (if not only Linux), Like a few components of libavdevice, that is not an issue. > - it will be subject to all the FFmpeg processes and drama, This problem does not come from SDR, it comes from you. > - it will be obscured by FFmpeg's existing own fame, remaining an obscure= =20 > feature set that hardly anybody outside FFmpeg-devel knows about. Like a lot of features. Scrapping the bottom of drawers for arguments are you? --=20 Nicolas George --1l0Zgy/U32vsK/4m Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE6ooRQGBoNzw0KnwPcZVLI8pNxgwFAmUVm7AACgkQcZVLI8pN xgxoGhAAnEXcOotmZ+YMD460r7trXhWqGX471/tCq4suGvJjajtF8VoWJYH+PGKu vfQFKGn2TxLaSvz94/xfqvd3eGZan+OHTQxjTf+m7oj0hWVEYAjQ4tlnxYnt6dRE Pn8tDNfz453FkoemIlQ8tJhJAong95H0nP3gHLZ8aZhpkx7UQxrgnXqtglj3Rp1R JK8JTc0kU1tCRZVlPxyjZ/nWjqGJUHblZoJXizDcptuy95FsWTGNUDEY24Y6E4VG dXk3RGDFQb2ngoQFmwHtsoRIZ3ZSZncAzLoVju6G0LOm+989amifjI6un4cMHwC8 EFgLGorOHrtgkLHaNbx49pgWq0Ft0AO+rEVOG3nTjRIi4ivcYxmLocpMUO8Da0s0 OVDyr5S52AuaF+DBS2PUUCYuQz9XFbUYodJr2VU/U7taxuy7OeR2v7RjKjKQTgF9 Yn6mUyHodFmNR+68+UVEtMJCtMNm/tEnDWj7BKICjibdGk0JEqCgZCaTlPFx/jAO Rv+GO4EEFMs/Dg0DaBuN3SuEejJoIkIbFBqVOIwfuLsxzKytMOIBa/rAjDp6xjAp FVVld7w8Qvs8kHlewoMfD4zDZ1E5OnNFvfE+SN/i9zcG/PmAN+MxzfqXJggFYHZx MhAJnZ7eBfaF9JrwUj9QWIntG6QEfpOuToHaxAwxayd/aQheb1A= =JDc5 -----END PGP SIGNATURE----- --1l0Zgy/U32vsK/4m-- --===============9168953228418543071== 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". --===============9168953228418543071==--