From: Nicolas George via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: cenzhanquan1 <code@ffmpeg.org>, Nicolas George <george@nsup.org>
Subject: [FFmpeg-devel] Re: [PATCH] avfilter: enhance command processing with chain propagation and direction control. (PR #20731)
Date: Thu, 30 Oct 2025 20:12:14 +0100
Message-ID: <aQO4jjvc5JlNvilp@phare.normalesup.org> (raw)
In-Reply-To: <176103962100.62.8039215404646309233@bf907ddaa564>
cenzhanquan1 via ffmpeg-devel (HE12025-10-21):
> PR #20731 opened by cenzhanquan1
> URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20731
> Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20731.patch
> 
> The existing avfilter_process_command and avfilter_graph_send_command havelimitations in
> command propagation: they only handle commands for individualfilters and lack the ability
> to propagate commands through the entire filterchain, nor do they support directional
> traversal of the filter graph. Thismakes it difficult to control multiple filters in a chain
> (e.g., adjustingvolume for all related filters or enabling/disabling a series of filters)with
> a single command.
You are proposing to add an API without adding any code that uses that
API, let alone user-oriented examples. That makes it impossible to guess
if the feature is useful or if there are better ways to achieve what you
want it to do.
Regards,
-- 
  Nicolas George
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
     prev parent reply	other threads:[~2025-10-30 19:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-21  9:40 [FFmpeg-devel] " cenzhanquan1 via ffmpeg-devel
2025-10-30 19:12 ` Nicolas George via ffmpeg-devel [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=aQO4jjvc5JlNvilp@phare.normalesup.org \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=code@ffmpeg.org \
    --cc=george@nsup.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