From: Nicolas George via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: jbvsmo <code@ffmpeg.org>, Nicolas George <george@nsup.org>
Subject: [FFmpeg-devel] Re: [PR] libavfilter: split combined AVClass definitions into per-filter classes (PR #21681)
Date: Mon, 9 Feb 2026 15:11:16 +0100
Message-ID: <aYnrBKFg6hSdCL3o@phare.normalesup.org> (raw)
In-Reply-To: <177051964091.25.10944908971436056935@4457048688e7>
jbvsmo via ffmpeg-devel (HE12026-02-08):
> Several filters that share the same options array also shared a single
> AVClass with a combined class_name like "(h|v)stack",
> "(a)split", "kirsch/prewitt/roberts/scharr/sobel", etc. While
> compact, this causes ffmpeg -help full and the AVOptions API to
> report a single merged entry for multiple distinct filters, making the
> output unsuitable for machine parsing.
>
> This patch gives each filter its own AVFILTER_DEFINE_CLASS_EXT with
> its actual filter name, while continuing to share the same underlying
> options array. The generated class symbols remain static, so there
> is no ABI or API change for downstream users.
I am rather against this. I remember efforts were made deliberately to
remove the duplication of the options array.
If your issue is to make the output convenient for parsers, then I
suggest you add an option “ffmpeg -help full-script" that does exactly
that.
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:[~2026-02-09 14:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-08 3:00 [FFmpeg-devel] " jbvsmo via ffmpeg-devel
2026-02-09 14:11 ` 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=aYnrBKFg6hSdCL3o@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