Package Details: libva-vdpau-driver-vp9-git r57.509d3b2-4

Git Clone URL: https://aur.archlinux.org/libva-vdpau-driver-vp9-git.git (read-only, click to copy)
Package Base: libva-vdpau-driver-vp9-git
Description: VDPAU backend for VA API. (Version with VP9 codec support)
Upstream URL: https://github.com/xuanruiqi/vdpau-va-driver-vp9
Keywords: chromium vaapi vdpau vp9
Licenses: GPL
Conflicts: libva-vdpau-driver, nvidia-vaapi-driver
Provides: libva-vdpau-driver
Replaces: vdpau-video
Submitter: Terence
Maintainer: Terence (xuanruiqi)
Last Packager: Terence
Votes: 16
Popularity: 0.000000
First Submitted: 2020-01-27 20:21 (UTC)
Last Updated: 2022-01-04 21:58 (UTC)

Required by (12)

Sources (1)

Pinned Comments

xuanruiqi commented on 2023-02-20 15:00 (UTC)

With the removal of --use-gl=desktop in Chromium 110, this extension is extremely brittle and effectively dead for many Chromium users. The new way of handling things in Chromium may further make any VDPAU-based solution impossible to support. If video acceleration is critical for you, the only solution might be to move to Firefox.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

pc00per commented on 2022-05-25 10:59 (UTC) (edited on 2022-05-25 10:59 (UTC) by pc00per)

@DAC324 There are still some users today who claim to have a working vp9 browser acceleration, but don't exactly tell us how they achieved on their Nvidia card...¯\_(ツ)_/¯

DAC324 commented on 2022-05-25 10:54 (UTC) (edited on 2022-05-25 10:55 (UTC) by DAC324)

@pcooper: chromium-vaapi is no longer needed as the VAAPI patch has made it in the stock Chromium.

If my memory serves me right, I already had VP9 hardware accelerated video decode working in Chromium but apparently, it got broken again. By the way, it does not matter if I have libva-vdpau-driver-chromium or libva-vdpau-driver-vp9 installed - it simply does not work anymore :(

pc00per commented on 2022-05-25 10:26 (UTC)

I donno how this is possible. AUR version of chromium-vaapi does not even compile. It's even flagged outdated. I donno what other browsers come with vaapi supported, I've literally tried every browser from pacman, aur binary, snap & flathub repos too. None of them have working vp9 Decoder (atleast for me). Tried searching every corner of the internet & Nvidia Linux forum discussions. Tried all kinds of flags, enabling vaapi, gl desktop, disabling ozone, etc etc. It's always been VpxVideoDecoder for me.

DAC324 commented on 2022-05-25 09:39 (UTC) (edited on 2022-05-25 09:40 (UTC) by DAC324)

No VP9 support in Chromium with this driver:

As soon as a VP9 video is opened, VpxVideoDecoder is chosen (i.e.,software decoding). 

00:00:00.136    info    "Failed to initialize DecryptingVideoDecoder"
00:00:00.136    info    "Failed to initialize VDAVideoDecoder"
00:00:00.137    kIsVideoDecryptingDemuxerStream false
00:00:00.137    kVideoDecoderName   "VpxVideoDecoder"
00:00:00.137    kIsPlatformVideoDecoder false
00:00:00.137    info    "Selected VpxVideoDecoder for video decoding, config: codec: vp9, profile: vp9

Hardware accelerated video decoding currently only works for h.264 videos, using VDAVideoDecoder. There is VAAPIVideoDecoder available for Linux, but it just does not work (yet?). See https://bugs.chromium.org/p/chromium/issues/detail?id=1236697 for a discussion about it.

pc00per commented on 2022-04-30 23:10 (UTC) (edited on 2022-04-30 23:14 (UTC) by pc00per)

@gardotd426 The last time you showed your decoder information (https://i.imgur.com/sfjwVQN.jpg) was probably using VDAVideoDecoder. Mine's using VPXVideoDecoder (https://ibb.co/PYb47dk). So I'm not sure how I progress further to resolve this issue.

MarsSeed commented on 2022-03-30 08:49 (UTC)

Hi,

This should conflict with libva-nvidia-driver and nvidia-vaapi-driver-git.

Both are created from the same source and both provide nvidia_drv_video.so like this package.

The difference of course is that this package is a VA-API frontend with VDPAU backend, while the above mentioned two are VA-API frontends with NVDEC backend and therefore are NVIDIA-only.

pc00per commented on 2022-02-05 21:01 (UTC)

@gardotd426 Ah I've forgot to pass --enable-features=VaapiVideoDecoder to chromium. Apologize for this mate XD.

gardotd426 commented on 2022-02-02 06:17 (UTC)

@pcooper yes man, I've been using this project/package for over a year and a half, since you also needed chromium-vaapi before the regular Chromium, Chrome, and Brave repo packages supported vaapi GPU video decoding. I have GreenWithEnvy up at all times on my second monitor, and can literally watch the Decoder % bar go from 0% to 5-10% (depending on which resolution I'm watching the video at). These videos are in 1440p or 4K, which H264 doesn't support. This project doesn't work with av1. So it can only be vp9, but just to double the confirmation, I've regularly (including 6 times today on 6 different videos) checked the "Stats for Nerds" on YouTube and saw that it was using VP9 while it was being hardware-decoded.

To triple confirm, I've also used the developer tools to confirm that the video decoder is VDAVideoDecoder and that "Hardware Decoder" says "true."

Here you go, look for yourself: https://i.imgur.com/sfjwVQN.jpg

I hope that settles that question, because I mean, it's objective proof using every possible metric.

pc00per commented on 2022-02-02 03:43 (UTC)

@gardotd426 you sure you played vp9 streams specifically?

gardotd426 commented on 2022-02-02 03:41 (UTC)

@pcooper no, I can't reproduce. GPU accelerated video decode is working on YouTube with Chromium, Brave, and Chrome. Just checked.

What are your flags in ~/.config/chromium-flags.conf? Or are you using any flags at all? If not, then what have you set in chrome://flags?

« First ‹ Previous 1 2 3 4 5 6 Next › Last »