From: Nuo Mi <nuomi2021@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 2/2] lavc/vvc: Fix pps_single_slice_picture Date: Sun, 2 Mar 2025 20:03:36 +0800 Message-ID: <CAFXK13e89VfaQ9g84ua4Ke10S4pX+nkNq+uif+bvLmQJXC7qDQ@mail.gmail.com> (raw) In-Reply-To: <e5e679f0-2997-44d1-8e6c-0f1d129f29ba@frankplowman.com> On Tue, Feb 25, 2025 at 3:16 AM Frank Plowman <post@frankplowman.com> wrote: > On 24/02/2025 02:23, James Almer wrote: > > On 2/23/2025 9:04 AM, Frank Plowman wrote: > >> Signed-off-by: Frank Plowman <post@frankplowman.com> > >> --- > >> libavcodec/vvc/ps.c | 3 ++- > >> 1 file changed, 2 insertions(+), 1 deletion(-) > >> > >> diff --git a/libavcodec/vvc/ps.c b/libavcodec/vvc/ps.c > >> index fae6655cc0..603a6d42d1 100644 > >> --- a/libavcodec/vvc/ps.c > >> +++ b/libavcodec/vvc/ps.c > >> @@ -368,9 +368,10 @@ static int pps_add_ctus(VVCPPS *pps, int *off, > const int rx, const int ry, > >> > >> static void pps_single_slice_picture(VVCPPS *pps, int *off) > >> { > >> + pps->num_ctus_in_slice[0] = 0; > >> for (int j = 0; j < pps->r->num_tile_rows; j++) { > >> for (int i = 0; i < pps->r->num_tile_columns; i++) { > >> - pps->num_ctus_in_slice[0] = pps_add_ctus(pps, off, > >> + pps->num_ctus_in_slice[0] += pps_add_ctus(pps, off, > >> pps->col_bd[i], pps->row_bd[j], > >> pps->r->col_width_val[i], pps->r->row_height_val[j]); > >> } > > > > Is there a sample in the conformance suite this fixes? Or one we can > > upload to FATE to make a test. > > Hi James, > > The conformance suite is pretty lacking here considering the number of > combinations of these different partitioning tools possible in VVC. > I think the lack of examples in the conformance suite is the main reason > we're still running into bugs in this area. > > I crafted a sample which exhibits this bug though, and have sent it to > samples-request@ffmpeg.org. I tried to also craft a sample which tests > 93aae172ea909ec96b67077b8b3005886a83d0ae, but any attempt at this seemed > to segfault the reference software :) > Creating error-prone conformance streams is challenging; some companies sell them at a high price > > -- > All the best, > Frank > > _______________________________________________ > 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:[~2025-03-02 12:04 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-02-23 12:04 [FFmpeg-devel] [PATCH 1/2] lavc/vvc: Fix NumEntryPoints derivation Frank Plowman 2025-02-23 12:04 ` [FFmpeg-devel] [PATCH 2/2] lavc/vvc: Fix pps_single_slice_picture Frank Plowman 2025-02-24 2:23 ` James Almer 2025-02-24 19:16 ` Frank Plowman 2025-03-02 12:03 ` Nuo Mi [this message] 2025-03-02 12:49 ` Nuo Mi 2025-03-02 12:41 ` [FFmpeg-devel] [PATCH 1/2] lavc/vvc: Fix NumEntryPoints derivation 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=CAFXK13e89VfaQ9g84ua4Ke10S4pX+nkNq+uif+bvLmQJXC7qDQ@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