Package Details: chromium-vaapi 77.0.3865.120-2

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: 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 ... 40 41 42 43 44 45 46 47 48 49 50 ... Next › Last »

agm28011997 commented on 2017-06-22 09:40

i am warning about use the last patch for chromium vaapi other, the patch fix the problem of chromium disabling the hardware acceleration but not the vaapi use problem, in chrome : media-internals not show gpuvidedecoder like in my intel graphics card.. for that reason, the patch is not fixing the problem and build a normal chromium without accel(tested by me in a few emails with samcv and confirmated with the link of chrome)
Sorry for this, but i have to tell that the users of amd( and maybe nvidia too) like me in one of my computers, have to wait for someone to apply a good patch or it never have hardware accel.. a shame for chrome and firefox to not to have but it is the reality, the only browser hat have accel with intel and a patch is chromium, out of this there isn't any browser more, you can only use mpv with smplayer for view videos..

maximbaz commented on 2017-06-21 16:25

That makes sense :)

I was actually thinking to look into creating maybe a Travis build job, that would automatically compile the package and release you from this burden of having to do it every time - I'll let you know if I find some way to achieve this.

But this would still not help with other GPUs, if someone interested helps with getting chromium-vaapi-other patch up to date, I might be able to plug it in this build job as well.

OneObsession commented on 2017-06-21 16:15

I assume ArchCN is using AUR as source. So their vaapi patch should be the same
as ours because we source the chromium-dev package.

I didn't have time to look at the chromium-vaapi-other patch hence i don't know
how many modifications are required to make it work. Also, I can only test on
Intel Graphics and not on other graphic cards. And i certainly do not want to
compile it several times to make the patch work for other brands.

maximbaz commented on 2017-06-21 07:48

I'm asking out of curiosity:
- Does chromium-dev-vaapi from ArchCN support other GPUs, or also only Intel?
- What happened to the chromium-vaapi-other patch, was it lost, or it is fully incompatible with recent Chromium and actually requires full rewrite?

OneObsession commented on 2017-06-21 07:27

@bugsmanagement currently, the vaapi patch only works with intel graphic cards.

Next time i'll change the description.

bugsmanagement commented on 2017-06-21 05:53

I recall it mentioned somewhere here that you might need chromium-vaapi-other for AMD users? Is that still relevant?

maximbaz commented on 2017-06-17 18:02

Amazing, thank you so much!

OneObsession commented on 2017-06-17 17:52

@maximbaz done :)

maximbaz commented on 2017-06-17 14:32

I created the AUR package chromium-vaapi-bin, seems to work :)

@OneObsession you are added as maintainer there as well. Could you please update the binary to 59.0.3071.104, if you have it compiled? So that versions of chromium-vaapi and chromium-vaapi-bin match, and also to test that you have access to everything.

maximbaz commented on 2017-06-17 11:10

I created the repo and sent you a request for collaborator access:

Will you create the AUR package, or should I do it? My main request for you is to keep updating the binaries in that git repo :)