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 99A004619C for ; Fri, 5 Jan 2024 20:47:24 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id A2A8F68CDDD; Fri, 5 Jan 2024 22:47:21 +0200 (EET) Received: from relay3-d.mail.gandi.net (relay3-d.mail.gandi.net [217.70.183.195]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id 9629468C996 for ; Fri, 5 Jan 2024 22:47:15 +0200 (EET) Received: by mail.gandi.net (Postfix) with ESMTPSA id 75CF360004 for ; Fri, 5 Jan 2024 20:47:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=niedermayer.cc; s=gm1; t=1704487634; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=TeoBXmzFQ7fqlM0JzhG6xUs5tQ63TBBX+b1FJ/voNLE=; b=CqwKjL0Pb8dOuHTSQS55iwz+0JkOnV/2PsmNtt+6NNYfd61jyLW7e5e4g+WcqJCtC+cicF fx7P76+kMnM6kkq9/+vU3sRMjDzZqLvOfvmkX3MMOD9ZORP2FbzNtIQRyuQjmHKao3C3ta hgtmEBgqAFKrgjEWFjM6Mn758a5+/5+jhfocra0CZWxkOAtFpA5xtT+IYPPjnomlezBFvx Ajh0FBAU7e9Z7Yf1nAtcAFAK67XUFQogP6su+GP9xZ6rs+DlhPOBjYrWxLjZ3MCJsjPbZS iAzXXHLp29Enwvf8iA9iifv6WcrZ8CNTrrLMcGZY1Bl/z4r1se1g2kxonHQNsw== Date: Fri, 5 Jan 2024 21:47:13 +0100 From: Michael Niedermayer To: FFmpeg development discussions and patches Message-ID: <20240105204713.GD6420@pb2> References: <20240101141239.6623-1-nuomi2021@gmail.com> <20240103183821.GY6420@pb2> <5859498f-c481-040-11a0-6dd67a17094@martin.st> <92d9a765-062c-4174-8a38-4589e778339b@gmail.com> <7f1d047-cce2-30f3-e5be-6444896d12c@martin.st> MIME-Version: 1.0 In-Reply-To: <7f1d047-cce2-30f3-e5be-6444896d12c@martin.st> X-GND-Sasl: michael@niedermayer.cc Subject: Re: [FFmpeg-devel] [PATCH v9 09/13] vvcdec: add LMCS, Deblocking, SAO, and ALF filters 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="===============1428124783756041425==" Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: --===============1428124783756041425== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Guc8tSoCmQxpftue" Content-Disposition: inline --Guc8tSoCmQxpftue Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 05, 2024 at 01:55:08PM +0200, Martin Storsj=C3=B6 wrote: > On Thu, 4 Jan 2024, James Almer wrote: >=20 > > On 1/4/2024 10:57 AM, Nuo Mi wrote: > > > On Thu, Jan 4, 2024 at 8:07=E2=80=AFPM Martin Storsj=C3=B6 wrote: > > >=20 > > > > On Thu, 4 Jan 2024, Nuo Mi wrote: > > > >=20 > > > > > On Thu, Jan 4, 2024 at 2:38=E2=80=AFAM Michael Niedermayer < > > > > michael@niedermayer.cc> > > > > > wrote: > > > > >=20 > > > > > > On Tue, Jan 02, 2024 at 05:47:53PM +0800, Nuo Mi wrote: > > > > > > [...] > > > > > > > maintainer, and any HEVC code change requires a very long rev= iew time. > > > > > >=20 > > > > > > I think changes that just move code around or rename functions = would be > > > > > > quickly reviewed > > > > > > I dont know if things are 1:1 identical or some complex changes= are > > > > needed > > > > > >=20 > > > > > > I think if things are 1:1 identical it can be done now otherwis= e it may > > > > be > > > > > > better to do after the initial merge > > > > > >=20 > > > > > Agree, > > > > >=20 > > > > > Taking https://patchwork.ffmpeg.org/project/ffmpeg/list/?series= =3D10404 > > > > as > > > > > an example, > > > > > The following items are worth discussing, though they won't impac= t the > > > > > functionality: > > > > > 1. Can we use "XVC" as a common name for HEVC and VVC, or should = we use > > > > > "h2656" instead of "XVC"? > > > >=20 > > > > The name "xvc" is potentially confusing - there is another video co= dec > > > > with the name xvc as well - see https://xvc.io. > > > >=20 > > > Yes, it's been dead for 4 years :). https://github.com/divideon/xvc > > > Not sure if the new codec will be named as xvc or not. > > > h2656 is safer but ugly > >=20 > > How about h26x? h264 also shares some code with hevc and vvc, like the > > NALu splitting code. >=20 > h264x looks clearer, not that ugly, and less ambiguous to me, so that sou= nds > reasonable to me. i agree there h261, h262/mpeg2, h263/mpeg4 it would be better for clarity if these groups can be distinguished from th= eir names or location thx [...] --=20 Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB The bravest are surely those who have the clearest vision of what is before them, glory and danger alike, and yet notwithstanding go out to meet it. -- Thucydides --Guc8tSoCmQxpftue Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EABEIAB0WIQSf8hKLFH72cwut8TNhHseHBAsPqwUCZZhqygAKCRBhHseHBAsP q5PVAKCaFdpiuA7bzdIBOQs6B2vWhKbmwQCfaqnKeHkd/eCDsdK48km7QjtgKR8= =PKfM -----END PGP SIGNATURE----- --Guc8tSoCmQxpftue-- --===============1428124783756041425== 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". --===============1428124783756041425==--