From: Soft Works <softworkz-at-hotmail.com@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] Captions SCC Date: Fri, 7 Feb 2025 18:54:46 +0000 Message-ID: <DM8P223MB03659B80A3CA1AD7AF706070BAF12@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw) In-Reply-To: <0A2EA9D5-B1A3-4381-A4AF-D5C2E633B3C2@tvaughan.com> > -----Original Message----- > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Tom > Vaughan > Sent: Friday, February 7, 2025 7:36 PM > To: FFmpeg development discussions and patches <ffmpeg- > devel@ffmpeg.org> > Subject: Re: [FFmpeg-devel] Captions SCC > > Soft Works said... "the CC data needs to get into the video frames - > so that it exists as input to the video encoder. > For the same reason, it is also not possible to add CCs at the muxer > level. It always requires video encoding because the data needs to > get into the video stream itself, so there's no way to get data from > an SCC file into a video stream currently." Hi Tom, > You're confusing subtitles with closed captions. No. > Subtitles are text that is composited into the video. No. > CEA-708 closed captions are > carried as metadata in SEI NAL units, muxed into the elementary video > stream. I wouldn't call this "muxing" but that's not worth a debate. (you might want to spend a thought on why it's called "elementary stream") I said "it is also not possible to add CCs at the muxer level". By that I mean "muxing" in ffmpeg terminology which is unambiguous. sw > > On 2/6/25, 11:48 PM, "ffmpeg-devel on behalf of Soft Works" <ffmpeg- > devel-bounces@ffmpeg.org <mailto:ffmpeg-devel-bounces@ffmpeg.org> on > behalf of softworkz-at-hotmail.com@ffmpeg.org <mailto:softworkz-at- > hotmail.com@ffmpeg.org>> wrote: > > > > -----Original Message----- > > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org <mailto:ffmpeg- > devel-bounces@ffmpeg.org>> On Behalf Of > > Devlist Archive > > Sent: Friday, February 7, 2025 6:13 AM > > To: FFmpeg development discussions and patches <ffmpeg- > > devel@ffmpeg.org <mailto:devel@ffmpeg.org>> > > Subject: Re: [FFmpeg-devel] Captions SCC > > > Hi Zack, > that message from "Jack" had confused me for a moment, but on re- > reading it appears to be an AI response. > The content is total nonsense. There is no "SCC" encoder in ffmpeg, > and if there was one, it wouldn't help much because the CC data needs > to get into the video frames - so that it exists as input to the > video encoder. > For the same reason, it is also not possible to add CCs at the muxer > level. It always requires video encoding because the data needs to > get into the video stream itself, so there's no way to get data from > an SCC file into a video stream currently. > > The only way in the ffmpeg architecture to get CC data encoded would > be at the filtering level. The Subtitle Filtering patchset that I > have submitted a while ago has a "splitcc" filter which has video as > input and a video plus a subtitle pin/pad at the output side. > What would be needed is a reverse pendant like a "mergecc" filter > with video and subtitles input - plus a CEA-608/708 encoder. > > softworkz > > _______________________________________________ > 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". _______________________________________________ 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-07 18:55 UTC|newest] Thread overview: 36+ 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 [this message] 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
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=DM8P223MB03659B80A3CA1AD7AF706070BAF12@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