cancel
Showing results for 
Search instead for 
Did you mean: 

Shibblet's Posts

Well, after a bunch of trying, I have been able to get Hardware Acceleration to work in Linux for YouTube with the "h264ify" extension.  Basically, this extension tells YouTube to send an H.264 Strea... See more...
Well, after a bunch of trying, I have been able to get Hardware Acceleration to work in Linux for YouTube with the "h264ify" extension.  Basically, this extension tells YouTube to send an H.264 Stream (limited to 1080p 60fps, of course) so that my video card can decode it. Now, if I tell Stadia to use H.264 instead of VP9 (Stadia Enhanced), it still uses Software Decoding.  Even after I got it to work, it still doesn't work? Any idea why it works in YouTube, but doesn't work in Stadia?
That's my point.  It does work with VAAPI, but that doesn't use the Hardware Decoder built on the Card, it's more of a "Hardware Assisted" decoding, and it apparently only helps with extending batter... See more...
That's my point.  It does work with VAAPI, but that doesn't use the Hardware Decoder built on the Card, it's more of a "Hardware Assisted" decoding, and it apparently only helps with extending battery life on laptops, but doesn't make much a difference for desktops. VDPAU is useful for both Nvidia and AMD Graphics cards, and I am pretty sure it works with Intel HD Decoders as well.  VDPAU not only decodes H.264, but can also be used for the current VP9.  I know my graphics card (GTX 780ti) only uses H.264. With hardware decoding, this would eliminate any "decoding" problems on my side, and smooth out game play.  My decode time is too high, and my games keep dropping from 1080p to 720p.  You know, the service quality that I am paying for... The ultimate solution here is to either add all of the above to the Chrome Browser, or make a Stadia Client application for Linux.  Although, I have also suggested a different solution that would work immediately without having to go that next step. To be honest, I am sorry that I keep making a big deal about this, but this situation needs to be resolved, and it seems as if Google doesn't even acknowledge that it's an issue.  And again, everybody seems to only be making excuses as to why it cannot be done. Simply put, if my Asus 425C Chromebook can handle HW Decoding, then it can be done in ANY Desktop Linux.
Except that it doesn't actually work. I'll point you toward a post in a different forum:  Nvidia / GPU Video Acceleration (ubuntuforums.org) It only "assists" with decoding.  What Linux users need ... See more...
Except that it doesn't actually work. I'll point you toward a post in a different forum:  Nvidia / GPU Video Acceleration (ubuntuforums.org) It only "assists" with decoding.  What Linux users need is VDPAU support, so that the built in Video Decoder on our video cards will actually decode the incoming stream.
I did what you asked: How do we enable Video Acceleration with YouTube & Stadia in Linux? - Google Chrome Community However, I'd like to know why this is such an issue with Linux.  I have an Asus C... See more...
I did what you asked: How do we enable Video Acceleration with YouTube & Stadia in Linux? - Google Chrome Community However, I'd like to know why this is such an issue with Linux.  I have an Asus Chromebook C425, with an Intel Core M3 Processor.  Hardware VP9 is supported, right out of the box.  No questions, it all just works.  No "enabling" VA-API, or wrappering VDPAU, etc... If it works so readily on a Chromebook (which is a distribution of Linux), why isn't this available for Desktop Linux? Why is this so difficult to support?  Do you know what this would do in the Linux community if HW Acceleration was supported?
Can someone please explain to me why Hardware Acceleration works on my Asus C425 Chromebook with an Intel Core M3 Processor, and not in other Linux distributions without having to spend hours on fart... See more...
Can someone please explain to me why Hardware Acceleration works on my Asus C425 Chromebook with an Intel Core M3 Processor, and not in other Linux distributions without having to spend hours on farting around with drivers just to get a weak comparison? What the heck?
So... here is a solution for you Google.  Stadia on Linux currently does not have "great" hardware support for Hardware Accelerated Decoding.  This doesn't directly come down to having Hardware H.264... See more...
So... here is a solution for you Google.  Stadia on Linux currently does not have "great" hardware support for Hardware Accelerated Decoding.  This doesn't directly come down to having Hardware H.264 or VP9, it comes down to driver issues, and the like.   NVIDIA owners can enable (what I call) Hardware Assisted Decoding with VA-API / VDPAU wrappers that (kind of) decode the video a bit faster, but still do not take advantage of the internal video decoder.  This is not just a Stadia issue, but also an issue with YouTube, and other Video Services on-line. Now, VLC Player uses VDPAU, and decodes video directly through the Hardware Video Decoder on our Video Cards.  You can go to YouTube, and copy the link directly into VLC, and it will play it back with Hardware Decoding via VDPAU. So... Follow with me here.   Why can't Linux users go to Stadia.com, log-in, and then instead of playing the video directly in the browser, have a link they could use to copy into VLC, and use the stream there... Hardware Decoded? Obviously, we would still need the browser window open for navigating our libraries, purchases, and controller connections, but that could run in the background while the game video and audio streams to VLC.   How hard would this be?  This would create a major solution for Linux users, and probably get you more subscriptions/purchases.  When Steam assisted the Wine project, and came up with Proton, it was a MAJOR boost to the Linux community, and they are now selling more games as a result. What about it Google?  Can you do this?  Seems a simple enough solution, right?
I'd like to understand what you are saying, but when applications such as "VLC Player" have VDPAU and VA-API built in, and work directly with the Nvidia Graphics Drivers, It's hard to believe that Go... See more...
I'd like to understand what you are saying, but when applications such as "VLC Player" have VDPAU and VA-API built in, and work directly with the Nvidia Graphics Drivers, It's hard to believe that Google can't do the same with Chrome.
So, I asked about this two weeks ago on this forum.  Is there any way that Hardware Acceleration can be enabled, and actually work, for Linux OS's? I have followed up with this "walkthrough," to abs... See more...
So, I asked about this two weeks ago on this forum.  Is there any way that Hardware Acceleration can be enabled, and actually work, for Linux OS's? I have followed up with this "walkthrough," to absolutely no avail. How To Enable Hardware Accelerated Video Decode In Google Chrome, Brave, Vivaldi And Opera Browsers On Debian, Ubuntu Or Linux Mint - Linux Uprising Blog I have also followed up with this link as well, as to use a "patched" Chromium Build (Beta & Dev) in order to get it to work. How To Enable Hardware Acceleration In Chromium On Ubuntu Or Linux Mint (VA-API Patched PPA Builds) - Linux Uprising Blog I mean, I have kept trying to fix this for over two weeks now, neither one of these seem to help, and nothing seems to work. I started a different thread 14 days ago... and there were a lot of helpful people... And I'd like to thank the people who helped.  Unfortunately though, there is still no solution. I really want this to be able to work under Linux, but unfortunately, without Hardware Acceleration, I am limited to 1280x720p, and my processor is pushing all the work.  One of the whole reasons I decided to go with Stadia, is because of the state of Linux Gaming as a whole.  Steam came up with Proton, which helps a lot, but still isn't 100% for all games. Stadia is 100% for all games!!!  It's the solution to this issue!  Unfortunately, it's been bottlenecked for Linux users who have to rely on their processor to decode 60fps 1080p Video, and Stadia likes to advertise that you can game without a beefy computer. So, the ultimate questions are:  Can Google add HW Acceleration to their Chrome Browser?  Can Google make a Stadia Client Program for Linux that has HW Acceleration built in?  Or does Google even care that Linux Users have to take a backseat because of their choice of OS? What can we do here?
It does work.  After some doing... I was able to get it to work for Hardware Video Acceleration.  However, it only works for things like YouTube.  It does not work for Stadia. Stadia still gives ... See more...
It does work.  After some doing... I was able to get it to work for Hardware Video Acceleration.  However, it only works for things like YouTube.  It does not work for Stadia. Stadia still gives me the "Software H.264" decoding.  With the Decode Time as high as it is, it will eventually bump the resolution down to 1280x720... I would love to get this to work.  Please someone, help!
Those are the PPA's and Chromium-Dev / Chromium-Beta builds that I was referring to.  I followed that list multiple times, and was never able to get things to work. It may be partially Nvidia's fa... See more...
Those are the PPA's and Chromium-Dev / Chromium-Beta builds that I was referring to.  I followed that list multiple times, and was never able to get things to work. It may be partially Nvidia's fault, but it seems to me that if someone can patch "Chromium" to add Hardware Acceleration, then that patch could be included in Chrome builds as well. That being said... Ubuntu is one of the most popular Linux Distros, especially with their entire Linux Distro Branch (Pop_OS, Linux Mint, etc.).  Why couldn't Nvidia work with Ubuntu to fix this issue?  I promise, that once Ubuntu has it working, it will spread throughout the Linux world.  I mean, look what's happened with Proton / Wine.  That took off like crazy to all of the other non Debian based distros. Anyway, I do appreciate the help. What about it Google?  How about patching Chrome to use H.264 / VP9 Hardware Acceleration in Linux?
I ran into a new problem with that last night.  I was trying to download the a Chromium-Dev branch that supports hardware acceleration.  However, even after I put in the PPA, I couldn't get the new C... See more...
I ran into a new problem with that last night.  I was trying to download the a Chromium-Dev branch that supports hardware acceleration.  However, even after I put in the PPA, I couldn't get the new Chromium to download... it kept installing the Snap instead. Yep... believe it or not "sudo apt install chromium-browser" launched "snap" to do the installation. So, I went a step further and removed "snap" entirely...  Then when I went to install "chromium-browser," it installed "snap" itself, and then went on to install the snap of "chromium-browser" on it's own! Check this link out:  Disabling Snaps in Ubuntu 20.10 (and 20.04 LTS) - Kevin Custer (kevin-custer.com) it explains the whole thing. Unfortunately, until Google steps up to the plate, and bakes it into the browser, it appears we are going to be out of luck.
That's a great link to follow as well.  And as I do have an Intel i7-3770 with an HD 4000 built in, my monitor is plugged into my GTX780ti. That particular link shows how to enable hardware decodi... See more...
That's a great link to follow as well.  And as I do have an Intel i7-3770 with an HD 4000 built in, my monitor is plugged into my GTX780ti. That particular link shows how to enable hardware decoding for my iGPU, and not my dGPU.
Hey Shadow, Thanks for the quick response. Yes, I have turned on that flag in chrome://flags.  If I go to the chrome://gpu screen, it will show that it is enabled.  However, it does not work.  Stad... See more...
Hey Shadow, Thanks for the quick response. Yes, I have turned on that flag in chrome://flags.  If I go to the chrome://gpu screen, it will show that it is enabled.  However, it does not work.  Stadia still uses Software H.264, and limits my resolution to 1280x720.  The Stadia "Decode Time" is not fast enough to do 1920x1080. If you followed the link I posted, I have gone through that checklist, and followed the instructions to the "T" multiple times.  Unfortunately, I still do not get Hardware Video Decoding.
I am a Kubuntu user, and have been for many years.  Started with 8.04, and am currently running 20.04.2. Also, I currently own an i7-3770 and a Nvidia GTX780ti. No matter what I try, Stadia will onl... See more...
I am a Kubuntu user, and have been for many years.  Started with 8.04, and am currently running 20.04.2. Also, I currently own an i7-3770 and a Nvidia GTX780ti. No matter what I try, Stadia will only run my games in Software mode.  Even if I use "Stadia Enhanced" to force h.264, it still only uses Software decoding. Now, I have been trying all of these online walk-throughs on how to enable HW Acceleration on the Chrome Browser...  but to no avail. https://www.linuxuprising.com/2021/01/how-to-enable-hardware-accelerated.html?m=1 I don't really want to upgrade my video card either.  A GTX1660 is going for $700 - $800 right now... and the Video Card "crisis" is kinda why I decided to start using Stadia in the first place. What can be done here to allow Stadia to decide h.264 in Hardware?
So far, I really like Stadia.  Of course, the games run great for me. I have a couple of questions though.  Are there going to be improvements to the interface?When can these features be implemented... See more...
So far, I really like Stadia.  Of course, the games run great for me. I have a couple of questions though.  Are there going to be improvements to the interface?When can these features be implemented?  Don't think I am asking for anything outside of the ordinary here...  These options are pretty standard for online game services, It's kind of strange not to have them... Scrollbar Search Feature Library Management There is no scroll bar, or search function.  Also, there is no way to manage my library of games.  Are these "features" going to be added soon? I have tried a few of the "Pro" version games, and I don't really like them, so I'd like to remove them from my library.