<!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 11.12.2024 23:56, skrev Andrew
Randrianasulu:<br>
</div>
<blockquote type="cite"
cite="mid:CA+rFky6PaXCm-4_vODs2xJApx9csovtZYh49CH=DhnpvSTrVKg@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">чт, 12 дек. 2024 г., 00:43
Terje J. Hanssen via Cin <<a
href="mailto:cin@lists.cinelerra-gg.org"
moz-do-not-send="true" class="moz-txt-link-freetext">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> To clarify some pieces once again, I put up some
basic statements or questions:<br>
<br>
For an end-user to utilize video acceleration support,
he/she need a computer with supported graphical hardware
with libs/API and drivers for it(?)<br>
</div>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">yes</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>
The libs and drivers can be dynamical linked (enabled)
to the system or static built (embedded) in CinGG?</div>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">well, here it gets complicated. vaapi and such
actually TWO libs at least - one with generic code ffmpeg use,
and hw-specific driver lib. Both are shared (*.so) and
moreover runtime path where given generic lib looks for
drivers depend on Linux distro/how it was compiled.</div>
</div>
</blockquote>
<br>
Yeah, it is not easy to get an overview understanding. Fore example
I have the following "mix" installed on my machine:<br>
<br>
<font face="Courier New, Courier, monospace">i |
intel-vaapi-driver | Intel Driver for Video Acceleration (VA)
API-> | pakke<br>
i | Mesa-libva | Mesa VA-API
implementation | pakke<br>
i | kernel-firmware-i915 | Kernel firmware files for Intel i915
graphics driver | pakke<br>
i | libva2 | Video Acceleration
API pakke</font><br>
<blockquote type="cite"
cite="mid:CA+rFky6PaXCm-4_vODs2xJApx9csovtZYh49CH=DhnpvSTrVKg@mail.gmail.com">
<div dir="auto">
<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>
So what happened when adding oneVPL (qsv) support to the
build system; dynamic linked to system or static added
embedded into the build?<br>
</div>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">dynamic</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> If oneVPL was dynamic linked, the qsv support may be
be distribution specific, or if static built it will be
generic available on compliant hardware?</div>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">as above, at least due to different driver path
it will not work out of the box everywhere even if static
(*.a) libs were used. You probably should ask for details on
ffmpeg or intel mailing lists ...</div>
<div dir="auto"><br>
</div>
<div dir="auto">Distributions nowadays tend to avoid *.a files
if possible, due to consistency in upgradeability (if you
embed say libpng at some point any update to it will require
not just updating *.so but also any application with embedded
libpng, and there is no simple way to even tell from stripped
binary that symbols it use)</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>
Is it correct to say the build machine does not need the
specific graphical hardware, but needs the actual
graphic libs installed to build Cingg with it?<br>
</div>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">yes</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>
Could in principle similar methods be extended to
include broader video acceleration support for AMD/amf
and NVIDIA/nvenc?<br>
</div>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">nvenc already supported, I think? At some point
I tried it with GF710 on livedvd and it was working for me.
try to test it if you have proprietary nvidia drivers.</div>
</div>
</blockquote>
<br>
Yes, seemingly:<br>
Cin/bin/ffmpeg/video> ls *nvenc*<br>
h264_nvenc.mp4 h264_nvenc.qt h265_nvenc.mp4<br>
<br>
Maybe I can do an attempt later, if I get life in the old GeForce
GTX 960 in my Skylake workstation.<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CA+rFky6PaXCm-4_vODs2xJApx9csovtZYh49CH=DhnpvSTrVKg@mail.gmail.com">
<div dir="auto">
<div dir="auto"><br>
</div>
<div dir="auto">amf ... I have no idea how well it work or that
it demand lib-wise. As long as it just ffmpeg switch - I can
try to add this too but honestly, isn't it more like
"checkbox" feature? Does it provide anything over vaapi?</div>
</div>
</blockquote>
<br>
<blockquote type="cite"
cite="mid:CA+rFky6PaXCm-4_vODs2xJApx9csovtZYh49CH=DhnpvSTrVKg@mail.gmail.com">
<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> <br>
--------------<br>
<br>
So a confusing piece if "oneVPL" instead should have
been replaced with "libvpl?, because I just read<br>
<blockquote><i>Note for Users of Intel® oneAPI Video
Processing Library (oneVPL) and for Intel® Media SDK</i><br>
<i><a
href="https://www.intel.com/content/www/us/en/developer/tools/vpl/overview.html"
target="_blank" rel="noreferrer"
moz-do-not-send="true"
class="moz-txt-link-freetext">https://www.intel.com/content/www/us/en/developer/tools/vpl/overview.html</a></i><br>
<br>
<i>oneVPL is now called the Intel® Video Processing
Library (Intel® VPL). The library will no longer be
part of the oneAPI specification so that Intel can
focus on providing video processing features on
Intel GPUs.</i><br>
<br>
</blockquote>
In comparision on openSUSE/Slowroll on Intel, there are
libvpl(2) (and no oneVPL).<br>
<blockquote><i>The oneAPI Video Processing Library
(oneVPL) provides a single video processing API for
encode, decode, and video processing that works
across a wide range of accelerators.<br>
</i></blockquote>
ffmpeg similar has --enable-libvpl --enable-vaapi
--enable-vdpau --enable-vulkan<br>
</div>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">naming a bit confusing, but this is what intel
invented! </div>
<div dir="auto"><br>
</div>
<div dir="auto">Probably OneVPL is technology/marketing name and
libvpl is library component ffmpeg actually looks for.</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>
<blockquote><i><br>
<br>
<br>
</i></blockquote>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</div>
-- <br>
Cin mailing list<br>
<a href="mailto:Cin@lists.cinelerra-gg.org"
target="_blank" rel="noreferrer" moz-do-not-send="true"
class="moz-txt-link-freetext">Cin@lists.cinelerra-gg.org</a><br>
<a
href="https://lists.cinelerra-gg.org/mailman/listinfo/cin"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://lists.cinelerra-gg.org/mailman/listinfo/cin</a><br>
</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>