From: Nicolas George <george@nsup.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avfilter: add alphamerge_cuda filter
Date: Thu, 7 Aug 2025 12:15:44 +0200
Message-ID: <aJR80HPsl0vkHBbW@phare.normalesup.org> (raw)
In-Reply-To: <20250807025358.49096-1-jestrada.list@gmail.com>
Jorge Estrada (HE12025-08-06):
> This patch adds the alphamerge_cuda video filter
Thanks, but sorry, no: this is wrong, although not by your fault.
Your filter supports only planar formats. Changing a whole plane in a
planar format should involve a little reference counting gymnastics and
updating a pointer, no data copy.
See <https://code.ffmpeg.org/FFmpeg/FFmpeg/issues/20153>:
# `vf_alphamerge` was added in July 2012 (82ecae8a70), it used memcpy() to
# replace the alpha plane of the frame, that was later (d6b9f2b7da)
# updated to use av_image_copy_plane().
#
# But in March 2013 (c4e8821732), we gained the ability to share plane
# data between multiple frames, thanks to refcounted buffers.
# `vf_alphamerge` could have used that ability, but it was never done,
# probably because `vf_alphamerge` came from the FFmpeg side while the
# refcounting came from the libav side.
#
# `vf_alphamerge` needs to be updated to only create a new reference to
# the alpha plane of the input frame and use it in the output frame. No
# data copy involved at all.
The same probably applies to vf_extractplanes.c, although the excuse of
having been added before refcounting is not valid for this one.
These are rather low-hanging fruits.
Regards,
--
Nicolas George
_______________________________________________
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-08-07 10:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 2:53 Jorge Estrada
2025-08-07 10:15 ` Nicolas George [this message]
2025-08-07 19:14 ` 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=aJR80HPsl0vkHBbW@phare.normalesup.org \
--to=george@nsup.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