On 10/01/2020 21:05, Lynne wrote: > From 1e3a50fbe4399f76c0ab0f62bf6d6c65b8565db4 Mon Sep 17 00:00:00 2001 > From: Lynne <d...@lynne.ee> > Date: Sun, 27 Oct 2019 14:47:18 +0000 > Subject: [PATCH 7/9] lavfi: add an avgblur_vulkan filter > > This commit adds a fast avgblur Vulkan filter. > This will reset Intel GPUs on Windows due to a known, year-old driver bug. > --- > configure | 1 + > libavfilter/Makefile | 1 + > libavfilter/allfilters.c | 1 + > libavfilter/vf_avgblur_vulkan.c | 406 ++++++++++++++++++++++++++++++++ > 4 files changed, 409 insertions(+) > create mode 100644 libavfilter/vf_avgblur_vulkan.c
There is something weirdly wrong with the edges of the local blocks here. With a pure white input: ./ffmpeg_g -v 55 -y -init_hw_device vulkan:0,debug=1 -i white.png -filter_hw_device vulkan0 -vf format=yuv420p,hwupload,avgblur_vulkan,hwdownload,format=yuv420p -frames:v 1 out.png <http://ixia.jkqxz.net/~mrt/f242fc36ea7ed26c8809fe442e8e67df/out.png> Looks like undefined values are leaking in to the average? 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-requ...@ffmpeg.org with subject "unsubscribe".
