From: Nicolas George via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Nicolas George <george@nsup.org>
Subject: [FFmpeg-devel] Re: [PATCH] avfilter: enhance command processing with chain propagation and direction control. (PR #20731)
Date: Fri, 31 Oct 2025 10:58:34 +0100
Message-ID: <aQSISkHAAUOImc1s@phare.normalesup.org> (raw)
In-Reply-To: <tencent_EF90BF26CDA7FDEA80D313DC504BA0A61806@qq.com>
Zhao Zhili via ffmpeg-devel (HE12025-10-31):
> Current implementation isn’t a new API, but new flags. It extends the ways to
> traverse a graph.
A new flag is a new API.
> The existing API has the capability to send commands to a specific filter, a certain
> type of filter, or all filters, but it lacks the ability to send commands to a subgraph,
> unless the user manually filters out all filters belonging to the subgraph, which is
> possible but complex.
>
> The newly added flags provide subgraph traversal capability.
>
> A common use case is when a graph contains multiple sources; I want to send
> commands, such as volume control, to a subgraph with a specific source as the
> root node, without affecting other sources. While controlling via volume instance
> names is also feasible, using the source for control offers additional flexibility.
Then we need a patch series that really allows to do that, including
examples.
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-31 9:59 UTC|newest]
Thread overview: 4+ 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 ` [FFmpeg-devel] " Nicolas George via ffmpeg-devel
2025-10-31 9:14 ` Zhao Zhili via ffmpeg-devel
2025-10-31 9:58 ` 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=aQSISkHAAUOImc1s@phare.normalesup.org \
--to=ffmpeg-devel@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