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 19:44:29 +0000
Message-ID: <DM8P223MB0365B0CF96BC60164FA54FCCBAF12@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <CANJxsBk-OeWEJ1EmTDSL+b4r2k=WN7pXhLfHxkL=3APcdq9ZhQ@mail.gmail.com>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Devlist Archive
> Sent: Friday, February 7, 2025 8:31 PM
> To: FFmpeg development discussions and patches <ffmpeg-
> devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] Captions SCC
>
> >
> > The cc_fifo mechanism is actually implemented within the various
> > filters which change the framerate (deinterlacing, framerate
> > conversion, interlacing), so no extra command line arguments are
> > required. There are some edge cases though that don't properly
> handle
> > it, and those mainly relate to cases such as the captions crossing
> > back/forth between SEI and dedicated caption tracks (e.g. MP4 with
> a
> > caption track, the subcc output, etc).
> >
>
> Ok, based on this information I am going to make a bug report ticket
> for
> the particular type of mp4 files I am using because while some
> caption data
> is passed, it is garbled and the transcoding process is producing
> errors.
> I was not aware that some work had been done to try to solve the
> frame rate
> conversion issue already as the behaviour of ffmpeg implies that it
> doesn't
> try to compensate for those changes for the file types I am working
> with.
> There are also bugs in the subcc function that seem to be affecting
> display
> time and other metadata.
>
> I assume that it would be more efficient and better to fix the
> existing 608
> only data path before trying to expand things to include 708?
>
> Zach
Unfortunately, there's no bug which could be "fixed".
For a proper solution, a CEA-608 ENcoder is required.
And more - like already said.
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 19:44 UTC|newest]
Thread overview: 38+ 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 [this message]
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
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=DM8P223MB0365B0CF96BC60164FA54FCCBAF12@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