However, the videos stutter on this laptop with these settings. ] I've tried using the instructions below, and then launch the browser with the -use-gl=egl and -disable-features=UseChromeOSDirectVideoDecoder flags on Wayland, on a laptop with Intel graphics, and hardware-accelerated video playback works. Starting with Google Chrome 91 (and other browsers based on Chromium 91), you'll also need to append the -enable-features=VaapiVideoDecoder and -disable-features=UseChromeOSDirectVideoDecoder flags. You can use VA-API on XWayland, using the -use-gl=egl command line flag, but I did not try it. Microsoft Edge - there's not even a chrome://flags/#enable-accelerated-video-decode flag (to enable hardware-accelerated video decode).Vivaldi stable is now version 36, and that does have working hardware-accelerated video decoding Obviously, it should continue to work with versions newer than these (so Google Chrome 89, Brave 1.20, etc.).įor me, hardware-accelerated video decode didn't work using: Vivaldi snapshot 3.6 / The latest Vivaldi stable 3.6 also works.In my test, I was able to get hardware-accelerated video decode to work on Linux using: I don't own a device with AMD graphics to test this. Also tested using a laptop with Intel graphics (10th gen) on Ubuntu 20.04 and 20.10. I tested these instructions using Ubuntu 20.10 desktop with Nvidia graphics, and the web browsers listed below installed using their original Ubuntu packaging (using a DEB package). I'd also like to add that these instructions to enable hardware accelerated video decoding also work on other Linux distributions, and not just Debian / Ubuntu-based Linux distributions, however, the driver names are different. Thus, these instructions may also work for Chromium browser, depending on how it's built. on Ubuntu / Linux Mint there's a PPA with VA-API patched Chromium builds. So Chromium users have had hardware acceleration on Linux for some time, depending on their Linux distribution or if they installed the patched Chromium in some other way. It's worth noting that Chromium web browser had patches that allowed making hardware accelerated video decoding available on Linux for some time, and some Linux distributions packaged it using those patches. ![]() Using hardware-accelerated video decode in your web browser should result in using less CPU usage (and thus, less battery draining) when playing online videos. This article explains how to enable hardware-accelerated video decoding in Google Chrome, Brave, Vivaldi and Opera web browsers running on Debian, Ubuntu, Pop!_OS or Linux Mint (Xorg only). Google Chrome is not the only Chromium-based web browser to support hardware acceleration on Linux though. It’s done via brave://settings/manageProfile while in the user profile of choice.Google Chrome 88 (and newer) has made hardware accelerated video decoding available on Linux, but it's not enabled by default. Until the Github issues I listed above have been addressed, you could achieve what you want by creating a specific shortcut for the wanted user profile. "C:\Program Files\BraveSoftware\Brave-Browser\Application\brave.exe" -profile-directory="Default"įor better understanding of that, you could open C:\Users\User\AppData\Local\BraveSoftware\Brave-Browser\User Data and check how your user profiles are stored.īut like I said twice, Brave allows users to create specific desktop shortcuts easily, so it’s not really needed to burden yourself with directories and don’t have Google Chrome installed on my PC so can’t test, but I think that’s how it works there too, and Brave developers haven’t bothered to change the behavior of Chromium. It corresponds to the default directory, other user profiles will be Profile X where X is a number. For the current example, I created a specific desktop shortcut that will always open my daily profile. Is the issue reproducible on the latest version of Chrome? No Does the issue resolve itself when disabling Brave Rewards? No Does the issue resolve itself when disabling Brave Shields? No Can you reproduce this issue with the nightly channel? Don't know ![]() Can you reproduce this issue with the beta channel? Don't know Can you reproduce this issue with the current release? Yes Open Brave in initial profile `Profile 1`īrave | 1.26.74 Chromium. ![]() If not set it would be able to go back to last opened profile, like currently.ġ. It would be handy to have a default profile, possibly a default radio button underneath each profile in the `Manage Profiles` window.Ī CLI option to always open a specific profile `brave-browser -profile "Profile 1"` On opening the browser one knows which profile was last opened.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |