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.000022
First Submitted: 2020-01-27 20:21 (UTC)
Last Updated: 2022-01-04 21:58 (UTC)

Required by (25)

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

1 2 3 4 5 6 Next › Last »

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.

pc00per commented on 2022-07-22 11:24 (UTC)

@urbenlegend Right now the only way of hw decoding on a wayland session, is on firefox-beta with nvidia-vaapi-driver with the instructions provided in readme. It's funny that it doesn't use vdpau, but directly utilizes nvdec through nvidia-libs.

urbenlegend commented on 2022-07-22 05:43 (UTC)

@pc00per Using the flags you listed I was able to get VDAVideoDecoder to be used. Unfortunately, the --use-gl=desktop flag really messes with the browser framerate. It lowers my framerate from 120Hz to a weird stutery 45-50hz. If I don't use the --use-gl flag then all I get is a black screen. So close, but no cigar.

pc00per commented on 2022-06-28 22:02 (UTC)

@xuanruiqi @Terence Any chance whether it works on wayland ?

pc00per commented on 2022-06-10 22:33 (UTC) (edited on 2022-06-24 11:02 (UTC) by pc00per)

@DAC324 Ya you're right. It's blank without gl. ANGLE seems to mess with decoding here. Also had to explicitly --use-vulkan. Turning vulkan from the flags section seems to mess with acceleration.

DAC324 commented on 2022-06-10 17:18 (UTC) (edited on 2022-06-10 17:21 (UTC) by DAC324)

@pcooper Thank you very much for that update.

As for your previous quote

No need of use-gl=egl or desktop to disable ANGLE (unless you're on wayland) or forced gpu rasterization in general.

At least here, I need use-gl=desktop as otherwise, there will be no picture in the videos, they remain black with only audio being played. Also, --use-vulkan can be left enabled, it does not make any difference here.

pc00per commented on 2022-06-10 13:38 (UTC) (edited on 2022-06-24 11:06 (UTC) by pc00per)

@DAC324 Finally fixed it. Some notes to consider to successfully get a working VDAVideoDecoder.

  • Don't disable SkiaRenderer.
  • Must disable ChromeOSDirectVideoDecoder.
--use-gl=desktop
--use-vulkan
--enable-features=VaapiVideoDecoder,VaapiVideoEncoder,VaapiIgnoreDriverChecks
--disable-features=UseChromeOSDirectVideoDecoder 

DAC324 commented on 2022-06-03 07:57 (UTC) (edited on 2022-06-03 08:18 (UTC) by DAC324)

@pcooper: That's no surprise. Just check https://en.wikipedia.org/wiki/Nvidia_NVDEC for video codec support. You will encounter that the RTX3090 fully supports VP9 decoding.

The problem here is the difference between NVDEC and VDPAU. Chromium currently does not seem to support NVDEC but VDPAU (via this driver package here) instead. As already discussed however, this driver package lacks VP9 support to some extent.

Here's a better link about video codecs and hardware support: https://developer.nvidia.com/video-encode-and-decode-gpu-support-matrix-new

Of note, Nvidia very much likes to confuse its customers by their product numbering schemes. Great example: A GeForce GTX 750 Ti is not as one might guess a special edition of a GeForce GTX 750 but in fact, even inferior. While the GeForce GTX 750 is "Maxwell 2nd Generation", the GeForce GTX 750 Ti is "Maxwell 1st Generation" only, lacking a lot of support that the later chipsets have.

Fortunately, there is the chip number which appears to be still logical, with higher numbers indicating superior chipsets. So, instead of using that misleading product numbering scheme ("GeForce XXX Super Duper Whatever"), you must have a look at the chipset being actually used, and go from there.

pc00per commented on 2022-06-02 20:43 (UTC)

@DAC324 But this guy 3 months ago showed VDAVideoDecoder as working perfectly (https://i.imgur.com/sfjwVQN.jpeg) on his 3090. It's strange how he has got that kind of setup, as I've tried everything to get there but failed.

DAC324 commented on 2022-06-02 17:41 (UTC) (edited on 2022-06-02 18:27 (UTC) by DAC324)

@pcooper: The reason for that is surprisingly simple: Full VP9 hardware acceleration is only supported on GeForce GTX 1650 / MX450 or newer. Everybody having an older card, cannot use hardware acceleration for VP9 video playback, at least not on higher bit depths.

Source: https://en.wikipedia.org/wiki/Nvidia_NVDEC

Since I have an Nvidia NVIDIA GeForce GTX 750 Ti which at least supports 8-bit VP9 hardware acceleration, I apparently was misled previously by testing with inappropriate video specs :(