вс, 11 авг. 2024 г., 23:06 Phyllis Smith via Cin <cin@lists.cinelerra-gg.org>:

From reading Lynne's note, it seems like the ffmpeg team will be merging Vulcan into ffmpeg eventually. But if I remember correctly, it was Vulcan that was delaying release of version 6.0 so it may be awhile. Would it not make more sense to develop a patchset from Lynne's work rather than pull ffmpeg from their repository? That repository probably is not just 7.0, but more mods in it? Not sure.

https://github.com/cyanreg/FFmpeg/tree/vulkan

I think it more like 7.0+git , description says it 35 commits ahead of ffmpeg git snapshot that by itself 185 commits behind current ffmpeg.git head ?

May be if we interested in encoding part of it just try to build this tree standalone and pipe y4m to its ffmpeg binary?

Or pretend we have "7.1" already by packaging this git branch into tarball named like release, putting it in thirdparty/src, patching our configure.ac then see failures from API changes ? :)

On Sun, Aug 11, 2024 at 1:55 PM Andrea paz via Cin <cin@lists.cinelerra-gg.org> wrote:
A patch brings hardware encoding with vulkan into ffmpeg. In the
future I will try to make a preset for h264, but if I understand
correctly you have to use the ffmpeg from Lynne's repository and then
compile it with the --enable-vulkan option. Do you think a simple
replacement of our ffmpeg tar.gz with Lynne's tar.gz is enough?
https://lynne.ee/vulkan-video-encoding.html
--
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