Package Details: chromium-vaapi 74.0.3729.157-1

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: 66
Popularity: 3.220646
First Submitted: 2016-07-09 09:44
Last Updated: 2019-05-15 08:33

Dependencies (47)

Required by (44)

Sources (10)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 ... Next › Last »

maximbaz commented on 2019-02-05 20:35

VP8/9 is supported, but whether it can be used depends on your hardware. By the way, I noticed today that with our new MojoVideoDecoder a 4k VP9 video lags just a little bit, while it doesn't in the previous build. CPU usage is approximately the same, and going just a little down in the resolution removes the lags - still annoying...

xuanruiqi commented on 2019-02-05 19:35

Does VP8/9 decoding not work at all, or would it just not use GPU acceleration?

clap22 commented on 2019-02-01 21:36

Working with latest amdgpu+mesa RX580. With --use-gl=egl no need for allow_rgb_configs workaround anymore.

Foreigncon commented on 2019-02-01 11:12

@kureta Thanks.

kureta commented on 2019-02-01 09:15

@Foreigncon According to my tests (GTX 960 using proprietary drivers) if #ignore-gpu-blacklist flag is enabled, MojoVideoDecoder is used, which is HW accelerated and the decoder targeted by this experimental Fedora patch. If the flag is disabled FFmpegVideoDecoder is used, which is also HW accelerated on my configuration.

Foreigncon commented on 2019-02-01 09:08

@maximbaz Thanks. I will wait for his answer.

maximbaz commented on 2019-02-01 09:03

Foreigncon: I've asked kureta to answer your question, I only tested on Intel GPU and confirm that the new patch brings back HW acceleration.

Foreigncon commented on 2019-01-31 20:40

@maximbaz Can you please tell me how it is working on Nvidia? Isn't it supposed to get blacklisted by default on Nvidia platforms and can be enabled by disabling gpu blacklist in chrome://flags?

maximbaz commented on 2019-01-31 19:40

Folks, I've noticed that the current patch no longer works on Intel GPU, I'm getting VpxVideoDecoder now - and I've confirmed with another Intel user that the problem is not local to my machine.

However the first patch that xsmile has shared is working fine, and moreover it seems to perform even a bit better! kureta has also confirmed that it works fine on Nvidia.

Does anyone object to switching the patch? If so, please let me know, otherwise I'll make one final clean build to confirm everything compiles and then update this package.

xsmile commented on 2019-01-31 02:34

I had some trouble after refreshing the old VA-API patch and used an experimental patch [1] from the Fedora repositories instead, which is currently in review. It works well with an Intel GPU. The stable version on the other hand is at [2], as others already have mentioned.

1: https://src.fedoraproject.org/rpms/chromium/pull-request/18#

2: https://src.fedoraproject.org/rpms/chromium/blob/master/f/enable-vaapi.patch