From: Devlist Archive <devlist@rlb.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Captions SCC
Date: Fri, 7 Feb 2025 08:42:29 -0800
Message-ID: <CANJxsBnD7R29NeTHT4DTsk2eJmrsVa-FzP0uQ015QkYyp8OEKw@mail.gmail.com> (raw)
In-Reply-To: <CAAhd_PU8LhXwjeeE+QVSdOt9A=F1d2k-NHw0zc-LVgUb0vdzjQ@mail.gmail.com>
My application is actually to generate a playout library for over the air
TV, then implement a captions data path into a sub project that relies on
ffmpeg for decode/encode. So I need to not just do archival, but build a
library in a usable format. This requires an ingest process for both an
edit workflow and playout.
As such, I may be able to work out an edit workflow by using RCWT to make a
.bin file, using ccextractor to make an mcc file and importing into an edit
suite for transcode. The part I will still be missing is something to take
the .ssc file output from Premiere and put it back in the .mp4 container.
Embedding seems to be present for some forms of subtitles, but not for a
proper captions file generated by MacCaption or Captionmaker which is
software I am trying to avoid having to buy as I would much rather those
funds go towards development. One solution I guess would be to just
require sidecar files for playout which I would prefer not to require. I
can look into those solutions off list. MCC files or other formats that
support 708 are the ideal, but 608 is all that is required.
If anyone else has ideas or interest in developing a more integrated
process for ffmpeg, I may still be interested in funding that after I
investigate the above solutions off list.
Zach
On Fri, Feb 7, 2025 at 8:37 AM Marth64 <marth64@proxyid.net> wrote:
> Added bit: RCWT will preserve more than what the SCC muxer does
> You can also convert the RCWT back to SCC with a single EIA608 field
> array, again with either tool
> _______________________________________________
> 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 16:42 UTC|newest]
Thread overview: 37+ 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 [this message]
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
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=CANJxsBnD7R29NeTHT4DTsk2eJmrsVa-FzP0uQ015QkYyp8OEKw@mail.gmail.com \
--to=devlist@rlb.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