The vdpau driver is located under /usr/lib64/dri/ but the default path of LIBVA_DRIVER links to /usr/lib/dri/ - I then changed the environment var in my zshconfig.
I want to get “gpuVideoDecoder” under chrome://media-internals as in the linked post described. But even after all the steps and searching the state still persists, chromium seems to be using software rendering and doesn’t utilizes the gpu for video decoding.
I have no idea what is missing or if it’s even possible to get this working with an nvidia gpu.
So my question is, is there anyone with a working setup, having a nvidia gpu?
Any suggestions what I could have missed are appreciated as well.
Thanks for your reply.
I thought the default chromium in fedora is already the patched one with VAAPI support
I’m using the default chromium, not the VAAPI-version you are also referring to.
Out of curiosity I’ve just installed the vaapi-version next to the default one but it doesn’t make a difference…
still the same decoder and around the same cpu usage.
Unfortunately, hw video acceleration with chromium (either Fedora or RPM Fusion chromium-vaapi, both have vaapi support enabled at this time) doesn’t work with the proprietary NVIDIA driver. Even when using the vdpau->vaapi bridge that might work with others software.
It’s also sometimes broken with intel vaapi backend. I don’t know about AMD vaapi.
At least, this is the current situation as of today 2019/06/28.
This is not a specific distro behavior (it should be working/broken for all distros). If you have more information or can provide help, feel free to report issue to bugzilla.redhat.com or bugzilla.rpmfusion.org or use the upstream chromium bug tracker.
Thanks for your response.
Good to know that this doesn’t even work with intel graphics all the time for others, because that has been the case with my integrated gpu before installing the nvidia card.
I’ll definitely report back to one of the platforms as soon as I get the impression it might be of use to anyone.
Nvidia libva driver which is a vaapi—> vdpau translation driver doesn’t support VPP (video post processing) i.e VAProfileNone, so I’m trying to disable it in the next update and enable vaapi for Nvidia users.
Please note that,
vdpau is not supported on wayland.
vdpau doesn’t support vp9 decoding even if the card supports it.
Pack parameters work incorrectly with pack buffer bound: 563714 Applied Workarounds: pack_parameters_workaround_with_pack_buffer
Alignment works incorrectly with unpack buffer bound: 563714 Applied Workarounds: unpack_alignment_workaround_with_unpack_buffer
Framebuffer discarding can hurt performance on non-tilers: 570897 Applied Workarounds: disable_discard_framebuffer
Unpacking overlapping rows from unpack buffers is unstable on NVIDIA GL driver: 596774 Applied Workarounds: unpack_overlapping_rows_separately_unpack_buffer
Disable KHR_blend_equation_advanced until cc shaders are updated: 661715 Applied Workarounds: disable(GL_KHR_blend_equation_advanced), disable(GL_KHR_blend_equation_advanced_coherent)
glTexStorage* are buggy when base mipmap level is not 0: 877874 Applied Workarounds: reset_base_mipmap_level_before_texstorage
Some drivers can’t recover after OUT_OF_MEM and context lost: 893177 Applied Workarounds: exit_on_context_lost
adjust src/dst region if blitting pixels outside framebuffer on Linux NVIDIA: 830046 Applied Workarounds: adjust_src_dst_region_for_blitframebuffer
Native GpuMemoryBuffers have been disabled, either via about:flags or command line. Disabled Features: native_gpu_memory_buffers
Viz hit-test surface layer version is not enabled by default. Disabled Features: viz_hit_test_surface_layer
Skia renderer is not used by default. Disabled Features: skia_renderer
