- CHROMIUM SWIFT SHADER DRIVERS
- CHROMIUM SWIFT SHADER UPDATE
- CHROMIUM SWIFT SHADER DRIVER
- CHROMIUM SWIFT SHADER UPGRADE
- CHROMIUM SWIFT SHADER SOFTWARE
Using Nvida in Linux, especially a cutting-edge distro like Arch is tough man.Īlso, I thought it was the gnome window manager that was having problems with the archlinuxcn version, but it was re2 so thanks for letting me know.
Maybe wait for archlinuxcn version to be updated? Firefox video acceleration is coming soon too and it will use ffmpeg which is a much better approach imo. H.264 looks worse than vp9 with larger file size, I'd not recommend using it.
I have checked it already, it is using Mojovideodecoder on Youtube and also checked through intel_gpu_top. Why is it so difficult to get these browsers to use hardware video acceleration when most (streaming) media players have had it for many years? (That was a rhetorical question I have a general idea) It's very unfortunate for these regressions to appear. I read they're going to include X11 support in version 80, but the stable version of FF is only 78.0.1 as of posting. I would much rather just use Firefox, but it doesn't have VP9 enabled either and only works for Wayland as of yet (opposite problem of Chromium). Now, the only method that recently worked, doesn't. Is anyone else using nvidia and va-api (on X11, of course)? How did you get it to work? I've tried the other methods listed in AUR posts and Arch wiki, but they're either out-of-date or didn't work for me.
CHROMIUM SWIFT SHADER DRIVER
I can think of two solutions, but they're not very appealing:ġ) Compile/build chromium-vaapi from source (It takes several hours, and there's no guarantee it still works)Ģ) Use a browser extension to force H.264 codec instead of VP9 (the reason I chose this driver is because neither libva-vdpau-driver nor libva-vdpau-driver-chromium ever actually enabled "MojoVideoDecoder" for anything, including h264, during video playback) Apparently, whatever the regular Arch chromium build does to enable VA-API is different from 'chromium-vaapi' AUR package. ".ERROR:vaapi_video_decode_(674)] : Failed to initialize VppVaapiWrapper"īTW, all the various appropriate statuses in chrome://gpu says "Hardware accelerated" but it doesn't want to play with this particular driver. Instead, I'm getting this error at the bottom of chrome://gpu
CHROMIUM SWIFT SHADER DRIVERS
Since I'm using nvidia proprietary drivers and KDE, I probably wouldn't have problems with the new mesa and gnome-shell. Now, the archlinuxcn version is having dependency issues with re2 and won't launch, and I haven't bothered to build it myself yet.
CHROMIUM SWIFT SHADER SOFTWARE
If the player says kVideoDecoderName "VpxVideoDecoder" instead of "MojoVideoDecoder" then it is still using the software decoder regardless of what chrome://gpu says.īefore the most recent updates, 'chromium-vaapi' worked fine with 'libva-vdpau-driver-vp9', both from the AUR.
Be sure to check if hardware video acceleration is actually enabled by going to chrome://media-internals like the wiki says. Unfortunately, the official Arch chromium doesn't work with my configuration. Feels good using chromium from an official repo. SDK packages also have more development tools to be exposed in the following releases, as well as the NaCl support.Wow Chromium from regular Arch repos works for video acceleration now while chromium-vaapi from archlinuxcn was having problems with the new mesa and gnome-shell. lt can be opened by pressing F12 (Cmd-Alt-I on OSX). Normal build doesn't have devtools, only SDK build does. There are 2 builds for each platform - normal build, and SDK build.
CHROMIUM SWIFT SHADER UPGRADE
The stable upgrade contains many security fixes as well.
See the upstream announcement for more information. Chromium 61 features JavaScript modules support, Payment Request API and WebUSB. Last week we announced NW.js 0.25 with Chromium 61 upgrade. So you can provide advanced 3D graphics independent from hardware of your users. SwiftShader is a software 3D renderer used in Chrome that lets you use CSS 3D and WebGL even on hardware with incapable GPUs. One of the important improvements is that the swiftshader library is shipped on both Linux and Windows. This release includes bug fixes we've done since the last version. You can see more information on this here and here. Here comes another release for the Chromium 61 update, which contains important security fix regarding the V8 engine.
CHROMIUM SWIFT SHADER UPDATE
NW.js v0.25.3 Released with Important Chromium 61 Security Update and Swiftshader
0 kommentar(er)
