From: "Xiang, Haihao" <haihao.xiang-at-intel.com@ffmpeg.org>
To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v4 1/4] lavc/vaapi_encode_h265: Add GPB frame support for hevc_vaapi
Date: Wed, 16 Mar 2022 15:04:25 +0000
Message-ID: <69ed0e9ec49a6aed1a68b31a90465ac125846c9f.camel@intel.com> (raw)
In-Reply-To: <79eb995f-9064-8334-3544-105a83c10f86@jkqxz.net>
>
> Hmm. So if we ignore both the names and the documentation as unhelpful then
> the meanings you are intending are:
>
> Attribute unset -> no restrictions.
> Attribute set -> PREVIOUS bit must be set: P and B slices are both supported
> but RefPicList0 and RefPicList1 must in B slices must be equal.
>
> Then additional bits modify that:
>
> FUTURE bit set -> RefPicList0 and RefPicList1 in B slices may differ.
> BI_NOT_EMPTY bit set -> P slices are not supported.
>
> (If this is actually the intended meaning then maybe someone could add this to
> the documentation in libva?)
I submitted https://github.com/intel/libva/pull/581 to update the doc, you are
welcome to review it.
Thanks
Haihao
_______________________________________________
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".
next prev parent reply other threads:[~2022-03-16 15:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 9:00 Fei Wang
2022-03-11 9:00 ` [FFmpeg-devel] [PATCH v4 2/4] vaapi_encode: Move block size calculation after entrypoint selection Fei Wang
2022-03-11 9:00 ` [FFmpeg-devel] [PATCH v4 3/4] vaapi_encode_h265: Explicitly set and correct some flags Fei Wang
2022-03-11 9:00 ` [FFmpeg-devel] [PATCH v4 4/4] vaapi_encode_h265: Query encoding block sizes and features Fei Wang
2022-03-13 20:45 ` [FFmpeg-devel] [PATCH v4 1/4] lavc/vaapi_encode_h265: Add GPB frame support for hevc_vaapi Mark Thompson
2022-03-14 2:15 ` Xiang, Haihao
2022-03-14 11:07 ` Wang, Fei W
2022-03-15 0:24 ` Mark Thompson
2022-03-16 15:04 ` Xiang, Haihao [this message]
2022-03-14 23:38 ` Mark Thompson
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=69ed0e9ec49a6aed1a68b31a90465ac125846c9f.camel@intel.com \
--to=haihao.xiang-at-intel.com@ffmpeg.org \
--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