Hi Haihao,
this is an update finding myself in a happy mood 🙂
openSuSE ships both _libmfx_, and _libmfx-gen_.
It took me some time to realise that, but your last response lead me in the
right direction. I compiled libmfx-gen, and voila I can qsv transcode as
desired.
Thank you for your cont
Hi Martin,
/usr/lib64/libmfxhw64.so.1.35 is for legacy HWs, you should install the vpl
runtime for your i9-13900. libmfx-gen.so is a link to the vpl runtime. For
example, below is the runtime in my system:
$ ls -l /usr/lib/x86_64-linux-gnu/libmfx-gen.so*
lrwxrwxrwx 1 root root17 Apr 24
Hi Haihao,
when running
"vpl-inspect", I get this, and only this
Implementation #0: mfxhw64
 Library path: /usr/lib64/libmfxhw64.so.1.35
 AccelerationMode: MFX_ACCEL_MODE_VIA_VAAPI
 ApiVersion: 1.35
 Impl: MFX_IMPL_TYPE_HARDWARE
 VendorImplID: 0x
 ImplName: mfxhw64
 License:Â
 Versio
Hi Martin,
I may reproduce your issue in my side if there is only msdk runtime
(libmfxhw.so) in my system. Could you run vpl-inspect to check whether vpl gpu
runtime (libmfx-gen.so) is available in your side ?
$ vpl-inspect | grep libmfx-gen.so
BRs
Haihao
>
> Dear all,
>
> well, I tried dif
Dear all,
well, I tried different versions, compiled, tried everything.
Still the error is there, no progress, unfortunately.
If, at any time, I will be more lucky than right now, I will let you know.
Martin.
On Monday, 22 April, 2024 17:46 CEST, "Xiang, Haihao"
wrote:
Â
>
> Hi,
>
> yes, I
>
> Hi,
>
> yes, I did so, but it did not help, see here
> Â
> vainfoÂ
> Trying display: wayland
> Trying display: x11
> libva info: VA-API version 1.20.0
> libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so
> libva info: Found init function __vaDriverInit_1_20
> libva info: va_openDrive
On Mon, 22 Apr 2024, 18:25 Martin Stenzel via ffmpeg-user, <
ffmpeg-user@ffmpeg.org> wrote:
>
> Hi,
>
> yes, I did so, but it did not help, see here
>
> vainfo
> Trying display: wayland
> Trying display: x11
> libva info: VA-API version 1.20.0
> libva info: Trying to open /usr/lib64/dri/iHD_drv_vi
Hi,
yes, I did so, but it did not help, see here
Â
vainfoÂ
Trying display: wayland
Trying display: x11
libva info: VA-API version 1.20.0
libva info: Trying to open /usr/lib64/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_20
libva info: va_openDriver() returns 0
vainfo: VA-
[...]
[AVHWDeviceContext @ 0x560662049440] libva: VA-API version 1.20.0
[AVHWDeviceContext @ 0x560662049440] libva: User requested driver 'iHD'
[AVHWDeviceContext @ 0x560662049440] libva: Trying to open
/usr/lib64/dri/iHD_drv_video.so
[AVHWDeviceContext @ 0x560662049440] libva: Found init functi
Yes, in the initial email I forgot to mention this important information.
cat /proc/cpuinfo
vendor_id    : GenuineIntel
cpu family    : 6
model      : 183
model name    : 13th Gen Intel(R) Core(TM) i9-13900
stepping     : 1
microcode    : 0x113
cpu MHz     : 2399.975
cache s
On 21-04-2024 22:53, Martin Stenzel via ffmpeg-user wrote:
Error setting child device handle: -17
device=/dev/dri/renderD128
Did you test that this device does actually exist on your system?
Can you specify what GPU you have?
Does the error also occur if you leave out the explicit child devi
11 matches
Mail list logo