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 65B4C428DD for ; Sun, 5 Jun 2022 13:20:44 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 3331268B623; Sun, 5 Jun 2022 16:20:42 +0300 (EEST) Received: from mail0.khirnov.net (red.khirnov.net [176.97.15.12]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id EC02D68B0CD for ; Sun, 5 Jun 2022 16:20:35 +0300 (EEST) Received: from localhost (localhost [IPv6:::1]) by mail0.khirnov.net (Postfix) with ESMTP id 76DD1240175 for ; Sun, 5 Jun 2022 15:20:35 +0200 (CEST) Received: from mail0.khirnov.net ([IPv6:::1]) by localhost (mail0.khirnov.net [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id 5wmScoiYo_kv for ; Sun, 5 Jun 2022 15:20:34 +0200 (CEST) Received: from lain.red.khirnov.net (lain.red.khirnov.net [IPv6:2001:67c:1138:4306::3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "lain.red.khirnov.net", Issuer "smtp.khirnov.net SMTP CA" (verified OK)) by mail0.khirnov.net (Postfix) with ESMTPS id BACD02400F5 for ; Sun, 5 Jun 2022 15:20:34 +0200 (CEST) Received: by lain.red.khirnov.net (Postfix, from userid 1000) id C54F51601B2; Sun, 5 Jun 2022 15:20:34 +0200 (CEST) From: Anton Khirnov To: FFmpeg development discussions and patches In-Reply-To: =?utf-8?q?=3CDM8P223MB03655A93A4EC40F315580519BAA39=40DM8P223MB?= =?utf-8?q?0365=2ENAMP223=2EPROD=2EOUTLOOK=2ECOM=3E?= References: <20220323155720.20017-1-anton@khirnov.net> =?utf-8?q?=3CDM8P223M?= =?utf-8?q?B0365783CC5AF48817C137226BAA39=40DM8P223MB0365=2ENAMP223=2EPROD?= =?utf-8?q?=2EOUTLOOK=2ECOM=3E?= <165441247425.5088.1095760194724448724@lain.red.khirnov.net> =?utf-8?q?=3CD?= =?utf-8?q?M8P223MB036512ED3D29D532CECAF58DBAA39=40DM8P223MB0365=2ENAMP223?= =?utf-8?q?=2EPROD=2EOUTLOOK=2ECOM=3E?= <165441720181.5088.3725748658698613904@lain.red.khirnov.net> =?utf-8?q?=3CD?= =?utf-8?q?M8P223MB0365143E20505C262ACE1D89BAA39=40DM8P223MB0365=2ENAMP223?= =?utf-8?q?=2EPROD=2EOUTLOOK=2ECOM=3E?= <165442573064.5088.16462974575447102257@lain.red.khirnov.net> =?utf-8?q?=3C?= =?utf-8?q?DM8P223MB03655A93A4EC40F315580519BAA39=40DM8P223MB0365=2ENAMP223?= =?utf-8?q?=2EPROD=2EOUTLOOK=2ECOM=3E?= Mail-Followup-To: FFmpeg development discussions and patches Date: Sun, 05 Jun 2022 15:20:34 +0200 Message-ID: <165443523477.5088.13247718055308484660@lain.red.khirnov.net> User-Agent: alot/0.8.1 MIME-Version: 1.0 Subject: Re: [FFmpeg-devel] [PATCH 1/8] lavc/avcodec: simplify codec id/type validity checking 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: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: Quoting Soft Works (2022-06-05 13:10:49) > > > > -----Original Message----- > > From: ffmpeg-devel On Behalf Of Anton > > Khirnov > > Sent: Sunday, June 5, 2022 12:42 PM > > To: FFmpeg development discussions and patches > > Subject: Re: [FFmpeg-devel] [PATCH 1/8] lavc/avcodec: simplify codec id/type > > validity checking > > > > So much text, but no actual answer. Again: > > > I fail to see how calling avcodec_open2() with AVMEDIA_TYPE_ATTACHMENT > > > is valid API usage. What do you expect it to do? There are no > > > AVMEDIA_TYPE_ATTACHMENT decoders. > > As you didn't mention anything about how you want to address it, does it > mean that your intention is to leave it as is and declare all other code > being wrong? Frankly, your attitude of breathlessly repeating "ffprobe is BROKEN, and this is HORRIBLE" is unhelpful. I am open to various kinds of solutions, which include (temporarily?) reintroducing previous behavior, but first we must determine what the actual issue is. I.e. whether it is libavcodec or ffprobe that is broken. You seem uninterested in this question, which makes me not very interested in spending time on this. -- Anton Khirnov _______________________________________________ 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".