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 20:58:03 +0000
Message-ID: <DM8P223MB03651E07A277C95A3B95130BBAF12@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CANJxsB=3TVpOazWsWA+e6e3U475NXADr+Z5HFY4B8oJXa+k9jA@mail.gmail.com>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Devlist Archive
> Sent: Friday, February 7, 2025 9:50 PM
> To: FFmpeg development discussions and patches <ffmpeg-
> devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Captions SCC
>
> At some point we will need to separate the embed/extract conversation
> from
> the transcode conversation. I have made a ticket over on Trac that
> covers
> the information for the transcode issue. Let's focus on what needs
> to
> happen to be able to generate a valid CEA-608 .scc file and embed
> such a
> file to mp4 on this thread. The EP12 folder on that drive link
> contains
> captions files generated by the content producer using CaptionsMaker.
> That
> captions maker .scc file behaves differently and fails to embed
> compared to
> the premiere produced one.
You have never successfully "embedded" an scc file as CEA-608.
I had told you that twice already. Marth64 has told you the same.
That's not possible right now. Your commands are adding the scc
captions as mov_text (TTXT) subtitle stream, not as 608 CC.
sw
_______________________________________________
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 20:58 UTC|newest]
Thread overview: 42+ 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 [this message]
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
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=DM8P223MB03651E07A277C95A3B95130BBAF12@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