<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<br>
<br>
<div class="moz-cite-prefix">Den 18.10.2024 02:08, skrev Andrew
Randrianasulu:<br>
</div>
<blockquote type="cite"
cite="mid:CA+rFky5nGwGV+-0uimd6nJt0CNsue6hsWMAr_kns9ZLaf8c9CQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<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"
moz-do-not-send="true" class="moz-txt-link-freetext">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 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"
moz-do-not-send="true"
class="moz-txt-link-freetext">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"
moz-do-not-send="true"
class="moz-txt-link-freetext">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>
</blockquote>
<br>
Andrey replied to me in a previous thread:<br>
Hardware acceleration methods Sat, 14 Sep 2024 08:55:11 +0300<br>
<a class="moz-txt-link-freetext" href="https://lists.cinelerra-gg.org/pipermail/cin/2024-September/008621.html">https://lists.cinelerra-gg.org/pipermail/cin/2024-September/008621.html</a><br>
<blockquote type="cite">
<div><span style="font-size:12.8px">>Is there something that
prevent typical QSV to be prebuilt in the CinGG/FFmpeg rpm?</span><br>
</div>
<div><br>
</div>
<div dir="auto">The ffmpeg not installed on my suse build host. If
you how to enable QSV, I'll change the build script.</div>
<div dir="auto"><br>
</div>
</blockquote>
<br>
Is this a "path" we can continue with here?<br>
<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>