Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Kieran Kunhya via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Kieran Kunhya <kieran618@googlemail.com>
Subject: Re: [FFmpeg-devel] [PATCH] libavcodec/mpeg12dec.c: rename 0x0502 CC format
Date: Sun, 26 Jan 2025 10:04:42 +0000
Message-ID: <CABGuwEm_9PZ=Qj45XsqGxYDARUdaU3Z8SfcWqkOj-zMCyPxKEw@mail.gmail.com> (raw)
In-Reply-To: <DM8P223MB0365AFDAEE2440A4FC6F989ABAED2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>

On Sun, 26 Jan 2025, 00:31 Soft Works, <softworkz-at-hotmail.com@ffmpeg.org>
wrote:

> > -----Original Message-----
> > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> > Marth64
> > Sent: Sunday, January 26, 2025 1:14 AM
> > To: FFmpeg development discussions and patches <ffmpeg-
> > devel@ffmpeg.org>
> > Subject: Re: [FFmpeg-devel] [PATCH] libavcodec/mpeg12dec.c: rename
> > 0x0502 CC format
> >
> > > they are broadcasting using a variation of DVB-S (there is no US
> > standard for sat tv), so the current naming is actually valid.
> >
> > This is my understanding also, but I do believe there was 1 other
> > network that used the same variation.
> > Hence why I suggested a generic name. The counter argument from
> > Kieran
> > was that it's not a DVB standard either so DVB 0502 not a great name.
>
> It's "user data", so there doesn't necessarily need to be a standard. It's
> inconsistent anyway:
>
> SCTE-20 (5.7) defines a single byte:
>
> "user_data_type_code—An eight-bit code for picture user data, 0x03"
>
> while ATSC/A53-Part 4 (6.2.3) mandates a
>
> "user_data_identifier – This is a 32 bit code"
>
> Which is supposed to be registered with SMPTE:
>
>
> https://web.archive.org/web/20150324170029/http://www.smpte-ra.org/mpegreg/mpegreg.html
>
> Then followed by 03 as type code.
>
> (this aligns with the implementation)
>
>
> I haven't found the corresponding in the DVB specs, it must have a
> different name there.
>

DVB (TS 101 154) mandates a particular way of transporting captions (that
the Dish method predates). There are other operators that do their own
thing too.

Kieran

>
_______________________________________________
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-01-26 10:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-25 20:26 Scott Theisen
2025-01-25 20:39 ` Marton Balint
2025-01-25 22:52   ` Marth64
2025-01-25 23:28     ` Kieran Kunhya via ffmpeg-devel
2025-01-25 23:53       ` Scott Theisen
2025-01-26  0:07         ` Soft Works
2025-01-26  0:13           ` Marth64
2025-01-26  0:30             ` Soft Works
2025-01-26 10:04               ` Kieran Kunhya via ffmpeg-devel [this message]
2025-01-26 23:00                 ` Soft Works
2025-01-26 23:11                   ` Kieran Kunhya via ffmpeg-devel
2025-01-27  0:34                     ` Marth64
2025-02-02 18:55                       ` [FFmpeg-devel] [PATCH v2] " Scott Theisen
2025-02-03  2:40                         ` 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='CABGuwEm_9PZ=Qj45XsqGxYDARUdaU3Z8SfcWqkOj-zMCyPxKEw@mail.gmail.com' \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=kieran618@googlemail.com \
    /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