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 4145A40360 for ; Mon, 20 Dec 2021 14:55:29 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id A147C68AB71; Mon, 20 Dec 2021 16:55:28 +0200 (EET) Received: from mail0.khirnov.net (red.khirnov.net [176.97.15.12]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 0058168A4CD for ; Mon, 20 Dec 2021 16:55:22 +0200 (EET) Received: from localhost (localhost [IPv6:::1]) by mail0.khirnov.net (Postfix) with ESMTP id 8B13224017C; Mon, 20 Dec 2021 15:55:22 +0100 (CET) Received: from mail0.khirnov.net ([IPv6:::1]) by localhost (mail0.khirnov.net [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id i8LYYvaqh1tv; Mon, 20 Dec 2021 15:55:21 +0100 (CET) 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 3F97D240179; Mon, 20 Dec 2021 15:55:21 +0100 (CET) Received: by lain.red.khirnov.net (Postfix, from userid 1000) id 371B016008E; Mon, 20 Dec 2021 15:55:21 +0100 (CET) From: Anton Khirnov To: FFmpeg development discussions and patches In-Reply-To: <20211220154745.GB7072@xor.haasn.dev> References: <20211212115546.119662-1-ffmpeg@haasn.xyz> <20211212115546.119662-4-ffmpeg@haasn.xyz> <163999519548.13029.13385878156195650068@lain.red.khirnov.net> <20211220154745.GB7072@xor.haasn.dev> Mail-Followup-To: FFmpeg development discussions and patches , Niklas Haas Date: Mon, 20 Dec 2021 15:55:21 +0100 Message-ID: <164001212111.13443.14484780386734124009@lain.red.khirnov.net> User-Agent: alot/0.8.1 MIME-Version: 1.0 Subject: Re: [FFmpeg-devel] [PATCH v5 4/6] lavc: Implement Dolby Vision RPU parsing 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 Cc: Niklas Haas 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 Niklas Haas (2021-12-20 15:47:45) > So, the reason I made this an avctx is because I'm anticipating the need > to check `avctx->err_recognition` if the CRC32 check ever gets > implemented. In theory we could also do some profile-based verification > in AV_EF_BITSTREAM / AV_EF_EXPLODE, to check if the coded RPU values > actually match the legal combinations restricted by the profile > specification. I would much prefer this single flag to be passed in as a parameter, given how much of a god object AVCodecContext already is. -- 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".