Announcement

Collapse
No announcement yet.

Video Acceleration Takes The Backseat On Chrome For Linux

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Video Acceleration Takes The Backseat On Chrome For Linux

    Phoronix: Video Acceleration Takes The Backseat On Chrome For Linux

    Due to notorious Linux graphics drivers, Google developers working on Chrome/Chromium aren't looking to enable hardware video acceleration by default anytime soon. The problem ultimately comes down to poor Linux graphics drivers...

    http://www.phoronix.com/vr.php?view=MTYyMDk

  • #2
    without gpu aceleration, I suffer tearing with flash pepper, I am really disappointed.

    Comment


    • #3
      Meanwhile, Nvidia has been shipping a stable VDPAU implementation for many years, and the Mesa VDPAU implementation for Radeon and Nouveau graphics is shaping up nicely as well. Why does Google only care about Intel's proprietary VA-API?

      Comment


      • #4
        Originally posted by brent View Post
        Meanwhile, Nvidia has been shipping a stable VDPAU implementation for many years, and the Mesa VDPAU implementation for Radeon and Nouveau graphics is shaping up nicely as well. Why does Google only care about Intel's proprietary VA-API?
        google trolling the people

        Comment


        • #5
          GPU Drivers

          How is it possible? Intel drivers is good enough for playing games like L4D or Portal 2 or support new webgl google maps. VDPAU is supported under (linux not very friendly) flash. Isn't VAAPI supported in media players like XMBC or VLC?
          So why Chrome devs speaks about bad drivers?

          Comment


          • #6
            Mozilla managed to do this with whitelisits. Not sure why Chrome team can not.

            Comment


            • #7
              So the problems are with drivers that are open?......... something they can help tackle?


              Seems these google guys are just Lazy or don't use linux as main platform.

              Now that Valve is getting intel and amd to improve things a lot ,they should hire someone to look into the video stuff.

              Anyway does chromeOS has acceleration of some kind ? I would think they would enable it at least for their own platform

              Comment


              • #8
                We don't ship code we consider to be permanently 'experimental' or 'beta'
                Google? Really?

                Comment


                • #9
                  Originally posted by brent View Post
                  Meanwhile, Nvidia has been shipping a stable VDPAU implementation for many years, and the Mesa VDPAU implementation for Radeon and Nouveau graphics is shaping up nicely as well. Why does Google only care about Intel's proprietary VA-API?
                  Because Intel has been the only so far needing it, software acceleration (specially on now-considered old Intel CPUs/Chipsets) has been bad to barely playable since a long time before (on Windows too).

                  They don't think that much on the low end GPUs that need it anyway.

                  Comment


                  • #10
                    what to expect from a company that's even to lazy to support linux for their webdesigner...

                    Comment


                    • #11
                      Oh yes, let's blame Google for being tired the mess which is the graphical stack of Linux nowadays. We have a graphic stack which was designed more than 30 years ago and to make it work with modern paradigms we patch it in every conceivable way. So taking apart DRI vs DRI2, XInput vs XInput2, Mesa vs Gallium3D, KMS and any other new patch above X limitations:

                      It comes Intel with EXA, UXA, GEM, SNA and God knows what else
                      Nvidia replacing half of the mess with their own private, closed and cryptic implementation
                      AMD doing the same on their part

                      Everyone has their own implementation of video acceleration and every one supports other features or not depending on their will and I'm ruling out legacy sytems and graphic stacks out of the main three. So now Adobe, Google or whatever other company tries to get hardware acceleration for their product of implement some other fancy feature easily implemented on the unified stack of Windows or OSX and they find bug after bug and it's normal.

                      And the situation is not improving. Wayland is taking ages to come out and still we have to see the support it might get from Nvidia and AMD, because without it, it's useless and in the mix comes Mir. Really?

                      So either Steam or Canonical or anyone else comes into play and gets enough traction to get companies on their side and cleans this mess in a dictatorship way or we continue as we go right now. Contrary to propietary systems we have freedom to implement what we want, but the price to pay is not having features implemented by third parties in a timely manner or implemented at all.

                      Comment


                      • #12
                        Originally posted by getaceres View Post
                        Oh yes, let's blame Google for being tired the mess which is the graphical stack of Linux nowadays. We have a graphic stack which was designed more than 30 years ago and to make it work with modern paradigms we patch it in every conceivable way. So taking apart DRI vs DRI2, XInput vs XInput2, Mesa vs Gallium3D, KMS and any other new patch above X limitations:

                        It comes Intel with EXA, UXA, GEM, SNA and God knows what else
                        Nvidia replacing half of the mess with their own private, closed and cryptic implementation
                        AMD doing the same on their part

                        Everyone has their own implementation of video acceleration and every one supports other features or not depending on their will and I'm ruling out legacy sytems and graphic stacks out of the main three. So now Adobe, Google or whatever other company tries to get hardware acceleration for their product of implement some other fancy feature easily implemented on the unified stack of Windows or OSX and they find bug after bug and it's normal.

                        And the situation is not improving. Wayland is taking ages to come out and still we have to see the support it might get from Nvidia and AMD, because without it, it's useless and in the mix comes Mir. Really?

                        So either Steam or Canonical or anyone else comes into play and gets enough traction to get companies on their side and cleans this mess in a dictatorship way or we continue as we go right now. Contrary to propietary systems we have freedom to implement what we want, but the price to pay is not having features implemented by third parties in a timely manner or implemented at all.
                        Despite that screed of yours, one of the things I have noticed is that video playback on Linux is infinitely better than on Windows.

                        Anybody who has problems on Linux must have some turd hardware or software.

                        And Google has never been good at writing software. It's all third-rate, minimum-wage broken crap that looks like it was designed by a chimp on meth.

                        Comment


                        • #13
                          Originally posted by peppepz View Post
                          Google? Really?
                          I had a LOL-of-irony at that as well.

                          Comment


                          • #14
                            Originally posted by shmerl View Post
                            Mozilla managed to do this with whitelisits. Not sure why Chrome team can not.
                            Yeah. My thoughts exactly. I have the latest OSS stack from git (A8-6500 apu, radeon/r600g driver) and Seamonkey and Firefox run webgl demos just fine and has accelerated playback (decoding too if enabled in the mms.cfg, but that seems to be limited to youtube, flash content on other sites crashes typically).

                            Chrome untiil quite recently worked just fine (albeit with generally higher CPU usage than Firefox/Seamonkey) if i disabled its blacklist, but recent versions crapped out, even SD flash video playback is crap and manages to use 200-300% CPU (i have 4 cores). This makes Chrome on Linux with OSS drivers (at least radeon) crap.
                            Summing it up, Chrome devs are just lazy - if Firefox could do it, what stops the best funded browser in the world (ok, ONE of them) from implementing it?

                            BTW Steam Source games run just perfectly fine on the radeon/OSS drivers.

                            Comment


                            • #15
                              Originally posted by gradinaruvasile View Post
                              Yeah. My thoughts exactly. I have the latest OSS stack from git (A8-6500 apu, radeon/r600g driver) and Seamonkey and Firefox run webgl demos just fine and has accelerated playback (decoding too if enabled in the mms.cfg, but that seems to be limited to youtube, flash content on other sites crashes typically).

                              Chrome untiil quite recently worked just fine (albeit with generally higher CPU usage than Firefox/Seamonkey) if i disabled its blacklist, but recent versions crapped out, even SD flash video playback is crap and manages to use 200-300% CPU (i have 4 cores). This makes Chrome on Linux with OSS drivers (at least radeon) crap.
                              Summing it up, Chrome devs are just lazy - if Firefox could do it, what stops the best funded browser in the world (ok, ONE of them) from implementing it?

                              BTW Steam Source games run just perfectly fine on the radeon/OSS drivers.
                              I have an apu a8 5600k and I experienced the same issues with google chrome/chromium.

                              Comment

                              Working...
                              X