I have a desktop PC (Core i7-3770 with Nvidia GTX 780 ti) that does not support Hardware Accelerated Decoding in Linux (Kubuntu, Manjaro). I am aware that this computer can only decode H.264, and does not Support VP9. However, with the Stadia Enhanced Chrome-App, I can force H.264 Video, and it will show "Software H.264" is running.
I have a new Desktop PC now, a Minisforum HX90 - This has a Ryzen 9 5900HX, with built in AMD Vega 8 Graphics. Again, there is no Hardware Accelerated Decoding available in Linux.
I have tested both of these computers with Windows 10 (and 11 on the Minisforum HX90). Acceleration in Chrome (Google, Brave, and Edge) works "out of the box" with no problems what-so-ever. The i7/GTX780ti uses H.264 Hardware decoding by default, and the Minisforum HX90 uses Hardware VP9 by default.
I actually own an Asus Chromebook C425 - It runs Stadia wonderfully, along with Hardware VP9 (and H264) decoding.
Chrome OS is a Linux based OS, so it's not the fault of the hardware manufacturers. This computer runs an Intel Core m3 Processor.
Sooooooo.....
Why doesn't the Chrome Browser for Desktop Linux have Hardware Based Decoding?
I don't know much about Linux, but I do know that in terms of drivers it's pretty lacking, generally. Could it be that the drivers just don't support it for Linux?
As for why it does work on ChromeOS, I'm pretty sure that Google or the manufacturers of the devices have to include drivers which meet certain requirements (i.e. hardware accelerated h 264 decoding).
Hi @Shibblet
It is somehow disabled by Google. I also run linux but with a AMD device. You should have Chrome 92 at minimum.
If I run chrome this way press ALT+F2 to run a command: google-chrome-stable --use-gl=desktop --enable-features=VaapiVideoDecoder
Found online that could work Intel also or this one: google-chrome-stable --enable-features=VaapiVideoDecoder --use-gl=desktop --disable-features=UseOzonePlatform
My apologies for the frustration here. But no one seems to understand this actual problem.
Using "--use-gl=desktop" and "--enable-features=VaapiVideoDecoder" doesn't actually solve the problem. It only allows for "Hardware Assisted" decoding. You may get Hardware based decoding in YouTube with these features, but they don't do ANYTHING for Stadia.
I do not know why Google keeps removing Hardware Acceleration from their Linux Browser, but for some reason, they don't want to support it!
Some like to blame Nvidia/AMD/Intel, others like to blame Google/Chromium. In the mean-time, Linux users wait for nothing to happen. There's no forward motion here! Just a flippin' blame game.
Here's a great solution!!! Make a Linux Client for Stadia that uses HW Acceleration... I mean, if you don't want to update your browser to do so... Come on Google... do SOMETHING.
And it's not like this hasn't been brought up before. I submit these links:
April 26th, 2021: https://community.stadia.com/t5/Stadia-on-Chrome/Hardware-Acceleration-on-Chrome-for-Linux/m-p/59496...
June 21st, 2021: https://community.stadia.com/t5/Stadia-General/Stadia-on-Linux-How-about-Chrome-VLC/m-p/63341#M26704
Hi @Shibblet
I am not sure if we can help within this community board.
Did you try to reach out to the Chrome community?
It is pretty strange Chrome doesn't support this while it is possible. ![]()
well gess what I cant even play any games but yes i agrre