Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Maryla Ustarroz via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Maryla Ustarroz <maryla@google.com>
Subject: Re: [FFmpeg-devel] [PATCH v2] avcodec/itut35: always check the provider code and country code together
Date: Tue, 5 Aug 2025 12:14:23 +0200
Message-ID: <CA+yX6GH=ZzPYD_XVOKoaBZKwFNzZP7cFVCTUT-_Xy-PRA721Gw@mail.gmail.com> (raw)
In-Reply-To: <20250803230838.GL29660@pb2>

On Mon, Aug 4, 2025 at 1:08 AM Michael Niedermayer
<michael@niedermayer.cc> wrote:
>
> Hi Maryla
>
> On Wed, Jun 25, 2025 at 05:55:45PM +0200, Maryla Ustarroz-Calonge via ffmpeg-devel wrote:
> > Date: Wed, 25 Jun 2025 17:55:45 +0200
> > From: Maryla Ustarroz-Calonge <maryla@google.com>
> > To: ffmpeg-devel@ffmpeg.org
> > Subject: [PATCH v2] avcodec/itut35: always check the provider code and country code together
> >
> > From: Maryla <maryla@google.com>
> >
> > ITU-T T.35 provider codes are attributed by national bodies and it's
> > possible to have collisions across countries. This is why the country code
> > must always be checked as well.
> >
> > Use if statements rather than nested switches which would be unreadable.
> >
>
> > Rename some of the constants to match the corresponding organization.
>
> Renaming should be a seperate patch
>
>
> > Add a constant for AOM.
> > Write all constants with 4 hex digits to make it clear that they are 2-byte ids.
> >
>
> > The code for V-Nova should be 0x5000 instead of 0x0050 according to the
> > UK Register of Manufacturer Codes https://www.cix.co.uk/~bpechey/H221/h221code.htm
> > but I have been unable to find any reference for what code should be used for
> > LCEVC, and the author of the original change has not replied to my emails.
>
> this should be a seperate patch
>
> in general, please split this up a bit to make it easier to review
>
This was informational, I did not change the code.

> [...]
>
> > diff --git a/libavcodec/libdav1d.c b/libavcodec/libdav1d.c
> > index f4cbc927b5..a1158a23c4 100644
> > --- a/libavcodec/libdav1d.c
> > +++ b/libavcodec/libdav1d.c
> > @@ -386,6 +386,80 @@ static int libdav1d_receive_frame_internal(AVCodecContext *c, Dav1dPicture *p)
> >      return res;
> >  }
> >
> > +static int parse_itut_t35_metadata(Libdav1dContext *dav1d, Dav1dPicture *p,
> > +                                   const Dav1dITUTT35 *itut_t35, AVCodecContext *c,
> > +                                   AVFrame *frame) {
> > +    GetByteContext gb;
> > +    int provider_code, country_code;
> > +    int res;
>
> please split the factorization of code from changes to the code.
> That way the changes are clearer vissible in the patch
>
>
> thx
>

Thank you for the review. I resent this patch split into three parts.

> [...]
>
> --
> Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
> Some people wanted to paint the bikeshed green, some blue and some pink.
> People argued and fought, when they finally agreed, only rust was left.
> _______________________________________________
> 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".
_______________________________________________
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-08-05 10:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-25 15:55 Maryla Ustarroz-Calonge via ffmpeg-devel
2025-08-03 23:08 ` Michael Niedermayer
2025-08-05 10:14   ` Maryla Ustarroz via ffmpeg-devel [this message]
     [not found] <20250625155545.933182-1-maryla@google.com>
2025-07-30 15:49 ` Maryla Ustarroz via ffmpeg-devel

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='CA+yX6GH=ZzPYD_XVOKoaBZKwFNzZP7cFVCTUT-_Xy-PRA721Gw@mail.gmail.com' \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=maryla@google.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