From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avfilter/overlay_cuda: add timeline editing support
Date: Wed, 9 Jul 2025 14:09:44 +0200
Message-ID: <65710263-e58b-4681-b92b-7a7645c173b6@rothenpieler.org> (raw)
In-Reply-To: <20250707225303.68084-1-jestrada.list@gmail.com>
On 08/07/2025 00:53, Jorge Estrada wrote:
> Enables timeline editing options for overlay_cuda similar to what overlay allows
>
> Example overlaying an image on a video between 30 to 60 seconds:
>
> ffmpeg -hwaccel cuda -hwaccel_output_format cuda -i sample-video.mp4 -i sample-image.jpg
> -filter_complex "[1:v]hwupload_cuda[image],[0:v]scale_npp=format=yuv420p[video],[video][image]overlay_cuda=enable='between(t,30,60)'"
> -c:v h264_nvenc -c:a copy -y overlay-output-gpu.mp4
>
> Signed-off-by: Jorge Estrada <jestrada.list@gmail.com>
> ---
> libavfilter/vf_overlay_cuda.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/libavfilter/vf_overlay_cuda.c b/libavfilter/vf_overlay_cuda.c
> index 4708b34d30..3d39458f3f 100644
> --- a/libavfilter/vf_overlay_cuda.c
> +++ b/libavfilter/vf_overlay_cuda.c
> @@ -573,5 +573,6 @@ const FFFilter ff_vf_overlay_cuda = {
> FILTER_OUTPUTS(overlay_cuda_outputs),
> FILTER_SINGLE_PIXFMT(AV_PIX_FMT_CUDA),
> .preinit = overlay_cuda_framesync_preinit,
> + .p.flags = AVFILTER_FLAG_SUPPORT_TIMELINE_INTERNAL,
> .flags_internal = FF_FILTER_FLAG_HWFRAME_AWARE,
> };
looks reasonable to me, will apply
_______________________________________________
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:[~2025-07-09 12:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-07 22:53 Jorge Estrada
2025-07-09 12:09 ` Timo Rothenpieler [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=65710263-e58b-4681-b92b-7a7645c173b6@rothenpieler.org \
--to=timo@rothenpieler.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