You are not logged in.
Hi folks,
Forgive me if this has been discussed before -- I expect it has -- but is there any reason we aren't building Chromium with hardware acceleration enabled, as described in https://code.google.com/p/chromium/wiki … ideoDecode ?
I'm starting to get jealous as there's now a Ubuntu PPA that provides it ![]()
Google claims they don't do it because of stability issues, but it still isn't enabled by default (even on a build that's configured to support it) unless you set flags to override the GPU bug list in Chrome: https://code.google.com/p/chromium/issu … ?id=137247
I think Arch users can probably handle having that flag exposed to them. Thoughts?
Offline
Arch is just a platform for supplying largely unmodified and unpatched upstream software.
You could use the ABS to re-build Chromium to your desired specification.
https://wiki.archlinux.org/index.php/Arch_Build_System
Jin, Jîyan, Azadî
Offline
Google claims they don't do it because of stability issues, but it still isn't enabled by default (even on a build that's configured to support it) unless you set flags to override the GPU bug list in Chrome: https://code.google.com/p/chromium/issu … ?id=137247
You don't need to rebuild chromium to expose the gpu blacklist flag. You can already do that either from chrome://flags or by passing the --ignore-gpu-blacklist command line argument. After that you should should see hardware acceleration enabled if you check chrome://gpu
However hardware accelerated video decoding/encoding still doesn't seem to work (even though chrome://gpu reports that it's hardware accelerated) and you'll get 'Not implemented' errors when watching video, and the instructions behind the first link you posted addresses this issue.
Just wanted to clarify this. As Head_on_a_Stick already said, you can modify and rebuild the chromium package from ABS however you want.
Offline