From: Devin Heitmueller <devin.heitmueller@ltnglobal.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] lavc: Replace 181 magic number with ITU_T_T35_COUNTRY_CODE_US
Date: Mon, 31 Mar 2025 11:55:19 -0400
Message-ID: <CAHGibzHFZL6MKkK7D=H5PVmuornu-5HzSwn372+CtZKjCk6XUA@mail.gmail.com> (raw)
In-Reply-To: <0be580d28e930acff066051e6111bc72eaeaed7a.camel@haerdin.se>
Hello Tomas,
On Mon, Mar 31, 2025 at 11:24 AM Tomas Härdin <git@haerdin.se> wrote:
> > Yeah, I didn't have a particularly positive experience with
> > libcaption, despite the fact that I know it's what a number of
> > projects use (including OBS). Everytime I look at that code I spot a
> > whole pile of things they are doing wrong. Probably the most obvious
> > is that they don't properly do rate control for the 608/708 tuples to
> > embed in the stream, so the resulting stream won't work properly with
> > many decoders/transcoders. This was actually one reason I wrote the
> > vf_ccrepack filter in ffmpeg, to deal with cases where somebody used
> > libcaption to embed CC into a TS. The ccrepack filter puts the
> > caption tuples into.a queue and then re-embeds them at the appropriate
> > rate given the target framerate.
>
> Did you report this to libcaption's devs?
Respectfully, libcaption is essentially a dead project. The main repo
hasn't had a commit in seven years, there are numerous separate forks
with fixes/improvements. The OBS project has its own repo with fixes
they've made, and they are well aware of the problem (in fact the
ticket includes some discussion I had with one of the developers).
https://github.com/obsproject/obs-studio/issues/4006
Devin
--
Devin Heitmueller,
LTN Global Communications
o: m:
w: https://ltnglobal.com e: devin.heitmueller@ltnglobal.com
_______________________________________________
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-03-31 15:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 12:25 Tomas Härdin
2025-03-03 13:12 ` Andreas Rheinhardt
2025-03-04 9:12 ` Tomas Härdin
2025-03-04 11:31 ` Andreas Rheinhardt
2025-03-04 22:57 ` Michael Niedermayer
2025-03-03 13:55 ` Devin Heitmueller
2025-03-04 9:01 ` Tomas Härdin
2025-03-04 15:13 ` Devin Heitmueller
2025-03-04 23:13 ` Marth64
2025-03-10 9:57 ` Tomas Härdin
2025-03-10 13:57 ` Devin Heitmueller
2025-03-31 15:24 ` Tomas Härdin
2025-03-31 15:55 ` Devin Heitmueller [this message]
2025-03-31 16:02 ` Tomas Härdin
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='CAHGibzHFZL6MKkK7D=H5PVmuornu-5HzSwn372+CtZKjCk6XUA@mail.gmail.com' \
--to=devin.heitmueller@ltnglobal.com \
--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