From: Marth64 <marth64@proxyid.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Captions SCC
Date: Fri, 7 Feb 2025 10:18:22 -0600
Message-ID: <CAAhd_PWPT2tVoeqnODFBGfYbov1QV2xb-mmDQEb2MQ3Q7UpaKA@mail.gmail.com> (raw)
In-Reply-To: <CANJxsBkYuVh8exMSQ9_Yo40=ApHD4PoeOmxy8nof+ABFv-W5vA@mail.gmail.com>
Hey Zach,
Thanks for the additional context.
Embedding in the traditional sense is not available now.
If archival is also a primary goal, have you checked out the RCWT muxer?
This muxer can collect the original EIA608/CEA708 bytes with all
fields, in A53 Part 4 format,
to a preservable file. The RCWT format is ccextractor's native format
for archival and is publically documented.
You can do something like,
ffmpeg -f lavfi -i "movie=MyMovie.mkv[out+subcc]" -map 0:s -c:s copy
-f rcwt MyMoviePreservedCC.bin
Then postprocess with either ccextractor or FFmpeg, eg
ffmpeg -i MyMoviePreservedCC.bin output.ass
or
ccextractor -trim MyMoviePreservedCC.bin
FFmpeg's EIA608 decoder does an OK job of preserving some formatting
when converting to ASS.
RCWT gives you archival and post processing flexibility.
Does this help?
_______________________________________________
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 16:19 UTC|newest]
Thread overview: 54+ 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 [this message]
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
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
2025-05-28 15:20 ` 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_PWPT2tVoeqnODFBGfYbov1QV2xb-mmDQEb2MQ3Q7UpaKA@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