From: "Tomas Härdin" <git@haerdin.se> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 2/3] lavf/srtdec: Permit streaming input Date: Sat, 30 Mar 2024 15:44:02 +0100 Message-ID: <de18e1240f5bc52f3bfeabd4becd5bba160dc840.camel@haerdin.se> (raw) In-Reply-To: <Zgf7HodDxP1g4tCv@phare.normalesup.org> lör 2024-03-30 klockan 12:44 +0100 skrev Nicolas George: > Tomas Härdin (12024-03-30): > > More interesting is fate-sub-srt-badsyntax. Despite the name it > > doesn't > > really have bad syntax, but its cues are in a random order. I guess > > it > > exists to test the cue sorting logic. But should subtitle demuxers > > really sort subtitles in this way? We don't do that for other > > formats > > that can have non-decreasing timestamps. For comparison, the WebVTT > > spec explicitly disallows decreasing timestamps. > > On the other hand, I remember seeing a lot of ASS files from the > fansub > world where titles, signs and karaokes are added at the end after the > dialogues, relying on sorting by the player. Players can implement sorting if they wish. Why should we misrepresent what the file says? These people could also fix their workflows, put karaoke lyrics in a separate stream etc.. Business logic does not belong in lavf, and certainly not deep within demuxers. > (But I guess in the New and Improved FFmpeg, files originating from > the > fansub world are not worth our time, it is enough to be able to > decode > files for Crunchyroll…) Snark doesn't help your case. One potential solution is to do this style of parsing when the input is non-seekable. But then we have the silly situation where streamed and non-streamed behavior differs considerably. Another way could be to move the sorting further up, into demux.c or so, extending the generic index functionality. Finally I will note that sorting does not happen when subtitles are muxed in say mkv or avi, so the behavior is not even consistent across demuxers that support subtitles. With logic further up, and proper discarding, sorting could be done there 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".
next prev parent reply other threads:[~2024-03-30 14:44 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-28 22:55 [FFmpeg-devel] [PATCH 1/3] lavf/subtitles: Do not eat \n\n Tomas Härdin 2024-03-28 22:56 ` [FFmpeg-devel] [PATCH 2/3] lavf/srtdec: Permit streaming input Tomas Härdin 2024-03-28 22:57 ` Tomas Härdin 2024-03-29 23:35 ` Michael Niedermayer 2024-03-30 0:03 ` Tomas Härdin 2024-03-30 8:31 ` Tomas Härdin 2024-03-30 11:36 ` Paul B Mahol 2024-03-30 11:44 ` Nicolas George 2024-03-30 14:44 ` Tomas Härdin [this message] 2024-03-30 14:49 ` Nicolas George 2024-03-30 15:23 ` Tomas Härdin 2024-03-30 15:34 ` Nicolas George 2024-03-30 16:02 ` Andreas Rheinhardt 2024-03-30 16:28 ` Tomas Härdin 2024-04-01 13:15 ` arch1t3cht 2024-04-01 14:34 ` Tomas Härdin 2024-03-28 22:57 ` [FFmpeg-devel] [PATCH 1/3] lavf/subtitles: Do not eat \n\n Tomas Härdin 2024-03-28 23:06 ` [FFmpeg-devel] [PATCH 3/3] lavf/subtitles: Unfix ticket #5032 Tomas Härdin 2024-03-29 12:29 ` Tomas Härdin 2024-03-30 0:08 ` [FFmpeg-devel] [PATCH 1/2] lavf/subtitles: Add ff_text_peek_r16(), only accept \r, \n, \r\n and \r\r\n line endings 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=de18e1240f5bc52f3bfeabd4becd5bba160dc840.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