From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ffbox0-bg.mplayerhq.hu (ffbox0-bg.ffmpeg.org [79.124.17.100]) by master.gitmailbox.com (Postfix) with ESMTPS id 5F13B4CEDC for ; Thu, 13 Feb 2025 11:54:15 +0000 (UTC) Received: from [127.0.1.1] (localhost [127.0.0.1]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTP id D587868BECE; Thu, 13 Feb 2025 13:54:12 +0200 (EET) Received: from glom.nmugroup.com (glom.nmugroup.com [193.183.80.6]) by ffbox0-bg.mplayerhq.hu (Postfix) with ESMTPS id E58F368B864 for ; Thu, 13 Feb 2025 13:54:05 +0200 (EET) Received: from localhost (localhost [127.0.0.1]) by glom.nmugroup.com (Postfix) with ESMTP id 86821542B1E3 for ; Thu, 13 Feb 2025 12:54:05 +0100 (CET) Received: from debian.lan (unknown [IPv6:2a00:66c0:a::72c]) (Authenticated sender: git01) by glom.nmugroup.com (Postfix) with ESMTPSA id 59ECC542B08C for ; Thu, 13 Feb 2025 12:54:05 +0100 (CET) Message-ID: From: Tomas =?ISO-8859-1?Q?H=E4rdin?= To: FFmpeg development discussions and patches Date: Thu, 13 Feb 2025 12:54:04 +0100 User-Agent: Evolution 3.46.4-2 MIME-Version: 1.0 Subject: [FFmpeg-devel] [RFC] Documenting metadata keys, informative (non-copied) metadata X-BeenThere: ffmpeg-devel@ffmpeg.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: FFmpeg development discussions and patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: FFmpeg development discussions and patches Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ffmpeg-devel-bounces@ffmpeg.org Sender: "ffmpeg-devel" Archived-At: List-Archive: List-Post: 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".