Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
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 07:48:11 +0000
Message-ID: <DM8P223MB0365671DCF49C8686AFF7108BAF12@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CANJxsBkx5Qgte2sN4tk3u-F68FeNAia2ffSYga_4qHBEm5WPxA@mail.gmail.com>

> -----Original Message-----
> From: ffmpeg-devel <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>
> Subject: Re: [FFmpeg-devel] Captions SCC
> 
> On Thu, Feb 6, 2025 at 4:57 AM Jack Lau <jacklau1222gm@gmail.com>
> wrote:
> 
> >
> >
> > > I have been absent from the list for a few years, so I would
> appreciate
> > it
> > > if someone could catch me up a bit.  I am needing to extract and
> embed
> > scc
> > > files with 608 captions.  I am pleased to see that transcoding
> without
> > > frame rate changes now preserves 608 intact, and there appear to
> be
> > > extraction and embed functions but they do seem to have bugs for
> my files
> > > at 1080p2997.  Are there any developers willing to take on a paid
> project
> > > to fix whatever is the issue?  Here are the commands I am working
> with.
> > >
> > > Embed:
> > > "C:\FFmpeg\ffmpeg7.1_2024-12-14\ffmpeg.exe" -i
> > > "C:\Users\Captions\AIM-2301_premiereDF.mp4" -i
> > > "C:\Captions\AIM-2301_premiereDF.mp4.scc" -map 0:v -map 0:a -map
> 1 -c:v
> > > copy -c:a copy -c:s mov_text -metadata:s:s:0 language=eng
> > > "C:\Captions\AIM-2301_premiereDFcopy.mp4"
> > >
> > > Extract:
> > > "C:\FFmpeg\ffmpeg7.1_2024-12-14\ffmpeg.exe" -f lavfi -i
> > >
> > "movie=\'C:\\Captions\\AIM-
> 2301_premiereDF_ffmpegEmbedscc.mp4\'"[out+subcc]
> > > -map 0:1 -c:s copy "C:\Captions\AIM-
> 2301_premiereDF_ffmpegEmbedscc.scc”
> > >
> >
> >
> > Hi,
> >
> > I’ve reviewed the issue with embedding and extracting 608 SCC
> captions at
> > 1080p2997 resolution and identified a few areas that might help
> resolve the
> > character duplication and data spill. Here's a summary of my
> findings:
> >
> > The current command uses -c:s mov_text, but SCC files may work
> better with
> > -c:s scc to preserve the format correctly.
> > The current command uses a filtergraph that might not map correctly
> for
> > SCC extraction. Instead, try simplifying the extraction command: -
> map 0:s:0
> > -c:s copy
> > Frame Rate Issues: Ensure the video frame rate and the SCC file
> frame rate
> > match. You might want to force a specific frame rate (e.g., -r
> 29.97).
> >
> > Let me know if you have further questions.
> > _______________________________________________
> > ffmpeg-devel mailing list
> > ffmpeg-devel@ffmpeg.org
> > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

> Hi Jack,
> 
> Thanks for the suggestions.  Could you please tell me where I can get
> a
> build of ffmpeg that will work with the -c:s scc command?  That
> encoder
> doesn't seem to be in the release version I am working with.
> 
> It is slightly unclear to me how your suggestion for the extract
> command
> suggestion should be implemented.  All of my media files I am working
> with
> now are the same frame rate, but forcing a frame rate prior to
> embedding is
> probably a good idea.  I had assumed there were still bugs in the
> code for
> this, but it would be nice if extraction/embedding could work without
> having to  change more.
> 
> Zach


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".

  reply	other threads:[~2025-02-07  7:48 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 [this message]
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

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=DM8P223MB0365671DCF49C8686AFF7108BAF12@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