From: "Marvin S." <epirat07@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [RFC] Documenting metadata keys, informative (non-copied) metadata Date: Tue, 18 Feb 2025 18:35:43 +0100 Message-ID: <26862864-D6C7-4499-85B5-89956CBDDD41@gmail.com> (raw) In-Reply-To: <c479926cf67f4a338ab063b5bfb9bad9720f5748.camel@haerdin.se> On 18 Feb 2025, at 17:56, Tomas Härdin wrote: > tor 2025-02-13 klockan 12:54 +0100 skrev Tomas Härdin: >> 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. In reference to the AVDictionary patches (it was an attachment so I can not comment inline): IMHO such handling doesn't belong in an abstract container class. It is surprising behaviour that a dictionary cares about how the keys look (beyond the case-sensitive handling). I am not saying this isn't useful but I do not think it belongs in AVDictionary directly. > > Attached is a PoC for the latter part. Unlike the previous samples_md5 > patch, this one only requires updating a FATE ref concerning a .flac > file. > > I have to go, else I'd also post the documentation thing as well. > > /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". _______________________________________________ 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".
next prev parent reply other threads:[~2025-02-18 17:36 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-02-13 11:54 Tomas Härdin 2025-02-18 16:56 ` Tomas Härdin 2025-02-18 17:35 ` Marvin S. [this message] 2025-02-19 12:36 ` Tomas Härdin
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=26862864-D6C7-4499-85B5-89956CBDDD41@gmail.com \ --to=epirat07@gmail.com \ --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