After six months, the Chromium upstream maintainers made a statement that they are not interested to include this patch<\/a>. So after that I\u00a0started working on my own patch with referenced from the official patch. My patch is about using the existing flags that other operating system uses instead of creating a new flag just for experimentation.<\/p>\n Chromium uses AMDGPU’s UVD engine while playing a video<\/p>\n<\/div>\n Chromium uses Existing flags on Fedora<\/p>\n<\/div>\n Chromium with this patch was extremely stable on both of my machines. They both have AMD GPU. The video playback is smooth. This improved overall power savings as well.<\/p>\n Credits: Tobias Wolfshappen<\/p>\n<\/div>\n As you can see, chromium with the vaapi patch takes up significantly less resources in comparison to chromium without the patch and Firefox.\u00a0 The CPU usage went down from 120% to 10%. The playback is smooth with no shuttering.<\/p>\n It was then\u00a0Fedora’s Engineering Manager @ Red Hat and Chromium maintainer, Tom Callaway, <\/a>finally recognises the VAAPI patch and decides<\/a> to include in Fedora’s Chromium browser. Fedora becomes the second distribution to include the VAAPI patch in their official Chromium package.<\/p>\n","protected":false},"excerpt":{"rendered":" Do you like playing videos in your web browser? Well, good news, the Chromium web browser available in Fedora gets a Video Acceleration API support. That makes video playback much smoother while using significantly less resources. A little bit of history Chromium with a VAAPI patch was already available on other distributions. But this was […]<\/p>\n","protected":false},"author":2,"featured_media":73871,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[48],"tags":[341,441,45,46,75,47,44],"class_list":["post-73870","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-fedora-os","tag-browser","tag-chrome","tag-fedora","tag-magazine","tag-new-in-fedora","tag-news","tag-using-software"],"_links":{"self":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts\/73870","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/comments?post=73870"}],"version-history":[{"count":0,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/posts\/73870\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/media\/73871"}],"wp:attachment":[{"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/media?parent=73870"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/categories?post=73870"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sickgaming.net\/blog\/wp-json\/wp\/v2\/tags?post=73870"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"screenshot](\"http:\/\/www.sickgaming.net\/blog\/wp-content\/uploads\/2019\/01\/chromium-on-fedora-finally-gets-vaapi-support.png\")
<\/p>\n![\"chromium's](\"http:\/\/www.sickgaming.net\/blog\/wp-content\/uploads\/2019\/01\/chromium-on-fedora-finally-gets-vaapi-support-1.png\")
<\/p>\nEffects of the VAAPI patch<\/h2>\n
![\"Comparision](\"http:\/\/www.sickgaming.net\/blog\/wp-content\/uploads\/2019\/01\/chromium-on-fedora-finally-gets-vaapi-support.jpg\")
<\/p>\nVA-API patch in chromium for Fedora<\/h2>\n