>I believe that filters are not
accelerated even with standalone ffmpeg
Some filters of standalone ffmpeg are hardware accelerated without vulkan.
but for using them programmatically in cingg we need pass around hw device handle, and do manual format/hwupload/filter/hwdownload/format dance, because otherwise libavcodec does not know where we want to filter, and negotiation between different hw formats does not exist yet (?)
As you saw Paul said his lavfi-preview does not support this, may be OBS does support?
I enabled opencl/vulkan filters in my build especially for testing this, but so far no working solution found, with my weak understanding of both C++ and ffmpeg functions.
Yes, hw acceleration currently for playback-only, and on render you can select hw encoder, but data will roundtrip via system memory (and pcie bus for discrete GPUs)
> We have problem on input side, where hw decoding does not cooperate with filters ....
Maybe I didn't understand the problem: I thought that Hw acceleration
in timeline is only about playback. I believe that filters are not
accelerated even with standalone ffmpeg. In fact, there are few
filters built specifically for vulkan; are these the ones that don't
work for you?
During my tests I had managed to compile CinGG with the filters for
vulkan (it seems to me with a simple: “export FFMPEG_EXTRA_CFG=
--enable-vulkan”), but these did not work due to the classic errors
("input/Output error", "invalid argument", etc).
PS: among other tests, I failed to compile opencv (system) and opencl.
I have yet to try frei0r, lensfun and lcms2...
--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin