From: David Rosca <nowrep@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] lavc/vaapi_h264: Fix merging fields in DPB with missing references Date: Wed, 8 May 2024 17:43:39 +0200 Message-ID: <CAM7PDoiRqcYyP3x6P0WY5m_DVMN2-AmKsKSemNnGbh71Z4P0UA@mail.gmail.com> (raw) In-Reply-To: <ede8a042-ee9a-4bfa-9293-2a5f75d14197@jkqxz.net> On Tue, May 7, 2024 at 10:22 PM Mark Thompson <sw@jkqxz.net> wrote: > > On 07/05/2024 07:00, David Rosca wrote: > > If there are missing references, h264 decode does error concealment > > by copying previous refs which means there will be duplicated surfaces > > and this code would try to merge them instead of correctly appending > > to DPB. Make sure the fields were actually merged before early return. > > --- > > libavcodec/vaapi_h264.c | 3 ++- > > 1 file changed, 2 insertions(+), 1 deletion(-) > > > > diff --git a/libavcodec/vaapi_h264.c b/libavcodec/vaapi_h264.c > > index b47531ce1c..c62a320e97 100644 > > --- a/libavcodec/vaapi_h264.c > > +++ b/libavcodec/vaapi_h264.c > > @@ -112,8 +112,9 @@ static int dpb_add(DPB *dpb, const H264Picture *pic) > > } else { > > va_pic->BottomFieldOrderCnt = temp_va_pic.BottomFieldOrderCnt; > > } > > + return 0; > > } > > - return 0; > > + break; > > } > > } > > > > I agree that the old code did nasty things, but can you explain a bit more about the reasoning for what you've got now? > > I'm thinking that given duplication a top field could appear twice, so you'd want to merge twice if you have the matching bottom field. Right, that may be possible. Also I've looked at vdpau code and there it checks frame_num (in addition to surface) when searching for the other field, which seems better to avoid trying to merge when it should not. Posted v2 with this change + multiple merge. Thanks, David > > Thanks, > > - Mark > _______________________________________________ > 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".
prev parent reply other threads:[~2024-05-08 15:44 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-05-07 6:00 David Rosca 2024-05-07 20:22 ` Mark Thompson 2024-05-08 15:43 ` David Rosca [this message]
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=CAM7PDoiRqcYyP3x6P0WY5m_DVMN2-AmKsKSemNnGbh71Z4P0UA@mail.gmail.com \ --to=nowrep@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