From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [RFC] AVDictionary2 Date: Wed, 9 Apr 2025 00:35:21 +0200 Message-ID: <20250408223521.GU4991@pb2> (raw) In-Reply-To: <3503432.tdWV9SEqCh@falbala> [-- Attachment #1.1: Type: text/plain, Size: 2054 bytes --] Hi On Wed, Apr 09, 2025 at 12:18:10AM +0200, Gerion Entrup wrote: > Am Dienstag, 8. April 2025, 22:29:37 Mitteleuropäische Sommerzeit schrieb Michael Niedermayer: > > On Tue, Apr 08, 2025 at 11:10:21AM -0500, Romain Beauxis wrote: > > > Le mar. 8 avr. 2025 à 05:20, Michael Niedermayer > > > <michael@niedermayer.cc> a écrit : > >> [...] > > > * Any interest in storing multiple values for the same key? This seems > > > like a niche case but, as you pointed out in another thread, typically > > > vorbis metadata do allow multiple key/values for the same field. > > > > For a single key multiple values should not be stored > > You can do > > Author1=Eve > > Author2=Adam > > or > > Author=Adam and Eve > > > > But dont do > > Author=Eve > > Author=Adam > > because if you do that and then you get later a > > Author=Lilith > > what does that mean? that its now 1 Author or 3 Authors > > or 2 and if 2 then which 2 ? > > > > Or said another way, you cant have multiple identical keys like that AND > > allow updates. > > AFAIK, Matroska also has Metadata that are explicitly a tree and can have the same key. > A good example is the ACTOR tag: Most movies have more than one actor, the CHARACTER should be a subtag of ACTOR [1]. The AVDictionary2 API doesnt need to represent multiple actors the same way as the matroska bitstream. Also it changes nothing on the conflict between "multiple identical keys" and updates > Currently, FFmpeg just seem to ignore keys with multiple values and display the first. Since 80b77e8e8d0630710ad6069133f397459015f139, we have some support for multiple values in id3, this has the problem with updates described above though thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB If the United States is serious about tackling the national security threats related to an insecure 5G network, it needs to rethink the extent to which it values corporate profits and government espionage over security.-Bruce Schneier [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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-04-08 22:35 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-04-08 10:19 Michael Niedermayer 2025-04-08 16:10 ` Romain Beauxis 2025-04-08 20:29 ` Michael Niedermayer 2025-04-08 22:18 ` Gerion Entrup 2025-04-08 22:35 ` Michael Niedermayer [this message] 2025-04-08 22:37 ` softworkz . 2025-04-08 16:56 ` softworkz . 2025-04-08 18:16 ` Michael Niedermayer 2025-04-08 18:36 ` softworkz . 2025-04-08 19:45 ` Michael Niedermayer 2025-04-08 21:30 ` softworkz . 2025-04-11 19:06 ` Michael Niedermayer 2025-04-12 1:41 ` softworkz . 2025-04-12 11:02 ` softworkz . 2025-04-09 0:00 ` Leo Izen 2025-04-09 16:56 ` Michael Niedermayer 2025-04-10 8:40 ` Nicolas George 2025-04-10 18:31 ` softworkz . 2025-04-11 20:50 ` Michael Niedermayer
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=20250408223521.GU4991@pb2 \ --to=michael@niedermayer.cc \ --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