From: Lynne <dev@lynne.ee> To: Ffmpeg Devel <ffmpeg-devel@ffmpeg.org> Subject: [FFmpeg-devel] [PATCH] bwdif_vulkan: fix artifacts on vulkan decode images Date: Sun, 29 Oct 2023 07:22:46 +0100 (CET) Message-ID: <Nhu5LC2--3-9@lynne.ee> (raw) [-- Attachment #1: Type: text/plain, Size: 237 bytes --] Due to making the decode frames context use the coded size, the filter started to display those artifacts as it reused the input frame's size. Change it to instead output the real image size for images, not the input. Patch attached. [-- Attachment #2: 0001-bwdif_vulkan-fix-artifacts-on-vulkan-decode-images.patch --] [-- Type: text/x-diff, Size: 1065 bytes --] From 93d0b1012012b1a1a8d0701f9c78e4a1a9502d29 Mon Sep 17 00:00:00 2001 From: Lynne <dev@lynne.ee> Date: Sun, 29 Oct 2023 07:19:25 +0100 Subject: [PATCH] bwdif_vulkan: fix artifacts on vulkan decode images Due to making the decode frames context use the coded size, the filter started to display those artifacts as it reused the input frame's size. Change it to instead output the real image size for images, not the input. --- libavfilter/vf_bwdif_vulkan.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/libavfilter/vf_bwdif_vulkan.c b/libavfilter/vf_bwdif_vulkan.c index f1623e6ef7..690a89c4ba 100644 --- a/libavfilter/vf_bwdif_vulkan.c +++ b/libavfilter/vf_bwdif_vulkan.c @@ -325,8 +325,8 @@ static int bwdif_vulkan_config_input(AVFilterLink *inlink) /* Defaults */ vkctx->output_format = input_frames->sw_format; - vkctx->output_width = input_frames->width; - vkctx->output_height = input_frames->height; + vkctx->output_width = inlink->w; + vkctx->output_height = inlink->h; return 0; } -- 2.42.0 [-- Attachment #3: 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 reply other threads:[~2023-10-29 6:22 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-29 6:22 Lynne [this message] 2023-11-05 5:02 ` Philip Langdale via ffmpeg-devel
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=Nhu5LC2--3-9@lynne.ee \ --to=dev@lynne.ee \ --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