You are not logged in.
I am using a Skylake i7 with i965. I followed the guide at https://wiki.archlinux.org/index.php/Ch … celeration and I believe I have the `chromium-vaapi-bin` AUR package set up correctly to use HW acceleration for VP9 decoding.
Verifying my setup with playing Youtube, chrome://media-internals shows:
video_codec_name vp9
video_dds false
video_decoder MojoVideoDecoder
Which looks fine, but when I start Stadia (Google's cloud game streaming service), it shows:
video_codec_name vp9
video_dds false
video_decoder VpxVideoDecoder
What's possibly wrong with my setup, any hints or ideas?
Offline
SkyLake 6000-series Core CPUs do not support VP9.
You may be using the hybrid driver w/ i965 VA driver for chromium-vaapi. True VP9 support for Intel Graphics requires 7000-series and later.
Offline
SkyLake 6000-series Core CPUs do not support VP9.
You may be using the hybrid driver w/ i965 VA driver for chromium-vaapi. True VP9 support for Intel Graphics requires 7000-series and later.
oh wait, I double checked my cpu:
model name : Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
I believe that's a Kaby Lake then, right? That should work as expected?
Last edited by kjozsa (2020-01-05 07:05:50)
Offline
oh wait, I double checked my cpu:
model name : Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
I believe that's a Kaby Lake then, right? That should work as expected?
Yes, this CPU should work.
How do you know that Google Stadia support VAAPI? Even Google Chrome does not support VAAPI on Linux. Chromium-vaapi is a community effort.
Offline
How do you know that Google Stadia support VAAPI? Even Google Chrome does not support VAAPI on Linux. Chromium-vaapi is a community effort.
I'm not really familiar on this field, but I can't really interpret the question about Stadia supporting VAAPI. Stadia (as a service) simply sends a VP9 video stream which can be decoded either by software and hardware. I think if VAAPI support is set up correctly in Chromium, the decoding can be done by the gpu. What I don't see is how how Stadia's VP9 stream could be different to Youtube's VP9 stream.. hence my confusion shown in the first post
Offline
According to this article, you need to launch Stadia from browser but the claim was not verified. I am not a Google Stadia subscriber, so I can't verify the claim myself.
This issue shows intel_gpu_top VideoEngine activity even with VpxVideoDecoder, so very confusing.
Quite a number of reddit posts blamed Google Chrome of not supporting VAAPI in Linux version (input lag, CPU hog etc.) while launching Stadia from Google Chrome in Windows was playable.
Offline
I have an AMD Radeon RX 5700 XT and I also have the same problem...
Chromium can't use HW decode for VP9, but can do it for H264 because the Stadia Enhanced extension displays Hardware H264 (instead of Software VP9) in the Stream Monitor panel.
I hope these info could be of help to understand what's missing...
vainfo: VA-API version: 1.10 (libva 2.10.0)
vainfo: Driver version: Mesa Gallium driver 20.3.4 for AMD Radeon RX 5700 XT (NAVI10, DRM 3.40.0, 5.11.2-arch1-1, LLVM 11.1.0)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain : VAEntrypointEncSlice
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointEncSlice
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileVP9Profile0 : VAEntrypointVLD
VAProfileVP9Profile2 : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc
Last edited by tesfabpel (2021-03-24 19:08:58)
Offline