Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Jan Ekström" <jeebjp@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/mpegvideo_dec: properly set output frames as keyframes
Date: Sat, 15 Jul 2023 20:40:18 +0300
Message-ID: <CAEu79SbqXJ+6T5uf5LzVVn0iS1XOoFQegs_q4zsejOGzJUSK3w@mail.gmail.com> (raw)
In-Reply-To: <20230714123132.55249-1-jamrial@gmail.com>

On Fri, Jul 14, 2023 at 3:32 PM James Almer <jamrial@gmail.com> wrote:
>
> Should fix ticket #10426.
>
> Signed-off-by: James Almer <jamrial@gmail.com>
> ---
>  libavcodec/mpegvideo_dec.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/libavcodec/mpegvideo_dec.c b/libavcodec/mpegvideo_dec.c
> index fcca147cd6..670b0912e2 100644
> --- a/libavcodec/mpegvideo_dec.c
> +++ b/libavcodec/mpegvideo_dec.c
> @@ -344,9 +344,9 @@ FF_ENABLE_DEPRECATION_WARNINGS
>
>      s->current_picture_ptr->f->pict_type = s->pict_type;
>      if (s->pict_type == AV_PICTURE_TYPE_I)
> -        s->current_picture.f->flags |= AV_FRAME_FLAG_KEY;
> +        s->current_picture_ptr->f->flags |= AV_FRAME_FLAG_KEY;
>      else
> -        s->current_picture.f->flags &= ~AV_FRAME_FLAG_KEY;
> +        s->current_picture_ptr->f->flags &= ~AV_FRAME_FLAG_KEY;
>

Seems to fix the not-meant-to-happen switch from
`s->current_picture_ptr->f` to `s->current_picture.f` that occurred in
dc7bd7c5a5ad5ea800dfb63cc5dd15670d065527 .

Thus LGTM.

Jan
_______________________________________________
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:[~2023-07-15 17:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-14 12:31 James Almer
2023-07-15 17:40 ` Jan Ekström [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=CAEu79SbqXJ+6T5uf5LzVVn0iS1XOoFQegs_q4zsejOGzJUSK3w@mail.gmail.com \
    --to=jeebjp@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