From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] lavc/vvc: Correct sps_num_subpics_minus1 minimum Date: Sun, 25 Feb 2024 16:50:51 -0300 Message-ID: <f7981c5b-4e1c-41e6-a475-496b98fd1c06@gmail.com> (raw) In-Reply-To: <20240225175101.1252-1-post@frankplowman.com> On 2/25/2024 2:51 PM, Frank Plowman wrote: > The spec says "the value of sps_num_subpics_minus1 shall be in the > range of 0 to MaxSlicesPerAu − 1, inclusive." > > Signed-off-by: Frank Plowman <post@frankplowman.com> > --- > libavcodec/cbs_h266_syntax_template.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/libavcodec/cbs_h266_syntax_template.c b/libavcodec/cbs_h266_syntax_template.c > index 26ee7a420b..1d4d0c796f 100644 > --- a/libavcodec/cbs_h266_syntax_template.c > +++ b/libavcodec/cbs_h266_syntax_template.c > @@ -1130,7 +1130,7 @@ static int FUNC(sps)(CodedBitstreamContext *ctx, RWContext *rw, > > flag(sps_subpic_info_present_flag); > if (current->sps_subpic_info_present_flag) { > - ue(sps_num_subpics_minus1, 1, VVC_MAX_SLICES - 1); > + ue(sps_num_subpics_minus1, 0, VVC_MAX_SLICES - 1); Strictly speaking, MaxSlicesPerAu varies depending on the stream's general_level_idc value, listed in table A.2 from Annex-A (in ITU-T H.266 V3). Right now, VVC_MAX_SLICES is defined as 600 in vvc.h, but the max value in the spec is 1000, from level 6.3. I assume it was added in V3? > if (current->sps_num_subpics_minus1 > 0) { > flag(sps_independent_subpics_flag); > flag(sps_subpic_same_size_flag); _______________________________________________ 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:[~2024-02-25 19:50 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-25 17:51 Frank Plowman 2024-02-25 19:50 ` James Almer [this message] 2024-02-25 21:20 ` Frank Plowman 2024-02-27 6:08 ` 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=f7981c5b-4e1c-41e6-a475-496b98fd1c06@gmail.com \ --to=jamrial@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