From: Jorge Estrada <jestrada.list-at-gmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avfilter: add pad_npp filter
Date: Sun, 15 Jun 2025 18:38:12 -0700
Message-ID: <CAHPA9KTX78K1MCYMd7N9PJ2w+JDxj5N-ceRnc00YEb82TmXsnw@mail.gmail.com> (raw)
In-Reply-To: <17955819-8c3b-458b-a531-249dd2621fba@rothenpieler.org>
Got it. I don't mind writing a CUDA variant of this and submitting it
separately. What's the reasoning behind preferring a plain CUDA filter over
an NPP based one?
On Sun, Jun 15, 2025 at 5:37 PM Timo Rothenpieler <timo@rothenpieler.org>
wrote:
> On 16.06.2025 02:14, Jorge Estrada wrote:
> > This patch adds the pad_npp video filter. A filter similar to the
> existing pad filter but accelerated by NPP.
>
> I'm honestly not keen on adding another npp based filter, specially one
> this simple that a plain CUDA filter could easily do as well.
>
> My goal in the long term would be to make all npp based filters obsolete
> and then deprecate them.
> _______________________________________________
> 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:[~2025-06-16 1:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 0:14 Jorge Estrada
2025-06-16 0:37 ` Timo Rothenpieler
2025-06-16 1:38 ` Jorge Estrada [this message]
2025-06-16 11:08 ` Timo Rothenpieler
2025-06-16 15:13 ` Jorge Estrada
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=CAHPA9KTX78K1MCYMd7N9PJ2w+JDxj5N-ceRnc00YEb82TmXsnw@mail.gmail.com \
--to=jestrada.list-at-gmail.com@ffmpeg.org \
--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