<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">вс, 11 авг. 2024 г., 23:35 Andrew Randrianasulu <<a href="mailto:randrianasulu@gmail.com">randrianasulu@gmail.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">вс, 11 авг. 2024 г., 23:06 Phyllis Smith via Cin <<a href="mailto:cin@lists.cinelerra-gg.org" target="_blank" rel="noreferrer">cin@lists.cinelerra-gg.org</a>>:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-size:small"><p>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.<br></p></div></div></blockquote></div></div><div dir="auto"><a href="https://github.com/cyanreg/FFmpeg/tree/vulkan" target="_blank" rel="noreferrer">https://github.com/cyanreg/FFmpeg/tree/vulkan</a><br></div><div dir="auto"><br></div><div dir="auto">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 ?</div><div dir="auto"><br></div><div dir="auto">May be if we interested in encoding part of it just try to build this tree standalone and pipe y4m to its ffmpeg binary?</div><div dir="auto"><br></div><div dir="auto">Or pretend we have "7.1" already by packaging this git branch into tarball named like release, putting it in thirdparty/src, patching our <a href="http://configure.ac" target="_blank" rel="noreferrer">configure.ac</a> then see failures from API changes ? :)</div><div dir="auto"></div></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">ah, it seems to be merged 17 hours ago into main tree :)</div><div dir="auto"><br></div><div dir="auto"><a href="https://git.ffmpeg.org/gitweb/ffmpeg.git">https://git.ffmpeg.org/gitweb/ffmpeg.git</a><br></div><div dir="auto"><br></div><div dir="auto">see commits by Lynne</div><div dir="auto"><br></div><div dir="auto">so 'just' building with ffmpeg.git (and probably fixing thirdparty/Makefile so it does not disable vulkan for ffmpeg anymore - i hope building with old vulkan headers was fixed? or we need to pass --disable-vulkan on "old" OSes afterwards) should expose new encoder?</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-size:small"><p></p>
</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Aug 11, 2024 at 1:55 PM Andrea paz via Cin <<a href="mailto:cin@lists.cinelerra-gg.org" rel="noreferrer noreferrer" target="_blank">cin@lists.cinelerra-gg.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">A patch brings hardware encoding with vulkan into ffmpeg. In the<br>
future I will try to make a preset for h264, but if I understand<br>
correctly you have to use the ffmpeg from Lynne's repository and then<br>
compile it with the --enable-vulkan option. Do you think a simple<br>
replacement of our ffmpeg tar.gz with Lynne's tar.gz is enough?<br>
<a href="https://lynne.ee/vulkan-video-encoding.html" rel="noreferrer noreferrer noreferrer" target="_blank">https://lynne.ee/vulkan-video-encoding.html</a><br>
-- <br>
Cin mailing list<br>
<a href="mailto:Cin@lists.cinelerra-gg.org" rel="noreferrer noreferrer" target="_blank">Cin@lists.cinelerra-gg.org</a><br>
<a href="https://lists.cinelerra-gg.org/mailman/listinfo/cin" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.cinelerra-gg.org/mailman/listinfo/cin</a><br>
</blockquote></div>
-- <br>
Cin mailing list<br>
<a href="mailto:Cin@lists.cinelerra-gg.org" rel="noreferrer noreferrer" target="_blank">Cin@lists.cinelerra-gg.org</a><br>
<a href="https://lists.cinelerra-gg.org/mailman/listinfo/cin" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.cinelerra-gg.org/mailman/listinfo/cin</a><br>
</blockquote></div></div></div>
</blockquote></div></div></div>