From: Paul B Mahol <onemda@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] lavfi/bwdif: remove interpolated sample clipping Date: Sun, 2 Jul 2023 21:45:23 +0200 Message-ID: <CAPYw7P4UH8qZEVGb7HVz0U4EK1g=wYHZDufLF-xZwCe09kwLcA@mail.gmail.com> (raw) In-Reply-To: <NZN0_qH--3-9@lynne.ee> On Sun, Jul 2, 2023 at 9:13 PM Lynne <dev@lynne.ee> wrote: > Jul 2, 2023, 20:48 by onemda@gmail.com: > > > On Sun, Jul 2, 2023 at 6:57 PM Lynne <dev@lynne.ee> wrote: > > > >> Jul 2, 2023, 18:54 by dev@lynne.ee: > >> > >> > The issue is that clipping the interpolated temporal sample against > >> > the spatially predicted sample causes artifacts to appear. > >> > > >> > Discovered while writing the Vulkan version (where I omitted the > >> > same check). > >> > > >> > The clipping in the code is carried over from yadif. Removing the > >> > same code in yadif does not make any difference to the output. > >> > I think that the check was simply ill-adapted to the new prediction > >> > code and does more harm. > >> > > >> > I tested replacing the range clip with only an FFMAX, and only an > >> > FFMIN, but in both cases, artifacts still appeared. > >> > > >> > Test sample 1: > >> https://files.lynne.ee/testsamples/mbaff_1080i60_idx.mkvTest sample 2: > >> https://files.lynne.ee/testsamples/mbaff_bdmv_1080i60_8slice.mkv > >> > > >> > Command line: > >> > ./ffmpeg_g -cpuflags 0 -i <INPUT> -vf bwdif=mode=send_field -c:v > >> rawvideo -y <OUTPUT>.nut > >> > Make sure to disable the assembly. > >> > > >> > Comparisons: > >> > https://files.lynne.ee/bwdif_01_before.png > >> > https://files.lynne.ee/bwdif_01_after.png > >> > Generated from sample 1 via: > >> > ffmpeg -ss 00:00:00.184 -i <INPUT>.nut -vf > >> crop=w=420:h=240:x=700:y=300,scale=iw*2:ih*2 -y <OUTPUT>.png > >> > > >> > https://files.lynne.ee/bwdif_02_before.png > >> > https://files.lynne.ee/bwdif_02_after.pngffmpeg -ss 00:00:00.417 -i > >> <INPUT>.nut -vf crop=w=420:h=240:x=1100:y=200,scale=iw*2:ih*2 -y > >> <OUTPUT>.png > >> > > >> > >> Corrected links for the second sample: > >> > >> https://files.lynne.ee/bwdif_02_before.png > >> https://files.lynne.ee/bwdif_02_after.png > >> ffmpeg -ss 00:00:00.417 -i <INPUT>.nut -vf > >> crop=w=420:h=240:x=1100:y=200,scale=iw*2:ih*2 -y <OUTPUT>.png > >> > >> I'm sure I hit a newline. The artifacts are a lot more noticeable in the > >> second sample. > >> > > > > Single png images are not way to prove something. > > > > Please provide videos and not just single file that exhibit this issue. > > (Keep showing same file over and over is not going to help show that it > > helps) > > > > Also how PSNR/SSIM/VMAF changes before after not just in single sample > but > > in more samples. > > > > I posted samples and instructions. Enough for a discussion. > I'm not posting gigabytes of uncompressed samples. > PSNR is irrelevant if there are visible artifacts. > Nope, you havent. Some strange samples. PSNR is relevant as also SSIM and VMAF. Ignoring this does not help project, but just force tyrannic behavior. _______________________________________________ > 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:[~2023-07-02 19:38 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-02 16:54 Lynne [not found] ` <NZMWg6Y--3-9@lynne.ee-NZMWj_0----9> 2023-07-02 16:57 ` Lynne 2023-07-02 18:41 ` Thomas Mundt 2023-07-02 18:55 ` Paul B Mahol 2023-07-02 19:13 ` Lynne 2023-07-02 19:45 ` Paul B Mahol [this message] 2023-07-02 20:25 ` Lynne 2023-07-02 20:39 ` Paul B Mahol [not found] ` <CAC5+Sy4g=WqbbavyrLQOBMz+aWJK-sMzc1rebVdi-Y2EUNKjoA@mail.gmail.com-NZMuHBT----9> 2023-07-02 18:58 ` Lynne 2023-07-03 22:11 ` Thomas Mundt 2023-07-03 22:54 ` Lynne 2023-07-03 23:21 ` Thomas Mundt
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='CAPYw7P4UH8qZEVGb7HVz0U4EK1g=wYHZDufLF-xZwCe09kwLcA@mail.gmail.com' \ --to=onemda@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