From: ACE_code1 via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: =?gb18030?B?ZmZtcGVnLWRldmVs?= <ffmpeg-devel@ffmpeg.org>
Cc: =?gb18030?B?QUNFX2NvZGUx?= <2323180304@qq.com>
Subject: [FFmpeg-devel] [PATCH] avfilter/scale_npp: add runtime command support
Date: Sun, 30 Nov 2025 14:43:23 +0800
Message-ID: <tencent_0357B1A56CE8D8FCB449E3F045B254247806@qq.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="gb18030", Size: 1115 bytes --]
Hi,
this patch makes the CUDA-based scaler scale_npp react to runtime
commands for width and height, so that the output size can be changed
without recreating the filter graph.
In particular:
- mark the "w" and "h" options as AV_OPT_FLAG_RUNTIME_PARAM;
- implement process_command() to re-parse the expression for "w" / "h"
when receiving "width"/"w" or "height"/"h" commands;
- when the new expression is successfully parsed, the filter is
reconfigured on the next frame so the new size takes effect.
If parsing fails, the old expression is kept and an error is logged, so
existing pipelines are not broken.
This enables controlling scale_npp with sendcmd/zmq, for example:
-vf "scale_npp@sn0=w=iw:h=ih,zmq"
echo "scale_npp@sn0" w iw/2 | zmqsend
echo "scale_npp@sn0" h ih/2 | zmqsend
Tested with a simple RTSP output and verified that changing width and
height at runtime updates the output size without interrupting the stream.
Patch generated against current master.
Regards,
Wei Minghui (κÃ÷»Ô)
[-- Attachment #2: 0001-avfilter-scale_npp-support-runtime-width-height-commands.patch --]
[-- Type: application/octet-stream, Size: 5506 bytes --]
[-- Attachment #3: Type: text/plain, Size: 163 bytes --]
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
reply other threads:[~2025-12-04 2:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=tencent_0357B1A56CE8D8FCB449E3F045B254247806@qq.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=2323180304@qq.com \
/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