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 17:28:52 +0100 Message-ID: <6979f258ee706bf6938657402053b25d65d8404d.camel@haerdin.se> (raw) In-Reply-To: <GV1P250MB0737BC01860AAA755ADDA8DE8F392@GV1P250MB0737.EURP250.PROD.OUTLOOK.COM> lör 2024-03-30 klockan 17:02 +0100 skrev Andreas Rheinhardt: > > > ASS demuxer sorts its packets because > > > there is no guarantee the text are sorted in the file > > > > So? I'm making a normative argument. > > > > Normative about what? The ASS specification [1] explicitly says: > > "SSA does not care what order events are entered in. > > They could be entered in complete reverse order, and SSA would > still play everything correctly in the right order ie. you cannot > assume > that each dialogue line is in chronological order in the script > file." This describes what SSA does, not what lavf should do. lavf does not guarantee ordered subtitles in general, as far as I can tell. > If you force reordering on our users, then this is a breaking change Hence why we shouldn't put business logic in lavf. It would have been better to put it in ffmpeg.c. Not putting business logic in lavf is a point I've been making for years. Here we see an excellent reason why. We can maintain the current behavior by putting the sorting logic further up in lavf, assuming API users care. If API users don't care but CLI users do then we could put it in ffmpeg.c. If we are to maintain compatibility with an ill-defined set of API users rather than say specific packages (vlc, mpv, melt etc) then the only sensible solution is to put the sorting logic further up in lavf, say demux.c. /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 16:29 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 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 [this message] 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=6979f258ee706bf6938657402053b25d65d8404d.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