From: Niklas Haas <ffmpeg@haasn.xyz> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v2 1/8] swscale: document SWS_FULL_CHR_H_* flags Date: Thu, 4 Jul 2024 19:59:10 +0200 Message-ID: <20240704195910.GG4933@haasn.xyz> (raw) In-Reply-To: <20240704195656.GC4933@haasn.xyz> On Thu, 04 Jul 2024 19:56:56 +0200 Niklas Haas <ffmpeg@haasn.xyz> wrote: > On Thu, 04 Jul 2024 16:24:24 +0100 Andrew Sayers <ffmpeg-devel@pileofstuff.org> wrote: > > On Thu, Jul 04, 2024 at 04:30:57PM +0200, Niklas Haas wrote: > > > From: Niklas Haas <git@haasn.dev> > > > > > > Based on my best understanding of what they do, given the source code. > > > --- > > > libswscale/swscale.h | 28 ++++++++++++++++++++++++++-- > > > 1 file changed, 26 insertions(+), 2 deletions(-) > > > > > > diff --git a/libswscale/swscale.h b/libswscale/swscale.h > > > index 9d4612aaf3..e22931cab4 100644 > > > --- a/libswscale/swscale.h > > > +++ b/libswscale/swscale.h > > > @@ -82,11 +82,35 @@ const char *swscale_license(void); > > > #define SWS_PRINT_INFO 0x1000 > > > > > > //the following 3 flags are not completely implemented > > > -//internal chrominance subsampling info > > > + > > > +/** > > > + * Perform full chroma upsampling when converting to RGB as part of scaling. > > > > Nitpick: "as part of scaling" seems redundant - can it be removed? > > I wrote it this way because, afaict, this flag does not affect unscaled > special converters (yuv->rgba). But I can remove it if you still think > it's unnecessary. How about: "Perform full chroma upsampling when upscaling to RGB"? > > > > > > + * > > > + * For example, when converting 50x50 yuv420p to 100x100 rgba, setting this flag > > > + * will scale the chroma plane from 25x25 to 100x100 (4:4:4), and then convert > > > + * the 100x100 yuv444p image to rgba in the final output step. > > > + * > > > + * Without this flag, the chroma plane is instead scaled to 50x100 (4:2:2), > > > + * with a single chroma sample being re-used for both horizontally adjacent RGBA > > > + * output pixels. > > > > Nitpick: this would be more readable as "for both of the...". > > > > Consider the following sentence: > > > > Without this flag, the chroma plane is instead scaled to 50x100 (4:2:2), > > with a single chroma sample being re-used for both horizontally and vertically > > adjacent RGBA output pixels. > > > > Using "both of the" would make it clear what "both" refers to before the reader > > starts doing branch-prediction in their head. > > Fixed. > > > > > Otherwise, LGTM (by which I mean it's clear, not that I know whether it's > > correct). > > _______________________________________________ > > 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". _______________________________________________ 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:[~2024-07-04 17:59 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-07-04 14:30 Niklas Haas 2024-07-04 14:30 ` [FFmpeg-devel] [PATCH v2 2/8] avfilter/vf_setparams: allow setting chroma location Niklas Haas 2024-07-04 14:30 ` [FFmpeg-devel] [PATCH v2 3/8] swscale/options: relax src/dst_h/v_chr_pos value range Niklas Haas 2024-07-07 18:56 ` Michael Niedermayer 2024-07-04 14:31 ` [FFmpeg-devel] [PATCH v2 4/8] avfilter/swscale: always fix interlaced chroma location Niklas Haas 2024-07-04 14:31 ` [FFmpeg-devel] [PATCH v2 5/8] avfilter/vf_scale: add in/out_chroma_loc Niklas Haas 2024-07-04 14:31 ` [FFmpeg-devel] [PATCH v2 6/8] avfilter/vf_scale: fix 4:1:0 interlaced chroma pos Niklas Haas 2024-07-04 14:31 ` [FFmpeg-devel] [PATCH v2 7/8] avfilter/vf_zscale: remove unused fields Niklas Haas 2024-07-04 14:31 ` [FFmpeg-devel] [PATCH v2 8/8] fate/scalechroma: switch to standard chroma location Niklas Haas 2024-07-04 14:33 ` [FFmpeg-devel] [PATCH v2 1/8] swscale: document SWS_FULL_CHR_H_* flags Niklas Haas 2024-07-04 15:24 ` Andrew Sayers 2024-07-04 17:56 ` Niklas Haas 2024-07-04 17:59 ` Niklas Haas [this message] 2024-07-04 18:14 ` Andrew Sayers
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=20240704195910.GG4933@haasn.xyz \ --to=ffmpeg@haasn.xyz \ --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