From: Marth64 <marth64@proxyid.net> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] Captions SCC Date: Sun, 9 Feb 2025 13:37:52 -0600 Message-ID: <CAAhd_PU6xX3qK9t+M1AWVvpeL_=O65WjuvG0_6vKk0aH1ZXFfw@mail.gmail.com> (raw) In-Reply-To: <DM8P223MB03653FC216774C2863D7747EBAF32@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> Partial reply: FFmpeg's CC decoder is actually pretty decent for pop-on CC but produces non-compliant ASS that needs postprocessing. ASS can cover and render the pop-ons quite well, but the fundamental limitation with representing EIA608 with ASS is that ASS does not allow arbitrary positioning AND justification at the same time, without making each line its own cue and carefully positioning the cues or applying some other complex workarounds. The only alternative I can think of within the ASS domain is to use heuristics to determine numpad positioning of the caption cue and declare justification tags without arbitrary positioning, but it needs work and will not be exact. This is a problem for say, I want to render a cue at position x,y but I want it also left justified at that position. I will share details and an example in my slides. I am personally not a fan of WebVTT but irrelevant to the advancements I'm hoping to make. I think baby steps have to come first. Have a good day, _______________________________________________ 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-02-09 19:38 UTC|newest] Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-02-06 10:19 Devlist Archive 2025-02-06 12:57 ` Jack Lau 2025-02-07 5:12 ` Devlist Archive 2025-02-07 7:48 ` Soft Works 2025-02-07 7:58 ` Jack Lau 2025-02-07 8:16 ` Soft Works 2025-02-07 8:26 ` Jack Lau 2025-02-07 9:11 ` Soft Works 2025-02-07 9:44 ` Jack Lau 2025-02-07 15:38 ` Marth64 2025-02-07 16:05 ` Devlist Archive 2025-02-07 16:18 ` Marth64 2025-02-07 16:37 ` Marth64 2025-02-07 16:42 ` Devlist Archive 2025-02-07 18:05 ` Devin Heitmueller 2025-02-07 18:32 ` Devlist Archive 2025-02-07 19:03 ` Devin Heitmueller 2025-02-07 19:31 ` Devlist Archive 2025-02-07 19:44 ` Soft Works 2025-02-07 19:51 ` Devlist Archive 2025-02-07 19:55 ` Devin Heitmueller 2025-02-07 19:56 ` Devin Heitmueller 2025-02-07 19:56 ` Soft Works 2025-02-07 20:20 ` Devlist Archive 2025-02-07 19:52 ` Devin Heitmueller 2025-02-07 19:54 ` Devlist Archive 2025-02-07 17:37 ` Rémi Denis-Courmont 2025-02-07 17:31 ` Rémi Denis-Courmont 2025-02-07 17:47 ` Soft Works 2025-02-07 18:36 ` Tom Vaughan 2025-02-07 18:54 ` Soft Works 2025-02-07 20:09 ` Tom Vaughan 2025-02-07 20:49 ` Devlist Archive 2025-02-07 20:58 ` Soft Works 2025-02-07 21:05 ` Devlist Archive 2025-02-07 21:08 ` Devin Heitmueller 2025-02-07 22:02 ` Marth64 2025-02-07 22:18 ` Marth64 2025-02-07 23:12 ` Devin Heitmueller 2025-02-07 23:46 ` Soft Works 2025-02-07 23:58 ` Marth64 2025-02-08 0:10 ` Soft Works 2025-02-08 14:43 ` Devin Heitmueller 2025-02-09 3:39 ` Tom Vaughan 2025-02-09 14:03 ` Devin Heitmueller 2025-02-09 17:41 ` Devlist Archive 2025-02-09 18:41 ` Tom Vaughan 2025-02-09 18:45 ` Soft Works 2025-02-09 19:37 ` Marth64 [this message] 2025-02-09 20:14 ` Soft Works 2025-02-09 20:23 ` Marth64 2025-02-09 20:33 ` Soft Works 2025-02-10 2:55 ` Devlist Archive
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='CAAhd_PU6xX3qK9t+M1AWVvpeL_=O65WjuvG0_6vKk0aH1ZXFfw@mail.gmail.com' \ --to=marth64@proxyid.net \ --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