From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 1/7] avcodec/h263dec: Remove redundant code to set cur_pic_ptr Date: Tue, 16 Aug 2022 00:21:50 +0200 Message-ID: <20220815222150.GW2088045@pb2> (raw) In-Reply-To: <HE1PR0101MB2219AAC54B7B6A6758AD8A898F689@HE1PR0101MB2219.eurprd01.prod.exchangelabs.com> [-- Attachment #1.1: Type: text/plain, Size: 2000 bytes --] On Mon, Aug 15, 2022 at 01:49:24PM +0200, Andreas Rheinhardt wrote: > It is done later in ff_mpv_frame_start() (and nobody uses > current_picture_ptr between setting it in ff_mpv_frame_start()). > > (The reason the vsynth*-h263-obmc code changes is because > the call to ff_find_unused_picture() now happens after the older > pictures have been unreferenced in ff_mpv_frame_start(), > so that their slots in the picture array can be immediately > reused; the obmc code is somehow buggy and changes its output > depending on the earlier contents of the motion_val buffer.) > > Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com> > --- > I'd like to take this opportunity to once again ask anyone familiar > with H.263 to take a look at this OBMC issue. Iam too busy ATM :( i might look at some point but its not very high on my todo as it works :) security & release is more important but i can say this breaks fate as it is: --- ./tests/ref/vsynth/vsynth1-h263-obmc 2022-08-16 00:19:00.345967181 +0200 +++ tests/data/fate/vsynth1-h263-obmc 2022-08-16 00:19:05.262017999 +0200 @@ -1,4 +1,4 @@ 7dec64380f375e5118b66f3baaaa1e24 *tests/data/fate/vsynth1-h263-obmc.avi 657320 tests/data/fate/vsynth1-h263-obmc.avi -f5048b5f0c98833a1d11f8034fb1827f *tests/data/fate/vsynth1-h263-obmc.out.rawvideo -stddev: 8.12 PSNR: 29.93 MAXDIFF: 113 bytes: 7603200/ 7603200 +2a69f6b37378aa34418dfd04ec98c1c8 *tests/data/fate/vsynth1-h263-obmc.out.rawvideo +stddev: 8.38 PSNR: 29.66 MAXDIFF: 116 bytes: 7603200/ 7603200 Test vsynth1-h263-obmc failed. Look at tests/data/fate/vsynth1-h263-obmc.err for details. tests/Makefile:304: recipe for target 'fate-vsynth1-h263-obmc' failed make: *** [fate-vsynth1-h263-obmc] Error 1 [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Does the universe only have a finite lifespan? No, its going to go on forever, its just that you wont like living in it. -- Hiranya Peiri [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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-15 22:22 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-15 11:49 Andreas Rheinhardt 2022-08-15 11:52 ` [FFmpeg-devel] [PATCH 2/7] avcodec/h263dec: Don't set frame parameters redundantly Andreas Rheinhardt 2022-08-15 11:52 ` [FFmpeg-devel] [PATCH 3/7] avcodec/mpegpicture: Reset fields explicitly instead of memsetting them Andreas Rheinhardt 2022-08-15 11:52 ` [FFmpeg-devel] [PATCH 4/7] avcodec/mpegvideo_dec: Remove commented-out cruft Andreas Rheinhardt 2022-08-15 11:52 ` [FFmpeg-devel] [PATCH 5/7] avcodec/get_buffer: Don't get AVPixFmtDescriptor unnecessarily Andreas Rheinhardt 2022-08-15 11:52 ` [FFmpeg-devel] [PATCH 6/7] avcodec/ffv1enc: Don't create and keep unnecessary reference Andreas Rheinhardt 2022-08-15 11:52 ` [FFmpeg-devel] [PATCH 7/7] avcodec/ffv1enc: Remove redundant wrapper Andreas Rheinhardt 2022-08-15 22:21 ` Michael Niedermayer [this message] 2022-08-16 7:08 ` [FFmpeg-devel] [PATCH 1/7] avcodec/h263dec: Remove redundant code to set cur_pic_ptr Andreas Rheinhardt 2022-08-17 22:05 ` Andreas Rheinhardt
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=20220815222150.GW2088045@pb2 \ --to=michael@niedermayer.cc \ --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