Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Tom Yan <tom.ty89@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2] mpegvideo_parser: check picture_structure for field order
Date: Sun, 6 Feb 2022 16:59:24 +0800
Message-ID: <CAGnHSE=4HP-XE-GRx96+cTnFT6O-WP58icjViyt6TvdSF4JHwQ@mail.gmail.com> (raw)
In-Reply-To: <AM7PR03MB6660B9E17873045C732FD1888F2B9@AM7PR03MB6660.eurprd03.prod.outlook.com>

This is really just a matter of choice. If you don't care about
spec-conformance in this particular case, top_field_first *could* be 1
and/or picture_structure *could* be not 3 even when
progressive_sequence is 1, so which one do you choose to believe? The
truth is, it doesn't even matter.

If you insist on making it more clumsy and silly, I can resend.

On Sun, 6 Feb 2022 at 13:46, Andreas Rheinhardt
<andreas.rheinhardt@outlook.com> wrote:
>
> Tom Yan:
> > the top_field_first bit is only used to indicate the field order
> > when the picture is a frame picture (which consists of two fields)
> > but not when it is a field picture (which consists of one single
> > top or bottom field).
> >
> > also removing the unnecessary progressive_sequence check (the bit
> > is mandated to be 0 if progressive_frame is 0 on any picture in the
> > sequence).
> >
>
> Just because something is mandated does not mean that it is so;
> spec-incompliant files exist.
>
> > Signed-off-by: Tom Yan <tom.ty89@gmail.com>
> > ---
> >  libavcodec/mpegvideo_parser.c | 15 +++++++++------
> >  1 file changed, 9 insertions(+), 6 deletions(-)
> >
> > diff --git a/libavcodec/mpegvideo_parser.c b/libavcodec/mpegvideo_parser.c
> > index c5dc867d24..004ff602f6 100644
> > --- a/libavcodec/mpegvideo_parser.c
> > +++ b/libavcodec/mpegvideo_parser.c
> > @@ -181,6 +181,7 @@ static void mpegvideo_extract_headers(AVCodecParserContext *s,
> >                      break;
> >                  case 0x8: /* picture coding extension */
> >                      if (bytes_left >= 5) {
> > +                        s->picture_structure = buf[2] & 0x3;
> >                          top_field_first = buf[3] & (1 << 7);
> >                          repeat_first_field = buf[3] & (1 << 1);
> >                          progressive_frame = buf[4] & (1 << 7);
> > @@ -198,13 +199,15 @@ static void mpegvideo_extract_headers(AVCodecParserContext *s,
> >                              }
> >                          }
> >
> > -                        if (!pc->progressive_sequence && !progressive_frame) {
> > -                            if (top_field_first)
> > -                                s->field_order = AV_FIELD_TT;
> > -                            else
> > -                                s->field_order = AV_FIELD_BB;
> > -                        } else
> > +                        if (progressive_frame)
> >                              s->field_order = AV_FIELD_PROGRESSIVE;
> > +                        else if (top_field_first ||
> > +                                 /* top_field_first is mandated to be 0 when
> > +                                    the picture is not a frame picture) */
> > +                                 s->picture_structure == AV_PICTURE_STRUCTURE_TOP_FIELD)
> > +                            s->field_order = AV_FIELD_TT;
> > +                        else
> > +                            s->field_order = AV_FIELD_BB;
> >                      }
> >                      break;
> >                  }
>
> _______________________________________________
> 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:[~2022-02-06  8:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-05 12:51 [FFmpeg-devel] [PATCH] " Tom Yan
2022-02-05 13:12 ` Tom Yan
2022-02-05 13:31 ` James Almer
2022-02-06  5:41   ` [FFmpeg-devel] [PATCH v2] " Tom Yan
2022-02-06  5:45     ` Andreas Rheinhardt
2022-02-06  8:59       ` Tom Yan [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='CAGnHSE=4HP-XE-GRx96+cTnFT6O-WP58icjViyt6TvdSF4JHwQ@mail.gmail.com' \
    --to=tom.ty89@gmail.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