Search Criteria
Package Details: intel-hybrid-codec-driver-git 2.0.0.r6.gb0c7970d-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/intel-hybrid-codec-driver-git.git (read-only, click to copy) |
---|---|
Package Base: | intel-hybrid-codec-driver-git |
Description: | Libva support for partially hardware accelerated encode and decode on Haswell and newer |
Upstream URL: | https://github.com/kcning/intel-hybrid-driver |
Licenses: | MIT |
Conflicts: | intel-hybrid-codec-driver |
Provides: | intel-hybrid-codec-driver |
Submitter: | dreieck |
Maintainer: | xiota |
Last Packager: | xiota |
Votes: | 35 |
Popularity: | 1.03 |
First Submitted: | 2023-05-04 11:03 (UTC) |
Last Updated: | 2024-07-08 09:47 (UTC) |
Dependencies (6)
- libcmrtAUR
- libva (libva-gitAUR, intel-media-stack-binAUR, libva-headlessAUR)
- autoconf (autoconf-gitAUR) (make)
- automake (automake-gitAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- libva-intel-driver-hybridAUR (optional) – To be able to use the full hw codecs with hybrid codecs
Required by (1)
- libva-intel-driver-hybrid (requires intel-hybrid-codec-driver) (optional)
Latest Comments
« First ‹ Previous 1 2 3 4
wan109020 commented on 2018-11-08 17:44 (UTC)
It's working fine for me.
I am using a skylake CPU (Intel Corei7-6560U)
Playing YouTube in VP9 with chromium-vaapi is smooth, <10%CPU is used and no frame drops with libva-intel-driver-hybrid and this package installed
Without this package, ~30%is used when playing 1080p vp9 youtube and there's occasional frame drops
DetMittens commented on 2018-01-21 11:45 (UTC)
Unfortunately that sounds like the hardware just isn't fast enough, even with this driver (depending on which graphics generation) a lot of the decoding is still done in software. For example the Braswell nuc I have can do vp9 decoding but past ~720p30 it stutters and drops frames.
I've updated the package to make the driver at least partially usable for now and included a warning when upgrading from a previous version.
Burdeman commented on 2018-01-21 01:45 (UTC) (edited on 2018-01-21 01:46 (UTC) by Burdeman)
After adding --disable-x11 No more error and I can see the VP9 profile.
$ vainfo libva info: VA-API version 1.0.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_0 libva info: va_openDriver() returns 0 ................... VAProfileVP9Profile0 : VAEntrypointVLD
Chromium still runs like a dog on VP9 video (e.g. Youtube) so don't know whats going on there. It is indicating GPU decoding in use though.
Back to forcing h264 for now...
DetMittens commented on 2018-01-20 17:20 (UTC)
I'm not sure what is causing the driver to depend on the old version of libva-x11, as all the configures seem correct to me.
When I add --disable-x11 to this package's configure the resulting driver is able to load and I was able to use VP9 decoding on BSW successfully in mpv. Adding this flag means that when in an X11 session vaapi decoding of hybrid codecs can only be done via drm however this way is recommended over vaapi via X11 AFAIK
If anyone is able to test this package with --disable-x11 flag please let me know the outcome because if it works then I'll add it to the PKGBUILD until a better solution can be found.
Burdeman commented on 2018-01-20 15:18 (UTC) (edited on 2018-01-20 15:19 (UTC) by Burdeman)
init error on hybrid_drv_video.so
$ vainfo libva info: VA-API version 1.0.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_0 failed to open /usr/lib/dri/hybrid_drv_video.so Failed to wrapper hybrid_drv_video.so ...
strace reveals its looking for libva-x11.so.1:
<hr>openat(AT_FDCWD, "/usr/lib/tls/haswell/x86_64/libva-x11.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/usr/lib/tls/haswell/x86_64", 0x7ffd8640d1e0) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/lib/tls/haswell/libva-x11.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/usr/lib/tls/haswell", 0x7ffd8640d1e0) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/lib/tls/x86_64/libva-x11.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/usr/lib/tls/x86_64", 0x7ffd8640d1e0) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/lib/tls/libva-x11.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/usr/lib/tls", 0x7ffd8640d1e0) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/lib/haswell/x86_64/libva-x11.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/usr/lib/haswell/x86_64", 0x7ffd8640d1e0) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/lib/haswell/libva-x11.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/usr/lib/haswell", 0x7ffd8640d1e0) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/lib/x86_64/libva-x11.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/usr/lib/x86_64", 0x7ffd8640d1e0) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/usr/lib/libva-x11.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/usr/lib", {st_mode=S_IFDIR|0755, st_size=135168, ...}) = 0
...
argen14 commented on 2018-01-08 04:16 (UTC)
I guess I am having same problem as @Detmittens . I have i5-6200u skylake graphics. After installing this package I've re-compiled libva-intel-driver
$ yaourt -Sb libva-intel-driver I changed the lines of PKGBUILD:
Seems libva tries to load the driver but fails:
ibva info: VA-API version 1.0.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_0 /usr/lib/dri/hybrid_drv_video.so init failed Failed to wrapper hybrid_drv_video.so libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.0 (libva 2.0.0) vainfo: Driver version: Intel i965 driver for Intel(R) Skylake - 2.0.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple : VAEntrypointVLD VAProfileMPEG2Simple : VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileH264ConstrainedBaseline: VAEntrypointFEI VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264Main : VAEntrypointFEI VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointFEI VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main : VAEntrypointVLD VAProfileVC1Advanced : VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileVP8Version0_3 : VAEntrypointEncSlice VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice
Any ideas to try? Thanks
DetMittens commented on 2017-11-13 19:03 (UTC)
uth commented on 2017-11-13 18:06 (UTC) (edited on 2017-11-13 18:12 (UTC) by uth)
DetMittens commented on 2017-11-13 16:58 (UTC)
« First ‹ Previous 1 2 3 4