Package Details: chromium-vaapi 63.0.3239.108-1

Git Clone URL: https://aur.archlinux.org/chromium-vaapi.git (read-only)
Package Base: chromium-vaapi
Description: Chromium compiled with VA-API support for Intel Graphics
Upstream URL: https://www.chromium.org/Home
Keywords: browser web
Licenses: BSD
Conflicts: chromium
Provides: chromium
Submitter: samcv
Maintainer: OneObsession (maximbaz)
Last Packager: maximbaz
Votes: 27
Popularity: 2.266016
First Submitted: 2016-07-09 09:44
Last Updated: 2017-12-15 10:05

Dependencies (39)

Required by (30)

Sources (10)

Pinned Comments

samcv commented on 2016-08-01 05:11

NOTE: I no longer have time to maintain this package. I am looking for a co-maintainer who would be willing to take over. I am willing to help you, but I no longer have the time to spend compiling and debugging.

The version in the repo/on AUR is outdated and has certificate issues due to some timer inside Chromium that was triggered after a certain length of time from the build. You could also try chromium-dev-vaapi from ArchCN http://repo.archlinuxcn.org/x86_64/


I am now providing a repository in case you don't want to build the entire package yourself. The repository can be used by adding this to you pacman.conf:
[samcv]
Server = https://cry.nu/repo/$arch/
SigLevel = Required

The package is signed with my PGP key, so you must add my key to pacman by doing:
pacman-key -r C3881D62
pacman-key --lsign-key C3881D62

If you have an Intel GPU you should use the chromium-vaapi package, but if you use Radeon/NVIDIA you should use another package in my repository called chromium-vaapi-other (If you want compile it yourself, please rename the package name in the PKGBUILD to chromium-vaapi-other and it will use the chromium-vaapi-other patch instead of the intel one). If someone can test it out and email me if it works along with the make and model of your video card that would be great. Contact information is samantham@posteo.net Thank you.

Other useful info:
Run "vainfo" in terminal to see what your card supports. Most don't support VP9 encoding which is used by default on YouTube and other sites. If so you may try this plugin https://chrome.google.com/webstore/detail/h264ify/aleakchihdccplidncghkekgioiakgal If your card doesn't support 60fps H.264, make sure to go into the options for the plugin and disable 60fps video.
To see if it is working properly, when a video starts playing you should see the following in your terminal:
libva info: VA-API version 0.39.2
libva info: va_getDriverName() returns 0

This message also shows up twice when chromium first opens when chromium checks if the computer supports VAAPI.

Latest Comments

xsmile commented on 2017-12-10 13:14

Not sure which component is responsible and when the change happened, but Chromium can now play videos that couldn't be played with previous versions when using VA-API. I like this progress.

maximbaz commented on 2017-12-07 09:55

Awesome, thanks for the help!

I wait for the official chromium to be updated, because this PKGBUILD is always dependent on that one. Once they push PKGBUILD for v63, I'll get an email and update this package as well.

xsmile commented on 2017-12-07 03:15

@maximbaz: The latest revision of the VAAPI patch works as usual, along with the libva version patch:

https://raw.githubusercontent.com/gcarq/inox-patchset/feature/63/chromium-libva-r2.patch

https://raw.githubusercontent.com/gcarq/inox-patchset/feature/63/chromium-vaapi-r15.patch

maximbaz commented on 2017-11-23 10:00

The patch is submitted a long time ago [1], what is delaying the adoption is lack of attention to the patch from the Chromium team. Once someone from their team looks at the patch and merges it, we will get HW acceleration in the official Chromium ;)

[1]: https://chromium-review.googlesource.com/c/chromium/src/+/532294

olive commented on 2017-11-23 09:53

Does anyone know if there are plans to make this build the official chromium version (not in ArchLinux in particular but in general)? This mostly works fine and at least at the beginning, the HW acceleration would only be available by enabling special flags, so what could possibly delay the adoption of the patch for so long?

HeavyHDx commented on 2017-11-22 22:21

I'm getting these errors on startup with a GTX 970 with NVIDIA proprietary 387.22-5. Just wondering if I did something wrong or if NVIDIA is just not supported at all.


libva info: VA-API version 1.0.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/dri/nvidia_drv_video.so
libva info: Found init function __vaDriverInit_1_0
libva info: va_openDriver() returns 0
[14580:14580:1122/230215.500699:ERROR:vaapi_wrapper.cc(464)] vaQuerySurfaceAttributes failed VA error: invalid parameter
[14580:14580:1122/230215.500720:ERROR:vaapi_wrapper.cc(334)] GetMaxResolution failed for va_profile 0 and entrypoint 1
[14580:14580:1122/230215.500725:ERROR:vaapi_wrapper.cc(464)] vaQuerySurfaceAttributes failed VA error: invalid parameter
[14580:14580:1122/230215.500731:ERROR:vaapi_wrapper.cc(334)] GetMaxResolution failed for va_profile 1 and entrypoint 1
[14580:14580:1122/230215.500736:ERROR:vaapi_wrapper.cc(464)] vaQuerySurfaceAttributes failed VA error: invalid parameter
[14580:14580:1122/230215.500740:ERROR:vaapi_wrapper.cc(334)] GetMaxResolution failed for va_profile 2 and entrypoint 1
[14580:14580:1122/230215.500744:ERROR:vaapi_wrapper.cc(464)] vaQuerySurfaceAttributes failed VA error: invalid parameter
[14580:14580:1122/230215.500748:ERROR:vaapi_wrapper.cc(334)] GetMaxResolution failed for va_profile 3 and entrypoint 1
[14580:14580:1122/230215.500753:ERROR:vaapi_wrapper.cc(464)] vaQuerySurfaceAttributes failed VA error: invalid parameter
[14580:14580:1122/230215.500757:ERROR:vaapi_wrapper.cc(334)] GetMaxResolution failed for va_profile 5 and entrypoint 1
[14580:14580:1122/230215.500761:ERROR:vaapi_wrapper.cc(464)] vaQuerySurfaceAttributes failed VA error: invalid parameter
[14580:14580:1122/230215.500765:ERROR:vaapi_wrapper.cc(334)] GetMaxResolution failed for va_profile 6 and entrypoint 1
[14580:14580:1122/230215.500769:ERROR:vaapi_wrapper.cc(464)] vaQuerySurfaceAttributes failed VA error: invalid parameter
[14580:14580:1122/230215.500772:ERROR:vaapi_wrapper.cc(334)] GetMaxResolution failed for va_profile 7 and entrypoint 1
[14580:14580:1122/230215.500777:ERROR:vaapi_wrapper.cc(464)] vaQuerySurfaceAttributes failed VA error: invalid parameter
[14580:14580:1122/230215.500780:ERROR:vaapi_wrapper.cc(334)] GetMaxResolution failed for va_profile 8 and entrypoint 1
[14580:14580:1122/230215.500785:ERROR:vaapi_wrapper.cc(464)] vaQuerySurfaceAttributes failed VA error: invalid parameter
[14580:14580:1122/230215.500794:ERROR:vaapi_wrapper.cc(334)] GetMaxResolution failed for va_profile 9 and entrypoint 1
[14580:14580:1122/230215.500798:ERROR:vaapi_wrapper.cc(464)] vaQuerySurfaceAttributes failed VA error: invalid parameter
[14580:14580:1122/230215.500802:ERROR:vaapi_wrapper.cc(334)] GetMaxResolution failed for va_profile 10 and entrypoint 1
vdpau_video: vaTerminate(): config ID 0x01000000 is still allocated, destroying
vdpau_video: vaTerminate(): config ID 0x01000001 is still allocated, destroying
vdpau_video: vaTerminate(): config ID 0x01000002 is still allocated, destroying
vdpau_video: vaTerminate(): config ID 0x01000003 is still allocated, destroying
vdpau_video: vaTerminate(): config ID 0x01000004 is still allocated, destroying
vdpau_video: vaTerminate(): config ID 0x01000005 is still allocated, destroying
vdpau_video: vaTerminate(): config ID 0x01000006 is still allocated, destroying
vdpau_video: vaTerminate(): config ID 0x01000007 is still allocated, destroying
vdpau_video: vaTerminate(): config ID 0x01000008 is still allocated, destroying
vdpau_video: vaTerminate(): config ID 0x01000009 is still allocated, destroying

hans20056 commented on 2017-11-14 20:46

Can confirm. Everything works fine now on the latest Linux 4.14. Thanks!

maximbaz commented on 2017-11-14 14:56

@hans20056 thanks to @alexlu there is a patch that fixes grey boxes. Seems to work for me as well. Feel free to try, install and restart chromium:

https://github.com/maximbaz/chromium-vaapi-bin/blob/libva-intel-grey-boxes-fix/libva-intel-driver-2.0.0-3-x86_64.pkg.tar.xz

alexlu commented on 2017-11-14 05:46

I just reported it to libva-intel-driver[1] with a mpv-reproducible example.
[1]: https://github.com/01org/intel-vaapi-driver/issues/297

maximbaz commented on 2017-11-13 22:25

You are absolutely right! It happens almost immediately upon changing quality, and doesn't seem to happen with fixed quality value.

Does anyone know if there is a way to replicate this "quality change" in mpv, so that we could easily report this issue with steps to reproduce that don't require custom chromium build? @alexlu have you maybe already reported this issue?

All comments