From: "Tomas Härdin" <git@haerdin.se>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] [RFC] Documenting metadata keys, informative (non-copied) metadata
Date: Thu, 13 Feb 2025 12:54:04 +0100
Message-ID: <d56ba84a09726a02ede69e1fa2b8873f9d064440.camel@haerdin.se> (raw)
Hi
In the samples_md5 patch discussion Michael wanted the proposed key to
be documented. But it turns out we don't have any documentation for
metadata keys! So I'm starting this thread to talk about it. I reckon
we create a new file called doc/metadata_keys.texi with a table listing
keys and where they can appear (format, stream, frames), sorted by
name, with a brief description of each one. Any keys that require more
detailed documentation we could add sections for.
Another issue raised was that some metadata keys shouldn't be carried
over automatically to muxers. In the samples_md5 thread it was pointed
out by Andreas that we don't want to mux that in AIFF. It was also
pointed out that it stops being valid if the audio is cut. This isn't
the first time I've come across cases where we don't want metadata to
be copied, so I'm taking the opportunity to propose informative output-
only metadata could reside in their own namespace. I propose info: for
that, so info:samples_md5 in this specific case, or maybe just
info:md5. HEVC frames could similarly have such metadata applied.
/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".
reply other threads:[~2025-02-13 11:54 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=d56ba84a09726a02ede69e1fa2b8873f9d064440.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