From: "Tomas Härdin" <git@haerdin.se>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] doc/metadata.texi: Start documenting keys
Date: Wed, 05 Mar 2025 09:59:59 +0100
Message-ID: <86911cb59e1ec7d5d9225b436aef78d155a4b576.camel@haerdin.se> (raw)
In-Reply-To: <AS8P250MB0744A3DD69129EAFF4282F9A8FC82@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM>
tis 2025-03-04 klockan 12:36 +0100 skrev Andreas Rheinhardt:
> Tomas Härdin:
> > +@item ref-frame-config @tab @tab @tab
> > +@item reverb @tab S @tab argo_cvg @tab
>
> The first is libvp9enc-only, the second argo_cvg only. IMO it is
> better
> to document this at the documentation of the relevant encoder and
> demuxer.
For format-specific metadata maybe. But for metadata supported by
multiple formats, where the user can expect to be able to convert from
one format to the other while keeping the metadata, we'll want a single
place where this is documented, or else users have less chance of
seeing this feature. And then you have a central anyway so you might as
well put all the keys in it rather than having them spread out all over
the docs.
Maybe we could *also* put the keys in the docs for the relevant
formats, filters etc. But then there's a a higher risk of that getting
out of sync with the table.
/Tomas
_______________________________________________
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-03-05 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 15:42 Tomas Härdin
2025-03-04 11:28 ` Tomas Härdin
2025-03-04 11:36 ` Andreas Rheinhardt
2025-03-04 16:18 ` Marvin Scholz
2025-03-05 8:59 ` Tomas Härdin [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=86911cb59e1ec7d5d9225b436aef78d155a4b576.camel@haerdin.se \
--to=git@haerdin.se \
--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