<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<br>
<div class="moz-cite-prefix">Den 28.09.2024 21:24, skrev Andrew
Randrianasulu:<br>
</div>
<blockquote type="cite"
cite="mid:CA+rFky67W+e2js4jjXSfow3h=FfiHtYAdUjwewC5wfCWhPFASg@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">сб, 28 сент. 2024 г.,
21:59 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"><br>
<br>
Den 28.09.2024 19:10, skrev Andrew Randrianasulu:<br>
> May be ffmpeg tries onevpl on new hardware?<br>
><br>
> <a href="https://bugs.gentoo.org/590752"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://bugs.gentoo.org/590752</a><br>
><br>
> example output<br>
><br>
> <a
href="https://bugs.gentoo.org/attachment.cgi?id=835909"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://bugs.gentoo.org/attachment.cgi?id=835909</a><br>
<br>
<br>
I think so because Intel VPL GPU Runtime is for use on
Intel DG1 (Iris <br>
Xe graphics and newer),<br>
while Intel Media SDK for use on older, legacy Intel
graphics, selected <br>
by the VPL dispatcher<br>
<a
href="https://github.com/intel/libvpl/?tab=readme-ov-file#intel-video-processing-library-intel-vpl"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/intel/libvpl/?tab=readme-ov-file#intel-video-processing-library-intel-vpl</a><br>
<br>
I searched a time back for the vpl-inspect tool, but I
could not find it <br>
among my installed RT Intel packages<br>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">try <a
href="https://github.com/intel/libvpl-tools/"
moz-do-not-send="true" class="moz-txt-link-freetext">https://github.com/intel/libvpl-tools/</a>
?</div>
<div dir="auto"><br>
</div>
<div dir="auto">either as package name or your own source build
...</div>
<div dir="auto">(may be ping libvpl maintainer in suse?)</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
</div>
</blockquote>
<br>
Yeah, libvpl-tools is now built for openSUSE, and I ran two of them
on Slowroll/Arc A750 according to this article:<br>
<a class="moz-txt-link-freetext" href="https://www.intel.com/content/www/us/en/developer/articles/technical/overview-of-onevpl-examples-and-tools.html#articleparagraph_829690411">https://www.intel.com/content/www/us/en/developer/articles/technical/overview-of-onevpl-examples-and-tools.html#articleparagraph_829690411</a><br>
<br>
<i>oneVPL Tools<br>
<br>
There are oneVPL tools available in the oneVPL base repository
which are a good starting point to get familiar with the oneVPL
functionalities. The command line tools for checking available
implementation supported by the current system are in the cli
directory and the ‘sample-*’ tools are in the legacy directory.<br>
Tools for Checking Implementation Capabilities<br>
<br>
To check the implementation capabilities of oneVPL the following
approaches can be used:,<br>
<br>
First Approach:<br>
<br>
vpl-inspect|grep Implementation</i><br>
<br>
<font face="Courier New, Courier, monospace">vpl-inspect|grep
Implementation<br>
libva info: VA-API version 1.22.0<br>
libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so<br>
libva info: Found init function __vaDriverInit_1_22<br>
libva info: va_openDriver() returns 0<br>
libva info: VA-API version 1.22.0<br>
libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so<br>
libva info: Found init function __vaDriverInit_1_22<br>
libva info: va_openDriver() returns 0<br>
Implementation #0: mfx-gen</font><br>
<br>
=================<br>
<i><br>
Second Approach (improved visibility in Linux environment):<br>
<br>
system_analyzer<br>
.........snip<br>
<br>
Here, it is oneVPL dispatcher’s responsibility to load GPU
runtimes (libmfxhw64.so or libmfxgen.so) depending on the system’s
compatibility and selected codec. There are no plans for
libmfxhw64.xo.1 to support new Gen (Gen12 or newer) platforms.
Media SDK GPU runtime (libmfxhw64.so) runs on Gen9 and Gen11 while
oneVPL GPU runtime (libmfxgen.so) supports Gen12, Xe, and newer
hardware. Media SDK runtime supports API 1.35 and VPL runtime
supports API 2.x (currently 2.8)<br>
<br>
</i><br>
<font face="Courier New, Courier, monospace">system_analyzer<br>
------------------------------------<br>
Looking for GPU interfaces available to OS...<br>
FOUND: /dev/dri/renderD128<br>
GPU interfaces found: 1<br>
------------------------------------<br>
<br>
<br>
------------------------------------<br>
Available implementation details:<br>
libva info: VA-API version 1.22.0<br>
libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so<br>
libva info: Found init function __vaDriverInit_1_22<br>
libva info: va_openDriver() returns 0<br>
libva info: VA-API version 1.22.0<br>
libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so<br>
libva info: Found init function __vaDriverInit_1_22<br>
libva info: va_openDriver() returns 0<br>
<br>
Implementation #0: mfx-gen<br>
Library path: /usr/lib64/libmfx-gen.so.1.2.12<br>
AccelerationMode: MFX_ACCEL_MODE_VIA_VAAPI<br>
ApiVersion: 2.12<br>
Impl: MFX_IMPL_TYPE_HARDWARE<br>
ImplName: mfx-gen<br>
MediaAdapterType: MFX_MEDIA_DISCRETE<br>
VendorID: 0x8086<br>
DeviceID: 0x56A1<br>
GPU name: Intel® Arc(TM) A750 graphics (arch=Xe HPG
codename=DG2)<br>
PCI BDF: 0000:03:00.00<br>
PCI RevisionID: 0x0008<br>
DRMRenderNodeNum: 128<br>
DeviceName: mfx-gen<br>
------------------------------------</font><br>
<br>
I am not quite sure what the essence of this output really tell?<br>
There are also additional "sample_* tools " mentioned in the
article, that possibly are useful (?)<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CA+rFky67W+e2js4jjXSfow3h=FfiHtYAdUjwewC5wfCWhPFASg@mail.gmail.com">
<div dir="auto">
<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">
<a
href="https://www.intel.com/content/www/us/en/developer/articles/technical/overview-of-onevpl-examples-and-tools.html"
rel="noreferrer noreferrer" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">https://www.intel.com/content/www/us/en/developer/articles/technical/overview-of-onevpl-examples-and-tools.html</a><br>
<br>
</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>