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 (13)

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-02-02 00:18 (UTC)

I got broken white screen in youtube while decoding vp9. Anyone got the same? What's the solution for this?

account60217652 commented on 2022-01-23 13:08 (UTC)

If someone have high frame rate monitor (for example 144 or 165 Hz) and experiencing chromium bug 1200167 I made aur package for temporary solution.

gardotd426 commented on 2022-01-13 06:42 (UTC)

Shit. My bad, you're correct. However VDPAU AV1 decode support was added to 510, so it should be trivial to add to this driver, and decoding any AV1 videos in something like VLC or MPV should use hardware decoding now.

But IIRC, using this package, h264 didn't work with video decode previously, it only worked if the codec was VP9. Now it works with H264 too (without h264ify).

Shished commented on 2022-01-13 06:35 (UTC)

avc1 is H264 afaik.

gardotd426 commented on 2022-01-13 06:33 (UTC)

So, some awesome (in my opinion) news.

I don't know if this package is required for this or not, but now starting with the new 510 branch Nvidia driver, even AV1 decode use GPU accelerated video decoding. I just pulled up an AV1 test video (and confirmed it was using "avc1" as the codec in the "Stats for nerds" option), and sure enough it instantly used GPU decoding as confirmed by GreenWithEnvy.

So it's not just VP9 now, even AV1 uses hardware video decoding on Nvidia. I think this is amazing news.

gardotd426 commented on 2022-01-04 23:28 (UTC)

I mean the audiences are completely conflicting. nvidia-vaapi-driver is for people that want to attempt to use VAAPI to get hardware accelerated video decode in Firefox specifically (and pretty much nothing else).

Meanwhile, libva-vdpau-driver-vp9-git is for people that want hardware-accelerated video decode in Chrome/Chromium/Brave, and not just for YouTube, but for things like Stadia, GeForceNOW, Xcloud, etc.

How many people fall into both camps? How many people use both chrome and firefox in the first place? Basically you're going to be in either one use-case or the other, and never both, so considering that, and considering that removing the symlink (instead of making the packages conflict) would mean that all users would now have to use an ENVVAR to get HW accel video decode in Chromium-based browsers, then my vote-I-don't-have-a-right-to is that these packages are conflicts and not to remove the symlink.

Terence commented on 2022-01-04 22:02 (UTC)

I added it to the conflicts. Let me know if anything else is required or if I need to change this in the future.

afader commented on 2022-01-04 21:21 (UTC)

Can confirm on brief testing that using this driver with vdpau works better than the nvidia-driver-vaapi-git for now.

gardotd426 commented on 2022-01-04 19:53 (UTC)

After further investigation, I think Terence should add a "conflict" with that new package, until it's actually in a remotely stable state. The GitHub for nvidia-vaapi-driver itself says:

This is an VA-API implementation that uses NVDEC as a backend. This implementation is specifically designed to be used by Firefox for accelerated decode of web content, and may not operate correctly in other applications.

It's currently in early development, so don't expect it to work well.

And it's explicitly for Firefox, and nothing else.

Until it's ready, it should be added as a conflict, and maybe when it's actually production-ready (if that ever happens), the symlink can be removed

gardotd426 commented on 2022-01-04 19:53 (UTC)

After further investigation, I think Terence should add a "conflict" with that new package, until it's actually in a remotely stable state. The GitHub for nvidia-vaapi-driver itself says:

This is an VA-API implementation that uses NVDEC as a backend. This implementation is specifically designed to be used by Firefox for accelerated decode of web content, and may not operate correctly in other applications.

It's currently in early development, so don't expect it to work well.

And it's explicitly for Firefox, and nothing else.

Until it's ready, it should be added as a conflict, and maybe when it's actually production-ready (if that ever happens), the symlink can be removed

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