Chrome Rendering Pipeline Improvements For Better Performance

[RussianNeuroMancer]

That's not true, I'm watching videos with a Chromium-vaapi from AUR on Radeon HD5730, works fine.

Did you check video_decoder field on chrome://media-internals page while playback? What you see here?

[Hi-Angel]

Did you check video_decoder field on chrome://media-internals page while playback? What you see here?

It says "GpuVideoDecoder". I can say that it uses VAAPI because for I'm playing a video, I see the same output from chromium as from `vainfo` command, i.e. about va-driver, version, opening the lib.

[Vistaus]

Agree, that's exactly the problem.

If that's the problem, then how come this is enabled by default on ChromeOS? Last time I checked ChromeOS *is* Linux. See:
http://www.ghacks.net/2017/01/31/chr...-not-tell-you/
"This sounds all good and great, but Google fails to mention that the second method is not supported by all operating systems, and even architectures. If you follow the link to Intel's blog post about the new zero-copy feature, you will learn that the feature is only enabled by default on Chrome OS"

[RussianNeuroMancer]

It says "GpuVideoDecoder". I can say that it uses VAAPI because for I'm playing a video, I see the same output from chromium as from `vainfo` command, i.e. about va-driver, version, opening the lib.

Good to know! I stand corrected.

[darkbasic]

If that's the problem, then how come this is enabled by default on ChromeOS? Last time I checked ChromeOS *is* Linux. See:
http://www.ghacks.net/2017/01/31/chr...-not-tell-you/
"This sounds all good and great, but Google fails to mention that the second method is not supported by all operating systems, and even architectures. If you follow the link to Intel's blog post about the new zero-copy feature, you will learn that the feature is only enabled by default on Chrome OS"

ChromeOS != Linux. I had to backport patches for months to be able to use h264 hardware acceleration on Linux, because Google didn't support it in mainline Chrome (while they had patches in their ChromeOS builds).

[axfelix]

yeah, chromium-vaapi builds will work on Intel/AMD/nvidia, but you _still_ have to get special builds and (at least on Arch) they break pretty often and maintainers have to catch up. All to change like three flags in the source. I really, really, really wish they'd just enable this upstream on Linux.

[Vistaus]

ChromeOS != Linux. I had to backport patches for months to be able to use h264 hardware acceleration on Linux, because Google didn't support it in mainline Chrome (while they had patches in their ChromeOS builds).

Wrong. ChromeOS = Linux. It's based on vanilla Linux but uses some Gentoo tools like Portage: http://www.zdnet.com/article/the-sec...les-chrome-os/

[darkbasic]

Wrong. ChromeOS = Linux. It's based on vanilla Linux but uses some Gentoo tools like Portage: http://www.zdnet.com/article/the-sec...les-chrome-os/

No, they patch the graphic stack in many different ways and they also heavily patch Chrome itself. They care to test on ChromeOS but it takes ages to get the patches merged upstream.