Package Details: chromium-vaapi 71.0.3578.98-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: 62
Popularity: 4.552630
First Submitted: 2016-07-09 09:44
Last Updated: 2018-12-13 21:31

Dependencies (48)

Required by (37)

Sources (8)

Pinned Comments

Terence commented on 2018-11-13 23:15

[Nvidia users PLEASE READ]

To get hardware acceleration working, you also have to install https://aur.archlinux.org/packages/libva-vdpau-driver-chromium

Disclaimer : VP8/9 video decoding will not work!

GeForce GTX 750 SE and after support HEVC and VP9 video decoding but VDPAU,the only VAAPI backend available for Nvidia users with libva-vdpau-driver, doesn't support VP8/9.

4 ways to solve this:

Latest Comments

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

maximbaz commented on 2018-10-29 16:57

@Terence: unfortunately there isn't a place really, we are using what we called "an official patch", but it's not really backed up by Google. You can try to post a feedback there, but I don't think your comment will be addressed.

@ForeignCon: Everyone in the world who is tracking HW-acceleration issue is following the linked patch, so if any updates appear (fixes, improvements), that is the patch that will be updated first. Other distros have chromium package that includes that same patch. I would therefore prefer to stick to it for now, enabling the flag is easy anyway. Moreover it seems this patch you mention is mostly about cosmetic differences, I believe it is more relevant for code review than for end users. But I've seen this mentioned on the code review, so maybe the two patches will become the same one anyway.

ForeignCon commented on 2018-10-29 16:37

@darkbasic Check "Video Acceleration Information" section and log messages below it.

Btw @maximbaz Can you build with this patch please? https://github.com/biswasab/chromium-vaapi/raw/master/enable-vaapi.patch

It makes use of the existing flags instead of creating a one and also enables video acceleration by default.

There are also patches from russianfedora which fixes the libva version differences error but I haven't tested it.

Terence commented on 2018-10-29 16:36

@maximbaz then this must be an nvidia issue. Who should I report this to?

maximbaz commented on 2018-10-29 16:35

FWIW, VP9 HW decoding definitely works for me

Terence commented on 2018-10-29 16:32

I'm wondering why hardware video decoding works for h264 but not VP9. Chrome on windows is able to do it for VP9 too.

darkbasic commented on 2018-10-26 16:35

render_id: 105 player_id: 192 origin_url: https://www.youtube.com/ frame_url: https://www.youtube.com/watch?v=FfRN206symc&t=2612s frame_title: (12) YouTube url: blob:https://www.youtube.com/87199995-f6fa-404b-84dd-2c865d6d55dd info: Selected video track: [] pipeline_state: kPlaying found_video_stream: true video_codec_name: h264 debug: ISO-BMFF container metadata for video frame indicates that the frame is a keyframe, but the video frame contents indicate the opposite. found_audio_stream: true audio_codec_name: aac audio_dds: false audio_decoder: FFmpegAudioDecoder is_platform_audio_decoder: false seek_target: 2612 video_dds: false video_decoder: FFmpegVideoDecoder is_platform_video_decoder: false duration: 4129.041995 audio_buffering_state: BUFFERING_HAVE_ENOUGH video_buffering_state: BUFFERING_HAVE_ENOUGH height: 1080 width: 1920 for_suspended_start: false pipeline_buffering_state: BUFFERING_HAVE_ENOUGH event: PLAY

Why do I still get FFmpegVideoDecoder?

Graphics Feature Status Canvas: Hardware accelerated Flash: Hardware accelerated Flash Stage3D: Hardware accelerated Flash Stage3D Baseline profile: Hardware accelerated Compositing: Hardware accelerated Multiple Raster Threads: Enabled Native GpuMemoryBuffers: Hardware accelerated Out-of-process Rasterization: Hardware accelerated Hardware Protected Video Decode: Hardware accelerated Rasterization: Hardware accelerated Skia Deferred Display List: Disabled Skia Renderer: Disabled Surface Synchronization: Enabled Video Decode: Hardware accelerated Viz Service Display Compositor: Disabled WebGL: Hardware accelerated WebGL2: Hardware accelerated Problems Detected Viz service display compositor is not enabled by default. Disabled Features: viz_display_compositor Skia renderer is not used by default. Disabled Features: skia_renderer Skia deferred display list is not used by default. Disabled Features: skia_deferred_display_list

I DO have video decoding enabled...

maximbaz commented on 2018-10-25 22:27

Thank you very much, applied and compiling now, will update tomorrow if the result is successful ;)

foutrelis commented on 2018-10-25 09:54

Had the same issue with extra/chromium; you can use the following patch from Gentoo:

https://git.archlinux.org/svntogit/packages.git/plain/trunk/chromium-harfbuzz-r0.patch?h=packages/chromium

coldreaver commented on 2018-10-24 07:05

Compiling fails with the new harfbuzz for me (2.0.2-1), if I downgrade harfbuzz (1.9.0-1) everything works fine. Prolly not problem at your side but chromium needs api changes, since its calling deprecated functions.

maximbaz commented on 2018-10-18 12:25

Thank you everyone once again, success is confirmed, I updated chromium-vaapi and chromium-vaapi-bin :)