From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 1/7] lavu/pixfmt: summarize yuv naming conventions Date: Thu, 4 Aug 2022 17:04:41 +0200 Message-ID: <20220804150441.GL2088045@pb2> (raw) In-Reply-To: <YuvQR4jD5yQLQnX0@phare.normalesup.org> [-- Attachment #1.1: Type: text/plain, Size: 2061 bytes --] On Thu, Aug 04, 2022 at 03:57:27PM +0200, Nicolas George wrote: > Michael Niedermayer (12022-08-04): > > You seem to describe samples as rectangular areas of constant value IIUC. > > If you look at the ITU/ISO specs (mpeg2, h264 or others) they are described > > by point samples. The desity of samples matches. While the default locations > > do not. > > What you list above are where probably most sane people would place the > > samples. But ISO/ITU, probably because of historic TV standard reasons and > > interlacing convertion reasons place the chroma samples in a more crooked way > > I think either the ascii art should be adapted or the text should clarify > > this difference > > I am not sure what exactly you explain. What i meant is what is also in AVChromaLocation The chroma sample locations are shifted from where one would expect > > The picture represents memory cells and how we think of them when we > implement generic functions, for example cropping or drawutils. Do we > need to fix all this code somehow? I suspect several filters are somewhat "wrong" for example hflip fliping 4:1:1 would turn a: *--- into ---* where * is teh chroma sample location, i dont think it updates the chroma sample location metadata nor does it apply some filter to chroma to shift by 3/4 samples. so it looks wrong, one of the 2 is neeed. vf_scale contains some code to handle this but iam not seeing code considering the input and output frames chroma location metadata All this leads to small errors, often probably not vissible when you have one one chroma sample for 4 luma samples you will always have some artifacts on sharp color edges, if the location of the chroma sample is wrong the artifact would be more to one side of a diagonal edge than the other. If the locations are correct it should be more symmetric in theory. thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB No great genius has ever existed without some touch of madness. -- Aristotle [-- 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".
next prev parent reply other threads:[~2022-08-04 15:04 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-02 16:54 Nicolas George 2022-08-02 16:54 ` [FFmpeg-devel] [PATCH 2/7] lavfi/graphdump: add plain listing output Nicolas George 2022-08-02 16:54 ` [FFmpeg-devel] [PATCH 3/7] fftools: add -lavfi_dump option Nicolas George 2022-08-02 16:54 ` [FFmpeg-devel] [PATCH 4/7] lavfi/(a)format: factor finding the delimiter Nicolas George 2022-08-02 16:54 ` [FFmpeg-devel] [PATCH 5/7] lavfi/(a)format: support slash as a delimiter Nicolas George 2022-08-02 16:54 ` [FFmpeg-devel] [PATCH 6/7] lavi/pixdesc: add comments about pixel format scoring Nicolas George 2022-08-04 13:52 ` Michael Niedermayer 2022-08-02 16:54 ` [FFmpeg-devel] [PATCH 7/7] tests: add coverage for libavfilter's format negotiation Nicolas George 2022-08-04 13:49 ` [FFmpeg-devel] [PATCH 1/7] lavu/pixfmt: summarize yuv naming conventions Michael Niedermayer 2022-08-04 13:57 ` Nicolas George 2022-08-04 15:04 ` Michael Niedermayer [this message] 2022-08-06 10:36 ` 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=20220804150441.GL2088045@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