@opt9 I’d bet that they just missed it. Glad it’s working for you. 👍
Paul Rimmer
Retired embedded developer, full time geek. 🐧 You’ll find me travelling somewhere in the world with @heliepoo and/or watching a Liverpool game. 😊⚽
- 0 Posts
- 6 Comments
Joined 1 year ago
Cake day: July 16th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
@opt9 Looks like you found the issue. Did changing those settings fix the problem?
HW accel should be automatic on targets that support it (x86, AMD, Apple). I run on a #RaspberryPi4 target which is #Arm64 and doesn’t support it “yet”. The fix has been checked into git so next release will fix it on Firefox and LibreWolf. In your case though, if Firefox is working then LibreWolf also should.
I’d ask @librewolf if they have any ideas why it wouldn’t work. The Google turned up this: https://www.reddit.com/r/LibreWolf/comments/11isnra/how_to_enable_hardware_acceleration/
@Kidplayer_666 On Firefox/LibreWolf look at page: about:support -> Graphics -> Compositing. If it says “WebRender (Software)” it is not using HW accel. If it is using HW accel it will just say “WebRender”.
on Chromium/Chrome/Vivaldi etc. look at page: chrome://gpu/. You want to see “Hardware accelerated” and not “Software only. Hardware acceleration disabled”.
@Kidplayer_666 @opt9 What platform are you on? Chromium supports hardware accelerated video on Raspberry Pi’s, so less CPU load, while #Firefox (and derivatives like #LibreWolf) is about to with the upcoming 116 release. Currently I use LibreWolf on my Pi4 except for video watching and then I go back to Chromium. Once version 116 comes out I won’t need to switch.
@opt9 I knew how to check if HW accel was enabled. Beyond that I’m just spitballing. 🙂 You could raise an issue on their gitlab.
https://gitlab.com/groups/librewolf-community/-/issues