From: Nuo Mi <nuomi2021@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/8] cbs_h266: fix inference for sh_lmcs_used_flag and sh_explicit_scaling_list_used_flag
Date: Mon, 7 Aug 2023 23:47:18 +0800
Message-ID: <CAFXK13fib2HygSyk9Z7Czb-p2qzt_1jWtU8g62x926oPzS0Cew@mail.gmail.com> (raw)
In-Reply-To: <e3921820-dd38-2dba-4036-106783e9030d@gmail.com>
On Mon, Aug 7, 2023 at 11:17 PM James Almer <jamrial@gmail.com> wrote:
> On 8/7/2023 11:55 AM, Nuo Mi wrote:
> > if sh_picture_header_in_slice_header_flag is true
> > sh_lmcs_used_flag and sh_explicit_scaling_list_used_flag are infered
> from ph
> > ---
> > libavcodec/cbs_h266_syntax_template.c | 24 ++++++++++++++----------
> > 1 file changed, 14 insertions(+), 10 deletions(-)
> >
> > diff --git a/libavcodec/cbs_h266_syntax_template.c
> b/libavcodec/cbs_h266_syntax_template.c
> > index 98a8e033bf..857882655b 100644
> > --- a/libavcodec/cbs_h266_syntax_template.c
> > +++ b/libavcodec/cbs_h266_syntax_template.c
> > @@ -3151,17 +3151,21 @@ static int FUNC(slice_header)
> (CodedBitstreamContext *ctx, RWContext *rw,
> > infer(sh_alf_enabled_flag, 0);
> > }
> >
> > - if (ph->ph_lmcs_enabled_flag &&
> > - !current->sh_picture_header_in_slice_header_flag)
> > - flag(sh_lmcs_used_flag);
> > - else
> > - infer(sh_lmcs_used_flag, 0);
> > + if (current->sh_picture_header_in_slice_header_flag) {
> > + infer(sh_lmcs_used_flag, ph->ph_lmcs_enabled_flag);
> > + infer(sh_explicit_scaling_list_used_flag,
> > + ph->ph_explicit_scaling_list_enabled_flag);
> > + } else {
> > + if (ph->ph_lmcs_enabled_flag)
> > + flag(sh_lmcs_used_flag);
> > + else
> > + infer(sh_lmcs_used_flag, 0);
> >
> > - if (ph->ph_explicit_scaling_list_enabled_flag &&
> > - !current->sh_picture_header_in_slice_header_flag)
> > - flag(sh_explicit_scaling_list_used_flag);
> > - else
> > - infer(sh_explicit_scaling_list_used_flag, 0);
> > + if (ph->ph_explicit_scaling_list_enabled_flag)
> > + flag(sh_explicit_scaling_list_used_flag);
> > + else
> > + infer(sh_explicit_scaling_list_used_flag, 0);
> > + }
> >
> > if (!pps->pps_rpl_info_in_ph_flag &&
> > ((nal_unit_type != VVC_IDR_W_RADL &&
>
> Do you know which samples from the conformance suite exercise this, and
> patches 2 and 3?
>
Thank you for the review
Good idea. will send out v2 and add a clips list
> _______________________________________________
> 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".
>
_______________________________________________
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-08-07 15:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 14:55 Nuo Mi
2023-08-07 15:17 ` James Almer
2023-08-07 15:47 ` Nuo Mi [this message]
2023-08-08 10:58 ` [FFmpeg-devel] [PATCH v2 " Nuo Mi
2023-08-17 13:38 ` James Almer
[not found] ` <20230808105903.6667-1-nuomi2021@gmail.com>
2023-08-08 10:58 ` [FFmpeg-devel] [PATCH v2 2/8] cbs_h266: fix inference for sh_alf_enabled_flag Nuo Mi
2023-08-08 10:58 ` [FFmpeg-devel] [PATCH v2 3/8] cbs_h266: fix inference for xh_deblocking_filter_disabled_flag Nuo Mi
2023-08-08 10:58 ` [FFmpeg-devel] [PATCH v2 4/8] cbs_h266: fix slice_height_in_ctus for single slice tile Nuo Mi
2023-08-08 10:59 ` [FFmpeg-devel] [PATCH v2 5/8] cbs_h266: H266RawSliceHeader, expose NumEntryPoints Nuo Mi
2023-08-08 10:59 ` [FFmpeg-devel] [PATCH v2 6/8] cbs_h266: H266RawPredWeightTable, expose num_weights_l0 and num_weights_l1 Nuo Mi
2023-08-08 10:59 ` [FFmpeg-devel] [PATCH v2 7/8] cbs_h266: H266RawSliceHeader, expose NumRefIdxActive[] Nuo Mi
2023-08-08 10:59 ` [FFmpeg-devel] [PATCH v2 8/8] cbs_h266: slice_header, fix inference for pred_weight_table Nuo Mi
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=CAFXK13fib2HygSyk9Z7Czb-p2qzt_1jWtU8g62x926oPzS0Cew@mail.gmail.com \
--to=nuomi2021@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