From: Jack Lau <jacklau1222gm@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Captions SCC
Date: Fri, 7 Feb 2025 15:58:08 +0800
Message-ID: <3D8AD125-395A-48DD-A243-EEF878AF73FB@gmail.com> (raw)
In-Reply-To: <DM8P223MB0365671DCF49C8686AFF7108BAF12@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>
>
>
> 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
>
Hi softworkz,
Sorry about that, The response is indeed from AI. I thought this question was enough for AI to answer, I will pay attention to it next time.
Thank you for pointing it out.
Jack
_______________________________________________
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 7:58 UTC|newest]
Thread overview: 9+ 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 [this message]
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
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=3D8AD125-395A-48DD-A243-EEF878AF73FB@gmail.com \
--to=jacklau1222gm@gmail.com \
--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