Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v9 09/13] vvcdec: add LMCS, Deblocking, SAO, and ALF filters
Date: Fri, 5 Jan 2024 21:47:13 +0100
Message-ID: <20240105204713.GD6420@pb2> (raw)
In-Reply-To: <7f1d047-cce2-30f3-e5be-6444896d12c@martin.st>


[-- Attachment #1.1: Type: text/plain, Size: 2322 bytes --]

On Fri, Jan 05, 2024 at 01:55:08PM +0200, Martin Storsjö wrote:
> On Thu, 4 Jan 2024, James Almer wrote:
> 
> > On 1/4/2024 10:57 AM, Nuo Mi wrote:
> > > On Thu, Jan 4, 2024 at 8:07 PM Martin Storsjö <martin@martin.st> wrote:
> > > 
> > > > On Thu, 4 Jan 2024, Nuo Mi wrote:
> > > > 
> > > > > On Thu, Jan 4, 2024 at 2:38 AM Michael Niedermayer <
> > > > michael@niedermayer.cc>
> > > > > wrote:
> > > > > 
> > > > > > On Tue, Jan 02, 2024 at 05:47:53PM +0800, Nuo Mi wrote:
> > > > > > [...]
> > > > > > > maintainer, and any HEVC code change requires a very long review time.
> > > > > > 
> > > > > > 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
> > > > > > 
> > > > > > I think if things are 1:1 identical it can be done now otherwise it may
> > > > be
> > > > > > better to do after the initial merge
> > > > > > 
> > > > > Agree,
> > > > > 
> > > > > Taking   https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=10404
> > > > as
> > > > > an example,
> > > > > The following items are worth discussing, though they won't impact the
> > > > > functionality:
> > > > > 1. Can we use "XVC" as a common name for HEVC and VVC, or should we use
> > > > > "h2656" instead of "XVC"?
> > > > 
> > > > The name "xvc" is potentially confusing - there is another video codec
> > > > with the name xvc as well - see https://xvc.io.
> > > > 
> > > 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
> > 
> > How about h26x? h264 also shares some code with hevc and vvc, like the
> > NALu splitting code.
> 
> h264x looks clearer, not that ugly, and less ambiguous to me, so that sounds
> reasonable to me.

i agree
there h261, h262/mpeg2, h263/mpeg4
it would be better for clarity if these groups can be distinguished from their
names or location

thx

[...]
-- 
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

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
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".

  reply	other threads:[~2024-01-05 20:47 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240101141239.6623-1-nuomi2021@gmail.com>
2024-01-01 14:12 ` [FFmpeg-devel] [PATCH v9 01/13] vvcdec: add vvc_data Nuo Mi
2024-01-01 14:12 ` [FFmpeg-devel] [PATCH v9 02/13] vvcdec: add parameter parser for sps, pps, ph, sh Nuo Mi
2024-01-01 14:12 ` [FFmpeg-devel] [PATCH v9 03/13] vvcdec: add cabac decoder Nuo Mi
2024-01-01 15:13   ` Lynne
2024-01-02 13:21     ` Nuo Mi
2024-01-02 15:57       ` Lynne
2024-01-03  1:38         ` Nuo Mi
2024-01-01 17:34   ` Michael Niedermayer
2024-01-02 13:44     ` Nuo Mi
2024-01-01 14:12 ` [FFmpeg-devel] [PATCH v9 04/13] vvcdec: add reference management Nuo Mi
2024-01-01 14:12 ` [FFmpeg-devel] [PATCH v9 05/13] vvcdec: add motion vector decoder Nuo Mi
2024-01-01 14:12 ` [FFmpeg-devel] [PATCH v9 06/13] vvcdec: add inter prediction Nuo Mi
2024-01-01 15:04   ` Lynne
2024-01-02 14:16     ` Nuo Mi
2024-01-02 14:30       ` Kieran Kunhya
2024-01-02 15:59       ` Lynne
2024-01-01 14:12 ` [FFmpeg-devel] [PATCH v9 07/13] vvcdec: add inv transform 1d Nuo Mi
2024-01-01 14:50   ` Lynne
2024-01-02 13:01     ` Nuo Mi
2024-01-02 15:55       ` Lynne
2024-01-03 12:04         ` Nuo Mi
2024-01-01 14:12 ` [FFmpeg-devel] [PATCH v9 08/13] vvcdec: add intra prediction Nuo Mi
2024-01-01 14:12 ` [FFmpeg-devel] [PATCH v9 09/13] vvcdec: add LMCS, Deblocking, SAO, and ALF filters Nuo Mi
2024-01-01 15:17   ` Lynne
2024-01-02  9:47     ` Nuo Mi
2024-01-02 11:38       ` Jean-Baptiste Kempf
2024-01-02 15:51       ` Lynne
2024-01-03  1:14         ` Nuo Mi
2024-01-03 18:38       ` Michael Niedermayer
2024-01-04 11:45         ` Nuo Mi
2024-01-04 12:06           ` Martin Storsjö
2024-01-04 13:57             ` Nuo Mi
2024-01-04 14:53               ` James Almer
2024-01-05  0:02                 ` Nuo Mi
2024-01-05 11:55                 ` Martin Storsjö
2024-01-05 20:47                   ` Michael Niedermayer [this message]
2024-01-01 14:12 ` [FFmpeg-devel] [PATCH v9 10/13] vvcdec: add dsp init and inv transform Nuo Mi
2024-01-01 14:12 ` [FFmpeg-devel] [PATCH v9 11/13] vvcdec: add CTU parser Nuo Mi
2024-01-01 14:12 ` [FFmpeg-devel] [PATCH v9 12/13] vvcdec: add CTU thread logical Nuo Mi
2024-01-01 14:12 ` [FFmpeg-devel] [PATCH v9 13/13] vvcdec: add vvc decoder Nuo Mi
2024-01-01 14:53   ` Lynne
2024-01-01 15:14     ` Hendrik Leppkes
2024-01-01 15:22       ` Lynne
2024-01-02  9:38         ` Nuo Mi
2024-01-02 11:41           ` Jean-Baptiste Kempf
2024-01-02 16:00           ` Lynne
2024-01-05 20:48   ` James Almer
2024-01-06 17:47   ` James Almer
2024-01-07  5:31     ` Nuo Mi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240105204713.GD6420@pb2 \
    --to=michael@niedermayer.cc \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git