From: Nuo Mi <nuomi2021@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v2 00/16] avcodec/vvcdec: support subpicture Date: Thu, 4 Apr 2024 10:05:00 +0800 Message-ID: <CAFXK13dTt0AALGo0hbct1h0dD3O6XQMg9BDR-+OOrZnnCDRJ7w@mail.gmail.com> (raw) In-Reply-To: <7e8d29fc-4774-43f1-8186-c8d20cd1f4c3@gmail.com> On Tue, Apr 2, 2024 at 11:24 PM James Almer <jamrial@gmail.com> wrote: > On 4/2/2024 10:01 AM, Nuo Mi wrote: > > On Wed, Mar 27, 2024 at 9:01 PM Nuo Mi <nuomi2021@gmail.com> wrote: > > > >> Changes since v1: > >> add v2-0004-avcodec-vvcdec-fix-uninitialized-last-element-of-.patch to > >> address > >> the clang-usan and clang-asan failures reported by Frank > > > > > > pushed. > > I added a test for this using SUBPIC_C_ERICSSON_1.bit > Also, i disabled the tests for OPI_B_3.bit and VPS_A_3.bit as they rely > on a non-implemented feature. And while they still output a frame or two > as is, it's not the case on all systems. > Thank you. > > There's not a lot of VVC bitstreams currently in the FATE suite, so if > you know of any that will increase the coverage (See for example > > http://coverage.ffmpeg.org/index.vvc_intra.c.5d0b519a39871515a1754ee8847b6d69.html#l678, > > where vvc_predict_ibc() is never run), then please make a test for it > and I'll upload the sample. > Sure. Tracked with https://github.com/ffvvc/FFmpeg/issues/206 > _______________________________________________ > 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:[~2024-04-04 2:05 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-27 13:00 Nuo Mi 2024-04-02 13:01 ` Nuo Mi 2024-04-02 15:24 ` James Almer 2024-04-04 2:05 ` Nuo Mi [this message] 2024-04-04 2:09 ` James Almer 2024-04-04 3:12 ` Nuo Mi 2024-04-04 3:26 ` James Almer
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=CAFXK13dTt0AALGo0hbct1h0dD3O6XQMg9BDR-+OOrZnnCDRJ7w@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