From: "Daniel Cantarín" <canta@canta.com.ar> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] Politics Date: Sat, 18 Dec 2021 14:59:11 -0300 Message-ID: <cb2a57ad-55df-4209-ebb5-ece8ab946159@canta.com.ar> (raw) In-Reply-To: <DM8P223MB036565FBE4AF324B3CE43CC6BA799@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> >> as well as ATSC subtitles > > There are like 2 or 3 characters in each frame. Sometimes > they are shown as they are coming in, sometimes only > when a line is completed, sometimes needs to wait > for subsequent frames before emitting new characters. > This is really not a high-precision thing. Can confirm. I did implemented this using video filters, precisely because we don't have subtitle filters and I was forced to do OCR. It works OK, but it's unrealiable when speaking about timings. You have 2 bytes/chars per frame, non-ascii chars use 2 bytes, and there are also commands that also use one or two bytes. This leaves you with a max speed of 60 chars per second for a 30 FPS video stream: a condition no other subtitle/caption format that I know of share. When there's fast dialogue, it desyncs. It later re-syncs: it doesn't drift away. But dialogue faster than 60 chars (including non-ascii and command) per second does affect the captions timings. But there's more. Implementations in players are chaotic, and some commands are ignored or works erratically. Also, there are line width issues: 30 chars max by the standard, even when some players change that. But you have to deal with word wrapping by doing text treatment and applying commands. Then there's 4 modes of rendering, as you say, which you are supposed to control but then players do what they want, and given that this are bytes added to the video frames you gotta encode two different video streams if you want to have two different caption configurations. It may be the most available format in the world. But it's also a PITA because a lot of details, and that's why I'm so interested in finally having subtitles in filters first, and dealing with the internal details later. _______________________________________________ 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:[~2021-12-18 17:59 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <8dbfd345-c661-459e-b242-94830107eae3@www.fastmail.com> [not found] ` <DM8P223MB0365510C72E8CFEF027FF97FBA749@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> [not found] ` <MqpKkF_--7-2@lynne.ee> [not found] ` <DM8P223MB0365FEDCCEFB370D20979CF5BA749@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> [not found] ` <c2f7048d-a1b6-253e-8a50-7fdf9a34ada3@canta.com.ar> [not found] ` <DM8P223MB036596CACBB6509CB1AE78CBBA759@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> [not found] ` <CAPYw7P64=axtAC0-8Ux+1d+f8WEseuWk9OkhmbAnNWp-eRpq8A@mail.gmail.com> 2021-12-15 13:34 ` Soft Works 2021-12-18 10:26 ` Paul B Mahol 2021-12-18 11:34 ` Soft Works 2021-12-18 13:32 ` Lynne 2021-12-18 14:28 ` Soft Works 2021-12-18 15:16 ` Lynne 2021-12-18 15:43 ` Soft Works 2021-12-18 17:53 ` Lynne 2021-12-18 18:16 ` Daniel Cantarín 2021-12-18 18:30 ` Hendrik Leppkes 2021-12-18 18:49 ` Soft Works 2021-12-18 20:05 ` Daniel Cantarín 2021-12-18 20:41 ` Soft Works 2021-12-19 15:16 ` Michael Niedermayer 2021-12-19 18:23 ` Soft Works 2021-12-19 18:31 ` Soft Works 2021-12-20 14:49 ` Michael Niedermayer 2021-12-20 22:35 ` Soft Works 2021-12-20 23:20 ` Soft Works 2021-12-21 18:38 ` Michael Niedermayer 2021-12-22 10:23 ` Soft Works 2021-12-18 17:59 ` Daniel Cantarín [this message] 2021-12-18 15:41 ` Daniel Cantarín 2021-12-20 13:48 Daniel Cantarín 2021-12-20 14:06 Daniel Cantarín 2021-12-20 15:23 ` Michael Niedermayer 2021-12-22 13:29 ` Soft Works 2021-12-22 19:54 ` Michael Niedermayer 2021-12-22 20:17 ` Soft Works 2021-12-20 16:27 Daniel Cantarín
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=cb2a57ad-55df-4209-ebb5-ece8ab946159@canta.com.ar \ --to=canta@canta.com.ar \ --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