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 8BD8D4A85C for ; Mon, 17 Jun 2024 07:22:57 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id 6F1EF68D760; Mon, 17 Jun 2024 10:22:55 +0300 (EEST) Received: from mail0.khirnov.net (red.khirnov.net [176.97.15.12]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id B155D68D5CA for ; Mon, 17 Jun 2024 10:22:49 +0300 (EEST) Authentication-Results: mail0.khirnov.net; dkim=pass (2048-bit key; unprotected) header.d=khirnov.net header.i=@khirnov.net header.a=rsa-sha256 header.s=mail header.b=JfVW9qSY; dkim-atps=neutral Received: from localhost (localhost [IPv6:::1]) by mail0.khirnov.net (Postfix) with ESMTP id 73ADF240DAC for ; Mon, 17 Jun 2024 09:22:49 +0200 (CEST) Received: from mail0.khirnov.net ([IPv6:::1]) by localhost (mail0.khirnov.net [IPv6:::1]) (amavis, port 10024) with ESMTP id 7JPH7r3NHudn for ; Mon, 17 Jun 2024 09:22:47 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=khirnov.net; s=mail; t=1718608967; bh=uyk/9z+QT97CCqBtUKUwViQhq90qN+QPMZlTofHTaK4=; h=Subject:From:To:In-Reply-To:References:Date:From; b=JfVW9qSYXSTDFVWM1RnaO3UaLc4I52P625mkIDNBd9h4uK3jhyTzrJUMUOJTkPP3r 5aFXL7HjLchNxbRfZ1MyBURk/NW607hCqhxde3ujAcz3OdicfFohv8ySKQfxpvZBDt e9vc9ibqcL0F9rzhdbZarrySyYuFmP/XnaOT/K4DW5dKBH2MwB4uE78sbZeuCNoRBQ ezO6VkBOrC6mUpW27HS90DSkyd7LQJp3vJrgReLScdddq1JEDksfkldKjEmVH6nu0u NgORMcJnn1D9JBnvDtul52csqkMEf8wtTU+GyYODfdmLNl14ggCEwRtncQ+J8sFoNP 7ZtbU80jX9acA== Received: from lain.khirnov.net (lain.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.khirnov.net", Issuer "smtp.khirnov.net SMTP CA" (verified OK)) by mail0.khirnov.net (Postfix) with ESMTPS id 3B6E02404E5 for ; Mon, 17 Jun 2024 09:22:47 +0200 (CEST) Received: by lain.khirnov.net (Postfix, from userid 1000) id 2736A1601B9; Mon, 17 Jun 2024 09:22:47 +0200 (CEST) From: Anton Khirnov To: FFmpeg development discussions and patches In-Reply-To: References: <20240614093903.98716-1-post@frankplowman.com> <83198815-2c79-422b-a857-77f61e077825@frankplowman.com> Mail-Followup-To: FFmpeg development discussions and patches Date: Mon, 17 Jun 2024 09:22:47 +0200 Message-ID: <171860896713.28895.5648189518023056707@lain.khirnov.net> User-Agent: alot/0.8.1 MIME-Version: 1.0 Subject: Re: [FFmpeg-devel] [PATCH] lavc/vvc: Invalidate PPSs which refer to a changed SPS 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 Mark Thompson (2024-06-16 17:26:26) > Is there some requirement in H.266 that in a single stream the PPS precedes the SPS? > > Currently we effectively require that for a single stream because we use the SPS to enforce constraints on the PPS in both H.265 and H.266, but I'm not seeing a hard dependency and it looks like it will currently work on later stream starts as long as the parameters don't change too much. > > In H.264 there is an explicit dependency because you need chroma_format_idc to parse scaling lists, but again this will usually work because it's unlikely to change inline. IIRC the spec requirement is about PPS activation, not order in the bytestream. Our decoder does impose constraints on the order, and I don't recall it ever causing problems, but it does not follow from the spec. -- 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".