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] [PATCH] libavcodec/mpeg12dec.c: rename 0x0502 CC format
Date: Sun, 26 Jan 2025 00:07:17 +0000
Message-ID: <DM8P223MB0365D8678DD9402BF4D53BC6BAED2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <6b312a11-2a52-40e8-bfdb-1fba445f27a8@gmail.com>

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Scott Theisen
> Sent: Sunday, January 26, 2025 12:54 AM
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH] libavcodec/mpeg12dec.c: rename
> 0x0502 CC format
> 
> On 1/25/25 18:28, Kieran Kunhya via ffmpeg-devel wrote:
> > On Sat, 25 Jan 2025, 22:53 Marth64, <marth64@proxyid.net> wrote:
> >
> >> Hello,
> >>
> >> I am to blame here for suggesting DVB_0502 as the name.
> >> I realize it was not the best choice and apologize for wasting
> your
> >> cycles on this.
> >>
> >> Looping in Keiran as we had discussed this over IRC briefly a few
> weeks
> >> back.
> >> As I don't know how many networks actually use this in the wild,
> it
> >> could be one or more,
> >>
> >> How does something like this sound? CC_FORMAT_USERDATA_0502
> >>
> > I believe it's Dish Network:
> >
> >
> https://github.com/CCExtractor/ccextractor/blob/master/src/lib_ccx/es
> _userdata.c#L275
> >
> > Kieran
> 
> I had originally used CC_FORMAT_DISH because ccextractor said Dish
> Network, but Marth64 didn't want it referencing a specific provider [
> https://ffmpeg.org//pipermail/ffmpeg-devel/2024-November/336384.html
> ].
> 
> CC_FORMAT_USERDATA_0502 is fine with me, but I'm not sure if Marton
> Balint's objection was because the new name was only a number or if
> the
> additional USERDATA string is sufficient.


When it's Dish, then there's no need to change it, because they are broadcasting using a variation of DVB-S (there is no US standard for sat tv), so the current naming is actually valid.

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

  reply	other threads:[~2025-01-26  0:07 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 [this message]
2025-01-26  0:13           ` Marth64
2025-01-26  0:30             ` Soft Works
2025-01-26 10:04               ` Kieran Kunhya via ffmpeg-devel
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=DM8P223MB0365D8678DD9402BF4D53BC6BAED2@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