From: Hendrik Leppkes <h.leppkes@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] dxva2_hevc: don't use frames as reference if they are not marked as such
Date: Wed, 23 Mar 2022 15:17:07 +0100
Message-ID: <CA+anqdxR49LV=NnTGnORTg-i38-pwHDujqTcncbwFSeHVx8zng@mail.gmail.com> (raw)
In-Reply-To: <20220323135426.32530-1-robux4@ycbcr.xyz>
On Wed, Mar 23, 2022 at 2:54 PM Steve Lhomme <robux4@ycbcr.xyz> wrote:
>
> Similar to how a frame is considered for referencing for the RefPicList array.
> This will do the same for RefPicSetStCurrBefore, RefPicSetStCurrAfter and
> RefPicSetLtCurr.
>
> Fixes playback of http://www.gbbsoft.pl/!download/!/Film1.mp4
> Ref. VLC issue https://code.videolan.org/videolan/vlc/-/issues/26738
>
> Signed-off-by: Steve Lhomme <robux4@ycbcr.xyz>
> ---
> libavcodec/dxva2_hevc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libavcodec/dxva2_hevc.c b/libavcodec/dxva2_hevc.c
> index c91bcf3eeb..6b239d9917 100644
> --- a/libavcodec/dxva2_hevc.c
> +++ b/libavcodec/dxva2_hevc.c
> @@ -184,7 +184,7 @@ static void fill_picture_parameters(const AVCodecContext *avctx, AVDXVAContext *
> const HEVCFrame *frame = NULL; \
> while (!frame && j < rpl->nb_refs) \
> frame = rpl->ref[j++]; \
> - if (frame) \
> + if (frame && frame->flags & (HEVC_FRAME_FLAG_LONG_REF | HEVC_FRAME_FLAG_SHORT_REF)) \
> pp->ref_list[i] = get_refpic_index(pp, ff_dxva2_get_surface_index(avctx, ctx, frame->frame)); \
> else \
> pp->ref_list[i] = 0xff; \
> --
> 2.29.2
>
LGTM
_______________________________________________
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".
prev parent reply other threads:[~2022-03-23 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 13:54 Steve Lhomme
2022-03-23 13:57 ` Steve Lhomme
2022-03-23 14:17 ` Hendrik Leppkes [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='CA+anqdxR49LV=NnTGnORTg-i38-pwHDujqTcncbwFSeHVx8zng@mail.gmail.com' \
--to=h.leppkes@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