From: Ramiro Polla <ramiro.polla@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/4] swscale/yuv2rgb: prepare YUV2RGBFUNC macro for multi-planar rgb
Date: Tue, 6 Aug 2024 12:54:38 +0200
Message-ID: <CALweWgC8s12V1F7sMVK_RnVAzmsUZgvxO9+SubZFXWGAAXpaAw@mail.gmail.com> (raw)
In-Reply-To: <20240731111444.GS4991@pb2>
On Wed, Jul 31, 2024 at 1:14 PM Michael Niedermayer
<michael@niedermayer.cc> wrote:
> On Tue, Jul 30, 2024 at 03:05:22PM +0200, Ramiro Polla wrote:
> > On Tue, Jul 23, 2024 at 2:46 PM Ramiro Polla <ramiro.polla@gmail.com> wrote:
> > > This will be used in the upcoming yuv42{0,2}p -> gbrp unscaled
> > > colorspace converters.
> >
> > ping on this patchset.
>
> Maybe you can add benchmarks to things changing performance
> and, also put a note in commit messages for changes which
> change the output
For the commit that adds the c unscaled converter, what metric would
be important in the commit log? I would guess performance and ssim
difference from the current behaviour that goes through the swscaler,
but it doesn't seem like we have a tool to do that easily.
_______________________________________________
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".
prev parent reply other threads:[~2024-08-06 10:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 12:46 Ramiro Polla
2024-07-23 12:46 ` [FFmpeg-devel] [PATCH 2/4] swscale/yuv2rgb: add yuv42{0, 2}p -> gbrp unscaled colorspace converters Ramiro Polla
2024-07-23 12:46 ` [FFmpeg-devel] [PATCH 3/4] swscale/x86/yuv2rgb: add ssse3 " Ramiro Polla
2024-07-23 12:46 ` [FFmpeg-devel] [PATCH 4/4] swscale/aarch64/yuv2rgb: add neon " Ramiro Polla
2024-07-30 13:05 ` [FFmpeg-devel] [PATCH 1/4] swscale/yuv2rgb: prepare YUV2RGBFUNC macro for multi-planar rgb Ramiro Polla
2024-07-31 11:14 ` Michael Niedermayer
2024-08-06 10:54 ` Ramiro Polla [this message]
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=CALweWgC8s12V1F7sMVK_RnVAzmsUZgvxO9+SubZFXWGAAXpaAw@mail.gmail.com \
--to=ramiro.polla@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