On 6/26/2020 1:58 PM, Paul B Mahol wrote: > On 6/26/20, James Almer <jamr...@gmail.com> wrote: >> On 6/26/2020 1:13 PM, Paul B Mahol wrote: >>> On 6/26/20, Paul B Mahol <one...@gmail.com> wrote: >>>> On 6/24/20, Paul B Mahol <one...@gmail.com> wrote: >>>>> Signed-off-by: Paul B Mahol <one...@gmail.com> >>>>> --- >>>>> Please test it and reports benchmark results on non toyish GPUs. >>>> >>>> Please, I really need it! >>>> >>> >>> >>> Why nobody wants to help? >>> >>> This makes me really really sad. >> >> I can try. Can you give an example command line with a publicly >> available sample? > > You can use any sample, samples are irrelevant. just report resolution used. > Also compare with CPU solution with just v360 filter. > > For yuv420p inputs: > > ffmpeg -init_hw_device vulkan=vulkan -i INPUT -filter_hw_device vulkan > -vf > hwupload,v360_vulkan=fisheye:e:ih_fov=180:iv_fov=180:w=2048:h=1024,hwdownload,format=yuv420p > -f null - > > ffmpeg -i INPUT -vf v360=fisheye:e:ih_fov=180:iv_fov=180:w=2048:h=1024 -f > null - > > Just make sure that you get same output resolution in both cases. If > not, adjust w/h accordingly.
I'm getting a segfault on vkGetInstanceProcAddr, and i don't know if it's your filter or some issue in the driver. gdb is not being helpful. _______________________________________________ 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".
