Arch Linux

EcoPack34

Member

Registered: 2025-07-20

Posts: 4

[Solved] HVEC videos wont play on discord/vesktop

I've recently moved from Fedora to Arch using hyprland. When I installed discord (and also with vesktop) videos that use HVEC won't play, they only have sound.

This only happens in both discord and vesktop, and not other apps like mpv or firefox.

My setup is a Ryzen 7600x + RTX 3060 TI.
I have the nvidia-dkms driver installed.

I friend was having the same issue, but he was on an amd gpu. He fixed it by using the following arguments:

--enable-features=DefaultANGLEVulkan,VaapiIgnoreDriverChecks,Vulkan,VulkanFromANGLE

In my case, this makes it worse as I also loose audio when using it.

In case it helps, here are the outputs of "vainfo" and "vulkaninfo --summary":

vainfo:

Trying display: wayland
vainfo: VA-API version: 1.22 (libva 2.22.0)
vainfo: Driver version: VA-API NVDEC driver [direct backend]
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileVC1Simple              :	VAEntrypointVLD
      VAProfileVC1Main                :	VAEntrypointVLD
      VAProfileVC1Advanced            :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointVLD
      VAProfileHEVCMain               :	VAEntrypointVLD
      VAProfileVP8Version0_3          :	VAEntrypointVLD
      VAProfileVP9Profile0            :	VAEntrypointVLD
      VAProfileAV1Profile0            :	VAEntrypointVLD
      VAProfileHEVCMain10             :	VAEntrypointVLD
      VAProfileHEVCMain12             :	VAEntrypointVLD
      VAProfileVP9Profile2            :	VAEntrypointVLD
      VAProfileHEVCMain444            :	VAEntrypointVLD
      VAProfileHEVCMain444_10         :	VAEntrypointVLD
      VAProfileHEVCMain444_12         :	VAEntrypointVLD

vulkaninfo --summary:

==========
VULKANINFO
==========

Vulkan Instance Version: 1.4.313


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_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
VK_NV_display_stereo                   : extension revision 1

Instance Layers: count = 2
--------------------------
VK_LAYER_NV_optimus NVIDIA Optimus layer 1.4.303  version 1
VK_LAYER_NV_present NVIDIA GR2608 layer  1.4.303  version 1

Devices:
========
GPU0:
	apiVersion         = 1.4.303
	driverVersion      = 575.64.3.0
	vendorID           = 0x10de
	deviceID           = 0x2489
	deviceType         = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
	deviceName         = NVIDIA GeForce RTX 3060 Ti
	driverID           = DRIVER_ID_NVIDIA_PROPRIETARY
	driverName         = NVIDIA
	driverInfo         = 575.64.03
	conformanceVersion = 1.4.1.0
	deviceUUID         = 314ea80f-deaa-8a67-3dcd-b2c39a86189f
	driverUUID         = bc3026c2-9553-594d-9556-64cc156ab6f9

Last edited by EcoPack34 (2025-07-21 10:15:31)

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 71,610

Re: [Solved] HVEC videos wont play on discord/vesktop

Please use [code][/code] tags, not "quote" tags. Edit your post in this regard.

On topic: https://bbs.archlinux.org/viewtopic.php … 9#p2245469 ?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Xephon

Member

Registered: 2024-12-22

Posts: 189

Re: [Solved] HVEC videos wont play on discord/vesktop

Did you try the following launch flags

--enable-features=AcceleratedVideoDecodeLinuxGL,AcceleratedVideoDecodeLinuxZeroCopyGL,VaapiOnNvidiaGPUs,VaapiIgnoreDriverChecks

?

EcoPack34

Member

Registered: 2025-07-20

Posts: 4

Re: [Solved] HVEC videos wont play on discord/vesktop

Did you try the following launch flags

--enable-features=AcceleratedVideoDecodeLinuxGL,AcceleratedVideoDecodeLinuxZeroCopyGL,VaapiOnNvidiaGPUs,VaapiIgnoreDriverChecks

?

Doesn't work as well, similar effect as the one I mentioned before.

Xephon

Member

Registered: 2024-12-22

Posts: 189

Re: [Solved] HVEC videos wont play on discord/vesktop

Is your monitor connected to iGPU or dGPU?

EcoPack34

Member

Registered: 2025-07-20

Posts: 4

Re: [Solved] HVEC videos wont play on discord/vesktop

connected into dGPU.

Xephon

Member

Registered: 2024-12-22

Posts: 189

Re: [Solved] HVEC videos wont play on discord/vesktop

Disable iGPU in BIOS if you're not using it. Headless iGPU interferes with an application ability to select a correct rendering device.

Last edited by Xephon (2025-07-20 18:16:22)

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 71,610

Re: [Solved] HVEC videos wont play on discord/vesktop

https://wiki.hypr.land/Configuring/Multi-GPU/
The "nvidia_drm.modprobe=1" https://wiki.archlinux.org/title/Kernel_parameters (only! that!) will block the simpledrm device and restore normal card order what has helped in the past, but according to the vulkan summary, there does not even seem to be a second GPU?

Did you see the other thread and the reference to the nvidia vaapi shim there?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

EcoPack34

Member

Registered: 2025-07-20

Posts: 4

Re: [Solved] HVEC videos wont play on discord/vesktop

https://wiki.hypr.land/Configuring/Multi-GPU/
The "nvidia_drm.modprobe=1" https://wiki.archlinux.org/title/Kernel_parameters (only! that!) will block the simpledrm device and restore normal card order what has helped in the past, but according to the vulkan summary, there does not even seem to be a second GPU?

Did you see the other thread and the reference to the nvidia vaapi shim there?

After completely disabling the iGPU and adding some more enviroment variables in the thread you mentioned it finally works.

Thanks a lot for the help.

Xephon

Member

Registered: 2024-12-22

Posts: 189

Re: [Solved] HVEC videos wont play on discord/vesktop

1. You can't infer the amount of GPUs from the vulkan summary. If vulkan-radeon is not installed there will be no output for AMD GPU. And OP just confirmed that.

2. elFarto driver is in the official repos and since OP said "recently moved from Fedora to Arch" there was no reason to suspect that the driver was outdated.

3. If you think that electron apps select rendering device based on "normal card order" you're delusional.

4. Disabling headless iGPU is exactly what's needed to avoid problems in chromium-based apps on NVIDIA GPUs
https://bbs.archlinux.org/viewtopic.php … 1#p2250341

seth

Member

From: Don't DM me only for attention

Registered: 2012-09-03

Posts: 71,610

Re: [Solved] HVEC videos wont play on discord/vesktop

You can't infer the amount of GPUs from the vulkan summary.

No, but I guess we can infer facts out of the absence of information…

If you think that electron apps select rendering device based on "normal card order" you're delusional.

Me and everyone in https://bbs.archlinux.org/viewtopic.php?id=302138 it would seem.

Also https://bbs.archlinux.org/viewtopic.php … 1#p2250341

I'd also suggest to disable your iGPU in BIOS, because headless iGPU often leads to issues … I assume that Chromium is trying to launch with the AMD iGPU, not finding drivers for it, and having the GPU process crash as a result.

So we all agree that electron makes an uninformed guess about what GPU to render on and that ambiguity needs to be addressed?
So let's hear your take on what drives that uninformed guess.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc