From: "Wang, Fei W" <fei.w.wang-at-intel.com@ffmpeg.org> To: "ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org> Cc: Linjie Fu <linjie.justin.fu@gmail.com>, Linjie Fu <linjie.fu@intel.com> Subject: Re: [FFmpeg-devel] [PATCH v3 08/11] lavc/vaapi_hevc: Pass SCC parameters Through VA-API Date: Wed, 11 Jan 2023 02:45:09 +0000 Message-ID: <PH0PR11MB5030787A08DD4F8BE2F61858CDFC9@PH0PR11MB5030.namprd11.prod.outlook.com> (raw) In-Reply-To: <20230103125952.2707824-8-fei.w.wang@intel.com> > -----Original Message----- > From: Wang, Fei W <fei.w.wang@intel.com> > Sent: Tuesday, January 3, 2023 9:00 PM > To: ffmpeg-devel@ffmpeg.org > Cc: Linjie Fu <linjie.fu@intel.com>; Linjie Fu <linjie.justin.fu@gmail.com>; Wang, > Fei W <fei.w.wang@intel.com> > Subject: [FFmpeg-devel][PATCH v3 08/11] lavc/vaapi_hevc: Pass SCC parameters > Through VA-API > > From: Linjie Fu <linjie.fu@intel.com> > > Including sps/pps/slice parameters. > > Signed-off-by: Linjie Fu <linjie.justin.fu@gmail.com> > Signed-off-by: Fei Wang <fei.w.wang@intel.com> > --- > libavcodec/vaapi_hevc.c | 52 +++++++++++++++++++++++++++++++++++++---- > 1 file changed, 47 insertions(+), 5 deletions(-) > > diff --git a/libavcodec/vaapi_hevc.c b/libavcodec/vaapi_hevc.c index > 20fb36adfa..73a8f5b4ce 100644 > --- a/libavcodec/vaapi_hevc.c > +++ b/libavcodec/vaapi_hevc.c > @@ -124,7 +124,7 @@ static int vaapi_hevc_start_frame(AVCodecContext > *avctx, > const HEVCPPS *pps = h->ps.pps; > > const ScalingList *scaling_list = NULL; > - int pic_param_size, err, i; > + int pic_param_size, num_comps, pre_palette_size, err, i; > > VAPictureParameterBufferHEVC *pic_param = > (VAPictureParameterBufferHEVC *)&pic->pic_param; > > @@ -245,8 +245,46 @@ static int vaapi_hevc_start_frame(AVCodecContext > *avctx, > for (i = 0; i < 6; i++) > pic->pic_param.rext.cr_qp_offset_list[i] = pps->cr_qp_offset_list[i]; > } > + > + pre_palette_size = pps->pps_palette_predictor_initializers_present_flag ? > + pps->pps_num_palette_predictor_initializers : > + (sps->sps_palette_predictor_initializers_present_flag ? > + sps->sps_num_palette_predictor_initializers_minus1 + 1 : > + 0); > + > + if (avctx->profile == FF_PROFILE_HEVC_SCC) { > + pic->pic_param.scc = (VAPictureParameterBufferHEVCScc) { > + .screen_content_pic_fields.bits = { > + .pps_curr_pic_ref_enabled_flag = pps- > >pps_curr_pic_ref_enabled_flag, > + .palette_mode_enabled_flag = sps- > >palette_mode_enabled_flag, > + .motion_vector_resolution_control_idc = sps- > >motion_vector_resolution_control_idc, > + .intra_boundary_filtering_disabled_flag = sps- > >intra_boundary_filtering_disabled_flag, > + .residual_adaptive_colour_transform_enabled_flag > + = pps- > >residual_adaptive_colour_transform_enabled_flag, > + .pps_slice_act_qp_offsets_present_flag = pps- > >pps_slice_act_qp_offsets_present_flag, > + }, > + .palette_max_size = sps->palette_max_size, > + .delta_palette_max_predictor_size = sps- > >delta_palette_max_predictor_size, > + .predictor_palette_size = pre_palette_size, > + .pps_act_y_qp_offset_plus5 = pps- > >residual_adaptive_colour_transform_enabled_flag ? > + pps->pps_act_y_qp_offset + 5 : 0, > + .pps_act_cb_qp_offset_plus5 = pps- > >residual_adaptive_colour_transform_enabled_flag ? > + pps->pps_act_cb_qp_offset + 5 : 0, > + .pps_act_cr_qp_offset_plus3 = pps- > >residual_adaptive_colour_transform_enabled_flag ? > + pps->pps_act_cr_qp_offset + 3 : 0, > + }; > + > + num_comps = pps->monochrome_palette_flag ? 1 : 3; > + for (int comp = 0; comp < num_comps; comp++) > + for (int j = 0; j < pre_palette_size; j++) > + pic->pic_param.scc.predictor_palette_entries[comp][j] = > + pps->pps_palette_predictor_initializers_present_flag ? > + pps->pps_palette_predictor_initializer[comp][j]: > + sps->sps_palette_predictor_initializer[comp][j]; > + } > + > #endif > - pic_param_size = avctx->profile == FF_PROFILE_HEVC_REXT ? > + pic_param_size = avctx->profile >= FF_PROFILE_HEVC_REXT ? > sizeof(pic->pic_param) : sizeof(VAPictureParameterBufferHEVC); > > err = ff_vaapi_decode_make_param_buffer(avctx, &pic->pic, @@ -299,7 > +337,7 @@ static int vaapi_hevc_end_frame(AVCodecContext *avctx) > VASliceParameterBufferHEVC *last_slice_param = > (VASliceParameterBufferHEVC *)&pic->last_slice_param; > int ret; > > - int slice_param_size = avctx->profile == FF_PROFILE_HEVC_REXT ? > + int slice_param_size = avctx->profile >= FF_PROFILE_HEVC_REXT ? > sizeof(pic->last_slice_param) : > sizeof(VASliceParameterBufferHEVC); > > if (pic->last_size) { > @@ -413,7 +451,7 @@ static int vaapi_hevc_decode_slice(AVCodecContext > *avctx, > VAAPIDecodePictureHEVC *pic = h->ref->hwaccel_picture_private; > VASliceParameterBufferHEVC *last_slice_param = > (VASliceParameterBufferHEVC *)&pic->last_slice_param; > > - int slice_param_size = avctx->profile == FF_PROFILE_HEVC_REXT ? > + int slice_param_size = avctx->profile >= FF_PROFILE_HEVC_REXT ? > sizeof(pic->last_slice_param) : > sizeof(VASliceParameterBufferHEVC); > > int nb_list = (sh->slice_type == HEVC_SLICE_B) ? > @@ -478,11 +516,15 @@ static int vaapi_hevc_decode_slice(AVCodecContext > *avctx, > fill_pred_weight_table(avctx, h, sh, last_slice_param); > > #if VA_CHECK_VERSION(1, 2, 0) > - if (avctx->profile == FF_PROFILE_HEVC_REXT) { > + if (avctx->profile >= FF_PROFILE_HEVC_REXT) { > pic->last_slice_param.rext = (VASliceParameterBufferHEVCRext) { > .slice_ext_flags.bits = { > .cu_chroma_qp_offset_enabled_flag = sh- > >cu_chroma_qp_offset_enabled_flag, > + .use_integer_mv_flag = sh->use_integer_mv_flag, > }, > + .slice_act_y_qp_offset = sh->slice_act_y_qp_offset, > + .slice_act_cb_qp_offset = sh->slice_act_cb_qp_offset, > + .slice_act_cr_qp_offset = sh->slice_act_cr_qp_offset, Hello, https://patchwork.ffmpeg.org/project/ffmpeg/patch/20230103125952.2707824-8-fei.w.wang@intel.com/ A new warning during build reported in patchwork, but didn't appear in my local build. Does anyone can help tell me how to reproduce this warning? Any special configuration or build environment needed? Thanks Fei > }; > for (i = 0; i < 15 && i < sh->nb_refs[L0]; i++) { > pic->last_slice_param.rext.luma_offset_l0[i] = sh->luma_offset_l0[i]; > -- > 2.25.1 _______________________________________________ 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:[~2023-01-11 2:45 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-03 12:59 [FFmpeg-devel] [PATCH v3 01/11] lavc/hevc_ps: remove profile limitation of pps_range_extensions() Fei Wang 2023-01-03 12:59 ` [FFmpeg-devel] [PATCH v3 02/11] lavc/avcodec: Add HEVC Screen Content Coding Extensions profile Fei Wang 2023-01-03 12:59 ` [FFmpeg-devel] [PATCH v3 03/11] lavc/hevc_ps: Add SPS/PPS parse support for HEVC extension syntax Fei Wang 2023-01-03 12:59 ` [FFmpeg-devel] [PATCH v3 04/11] lavc/hevcdec: Add slice parse support for HEVC SCC extension Fei Wang 2023-01-03 12:59 ` [FFmpeg-devel] [PATCH v3 05/11] lavc/hevcdec: Fix the parsing for use_integer_mv_flag Fei Wang 2023-01-03 12:59 ` [FFmpeg-devel] [PATCH v3 06/11] lavc/hevcdec: Set max_num_merge_cand to uint8_t Fei Wang 2023-01-03 12:59 ` [FFmpeg-devel] [PATCH v3 07/11] lavc/hevc: Update reference list for SCC Fei Wang 2023-01-03 12:59 ` [FFmpeg-devel] [PATCH v3 08/11] lavc/vaapi_hevc: Pass SCC parameters Through VA-API Fei Wang 2023-01-11 2:45 ` Wang, Fei W [this message] 2023-01-03 12:59 ` [FFmpeg-devel] [PATCH v3 09/11] lavc/vaapi_hevc: Add vaapi profile parse support for SCC Fei Wang 2023-01-03 12:59 ` [FFmpeg-devel] [PATCH v3 10/11] lavc/vaapi_hevc: Set correct rps type for scc Fei Wang 2023-01-11 2:37 ` Wang, Fei W 2023-01-03 12:59 ` [FFmpeg-devel] [PATCH v3 11/11] lavc/vaapi_hevc: Loose the restricts for SCC decoding Fei Wang
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=PH0PR11MB5030787A08DD4F8BE2F61858CDFC9@PH0PR11MB5030.namprd11.prod.outlook.com \ --to=fei.w.wang-at-intel.com@ffmpeg.org \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=linjie.fu@intel.com \ --cc=linjie.justin.fu@gmail.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