Package Details: chromium-vaapi 62.0.3202.62-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: 4.140470
First Submitted: 2016-07-09 09:44
Last Updated: 2017-10-18 16:43

Dependencies (39)

Required by (29)

Sources (8)

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

maximbaz commented on 2017-10-18 17:33

I haven't tried, but I don't think so, the proposal [1] to revert offending patch in mesa was unfortunately left without attention.

[1]: https://lists.freedesktop.org/archives/mesa-stable/2017-September/007116.html

digitalone commented on 2017-10-18 17:29

Thank you @maximbaz. Is this new version working with the latest mesa packages?

maximbaz commented on 2017-10-18 16:46

It compiled, CPU usage is still low, so everything is hopefully fine :)

xsmile commented on 2017-10-18 10:30

@maximbaz: I did the same and I wait for my build to finish. Yours will probably be faster.

maximbaz commented on 2017-10-18 10:23

@xsmile I'm upgrading to v62 now, the chromium-libva-remove.patch does not apply anymore, as if it was already merged in upstream - could you or someone knowledgeable confirm?

Otherwise, I took the latest revision 14 from https://chromium-review.googlesource.com/c/chromium/src/+/532294 (it can be applied finally without modifications) and running a build now. If it succeeds, will update the package.

kayaogz commented on 2017-10-07 16:48

I just patched libva-intel-driver by changing those two lines in the source code just as alexlu proposed. I confirm that everything works fine now with the latest linux kernel (4.13.4-1).

Strangely, however, mpv plays 4k content just fine whereas there are still dropped frames using chromium on youtube. It is better than no acceleration, but is not on par with mpv.

Thanks @alexlu!

maximbaz commented on 2017-10-06 10:56

Awesome news, huge thanks @alexlu for following up on this!

alexlu commented on 2017-10-06 05:15

@maximbaz @kayaogz
it turns out that VP9 decoding issues are caused by libva-intel-driver[1] and a patch[2] fixes it has been merged into master.
I just built libva-intel-driver with [2] (using asp) and I comfirmed that VP9 videos can be playback without problems on linux 4.13.

[1]: https://github.com/01org/intel-vaapi-driver/issues/262
[2]: https://github.com/01org/intel-vaapi-driver/pull/263

alexlu commented on 2017-10-05 16:02

I guess it is normal.
With adblock/etc turned off, a youtube tab will have cpu loads around 20% even not start playing the video. You may want to try downloading a vp9/avc video to local filesystem and try it again.

indjera commented on 2017-10-04 20:23

yes chrome://media-internals shows (video_codec_name:vp9,video_dds:false,video_decoder:GpuVideoDecoder,width:1280) CPU(i5 7200u) usage is around 25% - 30% on 720p

All comments