From: Hendrik Leppkes <h.leppkes@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] lavu/pixfmt: summarize yuv naming conventions
Date: Wed, 27 Jul 2022 17:58:09 +0200
Message-ID: <CA+anqdyscfymtT+Ft0KLhg5aFDO=R92q6xFLGhd30cTO5-bLOA@mail.gmail.com> (raw)
In-Reply-To: <20220727152447.30944-1-george@nsup.org>
On Wed, Jul 27, 2022 at 5:25 PM Nicolas George <george@nsup.org> wrote:
>
> Signed-off-by: Nicolas George <george@nsup.org>
> ---
> libavutil/pixfmt.h | 17 +++++++++++++++++
> 1 file changed, 17 insertions(+)
>
>
> Note: we have log2_chroma_h = 2 for yuv410p, meaning each chroma pixel
> is 4×4 luma pixels, but everywhere I look on the web, ilcuding:
> https://en.wikipedia.org/wiki/Chroma_subsampling
> I find that it is supposed to be 4×2, and we should set log2_chroma_h = 1.
> Who is right?
Following the actual naming convention, you would arrive at a 4x2
grid, however even the Wikipedia article linked above is inconsistent
with that. In the first section describing how the naming convention
works, it lists an exception that 4:1:0 is supposedly referencing a
4x4 grid, however further down where 4:1:0 is being detailed, this is
no longer the case.
Many other resources just seem to copy this second Wikipedia description.
We have a variety of decoders that use this format as it is defined
right now, presumably successfully. Of course that could just mean
this format exists, and is just named wrong, on the other hand, did
any decoder ever require the one pixel per 4x4 grid format, giving any
technical baking to the other interpretation?
- Hendrik
_______________________________________________
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".
next prev parent reply other threads:[~2022-07-27 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 15:24 Nicolas George
2022-07-27 15:58 ` Hendrik Leppkes [this message]
2022-07-27 16:48 ` Nicolas George
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='CA+anqdyscfymtT+Ft0KLhg5aFDO=R92q6xFLGhd30cTO5-bLOA@mail.gmail.com' \
--to=h.leppkes@gmail.com \
--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