From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 2/2] avformat/id3v2: Check that decode_str() did advance Date: Wed, 16 Apr 2025 01:29:02 +0000 Message-ID: <DM8P223MB0365836071D915E428907879BABD2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw) In-Reply-To: <20250416012145.GE4991@pb2> > -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of > Michael Niedermayer > Sent: Mittwoch, 16. April 2025 03:22 > To: FFmpeg development discussions and patches <ffmpeg- > devel@ffmpeg.org> > Subject: Re: [FFmpeg-devel] [PATCH 2/2] avformat/id3v2: Check that > decode_str() did advance > > On Tue, Apr 15, 2025 at 10:59:07PM +0000, softworkz . wrote: > > > > > > > -----Original Message----- > > > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of > > > Michael Niedermayer > > > Sent: Mittwoch, 16. April 2025 00:50 > > > To: FFmpeg development discussions and patches <ffmpeg- > > > devel@ffmpeg.org> > > > Subject: Re: [FFmpeg-devel] [PATCH 2/2] avformat/id3v2: Check that > > > decode_str() did advance > > > > > > On Tue, Apr 15, 2025 at 07:59:00PM +0000, softworkz . wrote: > > > [...] > > > > > > > - The representation of multi-values - both, internally and when > > > > outputting as probe data - is a de-facto standard > > > > > > The external handling in formats is specified in the corresponing > > > specifications. ";" is certainly not correct for formats which > > > natively support multiple values per key. > > > > > > Internally, if you have a data structure that represents multiple > > > authors, you certainly do not set it to one author and a string > > > with a bunch of semicolons seperating multiple authors > > > > > > Title: "Smile ;)" > > > Author "Smily Face ;)" > > > > > > is not 2 Titles and not 2 Authors and software that cannot handle > that > > > should not be used as reference IMHO > > > > > > That said, anything that works is fine with me, > > > > > > But internally it will be better to use a representation that is > > > universal, generic and simple, ";" may seem to be that but only > > > as long as you do nothing with it and dont care about corner cases > > > > > > Ill leave this ";" question to everyone else, i have a backlog > > > of quite a few things i need to work on > > > > This is not a great outcome, because "leaving everyone else" means > > nothing will happen. > > I have a release to do, I have contracts that i should be working on, > as iam a few month behind some deadline, I have a backlog of fuzzer > issues i wanted to look at. I have a backlog of other things > > And this ";" thing is close to the last thing i want to spend my time > on ;) It's fine. You don't have to. I'm also not insisting on my patch. > > At least revert the rcombs patch until there's a conclusion, because > > it really makes things worse than better with regards to FFprobe > > output. > > I guess thats reasonable. Perfect, thanks. > > This will cause deserialization errors for many people in the world > > who are processing FFprobe data. > > As said, ffprobe should not produce troublesome output As I said, it cannot be remedied on the FFprobe side without making a breaking change to its output format, that's what turns this small thing into a big one. Thank you sw _______________________________________________ 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-16 1:29 UTC|newest] Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-04-11 22:27 [FFmpeg-devel] [PATCH 1/2] avformat/id3v2: Print the unknown encoding Michael Niedermayer 2025-04-11 22:27 ` [FFmpeg-devel] [PATCH 2/2] avformat/id3v2: Check that decode_str() did advance Michael Niedermayer 2025-04-12 1:49 ` softworkz . 2025-04-14 23:19 ` Michael Niedermayer 2025-04-14 23:59 ` softworkz . 2025-04-15 0:02 ` Ridley Combs via ffmpeg-devel 2025-04-15 0:17 ` softworkz . 2025-04-15 18:32 ` Michael Niedermayer 2025-04-15 19:03 ` Nicolas George 2025-04-15 20:12 ` softworkz . 2025-04-15 20:47 ` Nicolas George 2025-04-15 22:20 ` softworkz . 2025-04-16 5:15 ` Nicolas George 2025-04-16 5:59 ` softworkz . 2025-04-16 7:02 ` Nicolas George 2025-04-15 19:15 ` softworkz . 2025-04-15 19:02 ` Nicolas George 2025-04-16 8:02 ` Andreas Rheinhardt 2025-04-15 18:55 ` Michael Niedermayer 2025-04-15 19:59 ` softworkz . 2025-04-15 22:50 ` Michael Niedermayer 2025-04-15 22:59 ` softworkz . 2025-04-15 23:01 ` softworkz . 2025-04-16 0:53 ` Michael Niedermayer 2025-04-16 1:01 ` softworkz . 2025-04-16 2:39 ` softworkz . 2025-04-16 7:04 ` Nicolas George 2025-04-16 11:07 ` Michael Niedermayer 2025-04-16 11:15 ` softworkz . 2025-04-16 1:21 ` Michael Niedermayer 2025-04-16 1:29 ` softworkz . [this message] 2025-04-16 1:33 ` Michael Niedermayer 2025-04-16 2:18 ` softworkz . 2025-04-16 2:31 ` softworkz . 2025-04-16 10:41 ` Michael Niedermayer 2025-04-16 10:59 ` softworkz . 2025-04-16 2:52 ` softworkz . 2025-04-16 10:53 ` Michael Niedermayer 2025-04-16 10:57 ` Andreas Rheinhardt 2025-04-16 11:02 ` Michael Niedermayer 2025-04-16 10:58 ` softworkz . 2025-04-15 1:37 ` softworkz . 2025-04-15 18:25 ` Michael Niedermayer 2025-04-15 19:07 ` softworkz .
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=DM8P223MB0365836071D915E428907879BABD2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \ --to=softworkz-at-hotmail.com@ffmpeg.org \ --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