Package Details: chromium-vaapi 77.0.3865.120-2

Git Clone URL: https://aur.archlinux.org/chromium-vaapi.git (read-only)
Package Base: chromium-vaapi
Description: Chromium with VA-API support to enable hardware acceleration
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: 84
Popularity: 4.338706
First Submitted: 2016-07-09 09:44
Last Updated: 2019-10-14 19:00

Dependencies (49)

Required by (51)

Sources (12)

Pinned Comments

maximbaz commented on 2019-07-18 13:19

This package is compiled with 'use_vaapi=true', but you need to pass --ignore-gpu-blacklist if you want to enable hardware video acceleration using VA-API.

Latest Comments

« First ‹ Previous ... 37 38 39 40 41 42 43 44 45 46 47 ... Next › Last »

buttcake commented on 2017-08-08 12:37

@maximbaz, on xf86-video-ati with libva-mesa-driver chromium-vaapi starts but will not display anything but then again I have an older video card so I guess I'll have to wait for that patch to mature a bit. Thanks for your effort.

maximbaz commented on 2017-08-06 23:49

For those keen on trying out a new patch (thanks @xsmile!), I've placed the compiled package here:

https://github.com/maximbaz/chromium-vaapi-bin/raw/new-patch/new-patch/chromium-vaapi-60.0.3112.90-1-x86_64.pkg.tar.xz

I haven't seen any difference so far on my laptop with Intel (it is equally good), but the new patch does work on the AMD laptop :) I'll be using this package over the following days to see if I can spot some bugs.

Give it a try and share your results. I think it makes sense to also share testing results on the code review thread ( https://chromium-review.googlesource.com/c/532294 ), hopefully that will increase developers' confidence and the patch will be faster merged in the official build.

xsmile commented on 2017-08-06 19:57

@maximbaz:
See https://raw.githubusercontent.com/xsmile/inox-patchset/7df2994bf5f57f39b361377b10fb3b0f40a6ce68/chromium-vaapi.patch. This is based on version 10 of the official patch (https://chromium-review.googlesource.com/c/532294/10) with minor changes to make it work with current stable versions of Chromium.

It adds two new options named 'Hardware-accelerated video' and 'Hardware-accelerated mjpeg decode for captured frame' you can enable at chrome://flags.

maximbaz commented on 2017-08-06 16:46

Does anyone have an adapted patch for chromium 60? I can build an alternative binary for everyone who wants to give it a try, and I also have a laptop with AMD where I could test that patch.

buttcake commented on 2017-08-06 16:26

The official patch also doesn't contain any intel specific code. This would allow chromium-vaapi to work with all video cards.

OneObsession commented on 2017-07-27 13:55

@xsmile interesting, i think i read something like this on phoronix. Still looks
very experimental though. I would like to see more feedback on this topic.

xsmile commented on 2017-07-27 12:15

Consider using the official commit to enable VAAPI. It works well with 60.0.3112.78 after adjusting the patch.
https://chromium-review.googlesource.com/c/532294/

OneObsession commented on 2017-07-26 19:59

@maximbaz yeah that makeflag is just for fun and for personal use only.

maximbaz commented on 2017-07-26 19:52

I've read enough to understand that this is a change in /etc/makepkg.conf and not PKGBUILD, and the difference is probably negligible for most users as everything from official sources comes pre-compiled without this flag anyway. Nevermind me then, and I'll update the binary very soon :)

maximbaz commented on 2017-07-26 19:36

So I'm all curious now, how much of perf difference do you see with march=native, how do you compile it (do you modify PKGBUILD manually every time), and does it make sense to add it to PKGBUILD for everyone? It seems to be generally a good thing to always include march=native when one compiles for themselves.