<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">чт, 17 окт. 2024 г., 15:06 Terje J. Hanssen <<a href="mailto:terjejhanssen@gmail.com">terjejhanssen@gmail.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div>
<br>
<br>
<br>
<div>Den 17.10.2024 13:51, skrev Andrew
Randrianasulu:<br>
</div>
<blockquote type="cite">
<div dir="auto">
<div><br>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">чт, 17 окт. 2024 г., 13:40
Terje J. Hanssen <<a href="mailto:terjejhanssen@gmail.com" target="_blank" rel="noreferrer">terjejhanssen@gmail.com</a>>:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div> <br>
<br>
<br>
<div>Den 14.10.2024 00:38, skrev Andrew Randrianasulu:<br>
</div>
<blockquote type="cite">
<div dir="auto">
<div><br>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">пн, 14 окт.
2024 г., 01:36 Phyllis Smith <<a href="mailto:phylsmith2017@gmail.com" rel="noreferrer noreferrer" target="_blank">phylsmith2017@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="ltr">
<div class="gmail_default" style="font-size:small">Andrew, so it
seems prudent to check into GIT, the
av1_vaapi.mp4 render format (after
successfully tested of course); but what
about the QSV encoders?<br>
</div>
</div>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">wait for Terje's testing OR try to
build oneVPL-cpu (it sort of circles back to
different branch of ffmpeg, so ffmpeg will think
it uses qsv but it in fact will use another ffmpeg
.... well, in theory! it does not work for me on
32-bit!)</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"><br>
</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
I wonder if Hw accellerated encoding support via Vaapi
and QSV is to be embedded in future Cingg Appimage
and/or packages if possible?<br>
What about a list of supported dGPUs/iGPUs?<br>
</div>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Problem is - QSV/vaapi basically search for
driver component and this one might be in different location
on different distros, and interface between two also not set
in stone.</div>
<div dir="auto"><br>
</div>
<div dir="auto">For appimage you can just unpack them and remove
libva.so so on startup cingg will link to system's libva.</div>
<div dir="auto"><br>
</div>
<div dir="auto">QSV as we learned is another layer with their
own runtime path for yet another set of driver components. So,
while building libvpl itself is relatively easily making sure
it finds its drivers is not easy (at least for me).</div>
<div dir="auto"><br>
</div>
<div dir="auto">speaking about GPU list I think it will be
fairly short, you,Phyllis and Andrea probably only ones who
use it and report back. Stephan noticed some troubles and
reverted back to software. I can test nvdec/nvenc on livecd
but this is not my everyday setup (Nvidia proprietary drivers
enforce 64-bit system).</div>
<div dir="auto"><br>
</div>
<div dir="auto">But well, feel free to post short summary of
that works on your GPUs in cingg as another thread, hopefully
others will chime in!</div>
</div>
</blockquote>
<br>
If we get available a packaged Cingg test build (rpm/Leap for me),
it would be more useful to do this test. Then I have available three
gen. Intel, legacy Skylake/Kabylake iGPUs and current DG2/Arc GPU. I
also have/had a Nvidia GPU on Skylake, but it looks like it past
away.<br></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto">I think you can build rpm yourself, but for this we need to update spec file, so it will point at new source and add openvpl as requirements.</div><div dir="auto"><br></div><div dir="auto">In meantime you can just make your own appimage from just build cingg-with-system-ffmpeg, so it hopefully will not be lost after few system updates.</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>
<br>
<br>
<blockquote type="cite">
<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> <br>
<br>
<blockquote type="cite">
<div dir="auto">
<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 class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Sun,
Oct 13, 2024 at 2:36 PM Andrew
Randrianasulu via Cin <<a href="mailto:cin@lists.cinelerra-gg.org" rel="noreferrer 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">
<div dir="auto">hopefully with very silly
top-line-as-comment error fixed
<div dir="auto"><br>
</div>
<div dir="auto">SORRY!</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
</div>
-- <br>
Cin mailing list<br>
<a href="mailto:Cin@lists.cinelerra-gg.org" rel="noreferrer 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 noreferrer" target="_blank">https://lists.cinelerra-gg.org/mailman/listinfo/cin</a><br>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
</div>
</blockquote></div></div></div>