You are not logged in.
Thorium (https://github.com/Alex313031/Thorium/) offers hardware video acceleration by default.
Offline
Is it possible to use VAAPI on Wayland on regular Google Chrome?
Whether it's possible or not, VAAPI hw decode on chromium browsers is only available for XWayland, no native Wayland support.
Offline
viggy96 wrote:Is it possible to use VAAPI on Wayland on regular Google Chrome?
Whether it's possible or not, VAAPI hw decode on chromium browsers is only available for XWayland, no native Wayland support.
ungoogled-chromium in aur seems to have wayland vaapi patch applied. I'm currently building it to see if that works.
Offline
Thorium (https://github.com/Alex313031/Thorium/) offers hardware video acceleration by default.
Does this also work for VP9 videos?
Offline
ungoogled-chromium in aur seems to have wayland vaapi patch applied. I'm currently building it to see if that works.
Wow, it is actually works with Wayland.
1. Use this link for comfortable and fast install — https://github.com/ungoogled-software/u … -archlinux
2. In chromium-flags.conf set these strings:
--disable-features=UseChromeOSDirectVideoDecoder
--disable-gpu-memory-buffer-compositor-resources
--disable-gpu-memory-buffer-video-frames
--enable-hardware-overlays
3. For chrome://flags/ these flags:
Hardware-accelerated video decode → enabled.
Preferred Ozone platform → Auto.
Works on iHD, but I haven't success with AMDgpu. Power consumption is noticeable worse that in Firefox. But it is not so bad.
Offline
Thorium (https://github.com/Alex313031/Thorium/) offers hardware video acceleration by default.
Anyway to install it's binary on Arch? Doesn't seem to find in AUR too.
Offline
ungoogled-chromium in aur seems to have wayland vaapi patch applied. I'm currently building it to see if that works.
Thanks. Yesterday I tried it (downloaded binary from archlinuxcn repo) and surprisingly hardware decoding is working in native wayland on AMDGPU.
First time after years I have a fully working hardware decoding inside a chromium based browser on my old AMD laptop. Previously I only got a smooth reproduction till 1080p30 content, on 1080p60 I got small hangs and freezing. Now no issues on 1080p60 also, like it was happening in Firefox before Mozilla decided to break hardware decoding.
These are the flags I'm using:
--ozone-platform=wayland
--disable-features=UseChromeOSDirectVideoDecoder
--disable-gpu-memory-buffer-compositor-resources
--disable-gpu-memory-buffer-video-frames
--enable-hardware-overlays
These are reported on AUR, I only added `--ozone-platform=wayland` because ozone defaults to X11/XWayland, but specifying "wayland" I get hardware decoding on native Wayland also.
Last edited by digitalone (2022-06-03 07:35:27)
Offline
like it was happening in Firefox before Mozilla decided to break hardware decoding.
I think this is not broken for actual beta (if your laptop have single igpu).
For me Chromium isn't working on AMDgpu, Renoir series.
Offline
dimischiavone wrote:ungoogled-chromium in aur seems to have wayland vaapi patch applied. I'm currently building it to see if that works.
Wow, it is actually works with Wayland.
1. Use this link for comfortable and fast install — https://github.com/ungoogled-software/u … -archlinux
2. In chromium-flags.conf set these strings:
--disable-features=UseChromeOSDirectVideoDecoder
--disable-gpu-memory-buffer-compositor-resources
--disable-gpu-memory-buffer-video-frames
--enable-hardware-overlays
3. For chrome://flags/ these flags:
Hardware-accelerated video decode → enabled.
Preferred Ozone platform → Auto.Works on iHD, but I haven't success with AMDgpu. Power consumption is noticeable worse that in Firefox. But it is not so bad.
thanks ! working good on some youtube videos with my integrated Intel UHD Graphics 620 GPU !
unfortunately not with all the videos ... for example : https://www.youtube.com/watch?v=EfMN0os7Xh0 ... maybe because of the codec ? any opinion if my Intel integrated GPU can hardware-accelerate this video ???
(in windows Edge that video does get hardware acceleration ... but not in windows Chrome nor chromeos Chrome (chromeos dualbooted via brunch) )
thanks again !
Last edited by pierro78 (2022-06-05 13:28:26)
Offline
maybe because of the codec ? any opinion if my Intel integrated GPU can hardware-accelerate this video ???
I think it's cause of av1, which not supported by UHD620. Just come in Youtube's settings → Playback → flag AV1 just for SD videos.
Offline
Thorium (https://github.com/Alex313031/Thorium/) offers hardware video acceleration by default.
thanks for the tip ! I just unzipped it and no need to add command options or flags : I had hardware video acceleration by simply starting it ! (I am on "gnomish" garuda and I didn't have to install extra packages like intel drivers ...)
Offline
pierro78 wrote:maybe because of the codec ? any opinion if my Intel integrated GPU can hardware-accelerate this video ???
I think it's cause of av1, which not supported by UHD620. Just come in Youtube's settings → Playback → flag AV1 just for SD videos.
thanks so much for the tip ! I've just flagged "AV1 just for SD videos" and now this youtube video (or other youtube videos) above SD use the vp9 codec and are hardware decoded on my UHD620 !!
Last edited by pierro78 (2022-06-07 01:14:00)
Offline
Begemoth wrote:pierro78 wrote:maybe because of the codec ? any opinion if my Intel integrated GPU can hardware-accelerate this video ???
I think it's cause of av1, which not supported by UHD620. Just come in Youtube's settings → Playback → flag AV1 just for SD videos.
thanks so much for the tip ! I've just flagged "AV1 just for SD videos" and now this youtube video (or other youtube videos) above SD use the vp9 codec and are hardware decoded on my UHD620 !!
I use this extension to block av1 videos. It's like h264ify but for av1 on all websites.
Offline
There is an interesting aspect about Youtube I just found out on Reddit (https://www.reddit.com/r/chrome/comment … &context=3).
and VP9 is hardware accelerated in Chromium even on ancient cards like my GeForce GTX 750 Ti.
Edit: Btw it was my issue all the time. I've successfully managed to bring out VDAVideoDecoder out of libva-vdpau-driver-vp9-git. I had to disable Vulkan & allow inbuilt Skia Renderer do the GPU lifting.
these were enough:
--enable-features=VaapiVideoDecoder
--disable-features=UseChromeOSDirectVideoDecoder
--use-gl=desktop
No need of forced gpu rasterization. We just need to make sure disable ChromeOSDirectVideoDecoder, enable --use-gl=desktop & not use Vulkan in the first place, which is enough to resurrect VDAVideoDecoder.
Last edited by pc00per (2022-06-11 00:28:55)
Offline
DAC324 wrote:There is an interesting aspect about Youtube I just found out on Reddit (https://www.reddit.com/r/chrome/comment … &context=3).
and VP9 is hardware accelerated in Chromium even on ancient cards like my GeForce GTX 750 Ti.
Accelerated how? I've been trying day & night to accelerate VP9 on chromium for days. Nothing's working so far.
vainfo shows "VP9Profile0" entry. *chrome://gpu* shows Video Decode: Hardware Accelerated, but scroll down to "Video Acceleration Information", decoding section is just empty.
GPU: GTX 1660 super
according to the dev ( https://www.reddit.com/r/ChromiumBrowse … &context=3 ) Thorium supports VAAPI, VDPAU and video acceleration out of the box ... might be worth to give it a try
Offline
according to the dev ( https://www.reddit.com/r/ChromiumBrowse … &context=3 ) Thorium supports VAAPI, VDPAU and video acceleration out of the box ... might be worth to give it a try
Actually I was wrong. extra/chromium already supports VA-API out of the box.
I've just noticed chromium-vaapi been down
Last edited by pc00per (2022-06-10 14:04:11)
Offline
Sadly it seems vaapi under native wayland will need constant patching with each chromium update. Vaapi under xorg works without problems though. Does thorium support vaapi on both native wayland and xorg?
GPG key: 3DEA 6251 3C80 3538 3A24 5A12 E578 6B42 E8E5 D565
Offline
Hello, Thorium dev/maintainer here. You can use the portable .zips, or there is a PKGBUILD in the main repo > Here
Alex Frick, Thorium Developer/Maintainer, Arch User, Ubuntu User, ChromiumOS user.
Offline
Hello, Thorium dev/maintainer here.
Welcome, and Thank you.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Sorry, but no hardware decoding on native wayland with thorium.
Offline
Is anyone successful in getting hardware acceleration on Wayland? none of the flags seems to work in my case:
--enable-features=VaapiVideoDecoder
--disable-features=UseChromeOSDirectVideoDecoder
--disable-gpu-memory-buffer-compositor-resources
--disable-gpu-memory-buffer-video-frames
--enable-hardware-overlays
--ignore-gpu-blocklist
--enable-gpu-rasterization
--enable-zero-copy
--canvas-oop-rasterization
--ozone-platform=wayland
I'm running Ungoogled Chromium on Flatpak (103.0.5060.53), AMDGPU.
Last edited by moturhead (2022-07-01 14:00:50)
Offline
@moturhead
I don't think the flatpak versions contains the patches used by ungoogled-chromium in arch. Mainly this one, https://aur.archlinux.org/cgit/aur.git/ … d-chromium
You should ask the maintainer of the flatpak version to add that patch.
GPG key: 3DEA 6251 3C80 3538 3A24 5A12 E578 6B42 E8E5 D565
Offline
@justkdng
You released the same patch on github too about 4 days ago. Does this patch gets merged with other flavors of Ungoogled Chromium (Eloston's) too? I think the Flatpak maintainer must be using some other fork of the software for his package.
Offline
@moturhead
no, that patch is only included in arch linux right now. It could be included to other distributions but that is up to the distro's maintainer.
Last edited by justkdng (2022-07-02 01:31:08)
GPG key: 3DEA 6251 3C80 3538 3A24 5A12 E578 6B42 E8E5 D565
Offline
try this.
--use-gl=egl
--enable-features=VaapiVideoDecoder,VaapiVideoEncoder
--disable-features=UseChromeOSDirectVideoDecoder
--ignore-gpu-blocklist
--disable-gpu-driver-bug-workaround
Offline