Cannot transcode with Vaapi on intel GeminiLake [UHD Graphics 600]

[prahal]

.

I have tried both those drivers, this is the output from that command:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-====================================-============-============-================================================
un intel-media-va-driver <none> <none> (no description available)
ii intel-media-va-driver-non-free:amd64 21.1.1+ds1-1 amd64 VAAPI driver for the Intel GEN8+ Graphics family

The main difference I can spot in the output from 'vainfo' on next/emby is next uses va-api v1.10 while emby uses v1.18....not sure how to update this?

I doubt the vaapi matters but the intel-media-va-driver-non-free version does (or the equivalent pacakge version Emby uses).
https://packages.debian.org/search?keywo...ection=all
bookworm is intel-media-va-driver-non-free v23 while bullseye is 21.


From sub on page 1 of this thread: Sept 2022 https://forums.nextpvr.com/showthread.ph...#pid575187
v6 moved to being based on "mcr.microsoft.com/dotnet/aspnet:6.0", which is based on debian bullseye based

Mind bookworm is stable. Maybe there is a newer microsoft aspnet docker image based on bookworm instead of bullseye?
But first if you could check if bookworm indeed is new enough for your card that would help to know if you don't need an even newer release of the intel hw accel driver.
You might try to upgrade a container either way. But mind, a container is meant to be destroyed and recreated from an image.The Docker tooling make deleting your container pretty easy.

But from your Emby container output the 23.1.1 should do the job.
your log shows v23.1.4
vainfo: Driver version: Intel iHD driver for Intel® Gen Graphics - 23.1.4 (12e141dc2)
and bookworm is 23.1.1

[mvallevand]

The next version of NextPVR is .Net 8 and so Docker will be Debian 12 based.

Martin

[QDivision]

@Martin When will that release be out?

I manage to get this to work with a combination of building from source https://github.com/intel/gmmlib https://github.com/intel/libva and https://github.com/intel/media-driver

It was https://github.com/intel/media-driver that seemed to finally get vainfo to work and with that successful transcoding.

I might fresh install the next container and just build 'media-driver' to see if that does the trick but it sounds like moving to Debian 12 might solve it.

[mvallevand]

That's subject to the time sub has to complete it all and fix some things I've been tracking in pre-release. The Docker images don't get built until the Linux versions are final.

Debian 12 alone won't help if you guys don't tell sub what optional driver(s) he needs to install for Intel to work.

Martin.

[QDivision]

Ok so I've run a few tests with fresh containers and all drivers need to be built from source to fix vaapi on my CPU i.e. libva --> gmmlib --> media-driver.

I have created the following bash script to fix this for the current release (if this helps anyone else), hopefully the latest versions of these drivers will be rolled into the next release.

#!/bin/bash

mkdir /home/vaapi_fix && cd /home/vaapi_fix
apt update
apt -y upgrade
apt install -y git cmake g++ autoconf libtool libdrm-dev xorg xorg-dev openbox libx11-dev libgl1-mesa-glx pkg-config libdrm-dev automake libx11-xcb-dev libxcb-dri3-dev
git clone https://github.com/intel/libva
cd libva
./autogen.sh --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu
make
make install
cd /home/vaapi_fix
git clone https://github.com/intel/gmmlib
cd gmmlib
mkdir build && cd build
cmake -DCMAKE_BUILD_TYPE=Release ..
make -j"$(nproc)"
make install
cd /home/vaapi_fix
git clone https://github.com/intel/media-driver
cd media-driver
mkdir build && cd build
cmake ..
make -j"$(nproc)"
make install
cd /home
rm -rf vaapi_fix
apt remove -y git cmake g++ autoconf libtool libdrm-dev xorg xorg-dev openbox libx11-dev libgl1-mesa-glx pkg-config libdrm-dev automake libx11-xcb-dev libxcb-dri3-dev

[mvallevand]

Hopefully sub doesn't have to build them and he can just pull in gmmib from apt and update form the bookworm repos here like he did for buster

https://forums.nextpvr.com/showthread.ph...#pid575284

Martin

[mvallevand]

Sub installed the extra drivers for VAAPI support in v7 so with Debian 12 hopefully these work for you. He also is using tweaked VAAPI setting and I found that even compared with the VAAPI setting in v6, Docker v7 was using much fewer resources.

Martin

[QDivision]

Installed the latest v7 and looks like this issue has been resolved, thank you!

[sub]

Great!