Replies: 2 comments 1 reply
-
thanks i will add it to the faq |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks for the writeup, GRFTSOL. I could not get it to work on my NVIDIA system. I went through the entire Arch HW Acceleration guide and verified that the drivers are all working, but no combination of environment variables or chromium flags got me accelerated playback showing up in the dev tools. My file works cleanly on my Windows boot on the same system. There's probably some additional configuration that I'm missing locally, but I'm not sure where to dig next. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
TLDR:
Edit the
.desktop
file, changeExec
to below:Exec=losslesscut --enable-features=AcceleratedVideoDecodeLinuxGL,VaapiVideoDecodeLinuxGL,VaapiVideoDecoder,VaapiIgnoreDriverChecks,UseChromeOSDirectVideoDecoder,Vulkan,DefaultANGLEVulkan,VulkanFromANGLE
For those not WOOB linux distro like archlinux, before doing this, you need:
mesa
package on archlinuxvulkan-radeon
package on archlinux, which is recommended on amdgpu currently.amdvlk
on archlinux, in case wrong driver choice by env.desktop
file like above mentioned.Reference:
https://wiki.archlinux.org/title/Chromium#Hardware_video_acceleration
Note
--enable-features
lossless-cut
is already wayland support, but if you are using old version, maybe you need to refer this: https://wiki.archlinux.org/title/Chromium#Native_Wayland_support to add arguments with running on waylandHow to tell if hwaccel is actually enabled:
nvtop
, check theDEC
engine usage, if you don't seeDEC
, means hwaccel not enabled.Beta Was this translation helpful? Give feedback.
All reactions