Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Wu, Tong1" <tong1.wu-at-intel.com@ffmpeg.org>
To: "Xiang, Haihao" <haihao.xiang@intel.com>,
	"ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] avcodec/vaapi_encode_h265: use is_reference to fill reference_pic_flag
Date: Tue, 5 Mar 2024 08:06:59 +0000
Message-ID: <CH3PR11MB86594354BF709B33D7F71712C0222@CH3PR11MB8659.namprd11.prod.outlook.com> (raw)
In-Reply-To: <bef159119627eb44816080b3ab7fc3658cf5b8d6.camel@intel.com>

>Subject: Re: [FFmpeg-devel] [PATCH 2/2] avcodec/vaapi_encode_h265: use
>is_reference to fill reference_pic_flag
>
>On Di, 2024-02-27 at 11:48 +0800, tong1.wu-at-intel.com@ffmpeg.org wrote:
>> From: Tong Wu <tong1.wu@intel.com>
>>
>> This codec supports FLAG_B_PICTURE_REFERENCES. We need to fill
>> reference_pic_flag with pic->is_reference.
>>
>> Signed-off-by: Tong Wu <tong1.wu@intel.com>
>> ---
>>  libavcodec/vaapi_encode_h265.c | 8 ++++----
>>  1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/libavcodec/vaapi_encode_h265.c
>b/libavcodec/vaapi_encode_h265.c
>> index c4aabbf5ed..b5d3468152 100644
>> --- a/libavcodec/vaapi_encode_h265.c
>> +++ b/libavcodec/vaapi_encode_h265.c
>> @@ -949,22 +949,22 @@ static int
>> vaapi_encode_h265_init_picture_params(AVCodecContext *avctx,
>>      case PICTURE_TYPE_IDR:
>>          vpic->pic_fields.bits.idr_pic_flag       = 1;
>>          vpic->pic_fields.bits.coding_type        = 1;
>> -        vpic->pic_fields.bits.reference_pic_flag = 1;
>> +        vpic->pic_fields.bits.reference_pic_flag = pic->is_reference;
>>          break;
>>      case PICTURE_TYPE_I:
>>          vpic->pic_fields.bits.idr_pic_flag       = 0;
>>          vpic->pic_fields.bits.coding_type        = 1;
>> -        vpic->pic_fields.bits.reference_pic_flag = 1;
>> +        vpic->pic_fields.bits.reference_pic_flag = pic->is_reference;
>>          break;
>>      case PICTURE_TYPE_P:
>>          vpic->pic_fields.bits.idr_pic_flag       = 0;
>>          vpic->pic_fields.bits.coding_type        = 2;
>> -        vpic->pic_fields.bits.reference_pic_flag = 1;
>> +        vpic->pic_fields.bits.reference_pic_flag = pic->is_reference;
>>          break;
>>      case PICTURE_TYPE_B:
>>          vpic->pic_fields.bits.idr_pic_flag       = 0;
>>          vpic->pic_fields.bits.coding_type        = 3;
>> -        vpic->pic_fields.bits.reference_pic_flag = 0;
>> +        vpic->pic_fields.bits.reference_pic_flag = pic->is_reference;
>
>Better to move the assignment out of the switch statement.

Sorry I misunderstood. Please see patch V3.

>
>Thanks
>Haihao
>
>>          break;
>>      default:
>>          av_assert0(0 && "invalid picture type");

_______________________________________________
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:[~2024-03-05  8:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-27  3:48 [FFmpeg-devel] [PATCH 1/2] avcodec/vaapi_encode_h264: " tong1.wu-at-intel.com
2024-02-27  3:48 ` [FFmpeg-devel] [PATCH 2/2] avcodec/vaapi_encode_h265: " tong1.wu-at-intel.com
2024-03-05  7:29   ` Xiang, Haihao
2024-03-05  8:06     ` Wu, Tong1 [this message]
2024-03-05  7:30 ` [FFmpeg-devel] [PATCH 1/2] avcodec/vaapi_encode_h264: " Xiang, Haihao

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=CH3PR11MB86594354BF709B33D7F71712C0222@CH3PR11MB8659.namprd11.prod.outlook.com \
    --to=tong1.wu-at-intel.com@ffmpeg.org \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=haihao.xiang@intel.com \
    /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