Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
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: Tue, 4 Mar 2025 10:13:32 -0500
Message-ID: <CAHGibzFcdz0CRCevmQub4oj-cUcwPR4a0P9GZ25vKyLyDiBWLg@mail.gmail.com> (raw)
In-Reply-To: <eabed405c6685ddc05bf31e65d3c05b9b6c4dbf7.camel@haerdin.se>

On Tue, Mar 4, 2025 at 4:02 AM Tomas Härdin <git@haerdin.se> wrote:
> So it's "US" even if something is broadcast in Sweden? T.35 has a whole
> list of countries, some of which don't exist any more, and some new
> ones are missing

Correct.  So the T.35 country code doesn't actually have anything to
do with where the stream is broadcast.  It's intended to define which
standards body (via a country code and provider code) is responsible
for defining the structure of the payload that follows (in the case of
CEA-708 captions case the country code is US and the provider code is
ATSC).

> > Even if the captions are intended to
> > serve other countries, the country code will stay the same (defining
> > the country code for individual languages goes in the PMT).
>
> How is one supposed to mux multiple subtitle languages in MPEGTS +
> H.264 anyway? This isn't clear at all from what I've read. Country
> codes, as opposed to language codes, being used in the 708 SEI makes it
> worse. And what of other container formats that have no PMT?

So unlike with DVB/teletext, the caption data streams are not provided
on separate ES streams.  They are embedded in the video stream, and
the CEA-708 standard supports multiple languages within that payload
(depending on specifically which form is used, it can be up to six or
up to 64).  The actual languages assigned to the different streams
within the 708 payload are specified either in the PMT via the "ATSC
Caption" descriptor, or in the ATSC PSIP data.

Muxing together captions from different sources is pretty painful,
since you have to parse/decompose the 708 stream and recombine streams
from different sources (and then update the PMT).  I have code which
does it but haven't made any effort to open source it, and I'm not
confident it could easily be done within ffmpeg due to limitations in
the ffmpeg framework.

It's also worth noting that the Caption descriptor as defined in the
standard does not let you specify the language of individual CTA-608
channels within a 708 stream (which is what most people care about).
The only way to specify the language for the 608 channels (e.g.
CC1-CC4) is via XDS bytes within the 608 stream, which almost nobody
does nowadays.  I ran a scan across my network of thousands of
channels from different commercial hardware encoders, and couldn't
find a single one that specified the 608 language in XDS (if I found
cases where it was, I was prepared to submit patches to VLC to show
the language in the subtitle dropdown menu).

Devin

-- 
Devin Heitmueller, Senior Software Engineer
LTN Global Communications
o: +1 (301) 363-1001
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".

      reply	other threads:[~2025-03-04 15:13 UTC|newest]

Thread overview: 7+ 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-03 13:55 ` Devin Heitmueller
2025-03-04  9:01   ` Tomas Härdin
2025-03-04 15:13     ` Devin Heitmueller [this message]

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=CAHGibzFcdz0CRCevmQub4oj-cUcwPR4a0P9GZ25vKyLyDiBWLg@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