Package Details: chromium-vaapi 75.0.3770.90-3

Git Clone URL: (read-only)
Package Base: chromium-vaapi
Description: Chromium with VA-API support to enable hardware acceleration
Upstream URL:
Keywords: browser web
Licenses: BSD
Conflicts: chromium
Provides: chromium
Submitter: samcv
Maintainer: OneObsession (maximbaz)
Last Packager: maximbaz
Votes: 71
Popularity: 6.229244
First Submitted: 2016-07-09 09:44
Last Updated: 2019-06-18 11:51

Dependencies (48)

Required by (47)

Sources (10)

Latest Comments

« First ‹ Previous ... 33 34 35 36 37 38 39 40 41 42 43 ... Next › Last »

olive commented on 2017-08-18 14:26

Would it be difficult to make a package that can be installed alongside the official chromium? (This is what the google chrome on the AUR does). Because this software is still experimental, it will be great if we can keep the official stable chromium installed.

olive commented on 2017-08-17 09:09

The latest software (I used the -bin version) works great both on my desktop (AMD 6570 with xf86-video-ati and vaapi via libva-vdpau-driver) and on my laptop (integrated GPU from Core(TM) i5-2450M). I need to enable the two flags mentioned by maximbaz as well as "Override software rendering list" and install the h264ify youtube extension.

Let's hope that some day, we will have this supported in the official release.

maximbaz commented on 2017-08-16 19:20

**IMPORTANT**: We are using new VAAPI patch now. Enable new flags: "Hardware-accelerated video" and "Hardware-accelerated mjpeg decode for captured frame".

Please report to if you have issues with the new patch, there is still time go get things fixed before it is merged in upstream.

The old patch is still available, update PKGBUILD to use it if you need to.

maximbaz commented on 2017-08-16 11:25

The build is running now, when it completes in a couple of hours I'll update both this and -bin packages. This package will contain two vaapi patches, the old one (that works only for Intel) and the new one (based on v10). By default PKGBUILD will apply the new patch, but if someone cannot use it, it is a one line fix to switch to the old patch. The -bin package will contain only the binary based on the new patch (sorry :)).

Just like @xsmile said in chromium-dev, I also encourage everyone to report any issues with the new patch to while the code review is still open.

In a few days or so we should probably mention there that quite many people have tried out that patch, hopefully that will speed up getting the patch merged in upstream.

xsmile commented on 2017-08-16 09:31

Versions 10 and 12 of the patch should hardly have any functional differences. The later versions are mainly based on a newer codebase.

See for an issue with NVIDIA in connection with this patch.

olive commented on 2017-08-16 08:58

I have tested the new package proposed by maximbaz both with a Desktop (Intel Corei3-3240 with a radeon HD6570 with the opensourse xf86-video-ati driver, vdpau and vaapi with libva-vdpau-driver) and a laptop (Core(TM) i5-2450M with the integrated GPU and vaapi, no vdpau). I have enabled "Hardware-accelerated video" "Hardware-accelerated mjpeg decode for captured frame" and "Override software rendering list" and installed the h264ify youtube extension.

I have tested both in chromium and directly with mpv.

The result is great on the Desktop (from ~20% per core to ~5%), comparable to what I get in mpv. On the laptop the result is mitigated (from 40%-45% per core to 30%-35%). For the laptop mpv do better by diding the CPU time by a further factor 2.

Update: The chromium-vaapi-bin from the AUR seems to work perfectly in the laptop (Intel card). So it seems we indeed do need different packages for different graphic cards.

OneObsession commented on 2017-08-16 06:59

Yes, it looks that Googles own patch is
working very well. We can try the newest
patchset and see how it works. At the moment, I am a little bit busy with exams, so feel free to update the package.

digitalone commented on 2017-08-15 07:35

@olive I downloaded the package built by @maximebaz and installed it.
Previously HD videos on YouTube didn't play smoothly and CPU usage was on 80-90%. Now they play smoothly and CPU is about 30-40%.

maximbaz commented on 2017-08-15 07:03

@OneObsession I tend to use the new patch (ideally v12 instead of v10) for the update to 60.0.3112.101, since it is helping so many more people and there is no difference for Intel owners. Also, if after the update some people will come here reporting new issues with the latest version, this would be a useful direct feedback for the creator of the patch to fix these issues. So far I haven't heard any case when things stopped working on a new patch, but not many people actually tried it. What do you say?

maximbaz commented on 2017-08-15 06:50

@olive yes, I do see a big decrease in CPU usage. Right now two patches exist, this and -bin packages are built on an older patch that works only on Intel. The other patch is more recent and seems to work on other graphic cards as well, I built a custom binary for it. The link is this:

See comment from @digitalone below on what to do after you install the package, i.e. make sure two flags are enabled and you have "h264ify" extension installed. You can see if GPU is used on chrome://media-internals/ while a video is played, the expected value is "video_decoder: GpuVideoDecoder". Check what value you see now, install this other package, configure flags and extension, and check again :) And please share your results.