From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH] avcodec/vpx_rac: Adjust vpx_rac_is_end) threshold Date: Mon, 29 Aug 2022 17:29:03 +0200 Message-ID: <AS8P250MB0744C0402B7FA4B1B3B1AF958F769@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM> (raw) In-Reply-To: <20220828172545.8185-1-michael@niedermayer.cc> Michael Niedermayer: > A threshold of 180 is needed and sufficient for the sample, twice this is used to > cover potentially worse samples > > fate/vp5 changes as the sample file is truncated and the damaged part is handled > differently > > Fixes: ticket #9754 > > Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> > --- > libavcodec/vpx_rac.h | 2 +- > tests/ref/fate/vp5 | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/libavcodec/vpx_rac.h b/libavcodec/vpx_rac.h > index b158cc0754..2f5486f501 100644 > --- a/libavcodec/vpx_rac.h > +++ b/libavcodec/vpx_rac.h > @@ -52,7 +52,7 @@ static av_always_inline int vpx_rac_is_end(VPXRangeCoder *c) > { > if (c->end <= c->buffer && c->bits >= 0) > c->end_reached ++; > - return c->end_reached > 10; > + return c->end_reached > 360; Is the file from #9754 defective? Or is it our decoder that is overcautious? Your commit message sounds as if it were the latter. Is it guaranteed that is now enough for all spec-compliant samples? Does the answer depend upon the codec? (vpx_rac_is_end() is shared between several VPx codecs.); I presume you can't give any guarantees. > } > > static av_always_inline unsigned int vpx_rac_renorm(VPXRangeCoder *c) > diff --git a/tests/ref/fate/vp5 b/tests/ref/fate/vp5 > index 09ebe62b25..2116fb9b81 100644 > --- a/tests/ref/fate/vp5 > +++ b/tests/ref/fate/vp5 > @@ -249,4 +249,4 @@ > 0, 243, 243, 1, 233472, 0x6f530ac6 > 0, 244, 244, 1, 233472, 0x94f7466c > 0, 245, 245, 1, 233472, 0xa8c1d365 > -0, 246, 246, 1, 233472, 0x4f3ef38c > +0, 246, 246, 1, 233472, 0xedcff050 _______________________________________________ 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:[~2022-08-29 15:29 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-28 17:25 Michael Niedermayer 2022-08-29 15:29 ` Andreas Rheinhardt [this message] 2022-08-29 22:48 ` Michael Niedermayer
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=AS8P250MB0744C0402B7FA4B1B3B1AF958F769@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM \ --to=andreas.rheinhardt@outlook.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