You are not logged in.
Anyone else struggling to get this working properly on a dual-AMD-gpu laptop? It seems to decode on my dGPU with the flags under the vulkan section from the wiki, but if I disable my dGPU with supergfxctl it doesn't decode at all. If I use the new --render-node-override flag to point it to my iGPU, regardless of whether the dGPU is on or off it also doesn't work. Any ideas? Firefox and MPV are able to decode on the iGPU.
Using an Asus Zephyrus G14 2022.
Last edited by PrismaticCuttlefish (2025-04-12 05:03:45)
Offline
@PrismaticCuttlefish, did you try https://wiki.archlinux.org/title/Vulkan#Switching ?
Offline
@Xephon Thank you for the suggestion. Using MESA_VK_DEVICE_SELECT seems to have no effect for me. --render-node-override changes which gpu is listed as active under about:gpu and it keeps the dGPU from powering on, but GL_RENDERER there is still listed as the dGPU regardless of what I have the flag set to. I seem unable to get hardware decoding working at all on the iGPU.
Offline
Did you install vulkan-mesa-layers and reboot after that? Provide output of
vulkaninfo --summary
Offline
Seems to be installed correctly. Here:
$ vulkaninfo --summary
==========
VULKANINFO
==========
Vulkan Instance Version: 1.4.309
Instance Extensions: count = 24
-------------------------------
VK_EXT_acquire_drm_display : extension revision 1
VK_EXT_acquire_xlib_display : extension revision 1
VK_EXT_debug_report : extension revision 10
VK_EXT_debug_utils : extension revision 2
VK_EXT_direct_mode_display : extension revision 1
VK_EXT_display_surface_counter : extension revision 1
VK_EXT_headless_surface : extension revision 1
VK_EXT_surface_maintenance1 : extension revision 1
VK_EXT_swapchain_colorspace : extension revision 5
VK_KHR_device_group_creation : extension revision 1
VK_KHR_display : extension revision 23
VK_KHR_external_fence_capabilities : extension revision 1
VK_KHR_external_memory_capabilities : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2 : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2 : extension revision 1
VK_KHR_portability_enumeration : extension revision 1
VK_KHR_surface : extension revision 25
VK_KHR_surface_protected_capabilities : extension revision 1
VK_KHR_wayland_surface : extension revision 6
VK_KHR_xcb_surface : extension revision 6
VK_KHR_xlib_surface : extension revision 6
VK_LUNARG_direct_driver_loading : extension revision 1
Instance Layers: count = 5
--------------------------
VK_LAYER_MESA_device_select Linux device selection layer 1.4.303 version 1
VK_LAYER_VALVE_steam_fossilize_32 Steam Pipeline Caching Layer 1.3.207 version 1
VK_LAYER_VALVE_steam_fossilize_64 Steam Pipeline Caching Layer 1.3.207 version 1
VK_LAYER_VALVE_steam_overlay_32 Steam Overlay Layer 1.3.207 version 1
VK_LAYER_VALVE_steam_overlay_64 Steam Overlay Layer 1.3.207 version 1
Devices:
========
GPU0:
apiVersion = 1.4.305
driverVersion = 25.0.2
vendorID = 0x1002
deviceID = 0x1681
deviceType = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
deviceName = AMD Radeon 680M (RADV REMBRANDT)
driverID = DRIVER_ID_MESA_RADV
driverName = radv
driverInfo = Mesa 25.0.2
conformanceVersion = 1.4.0.0
deviceUUID = 00000000-0700-0000-0000-000000000000
driverUUID = 414d442d-4d45-5341-2d44-525600000000
GPU1:
apiVersion = 1.4.305
driverVersion = 25.0.2
vendorID = 0x1002
deviceID = 0x73ef
deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
deviceName = AMD Radeon RX 6800S (RADV NAVI23)
driverID = DRIVER_ID_MESA_RADV
driverName = radv
driverInfo = Mesa 25.0.2
conformanceVersion = 1.4.0.0
deviceUUID = 00000000-0300-0000-0000-000000000000
driverUUID = 414d442d-4d45-5341-2d44-525600000000
GPU2:
apiVersion = 1.4.305
driverVersion = 0.0.1
vendorID = 0x10005
deviceID = 0x0000
deviceType = PHYSICAL_DEVICE_TYPE_CPU
deviceName = llvmpipe (LLVM 19.1.7, 256 bits)
driverID = DRIVER_ID_MESA_LLVMPIPE
driverName = llvmpipe
driverInfo = Mesa 25.0.2 (LLVM 19.1.7)
conformanceVersion = 1.3.1.1
deviceUUID = 6d657361-3235-2e30-2e32-000000000000
driverUUID = 6c6c766d-7069-7065-5555-494400000000
Offline
This should work
MESA_VK_DEVICE_SELECT=1002:1681! chromium
UPD: It seems to be a problem with switching rendering devices under wayland
https://issues.chromium.org/issues/396434686
Last edited by Xephon (2025-04-12 23:54:27)
Offline
Thanks. I'll keep an eye on that issue thread then.
Offline
irql-notlessoreq wrote:Hi, I uploaded today an AUR package of my Intel legacy VA-API driver fork [1] and was wondering if anyone on older Intel hardware would be willing to try it out.
It's main feature is that the issue with Chromium is fixed so you no longer see the following error:
VaapiVideoDecoder: failed Initialize()ing the frame pool
What a work !
Your driver works very well on Ivybridge generation Thinkpads (t430s. w530)
I tested this driver's hardware video acceleration capability on some Chromium based browsers (Vivaldi, Brave) and found all work with vaapivideodecoder.Thank you
Hi, which flags or options did you have to use to make video acceleration to work? I've compiled the IRQL fork but couldn't made it work with Chromium or Brave (Firefox works, checked via intel_gpu_top). No matter which flags i use the chrome://gpu video acceleration section is empty (before the IRQL fork, with Brave, i was able to make at least show the info and stumbled at the VAAPI frame pool error, but i can't remember which flag made the trick)
Offline
Hi, which flags or options did you have to use to make video acceleration to work? I've compiled the IRQL fork but couldn't made it work with Chromium or Brave (Firefox works, checked via intel_gpu_top). No matter which flags i use the chrome://gpu video acceleration section is empty (before the IRQL fork, with Brave, i was able to make at least show the info and stumbled at the VAAPI frame pool error, but i can't remember which flag made the trick)
Per the Arch Wiki, for Chrome 130+ it is the following:
--enable-features=AcceleratedVideoDecodeLinuxGL
Also "AcceleratedVideoDecodeLinuxZeroCopyGL" is recommended for native (with the ozone platform hint set) Wayland users.
Last edited by irql-notlessoreq (2025-04-13 13:43:45)
Offline
In a shocking turn of events... vaapi hardware decoding is now working with nVidia in a pure native Wayland session.
Device 0 [NVIDIA GeForce GTX 1050 Ti] PCIe GEN 3@16x RX: 1.514 MiB/s TX: 450.0 KiB/s
GPU 1290MHz MEM 3504MHz TEMP 99°F FAN 31% POW N/A / 75 W
GPU[|| 7%] MEM[||||||||||||||2.254Gi/4.000Gi] DEC[|| 22%]
┌────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
100│GPU0 % │
│GPU0 mem% │
│ │
│ │
│ │
75│ │
│ │
│ │
│ ┌─────────┐ │
│ ┌───┘ └────────│
50│ ┌─┐ ┌───────────┐ │ │
│─────────────┐ │ │ ┌─────────────────┐ │ └─┘ │
│ └─────────────────┘ └─┘ │ ┌─────────┘ │
│ └───────────────────────────────────────────────────┘ │
│ ┌─┐ │
25│ │ │ │
│ │ │ ┌─┐ ┌─┐ ┌───────────────┐ │
│ ┌───┐ │ │ │ │ │ └─┘ └─┐ │
│ │ └─┐ │ │ │ │ ┌─┐ ┌─┐ ┌─────┐ ┌───┐ │ │ │
│ ┌───┐ ┌───┐ │ └───┐ │ └─┘ └─┐ │ └─┘ └───────┘ └─┘ └─┘ └─│
0│────┘ └───┘ └─────────────┘ └─────────┘ └─────────────────────────────────────────┘ │
└76s──────────────────────────────────57s───────────────────────────────────38s───────────────────────────────────19s──────────────────────────────────0s┘
PID USER DEV TYPE GPU GPU MEM CPU HOST MEM Command
1095 tekstryder 0 Graphic 0% 862MiB 21% 6% 1068MiB /usr/bin/gnome-shell
61880 tekstryder 0 Graphic 6% 823MiB 20% 5% 559MiB /usr/lib/chromium/chromium --type=gpu-process --ozone-platform=wayland --crashpad-handler-
--enable-features=AcceleratedVideoDecodeLinuxZeroCopyGL,AcceleratedVideoDecodeLinuxGL,VaapiOnNvidiaGPUs
• kernel 6.13.11
• gnome-shell 48.0
• mutter 48.1
• wayland (meson_options: xwayland=false, x11=false)
• chromium 135.0.7049.84
• brave-bin 1.77.97
Well slap my ass and call me Sally!
Never thought I'd see the day.
Offline
Hardware encoding for me works in firefox and brave, however, in all chromium based programs (brave, vscodium, ...) I have flickering issues.
LIBVA_DRIVER_NAME=nvidia
VDPAU_DRIVER=nvidia
NVD_BACKEND=direct
__GLX_VENDOR_LIBRARY_NAME=nvidia
EGL_PLATFORM=wayland
### https://github.com/elFarto/nvidia-vaapi-driver?tab=readme-ov-file#firefox
MOZ_DISABLE_RDD_SANDBOX=1
__EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/10_nvidia.json
$ brave --enable-features=AcceleratedVideoDecodeLinuxGL,AcceleratedVideoDecodeLinuxZeroCopyGL,VaapiOnNvidiaGPUs,VaapiIgnoreDriverChecks
<removed non-related errors>
[45:45:0414/201023.005856:ERROR:gl_display.cc(495)] EGL Driver message (Error) eglCreateContext: Requested version is not supported
Warning: eglCreateContext failed with EGL_BAD_ATTRIBUTE
- While trying to discover a BackendType::OpenGL adapter.
at CheckEGL (../../third_party/dawn/src/dawn/native/opengl/UtilsEGL.cpp:98)
I guess this error is related to the flickering?
Last edited by RobinSch (2025-04-14 18:16:06)
Offline
in all chromium based programs (brave, vscodium, ...) I have flickering issues.
LIBVA_DRIVER_NAME=nvidia VDPAU_DRIVER=nvidia NVD_BACKEND=direct __GLX_VENDOR_LIBRARY_NAME=nvidia EGL_PLATFORM=wayland __EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/10_nvidia.json
I would start by removing/commenting out... ALL of those.
No idea what platform you're running, but none of them are necessary for chromium-based browser hardware acceleration.
$ brave --enable-features=AcceleratedVideoDecodeLinuxGL,AcceleratedVideoDecodeLinuxZeroCopyGL,VaapiOnNvidiaGPUs,VaapiIgnoreDriverChecks
Get rid of VaapiIgnoreDriverChecks too.
Offline
nelsonhf wrote:Hi, which flags or options did you have to use to make video acceleration to work? I've compiled the IRQL fork but couldn't made it work with Chromium or Brave (Firefox works, checked via intel_gpu_top). No matter which flags i use the chrome://gpu video acceleration section is empty (before the IRQL fork, with Brave, i was able to make at least show the info and stumbled at the VAAPI frame pool error, but i can't remember which flag made the trick)
Per the Arch Wiki, for Chrome 130+ it is the following:
--enable-features=AcceleratedVideoDecodeLinuxGL
Also "AcceleratedVideoDecodeLinuxZeroCopyGL" is recommended for native (with the ozone platform hint set) Wayland users.
Thanks @irql-notlessoreq. Indeed the only flag needed was --enable-features=AcceleratedVideoDecodeLinuxGL since i'm on X11. It worked with Chromium and Brave on a Gen7 GPU (verified with chrome://media-internals and intel_gpu_top) The issue was on my side with an old libva. I compiled a new version (libva 2.20) and it worked. Thanks again for your fork of the legacy intel vaapi driver.
Last edited by nelsonhf (2025-04-14 19:51:20)
Offline
RobinSch wrote:in all chromium based programs (brave, vscodium, ...) I have flickering issues.
LIBVA_DRIVER_NAME=nvidia VDPAU_DRIVER=nvidia NVD_BACKEND=direct __GLX_VENDOR_LIBRARY_NAME=nvidia EGL_PLATFORM=wayland __EGL_VENDOR_LIBRARY_FILENAMES=/usr/share/glvnd/egl_vendor.d/10_nvidia.json
I would start by removing/commenting out... ALL of those.
No idea what platform you're running, but none of them are necessary for chromium-based browser hardware acceleration..
I tried to remove all of those. Firefox works fine, however, without the
__EGL_VENDOR_LIBRARY_FILENAMES
brave gives the following error (and hardware acceleration does not work anymore):
465:465:0414/220551.352166:ERROR:gl_display.cc(495)] EGL Driver message (Error) eglCreateContext: Requested version is not supported
Warning: eglCreateContext failed with EGL_BAD_ATTRIBUTE
- While trying to discover a BackendType::OpenGL adapter.
at CheckEGL (../../third_party/dawn/src/dawn/native/opengl/UtilsEGL.cpp:98)
[465:465:0414/220551.648948:ERROR:angle_platform_impl.cc(49)] ImageEGL.cpp:112 (operator()): eglCreateImage failed with 0x00003009
ERR: ImageEGL.cpp:112 (operator()): eglCreateImage failed with 0x00003009
[465:465:0414/220551.649210:ERROR:scoped_egl_image.cc(23)] Failed to create EGLImage: EGL_SUCCESS
[465:465:0414/220551.649473:ERROR:native_pixmap_egl_binding.cc(114)] Unable to initialize binding from pixmap
[465:465:0414/220551.649633:ERROR:ozone_image_backing.cc(319)] OzoneImageBacking::ProduceSkiaGanesh failed to create GL representation
[465:465:0414/220551.649770:ERROR:shared_image_manager.cc(408)] SharedImageManager::ProduceSkia: Trying to produce a Skia representation from an incompatible backing: OzoneImageBacking
[465:465:0414/220551.650090:ERROR:gpu_service_impl.cc(1186)] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly.
[67:10:0414/220551.670662:ERROR:command_buffer_proxy_impl.cc(327)] GPU state invalid after WaitForGetOffsetInRange.
[5:5:0414/220551.716510:ERROR:gpu_process_host.cc(954)] GPU process exited unexpectedly: exit_code=8704
[689:689:0414/220553.251350:ERROR:angle_platform_impl.cc(49)] ImageEGL.cpp:112 (operator()): eglCreateImage failed with 0x00003009
ERR: ImageEGL.cpp:112 (operator()): eglCreateImage failed with 0x00003009
[689:689:0414/220553.251557:ERROR:scoped_egl_image.cc(23)] Failed to create EGLImage: EGL_SUCCESS
[689:689:0414/220553.251672:ERROR:native_pixmap_egl_binding.cc(114)] Unable to initialize binding from pixmap
[689:689:0414/220553.251793:ERROR:ozone_image_backing.cc(319)] OzoneImageBacking::ProduceSkiaGanesh failed to create GL representation
[689:689:0414/220553.251902:ERROR:shared_image_manager.cc(408)] SharedImageManager::ProduceSkia: Trying to produce a Skia representation from an incompatible backing: OzoneImageBacking
[689:689:0414/220553.252107:ERROR:gpu_service_impl.cc(1186)] Exiting GPU process because some drivers can't recover from errors. GPU process will restart shortly.
[82:1:0414/220553.270196:ERROR:command_buffer_proxy_impl.cc(327)] GPU state invalid after WaitForGetOffsetInRange.
[5:5:0414/220553.329794:ERROR:gpu_process_host.cc(954)] GPU process exited unexpectedly: exit_code=8704
[141:10:0414/220554.653813:ERROR:command_buffer_proxy_impl.cc(127)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[116:7:0414/220554.662505:ERROR:command_buffer_proxy_impl.cc(127)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[862:862:0414/220554.773952:ERROR:gl_utils.cc(431)] [.WebGL-0x2cd4000e9500]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels
[862:862:0414/220554.886127:ERROR:gl_utils.cc(431)] [.WebGL-0x2cd4000e9500]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels
[862:862:0414/220554.955328:ERROR:gl_utils.cc(431)] [.WebGL-0x2cd4000e9500]GL Driver Message (OpenGL, Performance, GL_CLOSE_PATH_NV, High): GPU stall due to ReadPixels
If I add that one back then hardware acceleration works again, however, I still get the flickering issue.. hmm
Running hyprland with my nvidia gtx 1650 and proprietary drivers btw, and brave browser is running natively and not under xwayland
Last edited by RobinSch (2025-04-14 20:28:50)
Offline
however, I still get the flickering issue.. hmm
Get rid of VaapiIgnoreDriverChecks too.
And did you also drop this flag?
Offline
RobinSch wrote:however, I still get the flickering issue.. hmm
tekstryder wrote:Get rid of VaapiIgnoreDriverChecks too.
And did you also drop this flag?
Yes I did
I also noticed that if I remove all the flags (launch it without any at all), then brave://gpu still reports "Hardware accelerated", however, if I go to for example youtube it does not work (as expected). I still get flickering/glitches
If I also remove the only env variable still set, the __EGL_VENDOR_LIBRARY_FILENAMES, then brave://gpu no longer shows hardware accelerated (and the same errors as mentioned before show) and the flickering/glitches no longer occurs
Last edited by RobinSch (2025-04-15 13:58:15)
Offline
hey so i can't for the life of me to get hardware acceration to work for me on brave. it says it's working under brave://gpu and under vainfo etc but when i go to play a youtube video 90% cpu useage and 0% gpu decode useage. my system has av1 decode on it so idk why this is/ i've tried everythign mentioned under the arch wiki for video accleration on chorumium
Offline
says it's working under brave://gpu
brave://gpu still reports "Hardware accelerated"
In chromium-based browsers this only indicates that the browser's compositing is GPU accelerated.
It means nothing in regard to video decoding hardware acceleration.
tekstryder wrote:Get rid of VaapiIgnoreDriverChecks too.
tekstryder wrote:And did you also drop this flag?
Yes I did
That's curious. I can actually reproduce both the stuttering/flickering you noted, along with the same EGL-related journal errors when I enable VaapiIgnoreDriverChecks.
What does your EGL situation look like?
pacman -Qs egl
eglinfo -b
If possible, show output of eglinfo -b with and without __EGL_VENDOR_LIBRARY_FILENAMES set. I know zilch about hyprland, perhaps this is required for some reason?
Is this a single/discrete GPU system?
Last edited by tekstryder (2025-04-16 15:21:12)
Offline
Tried it yesterday with AMD GPU on Wayland, and it works for me with only
--ozone-platform=wayland
--enable-features=VaapiVideoDecoder,VaapiIgnoreDriverChecks,Vulkan,DefaultANGLEVulkan,VulkanFromANGLE
In .config/chromium-flags.conf and in .config/electron-flags.conf (for electron apps).
Offline
Hey guys, I'm also able to reproduce the flickering, when VA-API is enabled for chromium/electron apps. I've tested vesktop 1.5.6-1 from AUR
I've also tested, if this was a case of AMD IGPU in different system - it wasn't. It's something in between of NVIDIA drivers and Chromium.
Running a single RTX 3060 GPU, WM is Hyprland.
Running 570.133.07 GPU drivers with Electron 35.1.5 & Chromium 134.0.6998.179
Here's output from eglinfo -B WITHOUT __GLX_VENDOR_LIBRARY_NAME
Here's WITH (they're identical anyway)
Here's output from pacman -Qs egl
local/egl-gbm 1.1.2.1-1
The GBM EGL external platform library
local/egl-wayland 4:1.1.18-1
EGLStream-based Wayland external platform
local/egl-x11 1.0.0-1
NVIDIA XLib and XCB EGL Platform Library
local/eglexternalplatform 1.2-2
EGL External Platform interface
local/freeglut 3.6.0-1
Free OpenGL Utility Toolkit
local/lib32-libglvnd 1.7.0-1
The GL Vendor-Neutral Dispatch library
local/lib32-wayland 1.23.1-1
A computer display server protocol
local/libglvnd 1.7.0-1
The GL Vendor-Neutral Dispatch library
local/mesa-utils 9.0.0-5
Essential Mesa utilities
local/texlive-latexextra 2025.2-1 (texlive)
TeX Live - LaTeX additional packages
local/wayland 1.23.1-1
A computer display server protocol
I have also noticed the exact same flickering, when app was running without this flag.
--enable-features=WaylandLinuxDrmSyncobj
My guess, is that something is screwing up this protocol, when VA-API is enabled.
Last edited by vladyk144 (2025-04-19 21:11:57)
Offline
In chromium-based browsers this only indicates that the browser's compositing is GPU accelerated.
It means nothing in regard to video decoding hardware acceleration.
At least for brave it shows dedicated sections for video decoding/encoding:
* Video Decode: Hardware accelerated
* Video Encode: Software only. Hardware acceleration disabled (as expected)
That's curious. I can actually reproduce both the stuttering/flickering you noted, along with the same EGL-related journal errors when I enable VaapiIgnoreDriverChecks.
I also get the stuttering/flickering issue and the EGL-related error without the VaapiIgnoreDriverChecks btw
What does your EGL situation look like?
$ pacman -Qs egl
local/egl-gbm 1.1.2.1-1
The GBM EGL external platform library
local/egl-wayland 4:1.1.18-1
EGLStream-based Wayland external platform
local/egl-x11 1.0.0-1
NVIDIA XLib and XCB EGL Platform Library
local/eglexternalplatform 1.2-2
EGL External Platform interface
local/freeglut 3.6.0-1
Free OpenGL Utility Toolkit
local/libglvnd 1.7.0-1
The GL Vendor-Neutral Dispatch library
local/qemu-ui-egl-headless 9.2.3-1
QEMU EGL headless UI driver
local/wayland 1.23.1-1
A computer display server protocol
eglinfo with __EGL_VENDOR_LIBRARY_FILENAMES: https://l.robinsch.net/hCTn2l.txt => gives "eglinfo: eglInitialize failed", however, video decoding works regardless so I guess this error has to do with something else? I'm not too sure
eglinfo without it: https://l.robinsch.net/Mny9oM.txt => it seems like it tries my AMD integrated GPU, which I do not want.
I have found this environment variable from here https://github.com/elFarto/nvidia-vaapi-driver
Last edited by RobinSch (Yesterday 17:13:33)
Offline
tekstryder wrote:In chromium-based browsers this only indicates that the browser's compositing is GPU accelerated.
It means nothing in regard to video decoding hardware acceleration.
At least for brave it shows dedicated sections for video decoding/encoding:
* Video Decode: Hardware accelerated
Again, if that's under the brave://gpu page heading "Graphics Feature Status" listing, it's poorly worded and refers to compositing.
In my case that's been enabled for years before actual video GPU-accelerated decoding was possible.
The only way to verify for certain with nVidia is via nvtop. You will see the "Dec" usage bar show up and percentage of GPU usage for decoding.
EDIT: brave://media-internals will also show what decoder is in use.
According to #1136 you DO have functional GPU accelerated video decoding, albeit with the flickering issue.
Are you certain? Check with nvtop. My output in #1135 shows the decoding in action
I also get the stuttering/flickering issue and the EGL-related error without the VaapiIgnoreDriverChecks btw
I don't have a theory on the flickering as I cannot reproduce without that flag.
You and @vladyk144 are both on hyprland, that's all I see in common. Works fine under Mutter here.
it seems like it (also) tries my AMD integrated GPU, which I do not want.
Is this a single/discrete GPU system?
Well yeah, that's why I asked this.
Last edited by tekstryder (Yesterday 16:31:52)
Offline
Again, if that's under the brave://gpu page heading "Graphics Feature Status" listing, it's poorly worded and refers to compositing.
In my case that's been enabled for years before actual video GPU-accelerated decoding was possible.
Ahh I see, that's very misleading then...
Yes, my bad for wording it poorly. Hardware decoding (via my nvidia GPU) is working (just confirmed via both nvtop and nvidia-smi), however, I have this flickering issue (with the same flags as you have in #1135).
Also if I remove that __EGL_VENDOR_LIBRARY_FILENAMES env variable, then hardware decoding no longer works (as it tries my AMD iGPU in that case, I think?), so I guess on dual GPU systems that variable is needed? Or at least in my case
Last edited by RobinSch (Yesterday 17:12:01)
Offline