Arch Linux User Repository

@MarsSeed For watching videos with hardware acceleration, your impact is likely to be minimal, since you can continue to use vaapi for this. intel-media-driver supports your hardware (it supports broadwell and later), so you can use vaapi acceleration. The functionality that you will lose is qsv, which is what media-sdk/onevpl is about, but qsv is somewhat similar to vaapi. Regarding repository ffmpeg, I would say the contrary: support probably will be changed anytime soon. onevpl support has already been requested in FS#77760, and this would drop media sdk from ffmpeg, since both cannot be enabled at the same time. In my testings, qsv is broken in newer Intel hardware (alder lake and later) when using ffmpeg + intel-media-sdk, and works only with ffmpeg + onevpl. So, if my qsv testing experience can be confirmed with other people, more and more users will have a broken qsv setup with repository ffmpeg over the time. I've already switched all my maintained ffmpeg AUR packages to use onevpl, as this is the way to go in my view.

the support for your 2016 hardware is dropped by the new onevpl

I know. It's not really a biggie for me though. The difference is only how much power-saving can be gained by using HW video acceleration with the very economical Intel integrated GPU.

But I'm using my laptop plugged in anyway. :)

Nevetheless, if Arch repo drops intel-media-sdk, I can still build ffmpeg with it from AUR.

The FFMPEG code is unlikely to drop support of it any time soon.

@MarsSeed Unfortunately, the support for your 2016 hardware is dropped by the new onevpl. I hope someone can continue to maintain media sdk with at least critical fixes, so "legacy" hardware could be supported.

Thank you for your detailed answer. Your reasoning makes sense. Let's see what happens in the future with this code base.

Btw I still use an old 2016 quasi-gamer laptop, and this driver helps me save on CPU load and therefore generated heat, when watching videos.

@MarsSeed media sdk will still be useful for users of the so called "legacy" Intel hardware, as they are not supported by onevpl. Being such, I think it makes sense to still maintain media sdk in the AUR, at least for the time being and while it can be built. When intel-media-sdk is dropped from the official repositories (after being replaced in ffmpeg), then maybe it makes sense to stay only with the stable version in the AUR, as the upstream repository will not receive updates anymore, or maybe not, as it will not hurt. Someone could could pick the media sdk codebase and continue to maintain it, for supporting the "legacy" hardware. If this happens, having the VCS (-git) package with a different source will still be useful. That being said, I think we should not hurry to delete this package, and give time to things.

Intel closed (archived) the GitHub repo, they won't continue developing this legacy hardware support library.

As a consequence, this package now packs exactly the same version as the latest tagged release, v23.2.2, carried by Arch repo.

So is it still useful to keep in AUR? Or would it be better deleted?

@NobodyDBG I cannot reproduce your issue. Package is building fine. Please make sure that you have an up-to-date libva-git package installed. Probably you are building against an old one.

@dbermond I use Arch Linux. With makepkg I got the same error.

@NobodyDBG Your log shows that you are still using an AUR helper (and not makepkg), since there are references to 'yay'. AUR helpers are not supported. Are you using Arch Linux or an Arch derivative?

@dbermond Build with makepkg:

[ 81%] Built target mfxhw_static make[2]: Leaving directory '/ramdisk/yay/intel-media-sdk-git/src/build' [ 86%] Built target mfx_h264la_hw64 /ramdisk/yay/intel-media-sdk-git/src/MediaSDK/_studio/mfx_lib/encode_hw/hevc/linux/base/hevcehw_base_weighted_prediction_lin.cpp: In lambda function: /ramdisk/yay/intel-media-sdk-git/src/MediaSDK/_studio/mfx_lib/encode_hw/hevc/linux/base/hevcehw_base_weighted_prediction_lin.cpp:60:19: error: 'VAEncSliceParameterBufferHEVC' has no member named 'pred_weight_table_bit_offset' 60 | slice.pred_weight_table_bit_offset = itSSH->PackInfo.at(PACK_PWTOffset); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ /ramdisk/yay/intel-media-sdk-git/src/MediaSDK/_studio/mfx_lib/encode_hw/hevc/linux/base/hevcehw_base_weighted_prediction_lin.cpp:61:19: error: 'VAEncSliceParameterBufferHEVC' has no member named 'pred_weight_table_bit_length' 61 | slice.pred_weight_table_bit_length = itSSH->PackInfo.at(PACK_PWTLength); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ make[2]: *** [_studio/mfx_lib/encode_hw/CMakeFiles/encode_hw.dir/build.make:902: _studio/mfx_lib/encode_hw/CMakeFiles/encode_hw.dir/hevc/linux/base/hevcehw_base_weighted_prediction_lin.cpp.o] Error 1 make[2]: Leaving directory '/ramdisk/yay/intel-media-sdk-git/src/build' make[1]: *** [CMakeFiles/Makefile2:2954: _studio/mfx_lib/encode_hw/CMakeFiles/encode_hw.dir/all] Error 2 make[1]: Leaving directory '/ramdisk/yay/intel-media-sdk-git/src/build' make: *** [Makefile:146: all] Error 2 make: Leaving directory '/ramdisk/yay/intel-media-sdk-git/src/build' ==> ERROR: A failure occurred in build(). Aborting...