After further testing it seems that it only works reliable with HEVC video, on my machine :( But for hevc it really speeds things up :) second patch adds tooltip for Vulkan decoding, and changes pixel_format for more common for those hwaccels, hopefully. On Wed, May 7, 2025 at 3:49 AM Andrew Randrianasulu <randrianasulu@gmail.com> wrote:
Now non-tonemapped 4k h264 hit 56 fps in window :)
Checked into GIT after building and displaying on Fedora 32. Should be OK on Ubuntu 16 also. On Tue, May 6, 2025 at 11:31 PM Andrew Randrianasulu < randrianasulu@gmail.com> wrote:
After further testing it seems that it only works reliable with HEVC video, on my machine :(
But for hevc it really speeds things up :)
second patch adds tooltip for Vulkan decoding, and changes pixel_format for more common for those hwaccels, hopefully.
On Wed, May 7, 2025 at 3:49 AM Andrew Randrianasulu <randrianasulu@gmail.com> wrote:
Now non-tonemapped 4k h264 hit 56 fps in window :)
Thank you, just these days I'm testing with the “configure” flags; your patches happen right. In CinHV, Adam had put an option in the rendering window to write an ffmpeg command directly, without going through presets. An option that opens you a terminal (or a simple input window, as Adam did), makes you use external ffmpeg, and then the result falls back into the rendering window configuration would not be bad. This would get around the problem with the filter graph and using multiple streams that prevent some plugins from working. Do you think this is possible by copying Adam's commit?
пт, 9 мая 2025 г., 10:51 Andrea paz <gamberucci.andrea@gmail.com>:
Thank you, just these days I'm testing with the “configure” flags; your patches happen right. In CinHV, Adam had put an option in the rendering window to write an ffmpeg command directly, without going through presets.
This is for output side, no? We have problem on input side, where hw decoding does not cooperate with filters .... In theory you can use out-of-tree v4loopback module, and make ffmpeg process video and *output* to v4loopback device, from where our (8 bpc) input takes it ... May be using this as reason we even can request from v4l devs to extend it for 10/12 bit and different subsample formats, if they not already. But I suspect nowadays most work there done by paid contractors, on request of larger companies. So hobby proj like ours will have low standing .... An option that
opens you a terminal (or a simple input window, as Adam did), makes you use external ffmpeg, and then the result falls back into the rendering window configuration would not be bad.
Isn't there sort of Command Execution built already into cingg? I mean sending multiple assets as arguments to external command ... Ah, no, it for RenderMux.sh/output ... btw I think our script delete_brender_files fails to install for single user .... something to quick fix! This would get around
the problem with the filter graph and using multiple streams that prevent some plugins from working. Do you think this is possible by copying Adam's commit?
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...
I believe that filters are not accelerated even with standalone ffmpeg
Some filters of standalone ffmpeg are hardware accelerated without vulkan. Best regards, Andrey пт, 9 мая 2025 г., 15:59 Andrea paz via Cin <cin@lists.cinelerra-gg.org>:
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
пт, 9 мая 2025 г., 16:02 Андрей Спицын via Cin <cin@lists.cinelerra-gg.org>:
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)
Best regards, Andrey
пт, 9 мая 2025 г., 15:59 Andrea paz via Cin <cin@lists.cinelerra-gg.org>:
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
participants (4)
-
Andrea paz -
Andrew Randrianasulu -
Phyllis Smith -
Андрей Спицын