From: David Rosca via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: ffmpeg-devel@ffmpeg.org
Cc: David Rosca <code@ffmpeg.org>
Subject: [FFmpeg-devel] [PR] lavc/vaapi_h264: Set VA_PICTURE_H264_NON_EXISTING for invalid gaps (PR #21464)
Date: Wed, 14 Jan 2026 13:28:32 -0000
Message-ID: <176839731258.25.9689212013511117735@4457048688e7> (raw)
PR #21464 opened by David Rosca (nowrep)
URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21464
Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21464.patch
>From b6282c39aa4edad528b0d9df6a45bcf637ee3f63 Mon Sep 17 00:00:00 2001
From: David Rosca <david.rosca@amd.com>
Date: Wed, 14 Jan 2026 12:58:49 +0100
Subject: [PATCH] lavc/vaapi_h264: Set VA_PICTURE_H264_NON_EXISTING for invalid
gaps
---
libavcodec/vaapi_h264.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/libavcodec/vaapi_h264.c b/libavcodec/vaapi_h264.c
index 7f00da09fc..70279ab6d0 100644
--- a/libavcodec/vaapi_h264.c
+++ b/libavcodec/vaapi_h264.c
@@ -25,6 +25,11 @@
#include "hwaccel_internal.h"
#include "vaapi_decode.h"
+/* libva 2.24 */
+#ifndef VA_PICTURE_H264_NON_EXISTING
+#define VA_PICTURE_H264_NON_EXISTING 0x00000020
+#endif
+
/**
* @file
* This file implements the glue code between FFmpeg's and VA API's
@@ -68,6 +73,8 @@ static void fill_vaapi_pic(VAPictureH264 *va_pic,
va_pic->flags |= (pic_structure & PICT_TOP_FIELD) ? VA_PICTURE_H264_TOP_FIELD : VA_PICTURE_H264_BOTTOM_FIELD;
if (pic->reference)
va_pic->flags |= pic->long_ref ? VA_PICTURE_H264_LONG_TERM_REFERENCE : VA_PICTURE_H264_SHORT_TERM_REFERENCE;
+ if (pic->invalid_gap)
+ va_pic->flags |= VA_PICTURE_H264_NON_EXISTING;
va_pic->TopFieldOrderCnt = 0;
if (pic->field_poc[0] != INT_MAX)
--
2.49.1
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
reply other threads:[~2026-01-14 13:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=176839731258.25.9689212013511117735@4457048688e7 \
--to=ffmpeg-devel@ffmpeg.org \
--cc=code@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